Table Of Contents
mdr download reserve memory image
monitor event-trace sbc (EXEC)
monitor event-trace sbc (global)
service image-version compatibility
mail-server
To configure an SMTP e-mail server address for Call Home, use the mail-server command in call home configuration mode. To remove one or all mail servers, use the no form of this command.
mail-server {ipv4-address | name} priority number
no mail-server {[ipv4-address | name [priority number]] | all}
Syntax Description
Command Default
No e-mail server is configured.
Command Modes
Call home configuration (cfg-call-home)
Command History
Usage Guidelines
To support the e-mail transport method in the Call Home feature, you must configure at least one Simple Mail Transfer Protocol (SMTP) mail server using the mail-server command.
You can specify up to four backup e-mail servers, for a maximum of five total mail-server definitions.
Consider the following guidelines when configuring the mail server:
•
Only IPv4 addressing is supported.
•
•
Examples
The following example configures two mail servers, where the mail server at "smtp.example.com" serves as the primary (with lower priority number than the second mail server), while the mail server at 192.168.0.1 serves as a backup:
Router(config)# call-homeRouter(cfg-call-home)# mail-server smtp.example.com priority 1Router(cfg-call-home)# mail-server 192.168.0.1 priority 2The following example shows how to remove configuration of both configured mail servers:
Router(cfg-call-home)# no mail-server allRelated Commands
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
show call-home
Displays Call Home configuration information.
mdr download reserve memory image
To reserve memory for preloading new software onto line cards that support enhanced Fast Software Upgrade (eFSU), use the mdr download reserve memory image command in privileged EXEC mode. To keep the router from reserving memory on line cards, use the no form of the command.
mdr download reserve memory image {all-slots | slot slot-num}
no mdr download reserve memory image {all-slots | slot slot-num}
Syntax Description
all-slots
Reserves memory for the new software on all installed line cards that support eFSU.
slot slot-num
Reserves memory for the new software on the line card in the specified chassis slot.
Command Default
This command is enabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
On line cards that support eFSU, the router automatically reserves memory on the line card to store the new software image (decompressed format). During the upgrade, the router preloads new line card software onto supported line cards. The amount of memory needed varies according to line card type.
You can issue the show mdr download image command to display the amount of memory that will be reserved on the line cards that support eFSU.
Although we do not recommend it, you can issue the no mdr download reserve memory image command to keep the router from reserving memory for software preload on the specified line card.
Note
Examples
The following command reserves memory for the new software on the line card installed in slot 6:
Router# mdr download reserve memory image slot 6Related Commands
show mdr download image
Displays the amount of memory that will be reserved for software preload on line cards that support eFSU.
mls ip multicast sso
To configure the stateful switchover (SSO) parameters, use the mls ip multicast sso command in global configuration mode. To return to the default settings, use the no form of this command.
mls ip multicast sso {convergence-time time | leak {interval seconds | percent percentage}}
no mls ip multicast sso {convergence-time time | leak {interval seconds | percent percentage}}
Syntax Description
Command Default
The defaults are as follows:
•
•
•
Command Modes
Global configuration
Command History
12.2(18)SXD
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
Examples
This example shows how to set the maximum time to wait for protocol convergence to 300 seconds:
Router(config)# mls ip multicast sso convergence-time 300Router(config)#This example shows how to set the packet-leak interval to 200 seconds:
Router(config)# mls ip multicast sso leak interval 200Router(config)#This example shows how to set the packet-leak percentage to 55 percent:
Router(config)# mls ip multicast sso leak percent 55Router(config)#Related Commands
show mls ip multicast sso
Displays information about multicast high-availability SSO.
mode (redundancy)
To configure the redundancy mode of operation, use the mode command in redundancy configuration mode.
Cisco 7304 Router
mode {rpr | rpr-plus | sso}
Cisco 7500 Series Routers
mode {hsa | rpr | rpr-plus | sso}
Cisco 10000 Series Routers
mode {rpr-plus | sso}
Cisco 12000 Series Routers
mode {rpr | rpr-plus | sso}
Cisco uBR10012 Universal Broadband Router
mode {rpr-plus | sso}
Syntax Description
Command Default
The default mode for the Cisco 7500 series routers is HSA.
The default mode for the Cisco 7304 router and Cisco 10000 series routers is SSO.
The default mode for the Cisco 12000 series routers is RPR.
The default mode for the Cisco uBR10012 universal broadband router is SSO.Command Modes
Redundancy configuration (config-red)
Command History
Usage Guidelines
The mode selected by the mode command in redundancy configuration mode must be fully supported by the image that has been set into both the active and standby Route Processors (RPs). A high availability image must be installed into the RPs before RPR can be configured. Use the hw-module slot image command to specify a high availability image to run on the standby RP.
For Cisco IOS Release 12.2(33)SCA on the Cisco 10000 series routers and the Cisco uBR10012 universal broadband router, the use of SSO redundancy mode is recommended because RPR+ redundancy mode is being removed. If you enable RPR+ redundancy mode, you may see the following message:
********************************************************** Warning, The redundancy mode RPR+ is being deprecated ** and will be removed in future releases. Please change ** mode to SSO: ** redundancy ** mode sso *********************************************************Examples
The following example configures RPR+ redundancy mode on a Cisco 12000 series or Cisco 1000 series router:
Router# mode rpr-plusThe following example sets the mode to HSA on a Cisco 7500 series router:
Router# mode hsaRelated Commands
monitor event-trace sbc (EXEC)
To monitor and control the event trace function for the Session Border Controller (SBC), use the monitor event-trace sbc command in privileged EXEC mode.
monitor event-trace sbc ha {clear | continuous [cancel] | disable | dump [pretty] | enable | one-shot}
Syntax Description
Command Default
Event tracing for SBC is not enabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the monitor event-trace sbc ha command to control what, when, and how event trace data for the SBC on the Cisco ASR 1000 Series Aggregation Services Routers is collected.
Use this command after you have configured the event trace functionality on the Cisco ASR 1000 Series Routers using the monitor event-trace sbc ha command in global configuration mode.
Note
You can enable or disable SBC event tracing in one of two ways: using the monitor event-trace sbc ha command in privileged EXEC mode or using the monitor event-trace sbc command in global configuration mode. To disable event tracing, you would enter either of these commands with the disable keyword. To enable event tracing again, you would enter either of these commands with the enable keyword.
Use the show monitor event-trace sbc ha command to display trace messages. Use the monitor event-trace sbc ha dump command to save trace message information for a single event. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace sbc ha dump pretty command.
To configure the file in which you want to save trace information, use the monitor event-trace sbc ha dump-file dump-file-name command in global configuration mode. The trace messages are saved in binary format.
Examples
The following example shows the privileged EXEC commands that stop event tracing, clear the current contents of memory, and reenable the trace function for SBC HA events. This example assumes that the tracing function is configured and enabled on the networking device.
Router# monitor event-trace sbc ha disableRouter# monitor event-trace sbc ha clearRouter# monitor event-trace sbc ha enableThe following example shows how to configure the continuous display of the latest SBC HA trace entries:
Router# monitor event-trace sbc ha continuousThe following example shows how to stop the continuous display of the latest trace entries:
Router# monitor event-trace sbc ha continuous cancelRelated Commands
monitor event-trace sbc (global)
To configure event tracing for the Session Border Controller (SBC), use the monitor event-trace sbc command in global configuration mode. To remove an event tracing configuration for SBC, use the no form of this command.
monitor event-trace sbc ha {disable | dump-file dump-file-name | enable | size number | stacktrace [depth]}
no monitor event-trace sbc ha {dump-file dump-file-name | size number | stacktrace [depth]}
Syntax Description
Command Default
Event tracing for the SBC is not enabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the monitor event-trace sbc ha command to enable or disable event tracing and to configure event trace parameters for SBC.
The Cisco IOS XE software allows SBC to define whether support for event tracing is enabled or disabled by default. The command interface for event tracing allows you to change the default value in one of two ways: using the monitor event-trace sbc ha command in privileged EXEC mode or using the monitor event-trace sbc ha command in global configuration mode.
Additionally, default settings do not appear in the configuration file. If SBC enables event tracing by default, the monitor event-trace sbc ha enable command does not appear in the configuration file of the networking device; however, disabling event tracing that has been enabled by default by the subsystem creates a command entry in the configuration file.
Note
To determine whether event tracing is enabled by default for SBC, use the show monitor event-trace sbc ha command to display trace messages.
To specify the trace call stack at tracepoints, you must first clear the trace buffer with the monitor event-trace sbc ha clear privileged EXEC command.
Examples
The following example shows how to enable event tracing for SBC subsystem component in Cisco IOS XE software and configure the size to 10,000 messages. The trace messages file is set to sbc-ha-dump in flash memory.
Router(config)# monitor event-trace sbc ha enableRouter(config)# monitor event-trace sbc ha dump-file bootflash:sbc-ha-dumpRouter(config)# monitor event-trace sbc ha size 10000Related Commands
neighbor ha-mode sso
To configure a Border Gateway Protocol (BGP) neighbor to support BGP nonstop routing (NSR) with stateful switchover (SSO), use the neighbor ha-mode sso command in the appropriate command mode. To remove the configuration, use the no form of this command.
neighbor ip-address ha-mode sso
no neighbor ip-address ha-mode sso
Syntax Description
Command Default
BGP NSR with SSO support is disabled.
Command Modes
Address family configuration
Session-template configurationCommand History
Usage Guidelines
The neighbor ha-mode sso command is used to configure a BGP neighbor to support BGP NSR with SSO. BGP NSR with SSO is disabled by default.
BGP NSR with SSO is supported in BGP peer, BGP peer group, and BGP session template configurations. To configure BGP NSR with SSO in BGP peer and BGP peer group configurations, use the neighbor ha-mode sso command in address family configuration mode for IPv4 VRF address family BGP peer sessions. To include support for Cisco BGP NSR with SSO in a peer session template, use the ha-mode sso command in session-template configuration mode.
Examples
The following example shows how to configure a BGP neighbor to support SSO:
Router(config-router-af)# neighbor 10.3.32.154 ha-mode ssoRelated Commands
show ip bgp vpnv4
Displays VPN address information from the BGP table.
show ip bgp vpnv4 all sso summary
Displays the number of BGP neighbors that support SSO.
nsf (EIGRP)
To enable Cisco nonstop forwarding (NSF) operations for Enhanced Interior Gateway Protocol (EIGRP), use the nsf command in router configuration mode or address-family configuration mode. To disable EIGRP NSF and remove the EIGRP NSF configuration from the running-config file, use the no form of this command.
nsf
no nsf
Syntax Description
This command has no arguments or keywords.
Command Default
EIGRP NSF capability is enabled by default.
Command Modes
Router configuration (config-router)
Address-family configuration (config-router-af)Command History
Usage Guidelines
This command is used to enable or disable EIGRP NSF support on an NSF capable router. EIGRP NSF capability is enabled by default on distributed platforms that run a supporting version of Cisco IOS software.
Examples
The nsf command is used to enable or disable the EIGRP NSF capability. The following example disables NSF capability:
Router# configure terminalRouter(config)# router eigrp 101Router(config-router)# no nsfThe nsf command is used to enable or disable the EIGRP NSF capability. The following EIGRP named configuration example disables NSF capability:
Router(config)# router eigrp virtual-nameRouter(config-router)# address-family ipv4 as 10Router(config-router-af)# no nsfRelated Commands
nsf (IS-IS)
To configure Cisco nonstop forwarding (NSF) operations for Intermediate System-to-Intermediate System (IS-IS), use the nsf command in router configuration IS-IS 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.
nsf [cisco | ietf]
no nsf [cisco | ietf]
Syntax Description
Command Default
NSF is disabled by default.
Command Modes
Router configuration IS-IS
Command History
Usage Guidelines
The user must configure NSF operation only if a router is expected to perform NSF during restart. The optional cisco keyword enables the use of checkpointing to allow the standby route processor (RP) to restore protocol state when an NSF restart occurs.
Examples
The following example enables Cisco proprietary IS-IS NSF operation:
nsf ciscoThe following example enables IETF IS-IS NSF operation:
nsf ietfRelated Commands
nsf (OSPF)
Note
To configure Cisco nonstop forwarding (NSF) operations for Open Shortest Path First (OSPF), use the nsf command in router configuration mode. To disable Cisco NSF for OSPF, use the no form of this command.
nsf [enforce global]
no nsf [enforce global]
Syntax Description
enforce global
(Optional) Cancels NSF restart when non-NSF-aware neighboring networking devices are detected.
Command Default
This command is disabled by default; therefore, NSF operations for OSPF is not configured.
Command Modes
Router configuration (config-router)
Command History
Usage Guidelines
The user must configure NSF operation for OSPF only if a router is expected to perform NSF during restart. For users to have full NSF benefits, all OSPF neighbors of the specified router must be NSF-aware.
If neighbors that are not NSF-aware are detected on a network interface, NSF restart is aborted on the interface; however, NSF restart will continue on other interfaces. This functionality applies to the default NSF mode of operation when NSF is configured.
If the user configures the optional enforce global keywords, NSF restart will be canceled for the entire process when neighbors that are not NSF-aware are detected on any network interface during restart. NSF restart will also be canceled for the entire process if a neighbor adjacency reset is detected on any interface or if an OSPF interface goes down. To revert to the default NSF mode, enter the no nsf enforce global command.
Examples
The following example enters router configuration mode and cancels the NSF restart for the entire OSPF process if neighbors that are not NSF-aware are detected on any network interface during restart:
Router(config)# router ospf 1Router(config-router)# nsf cisco enforce globalRelated Commands
debug ip ospf nsf
Displays debugging messages related to OSPF NSF commands.
router ospf
Enables OSPF routing and places the router in router configuration mode.
nsf cisco
To enable Cisco nonstop forwarding (NSF) operations on a router that is running Open Shortest Path First (OSPF), use the nsf cisco command in router configuration mode. To return to the default, use the no form of this command.
nsf cisco [enforce global | helper [disable]]
no nsf cisco [enforce global | helper disable]
Syntax Description
Command Default
Cisco NSF restarting mode is disabled. Cisco NSF helper mode is enabled.
Command Modes
Router configuration (config-router)
Command History
Usage Guidelines
For Cisco IOS Release 12.0(32)S and later releases, this command replaces the nsf (OSPF) command.
This command enables Cisco NSF on an OSPF router. When NSF is enabled on a router, the router is NSF-capable and will operate in restarting mode.
If a router is expected to cooperate with a neighbor that is doing an NSF graceful restart only, the neighbor router must be running a Cisco software release that supports NSF but NSF need not be configured on the router. When a router is running a Cisco software release that supports NSF, the router is NSF-aware.
By default, neighboring NSF-aware routers will operate in NSF helper mode during a graceful restart. To disable Cisco NSF helper mode on an NSF-aware router, use this command with the disable keyword. To reenable helper mode after explicitly disabling helper mode on an NSF-aware router, use the no nsf cisco helper disable command.
If neighbors that are not NSF-aware are detected on a network interface during an NSF graceful restart, restart is aborted on that interface only and graceful restart will continue on other interfaces. To cancel restart for the entire OSPF process when neighbors that are not NSF-aware are detected during restart, configure this command with the enforce global keywords.
Note
Examples
The following example enables Cisco NSF restarting mode on a router and causes the NSF restart to be canceled for the entire OSPF process if neighbors that are not NSF-aware are detected on any network interface during the restart.
router ospf 24nsf cisco enforce globalRelated Commands
nsf ietf
To configure Internet Engineering Task Force (IETF) nonstop forwarding (NSF) operations on a router that is running Open Shortest Path First (OSPF), use the nsf ietf command in router configuration mode. To return to the default, use the no form of this command.
nsf ietf [restart-interval seconds | helper [disable | strict-lsa-checking]]
no nsf ietf [restart-interval | helper [disable | strict-lsa-checking]]
Syntax Description
Command Default
IETF NSF graceful restart mode is disabled. IETF NSF helper mode is enabled.
Command Modes
Router configuration (config-router)
Command History
Usage Guidelines
This command enables IETF NSF on an OSPF router. When NSF is enabled on a Cisco router, the router is NSF-capable and will operate in restarting mode.
If a router is expected to cooperate with a neighbor that is doing an NSF graceful restart only, the neighbor router must be running a Cisco software release that supports NSF but NSF need not be configured on the router. When a router is running a Cisco software release that supports NSF, the router is NSF-aware.
By default, neighboring NSF-aware routers will operate in NSF helper mode during a graceful restart. To disable IETF NSF helper mode on an NSF-aware router, use this command with the disable keyword. To reenable helper mode after explicitly disabling helper mode on an NSF-aware router, use the no nsf ietf helper disable command.
Strict LSA checking allows a router in IETF NSF helper mode to terminate the graceful restart process if it detects a changed LSA that would cause flooding during the graceful restart process. You can configure strict LSA checking on NSF-aware and NSF-capable routers but it is effective only when the router is in helper mode.
Examples
The following example enables IETF NSF restarting mode on a router and changes the graceful restart interval from default (120 seconds) to 200 seconds:
router ospf 24nsf ietf restart-interval 200Related Commands
nsf interface wait
To specify how long a Cisco nonstop forwarding (NSF) restart will wait for all interfaces with Intermediate System-to-Intermediate System (IS-IS) adjacencies to come up before completing the restart, use the nsf interface wait command in router configuration IS-IS 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.
nsf interface wait seconds
no nsf interface wait seconds
Syntax Description
Command Default
The default value for the seconds argument is 10.
Command Modes
Router configuration IS-IS
Command History
Usage Guidelines
The nsf interface wait command can be used if Cisco proprietary IS-IS NSF is configured or if Internet Engineering Task Force (IETF) IS-IS NSF is enabled using the nsf t3 manual command. You can use this command if an interface is slow to come up.
Examples
The following example specifies that NSF restart will wait 15 seconds for all interfaces with IS-IS adjacencies to come up before completing the restart:
Router(config)# router isisRouter(config-router)# nsf ciscoRouter(config-router)# nsf interface wait 15Related Commands
nsf interval
To configure the minimum time between Cisco nonstop forwarding (NSF) restart attempts, use the nsf interval command in router configuration Intermediate System-to-Intermediate System (IS-IS) 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.
nsf interval minutes
no nsf interval minutes
Syntax Description
minutes
The length of time in minutes between restart attempts. The valid range is from 0 to 1440 minutes.
Command Default
The default value for the minutes argument is 5.
Command Modes
Router configuration IS-IS
Command History
Usage Guidelines
The nsf interval command can be used with both Cisco proprietary IS-IS NSF and Internet Engineering Task Force (IETF) IS-IS NSF. When you use Cisco proprietary IS-IS NSF, the active route processor (RP) must be up for at least 5 minutes before IS-IS will attempt to perform an NSF restart as part of a stateful switchover.
When you use the nsf command with the ietf keyword, the standby RP must be up for at least 5 minutes before IS-IS will attempt to perform an NSF restart as part of a stateful switchover.
Examples
The following example configures the minimum time between NSF restart attempts to be 2 minutes:
Router(config-router)# router isisRouter(config-router)# nsf ciscoRouter(config-router)# nsf interval 2Related Commands
nsf t3
To specify the methodology used to determine how long Internet Engineering Task Force (IETF) Cisco nonstop forwarding (NSF) will wait for the link-state packet (LSP) database to synchronize before generating overloaded link-state information for itself and flooding that information out to its neighbors, use the nsf t3 command in router configuration IS-IS 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.
nsf t3 {manual seconds | adjacency}
no nsf t3 {manual seconds | adjacency}
Syntax Description
Command Default
The default value for the seconds argument is 30.
Command Modes
Router configuration IS-IS
Command History
Usage Guidelines
When the nsf t3 adjacency command is enabled, the time that IETF NSF waits for the LSP database to synchronize is determined by the adjacency holdtime advertised to the neighbors of the specified RP before switchover. When the nsf t3 manual command is enabled, the specified time in seconds is used.
The nsf t3 manual command can be used only if IETF IS-IS NSF is configured.
Examples
In the following example, the amount of time that IETF NSF waits for the LSP database to synchronize is set to 40 seconds:
nsf t3 manual 40In the following example, the amount of time that IETF NSF waits for the LSP database to synchronize is determined by the adjacency holdtime advertised to the neighbors of the specified RP before switchover:
nsf t3 adjacencyRelated Commands
phone-number
To assign the phone number to be used for customer contact for Call Home, use the phone-number command in call home configuration mode. To remove the phone number, use the no form of this command.
phone-number +phone-number
no phone-number +phone-number
Syntax Description
phone-number
12 to16 digits (not including the plus (+) prefix), using hyphens (-) or spaces, and numbers. If you include spaces, you must enclose your entry in quotes (" ").
Command Default
No phone number is assigned for customer contact.
Command Modes
Call home configuration (cfg-call-home)
Command History
Usage Guidelines
The phone-number command is optional.
Examples
The following example shows how to configure the phone number 1-222-333-444 for customer contact without dashes or spaces:
Router(config)# call-homeRouter(cfg-call-home)# phone-number +12223334444The following example shows how to configure the same phone number for customer contact using hyphens:
Router(config)# call-homeRouter(cfg-call-home)# phone-number +1-222-333-4444The following example shows how to configure the same phone number for customer contact using spaces:
Router(config)# call-homeRouter(cfg-call-home)# phone-number "+1 222 333 4444"Related Commands
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
show call-home
Displays call home configuration information.
platform redundancy bias
To configure the standby slot Supervisor (SUP) bootup delay time, use the platform redundancy bias command in global configuration mode.
platform redundancy bias seconds
Syntax Description
Command Default
The command is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
The slave slot SUP, on certain occasions, boots up faster than the master slot SUP, thereby becoming active. The platform redundancy bias command allows you to configure the delay in bootup time such that the slave slot SUP always boots up slower than the master slot SUP, and does not become active.
Examples
The following example shows how to configure the standby slot SUP bootup delay setting for 25 seconds:
Router# configure terminalRouter(config)# platform redundancy bias 25Router(config)# endRelated Commands
show platform redundancy bias
Displays the output for a specific platform redundancy bias command.
policy config-sync reload
To enable and specify the configuration synchronization policy during the reload between the active and standby supervisor engine or route switch processor, use the policy config-sync reload command in global configuration mode. To disable the configuration synchronization policy and return to the default setting, use the no form of this command.
policy config-sync {bulk | lbl} {bem | prc} reload
no policy config-sync {bulk | lbl} {bem | prc} reload
Syntax Description
Command Default
Disabled
Command Modes
Global configuration (config)
Command History
Examples
The following example shows how to enable and specify the configuration synchronization policy during the reload between the active and standby supervisor engine or route switch processor:
Router(config)# policy config-sync bulk reloadRelated Commands
profile (call home)
To configure a destination profile to specify how alert notifications are delivered for Call Home and enter call home profile configuration mode, use the profile (call home) command in call home configuration mode. To delete a named destination profile or all destination profiles, use the no form of this command.
profile profile-name
no profile {profile-name | all}
Syntax Description
Command Default
After you configure a destination profile, the profile is automatically enabled for Call Home. This does not apply to the CiscoTAC-1 predefined profile.
Command Modes
Call home configuration (cfg-call-home)
Command History
Usage Guidelines
When you enter the profile (call home) command, you enter call home profile configuration mode to specify how alert notifications are delivered for Call Home. Some of the available call home profile configuration commands are shown in the Examples section.
After you configure a profile, it is automatically enabled for use by Call Home. If you do not want the profile to be active in the Call Home configuration, use the no active command. You can reactivate the profile using the active command.
The predefined CiscoTAC-1 profile is disabled by default.
Examples
The following example shows how to enter call home profile configuration mode:
Router(conf)# call-homeRouter(cfg-call-home)# profile exampleRouter(cfg-call-home-profile)#?Call-home profile configuration commands:active Activate the current profiledefault Set a command to its defaultsdestination Message destination related configurationexit Exit from call-home profile configuration modeno Negate a command or set its defaultssubscribe-to-alert-group Subscribe to alert-groupRelated Commands
rate-limit (call home)
To configure the maximum number of messages per minute for Call Home, use the rate-limit (call home) command in call home configuration mode. To return to the default, use the no form of this command.
rate-limit threshold
no rate-limit [threshold]
Syntax Description
Command Default
If the rate-limit (call home) command is not configured, the maximum number of messages per minute is 20.
Command Modes
Call home configuration (cfg-call-home)
Command History
Usage Guidelines
The rate-limit (call home) command is optional.
Examples
The following example changes the call home maximum message rate to 50 messages per minute:
Router(config)# call-homeRouter(cfg-call-home)# rate-limit 50The following example changes the call home maximum message rate back to 20 messages per minute:
Router(cfg-call-home)# no rate-limitRelated Commands
call-home (global configuration)
Enters call home configuration mode for configuration of Call Home settings.
show call-home
Displays Call Home configuration information.
redundancy
To enter redundancy configuration mode, use the redundancy command in global configuration mode. This command does not have a no form.
redundancy
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the redundancy command to enter redundancy configuration mode, where you can define aspects of redundancy such as shelf redundancy for the Cisco AS5800 universal access server.
Cisco 10000 Series Router
Before configuring line card redundancy, install the Y-cables. Before deconfiguring redundancy, remove the Y-cables.
The following restrictions apply to line card redundancy on the Cisco 10000 series router:
•
•
•
Cisco 7600 Series Router
From redundancy configuration mode, you can enter the main CPU submode to manually synchronize the configurations that are used by the two supervisor engines.
From the main CPU submode, you can use the auto-sync command to use all the redundancy commands that are applicable to the main CPU.
To select the type of redundancy mode, use the mode command.
Nonstop forwarding (NSF) with stateful switchover (SSO) redundancy mode supports IPv4. NSF with SSO redundancy mode does not support IPv6, Internetwork Packet Exchange (IPX), and Multiprotocol Label Switching (MPLS).
After you enter redundancy configuration mode, you can use the interchassis command to specify the redundancy group number and enter interchassis redundancy mode. In the interchassis redundancy configuration mode, you can do the following:
•
•
•
•
•
Cisco uBR10012 Universal Broadband Router
After you enter redundancy configuration mode, you can use the main-cpu command to enter main-CPU redundancy configuration mode, which allows you to specify which files are synchronized between the active and standby Performance Routing Engine (PRE) modules.
Cisco RF Gateway 10
At the redundancy configuration mode, you can do the following:
•
•
•
•
•
•
Examples
The following example shows how to enable redundancy mode:
Router(config)# redundancyRouter(config-red)#The following example shows how to assign the configured router shelf to the redundancy pair designated as 25. This command must be issued on both router shelves in the redundant router-shelf pair:
Router(config)# redundancyRouter(config-red)# failover group-number 25Cisco 10000 Series Router
The following example shows how to configure two 4-port channelized T3 half eight line cards that are installed in line card slot 2 for one-to-one redundancy:
Router(config)# redundancyRouter(config-r)# linecard-group 1 y-cableRouter(config-r-lc)# member subslot 2/1 primaryRouter(config-r-lc)# member subslot 2/0 secondaryCisco 7600 Series Router
The following example shows how to enter the main CPU submode:
Router(config)# redundancyRouter(config-r)# main-cpuRouter(config-r-mc)#Cisco uBR10012 Universal Broadband Router
The following example shows how to enter redundancy configuration mode and display the commands that are available in that mode on the Cisco uBR10012 router:
Router# configure terminalRouter(config)# redundancyRouter(config-r)# ?Redundancy configuration commands:associate Associate redundant slotsexit Exit from redundancy configuration modemain-cpu Enter main-cpu modeno Negate a command or set its defaultsThe following example shows how to enter redundancy configuration mode and displays its associated commands on the Cisco RFGW-10 chassis:
Router# configure terminalRouter(config)# redundancyRouter(config-r)#?Redundancy configuration commands:default Set a command to its defaultsexit Exit from redundancy configuration modelinecard-group Enter linecard redundancy submodemain-cpu Enter main-cpu modemode redundancy mode for this chassisno Negate a command or set its defaultspolicy redundancy policy enforcementThe following example shows how to enter redundancy configuration mode and its associated commands in the interchassis mode:
Router# configure terminalRouter(config)# redundancyRouter(config-r)#?
Redundancy configuration commands:exit Exit from redundancy configuration modeinterchassis Enter interchassis modeno Negate a command or set its defaultsRouter(config-r)# interchassis group 100R1(config-r-ic)# ?Interchassis redundancy configuration commands:backbone specify a backbone interface for the redundancy groupexit Exit from interchassis configuration modemember specify a redundancy group membermlacp mLACP interchassis redundancy group subcommandsmonitor define the peer monitoring methodno Negate a command or set its defaultsRelated Commands
redundancy force-switchover
To force the standby Route Processor (RP) or Supervisor card to assume the role of the active RP or Supervisor card, use the redundancy force-switchover command in privileged EXEC mode.
redundancy force-switchover [main-cpu]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the redundancy force-switchover command to switch control of a router from the active RP or Supervisor card to the standby RP or Supervisor card. Both the active and standby RPs or Supervisor cards must have a high availability Cisco IOS image installed and must be configured for Route Processor Redundancy (RPR) mode before the redundancy force-switchover command can be used. Before the system switches over, it verifies that the standby RP or Supervisor card is ready to take over.
When you use the redundancy force-switchover command and the current running configuration is different from the startup configuration, the system prompts you to save the running configuration before the switchover is performed.
Note
Note
On Cisco 7600 series routers, the redundancy force-switchover command conducts a manual switchover to the redundant supervisor engine. The redundant supervisor engine becomes the new active supervisor engine running the new Cisco IOS image. The modules are reset and the module software is downloaded from the new active supervisor engine.
The active and redundant supervisor engines do not reset on a Route Processor Redundancy Plus (RPR+) switchover. The old active supervisor engine reboots with the new image and becomes the redundant supervisor engine.
Beginning with Cisco IOS Release 12.2(33)SCA, you can force a Performance Routing Engine (PRE) switchover using the redundancy force-switchover main-cpu command from either the primary or standby PRE. If you force a switchover from the active PRE, both PREs synchronize and the active PRE reloads normally. When you force a switchover from the standby PRE, a crash dump of the active PRE occurs for troubleshooting purposes. Forcing a switchover from the standby PRE should only be done if you cannot access the active PRE.
Examples
The following example shows a switchover from the active RP to the standby RP on a Cisco 7513 router with RPR configured:
Router# configure terminalRouter(config)# hw-module slot 7 image slot0:rsp-pv-mzRouter(config)# hw-module slot 6 image slot0:rsp-pv-mzRouter(config)# slave auto-sync configRouter(config)# redundancyRouter(config-r)# mode rprRouter(config-r)# endRouter# copy running-config startup-configRouter# redundancy force-switchoverThe following example shows how to perform a manual switchover from the active to the standby RP when the running configuration is different from the startup configuration:
Router# redundancy force-switchoverSystem configuration has been modified. Save? [yes/no]:yBuilding configuration.........[OK]Proceed with switchover to standby NSE? [confirm]y00:07:35:%SYS-5-SWITCHOVER:Switchover requestedThe following example shows how to perform a manual switchover from the active to the standby RP when the running configuration is the same as the startup configuration:
Router# redundancy force-switchoverProceed with switchover to standby NSE? [confirm]00:07:35:%SYS-5-SWITCHOVER:Switchover requestedCisco RF Gateway 10
The following example shows how to perform a manual switchover from the active to the standby RP when the running configuration is different from the startup configuration:
Router# redundancy force-switchoverSystem configuration has been modified. Save? [yes/no]:yBuilding configuration.........[OK]Proceed with switchover to standby NSE? [confirm]y00:07:35:%SYS-5-SWITCHOVER:Switchover requestedThe following example shows how to perform a manual switchover from the active to the standby RP when the running configuration is the same as the startup configuration:
Router# redundancy force-switchoverProceed with switchover to standby NSE? [confirm]00:07:35:%SYS-5-SWITCHOVER:Switchover requestedRelated Commands
rename profile
To change the name of a destination profile, use the rename profile command in call home configuration mode.
rename profile source-profile target-profile
Syntax Description
source-profile
Name of the existing destination profile that you want to rename.
target-profile
New name of the destination profile.
Command Default
This command has no default behavior or values.
Command Modes
Call home configuration (cfg-call-home)
Command History
Usage Guidelines
Use the rename profile command when you want to change the name of an existing destination profile for Call Home.
Examples
The following example changes the name of "profile2" to "testprofile":
Router(config)# call-homeRouter(cfg-call-home)# rename profile profile2 testprofileRelated Commands
sender
To assign the e-mail addresses to be used in the from and reply-to fields in messages for Call Home, use the sender command in call home configuration mode. To remove the assigned e-mail addresses, use the no form of this command.
sender {from | reply-to} email-address
no sender {from | reply-to} email-address
Syntax Description
Command Default
If the sender from command is not configured, the address specified in the contact-email-addr command for Call Home is used for all destination profiles. There is no default value for the reply-to option.
Command Modes
Call home configuration (cfg-call-home)
Command History
Usage Guidelines
The sender command is optional.
Examples
The following example configures the e-mail address "username@example.com" to appear in the from field of Call Home messages:
Router(config)# call-homeRouter(cfg-call-home)# sender from username@example.comRelated Commands
service call-home
To enable Call Home, use the service call-home command in global configuration mode. To disable the Call Home, use the no form of this command.
service call-home
no service call-home
Syntax Description
This command has no arguments or keywords.
Command Default
Call Home is disabled.
Command Modes
Global configuration (config)
Command History
Examples
The following example shows how to enable Call Home:
Router(config)# service call-homeThe following example shows how to disable Call Home:
Router(config)# no service call-homeRelated Commands
service image-version compatibility
To enable Fast Software Upgrade (FSU) functionality, use the service image-version compatibility command in global configuration mode. To omit the compatibility matrix and enable Enhanced Fast Software Upgrade (eFSU) functionality, use the no form of this command.
service image-version compatibility
no service image-version compatibility
Syntax Description
This command has no arguments or keywords.
Defaults
Fast Software Upgrade (FSU) is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the service image-version compatibility command to enable FSU, and use the no service image-version compatibility command to omit the compatibility matrix and enable eFSU functionality.
Examples
The following example enables eFSU functionality:
Router(config)# no service image-version compatibilityRelated Commands
service image-version efsu
To enable Enhanced Fast Software Upgrade (eFSU) functionality, use the no version of the service image-version efsu command in global configuration mode.
no service image-version efsu
Syntax Description
This command has no arguments or keywords.
Defaults
eFSU functionality is not enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The no service image-version efsu command functionality is similar to that of the service image-version compatibility command. The no service image-version efsu command is used to omit the compatibility matrix creation for Cisco 7600 series router eFSU images.
Examples
The following example enables eFSU functionality:
Router# no service image-version efsuRelated Commands
