Closed joschi99 closed 2 years ago
I don't understand the problem with option: --threshold-overload='psu,OK,offEnvOther'
?
The problem is that we have to exclude this problem using option --threshold-overload. But the main problem is that the plugin shows the interfaces as PSU and this is not correct. And if a interface is not in status UP, we have the problem with status offEnvOther. Using the option --threshold-overload to avoid this problem has the risk that maybe a real PSU in the status offEnvOther should not recognized correctly.
Could you provide a snmpwalk of the following branches:
.1.3.6.1.4.1.9.9.117.1.1.2
.1.3.6.1.4.1.9.9.13.1.5.1
I don't know if i can do the diff between power supplies type.
snmpwalk -On -v2c -cpublic x.x.x.x .1.3.6.1.4.1.9.9.13.1.5.1
.1.3.6.1.4.1.9.9.13.1.5.1.2.1 = STRING: "Power Supply 1"
.1.3.6.1.4.1.9.9.13.1.5.1.2.2 = STRING: "Power Supply 2"
.1.3.6.1.4.1.9.9.13.1.5.1.3.1 = INTEGER: 1
.1.3.6.1.4.1.9.9.13.1.5.1.3.2 = INTEGER: 1
.1.3.6.1.4.1.9.9.13.1.5.1.4.1 = INTEGER: 2
.1.3.6.1.4.1.9.9.13.1.5.1.4.2 = INTEGER: 2
the other snmpwalk you can find here: .1.3.6.1.4.1.9.9.117.1.1.2.txt
Maybe i should add an option: --add-fru-psu
option ? Because i don't have a solution to avoid that error.
could be a idee. So with this option we can decide to use .1.3.6.1.4.1.9.9.117.1.1.2 OID's?
Yes. By default, we don't check fru psu.
Sounds good
On a catalyst 4xxx with Linecard modules WS-X4648-RJ45V+E every interface will be shown as PSU on environment mode in additional to the correct PSU. And any interface with port status down will be threated as a problem while status is offEnvOther:
Using option
--threshold-overload='psu,OK,offEnvOther'
solved this problem in this case, but the problem is that this are not PSU and probably there is some issue on the environment mode.