Table Of Contents
Cisco IOS High Availability Command Reference
call-home (global configuration)
clear ip rsvp high-availability counters
configure issu set rollback timer
frame-relay redundancy auto-sync lmi-sequence-numbers
Cisco IOS High Availability Command Reference
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.
active
no active
default active
Command Default
A user-defined destination profile is automatically enabled in Call Home after it is created. The predefined CiscoTac-1 profile is disabled.
Command Modes
Call home profile configuration (cfg-call-home-profile)
Command History
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-homeSwitch(cfg-call-home)# profile ciscoSwitch(cfg-call-home-profile)# no activeThe following shows how to reactivate a destination profile that is disabled:
Switch(config)# call-homeSwitch(cfg-call-home)# profile ciscoSwitch(cfg-call-home-profile)# activeRelated Commands
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.
alert-group {all | configuration | diagnostic | environment | inventory | syslog}
no alert-group
Syntax Description
Command Default
All alert groups are enabled.
Command Modes
Call home configuration (cfg-call-home)
Command History
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:
•
Configuration
•
•
•
•
Note
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:
http://www.cisco.com/en/US/products/ps7334/serv_home.html
Examples
The following example shows how to enable a specific alert group:
Router(config)# call-homeRouter(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 allRelated Commands
call-home (global configuration)
Enters call home configuration mode.
show call-home
Displays call home configuration information.
call-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)
Command History
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-homeRouter(cfg-call-home)#?Call-home configuration commands:alert-group Enable or disable alert-groupcontact-email-addr System Contact's email addresscontract-id Contract identification for Cisco AutoNotifycopy Copy a call-home profilecustomer-id Customer identification for Cisco AutoNotifydefault Set a command to its defaultsexit Exit from call-home configuration modemail-server Configure call-home mail_serverno Negate a command or set its defaultsphone-number Phone number of the contact personprofile Enter call-home profile configuration moderate-limit Configure call-home message rate-limit thresholdrename Rename a call-home profilesender Call home msg's sender email addressessite-id Site identification for Cisco AutoNotifystreet-address Street address for RMA part shipmentsvrf VPN Routing/Forwarding instance nameRelated Commands
call-home request
To submit information about your system to Cisco for report and analysis information, use the call-home request command in privileged EXEC mode.
call-home request {bugs-list | command-reference | config-sanity | output-analysis "show-command" | product-advisory} {profile name [ccoid user-id] | ccoid user-id [profile name]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SXI
This command was introduced.
Cisco IOS XE Release 2.6
This command was integrated into Cisco IOS XE Release 2.6.
Usage Guidelines
When you use this command, an analysis report is sent by Cisco to a configured contact e-mail address. The recipient profile does not need to be enabled for the call-home request. The profile should specify the e-mail address where the transport gateway is configured so that the request message can be forwarded to the Cisco TAC and the user can receive the reply from the Smart Call Home service.
Based on the keyword option specified, the output of a predetermined set of commands as applicable to your system such as the show running-config all, show version, and show module (standalone) or show module switch all (VS system) commands, is sent to Cisco for analysis.
Examples
The following example shows a request for analysis of the show diagnostic result module all command to be sent to the contact information specified for the Call Home destination profile named "TG":
Router# call-home request output-analysis "show diagnostic result module all" profile TGThe following example shows a request for the known bugs list to be sent to the Call Home destination profile named "CiscoTAC-1" and a registered CCO userid "myuserid":
Router# call-home request bugs-list profile CiscoTAC-1 ccoid myuseridRelated Commands
call-home send
To execute an EXEC-level CLI command and send the command output for Call Home using e-mail, use the call-home send command in privileged EXEC mode.
call-home send "exec-command" {email email-addr [tac-service-request request-number] | tac-service-request request-number [email email-addr]}
Cisco 7600 Series Routers in Cisco IOS Release 12.2(33)SRC
call-home send "exec-command" {email email-addr [service-number SR] | service-number SR}
Syntax Description
Command Default
This command has no default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command causes the specified CLI command to be executed on the system. The command must be enclosed in quotes (" "), and can be any EXEC-level command, including commands for all modules.
The command output is then sent by e-mail to the specified e-mail address. If no e-mail address is specified, the command output is sent to the Cisco TAC at attach@cisco.com. The e-mail will be sent in long text format with the service number, if specified, in the subject line.
Examples
This example shows how to send a CLI command and have the command output e-mailed:
Router# call-home send "show diagnostic result module all" email support@example.comRelated Commands
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
Command Default
A Call Home alert group message is not manually sent.
Command Modes
Privileged EXEC (#)
Command History
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
If you do not specify the profile profile-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 test
To manually send a Call Home test message to a destination profile, use the call-home test command in privileged EXEC mode.
call-home test ["test-message"] profile profile-name
Syntax Description
"test-message"
(Optional) Test message text enclosed in required quotation marks (" ").
profile profile-name
Specifies the name of the destination profile.
Command Default
This command has no default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command sends a test message to the specified destination profile. If you enter test message text, you must enclose the text in quotes (" ") if it contains spaces. If you do not enter a message, a default message is sent.
Examples
The following example shows how to manually send a Call Home test message with the text "test of the day" to the profile named CiscoTAC-1:
Router# call-home test "test of the day" profile CiscoTAC-1Related Commands
clear ip rsvp high-availability counters
To clear (set to zero) the Resource Reservation Protocol (RSVP) traffic engineering (TE) high availability (HA) counters that are being maintained by a Route Processor (RP), use the clear ip rsvp high-availability counters command in privileged EXEC mode.
clear ip rsvp high-availability counters
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear ip rsvp high-availability counters command to clear (set to zero) the HA counters, which include state, ISSU, resource failures, and historical information.
Examples
The following example clears all the HA information currently being maintained by the RP:
Router# clear ip rsvp high-availability counters
Related Commands
show ip rsvp high-availability counters
Displays the RSVP TE HA counters that are being maintained by an RP.
clear issu state
To clear the state and current version of the Route Processors (RPs) during the In Service Software Upgrade (ISSU) process, use the clear issu state command in user EXEC or privileged EXEC mode.
clear issu state
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
This command clears the state and current version of RPs during the ISSU process.
Examples
The following example clears state and current version of the RPs during the ISSU process:
Router# clear issu stateconfigure 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)
Command History
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
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)
Command History
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-homeRouter(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)
Command History
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-homeRouter(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)
Command History
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-homeRouter(cfg-call-home)# copy profile profile1 profile2Related Commands
crashdump-timeout
To set the longest time that the newly active Route Switch Processor (RSP) will wait before reloading the formerly active RSP, use the crashdump-timeout command in redundancy mode. To reset the default time that the newly active RSP will wait before reloading the formerly active RSP, use the no form of this command.
crashdump-timeout [mm | hh:mm]
no crashdump-timeout
Syntax Description
Command Default
The default timeout for this command is 5 minutes.
Command Modes
Redundancy
Command History
Usage Guidelines
Use this command to specify the length of time that the newly active RSP will wait before reloading the previously active RSP. This time can be important when considering how long to wait for a core dump to complete before reloading the RSP.
In networking devices that support stateful switchover (SSO), the newly active primary processor runs the core dump operation after the switchover has taken place. Following the switchover, the newly active RSP will wait for a period of time for the core dump to complete before attempting to reload the formerly active RSP.
In the event that the core dump does not complete within the time period provided, the standby RSP is reset and reloaded based on the crashdump timeout command setting, regardless of whether it is still performing a core dump.
Note
Examples
The following example sets the time before the previously active RSP is reloaded to 10 minutes:
Router(config-r)# crashdump-timeout 10customer-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)
Command History
Usage Guidelines
The customer-id command is optional.
Examples
The following example configures "Customer1234" as the customer ID:
Router(config)# call-homeRouter(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.
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
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:
•
•
•
Command Modes
Call home profile configuration (cfg-call-home-profile)
Command History
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-homeRouter(cfg-call-home)# profile exampleRouter(cfg-call-home-profile)# destination transport-method emailRouter(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-homeRouter(cfg-call-home)# profile exampleRouter(cfg-call-home-profile)# destination address email username@example.comRouter(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:00Message Name : syslogMessage Type : Call HomeMessage Group : reactiveSeverity Level : 2Source ID : ASR1000Device ID : ASR1006@C@FOX105101DHCustomer ID : username@example.comContract ID : 123456789Site ID : example.comServer ID : ASR1006@C@FOX105101DHEvent Description : *Dec 3 12:26:02.319 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by consoleSystem Name : mcp-6ru-3Contact Email : username@example.comContact Phone : +12223334444Street Address : 1234 Any Street Any City Any State 12345Affected Chassis : ASR1006Affected Chassis Serial Number : FOX105101DHAffected Chassis Part No : 68-2584-05Affected Chassis Hardware Version : 2.1Command Output Name : show loggingAttachment Type : command outputMIME Type : text/plainCommand 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: disabledMonitor logging: level debugging, 0 messages logged, xml disabled,filtering disabledBuffer logging: level debugging, 112 messages logged, xml disabled,filtering disabledException Logging: size (4096 bytes)Count and timestamp logging messages: disabledPersistent logging: disabledNo active filter modules.Trap logging: level informational, 104 message lines loggedLog 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...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: disabledMonitor logging: level debugging, 0 messages logged, xml disabled,filtering disabledBuffer logging: level debugging, 114 messages logged, xml disabled,filtering disabledException Logging: size (4096 bytes)Count and timestamp logging messages: disabledPersistent logging: disabledNo active filter modules.Trap logging: level informational, 106 message lines loggedLog 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
frame-relay redundancy auto-sync lmi-sequence-numbers
To configure automatic synchronization of Frame Relay Local Management Interface (LMI) sequence numbers, use the frame-relay redundancy auto-sync lmi-sequence-numbers command in global configuration mode. To remove this command from the configuration file and restore the system to its default condition with respect to this command, use the no form of this command.
frame-relay redundancy auto-sync lmi-sequence-numbers
no frame-relay redundancy auto-sync lmi-sequence-numbers
Syntax Description
This command has no arguments or keywords.
Command Default
Automatic synchronization of Frame Relay LMI sequence numbers is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
Enabling the frame-relay redundancy auto-sync lmi-sequence-numbers command improves the chances of a clean switchover on Frame Relay DTE interfaces when the peer Frame Relay DCE is intolerant of LMI errors. Use this command to configure LMI if the DCE fails the line protocol after fewer than three LMI errors and if changing the DCE configuration is neither possible nor practical.
Examples
The following example enables synchronization of LMI DTE sequence numbers on a router that is running Frame Relay:
frame-relay redundancy auto-sync lmi-sequence-numbersRelated Commands
debug frame-relay redundancy
Debugs Frame Relay redundancy on the networking device.
issu abortversion
To cancel the In Service Software Upgrade (ISSU) upgrade or downgrade process in progress and restore the router to its state before the process had started, use the issu abortversion 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 abortversion slot image
Cisco ASR 1000 Series Router Syntax
issu abortversion [verbose]
Syntax Description
Command Default
This command is disabled by default.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Diagnostic (diag)Command History
Usage Guidelines
The issu abortversion command allows the user to stop the ISSU process at any time before the user commits to completing the process by issuing the issu commitversion command. Before any action is taken, a check is performed to ensure that both RPs are either in the run version (RV) or load version (LV) state.
When the issu abortversion command is issued before the issu runversion command, the standby RP is reset and reloaded. When the issu abortversion command is issued after the issu runversion command, the network switches to the former Cisco IOS software version.
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.
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 abortversion command resets and reloads the standby RP:
Router# issu abortversion bootdisk:c10k2-p11-mz.2.20040830In the following example, the issu abortversion command is entered to abort an ISSU upgrade of a consolidated package on a Cisco ASR 1000 Series Router:
Router# issu abortversion--- Starting installation state synchronization ---Finished installation state synchronization--- Starting installation changes ---Cancelling rollback timerFinished installation changesSUCCESS: Target RP will now reloadRelated Commands
issu acceptversion
To halt the rollback timer and ensure the new Cisco IOS software image is not automatically aborted during the In Service Software Upgrade (ISSU) process, use the issu acceptversion 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 acceptversion {active slot-number | active slot-name slot-name}
Cisco ASR 1000 Series Routers syntax
issu acceptversion [verbose]
Syntax Description
Command Default
45 minutes from the time the issu runversion command is issued to the time the issu acceptversion is issued.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Diagnostic (diag)Command History
Usage Guidelines
Use the issu acceptversion command to ensure that the active Route Processor (RP) is running the new image, that the standby RP is running the old image, and that both RPs are in the run version (RV) state. If the issu acceptversion command is not issued within 45 minutes from the time the issu runversion command is issued, the new active RP is assumed to be unreachable, and the entire ISSU process is automatically rolled back to the previous version of the software. The rollback timer starts immediately after the user issues the issu runversion command.
If the rollback timer is set for a short period of time, such as 1 minute, and the standby RP is not yet in a hot standby state, you then have 15 1-minute extensions during which the router will wait for the standby state to become hot standby state. However, if the standby state becomes hot standby state within the 15-minute extension, the router will abort the ISSU process because the 1-minute rollback timer has expired. Therefore, it is not recommended to set the rollback timer shorter than the time required for the standby state to become hot standby state.
If the rollback timer is set to a long period of time, such as the default of 45 minutes, and the standby RP goes into the hot standby state in 7 minutes, you have 38 minutes (45 minus 7) to roll back if necessary.
Use the configure issu set rollback timer to configure the 45-minute default value on the rollback timer.
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.
Examples
The following example shows how to halt the rollback timer and allow the ISSU process to continue:
Router# issu acceptversion b disk0:c10k2-p11-mz.2.20040830The following example shows how to halt the rollback timer and allow the ISSU process to continue on a Cisco ASR 1000 Series Router:
Router# issu acceptversionRelated Commands
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
Command Default
No upgrade has happened.
Command Modes
Privileged EXEC (#)
Command History
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:
1.
2.
3.
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
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
Command Default
This command is disabled by default.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Diagnostic (diag)Command History
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:
•
•
•
•
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 timerSaving image changesFinished installation changesBuilding configuration...[OK]SUCCESS: version committed: harddisk:ASR1000rp1-advipservicesk9.01.00.00.12-33.XN.binRelated Commands
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
Command Default
This command is disabled by default.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Diagnostic (diag)Command History
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 resetStarting automatic rollback timerFinished installation changesSUCCESS: Software will now load.Related Commands
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
Command Default
No default behavior or values.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Diagnostic (diag)Command History
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 synchronizationInitiating active RP failoverSUCCESS: Standby RP will now become activeRelated Commands
issu set rollback-timer
To set the rollback timer for the software image to revert to the previous software image after an unfinished or unsuccessful in-service software upgrade (ISSU), use the issu set rollback-timer command in global configuration mode. To disable the timer, use the no form of this command.
issu set rollback-timer {seconds | hh:mm:ss}
no issu set rollback-timer
Syntax Description
Command Default
The default rollback timer value is 2700 seconds (45 minutes).
Command Modes
Global configuration ((config)#)
Command History
Usage Guidelines
If the rollback timer expires during an ISSU, the software image reverts to the previous software image. To stop the timer, you must either accept or commit the new software image.
The timer duration can be set with one number (seconds), indicating the number of seconds, or as hours, minutes, and seconds with a colon as the delimiter (hh:mm:ss). The range is 0 to 7200 seconds (2 hours); the default is 2700 seconds (45 minutes). A setting of 0 disables the rollback timer.
Examples
This example shows how to set the rollback timer to 3600 seconds (one hour) using both command formats:
Router(config)# issu set rollback-timer 3600% Rollback timer value set to [ 3600 ] secondsRouter(config)# issu set rollback-timer 01:00:00% Rollback timer value set to [ 3600 ] secondsThe following examples shows how to disable the rollback timer:
Router(config) no issu set rollback-timerRelated Commands
show issu
Displays eFSU information.
show issu rollback-timer
Displays eFSU rollback timer value.
