Why does a module fail for a Cisco device in Chassis Manager but I do not receive an alarm?

book

Article ID: 131684

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction



Why does Spectrum not alarm when a module fails in Chassis Manager for a Cisco device?

Environment

Spectrum 10.2.x
Spectrum 10.3.x

 

Resolution

Spectrum gets the status from the module by reading the attribute InternalModuleStatus (0x12e66) from the module itself that is located inside Chassis Manager.  If the status is offline or down, then Spectrum should alarm, however if the status is unknown, then Spectrum will not create an alarm.
The attribute InternalModuleStatus (0x12e66) is calculated by the following two requirements:

1. The device CATStackApp model which is an application model that is created when the device is discovered must have the attribute sysEnableModuleTraps (0x11c0109) enabled

2. These two Cisco traps are responsible for the current status of InternalModuleStatus (0x12e66).  Please make sure that the device is sending these traps to Spectrum.

moduleUp NOTIFICATION-TYPE
OBJECTS { moduleIndex, moduleType }
STATUS current
DESCRIPTION "A moduleUp trap signifies that the agent entity
has detected that the moduleStatus object in this
MIB has transitioned to the ok(2) state for one of
its modules.
The generation of this trap can be controlled by
the sysEnableModuleTraps object in this MIB."
::= { ciscoStackNotificationsPrefix 3}

moduleDown NOTIFICATION-TYPE
OBJECTS { moduleIndex, moduleType }
STATUS current
DESCRIPTION "A moduleDown trap signifies that the agent entity
has detected that the moduleStatus object in this
MIB has transitioned out of the ok(2) state for
one of its modules.
The generation of this trap can be controlled by
the sysEnableModuleTraps object in this MIB."
::= { ciscoStackNotificationsPrefix 4}