We've configured snmptt to send traps to Zabbix and that is working successfully.
The issue is that when a varbind on the specific trap changes, a new snmptt/zabbix is not recognizing the change.
The specific trap is cpqHe4FltTolPowerSupplyFailed from Compaq, and it has a varbind entry for varbind 5, cpqHeFltTolPowerSupplyStatus, which is an integer. snmptt/zabix will translate to text correctly (i.e. the instances from the MIB are as follows:
noError(1)
generalFailure(2)
bistFailure(3)
fanFailure(4)
tempFailure(5)
interlockOpen(6)
epromFailed(7)
vrefFailed(8)
dacFailed(9)
ramTestFailed(10)
voltageChannelFailed(11)
orringdiodeFailed(12)
brownOut(13)
giveupOnStartup(14)
nvramInvalid(15)
calibrationTableInvalid(16) )
If I send a trap for, say, 'fanFailure(4),' I get the following in the snmptt.log file correctly:
10:13:08 2016/07/25 cpqHe4FltTolPowerSupplyFailed CRITICAL "Status Events" 10.192.246.26 - Power Supply Failed (6050): The Power Supply is Failed on Chassis 23456, Bay 45678, Status fanFailure, Model model, Serial Num serialnum2, Firmware firmwarerev SparePartNum sparepartnum SystemID systemid
and a trigger is created in Zabbix.
But if I change the varbind to, say, 'generalFailure(2),' it just repeats the same output in the snmptt.log file:
10:13:08 2016/07/25 cpqHe4FltTolPowerSupplyFailed CRITICAL "Status Events" 10.192.246.26 - Power Supply Failed (6050): The Power Supply is Failed on Chassis 23456, Bay 45678, Status fanFailure, Model model, Serial Num serialnum2, Firmware firmwarerev SparePartNum sparepartnum SystemID systemid
and nothing is written to Zabbix.
How do I get it to recognize the new trap (since the varbind data has changed)?
I have SNMP trap fallback set up in Zabbix as well.
Trigger in Zabbix is:
{Template SNMP traps:snmptrap["generalFailure|noError"].str(generalFailure)}=1
The output to the snmptt debug file shows the entry w/ the same varbind as well:
FORMAT line:
Power Supply Failed (6050): The Power Supply is Failed on Chassis 23456, Bay 45678, Status fanFailure, Model model, Serial Num serialnum2, Firmware firmwarerev SparePartNum sparepartnum SystemID systemid
cpqHe4FltTolPowerSupplyFailed CRITICAL "Status Events" 10.192.246.26 - Power Supply Failed (6050): The Power Supply is Failed on Chassis 23456, Bay 45678, Status fanFailure, Model model, Serial Num serialnum2, Firmware
firmwarerev SparePartNum sparepartnum SystemID systemid
I have an /etc/snmp/snmptt.conf.compaq file set up successfully (creates the initial alarm):
EVENT cpqHe4FltTolPowerSupplyFailed .1.3.6.1.4.1.232.0.6050 "Status Events" CRITICAL
FORMAT ZBXTRAP $aA Power Supply Failed (6050): The Power Supply is Failed on Chassis $3, Bay $4, Status $5, # Model $6, Serial Num $7, Firmware $9 SparePartNum $10 SystemID $11
SDESC
The fault tolerant power supply condition has been set
to failed for the specified chassis and bay location.
Variables:
1: sysName
2: cpqHoTrapFlags
3: cpqHeFltTolPowerSupplyChassis
4: cpqHeFltTolPowerSupplyBay
5: cpqHeFltTolPowerSupplyStatus
6: cpqHeFltTolPowerSupplyModel
7: cpqHeFltTolPowerSupplySerialNumber
8: cpqHeFltTolPowerSupplyAutoRev
9: cpqHeFltTolPowerSupplyFirmwareRev
10: cpqHeFltTolPowerSupplySparePartNum
11: cpqSiServerSystemId
EDESC
The issue is that when a varbind on the specific trap changes, a new snmptt/zabbix is not recognizing the change.
The specific trap is cpqHe4FltTolPowerSupplyFailed from Compaq, and it has a varbind entry for varbind 5, cpqHeFltTolPowerSupplyStatus, which is an integer. snmptt/zabix will translate to text correctly (i.e. the instances from the MIB are as follows:
noError(1)
generalFailure(2)
bistFailure(3)
fanFailure(4)
tempFailure(5)
interlockOpen(6)
epromFailed(7)
vrefFailed(8)
dacFailed(9)
ramTestFailed(10)
voltageChannelFailed(11)
orringdiodeFailed(12)
brownOut(13)
giveupOnStartup(14)
nvramInvalid(15)
calibrationTableInvalid(16) )
If I send a trap for, say, 'fanFailure(4),' I get the following in the snmptt.log file correctly:
10:13:08 2016/07/25 cpqHe4FltTolPowerSupplyFailed CRITICAL "Status Events" 10.192.246.26 - Power Supply Failed (6050): The Power Supply is Failed on Chassis 23456, Bay 45678, Status fanFailure, Model model, Serial Num serialnum2, Firmware firmwarerev SparePartNum sparepartnum SystemID systemid
and a trigger is created in Zabbix.
But if I change the varbind to, say, 'generalFailure(2),' it just repeats the same output in the snmptt.log file:
10:13:08 2016/07/25 cpqHe4FltTolPowerSupplyFailed CRITICAL "Status Events" 10.192.246.26 - Power Supply Failed (6050): The Power Supply is Failed on Chassis 23456, Bay 45678, Status fanFailure, Model model, Serial Num serialnum2, Firmware firmwarerev SparePartNum sparepartnum SystemID systemid
and nothing is written to Zabbix.
How do I get it to recognize the new trap (since the varbind data has changed)?
I have SNMP trap fallback set up in Zabbix as well.
Trigger in Zabbix is:
{Template SNMP traps:snmptrap["generalFailure|noError"].str(generalFailure)}=1
The output to the snmptt debug file shows the entry w/ the same varbind as well:
FORMAT line:
Power Supply Failed (6050): The Power Supply is Failed on Chassis 23456, Bay 45678, Status fanFailure, Model model, Serial Num serialnum2, Firmware firmwarerev SparePartNum sparepartnum SystemID systemid
cpqHe4FltTolPowerSupplyFailed CRITICAL "Status Events" 10.192.246.26 - Power Supply Failed (6050): The Power Supply is Failed on Chassis 23456, Bay 45678, Status fanFailure, Model model, Serial Num serialnum2, Firmware
firmwarerev SparePartNum sparepartnum SystemID systemid
I have an /etc/snmp/snmptt.conf.compaq file set up successfully (creates the initial alarm):
EVENT cpqHe4FltTolPowerSupplyFailed .1.3.6.1.4.1.232.0.6050 "Status Events" CRITICAL
FORMAT ZBXTRAP $aA Power Supply Failed (6050): The Power Supply is Failed on Chassis $3, Bay $4, Status $5, # Model $6, Serial Num $7, Firmware $9 SparePartNum $10 SystemID $11
SDESC
The fault tolerant power supply condition has been set
to failed for the specified chassis and bay location.
Variables:
1: sysName
2: cpqHoTrapFlags
3: cpqHeFltTolPowerSupplyChassis
4: cpqHeFltTolPowerSupplyBay
5: cpqHeFltTolPowerSupplyStatus
6: cpqHeFltTolPowerSupplyModel
7: cpqHeFltTolPowerSupplySerialNumber
8: cpqHeFltTolPowerSupplyAutoRev
9: cpqHeFltTolPowerSupplyFirmwareRev
10: cpqHeFltTolPowerSupplySparePartNum
11: cpqSiServerSystemId
EDESC