The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Once hardware is installed and operational, use alarms to monitor hardware status on a daily basis.
The Cisco ASR 1000 Series Aggregation Services Routers are designed to send alarm notifications when problems are detected. Network administrators do not need to use show commands to poll devices on a routine basis and can monitor the network remotely. However, network administrators can perform onsite monitoring if they so choose.
The following sections discuss ways in which you can monitor hardware using alarms:
An external element can be connected to a power supply using the DB-25 alarm connector on the power supply. The external element is a DC lightbulb for a visual alarm and a bell for an audible alarm.
If an alarm illuminates the CRIT, MIN, or MAJ LED on the Cisco ASR 1000 Series Route Processor (RP) faceplate, and a visual or audible alarm is wired, the alarm also activates an alarm relay in the power supply DB-25 connector (on the Cisco ASR 1006 Router and Cisco ASR 1004 Router). The bell rings or the lightbulb flashes.
To clear an audible alarm, do one of the following:
To clear a visual alarm, you must resolve the alarm condition. The clear facility-alarm command does not clear an alarm LED on the RP faceplate or turn off the DC lightbulb. For example, if a critical alarm LED is illuminated because an active SPA was removed without a graceful deactivation of the SPA, the only way to resolve that alarm is to replace the SPA.
The network administrator can monitor alarm messages by reviewing alarm messages sent to the system console or to a syslog. This section discusses the following topics:
The logging alarm command must be enabled for the system to send alarm messages to a logging device, such as the console or a syslog. This command is not enabled by default.
You can specify the severity level of alarm to log. All alarms at and above the specified threshold generate alarm messages. For example, the following command sends only critical alarm messages to logging devices:
If alarm severity is not specified, alarm messages for all severity levels are sent to logging devices.
The following alarm messages are examples of alarm messages that are sent to the console when a SPA is removed without first doing a graceful deactivation of the SPA. The alarm is cleared when the SPA is re-inserted.
*Aug 22 13:27:33.774: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/1, interfaces disabled
*Aug 22 13:27:33.775: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XT-SERIAL) offline in subslot 1/1
*Aug 22 13:32:29.447: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/1
*Aug 22 13:32:34.916: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XT-SERIAL) online in subslot 1/1
*Aug 22 13:32:35.523: %LINK-3-UPDOWN: SIP1/1: Interface EOBC1/1, changed state to up
ALARMS For Cisco ASR 1001 Router
To view the alarms on Cisco ASR 1001 router, use the show facility-alarm status command. The example shows a critical alarm for Power supply along with the description:
To view critical alarms specifically, use the show facility-alarm status critical command:
To view the operational state of the major hardware components on Cisco ASR 1001 Router, use the show platform diag command. This example shows the Power supply P0 has failed:
To view the operational state of the major hardware components on Cisco ASR 1013 Router, use the show platform diag command. This example shows the Power supply P0 has failed:
To facilitate the review of alarm messages, you can write scripts to analyze alarm messages sent to the console or syslog. Scripts can provide reports on events such as alarms, security alerts, and interface status.
Syslog messages can also be accessed through Simple Network Management Protocol (SNMP) using the history table defined in the CISCO-SYSLOG-MIB.
The Simple Network Management Protocol (SNMP) is an application-layer protocol that provides a standardized framework and a common language used for monitoring and managing devices in a network. Of all the approaches to monitor alarms, SNMP is the best approach for enterprise and service provider customers that have many routers to monitor.
SNMP provides notification of faults, alarms, and conditions that might affect services. SNMP allows a network administrator to access router information through a network management system (NMS) instead of by polling devices, reviewing logs, or reviewing log reports.
Note “Transceiver Missing - Link Down” alarm will be reported with a severity of “CRITICAL” in the output of show facility-alarm status command.
To use SNMP to get alarm notification, you must use the following MIBs:
For more information about the topics discussed in this chapter, see the following documents:
|
|
---|---|
Cisco IOS Master Command List, All Releases Command Lookup Tool (Requires Cisco.com user ID and password) |
|
Cisco ASR 1000 Series Aggregation Services Routers MIB Specifications Guide |
|
“SNMP Support” chapter in the Cisco IOS XE Network Management Configuration Guide, Release 2 |
|
Graceful Deactivation of a SIP or SPA: Online insertion and removal (OIR) |
“Installing and Removing a SIP” chapter in the |
MIBs supported on the Cisco ASR 1000 Series Aggregation Services Routers |
Cisco ASR 1000 Series Aggregation Services Routers MIB Specifications Guide |
“Cisco ASR 1000 Series Routers Components Overview” chapter in the Cisco ASR 1000 Series Aggregations Services Routers Hardware Installation Guide |