[j-nsp] Solarwinds Monitoring Problem

Paul Stewart paul at paulstewart.org
Sat Jun 5 09:23:53 EDT 2010


Hi folks...

 

I'm starting here to see if anyone has seen this behaviour before by
chance....

 

We're in a migration to Solarwinds for monitoring of our network resources.
On the network are several Juniper devices (and lots more coming soon).  

 

Every so often (about once a month or so), the Solarwinds system triggers
with a "node down" alarm.  When this occurs, it's showing a Juniper device
(which varies) as "down".  Definition of "down" simply means it's not
pingable.

 

The behaviour we're seeing is that from the Solarwinds server we suddenly
cannot ping the remote Juniper device - however - we continue to monitor
SNMP successfully on that device.  These Juniper devices have been MX480,
EX3200 and EX4200 to date.  During these outages I have been able to ping
these devices from any other location on our network except the Solarwinds
server.  

 

If I reboot the Solarwinds server, the alarm clears so I thought this is
clearly an issue with the monitoring system ... but ... recently I rebooted
one of the Juniper switches and the issue cleared as well....

 

Logs on the Juniper devices are clean - nothing indicating a problem.
Solarwinds systems doesn't show anything of interest...

 

Thoughts? ;) I'm thinking of setting up another open source monitoring
solution just to further eliminate the Juniper side of this...

 

Paul

 

 

 



More information about the juniper-nsp mailing list