- Preface
- Product Overview
- Configuring the Router for the First Time
- Configuring a Supervisor Engine 720
- Configuring a Route Switch Processor 720
- Configuring NSF with SSO Supervisor Engine Redundancy
- ISSU and eFSU on Cisco 7600 Series Routers
- Configuring RPR and RPR+ Supervisor Engine Redundancy
- Configuring Interfaces
- Configuring a Supervisor Engine 32
- Configuring LAN Ports for Layer 2 Switching
- Configuring Flex Links
- Configuring EtherChannels
- Configuring VTP
- Configuring VLANs
- Configuring Private VLANs
- Configuring Cisco IP Phone Support
- Configuring IEEE 802.1Q Tunneling
- Configuring Layer 2 Protocol Tunneling
- Configuring L2TPv3
- Configuring STP and MST
- Configuring Optional STP Features
- Configuring Layer 3 Interfaces
- Configuring GTP-SLB IPV6 Support
- IP Subscriber Awareness over Ethernet
- Configuring UDE and UDLR
- Configuring Multiprotocol Label Switching on the PFC
- Configuring IPv4 Multicast VPN Support
- Configuring Multicast VPN Extranet Support
- Configuring IP Unicast Layer 3 Switching
- Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching
- Configuring IPv4 Multicast Layer 3 Switching
- Configuring MLDv2 Snooping for IPv6 Multicast Traffic
- Configuring IGMP Snooping for IPv4 Multicast Traffic
- Configuring PIM Snooping
- Configuring Network Security
- Understanding Cisco IOS ACL Support
- Configuring VRF aware 6RD Tunnels
- Configuring VLAN ACLs
- Private Hosts (Using PACLs)
- Configuring IPv6 PACL
- IPv6 First-Hop Security Features
- Configuring Online Diagnostics
- Configuring Denial of Service Protection
- Configuring DHCP Snooping
- Configuring Dynamic ARP Inspection
- Configuring Traffic Storm Control
- Unknown Unicast Flood Blocking
- Configuring PFC QoS
- Configuring PFC QoS Statistics Data Export
- Configuring MPLS QoS on the PFC
- Configuring LSM MLDP based MVPN Support
- Configuring IEEE 802.1X Port-Based Authentication
- Configuring IEEE 802.1ad
- Configuring Port Security
- Configuring UDLD
- Configuring NetFlow and NDE
- Configuring Local SPAN, RSPAN, and ERSPAN
- Configuring SNMP IfIndex Persistence
- Power Management and Environmental Monitoring
- Configuring Web Cache Services Using WCCP
- Using the Top N Utility
- Using the Layer 2 Traceroute Utility
- Configuring Bidirectional Forwarding and Detection over Switched Virtual Interface
- Configuring Call Home
- Configuring IPv6 Policy Based Routing
- Using the Mini Protocol Analyzer
- Configuring Resilient Ethernet Protocol
- Configuring Synchronous Ethernet
- Configuring Link State Tracking
- Configuring BGP PIC Edge and Core for IP and MPLS
- Configuring VRF aware IPv6 tunnels over IPv4 transport
- ISIS IPv4 Loop Free Alternate Fast Reroute (LFA FRR)
- Multicast Service Reflection
- Y.1731 Performance Monitoring
- Online Diagnostic Tests
- Acronyms
- Cisco IOS Release 15S Software Images
- Index
Configuring RPR and RPR+ Supervisor Engine Redundancy
This chapter describes how to configure supervisor engine redundancy using route processor redundancy (RPR) and RPR+.
Note ● For complete syntax and usage information for the commands used in this chapter, refer to the Cisco 7600 Series Routers Command References at this URL:
http://www.cisco.com/en/US/products/hw/routers/ps368/prod_command_reference_list.html
- RPR and RPR+ support IPv6 multicast traffic.
- Release 12.2SR does not support single router mode (SRM) with stateful switchover (SSO).
Understanding RPR and RPR+
These sections describe supervisor engine redundancy using RPR and RPR+:
- Supervisor Engine Redundancy Overview
- RPR Operation
- RPR+ Operation
- Supervisor Engine Configuration Synchronization
Supervisor Engine Redundancy Overview
Note See the “Supervisor Engine Redundancy Guidelines and Restrictions” section for important information about supervisor engine redundancy.
Cisco 7600 series routers support fault resistance by allowing a redundant supervisor engine to take over if the primary supervisor engine fails. Cisco 7600 series routers support these redundancy modes:
RPR Operation
RPR supports the following features:
- Auto-startup and bootvar synchronization between active and redundant supervisor engines
- Hardware signals that detect and decide the active or redundant status of supervisor engines
- Clock synchronization every 60 seconds from the active to the redundant supervisor engine
- A redundant supervisor engine that is booted but not all subsystems are up: if the active supervisor engine fails, the redundant supervisor engine become fully operational
- An operational supervisor engine present in place of the failed unit becomes the redundant supervisor engine
- Support for fast software upgrade (FSU) (See the “Performing a Fast Software Upgrade” section.)
When the router is powered on, RPR runs between the two supervisor engines. The supervisor engine that boots first becomes the RPR active supervisor engine. The Multilayer Switch Feature Card and Policy Feature Card become fully operational. The MSFC and PFC on the redundant supervisor engine come out of reset but are not operational.
In a switchover, the redundant supervisor engine become fully operational and the following occurs:
- All switching modules power up again
- Remaining subsystems on the MSFC (including Layer 2 and Layer 3 protocols) are brought up
- Access control lists (ACLs) are reprogrammed into supervisor engine hardware
Note In a switchover, there is a disruption of traffic because some address states are lost and then restored after they are dynamically redetermined.
RPR+ Operation
When RPR+ mode is used, the redundant supervisor engine is fully initialized and configured, which shortens the switchover time. The active supervisor engine checks the image version of the redundant supervisor engine when the redundant supervisor engine comes online. If the image on the redundant supervisor engine does not match the image on the active supervisor engine, RPR redundancy mode is used.
With RPR+, the redundant supervisor engine is fully initialized and configured, which shortens the switchover time if the active supervisor engine fails or if a manual switchover is performed.
When the router is powered on, RPR+ runs between the two supervisor engines. The supervisor engine that boots first becomes the active supervisor engine. The Multilayer Switch Feature Card and Policy Feature Card become fully operational. The MSFC and PFC on the redundant supervisor engine come out of reset but are not operational.
RPR+ enhances RPR by providing the following additional benefits:
Depending on the configuration, the switchover time is 30 or more seconds.
Because both the startup configuration and the running configuration are continually synchronized from the active to the redundant supervisor engine, installed modules are not reloaded during a switchover.
RPR+ allows OIR of the redundant supervisor engine for maintenance. When the redundant supervisor engine is inserted, the active supervisor engine detects its presence and begins to transition the redundant supervisor engine to fully initialized state.
Supervisor Engine Configuration Synchronization
These sections describe supervisor engine configuration synchronization:
- RPR Supervisor Engine Configuration Synchronization
- RPR+ Supervisor Engine Configuration Synchronization
Note Configuration changes made through SNMP are not synchronized to the redundant supervisor engine. After you configure the router through SNMP, copy the running-config file to the startup-config file on the active supervisor engine to trigger synchronization of the startup-config file on the redundant supervisor engine and with RPR+, reload the redundant supervisor engine and MSFC.
RPR Supervisor Engine Configuration Synchronization
During RPR mode operation, the startup-config files and the config-register configurations are synchronized by default between the two supervisor engines. In a switchover, the new active supervisor engine uses the current configuration.
RPR+ Supervisor Engine Configuration Synchronization
With RPR+ mode, the following operations trigger configuration synchronization:
- When a redundant supervisor engine first comes online, the startup-config file is copied from the active supervisor engine to the redundant supervisor engine. This synchronization overwrites any existing startup configuration file on the redundant supervisor engine.
- When configuration changes occur during normal operation, redundancy performs an incremental synchronization from the active supervisor engine to the redundant supervisor engine. Redundancy synchronizes user-entered CLI commands incrementally line-by-line from the active supervisor engine to the redundant supervisor engine.
Even though the redundant supervisor engine is fully initialized, it only interacts with the active supervisor engine to receive incremental changes to the configuration files as they occur. You cannot enter CLI commands on the redundant supervisor engine.
Supervisor Engine Redundancy Guidelines and Restrictions
These sections describe supervisor engine redundancy guidelines and restrictions:
- Redundancy Guidelines and Restrictions
- RPR+ Guidelines and Restrictions
- Hardware Configuration Guidelines and Restrictions
- Configuration Mode Restrictions
Redundancy Guidelines and Restrictions
These guidelines and restrictions apply to RPR and RPR+ redundancy modes:
- With a Supervisor Engine 720, if all the installed switching modules have DFCs, enter the fabric switching-mode allow dcef-only command to disable the Ethernet ports on both supervisor engines, which ensures that all modules are operating in dCEF mode and simplifies switchover to the redundant supervisor engine. (CSCec05612)
Post SRE release, the uplink ports are also enabled in dcef mode for RSP720-10G supervisor engine. The other supervisor engines continue to have the uplink ports disabled.
- Supervisor engine redundancy does not provide supervisor engine mirroring or supervisor engine load balancing. Only one supervisor engine is active at any one time.
- Configuration changes made through SNMP are not synchronized to the redundant supervisor engine. After you configure the router through SNMP, copy the running-config file to the startup-config file on the active supervisor engine to trigger synchronization of the startup-config file on the redundant supervisor engine and with RPR+, reload the redundant supervisor engine and MSFC.
- Supervisor engine switchover takes place after the failed supervisor engine completes a core dump. A core dump can take up to 15 minutes. To get faster switchover time, disable core dump on the supervisor engines.
RPR+ Guidelines and Restrictions
These guidelines and restrictions apply to RPR+:
- Network services are disrupted until the redundant supervisor engine takes over and the router recovers.
- The Forwarding Information Base (FIB) tables are cleared on a switchover. As a result, routed traffic is interrupted until route tables reconverge.
- Static IP routes are maintained across a switchover because they are configured from entries in the configuration file.
- Information about dynamic states maintained on the active supervisor engine is not synchronized to the redundant supervisor engine and is lost on switchover.
These are examples of dynamic state information that is lost at switchover:
– Frame Relay Switched Virtual Circuits (SVCs)
Note Frame Relay-switched DLCI information is maintained across a switchover because Frame Relay-switched DLCI configuration is in the configuration file.
– All terminated TCP and other connection-oriented Layer 3 and Layer 4 sessions
– All Automatic Protection System (APS) state information
- Both supervisor engines must run the same version of Cisco IOS software. If the supervisor engines are not running the same version of Cisco IOS software, the redundant supervisor engine comes online in RPR mode.
- Supervisor engine redundancy does not support nondefault VLAN data file names or locations. Do not enter the vtp file file_name command on a router that has a redundant supervisor engine.
- Before installing a redundant supervisor engine, enter the no vtp file command to return to the default configuration.
- Supervisor engine redundancy does not support configuration entered in VLAN database mode. Use global configuration mode with RPR+ redundancy (see Chapter 14, “Configuring VLANs”).
Hardware Configuration Guidelines and Restrictions
For redundant operation, the following guidelines and restrictions must be met:
- Cisco IOS software running on the supervisor engine and the MSFC supports redundant configurations where the supervisor engines and MSFC routers are identical. If they are not identical, one will boot first and become active and hold the other supervisor engine and MSFC in a reset condition.
- Each supervisor engine must have the resources to run the router on its own, which means all supervisor engine resources are duplicated, including all Flash devices.
- Make separate console connections to each supervisor engine. Do not connect a Y cable to the console ports.
- Both supervisor engines must have the same system image (see the “Copying Files to the Redundant Supervisor Engine” section).
Note If a newly installed redundant supervisor engine has the Catalyst operating system installed, remove the active supervisor engine and boot the router with only the redundant supervisor engine installed. Follow the procedures in the current release notes to convert the redundant supervisor engine from the Catalyst operating system.
- The configuration register in the startup-config must be set to autoboot (see the Cisco IOS Configuration Fundamentals Configuration Guide for more information).
Note There is no support for booting from the network.
Configuration Mode Restrictions
The following configuration restrictions apply during the startup synchronization process:
- You cannot perform configuration changes during the startup (bulk) synchronization. If you attempt to make configuration changes during this process, the following message is generated:
Configuring Supervisor Engine Redundancy
These sections describe how to configure supervisor engine redundancy:
- Configuring Redundancy
- Synchronizing the Supervisor Engine Configurations
- Displaying the Redundancy States
Configuring Redundancy
To configure redundancy, perform this task:
|
|
|
---|---|---|
Configures RPR or RPR+. When this command is entered, the redundant supervisor engine is reloaded and begins to work in RPR or RPR+ mode. |
||
This example shows how to configure the system for RPR+ and display the redundancy state:
Synchronizing the Supervisor Engine Configurations
During normal operation, the startup-config and config-registers configuration are synchronized by default between the two supervisor engines. In a switchover, the new active supervisor engine uses the current configuration.
Note Do not change the default auto-sync configuration.
Displaying the Redundancy States
To display the redundancy states, perform this task:
|
|
---|---|
This example shows how to display the redundancy states:
Performing a Fast Software Upgrade
The fast software upgrade (FSU) procedure supported by RPR allows you to upgrade the Cisco IOS software image on the supervisor engines without reloading the system.
Note If you are performing a first-time upgrade to RPR from EHSA, you must reload both supervisor engines. FSU from EHSA is not supported.
To perform an FSU, perform this task:
This example shows how to perform an FSU:
Copying Files to the Redundant Supervisor Engine
Use the following command to copy a file to the disk0: device on a redundant supervisor engine:
Use the following command to copy a file to the bootflash: device on a redundant supervisor engine:
Use the following command to copy a file to the bootflash: device on a redundant MSFC: