Thanks for the info ,good to know, (cpu never went over 5% though)

We shut down the monitor today and the switch rebooted twice, and now appears 
to have crashed.

As Kurt pointed out if the FW upgrade doesn't fix it , it just maybe the 
hardware


From: bern...@yosemite.edu
To: ntsys...@lists.myitforum.com
Subject: RE: [NTSysADM] PRTG  crashed a switch?
Date: Wed, 15 Jul 2015 23:12:52 +0000











I don’t know about PRTG in particular, but in general I have read of monitoring 
systems crashing or causing high CPU
 utilization on the monitored device.  But the affected devices are usually 
small embedded types of things; I wouldn’t expect a network switch to be 
affected (although I think some of the high
cpu utilization reports were for a NetApp filer).
 
References:
 
How to disable combining SNMP
varbinds (getbulk)?
https://www.zabbix.com/forum/showthread.php?t=45001
 
there should be a way to disable SNMP bulk for each interface
https://support.zabbix.com/browse/ZBXNEXT-2301
 
--

Edward
Berner
 
 


From: listsadmin@lists.myitforum.com
 [mailto:listsadmin@lists.myitforum.com] On Behalf Of J- P

Sent: Wednesday, July 15, 2015 9:29 AM

To: NT

Subject: [NTSysADM] PRTG crashed a switch?


 

Hi all



Went onsite yesterday to check out some network issues, so I fired up PRTG and 
let it do its thing.

Later in the evening when I'm home I VPN into the site and after 12 minutes my 
vpn drops , I check the public IP internet is up.



I call the IT mgr and let him know that I cant authenticate, he goes to the 
office  and tells me the core switch (240 port procurve) is lit up like  
Christmas tree (all lights flashing), no telnet no ssh no ping reply , he does 
a physical shutdown , and I'm
 back in , ten minutes later it drops again this happened 4 times.



Finally the last time it remains online, they are telling me that this "has 
never happened before"  (at least that they know of it was late at night)



Oh and the logs on the switch only show 2 entries



1. First time installation 

2. Warning loss of link on B10



So is it possible that PRTG caused this, or is likley they've never been around 
that late to realize this?

 

                                          

Reply via email to