Cisco Systems RSP8 manual HSA Implementation Methods

Page 26

Configuring High System Availability

If a system crash causes the active RSP8 to fail, the standby RSP8 becomes the new active RSP8 and uses its own system image and configuration file to reboot the router. The failed RSP8 card (now the standby) remains inactive until you perform diagnostics, correct the problem, and then issue the standby reload command.

With HSA operation, use the following guidelines:

The standby RSP8 should have the same boot image, the same ROM monitor, and the same DRAM configuration as the active RSP8. (See the “Hardware Prerequisites” section on page 14 .)

The two RSP8 cards are not required to run the same active software image and configuration file. The standby-mode software is a subset of the active-mode software.

When enabled, automatic synchronization mode automatically ensures that the active and the standby RSP8 cards have the same configuration file. (See the “Ensuring that Both RSPs Contain the Same Configuration Files” section on page 28 .)

The console always connects to the active RSP8, so your view is always from the active RSP’s perspective.

You must not remove the system active RSP8 while the system is operating; however, the system standby RSP8 can be removed while the system is operating.

Caution Removing the active RSP8 while the system is operating might cause the system to crash; however, the system reloads with the standby RSP8 as the new active. To prevent any system problems, do not remove the active RSP8 while the system is operating.

HSA Implementation Methods

The two common ways to use HSA are as follows:

Hardware backup—Protects against an RSP8 card failure. You configure both RSP8 cards with the same software image and configuration information, and you configure the router to automatically synchronize configuration information on both cards when changes occur.

Software error protection—Protects against critical Cisco IOS software errors in a particular release. You configure the RSP8 cards with different software images, but with the same configuration information.

You can also use HSA for advanced implementations. For example, you can configure the RSP8 cards with the following:

Similar software versions, but different configuration files

Different software images and different configuration files

Widely varied configuration files (for example, various features or interfaces can be turned off or on per card)

Note Other, more complex uses of HSA are also possible, but are not addressed in this document. For more information, contact your Cisco service representative.

The following HSA configuration information specifically refers to a Cisco 7513 and Cisco 7513-MX. The primary difference between the Cisco 7507 and Cisco 7507-MX and the Cisco 7513 and

Cisco 7513-MX, with respect to HSA configuration, is that the RSP active and standby slots in the Cisco 7507 and Cisco 7507-MX are slot 2 and slot 3, respectively.

Route Switch Processor (RSP8) Installation and Configuration Guide

26

OL-4920-02

 

 

