Cisco Systems RSP8 manual Router# dir slavebootflash slaveslot0 slaveslot1

Page 31

Configuring High System Availability

 

Command

Purpose

 

 

 

Step 3

Router# dir {slavebootflash: slaveslot0: slaveslot1:}

Determines whether the standby RSP contains the

 

 

same microcode image in the same location.

 

 

 

Step 4

Router# copy {bootflash:[filename] slot0:[filename]

Copies the active’s system image to the appropriate

 

slot1:[filename]} {slavebootslot:[filename]

standby location. Use this command if the standby

 

slaveslot0:[filename] slaveslot1:[filename]}

RSP does not contain the same system image in the

 

Note You might also have to use the delete and/or

same location.

 

 

 

squeeze command in conjunction with the copy

Note Deleted space is not reusable until after you

 

command to accomplish this step.

perform the squeeze command.

 

 

 

The following example ensures that both RSPs have the same microcode image. Notice that slots 0, 1, 4, 9, and 10 load microcode from the bundled software, as noted by the statement “software loaded from system.” The Channel Interface Processor (CIP2) in slot 11 does not use the microcode bundled with the system. Instead, it loads the microcode from slot0:pond/bath/rsp_fsip20-1.Thus, you must ensure that the standby RSP8 has a copy of the same FSIP microcode in the same location.

Router# show controller cbus

MEMD at 40000000, 2097152 bytes (unused 416, recarves 3, lost 0) RawQ 48000100, ReturnQ 48000108, EventQ 48000110

BufhdrQ 48000128 (2948 items), LovltrQ 48000140 (5 items, 1632 bytes) IpcbufQ 48000148 (16 items, 4096 bytes)

3571 buffer headers (48002000 - 4800FF20) pool0: 28 buffers, 256 bytes, queue 48000130 pool1: 237 buffers, 1536 bytes, queue 48000138 pool2: 333 buffers, 4544 bytes, queue 48000150 pool3: 4 buffers, 4576 bytes, queue 48000158

slot0: EIP, hw 1.5, sw 20.00, ccb 5800FF30, cmdq 48000080, vps 4096 software loaded from system

Ethernet0/0, addr 0000.0ca3.cc00 (bia 0000.0ca3.cc00) gfreeq 48000138, lfreeq 48000160 (1536 bytes), throttled 0 rxlo 4, rxhi 42, rxcurr 0, maxrxcurr 2

txq 48000168, txacc 48000082 (value 27), txlimit 27

.........

slot1: FIP, hw 2.9, sw 20.02, ccb 5800FF40, cmdq 48000088, vps 4096

 

software loaded

from system

 

Fddi1/0, addr 0000.0ca3.cc20 (bia 0000.0ca3.cc20)

 

 

gfreeq 48000150, lfreeq 480001C0 (4544 bytes), throttled 0

 

 

rxlo 4, rxhi 165, rxcurr 0, maxrxcurr 0

 

 

txq 480001C8,

txacc 480000B2 (value 0), txlimit 95

 

slot4: AIP, hw 1.3, sw 20.02, ccb 5800FF70, cmdq 480000A0, vps 8192

 

software loaded

from system

 

ATM4/0, applique is SONET (155Mbps)

 

 

gfreeq 48000150, lfreeq 480001D0 (4544 bytes), throttled 0

 

 

rxlo 4, rxhi 165, rxcurr 0, maxrxcurr 0

 

 

txq 480001D8,

txacc 480000BA (value 0), txlimit 95

 

slot9: MIP, hw 1.0, sw 20.02, ccb 5800FFC0, cmdq 480000C8, vps 8192

 

software loaded

from system

 

T1 9/0, applique is Channelized T1

 

 

gfreeq 48000138, lfreeq 480001E0 (1536 bytes), throttled 0

 

 

rxlo 4, rxhi 42, rxcurr 0, maxrxcurr 0

 

 

txq 480001E8,

txacc 480000C2 (value 27), txlimit 27

 

 

 

.......

 

 

 

 

slot

10: TRIP, hw 1.1, sw 20.00, ccb 5800FFD0, cmdq 480000D0, vps 4096

 

software loaded

from system

 

TokenRing10/0, addr 0000.0ca3.cd40 (bia 0000.0ca3.cd40)

 

 

gfreeq 48000150, lfreeq 48000200 (4544 bytes), throttled 0

 

 

rxlo 4, rxhi 165, rxcurr 1, maxrxcurr 1

 

 

txq 48000208,

txacc 480000D2 (value 95), txlimit 95

 

 

 

Route Switch Processor (RSP8) Installation and Configuration Guide

 

 

 

 

 

 

 

 

OL-4920-02

 

 

 

31

 

 

 

 

 

 

Image 31
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 portShows the memory components on the RSP8 Memory ComponentsType Size Quantity Description Location Flash Memory Cards and Flash Disks There are no user-configurable jumpers on the RSP8Jumpers LEDsSerial Ports PC Card SlotsLED Label Color State Indication System Software SpecificationsLists the physical specifications for the RSP8 SpecificationsSafety Guidelines Installation PrerequisitesSafety Warnings Installation Prerequisites Electrical Equipment Guidelines Telephone Wiring GuidelinesPreventing Electrostatic Discharge Damage Chassis Slot and Dram Requirements Compatibility 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 to the Auxiliary Port Connecting a Console TerminalUsing 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# copy bootflashfilename slot0filename Router# dir slavebootflash slaveslot0 slaveslot1Slot1filename slavebootslotfilename Determines whether the standby RSP contains the same Router# copy source bootflash slot0 slot1Copies a different system image to the active RSP Upgrading to a New Software Version Example Now view the standby software image location and version BootflashRouter# copy tftp slot0rsp-pv-mz.120-22.3.S1 Routerconfig# config-register 0x010F Routerconfig# boot system tftp rsp-pv-mz.120-23.SBacking Up with an Older Software Version Example ANB Delete the rsp-pv-mz.120-22.3.S1image from the standby RSP Router# show bootflashRouter# 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 controlHigh Availability Feature Overview Enabling High Availability FeaturesRouter# slave sync config Enabling High Availability Features Hardware and Software Prerequisites Installation ProceduresEnabling the Router This completes the procedure to enable 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-specVerifying RPR and RPR+ Configuring RPR and RPR+ ExampleRouter# show redundancy Configuring a Stateful Switchover SSO Configuration file Saves the configuration changes to the startupVerifying SSO Router# show redundancy client Router# show redundancy states my state = 13 -ACTIVEConfiguring CEF NSF Configuring Nonstop Forwarding 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 Specifies the image to be used by the standby RSP at Routerconfig# hw-module slot slot-number imageName 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 Pin Signal Direction Description Console Port SignalsReference Information Female DB-25 Pins Male DB-25 Pins Signal Description Auxiliary Port SignalsConsole 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