Cisco Systems RSP8 manual Using the ping Command to Ensure Connectivity, Router# ping

Page 70

Maintenance Information

Configuration information resides in two places when the router is operating: the startup default (permanent) configuration in NVRAM, and the running (temporary) memory in RAM. The default startup configuration always remains available; NVRAM retains the information even when the power is shut down. The current information is lost if the system power is shut down. The current configuration contains all nondefault configuration information that you added with the configure command, the setup facility, or editing of the configuration file.

The configure command adds the current configuration to the default configuration in NVRAM so that it is also saved when power is shut down. Whenever you make changes to the system configuration, use the copy running-configstartup-configcommand to ensure that the new configuration is saved.

If you replace the RSP8 in a system with only one RSP8, you also replace the entire configuration, which resides in NVRAM on the RSP8. If you copy the configuration file to a remote server before removing the RSP8, you can retrieve it later and write it into NVRAM on the new RSP8. You can also use the copy running-configslot0:config-filecommand to save the configuration file to Flash memory, and then use the copy slot0:config-filenvram:startup-configcommand to restore it.

If you do not copy the configuration file, you must use the configure command or the setup command facility to re-enter the configuration information after you install the new RSP8. For complete descriptions of these two commands, and instructions for using them, refer to the Cisco IOS software documentation.

If you are temporarily removing an RSP8, it is not necessary to copy the configuration file to a remote server; the lithium batteries retain the configuration file in memory until you replace the RSP8 in the system. This procedure requires privileged-level access to the EXEC command interpreter, which usually requires a password. See the “Using the EXEC Command Interpreter” section on page 24 and contact your system administrator to obtain access, if necessary.

For configuration information and support, refer to the Cisco IOS software configuration documentation set that corresponds to the software release installed on your Cisco hardware.

Using the ping Command to Ensure Connectivity

Before you attempt to copy or retrieve a file from a remote host, ensure that the connection is good between the router and the remote server by using the packet internet groper (ping) program. The ping program sends a series of echo request packets to the remote device and waits for a reply. If the connection is good, the remote device echoes them back to the local device.

The console terminal displays the results of each message sent: an exclamation point (!) indicates that the local device received an echo, and a period (.) indicates that the server timed out while awaiting the reply. If the connection between the two devices is good, the system displays a series of exclamation points (! ! !) or [ok]. If the connection fails, the system displays a series of periods (. . .) or [timed out] or [failed].

To verify the connection between the router and a remote host, use the ping command followed by the name or Internet Protocol (IP) address of the remote server; then press Return. Although the ping command supports configurable options, the defaults, including IP as the protocol, are enabled when you enter a host name or address on the same line as the ping command. For a description of the configurable options, refer to the appropriate software documentation.

The following example shows a successful ping operation:

Router# ping 10.1.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/12 ms

The following example shows the results of a failed ping operation:

Route Switch Processor (RSP8) Installation and Configuration Guide

70

OL-4920-02

 

 

Image 70
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 U12Shows the memory components on the RSP8 Memory ComponentsType Size Quantity Description Location LEDs There are no user-configurable jumpers on the RSP8Jumpers Flash Memory Cards and Flash DisksSerial Ports PC Card SlotsLED Label Color State Indication Specifications SpecificationsLists the physical specifications for the RSP8 System SoftwareSafety Guidelines Installation PrerequisitesSafety Warnings Installation Prerequisites Electrical Equipment Guidelines Telephone Wiring GuidelinesPreventing Electrostatic Discharge Damage Chassis Slot and Dram Requirements Compatibility RequirementsMemory 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 Connecting to the Auxiliary Port Connecting a Console TerminalUsing the Y-Cables for Console and Auxiliary Connections 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 cbusRouter# 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 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 runsHigh Availability Feature Overview Enabling High Availability FeaturesRouter# slave sync config Enabling High Availability Features Installation Procedures Hardware and Software PrerequisitesEnabling the Router This completes the procedure to enable the routerCopying an Image onto an RSP 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 resetVerifying 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 states my state = 13 -ACTIVE Router# show redundancy clientConfiguring CEF NSF Configuring Nonstop Forwarding NSFConfiguring BGP 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 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 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 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-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