Table Of Contents
show ip bgp vpnv4 all sso summary
show ip rsvp high-availability counters
subscribe-to-alert-group configuration
subscribe-to-alert-group diagnostic
subscribe-to-alert-group environment
subscribe-to-alert-group inventory
subscribe-to-alert-group syslog
show call-home
To display the configured information for Call Home, use the show call-home command in privileged EXEC mode.
show call-home [alert-group | detail | mail-server status | profile {all | name} | statistics]
Syntax Description
Command Default
This command has no default settings.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example displays the Call Home configuration settings:
Router# show call-homeCurrent call home settings:call home feature : disablecall home message's from address: switch@example.comcall home message's reply-to address: support@example.comcontact person's email address: technical@example.comcontact person's phone number: +1-111-111-1111street address: 1234 Any Street, Any city, Any state, 12345customer ID: ExampleCorpcontract ID: X123456789site ID: SantaClaraMail-server[1]: Address: smtp.example.com Priority: 1Mail-server[2]: Address: 192.168.0.1 Priority: 2Rate-limit: 20 message(s) per minuteAvailable alert groups:Keyword State Description------------------------ ------- -------------------------------configuration Disable configuration infodiagnostic Disable diagnostic infoenvironment Disable environmental infoinventory Enable inventory infosyslog Disable syslog infoProfiles:Profile Name: campus-nocProfile Name: CiscoTAC-1The following example displays detailed configuration information for Call Home:
Router# show call-home detailCurrent call home settings:call home feature : disablecall home message's from address: switch@example.comcall home message's reply-to address: support@example.comcontact person's email address: technical@example.comcontact person's phone number: +1-111-111-1111street address: 1234 Any Street, Any city, Any state, 12345customer ID: ExampleCorpcontract ID: X123456789site ID: SantaClaraMail-server[1]: Address: smtp.example.com Priority: 1Mail-server[2]: Address: 192.168.0.1 Priority: 2Rate-limit: 20 message(s) per minuteAvailable alert groups:Keyword State Description------------------------ ------- -------------------------------configuration Disable configuration infodiagnostic Disable diagnostic infoenvironment Disable environmental infoinventory Enable inventory infosyslog Disable syslog infoProfiles:Profile Name: campus-nocProfile status: ACTIVEPreferred Message Format: long-textMessage Size Limit: 3145728 BytesPreferred Transport Method: emailEmail address(es): noc@example.comHTTP address(es): Not yet set upAlert-group Severity------------------------ ------------inventory normalSyslog-Pattern Severity------------------------ ------------N/A N/AProfile Name: CiscoTAC-1Profile status: INACTIVEPreferred Message Format: xmlMessage Size Limit: 3145728 BytesPreferred Transport Method: emailEmail address(es): callhome@cisco.comHTTP address(es): Not yet set upPeriodic configuration info message is scheduled every 1 day of the month at 09:27Periodic inventory info message is scheduled every 1 day of the month at 09:12Alert-group Severity------------------------ ------------diagnostic minorenvironment minorSyslog-Pattern Severity------------------------ ------------.* majorThe following example displays available Call Home alert groups:
Router# show call-home alert-groupAvailable alert groups:Keyword State Description------------------------ ------- -------------------------------configuration Disable configuration infodiagnostic Disable diagnostic infoenvironment Disable environmental infoinventory Enable inventory infosyslog Disable syslog infoThe following example displays e-mail server status information for Call Home:
Router# show call-home mail-server statusPlease wait. Checking for mail server status ...Translating "smtp.example.com"Mail-server[1]: Address: smtp.example.com Priority: 1 [Not Available]Mail-server[2]: Address: 192.168.0.1 Priority: 2 [Not Available]The following example displays information for all predefined and user-defined profiles for Call Home:
Router# show call-home profile allProfile Name: campus-nocProfile status: ACTIVEPreferred Message Format: long-textMessage Size Limit: 3145728 BytesPreferred Transport Method: emailEmail address(es): noc@example.comHTTP address(es): Not yet set upAlert-group Severity------------------------ ------------inventory normalSyslog-Pattern Severity------------------------ ------------N/A N/AProfile Name: CiscoTAC-1Profile status: INACTIVEPreferred Message Format: xmlMessage Size Limit: 3145728 BytesPreferred Transport Method: emailEmail address(es): callhome@cisco.comHTTP address(es): Not yet set upPeriodic configuration info message is scheduled every 1 day of the month at 09:27Periodic inventory info message is scheduled every 1 day of the month at 09:12Alert-group Severity------------------------ ------------diagnostic minorenvironment minorSyslog-Pattern Severity------------------------ ------------.* majorThe following example displays information for a user-defined destination profile named "campus-noc":
Router# show call-home profile campus-nocProfile Name: campus-nocProfile status: ACTIVEPreferred Message Format: long-textMessage Size Limit: 3145728 BytesPreferred Transport Method: emailEmail address(es): noc@example.comHTTP address(es): Not yet set upAlert-group Severity------------------------ ------------inventory normalSyslog-Pattern Severity------------------------ ------------N/A N/AThe following example displays Call Home statistics:
Router# show call-home statisticsSuccessful Call-Home Events: 0Dropped Call-Home Events due to Rate Limiting: 0The following example shows a sample of the Call Home statistics output on a Cisco ASR 1000 Series Router in Cisco IOS XE Release 2.6:
PE42_ASR-1004#show call-home statisticsMessage Types Total Email HTTP------------- -------------------- -------------------- ------------------Total Success 0 0 0Config 0 0 0Diagnostic 0 0 0Environment 0 0 0Inventory 0 0 0SysLog 0 0 0Test 0 0 0Request 0 0 0Send-CLI 0 0 0Total In-Queue 0 0 0Config 0 0 0Diagnostic 0 0 0Environment 0 0 0Inventory 0 0 0SysLog 0 0 0Test 0 0 0Request 0 0 0Send-CLI 0 0 0Total Failed 0 0 0Config 0 0 0Diagnostic 0 0 0Environment 0 0 0Inventory 0 0 0SysLog 0 0 0Test 0 0 0Request 0 0 0Send-CLI 0 0 0Total Ratelimit-dropped 0 0 0Config 0 0 0Diagnostic 0 0 0Environment 0 0 0Inventory 0 0 0SysLog 0 0 0Test 0 0 0Request 0 0 0Send-CLI 0 0 0Last call-home message sent time: n/aRelated Commands
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
service call-home
Enables Call Home.
show cef nsf
To show the current Cisco nonstop forwarding (NSF) state of Cisco Express Forwarding on both the active and standby Route Processors (RPs), use the show cef nsf command in privileged EXEC mode.
show cef nsf
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
Usage Guidelines
If you enter the show cef nsf command before a switchover occurs, no switchover activity is reported. After a switchover occurs, you can enter the show cef nsf command to display details about the switchover as reported by the newly active RP. On the Cisco 12000 and 7500 series Internet routers, details about line card switchover are also provided.
Examples
The following example shows the current NSF state:
Router# show cef nsfLast switchover occurred: 00:01:30.088 agoRouting convergence duration: 00:00:34.728FIB stale entry purge durations:00:00:01.728 - Default00:00:00.088 - RedSwitchoverSlot Count Type Quiesce Period1 2 sso 00:00:00.1082 1 rpr+ 00:00:00.9483 2 sso 00:00:00.1525 2 sso 00:00:00.0926 1 rpr+ 00:00:00.632No NSF stats available for the following linecards:4 7Table 1 describes the significant fields shown in the display.
Related Commands
show cef state
To display the state of Cisco Express Forwarding on a networking device, use the show cef state command in privileged EXEC mode.
show cef state
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
Example for Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12,2(33)SRA, 12,2(33)SXH, 12.4(20T, and Later Releases
The following example shows the state of Cisco Express Forwarding on the active route processor (RP):
Router# show cef stateCEF Status:RP instancecommon CEF enabledIPv4 CEF Status:CEF enabled/runningdCEF disabled/not runningCEF switching enabled/runninguniversal per-destination load sharing algorithm, id A189DD49IPv6 CEF Status:CEF enabled/runningdCEF disabled/not runningoriginal per-destination load sharing algorithm, id A189DD49Table 3 describes the significant fields shown in the display.
Example for Cisco IOS Releases Before Cisco IOS 12.2(25)S
The following example shows the state of Cisco Express Forwarding on the active route processor (RP):
Router# show cef stateRRP state:I am standby RRP: noRF Peer Presence: yesRF PeerComm reached: yesRedundancy mode: SSO(7)CEF NSF: enabled/runningTable 3 describes the significant fields shown in the display.
The following example shows the state of Cisco Express Forwarding on the standby RP:
Router# show cef stateRRP state:I am standby RRP: yesMy logical slot: 0RF Peer Presence: yesRF PeerComm reached: yesCEF NSF: runningRelated Commands
show ip bgp vpnv4 all sso summary
To display information about Border Gateway Protocol (BGP) peers that support BGP nonstop routing (NSR) with stateful switchover (SSO), use the show ip bgp vpn4 sso summary command in privileged EXEC mode.
show ip bgp vpnv4 all sso summary
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show ip bgp vpnv4 all sso summary command is used to display the number of BGP neighbors that are in SSO mode.
Examples
The following is sample output from the show ip bgp vpnv4 all sso summary command:
Router# show ip bgp vpnv4 all sso summaryStateful switchover support enabled for 40 neighborsTable 4 describes the significant fields shown in the display.
Table 4 show ip bgp vpnv4 all sso summary Field Descriptions
Stateful Switchover support enabled for
Indicates the number of BGP neighbors that are in SSO mode.
Related Commands
show ip ospf nsf
To display IP Open Shortest Path First (OSPF) nonstop forwarding (NSF) state information, use the show ip ospf nsf command in user EXEC or privileged EXEC mode.
show ip ospf nsf
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following is sample output from the show ip ospf nsf command. The fields are self-explanatory.
Router# show ip ospf nsfRouting Process "ospf 2"Non-Stop Forwarding enabledIETF NSF helper support enabledCisco NSF helper support enabledOSPF restart state is NO_RESTARTHandle 1786466308, Router ID 192.0.2.1, checkpoint Router ID 0.0.0.0Config wait timer interval 10, timer not runningDbase wait timer interval 120, timer not runningshow ip rsvp high-availability counters
To display all Resource Reservation Protocol (RSVP) traffic engineering (TE) high availability (HA) counters that are being maintained by a Route Processor (RP), use the show ip rsvp high-availability counters command in user EXEC or privileged EXEC mode.
show ip rsvp high-availability counters
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Use the show ip rsvp high-availability counters command to display the HA counters, which include state, ISSU, checkpoint messages, resource failures, and errors.
The command output differs depending on whether the RP is active or standby. (See the "Examples" section for more information.)
Use the clear ip rsvp high-availability counters command to clear all counters.
Examples
The following is sample output from the show ip rsvp high-availability counters command on the active RP:
Router# show ip rsvp high-availability countersState: ActiveP2P LSPs for which recovery:Attempted: 1Succeeded: 1Failed: 0P2MP subLSPs for which recovery:Attempted: 2Succeeded: 2Failed: 0Bulk syncinitiated: 1Send timerstarted: 2Checkpoint Messages (Items) SentSucceeded: 2 (8)Acks accepted:2 (8)Acks ignored: (0)Nacks: 0 (0)Failed: 0 (0)Buffer alloc: 2Buffer freed: 4ISSU:Checkpoint Messages Transformed:On Send:Succeeded: 2Failed: 0Transformations: 0On Recv:Succeeded: 2Failed: 0Transformations: 0Negotiation:Started: 2Finished: 2Failed to Start: 0Messages:Sent:Send succeeded: 14Send failed: 0Buffer allocated: 14Buffer freed: 0Buffer alloc failed: 0Received:Succeeded: 10Failed: 0Buffer freed: 10Init:Succeeded: 1Failed: 0Session Registration:Succeeded: 1Failed: 0Session Unregistration:Succeeded: 1Failed: 0Errors:NoneHistorical: (When Active was Standby)Checkpoint Messages (Items) ReceivedValid: 2 (11)Invalid: 0 (0)Buffer freed: 2Table 5 describes the significant fields shown in the display.
The following is sample output from the show ip rsvp high-availability counters command on the standby RP:
Router# show ip rsvp high-availability countersState: StandbyCheckpoint Messages (Items) ReceivedValid: 1 (2)Invalid: 0 (0)Buffer freed: 1ISSU:Checkpoint Messages Transformed:On Send:Succeeded: 0Failed: 0Transformations: 0On Recv:Succeeded: 1Failed: 0Transformations: 0Negotiation:Started: 1Finished: 1Failed to Start: 0Messages:Sent:Send succeeded: 5Send failed: 0Buffer allocated: 5Buffer freed: 0Buffer alloc failed: 0Received:Succeeded: 7Failed: 0Buffer freed: 7Init:Succeeded: 1Failed: 0Session Registration:Succeeded: 0Failed: 0Session Unregistration:Succeeded: 0Failed: 0Errors:NoneTable 6 describes the significant fields shown in the display.
Table 6 show ip rsvp high-availability counters—Standby RP Field Descriptions
State
The RP state:
•
Standby—Standby (backup) RP.
Checkpoint Messages (Items) Received
The details of the messages or items received by the standby RP. Values are the following:
•
•
•
ISSU
ISSU counters.
Note
Errors
The details of errors or caveats.
Related Commands
show ip rsvp interface detail
To display the hello configuration for specific interfaces, use the show ip rsvp interface detail command in user EXEC or privileged EXEC mode.
show ip rsvp interface detail [type number]
Syntax Description
type number
(Optional) Type and number of the interface for which you want to display the hello configuration.
Command Default
If the optional argument is not specified, the hello configuration for all interfaces is displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following is sample output from the show ip rsvp interface detail command:
Router# show ip rsvp interface detail GigabitEthernet 9/47Tu0:RSVP: EnabledInterface State: UpBandwidth:Curr allocated: 10K bits/secMax. allowed (total): 75K bits/secMax. allowed (per flow): 75K bits/secMax. allowed for LSP tunnels using sub-pools: 0 bits/secSet aside by policy (total): 0 bits/secAdmission Control:Header Compression methods supported:rtp (36 bytes-saved), udp (20 bytes-saved)Tunnel IP Overhead percent:4Tunnel Bandwidth considered:YesTraffic Control:RSVP Data Packet Classification is ON via CEF callbacksSignalling:DSCP value used in RSVP msgs: 0x3FNumber of refresh intervals to enforce blockade state: 4Authentication: disabledKey chain: <none>Type: md5Window size: 1Challenge: disabledHello Extension:State: DisabledTable 7 describes the significant fields shown in the display.
Related Commands
show isis nsf
To display current state information regarding Intermediate System-to-Intermediate System (IS-IS) Cisco nonstop forwarding (NSF), use the show isis nsf command in user EXEC mode.
show isis nsf
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Command History
Usage Guidelines
The show isis nsf command can be used with both Cisco proprietary IS-IS NSF and Internet Engineering Task Force (IETF) IS-IS NSF. The information displayed when this command is entered depends on which protocol has been configured. To configure nsf for a specific routing protocol, use the router bgp, router ospf, or router isis commands in global configuration mode.
Examples
The following example shows state information for an active RP that is configured to use Cisco proprietary IS-IS NSF:
Router# show isis nsfNSF enabled, mode 'cisco'RP is ACTIVE, standby ready, bulk sync completeNSF interval timer expired (NSF restart enabled)Checkpointing enabled, no errorsLocal state:ACTIVE, Peer state:STANDBY HOT, Mode:SSOTable 8 describes the significant fields shown in the display.
The following example shows state information for a standby RP that is configured to use Cisco proprietary IS-IS NSF:
Router# show isis nsfNSF enabled, mode 'cisco'RP is STANDBY, chkpt msg receive count:ADJ 2, LSP 314NSF interval timer notification received (NSF restart enabled)Checkpointing enabled, no errorsLocal state:STANDBY HOT, Peer state:ACTIVE, Mode:SSOThe following example shows state information when the networking device is configured to use IETF IS-IS NSF:
Router# show isis nsfNSF is ENABLED, mode IETFNSF pdb state:InactiveNSF L1 active interfaces:0NSF L1 active LSPs:0NSF interfaces awaiting L1 CSNP:0Awaiting L1 LSPs:NSF L2 active interfaces:0NSF L2 active LSPs:0NSF interfaces awaiting L2 CSNP:0Awaiting L2 LSPs:Interface:Serial3/0/2NSF L1 Restart state:RunningNSF p2p Restart retransmissions:0Maximum L1 NSF Restart retransmissions:3L1 NSF ACK requested:FALSEL1 NSF CSNP requested:FALSENSF L2 Restart state:RunningNSF p2p Restart retransmissions:0Maximum L2 NSF Restart retransmissions:3L2 NSF ACK requested:FALSEInterface:GigabitEthernet2/0/0NSF L1 Restart state:RunningNSF L1 Restart retransmissions:0Maximum L1 NSF Restart retransmissions:3L1 NSF ACK requested:FALSEL1 NSF CSNP requested:FALSENSF L2 Restart state:RunningNSF L2 Restart retransmissions:0Maximum L2 NSF Restart retransmissions:3L2 NSF ACK requested:FALSEL2 NSF CSNP requested:FALSERelated Commands
show issu
To display Enhanced Fast Software Upgrade (eFSU) information, use the show issu command.
show issu {outage slot {all | num} | patch context | patch type image | platform states}
Syntax Description
Command Default
None
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following example shows how to display an average estimate of the traffic outage for all slots during the upgrade or downgrade:
Router# show issu outage slot allSlot # Card Type MDR Mode Max Outage Time------ ------------------------------------- ----------- ---------------1 CEF720 24 port 1000mb SFP WARM_RELOAD 300 secs2 1-subslot SPA Interface Processor-600 WARM_RELOAD 300 secs3 4-subslot SPA Interface Processor-400 WARM_RELOAD 300 secs4 2+4 port GE-WAN RELOAD 360 secsRouter#Related Commands
show issu clients
To display a list of the current In Service Software Upgrade (ISSU) clients—that is, the network applications and protocols supported by ISSU—use the show issu clients command in user EXEC or privileged EXEC mode.
show issu clients
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
This command lists all ISSU clients currently operating in the network, along with their Client ID numbers and the number of entities each client contains.
You should enter this command before you enter the issu runversion command, because if a client (application or protocol) that needs to continue operating in the network does not appear in the displayed list, you will know not to continue the software upgrade (because proceeding further with ISSU would then halt the operation of that application or protocol).
Examples
The following example shows a client list displayed by entering this command:
Router# show issu clientsClient_ID = 2, Client_Name = ISSU Proto client, Entity_Count = 1Client_ID = 3, Client_Name = ISSU RF, Entity_Count = 1Client_ID = 4, Client_Name = ISSU CF client, Entity_Count = 1Client_ID = 5, Client_Name = ISSU Network RF client, Entity_Count = 1Client_ID = 7, Client_Name = ISSU CONFIG SYNC, Entity_Count = 1Client_ID = 8, Client_Name = ISSU ifIndex sync, Entity_Count = 1Client_ID = 9, Client_Name = ISSU IPC client, Entity_Count = 1Client_ID = 10, Client_Name = ISSU IPC Server client, Entity_Count = 1Client_ID = 11, Client_Name = ISSU Red Mode Client, Entity_Count = 1Client_ID = 12, Client_Name = ISSU EHSA services client, Entity_Count = 1Client_ID = 100, Client_Name = ISSU rfs client, Entity_Count = 1Client_ID = 110, Client_Name = ISSU ifs client, Entity_Count = 1Client_ID = 1001, Client_Name = OC3POS-6, Entity_Count = 4Client_ID = 1002, Client_Name = C10K ATM, Entity_Count = 1Client_ID = 1003, Client_Name = C10K CHSTM1, Entity_Count = 1Client_ID = 1004, Client_Name = C10K CT3, Entity_Count = 1Client_ID = 1005, Client_Name = C10K GE, Entity_Count = 1Client_ID = 1006, Client_Name = C10K ET, Entity_Count = 1Client_ID = 1007, Client_Name = C10K CHE1T1, Entity_Count = 1Client_ID = 1009, Client_Name = C10K MFE, Entity_Count = 1Client_ID = 1010, Client_Name = C10K APS, Entity_Count = 1Client_ID = 1013, Client_Name = C10K CARD OIR, Entity_Count = 1Client_ID = 2002, Client_Name = CEF Push ISSU client, Entity_Count = 1Client_ID = 2003, Client_Name = ISSU XDR client, Entity_Count = 1Client_ID = 2004, Client_Name = ISSU SNMP client, Entity_Count = 1Client_ID = 2005, Client_Name = ISSU HDLC Client, Entity_Count = 1Client_ID = 2006, Client_Name = ISSU QoS client, Entity_Count = 1Client_ID = 2007, Client_Name = ISSU LSD Label Mgr HA Client, Entity_Count = 1Client_ID = 2008, Client_Name = ISSU Tableid Client, Entity_Count = 1Client_ID = 2009, Client_Name = ISSU MPLS VPN Client, Entity_Count = 1Client_ID = 2010, Client_Name = ARP HA, Entity_Count = 1Client_ID = 2011, Client_Name = ISSU LDP Client, Entity_Count = 1Client_ID = 2012, Client_Name = ISSU HSRP Client, Entity_Count = 1Client_ID = 2013, Client_Name = ISSU ATM Client, Entity_Count = 1Client_ID = 2014, Client_Name = ISSU FR Client, Entity_Count = 1Client_ID = 2015, Client_Name = ISSU REDSSOC client, Entity_Count = 1Client_ID = 2019, Client_Name = ISSU TCP client, Entity_Count = 1Client_ID = 2020, Client_Name = ISSU BGP client, Entity_Count = 1Client_ID = 2021, Client_Name = XDR Int Priority ISSU client, Entity_Count = 1Client_ID = 2022, Client_Name = XDR Proc Priority ISSU client, Entity_Count = 1Client_ID = 2023, Client_Name = FIB HWIDB ISSU client, Entity_Count = 1Client_ID = 2024, Client_Name = FIB IDB ISSU client, Entity_Count = 1Client_ID = 2025, Client_Name = FIB HW subblock ISSU client, Entity_Count = 1Client_ID = 2026, Client_Name = FIB SW subblock ISSU client, Entity_Count = 1Client_ID = 2027, Client_Name = Adjacency ISSU client, Entity_Count = 1Client_ID = 2028, Client_Name = FIB IPV4 ISSU client, Entity_Count = 1Client_ID = 2030, Client_Name = MFI Pull ISSU client, Entity_Count = 1Client_ID = 2031, Client_Name = MFI Push ISSU client, Entity_Count = 1Client_ID = 2051, Client_Name = ISSU CCM Client, Entity_Count = 1Client_ID = 2052, Client_Name = ISSU PPP SIP CCM Client, Entity_Count = 1Client_ID = 2054, Client_Name = ISSU process client, Entity_Count = 1Base Clients:Client_Name = ISSU Proto clientClient_Name = ISSU RFClient_Name = ISSU CF clientClient_Name = ISSU Network RF clientClient_Name = ISSU CONFIG SYNCClient_Name = ISSU ifIndex syncClient_Name = ISSU IPC clientClient_Name = ISSU IPC Server clientClient_Name = ISSU Red Mode ClientClient_Name = ISSU EHSA services clientTable 8 describes the significant fields shown in the display.
Related Commands
show issu comp-matrix
To display information regarding the In Service Software Upgrade (ISSU) compatibility matrix, use the show issu comp-matrix command in user EXEC or privileged EXEC mode.
show issu comp-matrix {negotiated | stored}
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Before attempting an ISSU, you should know the compatibility level between the Cisco IOS software versions on the active and the standby Route Processors (RPs). ISSU will not work if the two versions are incompatible. Use the show issu comp-matrix command with the negotiated keyword to display information on the negotiation of the compatibility matrix data between two software versions on a given system.
Compatibility matrix data is stored with each Cisco IOS software image that supports the ISSU capability. Use the show issu comp-matrix command with the stored keyword to display stored compatibility matrix information.
Examples
The following example shows how to display stored compatibility matrix information:
Router# show issu comp-matrix storedshow issu entities
To display information about entities within one or more In Service Software Upgrade (ISSU) clients, use the show issu entities command in user EXEC or privileged EXEC mode.
show issu entities [client-id]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
This command was introduced.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.
Usage Guidelines
An entity is a logical group of sessions that possess some common attributes. Enter a Client_ID if you are interested in seeing information only about one client's entities. If a Client_ID is not specified, the command will display all ISSU clients' entities known to the device.
If you are not sure of the precise Client_ID number to enter for the client you are interested in, use the show issu clients command to display the current list of clients with their names and ID numbers.
Examples
The following example shows detailed information about the entities within the virtual routing and forwarding (VRF) ("Table ID") client:
Router# show issu entities 2008Client_ID = 2008 :Entity_ID = 1, Entity_Name = Tableid Entity :MsgType MsgGroup CapType CapEntry CapGroupCount Count Count count Count2 2 1 2 2Table 10 describes the significant field shown in the display.
Related Commands
show issu message types
To display formats ("types"), versions, and maximum packet size of the In Service Software Upgrade (ISSU) messages supported by a particular client, use the show issu message types command in user EXEC or privileged EXEC mode.
show issu message types client-id
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
This command was introduced.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.
Usage Guidelines
If you are not sure of the Client_ID number to enter into this command, use the show issu clients command. It displays the current list of clients, along with their names and ID numbers.
Examples
The following example displays the message type, version, and maximum message size supported by the Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) client:
Router# show issu message types 2009Client_ID = 2009, Entity_ID = 1 :Message_Type = 1, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 32Table 11 describes the significant fields shown in the display.
Related Commands
show issu negotiated
To display details of the session's negotiation about message version or client capabilities, use the show issu negotiated command in user EXEC or privileged EXEC mode.
show issu negotiated {version | capability} session-id
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
This command was introduced.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.
Usage Guidelines
If you are not sure of the session_ID number to enter into this command, enter the show issu sessions command. It will display the session_ID.
Examples
The following example displays the results of a negotiation about message versions:
router# show issu negotiated version 39Session_ID = 39 :Message_Type = 1, Negotiated_Version = 1, Message_MTU = 32Table 12 describes the significant fields shown in the display.
The following example displays the results of a negotiation about the client application's capabilities:
router# show issu negotiated capability 39Session_ID = 39 :Negotiated_Cap_Entry = 1Table 13 describes the significant fields shown in the display.
Related Commands
show issu outage
To display the maximum outage time for installed line cards during an in service software upgrade (ISSU), use the show issu outage command from the switch processor (SP) console.
show issu outage slot {slot-num | all}
Syntax Description
slot-num
Displays the maximum outage time for the line card in the specified slot.
all
Displays the maximum outage time for all installed line cards.
Command Modes
SP console
Command History
Usage Guidelines
Once the new software is downloaded onto the router (after you issue the issu loadversion command), you can issue show issu outage slot all from the SP console to display the maximum outage time for installed line cards.
During an ISSU, the router preloads line card software onto line cards that support enhanced Fast Service Upgrade (eFSU). Then, when the switchover occurs between active and standby processors, the line cards that support eFSU are restarted with the new, preloaded software, which helps to minimize outage time during the upgrade. Line cards that do not support eFSU undergo a hard reset at switchover, and the software image is loaded after the line card is restarted.
The output for the show issu outage command shows the type of reload that the line card will perform along with the maximum outage time (see the "Examples" section).
Note
Examples
The following command examples show the maximum outage time for installed line cards:
Router# show issu outage slot allSlot # Card Type MDR Mode Max Outage Time------ ------------------------------------------- ----------- ---------------1 CEF720 4 port 10-Gigabit Ethernet NSF_RELOAD 3 secs2 FRU type (0x6003, 0x3F8(1016)) NSF_RELOAD 3 secs3 4-subslot SPA Interface Processor-200 NSF_RELOAD 3 secsRouter#Router# show issu outage slot allSlot # Card Type MDR Mode Max Outage Time------ ------------------------------------- ----------- ---------------1 CEF720 24 port 1000mb SFP WARM_RELOAD 300 secs2 1-subslot SPA Interface Processor-600 WARM_RELOAD 300 secs3 4-subslot SPA Interface Processor-400 WARM_RELOAD 300 secs4 2+4 port GE-WAN RELOAD 360 secsRouter#Table 5 describes the fields in the display.
Related Commands
show issu patch
To provide information about upgrade installation on both active and standby routers, use the show issu patch command in privileged EXEC mode.
show issu patch {pending {disk} | context | type {image | patch}}
Syntax Description
Command Default
No information about the upgrade is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show issu patch command provides an overview of the impact on a system upgrade before and during the upgrade procedure.
Examples
The following example provides information about a pending upgrade on disk0:
Router# show issu patch pending disk0:/sysOverall Impact of the pending upgrade:Search Root: disk0:/sysType of upgrade: New base imageAction: Go StandbySlot # Card Type Impacted------ ------------------------------------------- -----------1 48 port 10/100 mb RJ-45 ethernet Yes2 SFM-capable 16 port 1000mb GBIC Yes3 48 port 10/100 mb RJ-45 ethernet Yes4 CEF720 48 port 10/100/1000mb Ethernet Yes8 CEF720 48 port 10/100/1000mb Ethernet Yes9 Intrusion Detection System YesTable 15 describes significant fields shown in the display.
.
show issu platform img-dnld
To display the progression of image download from slave to the Versatile Interface Processors (VIPs) and to display Minimal Disruptive Restart (MDR) details on Cisco 7600 series routers, use the show issu platform img-dnld command in user EXEC or privileged EXEC mode.
show issu platform img-dnld
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show issu platform img-dnld command is specific to Cisco 7600 series routers.
The show issu platform img-dnld command provides information to help you troubleshoot problems that may occur when performing an enhanced Fast Software Upgrade (eFSU). Entering this command allows you to display the progression of the image download from the slave unit to the VIPs and to display other details such as the following:
•
•
–
–
–
–
–
•
•
•
•
•
•
•
•
This command is available for eFSU on the Cisco 7600 series router platform only.
Examples
The following example output displays information before the download has been started:
Router# show issu platform img-dnldImage download not performed yet.Slot 1: VIP2 R5K, Slot enabled, does not support MDR.Slot 5: VIP2 R5K, Slot enabled, does not support MDR.Slot 9: VIP6-80 RM7000B, Slot enabled, Supports MDR (205702684 bytes Free). Image not downloaded.SLCR : enabledMDR Unsupported slots : 1 5MDR Supported slots : 9No. of Non empty slots : 5No. of Line cards : 3No. of MDR feasible cards : 1No. of MDR Incapable cards : 2No. of MDR capable cards : 1 (0 LC(s) disabled)MDR ready cards : 0Table 16 describes the significant fields shown in the display.
The following sample output occurred during image download. The example shows that 25 percent of the image is downloaded to VIPs. Because slot 1 and slot 5 are not MDR supported, these two line cards will be reloaded during switchover.
Router# show issu platform img-dnldImage downloading, 25% complete (1619968 / 6269374 bytes)Slot 1: VIP2 R5K, Slot enabled, does not support MDR.Slot 5: VIP2 R5K, Slot enabled, does not support MDR.Slot 9: VIP6-80 RM7000B, Slot enabled, Supports MDR (190981516 bytes Free).Image is downloadingSLCR : enabledMDR Unsupported slots : 1 5MDR Supported slots : 9No. of Non empty slots : 5No. of Line cards : 3No. of MDR feasible cards : 1No. of MDR Incapable cards : 2No. of MDR capable cards : 1 (0 LC(s) disabled)MDR ready cards : 02 VIP(s) will be reloaded.The following example output occurs after the image was downloaded. The examples shows that slot 9 completed the image download, and that the line card in slot 9 now has nearly 190 MB of free space:
Router# show issu platform img-dnldImage download complete.Slot 1: VIP2 R5K, Slot enabled, does not support MDR.Slot 5: VIP2 R5K, Slot enabled, does not support MDR.Slot 9: VIP6-80 RM7000B, Slot enabled, Supports MDR (190995548 bytesFree). Image downloaded.SLCR : enabledMDR Unsupported slots : 1 5MDR Supported slots : 9No. of Non empty slots : 5No. of Line cards : 3No. of MDR feasible cards : 1No. of MDR Incapable cards : 2No. of MDR capable cards : 1 (0 LC(s) disabled)MDR ready cards : 12 VIP(s) will be reloaded.Related Commands
show issu rollback timer
To display the current setting of the In Service Software Upgrade (ISSU) rollback timer, use the show issu rollback timer command in user EXEC or privileged EXEC mode.
show issu rollback timer
Syntax Description
This command has no arguments or keywords.
Command Default
The default rollback timer value is 45 minutes.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
If the ISSU rollback timer value has never been set, then the default rollback timer value of 45 minutes is displayed.
Examples
The following example shows the default rollback timer value:
Router# show issu rollback-timerRollback Process State = Not in progressConfigured Rollback Time = 45:00Table 17 describes the significant fields shown in the display.
Table 17 show issu rollback-timer Field Descriptions
Rollback Process State = Not in progress
State of the rollback process.
Configured Rollback Time = 45:00
Rollback timer value.
Related Commands
show issu sessions
To display detailed information about a particular In Service Software Upgrade (ISSU) client—including whether the client status for the impending software upgrade is compatible—use the show issu sessions command in user EXEC or privileged EXEC mode.
show issu sessions client-id
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
If you are not sure of the Client_ID number to enter into this command, use the show issu clients command to display the current list of clients with their names and ID numbers.
Examples
The following example shows detailed information about the LDP Client:
Router# show issu sessions 2011Client_ID = 2011, Entity_ID = 1 :*** Session_ID = 46, Session_Name = LDP Session :Peer Peer Negotiate Negotiated Cap Msg SessionUniqueID Sid Role Result GroupID GroupID Signature4 34 PRIMARY COMPATIBLE 1 1 0(no policy)Negotiation Session Info for This Message Session:Nego_Session_ID = 46Nego_Session_Name = LDP SessionTransport_Mtu = 3948Table 18 describes the significant fields shown in the display.
Related Commands
show issu state
To display the state and current version of the Route Processors (RPs) during the In Service Software Upgrade (ISSU) process, use the show issu state command in user EXEC or privileged EXEC mode.
show issu state [slot / port] [detail]
Syntax Description
slot
(Optional) PRE slot number.
port
(Optional) PRE port number.
detail
(Optional) Provides detailed information about the state of the active and standby RPs.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Use the show issu state command to display the state and current version of each RP.
It may take several seconds after the issu loadversion command is entered for Cisco IOS software to load onto the standby RP and the standby RP to transition to stateful switchover (SSO) mode. If you enter the show issu state command too soon, you may not see the information you need.
Examples
The following example displays the manner in which the ISSU state is verified.
Router# show issu state detailSlot = ARP State = ActiveISSU State = InitBoot Variable = disk0:ubr10k4-k9p6u2-mz.122SC_20100329,12;Operating Mode = SSOPrimary Version = N/ASecondary Version = N/ACurrent Version = disk0:ubr10k4-k9p6u2-mz.122SC_20100329Variable Store = PrstVblSlot = BRP State = StandbyISSU State = InitBoot Variable = disk0:ubr10k4-k9p6u2-mz.122SC_20100329,12;Operating Mode = SSOPrimary Version = N/ASecondary Version = N/ACurrent Version = disk0:ubr10k4-k9p6u2-mz.122SC_20100329Slot Red Role Peer Act/Sby Image Match RP LC ISSU State ISSU Proc---- --------- ---- -------- -------------- ------------------ ---------5/0 Secondary - standby Yes - -6/0 Primary 5/0 active Yes - -7/0 Primary 5/0 active Yes - -8/0 Primary 5/0 active Yes - -PRE is the new active: FALSEWaiting for MDR: FALSENo Transitional Line Card State information registered.No Peer Line Card State information registered.Peer Line Card Action:-------Card Type-------- -----Action------ --Slots---24rfchannel-spa-1 NO ACTION 0x000000044jacket-1 NO ACTION 0x000000042cable-dtcc NO ACTION 0x000000281gigethernet-hh-1 NO ACTION 0x00000200Table 19 describes the significant fields shown in the display.
Note
Related Commands
show mdr download image
To display the amount of memory needed to store the new software image on line cards that support enhanced Fast Software Upgrade (eFSU), use the show mdr download image command from the switch processor (SP) console in privileged EXEC mode.
show mdr download image
Syntax Description
This command has no arguments or keywords.
Command Modes
SP console
Command History
Usage Guidelines
You must issue the show mdr download image command from the SP console. You cannot issue the command from the line card or from the route processor (RP) console.
During an in service software upgrade (ISSU), the router preloads line card software onto line cards that support eFSU. As part of the software preload, the router automatically reserves memory on the line card to store the new software image (decompressed format).
You can use the show mdr download image command to determine how much memory is needed on the line cards for the new software image.
Note
Examples
The following example shows how much memory will be reserved for the new software on the installed line cards:
Router# remote command switch show mdr download imagePre-download informationSlot CPU In-Progress Complete LC Mem Resv (bytes)1 0 N N 01 1 N N 02 0 N N 317194242 1 N N 03 0 N N 359137283 1 N N 04 0 N N 317194244 1 N N 05 0 N N 05 1 N N 06 0 N N 06 1 N N 07 0 N N 07 1 N N 08 0 N N 08 1 N N 09 0 N N 09 1 N N 010 0 N N 010 1 N N 011 0 N N 011 1 N N 012 0 N N 012 1 N N 013 0 N N 013 1 N N 0Router#Table 5 describes the fields in the display.
show monitor event-trace sbc
To display event trace messages for the Session Border Controller (SBC), use the show monitor event-trace sbc command in privileged EXEC mode.
show monitor event-trace sbc ha {all [detail] | back {minutes | hours:minutes} [detail] | clock hours:minutes [day month] [detail] | from-boot [seconds] [detail] | latest [detail] | parameters}1
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Cisco IOS XE Release 2.1
This command was introduced.
Cisco IOS XE Release 2.3
The sbc_ha keyword was changed to two keywords, sbc and ha.
Usage Guidelines
Use the show monitor event-trace sbc ha command to display trace message information for SBC HA.
The trace function is not locked while information is displayed to the console, which means that new trace messages can accumulate in memory. If entries accumulate faster than they can be displayed, some messages can be lost. If this happens, the show monitor event-trace sbc ha command generates a message indicating that some messages might be lost; however, messages continue to display on the console. If the number of lost messages is excessive, the show monitor event-trace sbc ha command stops displaying messages.
Examples
The following is sample output from the show monitor event-trace sbc ha all command. In the following example, all messages from SBC HA events are displayed.
Router# show monitor event-trace sbc ha all*Jan 16 07:21:49.718: RF: Is Active, from boot = 0x1*Jan 16 07:21:49.720: IPC: Initialised as master*Jan 16 07:21:49.720: RF: Active reached, from boot = 0x1*Jan 16 07:21:59.448: ILT: Registered on 48, result = 0x1*Jan 16 07:21:59.448: RF: Start SM on 48*Jan 16 07:49:02.523: IPC: Session to peer opened*Jan 16 07:49:02.605: ISSU: Negotiation starting*Jan 16 07:49:02.605: RF: Delaying progression at 300*Jan 16 07:49:02.617: ISSU: Negotiation done*Jan 16 07:49:02.617: RF: Negotiation result = 0x1*Jan 16 07:49:02.617: RF: Peer state change, peer state = 0x1*Jan 16 07:49:02.617: RF: Resuming progression at event 300*Jan 16 07:50:00.853: ISSU: Transformed transmit message*Jan 16 07:50:00.853: IPC: Queuing message type SBC_HA_MPF_CAPS_MSG_TYPE*Jan 16 07:50:00.854: IPC: Queued message type SBC_HA_MPF_CAPS_MSG_TYPETable 21 describes the significant fields shown in the display.
The following is sample output from the show monitor event-trace sbc ha latest command. This command display messages from SBC HA events since the last show monitor event-trace sbc ha command was entered.
Router# show monitor event-trace sbc ha latest*Jan 16 07:50:00.922: IPC: Sent message type SBC_HA_SEND_IPS_MSG_TYPE*Jan 16 07:50:00.922: IPC: Received message type SBC_HA_SEND_IPS_MSG_TYPE*Jan 16 07:50:00.922: ISSU: Transformed received message*Jan 16 07:50:00.922: ILT: Received IPS for PID 0x30105000, type = 0x16820002*Jan 16 07:50:00.922: ILT: Target 49 is remote, for PID 0x31105000*Jan 16 07:50:00.922: ILT: Send IPS to PID 0x31105000, type = 0x16820001*Jan 16 07:50:00.922: ISSU: Transformed transmit message*Jan 16 07:50:00.922: IPC: Queuing message type SBC_HA_SEND_IPS_MSG_TYPE*Jan 16 07:50:00.922: IPC: Queued message type SBC_HA_SEND_IPS_MSG_TYPE*Jan 16 07:50:00.922: IPC: Sent message type SBC_HA_SEND_IPS_MSG_TYPEThis command displays the messages since the last show monitor event-trace sbc ha command was entered.
Table 22 describes the significant fields shown in the display.
The following is sample output from the show monitor event-trace sbc ha parameters command . This command displays the number of event-trace messages in the trace file and whether stacktrace is disabled.
Router# show monitor event-trace sbc ha parametersTrace has 2048 entriesStacktrace is disabled by defaultRelated Commands
monitor event-trace sbc (EXEC)
Monitors and controls the event trace function for the SBC.
monitor event-trace sbc (global)
Configures event tracing for the SBC.
show mpls ip iprm counters
To display the number of occurrences of various Multiprotocol Label Switching (MPLS) IP Rewrite Manager (IPRM) events, use the show mpls ip iprm counters command in privileged EXEC mode.
show mpls ip iprm counters
Syntax Description
This command has no arguments or keywords.
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command reports the occurrences of IPRM events.
Examples
The command in the following example displays the events that the IPRM logs:
Router# show mpls ip iprm countersCEF Tree Changes Processed/Ignored: 91/12CEF Deletes Processed/Ignored: 12/2Label Discoveries: 74Rewrite Create Successes/Failures: 60/0Rewrite Gets/Deletes: 82/0Label Announcements: Info/Local/Path: 6/119/80Walks: Recursion Tree/CEF Full/CEF interface: 78/2/0Table 23 describes the significant fields shown in the display.
Related Commands
clear mpls ip iprm counters
Clears the IPRM counters.
show mpls ip iprm ldm
Displays information about the IP LDMs that have registered with the IPRM.
show mpls ip iprm ldm
To display information about the IP Label Distribution Modules (LDMs) that have registered with the IP Rewrite Manager (IPRM), use the show mpls ip iprm ldm command in privileged EXEC mode.
show mpls ip iprm ldm [table {all | table-id} | vrf vrf-name] [ipv4 | ipv6]
Cisco 10000 Series Routers
show mpls ip iprm ldm [table {all | table-id} | vrf vrf-name] [ipv4]
Syntax Description
Defaults
If you do not specify any keywords or parameters, the command displays the LDMs for the global routing table (the default).
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays the IP LDMs registered with IPRM.
Examples
The command in the following example displays the LDMs for the global routing tables. It shows that two LDMs (lcatm and ldp) are registered for the ipv4 global routing table, and that one LDM (bgp ipv6) is registered for the ipv6 global routing table.
Router# show mpls ip iprm ldmtable (glbl;ipv4); ldms: 2lcatm, ldptable (glbl;ipv6); ldms: 1bgp ipv6The command in the following example displays all of the LDMs registered with IPRM. The output shows the following:
•
•
•
Router# show mpls ip iprm ldm table alltable (glbl;ipv4); ldms: 2lcatm, ldptable (glbl;ipv6); ldms: 1bgp ipv6table (all-tbls;ipv4); ldms: 1bgp vpnv4The command in the following example displays the LDMs registered for the IPv6 routing tables.
Router# show mpls ip iprm ldm ipv6table (glbl;ipv6); ldms: 1bgp ipv6Cisco 10000 Series Examples Only
The command in the following example displays the LDMs for the global routing tables. It shows that one LDM (ldp) is registered for the ipv4 global routing table.
Router# show mpls ip iprm ldmtable (glbl;ipv4); ldms: 1ldpThe command in the following example displays all of the LDMs registered with IPRM. The output shows the following:
•
•
Router# show mpls ip iprm ldm table alltable (glbl;ipv4); ldms: 1ldptable (all-tbls;ipv4); ldms: 1bgp vpnv4Related Commands
show mpls ip iprm counters
Displays the number of occurrences of various IPRM events.
show platform redundancy bias
To display output for a specific standby slot SUP bootup delay setting, use the show platform redundancy bias command in privileged EXEC mode.
show platform redundancy bias
Syntax Description
This command has no keywords or arguments.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the show platform redundancy bias command to display the output for a specific platform redundancy bias command.
Examples
The following example shows how to verify the standby slot SUP bootup delay setting after configuring it for 50 seconds:
Router# configure terminalRouter(config)# platform redundancy bias 50Router(config)# endRouter#show platform redundancy biasPlatform redundancy bias is set at 50 seconds
Note
Related Commands
show redundancy
To display current or historical status and related information on planned or logged handovers, use the show redundancy command in user EXEC or privileged EXEC mode.
Privileged EXEC Mode
show redundancy [clients | counters | debug-log | handover | history | switchover history | states | inter-device]
User EXEC Mode
show redundancy {clients | counters | history | states | switchover}
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Cisco AS5800
Use this command from the router-shelf console to determine when failover is enabled. Use this command with the history keyword to log failover events.
Cisco AS5850
To use this command, the router must have two route-switch-controller (RSC) cards installed and must be connected to one of them.
Examples
The following example shows how to display information about the RF client:
Router# show redundancy clientsclientID = 0 clientSeq = 0 RF_INTERNAL_MSGclientID = 25 clientSeq = 130 CHKPT RFclientID = 5026 clientSeq = 130 CHKPT RFclientID = 5029 clientSeq = 135 Redundancy Mode RFclientID = 5006 clientSeq = 170 RFS clientclientID = 6 clientSeq = 180 Const OIR ClientclientID = 7 clientSeq = 190 PF ClientclientID = 5008 clientSeq = 190 PF ClientclientID = 28 clientSeq = 330 Const Startup ConfigclientID = 29 clientSeq = 340 Const IDPROM ClientclientID = 65000 clientSeq = 65000 RF_LAST_CLIENTThe output displays the following information:
•
•
•
The following example shows how to display information about the RF counters:
Router# show redundancy countersRedundancy Facility OMscomm link up = 0comm link down down = 0invalid client tx = 0null tx by client = 0tx failures = 0tx msg length invalid = 0client not rxing msgs = 0rx peer msg routing errors = 0null peer msg rx = 0errored peer msg rx = 0buffers tx = 0tx buffers unavailable = 0buffers rx = 0buffer release errors = 0duplicate client registers = 0failed to register client = 0Invalid client syncs = 0The following example shows information about the RF history:
Router# show redundancy history00:00:00 client added: RF_INTERNAL_MSG(0) seq=000:00:00 client added: RF_LAST_CLIENT(65000) seq=6500000:00:02 client added: Const Startup Config Sync Clien(28) seq=33000:00:02 client added: CHKPT RF(25) seq=13000:00:02 client added: PF Client(7) seq=19000:00:02 client added: Const OIR Client(6) seq=18000:00:02 client added: Const IDPROM Client(29) seq=34000:00:02 *my state = INITIALIZATION(2) *peer state = DISABLED(1)00:00:02 RF_PROG_INITIALIZATION(100) RF_INTERNAL_MSG(0) op=0 rc=1100:00:02 RF_PROG_INITIALIZATION(100) CHKPT RF(25) op=0 rc=1100:00:02 RF_PROG_INITIALIZATION(100) Const OIR Client(6) op=0 rc=1100:00:02 RF_PROG_INITIALIZATION(100) PF Client(7) op=0 rc=11The following example shows information about the RF state:
Router# show redundancy statesmy state = 13 -ACTIVEpeer state = 1 -DISABLEDMode = SimplexUnit = PrimaryUnit ID = 1Redundancy Mode (Operational) = Route Processor RedundancyRedundancy Mode (Configured) = Route Processor RedundancySplit Mode = DisabledManual Swact = Disabled Reason: Simplex modeCommunications = Down Reason: Simplex modeclient count = 11client_notification_TMR = 30000 millisecondskeep_alive TMR = 4000 millisecondskeep_alive count = 0keep_alive threshold = 7RF debug mask = 0x0If you enter the show redundancy states command with stateful switchover (SSO) configured, the Redundancy Mode (Operational) and the Redundancy Mode (Configured) fields display stateful switchover.
The following example shows how to display the switchover counts, the uptime since active, and the total system uptime:
Router> show redundancy switchoverSwitchovers this system has experienced : 1Uptime since this supervisor switched to active : 1 minuteTotal system uptime from reload : 2 hours, 47 minutesCisco AS5850 Example
The following is sample output from the show redundancy handover and show redundancy states commands on a Cisco AS5850:
Router# show redundancy handoverNo busyout period specifiedHandover pending at 23:00:00 PDT Wed May 9 2001Router# show redundancy statesmy state = 14 -ACTIVE_EXTRALOADpeer state = 4 -STANDBY COLDMode = DuplexUnit = Preferred PrimaryUnit ID = 6Redundancy Mode = Handover-split: If one RSC fails, the peer RSC will take over the feature boardsMaintenance Mode = DisabledManual Swact = Disabled Reason: Progression in progressCommunications = Upclient count = 3client_notification_TMR = 30000 millisecondskeep_alive TMR = 4000 millisecondskeep_alive count = 1keep_alive threshold = 7RF debug mask = 0x0Cisco AS5800 Example
The following is sample output from the show redundancy command on a Cisco AS5800:
Router# show redundancyDSC in slot 12:Hub is in 'active' state.Clock is in 'active' state.DSC in slot 13:Hub is in 'backup' state.Clock is in 'backup' state.Cisco AS5800 with History Example
The following is sample output from the show redundancy history command on a Cisco AS5800:
Router# show redundancy historyDSC Redundancy Status Change History:981130 18:56 Slot 12 DSC: Hub, becoming active - RS instruction981130 19:03 Slot 12 DSC: Hub, becoming active - D13 orderCisco AS5800 Router Shelves as Failover Pair Example
The following is sample output from two Cisco AS5800 router shelves configured as a failover pair. The active router shelf is initially RouterA. The show redundancy history and show redundancy commands have been issued. The show redundancy command shows that failover is enabled, shows the configured group number, and shows that this router shelf is the active one of the pair. Compare this output with that from the backup router shelf (RouterB) that follows.
Note
show redundancy history command is issued after failover has occurred.Log from the First Router (RouterA)
RouterA# show redundancy historyDSC Redundancy Status Change History:010215 18:17 Slot -1 DSC:Failover configured -> ACTIVE role by default.010215 18:18 Slot -1 DSC:Failover -> BACKUP role.010215 18:18 Slot 12 DSC:Failover -> ACTIVE role.010215 18:18 Slot 12 DSC:Hub, becoming active - arb timeoutRouterA# show redundancyfailover mode enabled, failover group = 32Currently ACTIVE role.DSC in slot 12:Hub is in 'active' state.Clock is in 'active' state.No connection to slot 13RouterA# reloadProceed with reload? [confirm] y*Feb 15 20:19:11.059:%SYS-5-RELOAD:Reload requestedSystem Bootstrap, Version xxxCopyright xxx by cisco Systems, Inc.C7200 processor with 131072 Kbytes of main memoryLog from the Second Router (RouterB)
RouterB# show redundancyfailover mode enabled, failover group = 32Currently BACKUP role.No connection to slot 12DSC in slot 13:Hub is in 'backup' state.Clock is in 'backup' state.*Feb 16 03:24:53.931:%DSC_REDUNDANCY-3-BICLINK:Switching to DSC 13*Feb 16 03:24:53.931:%DSC_REDUNDANCY-3-BICLINK:Failover:changing to active mode*Feb 16 03:24:54.931:%DIAL13-3-MSG:02:32:06:%DSC_REDUNDANCY-3-EVENT:Redundancy event:LINK_FAIL from other DSC*Feb 16 03:24:55.491:%OIR-6-INSCARD:Card inserted in slot 12, interfaces administratively shut down*Feb 16 03:24:58.455:%DIAL13-3-MSG:02:32:09:%DSC_REDUNDANCY-3-EVENT:Redundancy event:LINK_FAIL from other DSC*Feb 16 03:25:04.939:%DIAL13-0-MSG:RouterB# show redundancyfailover mode enabled, failover group = 32Currently ACTIVE role.No connection to slot 12DSC in slot 13:Hub is in 'active' state.Clock is in 'backup' state.RouterB# show redundancy historyDSC Redundancy Status Change History:010216 03:09 Slot -1 DSC:Failover configured -> BACKUP role.010216 03:24 Slot 13 DSC:Failover -> ACTIVE role.010216 03:24 Slot 13 DSC:Hub, becoming active - D12 linkfail010216 03:24 Slot 13 DSC:Hub, becoming active - D12 linkfail*Feb 16 03:26:14.079:%DSIPPF-5-DS_HELLO:DSIP Hello from shelf 47 slot 1 Succeeded*Feb 16 03:26:14.255:%DSIPPF-5-DS_HELLO:DSIP Hello from shelf 47 slot 3 Succeeded*Feb 16 03:26:14.979:%DSIPPF-5-DS_HELLO:DSIP Hello from shelf 47 slot 10 SucceededPrivileged EXEC Mode Example
The following is sample output generated by this command in privileged EXEC mode on router platforms that support no keywords for the privileged EXEC mode form of the command:
RouterB# show redundancyMWR1900 is the Active RouterPrevious States with most recent at bottomINITL_INITL Dec 31 19:00:00.000LISTN_INITL Feb 28 19:00:15.568LISTN_LISTN Feb 28 19:00:15.568SPEAK_LISTN Feb 28 19:00:18.568SPEAK_SPEAK Feb 28 19:00:18.568STDBY_SPEAK Mar 19 08:54:26.191ACTIV_SPEAK Mar 19 08:54:26.191ACTIV_STDBY Mar 19 08:54:26.191ACTIV_ACTIV Mar 19 08:54:26.191INITL_ACTIV Mar 19 08:56:22.700INITL_INITL Mar 19 08:56:22.700INITL_LISTN Mar 19 08:56:28.544LISTN_LISTN Mar 19 08:56:28.652LISTN_SPEAK Mar 19 08:56:31.544SPEAK_SPEAK Mar 19 08:56:31.652SPEAK_STDBY Mar 19 08:56:34.544SPEAK_ACTIV Mar 19 08:56:34.544STDBY_ACTIV Mar 19 08:56:34.652ACTIV_ACTIV Mar 19 08:56:34.652INITL_ACTIV Mar 19 10:20:41.455INITL_INITL Mar 19 10:20:41.455INITL_LISTN Mar 19 10:20:49.243LISTN_LISTN Mar 19 10:20:49.299LISTN_SPEAK Mar 19 10:20:52.244SPEAK_SPEAK Mar 19 10:20:52.300SPEAK_STDBY Mar 19 10:20:55.244STDBY_STDBY Mar 19 10:20:55.300ACTIV_STDBY Mar 19 10:21:01.692ACTIV_ACTIV Mar 19 10:21:01.692Related Commands
show tcp ha connections
To display connection-ID-to-TCP mapping data, use the show tcp ha connections command in privileged EXEC mode.
show tcp ha connections
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show tcp ha connections command is used to display connection-ID-to-TCP mapping data.
Examples
The following is sample output from the show tcp ha connections command:
Router# show tcp ha connectionsSSO enabled for 40 connectionsTCB Local Address Foreign Address (state) Conn Id71EACE60 10.0.56.1.179 10.0.56.3.58671 ESTAB 3771EA9320 10.0.53.1.179 10.0.53.3.58659 ESTAB 3471EA35F8 10.0.41.1.179 10.0.41.3.58650 ESTAB 2271A21FE0 10.0.39.1.179 10.0.39.3.58641 ESTAB 2071EAA6E0 10.0.54.1.179 10.0.54.3.58663 ESTAB 3571EA2238 10.0.40.1.179 10.0.40.3.58646 ESTAB 2171EABAA0 10.0.55.1.179 10.0.55.3.58667 ESTAB 3671EAE710 10.0.28.1.179 10.0.28.3.58676 ESTAB 971EA2728 10.0.50.1.179 10.0.50.3.58647 ESTAB 31720541D8 10.0.49.1.179 10.0.49.3.58642 ESTAB 3071EAA1F0 10.0.44.1.179 10.0.44.3.58662 ESTAB 252180B3A8 10.0.33.1.179 10.0.33.3.58657 ESTAB 1471EAB5B0 10.0.45.1.179 10.0.45.3.58666 ESTAB 2621809FE8 10.0.32.1.179 10.0.32.3.58653 ESTAB 1371EA8E30 10.0.43.1.179 10.0.43.3.58658 ESTAB 2471EAD350 10.0.27.1.179 10.0.27.3.58672 ESTAB 82180A9C8 10.0.52.1.179 10.0.52.3.58655 ESTAB 332180A4D8 10.0.42.1.179 10.0.42.3.58654 ESTAB 2371EABF90 10.0.26.1.179 10.0.26.3.58668 ESTAB 771EA3AE8 10.0.51.1.179 10.0.51.3.58651 ESTAB 32720546C8 10.0.59.1.179 10.0.59.3.58643 ESTAB 40Table 24 describes the significant fields shown in the display.
site-id
To assign a site identifier for Call Home, use the site-id command in call home configuration mode. To remove the site ID, use the no form of this command.
site-id alphanumeric
no site-id alphanumeric
Syntax Description
alphanumeric
Site identifier, using up to 200 alphanumeric characters. If you include spaces, you must enclose your entry in quotes (" ").
Command Default
No site ID is assigned.
Command Modes
Call home configuration (cfg-call-home)
Command History
Usage Guidelines
The site-id command is optional.
Examples
The following example configures "Site1ManhattanNY" as the customer ID without spaces:
Router(config)# call-homeRouter(cfg-call-home)# site-id Site1ManhattenNYThe following example configures "Site1 Manhattan NY" as the customer ID using spaces and required " " notation:
Router(config)# call-homeRouter(cfg-call-home)# site-id "Site1 Manhatten NY"Related Commands
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
show call-home
Displays Call Home configuration information.
snmp-server enable traps
To enable all Simple Network Management Protocol (SNMP) notification types that are available on your system, use the snmp-server enable traps command in global configuration mode. To disable all available SNMP notifications, use the no form of this command.
snmp-server enable traps [notification-type] [vrrp]
no snmp-server enable traps [notification-type] [vrrp]
Syntax Description
notification-type
(Optional) Type of notification (trap or inform) to enable or disable. If no type is specified, all notifications available on your device are enabled or disabled (if the no form is used). The notification type can be one of the following keywords:
alarms—Enables alarm filtering to limit the number of syslog messages generated. Alarms are generated for the severity configured as well as for the higher severity values.
•
–
–
–
–
•
•
•
Catalyst 6500 Series Switches
The following keywords are available under the dot1x keyword:
–
–
–
–
•
•
•
•
•
•
•
–
–
–
–
•
•
•
•
–
–
–
–
•
•
•
•
•
•
Note
vrrp
(Optional) Specifies the Virtual Router Redundancy Protocol (VRRP).
1 Supported on the Catalyst 6500 series switches.
Command Default
No notifications controlled by this command are sent.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
For additional notification types, see the Related Commands table for this command.
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. To specify whether the notifications should be sent as traps or informs, use the snmp-server host [traps | informs] command.
To configure the router to send these SNMP notifications, you must enter at least one snmp-server enable traps command. If you enter the command with no keywords, all notification types are enabled. If you enter the command with a keyword, only the notification type related to that keyword is enabled. To enable multiple types of notifications, you must issue a separate snmp-server enable traps command for each notification type and notification option.
Most notification types are disabled by default but some cannot be controlled with the snmp-server enable traps command.
The snmp-server enable traps command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send notifications, you must configure at least one snmp-server host command.
Catalyst 6500 Series Switches
The following MIBs were enhanced or supported in Cisco IOS Release 12.2(33)SXI and later releases on the Catalyst 6500 series switch:
•
•
•
•
•
Examples
The following example shows how to enable the router to send all traps to the host specified by the name myhost.cisco.com, using the community string defined as public:
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com publicThe following example shows how to configure an alarm severity threshold of 3:
Router# snmp-server enable traps alarms 3The following example shows how to enable the generation of a DSP operational state notification from from the command-line interface (CLI):
Router(config)# snmp-server enable traps dsp oper-stateThe following example shows how to enable the generation of a DSP operational state notification from a network management device:
setany -v2c 1.4.198.75 test cdspEnableOperStateNotification.0 -i 1cdspEnableOperStateNotification.0=true(1)The following example shows how to send no traps to any host. The Border Gateway Protocol (BGP) traps are enabled for all hosts, but the only traps enabled to be sent to a host are ISDN traps (which are not enabled in this example).
Router(config)# snmp-server enable traps bgpRouter(config)# snmp-server host user1 public isdnThe following example shows how to enable the router to send all inform requests to the host at the address myhost.cisco.com, using the community string defined as public:
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicThe following example shows how to send HSRP MIB traps to the host myhost.cisco.com using the community string public:
Router(config)# snmp-server enable traps hsrpRouter(config)# snmp-server host myhost.cisco.com traps version 2c public hsrpThe following example shows that VRRP will be used as the protocol to enable the traps:
Router(config)# snmp-server enable traps vrrpRouter(config)# snmp-server host myhost.cisco.com traps version 2c vrrpThe following example shows how to send IEEE 802.1X MIB traps to the host "myhost.example.com" using the community string defined as public:
Router(config)# snmp-server enable traps dot1xRouter(config)# snmp-server host myhost.example.com traps publicRelated Commands
street-address
To specify a street address where RMA equipment for Call Home can be sent, use the street-address command in call home configuration mode. To remove the street address, use the no form of this command.
street-address alphanumeric
no street-address alphanumeric
Syntax Description
alphanumeric
Street address, using up to 200 alphanumeric characters, including commas and spaces. If you include spaces, you must enclose your entry in quotes (" ").
Command Default
No street address is specified.
Command Modes
Call home configuration (cfg-call-home)
Command History
Usage Guidelines
The street-address command is optional to specify where return materials authorization (RMA) equipment for Call Home should be sent.
Examples
The following example configures "1234AnyStreet,AnyCity,AnyState,12345" as the street address without spaces:
Router(config)# call-homeRouter(cfg-call-home)# street-address 1234AnyStreet,AnyCity,AnyState,12345The following example configures "1234 Any Street, Any City, Any State, 12345" as the street address using commas and spaces with required " " notation:
Router(config)# call-homeRouter(cfg-call-home)# street-address "1234 Any Street, Any City, Any State, 12345"Related Commands
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
show call-home
Displays Call Home configuration information.
subscriber redundancy
To configure broadband subscriber session redundancy policy for synchronization between high availability (HA) active and standby processors, use the subscriber redundancy command in global configuration mode. To delete the policy, use the no form of this command.
subscriber redundancy [{bulk dynamic} limit cpu percentage delay seconds allow value] [delay seconds] [rate sessions seconds]
no subscriber redundancy
Syntax Description
Command Default
Subscriber redundancy policy applies default values.
Command Modes
Global configuration
Command History
12.2(31)SB2
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
Usage Guidelines
Cisco IOS HA functionality for broadband protocols and applications allows for stateful switchover (SSO) and in service software upgrade (ISSU) features that minimize planned and unplanned downtime and failures. HA uses the CCM to manage the capability to synchronize subscriber session initiation on the standby processor of a redundant processor system. Use the subscriber redundancy bulk command to create and modify redundancy policy used during bulk (startup) synchronization. Use the subscriber redundancy dynamic command to tune subscriber redundancy policies that throttle dynamic synchronization by monitoring CPU usage and synchronization rates. Use the subscriber redundancy delay command to establish session duration minimums for synchronization and manage dynamic synchronizing of short duration calls. Use the subscriber redundancy rate command to throttle the number of sessions to be synchronized per period.
Examples
The following example configures a 10 second delay when CPU usage exceeds 90 percent during bulk synchronization, after which 25 sessions will be synchronized before the CCM again checks CPU usage:
Router(config)# subscriber redundancy bulk limit cpu 90 delay 10 allow 25The following example configures a minimum session duration of 15 seconds before dynamic synchronization to the standby processor:
Router(config)# subscriber redundancy dynamic 15The following example configures 2000 sessions to be synchronized per second during bulk and dynamic synchronization:
Router(config)# subscriber redundancy rate 2000 1Related Commands
subscribe-to-alert-group
To subscribe a destination profile to an alert group, use the subscribe-to-alert-group command in destination profile configuration mode. To unsubscribe from an alert group or all alert groups, use the no form of this command.
subscribe-to-alert-group {all | configuration [periodic {daily hh:mm | monthly day hh:mm | weekly day hh:mm}] | diagnostic [severity level] | environment | inventory | syslog}
Syntax Description
Command Default
Destination profiles are not subscribed to alert groups by default.
Command Modes
Destination profile configuration
Command History
Usage Guidelines
The valid values for the level argument are as follows:
•
•
•
•
•
•
•
•
•
•
Selecting the lowest severity level includes all higher severity events. The types of severity levels are as follows:
•
•
•
•
•
•
•
•
•
•
Examples
The following examples shows how to subscribe to all alert groups:
subscribe-to-alert-group allsubscribe-to-alert-group all
To configure a destination profile to receive messages for all available alert groups for Call Home, use the subscribe-to-alert-group all command in call home profile configuration mode. To remove the subscription, use the no form of this command.
subscribe-to-alert-group all
no subscribe-to-alert-group all
Syntax Description
This command has no arguments or keywords.
Command Default
This command has no default behavior or values.
Command Modes
Call home profile configuration (cfg-call-home-profile)
Command History
Usage Guidelines
To enter call home profile configuration mode, use the profile (call home) command in call home configuration mode.
Note
Caution
Examples
The following example shows how to configure a profile to receive messages for all available alert groups:
Switch(config)# call-homeSwitch(cfg-call-home)# profile exampleSwitch(cfg-call-home-profile)# subscribe-to-alert-group allRelated Commands
subscribe-to-alert-group configuration
To configure a destination profile to receive messages for the Configuration alert group for Call Home, use the subscribe-to-alert-group configuration command in call home profile configuration mode. To remove the subscription, use the no form of this command.
subscribe-to-alert-group configuration [periodic {daily hh:mm | monthly day hh:mm | weekly day hh:mm}]
no subscribe-to-alert-group configuration [periodic {daily hh:mm | monthly day hh:mm | weekly day hh:mm}]
Syntax Description
Command Default
This command has no default behavior or values.
Command Modes
Call home profile configuration (cfg-call-home-profile)
Command History
Usage Guidelines
To enter call home profile configuration mode, use the profile (call home) command in call home configuration mode.
When you subscribe to the Configuration alert group without the periodic option, a notification occurs whenever a configuration change occurs. Otherwise, the notification occurs at the date and time specified.
Note
Examples
The following example shows how to configure a profile to receive a weekly periodic configuration alert notification every Tuesday at 9:16 PM (21:16):
Switch(config)# call-homeSwitch(cfg-call-home)# profile exampleSwitch(cfg-call-home-profile)# subscribe-to-alert-group configuration periodic weekly Tuesday 21:16Related Commands
subscribe-to-alert-group diagnostic
To configure a destination profile to receive messages for the Diagnostic alert group for Call Home, use the subscribe-to-alert-group diagnostic command in call home profile configuration mode. To remove the subscription, use the no form of this command.
subscribe-to-alert-group diagnostic [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}]
no subscribe-to-alert-group diagnostic [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}]
Syntax Description
Command Default
When you configure the subscribe-to-alert-group diagnostic command without specifying any severity, the default is normal severity.
Command Modes
Call home profile configuration (cfg-call-home-profile)
Command History
Usage Guidelines
To enter call home profile configuration mode, use the profile (call home) command in call home configuration mode.
When specifying severity, selecting a lower level severity includes notification of events with any higher severity.
Note
Examples
The following example shows how to configure a profile to receive diagnostic alerts for events with severity level 2 or higher:
Switch(config)# call-homeSwitch(cfg-call-home)# profile exampleSwitch(cfg-call-home-profile)# subscribe-to-alert-group diagnostic severity majorRelated Commands
subscribe-to-alert-group environment
To configure a destination profile to receive messages for the Environment alert group for Call Home, use the subscribe-to-alert-group environment command in call home profile configuration mode. To remove the subscription, use the no form of this command.
subscribe-to-alert-group environment [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}]
no subscribe-to-alert-group environment [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}]
Syntax Description
Command Default
When you configure the subscribe-to-alert-group environment command without specifying any severity, the default is normal severity.
Command Modes
Call home profile configuration (cfg-call-home-profile)
Command History
Usage Guidelines
To enter call home profile configuration mode, use the profile (call home) command in call home configuration mode.
When specifying severity, selecting a lower level severity includes notification of events with any higher severity.
Note
Examples
The following example shows how to configure a profile to receive environment alerts for events with severity level 2 or higher:
Switch(config)# call-homeSwitch(cfg-call-home)# profile exampleSwitch(cfg-call-home-profile)# subscribe-to-alert-group environment severity majorRelated Commands
subscribe-to-alert-group inventory
To configure a destination profile to receive messages for the Inventory alert group for Call Home, use the subscribe-to-alert-group inventory command in call home profile configuration mode. To remove the subscription, use the no form of this command.
subscribe-to-alert-group inventory [periodic {daily hh:mm | monthly day hh:mm | weekly day hh:mm}]
no subscribe-to-alert-group inventory [periodic {daily hh:mm | monthly day hh:mm | weekly day hh:mm}]
Syntax Description
Command Default
This command has no default behavior or values.
Command Modes
Call home profile configuration (cfg-call-home-profile)
Command History
Usage Guidelines
To enter call home profile configuration mode, use the profile (call home) command in call home configuration mode.
When you subscribe to the Inventory alert group without the periodic option, a notification occurs whenever a device is cold-booted, or when field-replaceable units (FRUs) are inserted or removed. Otherwise, the notification occurs at the date and time specified.
Note
Examples
The following example shows how to configure a profile to receive periodic configuration alert notifications every day at 9:12 PM (21:12):
Switch(config)# call-homeSwitch(cfg-call-home)# profile exampleSwitch(cfg-call-home-profile)# subscribe-to-alert-group inventory periodic daily 21:12Related Commands
subscribe-to-alert-group syslog
To configure a destination profile to receive messages for the Syslog alert group for Call Home, use the subscribe-to-alert-group syslog command in call home profile configuration mode. To remove the subscription, use the no form of this command.
subscribe-to-alert-group syslog [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning} [pattern match]]
no subscribe-to-alert-group syslog [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning} [pattern match]]
Syntax Description
Command Default
When you configure the subscribe-to-alert-group syslog command without specifying any severity, the default is normal severity.
Command Modes
Call home profile configuration (cfg-call-home-profile)
Command History
Usage Guidelines
To enter call home profile configuration mode, use the profile (call home) command in call home configuration mode.
You can configure the Syslog alert group to filter messages based on severity and also by specifying a pattern to be matched in the syslog message. If the pattern contains spaces, you must enclose it in quotes (" ").
When specifying severity, selecting a lower level severity includes notification of events with any higher severity.
Note
Examples
The following example shows how to configure a profile to receive syslog alerts for events with severity level 5 or higher, where the syslog message includes the string "UPDOWN":
Switch(config)# call-homeSwitch(cfg-call-home)# profile exampleSwitch(cfg-call-home-profile)# subscribe-to-alert-group syslog severity notification pattern "UPDOWN"Related Commands
timers nsf converge
To adjust the maximum time that a restarting router will wait for the end of table (EOT) notification from a nonstop forwarding (NSF)-capable or NSF-aware peer, use the timers nsf converge command in router configuration mode or address-family configuration mode. To return the signal timer to the default value, use the no form of this command.
timers nsf converge seconds
no timers nsf converge
Syntax Description
seconds
Time, in seconds, for which a restarting router will wait for an EOT notification. Valid range is 60 to 180 seconds. The default is 120 seconds.
Command Default
Enhanced Interior Gateway Routing Protocol (EIGRP) NSF awareness is enabled by default. EIGRP NSF awareness uses 120 seconds as the default value if this command is not configured or if the no form of this command is entered.
Command Modes
Router configuration (config-router)
Address-family configuration (config-router-af)Command History
Usage Guidelines
This command is entered only on an NSF-capable router. The converge timer is be used to wait for the last EOT update if all startup updates have not been received within the signal timer period. If an EIGRP process discovers no neighbor, or if it has received all startup updates from its neighbor within the signal timer period, the converge timer will not be started.
Examples
The following configuration example adjusts the converge timer on an NSF-capable router. In the example, the converge timer is set to 1 minute:
Router(config-router)# timers nsf converge 60The following EIGRP named configuration example adjusts the converge timer on an NSF-capable router. In the example, the converge timer is set to 1 minute:
Router(config)# router eigrp virtual-nameRouter(config-router)# address-family ipv4 autonomous-system 1Router(config-router-af)# timers nsf converge 60Related Commands
timers nsf route-hold
Note
To set the route-hold timer to determine how long a nonstop forwarding (NSF)-aware router that is running Enhanced Interior Gateway Routing Protocol (EIGRP) will hold routes for an inactive peer, use the timers nsf route-hold command in router configuration mode. To return the route-hold timer to the default value, use the no form of this command.
timers nsf route-hold seconds
no timers nsf route-hold
Syntax Description
seconds
Time, in seconds, for which EIGRP will hold routes for an inactive peer. Valid range is 20 to 300 seconds. The default is 240 seconds.
Command Default
EIGRP NSF awareness is enabled by default. The default value for the route-hold timer is 240 seconds.
Command Modes
Router configuration (config-router)
Command History
Usage Guidelines
The route-hold timer sets the maximum period of time that the NSF-aware router will hold known routes for an NSF-capable neighbor during a switchover operation or a well-known failure condition. The route-hold timer is configurable so that you can tune network performance and avoid undesired effects, such as "black holing" routes if the switchover operation takes too much time. When this timer expires, the NSF-aware router scans the topology table and discards any stale routes, allowing EIGRP peers to find alternate routes instead of waiting during a long switchover operation.
Examples
The following configuration example sets the route-hold timer value for an NSF-aware router. In the example, the route-hold timer is set to 2 minutes:
Router(config-router)# timers nsf route-hold 120Related Commands
timers nsf signal
To adjust the maximum time for the initial signal timer restart period, use the timers nsf signal command in router configuration mode or address-family configuration mode. To return the signal timer to the default value, use the no form of this command.
timers nsf signal seconds
no timers nsf signal
Syntax Description
seconds
Time, in seconds, for which Enhanced Interior Gateway Routing Protocol (EIGRP) will hold routes for an inactive peer. Valid range is 10 to 30 seconds. The default is 20 seconds.
Command Default
EIGRP NSF awareness is enabled by default. EIGRP NSF awareness uses 20 seconds as the default value if this command is not configured or if the no form of this command is entered.
Command Modes
Router configuration (config-router)
Address-family configuration (config-router-af)Command History
Usage Guidelines
This command is entered only on a nonstop forwarding (NSF)-capable router. The EIGRP process starts a signal timer when it is notified of a switchover event. Hello packets with the RS bit set are sent during this period.
The converge timer is used to wait for the last end of table (EOT) update if all startup updates have not been received within the signal timer period. If an EIGRP process discovers no neighbor, or if it has received all startup updates from its neighbor within the signal timer period, the converge timer will not be started.
Examples
The following configuration example adjusts the signal timer value on an NSF-capable router. In the example, the signal timer is set to 30 seconds:
Router(config-router)# timers nsf signal 30The following EIGRP named configuration example adjusts the signal timer value on an NSF-capable router. In the example, the signal timer is set to 30 seconds:
Router(config)# router eigrp virtual-nameRouter(config-router)# address-family ipv4 autonomous-system 1Router(config-router-af)# timers nsf signal 30Related Commands
vrf (call home)
To associate a virtual routing and forwarding (VRF) instance for Call Home email message transport, use the vrf command in call home configuration mode. To remove the VRF association, use the no form of this command.
vrf name
no vrf name
Syntax Description
Command Default
No VRF is associated for Call Home. On platforms other than the Cisco ASR 1000 Series Aggregation Services Routers, the global routing table is used when this command is not configured.
Command Modes
Call home configuration (cfg-call-home)
Command History
Usage Guidelines
This command is used to configure VRF support in the Call Home feature for email transport only.
To use this command, the VRF instance must be configured on the router.
On the Cisco ASR 1000 Series Aggregation Services Routers, this command is required to support email message transport and uses the Gigabit Ethernet management interface VRF (Mgmt-intf). Therefore, to correctly use the vrf (call-home) command on the Cisco ASR 1000 Series Router, the Gigabit Ethernet management interface VRF must be configured.
VRF configuration for Call Home on other platforms is optional. If no VRF is specified on those platforms, the global routing table is used.
Note
Examples
The following example shows how to associate the Mgmt-intf VRF for Call Home on the Cisco ASR 1000 Series Routers:
Router(config)# call-homeRouter(cfg-call-home)# vrf Mgmt-intfThe following example shows how to associate the VRF instance for Call Home on the Cisco 7200 Series Routers:
Router(config)# call-homeRouter(cfg-call-home)# vrf mgmt-vrfRelated Commands
vrrp sso
To enable Virtual Router Redundancy Protocol (VRRP) support of Stateful Switchover (SSO) if it has been disabled, use the vrrp sso command in global configuration mode. To disable VRRP support of SSO, use the no form of this command.
vrrp sso
no vrrp sso
Syntax Description
This command has no arguments or keywords.
Command Default
VRRP support of SSO is enabled by default.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use this command to enable VRRP support of SSO if it has been manually disabled by the no vrrp sso command.
Examples
The following example shows how to disable VRRP support of SSO:
Router(config)# no vrrp ssoRelated Commands
