Appendix: Supported alarms
Equipment alarms
| Alarm ID: | 1001 |
| Alarm name: | Fan Tray Fault |
| Description: | This alarm is raised when the associated fan-tray is in down/empty/failed/degraded/low-power operational state. The system may have cooling issues. |
| Severity: | Major |
| Probable cause: | Equipment malfunction |
| Remedial action: | The failed fan unit should be replaced. |
| Alarm ID: | 1003 |
| Alarm name: | Power Supply Fault |
| Description: | The alarm is raised when the associated power supply is not operationally Up. The specified power supply can no longer supply power to the system. |
| Severity: | Critical |
| Probable cause: | Power problem |
| Remedial action: | Check the status of the power supply. |
| Alarm ID: | 1004 |
| Alarm name: | Chassis Fault |
| Description: | The alarm is raised when chassis is operationally down. |
| Severity: | Critical |
| Probable cause: | Equipment malfunction |
| Remedial action: | Chassis Down |
| Alarm ID: | 1005 |
| Alarm name: | CPM Fault |
| Description: | This alarm is generated when the control module is in an operationally down/empty/failed/degraded/low-power state. |
| Severity: | Critical |
| Probable cause: | Equipment malfunction |
| Remedial action: | Remove the card and reset it. If this does not clear the alarm then please contact your Nokia support representative for assistance. |
| Alarm ID: | 1006 |
| Alarm name: | SFM Fault |
| Description: | The alarm is raised when the associated SFM module is in operationally down/empty/failed/degraded/low-power state. Traffic could be impacted. |
| Severity: | Critical |
| Probable cause: | Equipment malfunction |
| Remedial action: | The active CPM is at risk of failing to initialize after node reboot because it cannot access the SFM. Contact Nokia customer support. |
| Alarm ID: | 1007 |
| Alarm name: | Line Card Fault |
| Description: | The alarm is raised when the specified line card is operationally down/empty/failed/degraded/low-power state. Traffic is no longer being transmitted from this line card. |
| Severity: | Major |
| Probable cause: | Equipment malfunction |
| Remedial action: | Ensure line card is operationally up. Linecard may need to be replaced. |
Communication alarms
| Alarm ID: | 4001 |
| Alarm name: | LLDP Adjacency Down |
| Description: | The alarm is raised when the Operational State of an LLDP adjacency is down. This is because the operational state of local interface is in a down state. |
| Severity: | Major |
| Probable cause: | DTE DCE Interface Error |
| Remedial action: | The operational state of the interface must be up in order for the selected adjacency to be up. |
| Alarm ID: | 4002 |
| Alarm name: | Interface Down |
| Description: | The alarm is raised when the operational state of interface is down. |
| Severity: | Critical |
| Probable cause: | DTE DCE Interface Error |
| Remedial action: | The condition exists because the physical interface is down
either because it is administratively disabled, faulty or a cabling
fault has occurred. Ensure that the interface is administratively
up. Check for a poor cable connection to the port or for a faulty cable/fiber. If neither appears to be the problem run diagnostics on the port to determine if it is faulty. |
| Alarm ID: | 4003 |
| Alarm name: | Subinterface Down |
| Description: | The alarm is raised when the operational state of subinterface is down. |
| Severity: | Critical |
| Probable cause: | DTE DCE Interface Error |
| Remedial action: | The condition exists because the subinterface is down
either because it is administratively disabled, faulty or a cabling
fault has occurred. Ensure that the subinterface is administratively
up. Check for a poor cable connection to the port or for a faulty cable/fiber. If neither appears to be the problem run diagnostics on the port to determine if it is faulty. |
| Alarm ID: | 4004 |
| Alarm name: | BGP Adjacency Down |
| Description: | The alarm is raised when the BGP neighbor state transitions out of the Established state. |
| Severity: | Critical |
| Probable cause: | DTE DCE BGP Error |
| Remedial action: | Verify reachability and BGP parameters match between BGP neighbors. |
| Alarm ID: | 4005 |
| Alarm name: | BFD Session Down |
| Description: | The alarm is raised when the BFD session is operationally down. |
| Severity: | Critical |
| Probable cause: | DTE DCE BFD Error |
| Remedial action: | Verify reachability between BFD neighbors. |
| Alarm ID: | 4006 |
| Alarm name: | Network Instance Down |
| Description: | The alarm is raised when a network-instance is down. |
| Severity: | Critical |
| Probable cause: | DTE DCE NET INST DOWN |
| Remedial action: | Verify the configuration of the network-instance. |
| Alarm ID: | 4007 |
| Alarm name: | Interface LAG Member Down |
| Description: | The alarm is raised when the member of a LAG goes into the operational down state. |
| Severity: | Warning |
| Probable cause: | DTE DCE INT LAG DOWN |
| Remedial action: | The condition exists because the physical interface
belonging to a LAG is down. The interface could be down because it is
administratively disabled, faulty or a cabling fault has occurred. Do the following:
|
Operational alarms
| Alarm ID: | 5001 |
| Alarm name: | GNMI Connection Fault |
| Description: | GNMI connection to the network element has been lost. |
| Severity: | Major |
| Probable cause: | DTE DCE Interface Error |
| Remedial action: | Check network connectivity to restore GNMI connection. |
Fabric Services System alarms
| Alarm ID: | 6001 |
| Alarm name: | Connect FSS Configuration Failed |
| Description: | The alarm is raised when changes on Plugin API cannot be configured on the Fabric Services System. |
| Severity: | Critical |
| Probable cause: | Configuration or customization error |
| Remedial action: | The condition exists because Connect cannot provision the Fabric Services System with the intended configuration on its Plugin API. Sanitize the Fabric Services System to resolve this error and perform audit on Connect. |
| Alarm ID: | 6002 |
| Alarm name: | Connect FSS Workload Intent Deploy Failed |
| Description: | The alarm is raised when generating configurations and deploying a workload intent is not possible. |
| Severity: | Critical |
| Probable cause: | Configuration or customization error |
| Remedial action: | The condition exists because Connect cannot deploy the workload intent on the Fabric Services System. Please make sure the workload intent is in a deployable state and perform an audit on Connect. |
| Alarm ID: | 6003 |
| Alarm name: | Connect Fabric Services System Authentication Failed |
| Description: | The alarm is raised when Connect cannot authenticate with the Fabric Services System. |
| Severity: | Critical |
| Probable cause: | Authentication failure |
| Remedial action: | The condition exists because Connect cannot authenticate with the Fabric Services System. Make sure the Connect configuration is correct and perform an audit on Connect. |
| Alarm ID: | 6005 |
| Alarm name: | Connect Plugin Heartbeat Lost |
| Description: | The alarm is raised when Connect no longer detects heartbeat messages from one of its plugins. |
| Severity: | Critical |
| Probable cause: | CONNECT PLUGIN HEARTBEAT LOST |
| Remedial action: | The condition exists because Connect cannot detect the presence of one of its plugins. Make sure the plugin is running and actively issuing heartbeat messages. |