For OldCiscoChassis:-
In general it is the line Card-Fault= OldCiscoChassis which will need to be added to the certification.
# Cisco XXXX
.1.3.6.1.4.1.9.1.XXX {
TYPE = Router
VENDOR = Cisco
MODEL = XXXX
CERTIFICATION = CERTIFIED
CONT = Cisco-Router
NEIGHBOR = Cisco-Cdp
HEALTH = Cisco-Router
INSTRUMENTATION:
Environment = CiscoEnvMon:DeviceID
CPU/Memory = CiscoRouter:DeviceID
Card-Fault = OldCiscoChassis
Interface-Fault = MIB2
Interface-Performance = CiscoRouter
Interface-Ethernet-Performance = CiscoRouter_Ethernet
}
For Cisco-EntityFRU:-
In general it is the line Card-Fault = CiscoEntityFRU which will need to be added to the certification.
# Cisco XXXX
.1.3.6.1.4.1.9.1.XXX {
TYPE = Router
VENDOR = Cisco
MODEL = XXXX
CERTIFICATION = CERTIFIED
CONT = Cisco-Entity
NEIGHBOR = Cisco-Cdp
HEALTH = Cisco-Router
INSTRUMENTATION:
Card-Fault = CiscoEntityFRU
Environment = CiscoEnvMon:DeviceID
CPU/Memory = CiscoRouter:DeviceID
Interface-Fault = MIB2
Interface-Performance = CiscoRouter
Interface-Ethernet-Performance = CiscoRouter_Ethernet
}
After the relevant change has been made, the certifications can be reloaded without restarting the IP domain using the following command :-
sm_tpmgr -s <AM_Domain> --reloadoid
Check the server log file for any errors. Then delete and rediscover the affected device.
The Cisco-EntityFRU MIB should replace the OldCiscoChasis MIB however it is apparent from many of the Cisco devices running on IOS versions after 12.1 that the Cisco-EntityFRU MIB is not available and the OldCiscoChassis MIB is still being utilized. The MIB being utilized for a particular device can be verified by greping for the following OID's in .SNAP file of the device in question:-
OldCiscoChassis cardOperStatus 1.3.6.1.4.1.9.3.6.11.1.9
CiscoEntityFRUControl cefcModuleOperStatus 1.3.6.1.4.1.9.9.117.1.2.1.1.2