One day I needed to research SNMP OID and write a Zabbix template for ETP4860-B1A2 (SMU11B).
Пример проверки SNMP OID:
snmpwalk -v2c -c public ixnfo.com OID
In the device settings, you can download the Mib File, to do this, open System Settings – SNMP, Mib File – Export.
After that, an archive with two files HUAWEI-MIB.mib and emap_snmp.mib will be downloaded, which I put on the server with Zabbix in the directory /usr/share/snmp/mibs/
Now I will describe several OIDs that I translated from the MIB and that I needed for monitoring.
Some OIDs require specifying the rectifier index (the ETP4860 device has two slots for rectifiers), the rectifier indices are different for each device, so in the Zabbix template I added the macro {$ETP4860_INDEX_ixnfo.com} to the OID and specified it in each network node so that the template would be the same for everyone, and the macro could be changed.
When translating MIB to OID, there were errors in the MIB file that I had to fix and OIDs started translating successfully.
I will give an example of the OID of a rectifier with index (28677), the result is multiplied by 0.1:
snmptranslate -IR -On EMAP-MIB::hwRectOutputVoltage
.1.3.6.1.4.1.2011.6.164.1.3.2.2.1.3
snmpwalk -v2c -c public 10.10.10.5 .1.3.6.1.4.1.2011.6.164.1.3.2.2.1.3
SNMPv2-SMI::enterprises.2011.6.164.1.3.2.2.1.3.28677 = Gauge32: 550
snmptranslate -IR -On EMAP-MIB::hwRectACVoltage
.1.3.6.1.4.1.2011.6.164.1.3.2.2.1.6
snmpwalk -v2c -c public 10.10.10.5 .1.3.6.1.4.1.2011.6.164.1.3.2.2.1.6
SNMPv2-SMI::enterprises.2011.6.164.1.3.2.2.1.6.28677 = Gauge32: 2313
snmptranslate -IR -On EMAP-MIB::hwRectifierTemperature
.1.3.6.1.4.1.2011.6.164.1.3.2.2.1.8
snmpwalk -v2c -c public 10.10.10.5 .1.3.6.1.4.1.2011.6.164.1.3.2.2.1.8
SNMPv2-SMI::enterprises.2011.6.164.1.3.2.2.1.8.28677 = INTEGER: 230
.1.3.6.1.4.1.2011.6.164.1.3.2.2.1.99.X (hwRectOperStatus, normal(1),fault(2),protect(3),commFail(4),switchOff(5),invalid(6),noConfig(7),alarmResume(254),other(255))
I will describe the following OIDs, they are already without the device index.
What values are specified for floating and fast charging:
Какие значения указаны для плавающей и быстрой зарядки:
.1.3.6.1.4.1.2011.6.164.1.4.1.8 (hwSetBattsFloatVoltage *0.1)
.1.3.6.1.4.1.2011.6.164.1.4.1.9 (hwSetBattsBoostVoltage *0.1)
Charge status, the value is usually 1 float or 2 boost, 3 discharge – not all firmware displays:
Статус заряда, значение обычно 1 float или 2 boost, 3 discharge – не на всех прошивках отображается:
.1.3.6.1.4.1.2011.6.164.1.4.2.3 hwBattsChargeStatus –
floatCharge(1),boostCharge(2),disCharge(3),hibernating(4),offline(7),unknown(255)
When there is no communication with the battery, it allows you to track when fast charging is turned on in order to accurately adjust the correct voltage for the Lifepo4 battery, because if fast charging with increased voltage is turned on when the battery is fully charged, there will be an imbalance in voltage across the battery cells and the BMS may turn off.
Current charging/discharging current of the battery:
.1.3.6.1.4.1.2011.6.164.1.4.2.1 (hwBattsTotalCurrent)
You can make a Zabbix trigger, for example, when it works on battery > 12 hours (usually OLT consumes about 0.5-1.5A, the value will be negative when discharged):
max(/templateIXNFO.COM/hwBattsTotalCurrent,12h)<0
How much battery capacity in % and hours is left and what capacity (A) is indicated in the settings:
.1.3.6.1.4.1.2011.6.164.1.4.2.10 hwTotalRemainingCapacityPercent
.1.3.6.1.4.1.2011.6.164.1.4.2.2 (hwBattsPreDischargeTime, Backup Time in hours)
.1.3.6.1.4.1.2011.6.164.1.4.2.8 (hwBattsRatedCapacity)
.1.3.6.1.4.1.2011.6.164.1.4.1.13 (hwSetBattsRatedCapacity)
.1.3.6.1.4.1.2011.6.164.1.4.4.2.1.2.5 (hwBattStringCurrent)
.1.3.6.1.4.1.2011.6.164.1.4.2.9 (hwBattsRemainCapacity, A)
Current AC/DC Power in Watts:
.1.3.6.1.4.1.2011.6.164.1.3.1.11 (hwRectsTotalACInputPower, in Watt)
.1.3.6.1.4.1.2011.6.164.1.3.1.9 (hwRectsTotalDCPower, in Watt)
.1.3.6.1.4.1.2011.6.164.1.6.1.5.0 (hwDcsTotalPower, in Watt)
What is the default voltage for the rectifier:
.1.3.6.1.4.1.2011.6.164.1.3.1.5 (hwRectsRatedVoltage) 53.5
What voltage is supplied to the battery (the voltage will rise as the battery charges to the value specified in hwRectOutputVoltage):
.1.3.6.1.4.1.2011.6.164.1.3.1.6 (hwModifyRectsOutputVoltage)
Some more OIDs:
1.3.6.1.4.1.2011.6.164.1.4.2.4 (hwBattsCurrLimitStatus, 1-not limited, 2-limited or unknown)
1.3.6.1.4.1.2011.6.164.1.6.2.1.1.99 (hwDcOutputOperStatus, normal(1), voltHigh(2), voltLow(3), alarmResume(254), other(255))
1.3.6.1.4.1.2011.6.164.1.3.1.3.0 (hwRectsTotalCurrent)
1.3.6.1.4.1.2011.6.164.1.5.1.3.0 (hwAcsTotalCurrent)
1.3.6.1.4.1.2011.6.164.1.5.2.1.1.99.1 (hwAcInputOperStatus, normal(1), acOff(2), acAbsent(3), voltHigh(4), voltLow(5), alarmResume(254), other(255))
.1.3.6.1.4.1.2011.6.164.1.3.1.10 (hwRectsLoadUsage)
.1.3.6.1.4.1.2011.6.164.1.1.2.99.1.2 (hwActiveAlarmText)
.1.3.6.1.4.1.2011.6.164.1.4.1.12 (hwCtrlBattsBoostFloat) floatCharge(1),boostCharge(2)
.1.3.6.1.4.1.2011.6.164.1.4.1.10 (hwSetBattsCurrLimitCoefficient, *0.01)
For hwAcInputOperStatus, you can make a trigger when it is not equal to 1, reporting that there is no light.
hwRectOperStatus is usually equal to 5 when there is no light or the rectifiers are broken, you can also make a trigger notifying about the breakdown, connected to hwAcInputOperStatus to take into account that there is electricity.
last(/ixnfo.com/hwRectOperStatus)<>1
and
last(/ixnfo.com/hwAcInputOperStatus)=1
Load Current (where the second to last digit 2 is the emu number, the result is multiplied by 0.001):
1.3.6.1.4.1.2011.6.2.1.3.1.10
1.3.6.1.4.1.2011.6.2.1.3.1.10.2.0
Module 0 and Module 1 current (using the example of emu id 1, multiply the result by 0.001):
1.3.6.1.4.1.2011.6.2.1.5.1.5
1.3.6.1.4.1.2011.6.2.1.5.1.5.1.0.0
1.3.6.1.4.1.2011.6.2.1.5.1.5.1.0.1
For Huawei ESM-48100B1:
SOC % (*0.1)
.1.3.6.1.4.1.2011.6.164.1.17.1.1.8.96 = Gauge32: 990
Battery Voltage V (*0.1)
.1.3.6.1.4.1.2011.6.164.1.17.1.1.5.96 = Gauge32: 488
Backup Time h (*0.1)
.1.3.6.1.4.1.2011.6.164.1.17.1.1.11.96 = Gauge32: 391
Battery Current A (*0.1)
.1.3.6.1.4.1.2011.6.164.1.17.1.1.6.96
Equalized Charge Voltage (*0.1)
.1.3.6.1.4.1.2011.6.164.1.17.2.1.11.96 = Gauge32: 564
Float Charge Voltage (*0.1)
.1.3.6.1.4.1.2011.6.164.1.17.2.1.12.96 = Gauge32: 545
Charge Current Limit Coefficient (*0.1)
.1.3.6.1.4.1.2011.6.164.1.17.2.1.13.96 = Gauge32: 22
High Temperature Alarm Threshold
.1.3.6.1.4.1.2011.6.164.1.17.2.1.21.96 = Gauge32: 58
Low Temperature Alarm Threshold
.1.3.6.1.4.1.2011.6.164.1.17.2.1.22.96 = INTEGER: 5
TEMPERATURE (*0.1)
.1.3.6.1.4.1.2011.6.164.1.17.1.1.9.96 = INTEGER: 107
CELLS TEMPERATURE (*0.1):
.1.3.6.1.4.1.2011.6.164.1.18.2.1.22.3668 = INTEGER: 110
.1.3.6.1.4.1.2011.6.164.1.18.2.1.23.3668 = INTEGER: 110
.1.3.6.1.4.1.2011.6.164.1.18.2.1.24.3668 = INTEGER: 110
.1.3.6.1.4.1.2011.6.164.1.18.2.1.25.3668 = INTEGER: 100
.1.3.6.1.4.1.2011.6.164.1.18.2.1.26.3668 = INTEGER: 100
.1.3.6.1.4.1.2011.6.164.1.18.2.1.27.3668 = INTEGER: 100
.1.3.6.1.4.1.2011.6.164.1.18.2.1.28.3668 = INTEGER: 100
.1.3.6.1.4.1.2011.6.164.1.18.2.1.29.3668 = INTEGER: 110
.1.3.6.1.4.1.2011.6.164.1.18.2.1.30.3668 = INTEGER: 110
.1.3.6.1.4.1.2011.6.164.1.18.2.1.31.3668 = INTEGER: 110
.1.3.6.1.4.1.2011.6.164.1.18.2.1.32.3668 = INTEGER: 110
.1.3.6.1.4.1.2011.6.164.1.18.2.1.33.3668 = INTEGER: 120
.1.3.6.1.4.1.2011.6.164.1.18.2.1.34.3668 = INTEGER: 120
.1.3.6.1.4.1.2011.6.164.1.18.2.1.35.3668 = INTEGER: 120
.1.3.6.1.4.1.2011.6.164.1.18.2.1.36.3668 = INTEGER: 120
See also my articles:
How to translate SNMP MIB to OID