Hi Matt,
You can use "filter-interfaces"
(https://www.juniper.net/documentation/en_US/junos13.3/topics/reference/conf
iguration-statement/filter-interfaces-edit-snmp.html ), if it is possible,
and a decent (like 5 min) check interval.
Silviu Mocanu
···
-----Original Message-----
From: checkmk-en-bounces@lists.mathias-kettner.de
[mailto:checkmk-en-bounces@lists.mathias-kettner.de] On Behalf Of Matthew
Nickerson
Sent: Wednesday, November 11, 2015 4:58 PM
To: checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] Check_MK, SNMP, Juniper, Help!
Thank you to everyone who contributed to this. It is helpful.
On 11/10/2015 4:28 PM, Raphael Mazelier wrote:
...
That says, this is not completly impossible to safely monitor this
type of device using snmp (I suppose we talk about EX2200, 3300, 45XX,
with cheap cpu, high end router do not pose problem).
Actually, my biggest "problem switch" is an EX8216! That said, it has a
very high port density.
- cacti is the right way to do : first poll to detect/scan wich
interface are present (poller cache), and then at each run do small
We actually cacti have a cacti server ready to use here. And perhaps I
could use the 'thold' plugin to generate syslog message, sending them to the
check_mk event console. This might be the way to go.
Again, this list is a great resource thanks all!
Matt
--
Matthew Nickerson
Network Engineer
Computing Facilities, SCS
Carnegie Mellon University
(412) 268-7273
_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en
________________________________
This e-mail and any attachment(s) are intended only for the recipient(s)
named above and others who have been specifically authorized to receive
them. They may contain confidential information. If you are not the intended
recipient, please do not read this email or its attachment(s). Furthermore,
you are hereby notified that any dissemination, distribution or copying of
this e-mail and any attachment(s) is strictly prohibited. If you have
received this e-mail in error, please immediately notify the sender by
replying to this e-mail and then delete this e-mail and any attachment(s) or
copies thereof from your system. Thank you.
This e-mail and any attachment(s) are intended only for the recipient(s) named above and
others who have been specifically authorized to receive them. They may contain confidential
information. If you are not the intended recipient, please do not read this email or its
attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or
copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this
e-mail in error, please immediately notify the sender by replying to this e-mail and then
delete this e-mail and any attachment(s) or copies thereof from your system. Thank you.