Alerts and Queryables for Module Status

Alerts and Queryable for Module Status

This use case establishes monitoring and alerting capabilities for Administrative state of Field Replaceable Units (FRUs)—things like line cards, supervisor engines, or power supplies—within modular chassis devices deployed in various physical environments such as data centers or headquarters.

Scale of this example: 297 devices, 4 vendors( Cisco, Arista, Palo Alto and HP), with many different models.

Dashboard for the Example

Alerts, including alarm codes, are configured and BigPanda is successfully receiving all configured alerts.

Module Status Dashboard

The following table shows the administrative state of Field Replaceable Units (FRUs)—things like line cards, supervisor engines, or power supplies—within a modular chassis.

Alert Name	Priority	Queryable	Notes
ModuleStatusDown	P3	module_admin_oper_status as honeycomb where module_admin_oper_status_violation>0 group-by device, entity_model_name	An alert is generated when the state of any FRU module is violating the condition of Status UP.

For Cisco Switches

An Alert is triggered if ModuleAdminStatus is not equal to enabled (1) or if ModuleOperStatus is not equal to OK (2).

Module Status for Cisco

When the Cisco MIB OID ModuleAdminStatus- 1.3.6.1.4.1.9.9.117.1.2.1.1.1 and ModuleOperStatus - 1.3.6.1.4.1.9.9.117.1.2.1.1.2 is polled with SNMP, an integer is returned. Each integer corresponds to a specific state, as shown in the following tables.

ModuleAdminStatus

Value	State	Description	Alert
1	enabled	The module is powered on and allowed to initialize.	No
2	disabled	The module is administratively shut down/powered off.	Yes
3	reset	Setting this value triggers a hardware reset (reboot) of the module.	Yes
4	outOfServiceAdmin	The module is taken out of service for administrative reasons (maintenance).	Yes

ModuleOperStatus

Value	State	Description	Alert
1	unknown	The status cannot be determined (often seen during a quick transition).	Yes
2	ok	Normal Operation. The module is powered on and functioning correctly.	No
3	disabled	The module is powered off (usually via ModuleAdminStatus).	Yes
4	okButMsiamMismatch	Operational, but there is a backplane/interface mismatch.	Yes
5	outOfService	The module is powered on but not providing service (manual override).	Yes
6	standby	The module is in hot-standby mode (common for redundant supervisors).	Yes
7	powerUp	The module is currently receiving power and beginning to boot.	Yes
8	identify	The module is being identified by the supervisor software.	Yes
9	boot	The module is currently loading its operating software.	Yes
10	mismatchConfig	The physical module does not match the provisioned configuration.	Yes
11	diagFailed	Hardware Failure. The module failed its Power-On Self-Test (POST).	Yes
12	dormant	The module is waiting for an internal/external event to go active.	Yes
13	outOfServiceAdmin	Put into a low-power maintenance mode by an administrator.	Yes

For Palo Alto

An Alert is triggered if StateAdmin is not equal to unlocked (4) or if StateOper is not equal to enabled (3)

Module Status for Palo Alto

For Arista

An Alert is triggered if StateAdmin is not equal to unlocked (4) or if StateOper is not equal to enabled (3)

Module Status for Arista

For HP

An Alert is triggered if StateAdmin is not equal to unlocked (4) or if StateOper is not equal to enabled (3).

Module Status for HP

Queryable

module_admin_oper_status as honeycomb where module_admin_oper_status_violation>0 group-by device, entity_model_name

When the OID entStateAdmin- 1.3.6.1.2.1.131.1.1.1.2 and entStateOper - 1.3.6.1.2.1.131.1.1.1.2 is polled with a SNMP, an integer Is returned. Each integer corresponds to a specific state, as shown in the following tables.

entStateAdmin

Value	State	Description	Alert
1	unknown	The administrative state is unknown or cannot be determined.	Yes
2	locked	The entity is administratively prohibited from providing service (similar to a “shutdown” command).	Yes
3	shuttingDown	The entity is in the process of shutting down and will soon transition to the locked state.	Yes
4	unlocked	Normal Operation. The entity is administratively permitted to provide service.	No

entStateOper

Value	State	Description	Alert
1	unknown	Status cannot be determined (e.g., during a system initialization).	Yes
2	disabled	The entity is non-functional, usually because the Admin state is locked.	Yes
3	enabled	Normal Operation. The entity is fully functional and providing service.	No
4	testing	The entity is currently undergoing internal diagnostics or loopback tests.	Yes