# Core 142 - check\_mk\_agent removed

**URL:** <https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428>\
**Category:** Monitoring\
**Created:** [28 February 2020 07:19 UTC](https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428 "2020-02-28T07:19:17Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![pablo78](https://community.ipfire.org/user_avatar/community.ipfire.org/pablo78/32/12788_2.png) [@pablo78](https://community.ipfire.org/u/pablo78)\
**Post date:** [28 February 2020 07:19 UTC](https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428/1 "2020-02-28T07:19:17Z")

</div>

Hello, everybody.

Unfortunately I had to hear that starting with Core 142 the package check\_mk\_agent is no longer offered and removed from the system. I was able to monitor the router with this package from my check\_mk server and also collect the up- and download rates. Is there a possibility to continue using this package?

With kind regards  
Paul

---

<div class="post-metadata">

**Author:** ![pablo78](https://community.ipfire.org/user_avatar/community.ipfire.org/pablo78/32/12788_2.png) [@pablo78](https://community.ipfire.org/u/pablo78)\
**Post date:** [29 February 2020 10:02 UTC](https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428/2 "2020-02-29T10:02:04Z")

</div>

It’s a pity that this evaluation is no longer possible from Core 142.

 ![check_mk-Output](https://community.ipfire.org/uploads/default/original/1X/28ff39c32145a412d76e15f707b3231a88bafc26.png)

---

<div class="post-metadata">

**Author:** ![pablo78](https://community.ipfire.org/user_avatar/community.ipfire.org/pablo78/32/12788_2.png) [@pablo78](https://community.ipfire.org/u/pablo78)\
**Post date:** [10 March 2020 14:18 UTC](https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428/3 "2020-03-10T14:18:45Z")

</div>

Too bad that there is no reaction of the developers. I would like to know how others monitor the router itself.

---

<div class="post-metadata">

**Author:** ![xperimental](https://community.ipfire.org/user_avatar/community.ipfire.org/xperimental/32/16702_2.png) [@xperimental](https://community.ipfire.org/u/xperimental)\
**Post date:** [10 March 2020 14:24 UTC](https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428/4 "2020-03-10T14:24:09Z")

</div>

With SMP 😀

---

<div class="post-metadata">

**Author:** ![pablo78](https://community.ipfire.org/user_avatar/community.ipfire.org/pablo78/32/12788_2.png) [@pablo78](https://community.ipfire.org/u/pablo78)\
**Post date:** [10 March 2020 14:26 UTC](https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428/5 "2020-03-10T14:26:49Z")

</div>

You probably mean SNMP but that’s not as charming and as with the check\_mk\_agent and the traffic analysis is also not really that well implemented.

There are agents everywhere. In my company nsclient++, nagios-nrpe or the check\_mk agent (home) and now I have to switch to SNMP by force. This will be a fiddle, if it works out.

---

<div class="post-metadata">

**Author:** ![xperimental](https://community.ipfire.org/user_avatar/community.ipfire.org/xperimental/32/16702_2.png) [@xperimental](https://community.ipfire.org/u/xperimental)\
**Post date:** [10 March 2020 14:35 UTC](https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428/6 "2020-03-10T14:35:30Z")

</div>

At least you will be able to monitor your printers and CCTV together with your firewall with one SNMP server (and maybe others). Yep SMP is out!

---

<div class="post-metadata">

**Author:** ![pablo78](https://community.ipfire.org/user_avatar/community.ipfire.org/pablo78/32/12788_2.png) [@pablo78](https://community.ipfire.org/u/pablo78)\
**Post date:** [10 March 2020 14:36 UTC](https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428/7 "2020-03-10T14:36:57Z")

</div>

What ist CCTV or SMP?  
So there will be no way to monitor the router except the insecure and complicated SNMP?

---

<div class="post-metadata">

**Author:** ![xperimental](https://community.ipfire.org/user_avatar/community.ipfire.org/xperimental/32/16702_2.png) [@xperimental](https://community.ipfire.org/u/xperimental)\
**Post date:** [10 March 2020 14:41 UTC](https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428/8 "2020-03-10T14:41:10Z")

</div>

And of course your managed network switches. SMP is the precursor of SNMP. CCTV == video surveillance.

---

<div class="post-metadata">

**Author:** ![arne\_f](https://community.ipfire.org/user_avatar/community.ipfire.org/arne_f/32/12760_2.png) [@arne\_f](https://community.ipfire.org/u/arne_f)\
**Post date:** [10 March 2020 14:49 UTC](https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428/9 "2020-03-10T14:49:00Z")

</div>

It was not maintained for years more than 5 years. A user want it has build in and not do the maintaining work.

> [@pablo78](#):
>
> There are agents everywhere. In my company nsclient++, nagios-nrpe or the check\_mk agent (home)

That is a second reason to remove. Why we need two of such agents. nagios\_nrpe is still available.

---

<div class="post-metadata">

**Author:** ![pablo78](https://community.ipfire.org/user_avatar/community.ipfire.org/pablo78/32/12788_2.png) [@pablo78](https://community.ipfire.org/u/pablo78)\
**Post date:** [26 May 2020 18:34 UTC](https://community.ipfire.org/t/core-142-check-mk-agent-removed/1428/10 "2020-05-26T18:34:48Z")

</div>

I was able to successfully integrate my router into my CheckMK monitoring using NRPE check and Check\_MK via SSH.  
Maybe this will help you a little bit.

[Check\_mk - Invoking over SSH](https://checkmk.com/cms_agent_linux.html#ssh)

[My CheckMK-Forum Thread](https://forum.checkmk.com/t/check-speedtest-sh-socket-timeout-after-10-seconds/17959/26)

 ![my-router-check](https://community.ipfire.org/uploads/default/original/2X/d/d4ce203c4355bd5e92432b6e71a7d9db24f02306.png)
