FeedbackContents
A through L
active (call home)
To enable a destination profile for Call Home, use the active command in call home profile configuration mode. To disable a profile, use the no form of the command. To enable a user-defined profile, use the default form of the command, or to disable the CiscoTac-1 predefined profile, use the default form of the command.
Command Default
A user-defined destination profile is automatically enabled in Call Home after it is created. The predefined CiscoTac-1 profile is disabled.
Release
Modification
12.2(33)SXH
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS XE Release 12.2(33)SRC.
12.4(24)T
This command was integrated into Cisco IOS Release 12.4(24)T.
12.2(52)SG
This command was integrated into Cisco IOS Release 12.2(52)SG.
Cisco IOS XE Release 2.6
This command was integrated into Cisco IOS XE Release 2.6.
Usage Guidelines
A destination profile in Call Home is enabled when it is created. To disable a profile, use the no active command.
Examples
The following shows how to disable a destination profile that is automatically activated upon creation:
Switch(config)# call-home Switch(cfg-call-home)# profile cisco Switch(cfg-call-home-profile)# no activeThe following shows how to reactivate a destination profile that is disabled:
Switch(config)# call-home Switch(cfg-call-home)# profile cisco Switch(cfg-call-home-profile)# activeRelated Commands
Command
Description
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
profile (call home)
Configures a destination profile to specify how alert notifications are delivered for Call Home and enters call home profile configuration mode.
show call-home
Displays Call Home configuration information.
alert-group
To enable an alert group, use the alert-group command in call home configuration mode. To disable an alert group, use the no form of this command.
Release
Modification
12.2(33)SXH
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
12.4(24)T
This command was integrated into Cisco IOS Release 12.4(24)T.
12.2(52)SG
This command was integrated into Cisco IOS Release 12.2(52)SG.
Cisco IOS XE Release 2.6
This command was integrated into Cisco IOS XE Release 2.6.
Usage Guidelines
An alert group is a predefined subset of Call Home alerts supported on a platform. Different types of Call Home alerts are grouped into different alert groups depending on their type. The alert are as follows:
Note
The diagnostic alert group is not supported in Cisco IOS Release 12.4(24)T.Call Home trigger events are grouped into alert groups with each alert group assigned command-line interface commands to execute when an event occurs. These alert group trigger events and executed commands are platform-dependent. For more information, see the platform-specific configuration guides on the Smart Call Home site on Cisco.com at:
Examples
The following example shows how to enable a specific alert group:
Router(config)# call-home Router(cfg-call-home)# alert-group configurationThe following example shows how to enable all alert groups:
Router(cfg-call-home)# alert-group allThe following example shows how to disable a specific alert group:
Router(cfg-call-home)# no alert-group syslogThe following example shows how to disable all alert groups:
Router(cfg-call-home)# no alert-group allcall-home (global configuration)
To enter call home configuration mode for configuration of Call Home settings, use the call-home (global configuration) command in global configuration mode.
call-home
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Global configuration (config)
Release
Modification
12.2(33)SXH
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
12.4(24)T
This command was integrated into Cisco IOS Release 12.4(24)T.
12.2(52)SG
This command was integrated into Cisco IOS Release 12.2(52)SG.
Cisco IOS XE Release 2.6
This command was integrated into Cisco IOS XE Release 2.6.
Usage Guidelines
When you use the call-home command, you enter call home configuration mode and can configure settings for the Call Home feature. Some of the available call home configuration commands are shown in the Examples section.
Examples
The following example shows how to enter call home configuration mode and lists the commands that are available for Call Home configuration in Cisco IOS XE Release 2.6:
Router(config)# call-home Router(cfg-call-home)#? Call-home configuration commands: alert-group Enable or disable alert-group contact-email-addr System Contact's email address contract-id Contract identification for Cisco AutoNotify copy Copy a call-home profile customer-id Customer identification for Cisco AutoNotify default Set a command to its defaults exit Exit from call-home configuration mode mail-server Configure call-home mail_server no Negate a command or set its defaults phone-number Phone number of the contact person profile Enter call-home profile configuration mode rate-limit Configure call-home message rate-limit threshold rename Rename a call-home profile sender Call home msg's sender email addresses site-id Site identification for Cisco AutoNotify street-address Street address for RMA part shipments vrf VPN Routing/Forwarding instance nameRelated Commands
Command
Description
alert-group
Enables an alert group.
contact-email-addr
Assigns the e-mail address to be used for customer contact for Call Home.
contract-id
Assigns the customer’s contract identification number for Call Home.
copy profile
Creates a new destination profile with the same configuration settings as an existing profile.
customer-id (call home)
Assigns a customer identifier for Call Home.
mail-server
Configures an SMTP e-mail server address for Call Home.
phone-number
Assigns the phone number to be used for customer contact for Call Home.
profile (call home)
Configures a destination profile to specify how alert notifications are delivered for Call Home and enters call home profile configuration mode.
rate-limit (call home)
Configures the maximum number of messages per minute for Call Home.
rename profile
Changes the name of a destination profile.
sender
Assigns the e-mail addresses to be used in the from and reply-to fields in messages for Call Home.
service call-home
Enables Call Home.
show call-home
Displays Call Home configuration information.
site-id
Assigns a site identifier for Call Home.
street-address
Specifies a street address where RMA equipment for Call Home can be sent.
vrf (call home)
Associates a VRF instance for Call Home e-mail message transport.
call-home send alert-group
To manually send an alert group message for the Call Home feature, use the call-home send alert-group command in privileged EXEC mode.
Cisco Catalyst 6500 Series Switches, Cisco Catalyst 4500 Series Switches, Cisco 7600 Series Routers
call-home send alert-group { configuration | diagnostic module number | inventory } [ profile profile-name ]
Cisco ASR 1000 Series Aggregation Services Routers
call-home send alert-group { configuration | diagnostic slot number | inventory } [ profile profile-name ]
Syntax Description
configuration
Sends the configuration alert-group message to the destination profile.
diagnostic module number
(Cisco Catalyst 6500 series switches, Cisco Catalyst 4500 series switches, and Cisco 7600 series souters) Sends the diagnostic alert-group message to the destination profile for a specific module, slot/subslot, or slot/bay number. This option is not supported on the Cisco ASR 1000 Series Router.
inventory
Sends the inventory call-home message.
profile profile-name
(Optional) Specifies the name of the destination profile.
diagnostic slot number
(Cisco ASR 1000 Series Routers) Sends the diagnostic alert-group message to destination profiles for the specified slot, such as R0 for Route Processor slot 0.
Command Default
A Call Home alert group message is not manually sent.
Command Modes
Privileged EXEC (#)
Release
Modification
12.2(33)SXH
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
12.4(24)T
This command was integrated into Cisco IOS Release 12.4(24)T.
12.2(52)SG
This command was integrated into Cisco IOS Release 12.2(52)SG.
Cisco IOS XE Release 2.6
This command was integrated into Cisco IOS XE Release 2.6. The diagnostic slot R0 keyword option was added.
Usage Guidelines
When you enter the module number, you can enter the number of the module, the slot/subslot, or the slot/bay number.
Note
The Cisco ASR 1000 Series Router does not support the module keyword option. Instead, use the slot keyword.If you do not specify the profileprofile-name, the message is sent to all subscribed destination profiles. If you do specify a profile, the destination profile does not need to be subscribed to the alert group.
Only the configuration, diagnostic, and inventory alert groups can be manually sent.
Examples
The following example shows how to send the configuration alert-group message to the destination profile:
Router# call-home send alert-group configurationThe following example shows how to send the diagnostic alert-group message to all subscribed destination profiles that have lower severity subscription than the diagnostic result for a specific module, slot/subslot, or slot/bay number:
Router# call-home send alert-group diagnostic module 3/2The following example shows how to send the diagnostic alert-group message to the destination profile named CiscoTAC-1 for a specific module, slot/subslot, or slot/bay number:
Router# call-home send alert-group diagnostic module 3/2 profile CiscoTAC-1The following example shows how to send the diagnostic alert-group message to the destination profile named CiscoTAC-1 on RP slot 0 on a Cisco ASR 1000 Series Router:
Router# call-home send alert-group diagnostic slot R0 profile CiscoTAC-1The following example shows how to send an inventory call-home message to the destuination profile:
Router# call-home send alert-group inventoryRelated Commands
call-home (global configuration)
Enters call home configuration mode.
call-home test
Manually sends a Call Home test message to a destination profile.
service call-home
Enables Call Home.
show call-home
Displays Call Home configuration information.
configure issu set rollback timer
To configure the rollback timer value, use the configure issu set rollback timer command in global configuration mode.
configure issu set rollback timer seconds
Syntax Description
seconds
The rollback timer value, in seconds. The valid timer value range is from 0 to 7200 seconds (two hours). A value of 0 seconds disables the rollback timer.
Command Default
Rollback timer value is 45 minutes.
Command Modes
Global configuration (config)
Release
Modification
12.2(28)SB
This command was introduced.
12.2(31)SGA
This command was integrated into Cisco IOS Release 12.2(31)SGA.
12.2(33)SRB
Enhanced Fast Software Upgrade (eFSU) support was added on the Cisco 7600 series routers.
In Service Software Upgrade (ISSU) is not supported in Cisco IOS Release 12.2(33)SRB.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
Use the configure issue set rollback timer command to configure the rollback timer value. Note that you can enable this command only when the Route Processors (RPs) are in the init state.
Examples
The following example sets the rollback timer value to 3600 seconds, or 1 hour:
Router(config)# configure issu set rollback timer 3600Related Commands
Command
Description
issu acceptversion
Halts the rollback timer and ensures the new Cisco IOS software image is not automatically aborted during the ISSU process.
show issu rollback timer
Displays the current setting of the ISSU rollback timer.
contact-email-addr
To assign the e-mail address to be used for customer contact for Call Home, use the contact-email-addr command in call home configuration mode. To remove the assigned e-mail address, use the no form of this command.
contact-email-addr email-address
no contact-email-addr email-address
Syntax Description
email-address
Up to 200 characters in standard e-mail address format (contactname@domain) with no spaces.
Command Default
No e-mail address is assigned for customer contact.
Command Modes
Call home configuration (cfg-call-home)
Release
Modification
12.2(33)SXH
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
12.4(24)T
This command was integrated into Cisco IOS Release 12.4(24)T.
12.2(52)SG
This command was integrated into Cisco IOS Release 12.2(52)SG.
Cisco IOS XE Release 2.6
This command was integrated into Cisco IOS XE Release 2.6.
Usage Guidelines
To support the Call Home feature, the contact-email-addr command must be configured.
Examples
The following example configures the e-mail address “username@example.com” for customer contact:
Router(config)# call-home Router(cfg-call-home)# contact-email-addr username@example.comRelated Commands
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
show call-home
Displays call home configuration information.
contract-id
To assign the customer’s contract identification number for Call Home, use the contract-id command in call home configuration mode. To remove the contract ID, use the no form of this command.
contract-id alphanumeric
no contract-id alphanumeric
Syntax Description
alphanumeric
Contract number, using up to 64 alphanumeric characters. If you include spaces, you must enclose your entry in quotes (“ ”).
Command Default
No contract ID is assigned.
Command Modes
Call home configuration (cfg-call-home)
Release
Modification
12.2(33)SXH
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
12.4(24)T
This command was integrated into Cisco IOS Release 12.4(24)T.
12.2(52)SG
This command was integrated into Cisco IOS Release 12.2(52)SG.
Cisco IOS XE Release 2.6
This command was integrated into Cisco IOS XE Release 2.6.
Usage Guidelines
You must have a service contract for your Cisco device to use the Smart Call Home service. You can specify this contract number in the Call Home feature using the contract-id (call home) command.
Examples
The following example configures “Company1234” as the customer contract ID:
Router(config)# call-home Router(cfg-call-home)# contract-id Company1234Related Commands
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
show call-home
Displays call home configuration information.
copy profile
To create a new destination profile with the same configuration settings as an existing profile, use the copy profile command in call home configuration mode.
copy profile source-profile target-profile
Syntax Description
source-profile
Name of the existing destination profile that you want to copy.
target-profile
Name of the new destination profile that you want to create from the copy.
Command Default
No default behavior or values.
Command Modes
Call home configuration (cfg-call-home)
Release
Modification
12.2(33)SXH
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
12.4(24)T
This command was integrated into Cisco IOS Release 12.4(24)T.
12.2(52)SG
This command was integrated into Cisco IOS Release 12.2(52)SG.
Cisco IOS XE Release 2.6
This command was integrated into Cisco IOS XE Release 2.6.
Usage Guidelines
To simplify configuration of a new profile, use the copy profile command when an existing destination profile has configuration settings that you want to use as a basis for a new destination profile.
After you create the new profile, you can use the profile (call home) command to change any copied settings that need different values.
Examples
The following example creates a profile named “profile2” from an existing profile named “profile1”:
Router(config)# call-home Router(cfg-call-home)# copy profile profile1 profile2Related Commands
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
profile (call home)
Configures a destination profile to specify how alert notifications are delivered for Call Home and enters call home profile configuration mode.
show call-home
Displays call home configuration information.
customer-id (call home)
To assign a customer identifier for Call Home, use the customer-id command in call home configuration mode. To remove the customer ID, use the no form of this command.
customer-id alphanumeric
no customer-id alphanumeric
Syntax Description
alphanumeric
Customer identifier, using up to 256 alphanumeric characters. If you include spaces, you must enclose your entry in quotes (“ ”).
Command Default
No customer ID is assigned.
Command Modes
Call home configuration (cfg-call-home)
Release
Modification
12.2(33)SXH
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
12.4(24)T
This command was integrated into Cisco IOS Release 12.4(24)T.
12.2(52)SG
This command was integrated into Cisco IOS Release 12.2(52)SG.
Cisco IOS XE Release 2.6
This command was integrated into Cisco IOS XE Release 2.6.
Usage Guidelines
The customer-id command is optional.
Examples
The following example configures “Customer1234” as the customer ID:
Router(config)# call-home Router(cfg-call-home)# customer-id Customer1234Related Commands
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
show call-home
Displays call home configuration information.
debug atm ha-events
To debug ATM high-availability (HA) events on the networking device, use the debug atm ha-events command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
Release
Modification
12.0(22)S
This command was introduced on Cisco 7500, 10000, and 12000 series Internet routers.
12.2(18)S
This command was integrated into Cisco IOS Release 12.2(18)S on Cisco 7500 series routers.
12.2(20)S
Support was added for the Cisco 7304 router. The Cisco 7500 series router is not supported in Cisco IOS Release 12.2(20)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
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.
XE 3.6S
This command was modified. The detailed keyword was added.
debug frame-relay redundancy
To debug Frame Relay and Multilink Frame Relay redundancy on the networking device, use the debug frame-relay redundancy command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug frame-relay redundancy
no debug frame-relay redundancy
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Release
Modification
12.0(22)S
This command was introduced on the Cisco 7500 series and Cisco 10000 series Internet routers.
12.2(18)S
This command was integrated into Cisco IOS Release 12.2(18)S on Cisco 7500 series routers.
12.2(20)S
Support was added for the Cisco 7304 router. The Cisco 7500 series router is not supported in Cisco IOS Release 12.2(20)S.
12.0(28)S
SSO support was added to the Multilink Frame Relay feature on the Cisco 12000 series Internet router.
12.2(25)S
SSO support was added to the Multilink Frame Relay feature on the Cisco 12000 series Internet router.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
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
Use this command to debug Frame Relay synchronization problems. The debug frame-relay redundancy command logs synchronization events and errors.
Examples
The following example displays debug messages regarding Frame Relay redundancy on the networking device:
Router# debug frame-relay redundancyRelated Commands
Command
Description
frame-relay redundancy auto-sync lmi-sequence-numbers
Configures LMI synchronization parameters.
debug ip bgp vpnv4 nsf
To display the nonstop forwarding events for the VRF table-id synchronization subsystem between the active and standby Route Processors, use the debug ip bgp vpnv4 nsf command in privileged EXEC mode. To disable the display of these events, use the no form of this command.
debug ip bgp vpnv4 nsf
no debug ip bgp vpnv4 nsf
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging is not enabled.
Command Modes
Privileged EXEC
Release
Modification
12.2(25)S
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series router.
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.
Examples
The following example shows the command output on the active Route Processor:
Router# debug ip bgp vpnv4 nsf MPLS VPN NSF Processing debugging is on Router(config)# ip vrf vpn3 3d18h: vrf-nsf: vrf vpn3 tableid 2 send rpc OK Router(config-vrf)# no ip vrf vpn3 % IP addresses from all interfaces in VRF vpn3 have been removed 3d18h: vrf-nsf: rx vrf tableid delete complete msg, tid = 2, name = vpn3The following example shows the command output on the standby Route Processor:
Router# debug ip bgp vpnv4 nsf MPLS VPN NSF Processing debugging is on 00:05:21: vrf-nsf: rx vrf tableid rpc msg, tid = 2, name = vpn3 % IP addresses from all interfaces in VRF vpn3 have been removed 00:06:22: vrf-nsf: vrf vpn3 tableid 2 , delete complete, send OKRelated Commands
Command
Description
debug ip bgp vpnv4 checkpoint
Display the events for the VRF checkpointing system between the active and standby Route Processors.
debug isis nsf
To display information about the Intermediate System-to-Intermediate System (IS-IS) state during a Cisco nonstop forwarding (NSF) restart, use the debug isis nsf command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug isis nsf [detail]
no debug isis nsf [detail]
Syntax Description
detail
(Optional) Provides detailed debugging information.
Command Modes
Privileged EXEC
Release
Modification
12.0(22)S
This command was introduced.
12.2(18)S
This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(20)S
Support for the Cisco 7304 router was added.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
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
Use the debug isis nsf command to display basic information about the IS-IS state during an NSF restart. Use the debug isis nsf detail command to display additional IS-IS state detail during an NSF restart.
Examples
The following example displays IS-IS state information during an NSF restart:
router# debug isis nsf IS-IS NSF events debugging is onThe following example displays detailed IS-IS state information during an NSF restart:
router# debug isis nsf detail IS-IS NSF events (detailed) debugging is on router# Jan 24 20:04:54.090:%CLNS-5-ADJCHANGE:ISIS:Adjacency to gsr1 (GigabitEthernet2/0/0) Up, Standby adjacency Jan 24 20:04:54.090:ISIS-NSF:ADJ:000C.0000.0000 (Gi2/0/0), type 8/1, cnt 0/1, ht 10 (NEW) Jan 24 20:04:54.142:ISIS-NSF:Rcv LSP - L2 000B.0000.0000.00-00, seq 251, csum B0DC, ht 120, len 123 (local) Jan 24 20:04:55.510:ISIS-NSF:Rcv LSP - L1 000B.0000.0000.00-00, seq 23E, csum D20D, ht 120, len 100 (local) Jan 24 20:04:56.494:ISIS-NSF:ADJ:000C.0000.0000 (Gi2/0/0), type 8/0, cnt 0/1, ht 30 Jan 24 20:04:56.502:ISIS-NSF:Rcv LSP - L1 000B.0000.0000.01-00, seq 21C, csum 413, ht 120, len 58 (local) Jan 24 20:04:58.230:ISIS-NSF:Rcv LSP - L2 000C.0000.0000.00-00, seq 11A, csum E197, ht 1194, len 88 (Gi2/0/0) Jan 24 20:05:00.554:ISIS-NSF:Rcv LSP - L1 000B.0000.0000.00-00, seq 23F, csum 1527, ht 120, len 111 (local)Related Commands
Command
Description
nsf (IS-IS)
Configures NSF operations for IS-IS.
nsf interface wait
Specifies how long an NSF restart will wait for all interfaces with IS-IS adjacencies to come up before completing the restart.
nsf interval
Specifies the minimum time between NSF restart attempts.
nsf t3
Specifies the methodology used to determine how long IETF NSF will wait for the LSP database to synchronize before generating overloaded link state information for itself and flooding that information out to its neighbors.
show clns neighbors
Displays both ES and IS neighbors.
show isis nsf
Displays current state information regarding IS-IS NSF.
debug mpls traffic-eng ha sso
To display debugging output for Multiprotocol Label Switching (MPLS) traffic engineering high availability (HA) activities during the graceful switchover from an active Route Processor (RP) to a redundant standby RP, use the debug mpls traffic-eng ha sso command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng ha sso { auto-tunnel | errors | link-management { events | standby | recovery | checkpoint } | tunnel { events | standby | recovery } }
no debug mpls traffic-eng ha sso { auto-tunnel | errors | link-management { events | standby | recovery | checkpoint } | tunnel { events | standby | recovery } }
Syntax Description
auto-tunnel
Displays information about autotunnel activity during the MPLS traffic engineering stateful switchover (SSO) process.
errors
Displays errors encountered during the MPLS traffic engineering SSO process.
link-management
Displays information about link management activity during the MPLS traffic engineering SSO process.
events
Displays significant events that occur during the MPLS traffic engineering SSO process.
standby
Displays information about the standby behavior during the MPLS traffic engineering SSO process.
recovery
Displays information about recovery activity during the MPLS traffic engineering SSO process.
checkpoint
Display information about checkpointing activities during the MPLS traffic engineering SSO process. Checkpointing occurs when a message is sent and acknowledged.
tunnel
Displays information about tunnel activity during the MPLS traffic engineering SSO process.
Command Default
Debugging is disabled until you issue this command with one or more keywords.
Command Modes
Privileged EXEC (#)
Release
Modification
12.2(33)SRA
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Usage Guidelines
This command displays debugging output about the SSO process for MPLS traffic engineering tunnels, autotunnels, and link management systems. The SSO process occurs when the active router becomes unavailable and system control and routing protocol execution is transferred from the now inactive RP to the redundant standby RP, thus providing uninterrupted network services.
Examples
The following is sample output from the debug mpls traffic-eng ha sso command when you enabled debugging keywords to monitor the SSO process for tunnels and link management systems as the standby router becomes active:
Router# debug mpls traffic-eng ha sso link-management events MPLS traffic-eng SSO link management events debugging is on Router# debug mpls traffic-eng ha sso link-management recovery MPLS traffic-eng SSO link management recovery debugging is on Router# debug mpls traffic-eng ha sso link-management standby MPLS traffic-eng SSO link management standby behavior debugging is on Router# debug mpls traffic-eng ha sso link-management checkpoint MPLS traffic-eng SSO link management checkpointed info debugging is on Router# debug mpls traffic-eng ha sso tunnel standby MPLS traffic-eng SSO tunnel standby behavior debugging is on Router# debug mpls traffic-eng ha sso tunnel recovery MPLS traffic-eng SSO tunnel head recovery debugging is on Router# debug mpls traffic-eng ha sso tunnel events MPLS traffic-eng SSO events for tunnel heads debugging is on Router# debug mpls traffic-eng ha sso errors MPLS traffic-eng SSO errors debugging is on Router# show debug <----- This command displays the debugging that is enabled. MPLS TE: MPLS traffic-eng SSO link management events debugging is on MPLS traffic-eng SSO link management recovery debugging is on MPLS traffic-eng SSO link management standby behavior debugging is on MPLS traffic-eng SSO link management checkpointed info debugging is on MPLS traffic-eng SSO tunnel standby behavior debugging is on MPLS traffic-eng SSO tunnel head recovery debugging is on MPLS traffic-eng SSO events for tunnel heads debugging is on MPLS traffic-eng SSO errors debugging is on Router# Standby-Router#Following is the sample debugging output displayed during a successful SSO recovery on the standby router as it becomes active:
*May 12 20:03:15.303: RRR_HA_STATE: Told to wait for IGP convergence *May 12 20:03:14.807: %FABRIC-SP-STDBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active. *May 12 20:03:15.763: RRR_HA_REC: Attempting to recover last flooded info; protocol: OSPF, area: 0 *May 12 20:03:15.763: RRR_HA_REC: recovered ospf area 0 instance 0x48FFF240 *May 12 20:03:15.763: RRR_HA_REC: recovered system info *May 12 20:03:15.763: RRR_HA_REC: recovered link[0] info *May 12 20:03:15.763: RRR_HA: Recovered last flooded info for igp: OSPF, area: 0 *May 12 20:03:15.763: Pre announce tunnel 10 *May 12 20:03:15.763: TSPVIF_HA_EVENT: added Router_t10 to dest list *May 12 20:03:15.763: TSPVIF_HA_EVENT: Completed announcement of 1 tunnel heads to IGP *May 12 20:03:15.763: TSPVIF_HA_REC: Attempting to recover Tunnel10 after SSO *May 12 20:03:15.763: LSP-TUNNEL-REOPT: Tunnel10 [61] set to recover *May 12 20:03:15.763: TSPVIF_HA_REC: Recovered number hops = 5 *May 12 20:03:15.763: TSPVIF_HA_REC: recovered ospf area 0 instance 0x48FFF240 *May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 0: 10.0.3.1, Id: 10.0.0.3 Router Node (ospf) flag:0x0 *May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 1: 10.0.3.2, Id: 10.0.0.7 Router Node (ospf) flag:0x0 *May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 2: 10.0.6.1, Id: 10.0.0.7 Router Node (ospf) flag:0x0 *May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 3: 10.0.6.2, Id: 10.0.0.9 Router Node (ospf) flag:0x0 *May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 4: 10.0.0.9, Id: 10.0.0.9 Router Node (ospf) flag:0x0 *May 12 20:03:15.763: TSPVIF_HA_REC: signalling recovered setup for Tunnel10: popt 1 [61], weight 2 *May 12 20:03:15.891: TSPVIF_HA_REC: recovered Tu10 forwarding info needed by query *May 12 20:03:15.891: TSPVIF_HA_REC: output_idb: GigabitEthernet3/2, output_nhop: 180.0.3.2 Standby-Router# Router# *May 12 20:03:25.891: TSPVIF_HA_REC: recovered Tu10 forwarding info needed by query *May 12 20:03:25.891: TSPVIF_HA_REC: output_idb: GigabitEthernet3/2, output_nhop: 10.0.3.2 *May 12 20:03:35.891: TSPVIF_HA_REC: recovered Tu10 forwarding info needed by query *May 12 20:03:35.891: TSPVIF_HA_REC: output_idb: GigabitEthernet3/2, output_nhop: 10.0.3.2 *May 12 20:03:35.895: RRR_HA_STATE: IGP flood prevented during IGP recovery *May 12 20:03:38.079: LSP-TUNNEL-REOPT: Tunnel10 [61] received RESV for recovered setup *May 12 20:03:38.079: LSP-TUNNEL-REOPT: Tunnel10 [61] removed as recovery *May 12 20:03:38.079: TSPVIF_HA_EVENT: notifying RSVP HA to add lsp_info using key 10.0.0.3->10.0.0.9 Tu10 [61] 10.0.0.3 *May 12 20:03:38.079: TSPVIF_HA_EVENT: updated 7600-1_t10 state; action = add; result = success *May 12 20:03:38.079: TSPVIF_HA_EVENT: 7600-1_t10 fully recovered; rewrite refreshed *May 12 20:03:38.079: TSPVIF_HA_EVENT: notifying CBTS bundle about Router_t10 *May 12 20:03:38.079: TSPVIF_HA_EVENT: notifying RSVP HA to remove lsp_info using key 10.0.0.3->10.0.0.9 Tu10 [61] 10.0.0.3 *May 12 20:03:38.079: RRR_HA: Received notification recovery has ended. Notify IGP to flood. *May 12 20:03:38.079: TSPVIF_HA_EVENT: Received notification recovery has ended *May 12 20:03:38.079: TSPVIF_HA_STANDBY: prevent verifying setups; IGP has not converged *May 12 20:03:38.083: TSPVIF_HA_STANDBY: preventing new setups; reason: IGP recovering *May 12 20:03:38.083: TSPVIF_HA_STANDBY: prevent verifying setups; IGP has not converged *May 12 20:03:38.083: TSPVIF_HA_STANDBY: preventing new setups; reason: IGP recovering *May 12 20:03:38.083: RRR_HA_STATE: IGP flood prevented during IGP recovery 7600-1# *May 12 20:03:47.723: RRR_HA: Received notification that RIB table 0 has converged. *May 12 20:03:47.723: RRR_HA: Received notification all RIBs have converged. Notify IGP to flood. *May 12 20:03:47.723: RRR_HA_STATE: Told not to wait for IGP convergence *May 12 20:03:47.723: RRR_HA_INFO: update flooded system info; action = add; result = success *May 12 20:03:47.723: LM System key:: *May 12 20:03:47.723: Flooding Protocol: ospf *May 12 20:03:47.723: IGP Area ID: 0 *May 12 20:03:47.723: LM Flood Data:: *May 12 20:03:47.723: LSA Valid flags: 0x0 Node LSA flag: 0x0 *May 12 20:03:47.723: IGP System ID: 10.0.0.3 MPLS TE Router ID: 10.0.0.3 *May 12 20:03:47.723: Flooded links: 1 TLV length: 0 (bytes) *May 12 20:03:47.723: Fragment id: 0 *May 12 20:03:47.723: rrr_ha_lm_get_link_info_size: link size: 212 bytes; num TLVs: 0 *May 12 20:03:47.723: rrr_ha_sizeof_lm_link_info: link size: 212 bytes; num TLVs: 0 *May 12 20:03:47.723: RRR_HA_INFO: update flooded link[0] info; action = add; result = success *May 12 20:03:47.723: RRR HA Checkpoint Info Buffer:: *May 12 20:03:47.723: Info Handle: 0x490BB1C8 *May 12 20:03:47.723: Max Size: 212 *May 12 20:03:47.723: Info Size: 212 *May 12 20:03:47.723: Info Write Pointer: 0x490BB29C *May 12 20:03:47.723: LM Link key:: *May 12 20:03:47.723: Flooding Protocol: ospf IGP Area ID: 0 Link ID: 0 (GigabitEthernet3/2) *May 12 20:03:47.723: Ifnumber: 5 Link Valid Flags: 0x193B *May 12 20:03:47.723 Link Subnet Type: Broadcast *May 12 20:03:47.723: Local Intfc ID: 0 Neighbor Intf ID: 0 *May 12 20:03:47.723: Link IP Address: 10.0.3.1 *May 12 20:03:47.723: Neighbor IGP System ID: 10.0.3.2 Neighbor IP Address: 10.0.0.0 *May 12 20:03:47.723: IGP Metric: 1 TE Metric: 1 *May 12 20:03:47.723: Physical Bandwidth: 1000000 kbits/sec *May 12 20:03:47.723: Res. Global BW: 3000 kbits/sec *May 12 20:03:47.723: Res. Sub BW: 0 kbits/sec *May 12 20:03:47.723: Upstream:: Router# *May 12 20:03:47.723: Global Pool Sub Pool *May 12 20:03:47.723: ----------- ---------- *May 12 20:03:47.723: Reservable Bandwidth[0]: 0 0 kbits/sec *May 12 20:03:47.723: Reservable Bandwidth[1]: 0 0 kbits/sec *May 12 20:03:47.723: Reservable Bandwidth[2]: 0 0 kbits/sec *May 12 20:03:47.723: Reservable Bandwidth[3]: 0 0 kbits/sec *May 12 20:03:47.723: Reservable Bandwidth[4]: 0 0 kbits/sec *May 12 20:03:47.723: Reservable Bandwidth[5]: 0 0 kbits/sec *May 12 20:03:47.723: Reservable Bandwidth[6]: 0 0 kbits/sec *May 12 20:03:47.723: Reservable Bandwidth[7]: 0 0 kbits/sec *May 12 20:03:47.723: Downstream:: *May 12 20:03:47.723: Global Pool Sub Pool *May 12 20:03:47.723: ----------- ---------- *May 12 20:03:47.723: Reservable Bandwidth[0]: 3000 0 kbits/sec *May 12 20:03:47.723: Reservable Bandwidth[1]: 3000 0 kbits/sec *May 12 20:03:47.723: Reservable Bandwidth[2]: 3000 0 kbits/sec *May 12 20:03:47.723: Reservable Bandwidth[3]: 3000 0 kbits/sec *May 12 20:03:47.727: Reservable Bandwidth[4]: 3000 0 kbits/sec *May 12 20:03:47.727: Reservable Bandwidth[5]: 3000 0 kbits/sec *May 12 20:03:47.727: Reservable Bandwidth[6]: 3000 0 kbits/sec *May 12 20:03:47.727: Reservable Bandwidth[7]: 2900 0 kbits/sec *May 12 20:03:47.727: Affinity Bits: 0x0 *May 12 20:03:47.727: Protection Type: Capability 0, Working Priority 0 *May 12 20:03:47.727: Number of TLVs: 0 *May 12 20:03:47.727: RRR_HA: Updated flood state for ospf area 0 with 1 links); result = success Router#The following example shows how to turn off debugging:
Router# no debug mpls traffic-eng ha sso link-management events MPLS traffic-eng SSO link management events debugging is off Router# no debug mpls traffic-eng ha sso link-management recovery MPLS traffic-eng SSO link management recovery debugging is off Router# no debug mpls traffic-eng ha sso link-management standby MPLS traffic-eng SSO link management standby behavior debugging is off Router# no debug mpls traffic-eng ha sso link-management checkpoint MPLS traffic-eng SSO link management checkpointed info debugging is off Router# no debug mpls traffic-eng ha sso tunnel standby MPLS traffic-eng SSO tunnel standby behavior debugging is off Router# no debug mpls traffic-eng ha sso tunnel recovery MPLS traffic-eng SSO tunnel head recovery debugging is off Router# no debug mpls traffic-eng ha sso tunnel events MPLS traffic-eng SSO events for tunnel heads debugging is off Router# no debug mpls traffic-eng ha errors MPLS traffic-eng SSO errors debugging is offRelated Commands
Command
Description
debug ip rsvp high-availability
Displays debugging output for RSVP HA activities that improve the accessibility of network resources.
debug ip rsvp sso
Displays debugging output for RSVP activities during the graceful switchover from an active RP to a redundant RP.
destination (call home)
To configure the message destination parameters in a profile for Call Home, use the destination (call home) command in call home profile configuration mode. To remove the destination parameters, use the no form of this command.
destination { address { email address | http url } | message-size-limit size | preferred-msg-format { long-text | short-text | xml } | transport-method { email | http } }
no destination { address { email address | http url } | message-size-limit size | preferred-msg-format { long-text | short-text | xml } | transport-method { email | http } }
Syntax Description
address {email address | http url
Configures the address type and location to which Call Home messages are sent, where:
- email address --Email address, up to 200 characters.
- httpurl --URL, up to 200 characters.
message-size-limit size
Displays maximum Call Home message size for this profile, in bytes. The range is from 50 to 3145728. The default is 3145728.
preferred-msg-format {long-text | short-text | xml}
Specifies the message format for this profile, where:
- long-text--Format for use in standard e-mail providing a complete set of information in message.
- short-text--Format for use with text pagers providing a smaller set of information in the message, including host name, timestamp, error message trigger, and severity level.
- xml--Format that includes a complete set of information in the message, including XML tags. This is the default.
transport-method
Specifies the transport method for this profile, where:
- email--Messages are sent using e-mail. This is the default.
- http--Messages are sent using HTTP or HTTPS.
Command Default
No destination address type is configured. If you do not configure the destination (call home) command, the following defaults are configured for the profile:
- message-size-limit--3,145,728 bytes
- preferred-msg-format--XML
- transport-method--E-mail
Command Modes
Call home profile configuration (cfg-call-home-profile)
Release
Modification
12.2(33)SXH
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
12.4(24)T
This command was integrated into Cisco IOS Release 12.4(24)T.
12.2(52)SG
This command was integrated into Cisco IOS Release 12.2(52)SG.
Cisco IOS XE Release 2.6
This command was integrated into Cisco IOS XE Release 2.6.
Usage Guidelines
You can repeat the destination (call home) command in call home profile configuration mode to configure different message parameters for a profile. There is no default for the destination address form of the command, and an address must be configured for every profile.
For a user-defined profile, you can enable both e-mail and HTTP as accepted transport methods, by entering the destination transport-method email command and also the destination transport-method http command for the profile.
For the CiscoTAC-1 predefined profile, only one transport method can be enabled at a time. If you enable a second transport method, the existing method is automatically disabled. By default, e-mail can be used to send information to the Cisco Smart Call Home backend server, but if you want to use a secure HTTPS transport, you need to configure HTTP.
Examples
The following examples shows configuration of both transport methods for a user profile:
Router(config)# call-home Router(cfg-call-home)# profile example Router(cfg-call-home-profile)# destination transport-method email Router(cfg-call-home-profile)# destination transport-method httpThe following example shows a profile configuration for e-mail messaging using long-text format:
Router(config)# call-home Router(cfg-call-home)# profile example Router(cfg-call-home-profile)# destination address email username@example.com Router(cfg-call-home-profile)# destination preferred-msg-format long-textThe following example shows part of a Syslog alert notification (when subscribed to receive syslog alerts) using long-text format on a Cisco ASR 1006 router:
TimeStamp : 2009-12-03 12:26 GMT+05:00 Message Name : syslog Message Type : Call Home Message Group : reactive Severity Level : 2 Source ID : ASR1000 Device ID : ASR1006@C@FOX105101DH Customer ID : username@example.com Contract ID : 123456789 Site ID : example.com Server ID : ASR1006@C@FOX105101DH Event Description : *Dec 3 12:26:02.319 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console System Name : mcp-6ru-3 Contact Email : username@example.com Contact Phone : +12223334444 Street Address : 1234 Any Street Any City Any State 12345 Affected Chassis : ASR1006 Affected Chassis Serial Number : FOX105101DH Affected Chassis Part No : 68-2584-05 Affected Chassis Hardware Version : 2.1 Command Output Name : show logging Attachment Type : command output MIME Type : text/plain Command Output Text : Syslog logging: enabled (1 messages dropped, 29 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled) No Active Message Discriminator. No Inactive Message Discriminator. Console logging: disabled Monitor logging: level debugging, 0 messages logged, xml disabled, filtering disabled Buffer logging: level debugging, 112 messages logged, xml disabled, filtering disabled Exception Logging: size (4096 bytes) Count and timestamp logging messages: disabled Persistent logging: disabled No active filter modules. Trap logging: level informational, 104 message lines logged Log Buffer (1000000 bytes): *Dec 3 07:16:55.020: ASR1000-RP HA: RF status CID 1340, seq 93, status RF_STATUS_REDUNDANCY_MODE_CHANGE, op 0, state DISABLED, peer DISABLED *Dec 3 07:17:00.379: %ASR1000_MGMTVRF-6-CREATE_SUCCESS_INFO: Management vrf Mgmt-intf created with ID 4085, ipv4 table-id 0xFF5, ipv6 table-id 0x1E000001 *Dec 3 07:17:00.398: %NETCLK-5-NETCLK_MODE_CHANGE: Network clock source not available. The network clock has changed to freerun *Dec 3 07:17:00.544: %LINEPROTO-5-UPDOWN: Line protocol on Interface LI-Null0, changed state to up *Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface EOBC0, changed state to up *Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface Lsmpi0, changed state to up *Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface LIIN0, changed state to up *Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to down *Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface EOBC0, changed state to up *Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface Lsmpi0, changed state to up *Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface LIIN0, changed state to up *Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down *Dec 3 07:17:01.818: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded from the Shell Manager *Dec 3 07:16:30.926: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 2 is pre-release hardware *Dec 3 07:16:24.147: %HW_IDPROM_ENVMON-3-HW_IDPROM_CHECKSUM_INVALID: F1: cman_fp: The idprom contains an invalid checksum in a sensor entry. Expected: 63, calculated: fe *Dec 3 07:16:24.176: %CMFP-3-IDPROM_SENSOR: F1: cman_fp: One or more sensor fields from the idprom failed to parse properly because Success. *Dec 3 07:16:27.669: %CPPHA-7-START: F1: cpp_ha: CPP 0 preparing image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode *Dec 3 07:16:27.839: %CPPHA-7-START: F1: cpp_ha: CPP 0 startup init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode *Dec 3 07:16:28.659: %CPPHA-7-START: F0: cpp_ha: CPP 0 preparing image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode *Dec 3 07:16:28.799: %CPPHA-7-START: F0: cpp_ha: CPP 0 startup init image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode *Dec 3 07:16:32.557: %CPPHA-7-START: F1: cpp_ha: CPP 0 running init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode *Dec 3 07:16:32.812: %CPPHA-7-READY: F1: cpp_ha: CPP 0 loading and initialization complete *Dec 3 07:16:33.532: %CPPHA-7-START: F0: cpp_ha: CPP 0 running init image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode *Dec 3 07:16:33.786: %CPPHA-7-READY: F0: cpp_ha: CPP 0 loading and initialization complete . . .Examples
Example: Sample Message Using XML Format
The following example shows part of a Syslog alert notification using XML format on a Cisco ASR 1006 router when the destination preferred-msg-format xml command for a profile is configured:
<?xml version="1.0" encoding="UTF-8"?> <soap-env:Envelope xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope"> <soap-env:Header> <aml-session:Session xmlns:aml-session="http://www.cisco.com/2004/01/aml-session" soap-env:mustUnderstand="true" soap-env:role="http://www.w3.org/2003/05/soap-envelope/role/next"> <aml-session:To>http://tools.cisco.com/neddce/services/DDCEService</aml-session:To> <aml-session:Path> <aml-session:Via>http://www.cisco.com/appliance/uri</aml-session:Via> </aml-session:Path> <aml-session:From>http://www.cisco.com/appliance/uri</aml-session:From> <aml-session:MessageId>M0:FOX105101DH:CEC1E73E</aml-session:MessageId> </aml-session:Session> </soap-env:Header> <soap-env:Body> <aml-block:Block xmlns:aml-block="http://www.cisco.com/2004/01/aml-block"> <aml-block:Header> <aml-block:Type>http://www.cisco.com/2005/05/callhome/syslog</aml-block:Type> <aml-block:CreationDate>2009-12-03 12:29:02 GMT+05:00</aml-block:CreationDate> <aml-block:Builder> <aml-block:Name>ASR1000</aml-block:Name> <aml-block:Version>2.0</aml-block:Version> </aml-block:Builder> <aml-block:BlockGroup> <aml-block:GroupId>G1:FOX105101DH:CEC1E73E</aml-block:GroupId> <aml-block:Number>0</aml-block:Number> <aml-block:IsLast>true</aml-block:IsLast> <aml-block:IsPrimary>true</aml-block:IsPrimary> <aml-block:WaitForPrimary>false</aml-block:WaitForPrimary> </aml-block:BlockGroup> <aml-block:Severity>2</aml-block:Severity> </aml-block:Header> <aml-block:Content> <ch:CallHome xmlns:ch="http://www.cisco.com/2005/05/callhome" version="1.0"> <ch:EventTime>2009-12-03 12:29:01 GMT+05:00</ch:EventTime> <ch:MessageDescription>*Dec 3 12:29:01.017 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console</ch:MessageDescription> <ch:Event> <ch:Type>syslog</ch:Type> <ch:SubType></ch:SubType> <ch:Brand>Cisco Systems</ch:Brand> <ch:Series>ASR1000 Series Routers</ch:Series> </ch:Event> <ch:CustomerData> <ch:UserData> <ch:Email>username@example.com</ch:Email> </ch:UserData> <ch:ContractData> <ch:CustomerId>username@example.com</ch:CustomerId> <ch:SiteId>example.com</ch:SiteId> <ch:ContractId>123456789</ch:ContractId> <ch:DeviceId>ASR1006@C@FOX105101DH</ch:DeviceId> </ch:ContractData> <ch:SystemInfo> <ch:Name>mcp-6ru-3</ch:Name> <ch:Contact></ch:Contact> <ch:ContactEmail>username@example.com</ch:ContactEmail> <ch:ContactPhoneNumber>+12223334444</ch:ContactPhoneNumber> <ch:StreetAddress>1234 Any Street Any City Any State 12345</ch:StreetAddress> </ch:SystemInfo> <ch:CCOID></ch:CCOID> </ch:CustomerData> <ch:Device> <rme:Chassis xmlns:rme="http://www.cisco.com/rme/4.0"> <rme:Model>ASR1006</rme:Model> <rme:HardwareVersion>2.1</rme:HardwareVersion> <rme:SerialNumber>FOX105101DH</rme:SerialNumber> <rme:AdditionalInformation> <rme:AD name="PartNumber" value="68-2584-05" /> <rme:AD name="SoftwareVersion" value="" /> <rme:AD name="SystemObjectId" value="1.3.6.1.4.1.9.1.925" /> <rme:AD name="SystemDescription" value="Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Experimental Version 12.2(20091118:075558) [v122_33_xnf_asr_rls6_throttle-mcp_dev_rls6 102] Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled Wed 18-Nov-09 01:14 by " /> </rme:AdditionalInformation> </rme:Chassis> </ch:Device> </ch:CallHome> </aml-block:Content> <aml-block:Attachments> <aml-block:Attachment type="inline"> <aml-block:Name>show logging</aml-block:Name> <aml-block:Data encoding="plain"> <![CDATA[ Syslog logging: enabled (1 messages dropped, 29 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled) No Active Message Discriminator. No Inactive Message Discriminator. Console logging: disabled Monitor logging: level debugging, 0 messages logged, xml disabled, filtering disabled Buffer logging: level debugging, 114 messages logged, xml disabled, filtering disabled Exception Logging: size (4096 bytes) Count and timestamp logging messages: disabled Persistent logging: disabled No active filter modules. Trap logging: level informational, 106 message lines logged Log Buffer (1000000 bytes): *Dec 3 07:16:55.020: ASR1000-RP HA: RF status CID 1340, seq 93, status RF_STATUS_REDUNDANCY_MODE_CHANGE, op 0, state DISABLED, peer DISABLED *Dec 3 07:17:00.379: %ASR1000_MGMTVRF-6-CREATE_SUCCESS_INFO: Management vrf Mgmt-intf created with ID 4085, ipv4 table-id 0xFF5, ipv6 table-id 0x1E000001 *Dec 3 07:17:00.398: %NETCLK-5-NETCLK_MODE_CHANGE: Network clock source not available. The network clock has changed to freerun *Dec 3 07:17:00.544: %LINEPROTO-5-UPDOWN: Line protocol on Interface LI-Null0, changed state to up *Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface EOBC0, changed state to up *Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface Lsmpi0, changed state to up *Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface LIIN0, changed state to up *Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to down *Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface EOBC0, changed state to up *Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface Lsmpi0, changed state to up *Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface LIIN0, changed state to up *Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down *Dec 3 07:17:01.818: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded from the Shell Manager *Dec 3 07:16:30.926: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 2 is pre-release hardware *Dec 3 07:16:24.147: %HW_IDPROM_ENVMON-3-HW_IDPROM_CHECKSUM_INVALID: F1: cman_fp: The idprom contains an invalid checksum in a sensor entry. Expected: 63, calculated: fe *Dec 3 07:16:24.176: %CMFP-3-IDPROM_SENSOR: F1: cman_fp: One or more sensor fields from the idprom failed to parse properly because Success. *Dec 3 07:16:27.669: %CPPHA-7-START: F1: cpp_ha: CPP 0 preparing image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode *Dec 3 07:16:27.839: %CPPHA-7-START: F1: cpp_ha: CPP 0 startup init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode *Dec 3 07:16:28.659: %CPPHA-7-START: F0: cpp_ha: CPP 0 preparing image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode *Dec 3 07:16:28.799: %CPPHA-7-START: F0: cpp_ha: CPP 0 startup init image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode *Dec 3 07:16:32.557: %CPPHA-7-START: F1: cpp_ha: CPP 0 running init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode *Dec 3 07:16:32.812: %CPPHA-7-READY: F1: cpp_ha: CPP 0 loading and initialization complete . . .Related Commands
Command
Description
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
profile (call home)
Configures a destination profile to specify how alert notifications are delivered for Call Home and enters call home profile configuration mode.
issu changeversion
To perform a single-step complete In-Service Software Upgrade (ISSU) upgrade process cycle, use the issu changeversion command in privileged EXEC mode.
issu changeversion active-image
Syntax Description
active-image
The active image on the networking device.
Command Default
No upgrade has happened.
Command Modes
Privileged EXEC (#)
Release
Modification
12.2(33)SCD2
This command was introduced.
Usage Guidelines
The issu changeversion command starts a single-step complete upgrade process cycle. This command performs the logic for all four of the standard commands (issu loadversion, issu runversion, issu acceptversion, and issu commitversion) without any user intervention required to complete the next step.
The issu changeversion command allows the networking device to inform the system that the networking device is performing a complete upgrade cycle automatically, and allows the state transitions to move to the next step automatically.
Once the issu changeversion command is issued, the upgrade can be aborted using the issu abortversion command. An upgrade using the issu changeversion command may also be automatically aborted if the system detects any problems or an unhealthy system is determined during the upgrade.
The ISSU upgrade process consists of three states:
- Initialization (INIT) state
- Load version (LV) state
- Run version (RV) state
Each of these states is defined by a set of variables, which are primary version (PV), secondary version (SV), current version (CV), and the ISSU state (IS). The transition of all these states is accomplished using the issu changeversion command, which automatically performs these state transitions.
Examples
The following example starts a single-step complete upgrade process cycle using the disk0:ubr10k4-k9p6u2-mz.122-33.SCC2 image from slot 0:
Router# issu changeversion disk0:ubr10k4-k9p6u2-mz.122-33.SCC2Related Commands
Command
Description
issu abortversion
Cancels the ISSU upgrade or downgrade process in progress and restores the router to its state before the process had started.
issu acceptversion
Halts the rollback timer and ensures the new Cisco IOS software image is not automatically aborted during the ISSU process.
issu commitversion
Allows the new Cisco IOS software image to be loaded into the standby RP.
issu loadversion
Starts the ISSU process.
issu runversion
Forces a switchover from the active RP to the standby RP and causes the newly active RP to run the new image specified in the issu loadversion command.
show issu state
Displays the state and current version of the RPs during the ISSU process.
issu commitversion
To allow the new Cisco IOS software image to be loaded into the standby Route Processor (RP), use the issu commitversion command in user EXEC or privileged EXEC mode. This command is also available in diagnostic mode on the Cisco ASR 1000 Series Routers.
General Syntax
issu commitversion slot active-image
Cisco ASR 1000 Series Routers Syntax
issu commitversion [verbose]
Syntax Description
slot
The specified slot on the networking device. Refer to your hardware documentation for information on the number of slots on your networking device.
active-image
The new image to be loaded into the active networking device.
verbose
Displays verbose information, meaning all information that can be displayed on the console during the process will be displayed.
Command Default
This command is disabled by default.
Command Modes
User EXEC (>) Privileged EXEC (#) Diagnostic (diag)
Release
Modification
12.2(28)SB
This command was introduced.
12.2(31)SGA
This command was integrated into Cisco IOS Release 12.2(31)SGA.
12.2(33)SRB
Enhanced Fast Software Upgrade (eFSU) support was added on the Cisco 7600 series routers.
In Service Software Upgrade (ISSU) is not supported in Cisco IOS Release 12.2(33)SRB.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
Cisco IOS XE Release 2.1
This command was introduced on the ASR 1000 Series Routers, and introduced in diagnostic mode.
12.2(33)SXI
This command was integrated into Cisco IOS Release 12.2(33)SXI.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
The issu commitversion command verifies that the standby RP has the new Cisco IOS software image in its file system and that both RPs are in the run version (RV) state. If these conditions are met, then the following actions take place:
- The standby RP is reset and booted with the new version of Cisco IOS software.
- If both images are compatible, the standby RP moves into the stateful switchover (SSO) mode and is fully stateful for all clients and applications with which the standby RP is compatible.
- If both images are not compatible, the standby RP moves into Route Processor Redundancy Plus (RPR+) mode or RPR mode.
- If all conditions are correct, the RPs are moved into final state, which is the same as initial state.
Issuing the issu commitversion command completes the In Service Software Upgrade (ISSU) process. This process cannot be stopped or reverted to its original state without starting a new ISSU process.
Issuing the issu commitversion command at this stage is equivalent to entering both the issu acceptversion and the issu commitversion commands. Use the issu commitversion command if you do not intend to run in the current state for a period of time and are satisfied with the new software version.
On Cisco ASR 1000 series routers, the issu command set, including this command, can be used to upgrade individual subpackages and consolidated packages. The request platform software package command set can also be used for ISSU upgrades on this platform, and generally offer more options for each upgrade.
The issu runversion step can be bypassed on a Cisco ASR 1000 Series Router by using the redundancy force-switchover command to switchover between RPs and entering the issu commitversion command on the RP being upgraded. However, the issu runversion command is still available on this router and can still be used as part of the process for upgrading software using ISSU.
Previously, when ISSU was in a state other than Init, either the issu commitversion or issu runversion command had been issued, and the image being loaded or run was not present, the only way to return to the ISSU Init state was to clear the state manually and reload the router. Now, if either the issu commitversion or the issu runversion command is issued and the image cannot be located, the ISSU state is cleared automatically, and the standby RP is reloaded with the image that existed before the issu abortversion or the issu loadversion command was issued.
Examples
The following example shows how to reset the standby RP and reload it with the new Cisco IOS software version:
Router# issu commitversion a stby-disk0:c10k2-p11-mz.2.20040830The following example shows how the standby RP or Cisco IOS process is reset and reloaded with the new Cisco consolidated package on the Cisco ASR 1000 Series Router:
Router# issu commitversion --- Starting installation changes --- Cancelling rollback timer Saving image changes Finished installation changes Building configuration... [OK] SUCCESS: version committed: harddisk :ASR1000rp1-advipservicesk9.01.00.00.12-33.XN.binRelated Commands
Command
Description
issu abortversion
Cancels the ISSU upgrade or downgrade process in progress and restores the router to its state before the process had started.
issu acceptversion
Halts the rollback timer and ensures the new Cisco IOS software image is not automatically aborted during the ISSU process.
issu loadversion
Starts the ISSU process.
issu runversion
Forces a switchover of the active to the standby processor and causes the newly active processor to run the new image.
show issu state
Displays the state and current version of the RPs during the ISSU process.
issu loadversion
To start the In Service Software Upgrade (ISSU) process, use the issu loadversion command in user EXEC or privileged EXEC mode. This command is also available in diagnostic mode on the Cisco ASR 1000 series routers.
General Syntax
issu loadversion active-slot active-image standby-slot standby-image [force]
Cisco ASR 1000 Series Routers Syntax
issu loadversion rp [ 0 | 1 ] file file-URL [ bay bay-number ] [ slot slot-number ] [force] [verbose]
Syntax Description
active-slot
The active slot on the networking device.
active-image
The active image on the networking device.
rp [0 | 1]
Specifies the Route Processor (RP) on the Aggregation Services Router to install the Cisco IOS-XE image. Entering rp 0 selects the RP in slot 0, and entering rp 1 selects the RP in slot 1.
filefile-URL
Specifies the URL to the Cisco IOS-XE image file that will be used to perform this upgrade.
standby-slot
The standby slot on the networking device.
standby-image
The new image to be loaded into the standby networking device.
bay bay-number
Specifies the bay number within a SIP where a SPA is installed.
slot slot-number
Specifies the router slot number where a SIP is installed.
force
(Optional) Used to override the automatic rollback when the new Cisco IOS software version is detected to be incompatible, which is the case when as user intends to perform a fast software upgrade (FSU) in Route Processor Redundancy (RPR) mode.
verbose
Displays verbose information, meaning all information that can be displayed on the console during the process will be displayed.
Command Default
This command is disabled by default.
Command Modes
User EXEC (>) Privileged EXEC (#) Diagnostic (diag)
Release
Modification
12.2(28)SB
This command was introduced.
12.2(31)SGA
This command was integrated into Cisco IOS Release 12.2(31)SGA.
12.2(33)SRB
Enhanced Fast Software Upgrade (eFSU) support was added on the Cisco 7600 series routers.
ISSU is not supported in Cisco IOS Release 12.2(33)SRB.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
Cisco IOS XE Release 2.1
This command was introduced on the Cisco ASR 1000 Series Routers, and introduced in diagnostic mode.
12.2(33)SXI
This command was integrated into Cisco IOS Release 12.2(33)SXI.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
Enabling the issue loadversion command causes the standby RP to be reset and booted with the new Cisco IOS software image specified by the command. If both the active and standby RP images are ISSU-capable, ISSU-compatible, and have no configuration mismatches, then the standby RP moves into stateful switchover (SSO) mode, and both RPs move into the load version (LV) state.
It may take several seconds after the issu loadversion command is entered for Cisco IOS software to load into the standby RP and the standby RP to transition to SSO mode.
Cisco ASR 1000 Series Routers Usage Guidelines
On Cisco ASR 1000 Series Routers, the issu command set, including this command, can be used to upgrade individual sub-packages and consolidated packages. The request platform software package command set can also be used for ISSU upgrades on this platform, and generally offer more options for each upgrade.
The ISSU rollback timer starts at issu loadversion on the Cisco ASR 1000 Series Routers.
Previously, when ISSU was in a state other than Init, either the issu commitversion or issu runversion command had been issued, and the image being loaded or run was not present, the only way to return to the ISSU Init state was to clear the state manually and reload the router. Now, if either the issu commitversion or the issu runversion command is issued and the image cannot be located, the ISSU state is cleared automatically, and the standby RP is reloaded with the image that existed before the issu abortversion or the issu loadversion command was issued.
Examples
The following example shows how to initiate the ISSU process by loading the active image into the active RP slot and loading the standby image into the standby RP slot:
Router# issu loadversion a disk0:c10k2-p11-mz.2.20040830 b stby-disk0:c10k2-p11-mz.2.20040830The following example shows how to initiate an ISSU consolidated package upgrade on a Cisco ASR 1000 Series Router.
Router# issu loadversion rp 1 file stby-harddisk:ASR1000rp1-advipservicesk9.01.00.00.12-33.XN.bin --- Starting installation state synchronization --- Finished installation state synchronization --- Starting file path checking --- Finished file path checking --- Starting system installation readiness checking --- Finished system installation readiness checking --- Starting installation changes --- Setting up image to boot on next reset Starting automatic rollback timer Finished installation changes SUCCESS: Software will now load.Related Commands
Command
Description
issu abortversion
Cancels the ISSU upgrade or downgrade process in progress and restores the router to its state before the process had started.
issu acceptversion
Halts the rollback timer and ensures the new Cisco IOS software image is not automatically aborted during the ISSU process.
issu commitversion
Allows the new Cisco IOS software image to be loaded into the standby RP.
issu runversion
Forces a switchover of the active to the standby processor and causes the newly active processor to run the new image.
show issu state
Displays the state and current version of the RPs during the ISSU process.
issu runversion
To force a switchover from the active Route Processor (RP) to the standby RP and cause the newly active RP to run the new image specified in the issu loadversion command, use the issu runversion command in user EXEC or privileged EXEC mode. This command is also available in diagnostic mode on the Cisco ASR 1000 Series Routers.
General Syntax
issu runversion slot image
Cisco ASR 1000 Series Routers Syntax
issu runversion [verbose]
Syntax Description
slot
The specified slot on the networking device. Refer to your hardware documentation for information on the number of slots on your networking device.
image
The new image to be loaded into the standby RP.
verbose
Displays verbose information, meaning all information that can be displayed on the console during the process will be displayed.
Command Default
No default behavior or values.
Command Modes
User EXEC (>) Privileged EXEC (#) Diagnostic (diag)
Release
Modification
12.2(28)SB
This command was introduced.
12.2(31)SGA
This command was integrated into Cisco IOS Release 12.2(31)SGA.
12.2(33)SRB
Enhanced Fast Software Upgrade (eFSU) support was added on the Cisco 7600 series routers.
ISSU is not supported in Cisco IOS Release 12.2(33)SRB.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
Cisco IOS XE Release 2.1
This command was introduced on the Cisco ASR 1000 Series Routers, and introduced in diagnostic mode.
12.2(33)SXI
This command was integrated into Cisco IOS Release 12.2(33)SXI.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
When a user enables the issu runversion command, a switchover is performed, and the standby RP is booted with the old image version following the reset caused by the switchover. As soon as the standby RP moves into the standby state, the rollback timer is started.
On Cisco ASR 1000 Series Routers, the issu command set, including this command, can be used to upgrade individual sub-packages and consolidated packages. The request platform software package command set can also be used for ISSU upgrades on this platform, and generally offer more options for each upgrade.
The issu runversion step can be bypassed on a Cisco ASR 1000 Series Router by using the redundancy force-switchover command to switchover between RPs and entering the issu commitversion command on the RP being upgraded. However, issu runversion is still available on this router and can still be used as part of the process for upgrading software using ISSU.
Previously, when ISSU was in a state other than Init, either the issu commitversion or issu runversion command had been issued, and the image being loaded or run was not present, the only way to return to the ISSU Init state was to clear the state manually and reload the router. Now, if either the issu commitversion or the issu runversion command is issued and the image cannot be located, the ISSU state is cleared automatically, and the standby RP is reloaded with the image that existed before the issu abortversion or the issu loadversion command was issued.
Examples
In the following example, the issu runversion command is used to switch to the redundant RP with the new Cisco IOS software image:
Router# issu runversion b stby-disk0:c10k2-p11-mz.2.20040830In the following example, the issu runversion command is used to switch to the standby RP with the new Cisco IOS-XE consolidated package on the Cisco ASR 1000 Series Routers:
Router# issu runversion --- Starting installation state synchronization --- Finished installation state synchronization Initiating active RP failover SUCCESS: Standby RP will now become activeRelated Commands
Command
Description
issu abortversion
Cancels the ISSU upgrade or downgrade process in progress and restores the router to its state before the process had started.
issu acceptversion
Halts the rollback timer and ensures the new Cisco IOS software image is not automatically aborted during the ISSU process.
issu commitversion
Commits the new Cisco IOS software image in the file system of the standby RP and ensures that both the active and standby RPs are in the RV state.
issu loadversion
Starts the ISSU process.
show issu state
Displays the state and current version of the RPs during the ISSU process.