Image 26
Contents Document Contents Related Documentation Cisco.com, Obtaining Documentation,Product Description Topics discussed in this section areMonitoring interface and environmental status RSP8-Horizontal Front-Panel ViewFlash Eprom ROMmon Bus connectors Auxiliary port U12Type Size Quantity Description Location Memory ComponentsShows the memory components on the RSP8 LEDs There are no user-configurable jumpers on the RSP8Jumpers Flash Memory Cards and Flash DisksLED Label Color State Indication PC Card SlotsSerial Ports Specifications SpecificationsLists the physical specifications for the RSP8 System SoftwareSafety Warnings Installation PrerequisitesSafety Guidelines Installation Prerequisites Preventing Electrostatic Discharge Damage Telephone Wiring GuidelinesElectrical Equipment Guidelines Memory Requirements Compatibility RequirementsChassis Slot and Dram Requirements Software Prerequisites Hardware PrerequisitesList of Parts and Tools Microcode RequirementsInstalling the RSP8 Removing the RSP8Ejector Levers and Captive Installation Screw Replacing the RSP8 Handling the RSP8 During Removal and Installation Using the Y-Cables for Console and Auxiliary Connections Connecting a Console TerminalConnecting to the Auxiliary Port Restarting the System Shows the console Y-cable and shows the auxiliary Y-cableInstalling the RSP8 Router show version Configuring the Router for a Single RSP8 Using the Exec Command InterpreterConfiguring High System Availability HSA Active and Standby OperationHSA Implementation Methods HSA Configuration Task List HSA System RequirementsRouter# configure terminal Specifying the Default Standby RSPCommand Purpose Router# copy system running-config nvramstartup-configEnsuring that Both RSPs Contain the Same System Image Ensuring that Both RSPs Contain the Same Microcode Image Router# show controller cbusSlot1filename slavebootslotfilename Router# dir slavebootflash slaveslot0 slaveslot1Router# copy bootflashfilename slot0filename Copies a different system image to the active RSP Router# copy source bootflash slot0 slot1Determines whether the standby RSP contains the same Upgrading to a New Software Version Example Router# copy tftp slot0rsp-pv-mz.120-22.3.S1 BootflashNow view the standby software image location and version Backing Up with an Older Software Version Example Routerconfig# boot system tftp rsp-pv-mz.120-23.SRouterconfig# config-register 0x010F ANB Router# delete slaveslot0rsp-pv-mz.120-22.3.S1 Router# show bootflashDelete the rsp-pv-mz.120-22.3.S1image from the standby RSP Manually Setting Environment Variables on the Standby RSP Router# copy system running-config startup-configRouter# copy running-config startup-config Routerconfig# slave sync configInformation under that RSP’s ROM monitor control Routerconfig# hw-module slot imageMonitoring and Maintaining HSA Operation Specifies which image the standby runsRouter# slave sync config Enabling High Availability FeaturesHigh Availability Feature Overview Enabling High Availability Features Installation Procedures Hardware and Software PrerequisitesCopying an Image onto an RSP This completes the procedure to enable the routerEnabling the Router Router# copy tftp slot slot-number Router# copy tftp slaveslot slot-numberRouterconfig# boot system flash Setting the Config-Register Boot VariableConfiguring RPR and RPR+ Router# show versionRouterconfig# hw-module slot slot-numberimage file-spec Router# hw-module sec-cpu resetRouter# show redundancy Configuring RPR and RPR+ ExampleVerifying RPR and RPR+ Configuring a Stateful Switchover SSO Verifying SSO Saves the configuration changes to the startupConfiguration file Router# show redundancy states my state = 13 -ACTIVE Router# show redundancy clientConfiguring BGP NSF Configuring Nonstop Forwarding NSFConfiguring CEF NSF As-number Configuring Ospf NSFConfiguring IS-IS NSF Graceful-restartVerifying CEF NSF Seconds adjacencyVerifying BGP NSF Router# show ip bgp neighborsVerifying Ospf NSF Running-config commandThis example, note the presence of NSF restart enabled Verifying IS-IS NSFNetworking device Troubleshooting NSF Features NSF Troubleshooting TipsOspf NSF Configuration Example BGP NSF Configuration ExampleBGP NSF Neighbor Device Configuration Example IS-IS NSF Configuration ExamplePerforming a Fast Software Upgrade Name of the image of the standby RSP Routerconfig# hw-module slot slot-number imageSpecifies the image to be used by the standby RSP at Router# redundancy force-switchover Configuring SlcrFast Software Upgrade Example Routerconfig# service single-slot-reload-enableSlcr Troubleshooting Tips RPR, RPR+, SSO, and FSU Troubleshooting TipsSlcr Configuration Example Disabling SlcrMonitoring and Maintaining the Active and Standby RSPs Troubleshooting the InstallationSystem Power LEDs Verifying LEDsRSP8 LEDs NormalVerifying System Startup Sequence Troubleshooting the Installation Troubleshooting a Router That is Failing to Boot Troubleshooting a Failed RSP8Reloading a Failed RSP Maintenance InformationSaving and Retrieving a Configuration File Displaying a Stack Trace of an RSPUsing the ping Command to Ensure Connectivity Router# pingMight include the name or address of a default file server Copying the Configuration FileSection on page 24 to enable the privileged level Copy to this fileRouter# show startup-config Retrieving the Configuration File Replacing and Upgrading Dram DIMMs Product Numbers Quantity Dram Sockets Totals Sdram DimmRemoving DIMMs Polarization notchInstalling New DIMMs Inserting the DimmRecovering a Lost Password Checking the RSP Memory UpgradeInitialize the router using the i command as follows Reference Information Console Port SignalsPin Signal Direction Description Console and Auxiliary Y-Cable Pinouts Auxiliary Port SignalsFemale DB-25 Pins Male DB-25 Pins Signal Description P1-5 J1-5 and J2-5 Software Configuration Register SettingsMale DB-25 Pins Female DB-25 Pins Signal Description P1-7 J1-7 and J2-7 Ground P1-8 J1-8 and J2-8Boots the first system image in onboard Flash memory Boot Field MeaningStays at the system bootstrap prompt Bit Number Hexadecimal MeaningBit Meanings Changing SettingsRouterconfig# config-register 0xvalue Tftp flash filenameAction/Filename Bit Bit Address net host Enabling a Boot from Flash MemoryRouterconfig# boot system flash devicefilename Baud BitEnabling a Boot from the Flash Disk Obtaining Documentation Using Flash MemorySystem# copy running-config startup-config Cisco.comOrdering Documentation Obtaining Technical AssistanceDocumentation CD-ROM Documentation FeedbackCisco TAC Website Opening a TAC Case TAC Case Priority DefinitionsObtaining Additional Publications and Information Copyright 2004 Cisco Systems, Inc. All rights reserved