Cisco Systems RSP8 Router# copy running-config startup-config, Routerconfig# slave sync config

Page 39

Configuring High System Availability

However, automatic synchronization is enabled by default on the RSP. Therefore, unless you have disabled automatic synchronization, or this is the first time you are installing a second RSP, a manual update is not required. For more information about automatic synchronization, see the “Ensuring that Both RSPs Contain the Same Configuration Files” section on page 28 .

Caution When you install a second RSP for the first time, you must immediately configure it using the slave sync config command. This ensures that the new standby RSP is configured consistently with the active RSP. Failure to do so might result in an unconfigured standby RSP taking control of the router when the active RSP fails, rendering the network inoperable.

For additional information about using the slave sync config command, see the “Monitoring and Maintaining HSA Operation” section on page 40 . For more complete HSA configuration information, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and the Cisco IOS Configuration Fundamentals Command Reference publications.

To manually set environment variables on the standby RSP, use the following commands beginning in global configuration mode:

 

Command

Purpose

 

 

 

Step 1

Router(config)# boot system

(Optional) Specifies the system image that the router loads at

 

 

startup and stores it in the BOOT variable in the current running

 

 

configuration.

 

 

Note For a complete syntax description and usage guidelines,

 

 

refer to the Cisco IOS Configuration Fundamentals

 

 

Command Reference publication.

 

 

 

Step 2

Router(config)# boot bootldr file-url

(Optional) Specifies the Flash file system and file name that ROM

 

 

uses at startup and stores it in the BOOTLDR variable in the

 

 

current running configuration

 

 

 

Step 3

Router(config)# boot config file-url

(Optional) Specifies the location of the configuration file that the

 

 

router uses at startup and stores it in the CONFIG_FILE

 

 

environment variable in the current running configuration.

 

 

 

Step 4

Router(config)# end

Exits global configuration mode and returns you to privileged

 

 

EXEC configuration mode.

 

 

 

Step 5

Router# copy running-config startup-config

Saves the current running configuration settings to the startup

 

 

configuration. This also puts the information under the RSP’s

 

 

ROM monitor control.

 

 

 

Step 6

Router# show bootvar

Verifies the environment variable settings.

 

 

 

Step 7

Router# configure terminal

Enters global configuration mode.

 

 

 

Step 8

Router(config)# slave sync config

Saves the same environment variables to the standby RSP by

 

 

manually synchronizing their configuration files.

 

 

 

Automatically Setting Environment Variables on the Standby RSP

With automatic synchronization turned on, when you set the active RSP environment variables and save them, the system automatically saves the same environment variables to the standby’s startup configuration.

Route Switch Processor (RSP8) Installation and Configuration Guide

 

OL-4920-02

39

 

 

 

