Why does Spectrum not alarm on StackPort modules when one goes down?

Document ID : KB000012971
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

When a Cisco StackPort module goes down, an alarm is not raised on the corresponding Cisco StackPort model in Spectrum but instead can be configured to be raised on the StackSub parent interface model (by enabling attribute PollPortStatus on the StackSub model).

Question:

Why can we not configure Spectrum to raise an alarm on the StackPort model instead of on the parent StackSub?

Environment:
Spectrum 10.xSpectrum 9.4.x
Answer:

The reason is in the way Cisco reports the Stackport status. The ifTable in the MIB data of the Cisco devices shows that the StackPort interfaces are stacked underneath the StackSub interfaces. 

However, when the device is down the StackPort interface is removed from this table. This causes the stack port interface models to go with a status of unknown/not present depending on if a reconfiguration has occurred. But in either state, the PortStack interface model is grey. 

But the StackSub Interface model does go operationally down (red). For this to change, Cisco would have to change the way it reports the StackPort status in the MIB data. 

This is why we advise to turn on PollPortStatus to true for the StackSub models so that the alarm is at least raised on the Stacksub.