I am basing my question on the logic that a device can be polled successfully at 09:54:00, go off-line at 09:54:32 and return on-line again at 09:54:98 in time for the next NMS poll and this would show no down time at all.
What I am seeing is the opposite, in that I think the device is being polled and is failing to respond, then it is coming back on-line x seconds later and is then being successfully polled and the NMS is reporting a down time of 49 seconds (the difference between when it physically came back on-line and when it was next polled). Does the SNMP Agent have some internal mechanism to retain the up/down time duration so that it can be reported back to the NMS when it is back on-line and successfully being polled, or is the value of 49 seconds down-time duration being generated by the NMS system as to how long ago it was since it was successfully able to poll the device. If it is the latter why would this be 49 seconds if the attempts to poll interval is every 60 seconds?
My network monitoring is set up to poll every 60 seconds and has an icmp threshold set of 2 seconds.
As I understand it, this means that every 60 seconds a device will be sent a ping and it has up to 2 seconds with which to respond otherwise it is classed as down.
Looking at the reports I can see that a router did not respond and shows a down duration of 49 seconds, before reporting up time of 1 minute in the next entry. What I am trying to work out is how it got to this 49 second duration value?
If the NMS was set to ping the device every 60 seconds and the first ping occurred at 09:54:00 and succeeded, the next poll would be at 09:55:00. Lets say that the 09:55:00 icmp poll was unsuccessful. This is then reported back to the NMS as down. It would then try and poll again at 09:56 to see if the device is back on-line and in my case it was, only the total downtime shows as 49 seconds
Should this not always be 1 minute or multiples thereof?
Could it be that the NMS system once detecting that a device is down, will then step up it’s polling to that down device with repeat polls for a specified period until it gives up and reverts back to it’s regular schedule. I.e. it pings every second and on the 49th second it got a response?
Wi-Fi 6 vs. 5G: Who is the winner? What’s the best one? Which one to choose?You may have heard these topics in many articles and conversations. But the fact is that if you choose one over the other, you may fail to provide your organization with the best ...
Whilst carrying out resilience testing to confirm igp/ebgp multipath is working, I have stumbled upon the below issue.The attached sketch crudely shows the topolgy of the network. 2 cores with a cross connect running ibgp, from each of the cores I have 1 ...
Learn how Cisco wireless assurance provides real-time and historical analytics for deep network visibility and simplified troubleshooting.
Learn how you can easily manage all of your connected devices and services and identify and solve issues before they...
I have a device connected to an access switch port. I would like to configure a net flow to gather the amount of traffic going via the interface. I will be sending all that data to SolarWinds. My question is how do I configure a netflow on WS-C6506. I tri...
Hello, We are working on a spare switch (with 12 fibre modules), which needs to be used as the failover switch in our company data centre. Cisco switch model : WS-C3750-12S(PowerPC405) Can you confirm the below : i. Does this switch su...