Closed runborg closed 1 week ago
The value causing this error is also logged, but at a DEBUG
level, this can be seen here: https://github.com/Uninett/zino/blob/master/src/zino/tasks/juniperalarmtask.py#L51-L55
When changing the log level to debug we see what the values recorded are:
2024-05-29 15:07:21,953 - DEBUG - zino.tasks.juniperalarmtask (MainThread) - Yellow alarm count: value ''. Red alarm count: value ''.
And when running snmpget -v2c -c community host-name 1.3.6.1.4.1.2636.3.4.2.2.2
(jnxYellowAlarmCount
) on such a router we get
iso.3.6.1.4.1.2636.3.4.2.2.2 = No Such Object available on this agent at this OID
so it seems like for juniper routers that do not have a yellow/red alarm count this error happens.
This might be relevant for NAV as well.
This might be relevant for NAV as well.
I don't think so. NAV's SNMP code is a bit more mature than Zino 2 :)
Not entirely closed until changes in the alarmtask is done
After running the server for a while I get quite a number of devices that returns a string instead of an int alarm count. This gives the error:
the error does not give any indications of whats inside the value retrieved. if this is a unsupported feature on the platform or if there are other issues?
Looking into this it looks like the same routers reporting this error and the "router count" is stable...
48 out of our routers returns this, and i'm able to produce a list of affected routers if there is interest in this for troubleshooting.