Image 39
Contents Document Contents Cisco.com, Obtaining Documentation, Related DocumentationTopics discussed in this section are Product DescriptionRSP8-Horizontal Front-Panel View Monitoring interface and environmental statusU12 Flash Eprom ROMmon Bus connectors Auxiliary portMemory Components Shows the memory components on the RSP8Type Size Quantity Description Location Flash Memory Cards and Flash Disks There are no user-configurable jumpers on the RSP8Jumpers LEDsPC Card Slots Serial PortsLED Label Color State Indication System Software SpecificationsLists the physical specifications for the RSP8 SpecificationsInstallation Prerequisites Safety GuidelinesSafety Warnings Installation Prerequisites Telephone Wiring Guidelines Electrical Equipment GuidelinesPreventing Electrostatic Discharge Damage Compatibility Requirements Chassis Slot and Dram RequirementsMemory Requirements Hardware Prerequisites Software PrerequisitesMicrocode Requirements List of Parts and ToolsRemoving the RSP8 Installing the RSP8Ejector Levers and Captive Installation Screw Replacing the RSP8 Handling the RSP8 During Removal and Installation Connecting a Console Terminal Connecting to the Auxiliary PortUsing the Y-Cables for Console and Auxiliary Connections Shows the console Y-cable and shows the auxiliary Y-cable Restarting the SystemInstalling the RSP8 Router show version Using the Exec Command Interpreter Configuring the Router for a Single RSP8HSA Active and Standby Operation Configuring High System AvailabilityHSA Implementation Methods HSA System Requirements HSA Configuration Task ListRouter# copy system running-config nvramstartup-config Specifying the Default Standby RSPCommand Purpose Router# configure terminalEnsuring that Both RSPs Contain the Same System Image Router# show controller cbus Ensuring that Both RSPs Contain the Same Microcode ImageRouter# dir slavebootflash slaveslot0 slaveslot1 Router# copy bootflashfilename slot0filenameSlot1filename slavebootslotfilename Router# copy source bootflash slot0 slot1 Determines whether the standby RSP contains the sameCopies a different system image to the active RSP Upgrading to a New Software Version Example Bootflash Now view the standby software image location and versionRouter# copy tftp slot0rsp-pv-mz.120-22.3.S1 Routerconfig# boot system tftp rsp-pv-mz.120-23.S Routerconfig# config-register 0x010FBacking Up with an Older Software Version Example ANB Router# show bootflash Delete the rsp-pv-mz.120-22.3.S1image from the standby RSPRouter# delete slaveslot0rsp-pv-mz.120-22.3.S1 Router# copy system running-config startup-config Manually Setting Environment Variables on the Standby RSPRouterconfig# slave sync config Router# copy running-config startup-configSpecifies which image the standby runs Routerconfig# hw-module slot imageMonitoring and Maintaining HSA Operation Information under that RSP’s ROM monitor controlEnabling High Availability Features High Availability Feature OverviewRouter# slave sync config Enabling High Availability Features Hardware and Software Prerequisites Installation ProceduresThis completes the procedure to enable the router Enabling the RouterCopying an Image onto an RSP Router# copy tftp slaveslot slot-number Router# copy tftp slot slot-numberRouter# show version Setting the Config-Register Boot VariableConfiguring RPR and RPR+ Routerconfig# boot system flashRouter# hw-module sec-cpu reset Routerconfig# hw-module slot slot-numberimage file-specConfiguring RPR and RPR+ Example Verifying RPR and RPR+Router# show redundancy Configuring a Stateful Switchover SSO Saves the configuration changes to the startup Configuration fileVerifying SSO Router# show redundancy client Router# show redundancy states my state = 13 -ACTIVEConfiguring Nonstop Forwarding NSF Configuring CEF NSFConfiguring BGP NSF Graceful-restart Configuring Ospf NSFConfiguring IS-IS NSF As-numberSeconds adjacency Verifying CEF NSFRouter# show ip bgp neighbors Verifying BGP NSFVerifying IS-IS NSF Running-config commandThis example, note the presence of NSF restart enabled Verifying Ospf NSFNetworking device NSF Troubleshooting Tips Troubleshooting NSF FeaturesIS-IS NSF Configuration Example BGP NSF Configuration ExampleBGP NSF Neighbor Device Configuration Example Ospf NSF Configuration ExamplePerforming a Fast Software Upgrade Routerconfig# hw-module slot slot-number image Specifies the image to be used by the standby RSP atName of the image of the standby RSP Routerconfig# service single-slot-reload-enable Configuring SlcrFast Software Upgrade Example Router# redundancy force-switchoverDisabling Slcr RPR, RPR+, SSO, and FSU Troubleshooting TipsSlcr Configuration Example Slcr Troubleshooting TipsVerifying LEDs Troubleshooting the InstallationSystem Power LEDs Monitoring and Maintaining the Active and Standby RSPsNormal RSP8 LEDsVerifying System Startup Sequence Troubleshooting the Installation Troubleshooting a Failed RSP8 Troubleshooting a Router That is Failing to BootDisplaying a Stack Trace of an RSP Maintenance InformationSaving and Retrieving a Configuration File Reloading a Failed RSPRouter# ping Using the ping Command to Ensure ConnectivityCopy to this file Copying the Configuration FileSection on page 24 to enable the privileged level Might include the name or address of a default file serverRouter# show startup-config Retrieving the Configuration File Replacing and Upgrading Dram DIMMs Sdram Dimm Product Numbers Quantity Dram Sockets TotalsPolarization notch Removing DIMMsInserting the Dimm Installing New DIMMsChecking the RSP Memory Upgrade Recovering a Lost PasswordInitialize the router using the i command as follows Console Port Signals Pin Signal Direction DescriptionReference Information Auxiliary Port Signals Female DB-25 Pins Male DB-25 Pins Signal DescriptionConsole and Auxiliary Y-Cable Pinouts P1-7 J1-7 and J2-7 Ground P1-8 J1-8 and J2-8 Software Configuration Register SettingsMale DB-25 Pins Female DB-25 Pins Signal Description P1-5 J1-5 and J2-5Bit Number Hexadecimal Meaning Boot Field MeaningStays at the system bootstrap prompt Boots the first system image in onboard Flash memoryTftp flash filename Changing SettingsRouterconfig# config-register 0xvalue Bit MeaningsAction/Filename Bit Baud Bit Enabling a Boot from Flash MemoryRouterconfig# boot system flash devicefilename Bit Address net hostEnabling a Boot from the Flash Disk Cisco.com Using Flash MemorySystem# copy running-config startup-config Obtaining DocumentationDocumentation Feedback Obtaining Technical AssistanceDocumentation CD-ROM Ordering DocumentationTAC Case Priority Definitions Cisco TAC Website Opening a TAC CaseObtaining Additional Publications and Information Copyright 2004 Cisco Systems, Inc. All rights reserved