I ran into a PoE (power-over-ethernet) error on one of our Aruba switches (5400R ZL2). An error on a particular port that my existing Zabbix monitors didn't catch. Basically the PoE status on a single port is 'otherFault'. I found it in SNMP, but the discovery is unusual.
The OID is pethPsePortDetectionStatus and the walk looks like this:
The index includes a "group" which means the "box in the stack" or a "module in a rack". As this is a modular switch, that number changes. So '3.65' is on blade C. The 64 matches the regular interface index (C1).
But it presents a challenge. I can't just add 'pethPsePortDetectionStatus' to the Network discovery item prototype. And I don't see a way to associate it with an interface. I've looked at preprocessing for a discovery rule, but it won't ever match the SNMPINDEX of the Network interface discovery rule. And with the data I have, the best I could do with a separate discovery rule is translate the '3' part to 'C'. Although I don't know how see the data the discovery rule is using. And I don't think there's any way to lookup the IfDescr in javascript in a preprocessing step.
Right now, I just have a separate Application with these all grouped together with depressing names like "POE Port Status 5.129". That's real helpful in a trigger. At least I know something is wrong.
Anyone have any bright ideas on how to handle this?
- Steve
The OID is pethPsePortDetectionStatus and the walk looks like this:
Code:
POWER-ETHERNET-MIB::pethPsePortDetectionStatus.3.65 = INTEGER: searching(2) POWER-ETHERNET-MIB::pethPsePortDetectionStatus.3.66 = INTEGER: deliveringPower(3) POWER-ETHERNET-MIB::pethPsePortDetectionStatus.3.67 = INTEGER: deliveringPower(3) POWER-ETHERNET-MIB::pethPsePortDetectionStatus.3.68 = INTEGER: searching(2) ... POWER-ETHERNET-MIB::pethPsePortDetectionStatus.4.116 = INTEGER: searching(2) POWER-ETHERNET-MIB::pethPsePortDetectionStatus.5.129 = INTEGER: otherFault(6) POWER-ETHERNET-MIB::pethPsePortDetectionStatus.5.130 = INTEGER: otherFault(6)
But it presents a challenge. I can't just add 'pethPsePortDetectionStatus' to the Network discovery item prototype. And I don't see a way to associate it with an interface. I've looked at preprocessing for a discovery rule, but it won't ever match the SNMPINDEX of the Network interface discovery rule. And with the data I have, the best I could do with a separate discovery rule is translate the '3' part to 'C'. Although I don't know how see the data the discovery rule is using. And I don't think there's any way to lookup the IfDescr in javascript in a preprocessing step.
Right now, I just have a separate Application with these all grouped together with depressing names like "POE Port Status 5.129". That's real helpful in a trigger. At least I know something is wrong.
Anyone have any bright ideas on how to handle this?
- Steve
Comment