-
Cisco IOS High Availability Command Reference
-
Introduction
-
action cli through configure replace
-
control-plane through debug mpls ldp checkpoint
-
debug mpls ldp graceful-restart through event wdsysmon
-
frame-relay redundancy auto-sync lmi-sequence-numbers through issu set rollback-timer
-
match mpls-label through route-target
-
service call-home through show ip pim interface
-
show ip pim neighbor through show ppp subscriber statistics
-
show pppatm statistics through vrrp timers learn
-
Table Of Contents
frame-relay redundancy auto-sync lmi-sequence-numbers
ip rsvp signalling hello (configuration)
ip rsvp signalling hello (interface)
ip rsvp signalling hello refresh interval
ip rsvp signalling hello refresh misses
ip rsvp signalling hello statistics
ip vrf forwarding (interface configuration)
ip vrf forwarding (server-group)
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.
glbp authentication
To configure an authentication string for the Gateway Load Balancing Protocol (GLBP), use the glbp authentication command in interface configuration mode. To disable authentication, use the no form of this command.
glbp group-number authentication {text string | md5 {key-string [0 | 7] key | key-chain name-of-chain}}
no glbp group-number authentication {text string | md5 {key-string [0 | 7] key | key-chain name-of-chain}}
Syntax Description
Command Default
No authentication of GLBP messages occurs.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The same authentication method must be configured on all the routers that are configured to be members of the same GLBP group, to ensure interoperation. A router will ignore all GLBP messages that contain the wrong authentication information.
If password encryption is configured with the service password-encryption command, the software saves the key string in the configuration as encrypted text.
Examples
The following example configures stringxyz as the authentication string required to allow GLBP routers in group 10 to interoperate:
interface fastethernet 0/0glbp 10 authentication text stringxyzIn the following example, GLBP queries the key chain "AuthenticateGLBP" to obtain the current live key and key ID for the specified key chain:
key chain AuthenticateGLBPkey 1key-string ThisIsASecretKeyinterface Ethernet0/1ip address 10.0.0.1 255.255.255.0glbp 2 ip 10.0.0.10glbp 2 authentication md5 key-chain AuthenticateGLBPRelated Commands
glbp forwarder preempt
To configure a router to take over as active virtual forwarder (AVF) for a Gateway Load Balancing Protocol (GLBP) group if the current AVF falls below its low weighting threshold, use the glbp forwarder preempt command in interface configuration mode. To disable this function, use the no form of this command.
glbp group forwarder preempt [delay minimum seconds]
no glbp group forwarder preempt [delay minimum]
Syntax Description
Command Default
Forwarder preemption is enabled with a default delay of 30 seconds.
Command Modes
Interface configuration (config-if)
Command History
Examples
The following example shows a router being configured to preempt the current AVF when the current AVF falls below its low weighting threshold. If the router preempts the current AVF, it waits 60 seconds before taking over the role of the AVF.
glbp 10 forwarder preempt delay minimum 60Related Commands
glbp ip
To activate the Gateway Load Balancing Protocol (GLBP), use the glbp ip command in interface configuration mode. To disable GLBP, use the no form of this command.
glbp group ip [ip-address [secondary]]
no glbp group ip [ip-address [secondary]]
Syntax Description
Command Default
GLBP is disabled by default.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The glbp ip command activates GLBP on the configured interface. If an IP address is specified, that address is used as the designated virtual IP address for the GLBP group. If no IP address is specified, the designated address is learned from another router configured to be in the same GLBP group. For GLBP to elect an active virtual gateway (AVG), at least one router on the cable must have been configured with the designated address. A router must be configured with, or have learned, the virtual IP address of the GLBP group before assuming the role of a GLBP gateway or forwarder. Configuring the designated address on the AVG always overrides a designated address that is in use.
When the glbp ip command is enabled on an interface, the handling of proxy Address Resolution Protocol (ARP) requests is changed (unless proxy ARP was disabled). ARP requests are sent by hosts to map an IP address to a MAC address. The GLBP gateway intercepts the ARP requests and replies to the ARP on behalf of the connected nodes. If a forwarder in the GLBP group is active, proxy ARP requests are answered using the MAC address of the first active forwarder in the group. If no forwarder is active, proxy ARP responses are suppressed.
Examples
The following example activates GLBP for group 10 on Fast Ethernet interface 0/0. The virtual IP address to be used by the GLBP group is set to 10.21.8.10.
interface fastethernet 0/0ip address 10.21.8.32 255.255.255.0glbp 10 ip 10.21.8.10The following example activates GLBP for group 10 on Fast Ethernet interface 0/0. The virtual IP address used by the GLBP group will be learned from another router configured to be in the same GLBP group.
interface fastethernet 0/0glbp 10 ipRelated Commands
glbp load-balancing
To specify the load-balancing method used by the active virtual gateway (AVG) of the Gateway Load Balancing Protocol (GLBP), use the glbp load-balancing command in interface configuration mode. To disable load balancing, use the no form of this command.
glbp group load-balancing [host-dependent | round-robin | weighted]
no glbp group load-balancing
Syntax Description
Command Default
The round-robin method is the default.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Use the host-dependent method of GLBP load balancing when you need each host to always use the same router. Use the weighted method of GLBP load balancing when you need unequal load balancing because routers in the GLBP group have different forwarding capacities.
Examples
The following example shows the host-dependent load-balancing method being configured for the AVG of the GLBP group 10:
interface fastethernet 0/0glbp 10 ip 10.21.8.10glbp 10 load-balancing host-dependentRelated Commands
glbp preempt
To configure the gateway to take over as active virtual gateway (AVG) for a Gateway Load Balancing Protocol (GLBP) group if it has higher priority than the current AVG, use the glbp preempt command in interface configuration mode. To disable this function, use the no form of this command.
glbp group preempt [delay minimum seconds]
no glbp group preempt [delay minimum]
Syntax Description
Command Default
A GLBP router with a higher priority than the current AVG cannot assume the role of AVG.
The default delay value is 30 seconds.Command Modes
Interface configuration (config-if)
Command History
Examples
The following example shows a router being configured to preempt the current AVG when its priority of 254 is higher than that of the current AVG. If the router preempts the current AVG, it waits 60 seconds before assuming the role of AVG.
glbp 10 preempt delay minimum 60glbp 10 priority 254Related Commands
glbp ip
Enables GLBP.
glbp priority
Sets the priority level of the router within a GLBP group.
glbp priority
To set the priority level of the gateway within a Gateway Load Balancing Protocol (GLBP) group, use the glbp priority command in interface configuration mode. To remove the priority level of the gateway, use the no form of this command.
glbp group priority level
no glbp group priority level
Syntax Description
group
GLBP group number in the range from 0 to 1023.
level
Priority of the gateway within the GLBP group. The range is from 1 to 255. The default is 100.
Command Default
The GLBP virtual gateway preemptive scheme is disabled
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Use this command to control which virtual gateway becomes the active virtual gateway (AVG). After the priorities of several different virtual gateways are compared, the gateway with the numerically higher priority is elected as the AVG. If two virtual gateways have equal priority, the gateway with the higher IP address is selected.
Examples
The following example shows a virtual gateway being configured with a priority of 254:
glbp 10 priority 254Related Commands
glbp ip
Enables GLBP.
glbp preempt
Configures a router to take over as the AVG for a GLBP group if it has higher priority than the current AVG.
glbp sso
To enable Gateway Load Balancing Protocol (GLBP) support of Stateful Switchover (SSO) if it has been disabled, use the glbp sso command in global configuration mode. To disable GLBP support of SSO, use the no form of this command.
glbp sso
no glbp sso
Syntax Description
This command has no arguments or keywords.
Command Default
GLBP Support for SSO is enabled by default.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use this command to enable GLBP support of SSO if it has been manually disabled by the no glbp sso command.
Examples
The following example show how to disable GLBP support of SSO:
Router(config)# no glbp ssoRelated Commands
debug glbp events
Displays debugging messages about GLBP events.
show glbp
Displays GLBP information.
glbp timers
To configure the time between hello packets sent by the Gateway Load Balancing Protocol (GLBP) gateway and the time that the virtual gateway and virtual forwarder information is considered valid, use the glbp timers command in interface configuration mode. To restore the timers to their default values, use the no form of this command.
glbp group timers [msec] hellotime [msec] holdtime
no glbp group timers
Syntax Description
Defaults
hellotime: 3 seconds
holdtime: 10 secondsCommand Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Routers on which timer values are not configured can learn timer values from the active virtual gateway (AVG). The timers configured on the AVG always override any other timer settings. All routers in a GLBP group should use the same timer values. If a GLBP gateway sends a hello message, the information should be considered valid for one holdtime. Normally, holdtime is greater than three times the value of hello time, (holdtime > 3 * hellotime). The range of values for holdtime force the holdtime to be greater than the hello time.
Examples
The following example shows the GLBP group 10 on Fast Ethernet interface 0/0 timers being configured for an interval of 5 seconds between hello packets, and the time after which virtual gateway and virtual forwarder information is considered to be invalid to 18 seconds:
interface fastethernet 0/0glbp 10 ipglbp 10 timers 5 18glbp timers redirect
To configure the time during which the active virtual gateway (AVG) for a Gateway Load Balancing Protocol (GLBP) group continues to redirect clients to a secondary active virtual forwarder (AVF), use the glbp timers redirect command in interface configuration mode. To restore the redirect timers to their default values, use the no form of this command.
glbp group timers redirect redirect timeout
no glbp group timers redirect redirect timeout
Syntax Description
Command Default
redirect: 600 seconds (10 minutes)
timeout: 14,400 seconds (4 hours)Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
A virtual forwarder that is assigned a virtual MAC address by the AVG is known as a primary virtual forwarder. If the virtual forwarder has learned the virtual MAC address from hello messages, it is referred to as a secondary virtual forwarder.
The redirect timer sets the time delay between a forwarder failing on the network and the AVG assuming that the forwarder will not return. The virtual MAC address to which the forwarder was responsible for replying is still given out in Address Resolution Protocol (ARP) replies, but the forwarding task is handled by another router in the GLBP group.
Note
The zero value for the redirect argument cannot be removed from the range of acceptable values because preexisting configurations of Cisco IOS software already using the zero value could be negatively affected during an upgrade. However, be advised that a zero setting is not recommended and, if used, results in a redirect timer that never expires. If the redirect timer does not expire, then when a router fails, new hosts continue to be assigned to the failed router instead of being redirected to the backup.
The timeout interval is the time delay between a forwarder failing on the network and the MAC address for which the forwarder was responsible becoming inactive on all of the routers in the GLBP group. After the timeout interval, packets sent to this virtual MAC address will be lost. The timeout interval must be long enough to allow all hosts to refresh their ARP cache entry that contained the virtual MAC address.
Examples
The following example shows the commands used to configure GLBP group 1 on Fast Ethernet interface 0/0 with a redirect timer of 1800 seconds (30 minutes) and timeout interval of 28,800 seconds (8 hours):
Router# config terminalRouter(config)# interface fastEthernet 0/0Router(config-if)# glbp 1 timers redirect 1800 28800glbp weighting
To specify the initial weighting value of the Gateway Load Balancing Protocol (GLBP) gateway, use the glbp weighting command in interface configuration mode. To restore the default values, use the no form of this command.
glbp group weighting maximum [lower lower] [upper upper]
no glbp group weighting
Syntax Description
Command Default
The default gateway weighting value is 100 and the default lower weighting value is 1.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The weighting value of a virtual gateway is a measure of the forwarding capacity of the gateway. If a tracked interface on the router fails, the weighting value of the router may fall from the maximum value to below the lower threshold, causing the router to give up its role as a virtual forwarder. When the weighting value of the router rises above the upper threshold, the router can resume its active virtual forwarder role.
Use the glbp weighting track and track commands to configure parameters for an interface to be tracked. If an interface on a router goes down, the weighting for the router can be reduced by a specified value.
Examples
The following example shows the weighting of the gateway for GLBP group 10 being set to a maximum of 110 with a lower weighting limit of 95 and an upper weighting limit of 105:
interface fastethernet 0/0ip address 10.21.8.32 255.255.255.0glbp 10 weighting 110 lower 95 upper 105Related Commands
glbp weighting track
Specifies an object to be tracked that affects the weighting of a GLBP gateway.
track
Configures an interface to be tracked.
glbp weighting track
To specify a tracking object where the Gateway Load Balancing Protocol (GLBP) weighting changes based on the availability of the object being tracked, use the glbp weighting track command in interface configuration mode. To remove the tracking, use the no form of this command.
glbp group weighting track object-number [decrement value]
no glbp group weighting track object-number [decrement value]
Syntax Description
Command Default
Objects are not tracked for GLBP weighting changes.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
This command ties the weighting of the GLBP gateway to the availability of its interfaces. It is useful for tracking interfaces that are not configured for GLBP.
When a tracked interface goes down, the GLBP gateway weighting decreases by 10. If an interface is not tracked, its state changes do not affect the GLBP gateway weighting. For each GLBP group, you can configure a separate list of interfaces to be tracked.
The optional value argument specifies by how much to decrement the GLBP gateway weighting when a tracked interface goes down. When the tracked interface comes back up, the weighting is incremented by the same amount.
When multiple tracked interfaces are down, the configured weighting decrements are cumulative.
Use the track command to configure each interface to be tracked.
Examples
In the following example, Fast Ethernet interface 0/0 tracks two interfaces represented by the numbers 1 and 2. If interface 1 goes down, the GLBP gateway weighting decreases by the default value of 10. If interface 2 goes down, the GLBP gateway weighting decreases by 5.
interface fastethernet 0/0ip address 10.21.8.32 255.255.255.0glbp 10 weighting track 1glbp 10 weighting track 2 decrement 5Related Commands
glbp weighting
Specifies the initial weighting value of a GLBP gateway.
track
Configures an interface to be tracked.
hw-module reset
To reset a module by turning the power off and then on, use the hw-module reset command in privileged EXEC mode.
hw-module module num reset
Syntax Description
module num
Applies the command to a specific module; see the "Usage Guidelines" section for valid values.
Command Default
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The num argument designates the module number. Valid values depend on the chassis that is used. For example, if you have a 13-slot chassis, valid values for the module number are from 1 to 13.
Examples
This example shows how to reload a specific module:
Router# hw-module module 3 resethw-module sec-cpu reset
To reset and reload the standby Route Switch Processor (RSP) with the specified Cisco IOS image and to execute the image, use the hw-module sec-cpu reset command in privileged EXEC mode.
hw-module sec-cpu reset
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Before using this command, you must use the hw-module slot image global configuration command to specify a high availability Cisco IOS image to run on the standby RSP. After the high availability image is loaded in the active RSP, use the hw-module sec-cpu reset command to reset and reload the standby RSP with the specified Cisco IOS image and to execute the image. To load the standby RSP with the default micro-IOS software contained in the active RSP image instead of a high availability Cisco IOS image, use the no form of the hw-module slot image command followed by the hw-module sec-cpu reset command.
Examples
The following example shows a Cisco 7513 router with the standby RSP loaded in slot 7. The standby RSP is reset and reloaded with the rsp-pv-mz high availability Cisco IOS image. Both RSPs have slot 0 flash memory cards.
Router(config)# hw-module slot 7 image slot0:rsp-pv-mzRouter(config)# endRouter# hw-module sec-cpu resetRelated Commands
hw-module slot image
Specifies a high availability Cisco IOS image to run on an active or standby RSP.
ip multicast rpf backoff
To configure the intervals at which Protocol Independent Multicast (PIM) Reverse Path Forwarding (RPF) failover will be triggered by changes in the routing tables, use the ip multicast rpf backoff command in global configuration mode. To set the triggered RPF check to the default values, use the no form of this command.
ip multicast rpf backoff minimum maximum [disable]
no ip multicast rpf backoff minimum maximum [disable]
Syntax Description
Command Default
This command is enabled by default.
minimum: 500 ms.
maximum: 5000 ms.Command Modes
Global configuration
Command History
Usage Guidelines
In an unstable unicast routing environment that uses triggered RPF checks, the environment could be constantly triggering RPF checks, which places a burden on the resources of the router. To avoid this problem, use the ip multicast rpf backoff command to prevent a second triggered RPF check from occurring for the length of time configured. That is, the PIM "backs off" from another triggered RPF check for a minimum amount of milliseconds as configured by the user.
If the backoff period expires without further routing table changes, PIM then scans for routing changes and accordingly establishes multicast RPF changes. However, if more routing changes occur during the backoff period, PIM doubles the backoff period to avoid overloading the router with PIM RPF changes while the routing table is still converging.
Note
The maximum argument is used to configure the maximum backoff interval. The backoff time is reset to the time configured by the minimum argument if an entire backoff interval has expired without routing changes.
The maximum argument default allows the RPF change behavior to be backward-compatible, allowing a 5-second RPF check interval in case of frequent route changes and a 500-ms RPF check interval in stable networks with only unplanned routing changes. Before the introduction of the ip multicast rpf backoff command, PIM polled the routing tables for changes every 5 seconds.
You likely need not change the defaults of the ip multicast rpf backoff command unless you have frequent route changes in your router (for example, on a dial-in router). Changing the defaults can allow you to reduce the maximum RPF check interval for faster availability of IP multicast on newly established routes or to increase the maximum RPF check interval to reduce the CPU load caused by the RPF check.
Examples
The following example shows how to set the minimum backoff interval to 100 ms and the maximum backoff interval to 2500 ms:
ip multicast rpf backoff 100 2500ip multicast rpf interval
To modify the intervals at which periodic Reverse Path Forwarding (RPF) checks occur, use the ip multicast rpf interval command in global configuration mode. To return to the default interval, use the no form of this command.
ip multicast rpf interval seconds [list access-list | route-map route-map]
no ip multicast rpf interval seconds [list access-list | route-map route-map]
Syntax Description
Command Default
This command is enabled by default.
seconds: 10Command Modes
Global configuration
Command History
Usage Guidelines
You can configure multiple instances of this command by using an access list or a route map.
Note
Examples
The following example shows how to set the periodic RPF check interval to 10 seconds:
ip multicast rpf interval 10The following example shows how to set the periodic RPF check interval for groups that are defined by access list 10 to 3 seconds:
ip multicast rpf interval 3 list 10The following example shows how to set the periodic RPF check interval for groups that are defined by the route map named map to 2 seconds:
ip multicast rpf interval 2 route-map mapRelated Commands
ip igmp query-interval
Configures the frequency at which the Cisco IOS software sends IGMP host hello messages.
ip ospf bfd
To enable Bidirectional Forwarding Detection (BFD) on a specific interface configured for Open Shortest Path First (OSPF), use the ip ospf bfd command in interface configuration mode. To disable BFD on the OSPF interface, use the disable keyword. To remove the ospf bfd command, use the no form of this command.
ip ospf bfd [disable]
no ip ospf bfd
Syntax Description
Defaults
When the disable keyword is not used, the default behavior is to enable BFD support for OSPF on the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
Enter the ip ospf bfd command to configure an OSPF interface to use BFD for failure detection. If you have used the bfd-all interfaces command in router configuration mode to globally configure all OSPF interfaces for an OSPF process to use BFD, you can enter the ip ospf bfd command in interface configuration mode with the disable keyword to disable BFD for a specific OSPF interface.
Examples
In the following example, the interface associated with OSPF, Fast Ethernet interface 3/0, is configured for BFD:
Router> enableRouter# configure terminalRouter(config)# interface fastethernet 3/0Router(config-if)# ip ospf bfdRouter(config-if)# endRelated Commands
ip ospf resync-timeout
To configure how long the router will wait before taking a neighbor adjacency down if the out-of-band resynchronization (oob-resync) has not taken place since the time a restart signal (Open Shortest Path First [OSPF] hello packet with RS-bit set) was received from the neighbor, use the ip ospf resync-timeout command in interface configuration mode. To restore the default value, use the no form of this command.
ip ospf resync-timeout seconds
no ip ospf resync-timeout
Syntax Description
Command Default
The default value is 40 seconds or the value set for the interface's OSPF dead interval, whichever is greater.
Command Modes
Interface configuration
Command History
Usage Guidelines
When an OSPF nonstop forwarding (NSF) router performs a route processor (RP) switchover, it notifies its neighbors, via a special hello packet, of such action and requests that each neighbor help resynchronize the Link State Database.
When a neighbor (that is NSF-aware) receives the special hello packet from the NSF-capable router, it starts a resync timeout timer and waits to synchronize its database with the NSF-capable router. If the NSF-capable router does not initiate the database resynchronization process before the resync-timeout timer expires, the NSF-aware neighbor will take down the adjacency with the NSF-capable router.
By default, the resync-timeout timer is set to 40 seconds or the dead interval of the interface, whichever is greater. (By default, the dead interval is 4 times the hello interval; the hello interval defaults to 10 seconds for Ethernet or 30 seconds for nonbroadcast.) The ip ospf resync-timeout command allows the resync-timeout to be changed and independent of the dead interval or default value.
Examples
This example sets the OSPF resync-timeout interval to 50 seconds:
interface GigabitEthernet 6/0/0ip ospf resync-timeout 50Related Commands
ip pim query-interval
To configure the frequency of Protocol Independent Multicast (PIM) query (hello) messages, use the ip pim query-interval command in interface configuration mode. To return to the default interval, use the no form of this command.
ip pim query-interval period [msec]
no ip pim query-interval
Syntax Description
Command Default
PIM hello (query) messages are sent every 30 seconds.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to configure the frequency of PIM neighbor discovery messages. By default these messages are sent once every 30 seconds. In PIM Version 1 (PIMv1), these messages are referred to as PIM query messages; in PIM Version 2 (PIMv2), these messages are referred to as PIM hello messages. By default, routers run PIMv2 and send PIM hello messages. A router will change (auto-fallback) to PIMv1 and will send PIM query messages if it detects a neighboring router that only supports PIMv1. As soon as that neighboring PIMv1 router is removed from the network, the router will revert to PIMv2.
Note
Note
PIM neighbor discovery messages are used to determine which router on a network is acting as the Designated Router (DR) for PIM sparse mode (PIM-SM) and Source Specific Multicast (SSM). The DR is responsible for joining PIM-SM and SSM groups receiving multicast traffic from sources requested by receivers (hosts). In addition, in PIM-SM, the DR is also responsible for registering local sources with the RP. If the DR fails, a backup router will become the DR and then forward traffic for local receivers and register local sources.
The period argument is used to specify the PIM hello (query) interval. The interval determines the frequency at which PIM hello (query) messages are sent.
Note
The configured PIM hello interval also determines the holdtime used by a PIM router. The Cisco IOS software calculates the holdtime as follows:
3 * the interval specified for the period argument
By default, PIM routers announce the holdtime in PIM hello (query) messages.If the holdtime expires and another router has not received another hello (query) message from this router, it will timeout the PIM neighbor. If the timed out router was the DR, the timeout will trigger DR election. By default, the DR-failover interval occurs after 90 seconds (after the default holdtime expires for a DR). To reduce DR-failover time in redundant networks, a lower value for the period argument can be configured on all routers. The minimum DR-failover time that can be configured (in seconds) is 3 seconds (when the period argument is set to 1 second). The DR-failover time can be reduced to less than 3 seconds if the msecs keyword is specified. When the msecs keyword is used with the ip pim query-interval command, the value specified for the period argument is interpreted as a value in milliseconds (instead of seconds). By enabling a router to send PIM hello messages more often, this functionality allows the router to discover unresponsive neighbors more quickly. As a result, the router can implement failover or recovery procedures more efficiently
Note
Examples
The following example shows how to set the PIM hello interval to 45 seconds:
interface FastEthernet0/1ip pim query-interval 45The following example shows how to set the PIM hello interval to 100 milliseconds:
interface FastEthernet0/1ip pim query-interval 100 msecRelated Commands
show ip pim neighbor
Displays information about PIM neighbors discovered by PIMv1 router query messages or PIMv2 hello messages
ip rsvp signalling hello (configuration)
To enable Hello globally on the router, use the ip rsvp signalling hello command in global configuration mode. To disable Hello globally on the router, use the no form of this command.
ip rsvp signalling hello
no ip rsvp signalling hello
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Global configuration
Command History
Usage Guidelines
To enable Hello globally on the router, you must enter this command. You also must enable Hello on the interface.
Examples
In the following example, Hello is enabled globally on the router:
Router(config)# ip rsvp signalling helloRelated Commands
ip rsvp signalling hello (interface)
To enable hello on an interface where you need Fast Reroute protection, use the ip rsvp signalling hello command in interface configuration mode. To disable hello on an interface where you need Fast Reroute protection, use the no form of this command
ip rsvp signalling hello
no ip rsvp signalling hello
Syntax Description
This command has no arguments or keywords.
Command Default
No hellos are enabled.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
You must configure hello globally on a router and on the specific interface.
Examples
In the following example, hello is enabled on an interface:
Router(config-if)# ip rsvp signalling helloRelated Commands
ip rsvp signalling hello dscp
To set the differentiated services code point (DSCP) value that is in the IP header of a Resource Reservation Protocol (RSVP) traffic engineering (TE) hello message sent from an interface, use the ip rsvp signalling hello dscp command in interface configuration mode. To set the DSCP value to its default, use the no form of this command.
ip rsvp signalling hello [fast-reroute] dscp num
no ip rsvp signalling hello [fast-reroute] dscp
Syntax Description
fast-reroute
(Optional) Initiates Fast Reroute capability.
num
DSCP value. Valid values are from 0 to 63.
Command Default
The default DSCP value is 48.
Command Modes
Interface configuration
Command History
Usage Guidelines
If a link is congested, it is recommended that you set the DSCP to a value higher than 0 to reduce the likelihood that hello messages will be dropped.
You configure the DSCP per interface, not per flow.
The DSCP applies to the RSVP hellos created on a specific interface. You can configure each interface independently for DSCP.
If you issue the ip rsvp signalling hello dscp command without the optional fast-reroute keyword, the command applies to Fast Reroute hellos. This command is provided for backward compatibility; however, we recommend that you use the ip rsvp signalling hello fast-reroute dscp command.
Examples
In the following example, hello messages sent from this interface have a DSCP value of 30 and Fast Reroute capability is enabled by specifying the fast-reroute keyword:
Router(config-if)# ip rsvp signalling hello fast-reroute dscp 30In the following example, hello messages sent from this interface have a DSCP value of 30 and Fast Reroute capability is enabled by default:
Router(config-if)# ip rsvp signalling hello dscp 30Related Commands
ip rsvp signalling hello refresh interval
To configure the Resource Reservation Protocol (RSVP) traffic engineering (TE) hello refresh interval, use the ip rsvp signalling hello refresh interval command in interface configuration mode. To set the refresh interval to its default value, use the no form of this command.
ip rsvp signalling hello [fast-reroute] refresh interval interval-value
no ip rsvp signalling hello [fast-reroute] refresh interval
Syntax Description
Command Default
The default frequency at which a node sends hello messages to a neighbor is 1000 milliseconds (10 seconds).
Command Modes
Interface configuration
Command History
Usage Guidelines
You can configure the hello request interval on a per-interface basis. A node periodically generates a hello message containing a Hello Request object for each neighbor whose status is being tracked. The frequency of those hello messages is determined by the hello interval.
If you issue the ip rsvp signalling hello refresh interval command without the optional fast-reroute keyword, the command applies to Fast Reroute hellos. This command is provided for backward compatibility; however, we recommend that you use the ip rsvp signalling hello fast-reroute refresh interval command.
Examples
In the following example, hello requests are sent to a neighbor every 5000 milliseconds and Fast Reroute capability is enabled by specifying the fast-reroute keyword:
Router(config-if)# ip rsvp signalling hello fast-reroute refresh interval 5000In the following example, hello requests are sent to a neighbor every 5000 milliseconds and Fast Reroute capability is enabled by default:
Router(config-if)# ip rsvp signalling hello refresh interval 5000Related Commands
ip rsvp signalling hello refresh misses
To specify how many Resource Reservation Protocol (RSVP) traffic engineering (TE) hello acknowledgments a node can miss in a row before the node considers that communication with its neighbor is down, use the ip rsvp signalling hello refresh misses command in interface configuration mode. To return the missed refresh limit to its default value, use the no form of this command.
ip rsvp signalling hello [fast-reroute] refresh misses msg-count
no ip rsvp signalling hello [fast-reroute] refresh misses
Syntax Description
Command Default
The default number of sequential hello acknowledgments is 4.
Command Modes
Interface configuration
Command History
Usage Guidelines
A hello comprises a hello message, a Hello Request object, and a Hello ACK object. Each request is answered by an acknowledgment. If a link is very congested or a router has a very heavy load, set this number to a value higher than the default value to ensure that hello does not falsely declare that a neighbor is down.
If you issue the ip rsvp signalling hello refresh misses command without the optional fast-reroute keyword, the command applies to Fast Reroute hellos and Fast Reroute capability is enabled by default. This command is provided for backward compatibility; however, we recommend that you use the ip rsvp signalling hello fast-reroute refresh misses command.
Examples
In the following example, if the node does not receive five hello acknowledgments in a row, the node declares that its neighbor is down and Fast Reroute is enabled by specifying the fast-reroute keyword:
Router(config-if)# ip rsvp signalling hello fast-reroute refresh misses 5In the following example, if the node does not receive five hello acknowledgments in a row, the node declares that its neighbor is down and Fast Reroute is enabled by default:
Router(config-if)# ip rsvp signalling hello refresh misses 5Related Commands
ip rsvp signalling hello dscp
Sets the DSCP value in hello messages.
ip rsvp signalling hello refresh interval
Sets the refresh interval in hello messages.
ip rsvp signalling hello statistics
To enable Hello statistics on the router, use the ip rsvp signalling hello statistics command in global configuration mode. To disable Hello statistics on the router, use the no form of this command.
ip rsvp signalling hello statistics
no ip rsvp signalling hello statistics
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Global configuration
Command History
Examples
In the following example, Hello statistics are enabled on the router:
Router(config)# ip rsvp signalling hello statisticsRelated Commands
ip vrf
To define a VPN routing and forwarding (VRF) instance and to enter VRF configuration mode, use the ip vrf command in global configuration mode. To remove a VRF instance, use the no form of this command.
ip vrf vrf-name
no ip vrf vrf-name
Syntax Description
Command Default
No VRFs are defined. No import or export lists are associated with a VRF. No route maps are associated with a VRF.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The ip vrf vrf-name command creates a VRF instance named vrf-name. To make the VRF functional, a route distinguisher (RD) must be created using the rd route-distinguisher command in VRF configuration mode. The rd route-distinguisher command creates the routing and forwarding tables and associates the RD with the VRF instance named vrf-name.
Examples
The following example shows how to import a route map to a VRF instance named VPN1:
ip vrf vpn1rd 100:2route-target both 100:2route-target import 100:1Related Commands
ip vrf forwarding (interface configuration)
To associate a Virtual Private Network (VPN) routing and forwarding (VRF) instance with an interface or subinterface, use the ip vrf forwarding command in interface configuration mode. To disassociate a VRF, use the no form of this command.
ip vrf forwarding vrf-name [downstream vrf-name2]
no ip vrf forwarding vrf-name [downstream vrf-name2]
Syntax Description
Defaults
The default for an interface is the global routing table.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to associate an interface with a VRF. Executing this command on an interface removes the IP address. The IP address should be reconfigured. The downstream keyword is available on supported platforms with virtual interfaces. The downstream keyword associates the interfaces with a downstream VRF, which enables half duplex VRF functionality on the interface. Some functions operate in the upstream VRFs, and others operate in the downstream VRFs. The following functions operate in the downstream VRFs:
–
–
–
Examples
The following example shows how to link a VRF to ATM interface 0/0:
Router(config)# interface atm0/0Router(config-if)# ip vrf forwarding vpn1The following example associates the VRF named U with the virtual-template 1 interface and specifies the downstream VRF named D:
Router> enableRouter# configure terminalRouter(config)# interface virtual-template 1Router(config-if)# ip vrf forwarding U downstream DRouter(config-if)# ip unnumbered Loopback1Related Commands
ip route vrf
Establishes static routes for a VRF.
ip vrf
Configures a VRF routing table.
ip vrf forwarding (server-group)
To configure the Virtual Private Network (VPN) routing and forwarding (VRF) reference of an authentication, authorization, and accounting (AAA) RADIUS or TACACS+ server group, use the ip vrf forwarding command in server-group configuration mode. To enable server groups to use the global (default) routing table, use the no form of this command.
ip vrf forwarding vrf-name
no ip vrf forwarding vrf-name
Syntax Description
Command Default
Server groups use the global routing table.
Command Modes
Server-group configuration (server-group)
Command History
Usage Guidelines
Use the ip vrf forwarding command to specify a VRF for a AAA RADIUS or TACACS+ server group. This command enables dial users to utilize AAA servers in different routing domains.
Examples
The following example shows how to configure the VRF user to reference the RADIUS server in a different VRF server group:
aaa group server radius sg_globalserver-private 172.16.0.0 timeout 5 retransmit 3!aaa group server radius sg_waterserver-private 10.10.0.0 timeout 5 retransmit 3 key waterip vrf forwarding waterThe following example shows how to configure the VRF user to reference the TACACS+ server in the server group tacacs1:
aaa group server tacacs+tacacs1server-private 10.1.1.1 port 19 key ciscoip vrf forwarding ciscoip tacacs source-interface Loopback0ip vrf ciscord 100:1interface Loopback0ip address 10.0.0.2 255.0.0.0ip vrf forwarding ciscoRelated Commands
isis bfd
To enable or disable Bidirectional Forwarding Detection (BFD) on a specific interface configured for Intermediate System-to-Intermediate System (IS-IS), use the isis bfd command in interface configuration mode. To disable BFD on the IS-IS interface, use the disable keyword. To remove the isis bfd command, use the no form of this command.
isis bfd [disable]
no isis bfd
Syntax Description
Defaults
When the disable keyword is not used, the default behavior is to enable BFD support for IS-IS on the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
Enter the isis bfd command in interface mode to configure an IS-IS interface to use BFD for failure detection. If you have used the bfd-all interfaces command in router configuration mode to globally configure all IS-IS interfaces for an IS-IS process to use BFD, you can enter the isis bfd command with the disable keyword in interface configuration mode to disable BFD for a specific IS-IS interface.
Entering the no isis bfd command will remove the command. In that case, whether or not an IS-IS interface for a particular IS-IS process is registered with the BFD protocol will depend on whether or not you have entered the bfd all-interfaces command in router configuration mode for the specific IS-IS process.
Examples
In the following example, the interface associated with OSPF, Fast Ethernet interface 3/0, is configured for BFD:
Router> enableRouter# configure terminalRouter(config)# interface fastethernet 3/0Router(config-if)# isis bfdRouter(config-if)# endRelated Commands
ispf
To enable incremental shortest path first (SPF), use the ispf command in router configuration mode. To disable incremental SPF, use the no form of this command.
ispf {level-1 | level-2 | level-1-2} [seconds]
no ispf
Syntax Description
Command Default
Incremental SPF is disabled.
seconds: 120Command Modes
Router configuration
Command History
Usage Guidelines
Intermediate System-to-Intermediate System (IS-IS) and Open Shortest Path First (OSPF) use Dijkstra's SPF algorithm to compute the shortest path tree (SPT). During the computation of the SPT, the shortest path to each node is discovered. The topology tree is used to populate the routing table with routes to IP networks. When changes to a Type 1 or Type 2 link-state advertisement (LSA) occur in an area, the entire SPT is recomputed. In many cases, the entire SPT need not be recomputed because most of the tree remains unchanged. Incremental SPF allows the system to recompute only the affected part of the tree. Recomputing only a portion of the tree rather than the entire tree results in faster OSPF convergence and saves CPU resources. Note that if the change to a Type 1 or Type 2 LSA occurs in the calculating router itself, then the full SPT is performed.
Incremental SPF computes only the steps needed to apply the changes in the network topology diagram. That process requires that the system keep more information about the topology in order to apply the incremental changes. Also, more processing must be done on each node for which the system receives a new link-state packet (LSP). However, incremental SPF typically reduces demand on CPU.
Incremental SPF is scheduled in the same way as the full SPF. Routers enabled with incremental SPF and routers not enabled with incremental SPF can function in the same internetwork.
Incremental SPF works only for IPv4.
Even if incremental SPF is configured, there are some cases where full SPF is executed; for example, periodic SPF, a calculation change for the routing calculation (such as a change in metric, is-type, and so on), the configuration of the clear ip route or clear isis commands, or adjacency changes.
Examples
The following example enables OSPF incremental SPF:
Router(config)# router ospf 1Router(config-router)# ispf level-1The following examples enables IS-IS incremental SPF for Level 1 and Level 2 packets:
Router(config)# router isisRouter(config-router)# ispf level-1-2issu 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 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.
