snmpAgentDown blocks BoxDown event
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
High
|
Morten Brekkevold |
Bug Description
NAV 4.2.2
We have had a couple of cases where boxes were down, but NAV belived they were still up.
Symptoms:
The box is down and does not answer to ping.
Nav Status is "Uptime Up for X days Y hours", while Availability counts down
Both times we see a SnmpAgentDown imidiately before the box is marked as down.
eventengine.
eventengine.
eventengine.
pping.log:
ipdevpoll.
Changed in nav: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Morten Brekkevold (mbrekkevold) |
status: | Confirmed → In Progress |
Changed in nav: | |
status: | Fix Committed → Fix Released |
fix consisting of multiple changesets merged here: https:/ /nav.uninett. no/hg/stable/ rev/b462c09dbbb 9
This includes changes to snmpAgentState event handling, where snmpAgentDown alerts will be willfully held back if the netbox itself has stopped responding to ping while we were waiting for an snmpAgentUp resolve. It's kind of given that the box stops responding to snmp if its down, we don't need an extra alert for that.