Monitoring High Availability
This section shows how to use the show commands to view your high availability configuration and how to clear the high availability switchover history for the router.
High Availability show Commands
You can monitor various aspects of high availability using show commands. These aspects include redundancy modes and status, redundancy clients, historical information about redundancy on the router, and specific redundancy information for line modules and SRPs.
show redundancy
- Use to display the supported redundancy modes and other status relating to high availability. In particular, the output indicates any conditions that are preventing high availability from operating.
- Field descriptions
- high-availability state—State of the high availability mode (disabled, active, or pending)
- current redundancy mode—Redundancy mode currently being used by this router (high-availability or file-system-synchronization)
- last activation type—Last type of activation that occurred on this router (that is, the method by which the SRP las booted [cold-start or warm-start])
- Criteria Required for High Availability to be Active—criteria required for HA to be active.
NOTE: All criteria must be "yes" for High Availability to be active.
- Line Card
- automatic reverting—State of automatic reverting (on or off)
- slot(s)—Slots in which the line modules reside
- hardware role—Function of the line module: primary or spare
- lockout config—Status of redundancy on this line module (protected—line module redundancy is enabled; locked out—line module redundancy is disabled)
- backed up by slot—Slot that contains the line module that is a spare for this primary line module
- sparing for slot—Slot that contains the primary line module for which this line module is a spare
- revert at—Time at which you want line module to revert
- midplane type—Identifier for the type of midplane
- midplane rev—Hardware revision number of the redundancy midplane
host1#show redundancySRP---high-availability state: activecurrent redundancy mode: high-availabilitylast activation type: cold-switchLine Card---------automatic reverting is offbackedup sparinghardware lockout by for revertslot role config slot slot at---- -------- --------- ------ ------- ------3 --- --- --- --- ---8 spare --- --- --- ---12 primary protected --- --- ---midplane midplaneslots type rev------ -------- --------8 - 13 6 0Example 2 host1#show redundancy detailSRP---high-availability state: activecurrent redundancy mode: high-availabilitylast activation type: cold-switchCriteria Required for High Availability to be Active----------------------------------------------------criterion met---------------------------------------------------- ---Active SRP hardware supports High Availability? YesHigh Availability mode configured? YesMirroring Subsystem present? YesNetwork Core Dumps disabled? YesRunning configuration is safe for High Availability? YesStandby SRP hardware supports High Availability? YesStandby SRP is online and capable of mirroring? YesStandby SRP is running the same release? YesLine Card---------automatic reverting is offbackedup sparinghardware lockout by for revertslot role config slot slot at---- -------- --------- ------ ------- ------3 --- --- --- --- ---8 spare --- --- --- ---12 primary protected --- --- ---midplane midplaneslots type rev------ -------- --------8 - 13 6 0show redundancy clients
- Use to display high availability clients and their various levels of high availability support.
- Specify an optional client type that you want to view (all, supported, unsafe, unsupported)
NOTE: Issuing this command without the optional client type results in showing only unsupported high availability clients (the default).
- Field descriptions
- client—High availability client
- mode—Whether the client is supported or unsupported for high availability
- configuration—Safety level of the configuration based on whether or not the client is supported or unsupported and, in the case of those unsupported, whether or not the client has been configured (for example, if an unsupported client is configured on a router with high availability enabled, the configuration would read "unsafe")
host1#show redundancy clientsUnsupported High Availability Clients-------------------------------------client configuration--------------------- -------------Bridged Ethernet safeTransparent Bridging safeDHCP Proxy Client safeFlow Inspection safeframeRelay safeGlobal Ipv6 safeIPsec Transport (ITM) safel2tpDialoutGenerator safel2tp safeDHCPv4 Local Server safeDHCPv6 Local Server safeMPLS safeRadius Relay Server safeSMDS safeSonetVT safeIPsec Tunnel (ST) safeExample 2 host1#show redundancy clients allHigh Availability Client Information------------------------------------client mode configuration--------------------- ----------- -------------atm1483DataService supported safeAA83 supported safeaaaServer supported safeatmAal5 supported safeatm supported safeBridged Ethernet unsupported safeTransparent Bridging unsupported safedcm supported safedhcpExternal supported safeDHCP Proxy Client unsupported safeDS1 supported safeDS3 supported safeethernet supported safeFlow Inspection unsupported safeframeRelay unsupported safeFT1 supported safeGlobal Ipv6 unsupported safeGlobal Ip supported safeHDLC supported safeipflowstats supported safeIpSubscriberManager supported safeIPTU supported safeIPVR supported safeIPsec Transport (ITM) unsupported safel2tpDialoutGenerator unsupported safel2tp unsupported safeDHCPv4 Local Server unsupported safeDHCPv6 Local Server unsupported safeMPLS unsupported safePMGR supported safepppoe supported safeppp supported safeqos supported safeRadius Relay Server unsupported safeSCM supported safeCisco HDLC supported safeSMDS unsupported safeSonet supported safeSonetPath supported safeSonetVT unsupported safeIPsec Tunnel (ST) unsupported safeshow redundancy history
- Use to display information about dates, times, and the number of occurrences for starts and switchovers.
- Use the srp keyword to view SRP module-specific information.
- Use the detail keyword to view additional history information.
- Field descriptions
- system up time—Amount of time elapsed since the last cold boot
- last cold start—Date and time the router experienced the last cold start
- last cold switchover—Date and time the router experienced the last cold switchover
- last warm switchover—Date and time the router experienced the last warm switchover
- cold starts—Total number of cold starts the router has experienced
- switchovers—Number of cold, warm, and consecutive warm switchovers the router has experienced
host1#show redundancy historysystem up time: 0 00:08:01last cold start: 2004-07-26 10:44:25last cold switchover: 2004-07-25 18:51:56last warm switchover: 2004-07-25 20:58:57activation statistics:cold starts: 92switchovers:cold: 21warm: 147consecutive warm: 0Example 2 host1#show redundancy history detailsystem up time: 0 00:08:01last cold start: 2004-07-26 10:44:25last cold switchover: 2004-07-25 18:51:56last warm switchover: 2004-07-25 20:58:57activation statistics:cold starts: 92switchovers:cold: 21warm: 147consecutive warm: 0systemSRP activation time type slot uptime running release------------------- ---------- ---- ------ -----------------2004-09-08 15:10:40 cold-start 00 --- erx_6-0-0b1-8.rel2004-09-08 14:39:10 cold-start 00 --- erx_6-0-0b1-1.relshow redundancy line-card
- automatic reverting—State of automatic reverting (on or off)
- slot(s)—Slots in which the line modules reside
- hardware role—Function of the line module: primary or spare
- lockout config—Status of redundancy on this line module (protected—Line module redundancy is enabled; locked out—Line module redundancy is disabled)
- backed up by slot—Slot that contains the line module that is a spare for this primary line module
- sparing for slot—Slot that contains the primary line module for which this line module is a spare
- revert at—Time at which you want line module to revert
- midplane type—Identifier for the type of midplane
- midplane rev—Hardware revision number of the redundancy midplane
host1#show redundancy line-cardautomatic reverting is offbackedup sparinghardware lockout by for revertslot role config slot slot at---- -------- --------- ------ ------- ------3 --- --- --- --- ---8 spare --- --- --- ---12 primary protected --- --- ---midplane midplaneslots type rev------ -------- --------8 - 13 6 0show redundancy srp
- Use to display SRP-module-specific redundancy information.
- Use the brief keyword to display
- Field descriptions
- high-availability state—State of the high availability mode (disabled, active, or pending)
- current redundancy mode—Redundancy mode currently being used by this router (high-availability or file-system-synchronization)
- last activation type—Last type of activation that occurred on this router (that is, the method by which the SRP las booted [cold-start or warm-start])
- Criteria Required for High Availability to be Active—Criteria required for HA to be active.
NOTE: All criteria must be "yes" for High Availability to be active.
host1#show redundancy srphigh-availability state: activecurrent redundancy mode: high-availabilitylast activation type: warm-switchExample 2 host1#show redundancy srp detailhigh-availability state: activecurrent redundancy mode: high-availabilitylast activation type: warm-switchCriteria Required for High Availability to be Active----------------------------------------------------criterion met---------------------------------------------------- ---Active SRP hardware supports High Availability? YesHigh Availability mode configured? YesMirroring Subsystem present? YesNetwork Core Dumps disabled? YesRunning configuration is safe for High Availability? YesStandby SRP hardware supports High Availability? YesStandby SRP is online and capable of mirroring? YesStandby SRP is running the same release? Yesshow redundancy switchover-history
- SRP activation time—Amount of time the SRP module has been active
- type—Type of switchover
- slot—Slot in which the SRP module resides
- system uptime—Amount of time the chassis has been operational
- running release—Release running on the SRP module at the time of the switchover
host1#show redundancy switchover-historysystemSRP activation time type slot uptime running release------------------- ----------- ---- ---------- -------------------------2004-07-26 10:44:25 cold-start 07 --- L-07-25-60b1mrg-e.rel2004-07-25 20:58:57 warm-switch 06 0 00:15:08 L-07-25-60b1mrg-e.rel2004-07-25 20:53:41 warm-switch 07 0 00:09:51 L-07-25-60b1mrg-e.rel2004-07-25 20:44:43 cold-start 06 --- L-07-25-60b1mrg-e.rel2004-07-25 19:32:01 cold-start 06 --- L-07-25-60b1mrg-d.rel2004-07-25 18:58:01 warm-switch 06 0 00:12:01 L-07-25-60b1mrg-c.rel2004-07-25 18:51:56 cold-switch 07 0 00:05:56 L-07-25-60b1mrg-c.rel2004-07-25 18:46:54 cold-start 06 --- L-07-25-60b1mrg-c.rel2004-07-25 17:44:48 warm-switch 06 0 00:14:32 L-07-25-60b1mrg-b.rel2004-07-25 17:31:07 cold-start 07 --- L-07-25-60b1mrg-b.rel2004-07-25 16:05:08 cold-start 07 --- L-07-25-60b1mrg-a.rel2004-07-24 23:25:09 warm-switch 07 0 16:27:03 L-07-24-60b1mrg-b.rel2004-07-24 23:18:23 cold-switch 06 0 16:20:17 L-07-24-60b1mrg-b.relClearing the Redundancy History
You can use the clear redundancy history command to clear the high availability switchover history for the router.
clear redundancy history
host1#show redundancy history detailsystem up time: 0 00:08:01last cold start: 2004-07-26 10:44:25last cold switchover: 2004-07-25 18:51:56last warm switchover: 2004-07-25 20:58:57activation statistics:cold starts: 92switchovers:cold: 21warm: 147consecutive warm: 0systemSRP activation time type slot uptime running release------------------- ----------- ---- ---------- -------------------------2004-07-26 10:44:25 cold-start 07 --- L-07-25-60b1mrg-e.rel2004-07-25 20:58:57 warm-switch 06 0 00:15:08 L-07-25-60b1mrg-e.rel2004-07-25 20:53:41 warm-switch 07 0 00:09:51 L-07-25-60b1mrg-e.rel2004-07-25 20:44:43 cold-start 06 --- L-07-25-60b1mrg-e.rel2004-07-25 19:32:01 cold-start 06 --- L-07-25-60b1mrg-d.rel2004-07-25 18:58:01 warm-switch 06 0 00:12:01 L-07-25-60b1mrg-c.rel2004-07-25 18:51:56 cold-switch 07 0 00:05:56 L-07-25-60b1mrg-c.relhost1#clear redundancy historyhost1#show redundancy historysystem up time: 0 00:08:01last cold start: 2004-07-26 10:44:25last cold switchover: 2004-07-25 18:51:56last warm switchover: 2004-07-25 20:58:57activation statistics:cold starts: 92switchovers:cold: 21warm: 147consecutive warm: 0systemSRP activation time type slot uptime running release------------------- ----------- ---- ---------- -------------------------