7 Replies Latest reply on Oct 10, 2017 8:43 AM by Cassie Derrick

    SNMP Trap OIDST contains slots not found in MIB file.

    Tammy Ryan
      Share This:

      Our BPPM 9.6 has been successfully receiving SNMP Traps from Andover Controller for years.  Now all of a sudden they aren't mapping correctly due to extra values appearing in the OIDST and SNMP_Vals that weren't there previously.  The vendor says nothing has changed on the Andover side.  And unfortunately, it was discovered after we upgraded BPPM to SP2 and we have no events prior to the upgrade to confirm that is when it changed.

       

      NEW:

      snmp_oidst=['sysUpTime','snmpTrapOID','alarmControllerName','alarmInfinetControllerName','alarmPointName','alarmPointDescription','alarmAlarmName','alarmState','alarmAlmTime','alarmAlmValue','alarmRtnTime','alarmRtnValue'];

      snmp_vals=['411545290','1.3.6.1.4.1.10829.5.2.1.3','DataCenter','CracUnit_1','HO_CRAC1.H2OUF','Water under floor-CRAC1','W10MZ02','rtn','à-!','Off','à.','On'];

      snmp_version=1;

       

      PREVIOUS:

      snmp_oidst=['alarmControllerName','alarmInfinetControllerName','alarmPointName','alarmPointDescription','alarmAlarmName','alarmState','alarmAlmTime','alarmAlmValue','alarmRtnTime','alarmRtnValue'];

      snmp_vals=['DataCenter','CracUnit_1','HO_CRAC1.H2OUF','Water under floor-CRAC1','W10MZ02','rtn','à-!','Off','à.','On'];

      snmp_version=1;


      The MIB file is expecting alarmControllerName to be the first value so in the new events, alarmControllerName is "411545290" when it should be "DataCenter" and so on.

       

      I have SNMP Traps from other vendors that aren't having this problem so I'm not ready to say that BPPM SP2 has caused this.

       

      I've never attempted to re-code a MIB file but could write a rule to parse the slots from the new location if I have to.  Has anyone else experienced this behavior?