HI, HMC is an IBM product which is trying to send check-mk snmp traps. I have loaded the mib file provided by IBM, however I am getting the information in hex.
2020-03-12 02:03:22,565 [15] [cmk.mkeventd.EventServer.snmp] Trap received from 10.62.127.30:54971. Checking for accepta
nce now.
2020-03-12 02:03:22,574 [15] [cmk.mkeventd.EventServer.snmp] Trap accepted from 10.62.127.30 (ContextEngineId “0x80004fb
8056374732d72316177737072622e666e623e2d75a8”, ContextName “”)
2020-03-12 02:03:22,574 [15] [cmk.mkeventd.EventServer.snmp] 1.3.6.1.2.1.1.3.0 = 112318289
2020-03-12 02:03:22,574 [15] [cmk.mkeventd.EventServer.snmp] 1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.2.6.
42.0.1
2020-03-12 02:03:22,574 [15] [cmk.mkeventd.EventServer.snmp] 1.3.6.1.6.3.18.1.3.0 = 10.62.127.30
2020-03-12 02:03:22,574 [15] [cmk.mkeventd.EventServer.snmp] 1.3.6.1.6.3.18.1.4.0 = HMC1
2020-03-12 02:03:22,574 [15] [cmk.mkeventd.EventServer.snmp] 1.3.6.1.6.3.1.1.4.3.0 = 1.3.6.1.4.1.2.6.
42
2020-03-12 02:03:22,574 [15] [cmk.mkeventd.EventServer.snmp] 1.3.6.1.4.1.2.6.42.1.0.4257418604 = 1
2020-03-12 02:03:22,575 [15] [cmk.mkeventd.EventServer.snmp] 1.3.6.1.4.1.2.6.42.1.0.9.1.4257418604 = 1
2020-03-12 02:03:22,575 [15] [cmk.mkeventd.EventServer.snmp] 1.3.6.1.4.1.2.6.42.1.0.9.2.4257418604 = 0x4c6963656e7365
6420696e7465726e616c20636f64652068617320646574656374656420612070726f626c656d2e2020205b50726f626c656d20232038325d00
2020-03-12 02:03:22,575 [15] [cmk.mkeventd.EventServer.snmp] 1.3.6.1.4.1.2.6.42.1.0.9.11.4257418604 = 0
2020-03-12 02:03:22,575 [15] [cmk.mkeventd.EventServer.snmp] 1.3.6.1.4.1.2.6.42.1.0.9.12.4257418604 = 0x30332d31322d32
3032302030323a30303a31343a34323000
2020-03-12 02:03:22,585 [20] [cmk.mkeventd.EventServer] matching groups:
{‘match_groups_message’: ()}
2020-03-12 02:03:22,586 [20] [cmk.mkeventd.EventServer] Rule ‘testEC/test’ hit by message snmptrap/notice - 'SNMPv2-MIB::sysUpTime.0: 112318289, SNMP-COMMUNITY-MIB::snmpTrapAddress.0: 10.62.127.30, SNMP-COMMUNITY-MIB::snmpTrapCommunity.0: HMC1, SNMPv2-MIB::snmpTrapEnterprise.0: IBMhmc::hmc, IBMhmc::cpcObject.4257418604: 1, IBMhmc::cpcMsgType.4257418604: hardware, IBMhmc::cpcMsgText.4257418604: 0x4c6963656e73656420696e7465726e616c20636f64652068617320646574656374656420612070726f626c656d2e2020205b50726f626c656d20232038325d00, IBMhmc::cpcMsgRefresh.4257418604: false, IBMhmc::cpcMsgTimestamp.4257418604: 0x30332d31322d323032302030323a30303a31343a34323000, IBMhmc::cpcMsgImageList.4257418604: 0x524544345a31340a52344346343020524544345a31340a52345359534120524544345a31340a52345359534220524544345a31340a523453595
I had a similar problem in spectrum, so we contacted IBM who found a fault with the classification of an octet string. I still got errors in spectrum after loading the new mib. The Broadcom team could reproduce the problem using the same version as we are using but they upgraded and they could not reproduce the problem and could read the trap message.
Thanks
Vee