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.
This chapter describes the Dying-Gasp feature for the Supported Hardware, which enables the systems to send dying gasp messages through SNMP, syslog, or Ethernet-OAM (Operations Administration and Maintenance) to report the abrupt loss of power to the host platform.
|
|
|
|
---|---|---|---|
Dying Gasp resides on a hardware component on the High-performance WAN Interface Card (HWIC) and supports the Fast Ethernet and Gigabit Ethernet interfaces. The networking devices rely on a temporary back-up power supply on a capacitor, that allows for a graceful shutdown and the generation of the dying-gasp message. This temporary power supply is designed to last from 10 to 20 milliseconds to perform these tasks.
Dying-Gasp packets are created when you configure the host by using the dying-gasp configuration command. The show dying-gasp packets command displays the detailed information about the created packets.
The SNMP server for the SNMP Dying Gasp message is specified through the snmp-server host configuration command. The syslog server sending the syslog Dying Gasp message is specified through the logging host hostname-or-ipaddress transport udp command. The Ethernet-OAM Dying Gasp packets are created for interfaces where Ethernet-OAM is enabled.
Dying Gasp packets can be sent to a maximum number of 5 servers for each notification type.
To enable dying-gasp notification through syslog, SNMP trap, or Ethernet OAM, use the dying-gasp command:
|
|
---|---|
dying-gasp primary { syslog | snmp-trap | ethernet-oam } secondary { syslog | snmp-trap | ethernet-oam } |
The following are descriptions of the show dying-gasp command keywords:
|
|
---|---|
show dying-gasp { status | packets [ snmp-trap | syslog | ethernet-oam ]} |
The following is sample output for the show dying-gasp status command on a CGR 2010:
The following is sample output for the show dying-gasp status command on a CGS 2520:
The following is sample output for the show dying-gasp packets snmp-trap command:
To turn on debugging for dying gasp, issue the debug dying-gasp command:
|
|
---|---|