Not receiving module removal alarms in Spectrum for Ca29xxStack devices
Article ID: 205707
Updated On:
Products
Issue/Introduction
After modeling a Cat29xxStack device in Spectrum, when a module is removed from the stack, Spectrum is not asserting a module removed alarm on the model as expected.
If the model is reconfigured, Spectrum then asserts the module removed alarm.
Cause
Possible root cause is the device is not updating the ifStackStackLastChange and ifTableLastChange attributes on the device when the module is removed.
ifStackLastChange OBJECT-TYPE
SYNTAX TimeTicks (0 .. 4294967295)
ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the last change of
the (whole) interface stack. A change of the interface
stack is defined to be any creation, deletion, or change in
value of any instance of ifStackStatus. If the interface
stack has been unchanged since the last re-initialization of
the local network management subsystem, then this object
contains a zero value."
::= { ifMIBObjects 6 }
-- 1.3.6.1.2.1.31.1.6
ifTableLastChange OBJECT-TYPE
SYNTAX TimeTicks (0 .. 4294967295)
ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the last creation or
deletion of an entry in the ifTable. If the number of
entries has been unchanged since the last re-initialization
of the local network management subsystem, then this object
contains a zero value."
::= { ifMIBObjects 5 }
-- 1.3.6.1.2.1.31.1.5
Environment
Release : Any
Component : Spectrum Chassis Manager
Resolution
Spectrum monitors the ifStackStackLastChange and ifTableLastChange attributes on the device to determine of a module has been pulled.
Verify if the ifStackStackLastChange and ifTableLastChange attributes on the device change after pulling the module. If not, please contact the vendor to determine why these attribute values are not changed when a module has been pulled.
Feedback
