Software Configuration Guide for the Cisco 12000 Series Internet Router
Additional Router Configuration Tasks
Download this chapter
Additional Router Configuration TasksAdditional Router Configuration Tasks
give_us_feedback

Table Of Contents

Additional Configuration Tasks for the
Cisco 12000 Series Internet Router

Configuration Tasks

The Software Configuration Register

Description of the Software Configuration Register

Boot Field Settings

Configuring the Software Configuration Register

Bits in the Software Configuration Register

Recovering a Lost Password

Useful Configuration Commands

Troubleshooting Tips

Field Diagnostics

Upgrading the FPGA Image on a Line Card

Retrieving Information from the Crashinfo File

Monitoring and Maintaining the Cisco 12000 Series Internet Router

Monitoring the Router Configuration

Additional System Monitoring

Monitoring and Maintaining the PRP Software Configuration


Additional Configuration Tasks for the
Cisco 12000 Series Internet Router

This chapter describes additional configuration and troubleshooting tasks for the Cisco 12000 Series Internet Router. It discusses the following subjects:

•Configuration Tasks

•Troubleshooting Tips

•Monitoring and Maintaining the Cisco 12000 Series Internet Router

Configuration Tasks

This section details additional configuration tasks that may need to be performed on your router. The following items are described:

•The Software Configuration Register

•Recovering a Lost Password

•Useful Configuration Commands

The Software Configuration Register

Configuring the software configuration register is described in the following sections:

•Description of the Software Configuration Register

•Boot Field Settings

•Configuring the Software Configuration Register

•Bits in the Software Configuration Register

Description of the Software Configuration Register

The software configuration register is a 16-bit register in NVRAM that you use to define specific system parameters. You can set or change the contents of this register to accomplish the following tasks:

•Define the source for the default Cisco IOS software. You can specify any of the following:

–Flash memory card inserted in PCMCIA slot 0

–TFTP server on the network

–Flash memory SIMM (NVRAM) on the RP

–Boot image stored within the operating environment, which you access by using an appropriate form of the boot command entered at the ROM monitor prompt (rommon>)

•Define a default boot filename.

•Enable or disable the Break function.

•Control broadcast addresses.

•Set the console terminal baud rate.

•Recover a lost password.

•Force an automatic boot using a boot image.

When you first power on the router, a boot image called the RP ROM monitor is executed, resulting in the display of the ROM monitor prompt (Rommon>). At this prompt, you have access to a limited set of commands that enable you to set values in the software configuration register and to perform a number of other tasks.

The RP ROM monitor is loaded into the RP Flash ROM when the RP is manufactured. You can use it to boot the system from local Flash memory devices. The RP ROM monitor software can be upgraded in the field, if necessary.

•Read boot system commands from the configuration file stored in NVRAM.

Table 3-1 defines the bits in the software configuration register.

Table 3-1 Software Configuration Register Bit Meanings

Bit Number1
Hexadecimal Value
Meaning/Function

00 to 03

0x0000 to 0x000F

Comprises the boot field for defining the source of a default Cisco IOS software image required to run the router (see Table 3-2)

06

0x0040

Causes system software to ignore the contents of NVRAM

07

0x0080

Enables the OEM2 bit

08

0x0100

Disables the Break function

09

0x0200

Uses a secondary bootstrap

10

0x0400

Broadcasts Internet Protocol (IP) with all zeros

11 and 12

0x0800 to 0x1000

Defines the console baud rate (the default setting is 9600 bps)

13

0x2000

Boots the default Flash memory software if the network boot fails

14

0x4000

Excludes network numbers from IP broadcasts

15

0x8000

Enables diagnostic messages and ignores the contents of NVRAM

1 The factory default value for the software configuration register is 0x0102. This value is a combination of binary bit 8 = 0x0100 and binary bits 00 through 03 = 0x0002.

2 OEM = original equipment manufacturer.


Note Valid software configuration register values may be combinations of settings, rather than the individual settings listed in Table 3-1. For example, the factory default value 0x0102 for the software configuration register is actually a composite of several settings.

Boot Field Settings

Bits 00 to 03 of the software configuration register are referred to as the boot field, which defines a source for booting the default Cisco IOS software image required to run the router. The value of the boot field is specified as a binary number, as described in Table 3-2.

Table 3-2 Definition of Bits in Boot Field of Software Configuration Register 

Boot Field
Meaning

00

On power up, the system remains at the ROM monitor prompt (rommon>), awaiting a user command to boot the system manually. See the "Manually Booting from a Cisco IOS Software Image" section on page 2-2.

01

On power up, the system automatically boots the first system image found in the onboard Flash memory SIMM on the RP.

02 to 0F

If a valid boot system command is stored in the NVRAM configuration file, the router boots the Cisco IOS software image as directed by that value.

If no boot system command is present in the configuration file, the router forms a default boot filename and attempts to acquire that file from a network TFTP server. To compute the filename of this default image, the router starts with cisco and appends the octal equivalent of the boot field value, a hyphen, and the processor type (grp or prp). Table 3-3 lists the range of possible computed default filenames for booting over the network.

The router would use one of these filenames to boot a default system image stored on a network TFTP server. If the configuration file contains a valid boot system configuration command, the system uses these instructions to boot the system, rather than using the filename it computed from the software configuration register settings.

For this setting, it is assumed that the Ethernet port on the RP is configured and operational.

Note If a bootable Cisco IOS software image exists in a Flash memory card inserted in PCMCIA slot 0 or slot 1, the software configuration register boot field setting is overridden, and the system boots from the Cisco IOS software image in the Flash memory card, rather than from a network TFTP image.


Note Cisco 12000 Series Internet Routers are typically delivered from the factory with a mini-Cisco IOS software boot image in the boot flash and a flash card containing a suitable working Cisco IOS image. If you discover that you need a Cisco IOS upgrade, you should download the appropriate Cisco IOS image from Cisco.com. Refer to the "Upgrading and Backing Up Cisco IOS Software Images and Configuration Files" section on page 2-13.

Configuring the Software Configuration Register

To configure the software configuration register, follow these steps:

 
Command
Purpose

Step 1 

Router> enable

Password: <password>

Enters privileged EXEC mode.

Step 2 

Router# configure terminal

Enters global configuration mode.

Step 3 

Router(config)# config-register 0xvalue

Sets the contents of the software configuration register, where value is a 4-bit hexadecimal number as described in Table 3-1.

Step 4 

Router(config)# ctrl-Z

Exits global configuration mode.

Step 5 

Router# show version 

Displays the software configuration register value currently in 
effect. This is the value that will be used the next time the router 
reloads. The value is displayed on the last line of the display, as 
in the following example:

Configuration register is 0x141 (will be 0x102 at next reload)

Step 6 

Router# copy running-config startup-config

or

Router# write memory 

Saves the software configuration register settings to NVRAM.

Step 7 

Router# reload 

Reboots the router. Configuration register changes take effect 
only after the system reloads.

Bits in the Software Configuration Register

As described in the "Boot Field Settings" section, the boot field setting determines the source of the Cisco IOS software image that is used to boot the router. A detailed description of the bit values for the boot field and their associated action or filename is given in Table 3-3

Table 3-3 Default Boot Filenames 

Action/Filename
Bit 3
Bit 2
Bit 1
Bit 0

Bootstrap mode

0

0

0

0

Default software

0

0

0

1

cisco2-grp or cisco2-prp

0

0

1

0

cisco3-grp or cisco3-prp

0

0

1

1

cisco4-grp or cisco4-prp

0

1

0

0

cisco5-grp or cisco5-prp

0

1

0

1

cisco6-grp or cisco6-prp

0

1

1

0

cisco7-grp or cisco7-prp

0

1

1

1

cisco10-grp or cisco10-prp

1

0

0

0

cisco11-grp or cisco11-prp

1

0

0

1

cisco12-grp or cisco12-prp

1

0

1

0

cisco13-grp or cisco13-prp

1

0

1

1

cisco14-grp or cisco14-prp

1

1

0

0

cisco15-grp or cisco15-prp

1

1

0

1

cisco16-grp or cisco16-prp

1

1

1

0

cisco17-grp or cisco17-prp

1

1

1

1


The remaining bits in the software configuration register are described following:

Bit 8 of the software configuration register controls the console Break key. Setting bit 8 causes the system to ignore the console Break key. This is the factory default. Conversely, clearing bit 8 causes the system to interpret a Break keystroke as a command to halt normal system operation and force the system into ROM monitor mode. Regardless of the setting of the Break enable bit in the software configuration register, pressing the Break key during approximately the first 5 seconds of booting causes a return to the ROM monitor.

Bit 9 is not used.

Bit 10 of the software configuration register controls the host portion of the IP broadcast address. Setting bit 10 causes the processor to use all zeros in the host portion of the IP broadcast address; clearing bit 10 (the factory default) causes the processor to use all ones. Bit 10 interacts with bit 14, which controls the network and subnet portions of the IP broadcast address.

Table 3-4Table 3-4 shows the combined effect of bits 10 and 14.

Table 3-4 Configuration Register Settings for Broadcast Address Destination

Bit 14
Bit 10
Address (<net> <host>)

Off

Off

<ones> <ones>

Off

On

<zeros> <zeros>

On

On

<net> <zeros>

On

Off

<net> <ones>


Bits 11 and 12 of the software configuration register determine the data transmission rate of the console terminal. Table 3-5 Table 3-5 shows the bit settings for the four available data transmission rates. The factory-set default data transmission rate is 9600 bps.

Table 3-5 System Console Terminal Data Transmission Rate Settings 

Bit 12
Bit 11
Data Transmission Rate (bps)

0

0

9600

0

1

4800

1

0

1200

1

1

2400


Bit 13 of the software configuration register determines the system's response to a bootload failure. Setting bit 13 causes the system to load Cisco IOS software from Flash memory after five unsuccessful attempts to load a boot file from the network TFTP server. Clearing bit 13 causes the system to continue attempting to load a boot file from the network TFTP server indefinitely. Bit 13 in the software configuration register is set to 0 as the default at the factory.

Recovering a Lost Password

Note If the enable password is encrypted, the following procedure will not work for password recovery, and you will have to reconfigure the system before attempting a reboot. To reconfigure the system, use the displayed configuration, which is shown using the show startup-config command in privileged EXEC mode.

Before you begin the procedure to recover a lost password, you must attach an ASCII terminal to the RP console port and configure the terminal to operate at the same settings as the console port (usually 9600 bps, 8 data bits, no parity, and 2 stop bits). After you correctly connect the terminal to the console port, continue with the following steps to recover a lost password:

 
Command
Purpose

Step 1 

Router# show version

Displays the existing software configuration register value. The current configuration setting appears in the last line of the display output. Record this value for use in Step 9.

Step 2 

Router# reload

Break key or Ctrl-]

Enters ROM monitor mode. You must press the Break key or Ctrl-] within 5 seconds of the router turning on.

Step 3 

rommon 1> config-register 


Configuration Summary

enabled are:

console baud: 9600

boot: image specified by the boot system command or 
default to: cisco2-prp


do you wish to change the configuration? y/n [n]: y

enable "diagnostic mode"? y/n [n]:

enable "use net in IP bcast address"? y/n [n]:

enable "load rom after netbootfails"? y/n [n]:

enable "use all zero broadcast"? y/n [n]:

enable "break/abort has effect?" y/n [n]:

enable "ignore system config info?" [n]: y

change console baud rate? y/n [n]:

change boot characteristics? y/n [n]


Configuration Summary

enabled are:

console baud: 9600

boot: image specified by the boot system command

or default to: cisco2-prp

do you wish to change the configuration? y/n [n]


You must reset or power cycle for the new config to 
take effect

Sets the software configuration register to ignore the configuration file information. Answer yes to the following prompts:

•do you wish to change the configuration?

•enable "ignore system config info?"

Step 4 

rommon 2> initialize

Initializes the router. The router goes through a power cycle; the software configuration register is set to ignore the configuration file; the router boots the system image and displays the system configuration dialog.

Step 5 

--- System Configuration Dialog ---


Continue with configuration dialog? [yes/no]: n

Press RETURN to get started!

Exits the system configuration dialog. You must answer no to continue with the configuration dialog and then press Return to exit the configuration dialog.

Step 6 

Router> enable

Password: <password>

Enters privileged EXEC mode.

Step 7 

Router# show startup-config

Displays the enable password in the configuration file.

Step 8 

Router# configure terminal 

Enter configuration commands, one per line. End with 
CNTL/Z.

Enters global configuration mode.

Step 9 

Router(config)# config-register 0xvalue

Changes the software configuration register value back to its original value, where value is the hexadecimal number noted in Step 1.

Step 10 

Router(config)# Ctrl-z

Exits global configuration mode.

Step 11 

Router# reload

Reboots the router. You should now be able to use the recovered password with the enable command to gain access to the router.

Useful Configuration Commands

The following are additional commands that are useful in configuring your router:

Command
Purpose

Router# attach slot-number

Accesses the Cisco IOS software image on a line card to monitor and maintain information on the line card. To exit from the Cisco IOS software image on the line card and return to the Cisco IOS image on the RP card, use the exit command.

Router# execute on {slot slot-number | all} command

Executes commands remotely on a line card.

Router(config)# microcode slot slot-number {flash file-id | tftp file-id}

Loads a Cisco IOS software image on a line card from Flash memory or a TFTP server.

Router(config)# microcode reload slot-number

Reloads the Cisco IOS image on a line card on a Cisco 12000 Series Internet Router after all microcode configuration commands have been entered.

Router# hw-module slot slot-number reload

Reloads the line card. This causes the line card to reset and redownload the Maintenance Bus (MBus) and Fabric Downloader software modules before attempting to redownload the line card Cisco IOS software.


Troubleshooting Tips

This section contains information for diagnosing faulty hardware cards and troubleshooting router crash information. It contains the following sections:

•Field Diagnostics

•Upgrading the FPGA Image on a Line Card

•Retrieving Information from the Crashinfo File

Field Diagnostics

Field diagnostics are available for the Cisco 12000 Series Internet Router to help you isolate faulty hardware to the level of a field-replaceable unit (FRU) without disrupting the operation of the system. After you identify the faulty unit, you can replace it with a spare unit.

Field diagnostics are not designed to identify specific components within the router. They simply determine whether a particular card is operational or defective.

Starting with Cisco IOS Release 12.0(22)S, Cisco Systems has unbundled the Cisco 12000 Series Internet Router field diagnostics line card image from the IOS image. In earlier versions, diagnostics could be launched from the command line and the embedded image would be launched. To accommodate customers with 20-MB Flash memory cards, line card field diagnostics are now stored and maintained as a separate image that must be available on a Flash memory card or a TFTP boot server before the field diagnostics commands can be used. Router processor and switch fabric field diagnostics continue to be bundled and need not be launched from a separate image.

Field diagnostics images are approximately 18 MB in size. IOS images are slightly larger. A single 64-MB Flash memory card can contain both images, or these images can be stored individually on two 20-MB memory cards in PCMCIA slots 0 and 1. To accomodate future feature releases, it is recommended that you use the larger Flash memory disks.

The diagnostics image is named c12k-fdiagsbflc-mz.120-25.S and is always available on Cisco.com. 120-25.S is the version number of the image that corresponds to the Cisco IOS image, in this example: 12.0(25)S.

Caution Performing field diagnostics on a line card stops all activity on the line card. Before the diag command begins running diagnostics, you are prompted to confirm the request to perform field diagnostics on the line card.

To perform field diagnostics on your router, use one of the following commands:

Command
Purpose

Router# diag slot-number source tftp tftp://192.168.2.2/c12k-fdiagsbflc.120-22.S

Performs field diagnostics on the line card in slot slot-number, using the image contained at the specified TFTP site. The file name in this example is a sample only; you must use a valid image file.

Router# diag slot-number source flash slot0:/c12k-fdiagsbflc.120-22.S

Performs field diagnostics on the line card in slot slot-number, using the image contained on the Flash memory card located in slot 0. The file name in this example is a sample only; you must use a valid image file.

Router# diag slot-number previous

Displays previous test results (if any exist) for the card. This option is only available for line cards and RPs.

Router# diag slot-number halt

Stops the field diagnostic testing on the line card. This option is only available for line cards and RPs.

Router# diag slot-number

Performs field diagnostics on a SFC or CSC in slot slot-number. The image is included with the standard Cisco IOS software and does not need to be available from an external source.


Additional keywords can be used with the diag command to limit the output or amount of testing performed. For more information, see the "diag" section on page 4-6. Field diagnostics are described more fully in the document Field Diagnostics for the Cisco 12000 Series Internet Router at the following location:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/dia
g.htm

Upgrading the FPGA Image on a Line Card

If a line card does not boot and you receive an error message indicating that there is a problem with the field-programmable gate array (FPGA) image, or if the line card alphanumeric LED display remains frozen in IOS STRT state, you need to upgrade the FPGA image using the diag command.

Note The Cisco IOS image running on the router has an associated FPGA image that is identified by a version number. The major version number of the FPGA image must match the FPGA image version defined in the Cisco IOS image; the minor version number on the FPGA image must be the same as or greater than the minor version numbers on the FPGA image defined in the Cisco IOS image. For example, if the Cisco IOS image specifies a minimum FPGA image of 03.02, the software will verify that the actual major version number of the FPGA image in the line card bootflash is 03, and that the minor version number is 02 or above.

To upgrade the FPGA image on a line card, follow these steps:

 
Command
Purpose

Step 1 

Router> enable

Password: <password>

Enters privileged EXEC mode.

Step 2 

Router# diag slot-number update-fpga source {tftp | flash} source-path

Updates flash memory with field-programmable gate array (FPGA) image(s) from the current field diagnostics download image.

The name of the image file is c12k-fdiagsbflc-mz.120-25.S where 120-25.S is the version number. For Flash cards, the source path would typically be slot0:c12k-fdiagsbflc-mz.120-25.S or slot1:c12k-fdiagsbflc-mz.120-25.S. The TFTP source path would typically be: tftp://tftp_server_ip_address/my_directory/c12k-fdiagsbflc-mz.120-25.S.

Note Do not unplug the line card or terminate the field diagnostics session during this test.

Retrieving Information from the Crashinfo File

The crashinfo file is a collection of useful information related to the most recent router crash. When a router crashes as a result of data or stack corruption, additional reload information required to debug this type of crash can be found in the crashinfo file. By default, the crashinfo file is stored in the onboard Flash memory SIMM or bootflash under the name "crashinfo".

Use any of the following commands to obtain information about or display the contents of the crashinfo file:

Command
Purpose

Router# show stack

Displays information about the crashinfo file located in the bootflash. If a crashinfo file exists, at the end of the show stack output is a section called Information of Last System Crash that contains the name of the crashinfo file.

Router# dir bootflash:

or

Router# dir sec-bootflash:

Lists the contents of the bootflash. If a crashinfo file exists, it will be listed. Only the last crashinfo file is listed.

Router# more bootflash: crashinfo_20000323-061850

Displays more information about the specific crashinfo file.

Router# dir /all bootflash:

Lists the entire contents of the bootflash, including previous crashinfo files that have been marked as deleted. You can use the undelete command to restore older crashinfo files. However, before you can undelete an old crashinfo file, you must delete the most recent file. You can use the squeeze command on the bootflash to permanently delete old files.

Router# show file bootflash:crashinfo

Displays the contents of the most recent crashinfo file.

Router# delete bootflash:crashinfo

Marks the most recent crashinfo file as being deleted.

Router# undelete file-index bootflash:

Restores a deleted crashinfo file. The file-index is the number corresponding to the file you want to delete on the directory listing. Use the dir bootflash: command to view the file-index.

Router# squeeze bootflash:

Permanently deletes all files in the bootflash that are marked as deleted.


The following example illustrates how to view the contents of the bootflash, how to view the contents of the crashinfo file, and how to restore a previous crashinfo file and view its contents: 

Router# show stack

...

    *************************************************** 

    ******* Information of Last System Crash **********

    ***************************************************


    Using bootflash:crashinfo_20000323-061850. 2000

    CMD: 'sh int fas' 03:23:41 UTC Thu Mar 2 2000

    CMD: 'sh int fastEthernet 6/0/0' 03:23:44 UTC Thu Mar 2 2000

    CMD: 'conf t' 03:23:56 UTC Thu Mar 2 2000

    CMD: 'no ip cef di' 03:23:58 UTC Thu Mar 2 2000

    CMD: 'no ip cef distributed ' 03:23:58 UTC Thu Mar 2 2000

...


Router# dir bootflash:

    Directory of bootflash:/ 


      1  -rw-     4088008   Oct 07 1999 04:51:29  rsp-boot-mz.120-6.6

      2  -rw-      178619   Mar 23 2000 06:18:50  crashinfo_20000323-061850 


    7602176 bytes total (3335292 bytes free)


Router# more bootflash:crashinfo_20000323-061850 

     2000 

    CMD: 'sh int fas' 03:23:41 UTC Thu Mar 2 2000 

    CMD: 'sh int fastEthernet 6/0/0' 03:23:44 UTC Thu Mar 2 2000 

    CMD: 'conf t' 03:23:56 UTC Thu Mar 2 2000

    CMD: 'no ip cef DI 03:23:58 UTC Thu Mar 2 2000 

    CMD: 'no ip cef distributed ' 03:23:58 UTC Thu Mar 2 2000 

    CMD: 'ip cef' 03:24:01 UTC Thu Mar 2 2000 

... 


Router# dir /all bootflash: 

    -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 

    1   .. unknown  FD38E5C7  3FD81C   25  3921820 Oct 02 1998 14:43:56 rsp-boot-mz.112-15a.P.bin 

    2   .D config   AF12EF9F  41C308    9   125547 Oct 16 1998 11:10:10 crashinfo 

    3   .. config   33DEAF65  43A950    9   124360 Oct 16 1998 11:15:50 crashinfo 


    3430064 bytes available (4172112 bytes used) 


Router# show file bootflash:crashinfo 


    Compliance with U.S. Export Laws and Regulations - Encryption 


    This product performs encryption and is regulated for export 

    by the US Government. 


    .....  file continues here.... 

...

Router# dir /all bootflash: 

    -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 

    1   .. unknown  FD38E5C7  3FD81C   25  3921820 Oct 02 1998 14:43:56 rsp-boot-mz.112-15a.P.bin 

    2   .D config   AF12EF9F  41C308    9   125547 Oct 16 1998 11:10:10 crashinfo 

    3   .. config   33DEAF65  43A950    9   124360 Oct 16 1998 11:15:50 crashinfo 


    3430064 bytes available (4172112 bytes used)


Router# delete bootflash:crashinfo 


Router# dir /all bootflash: 

    -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 

    1   .. unknown  FD38E5C7  3FD81C   25  3921820 Oct 02 1998 14:43:56 rsp-boot-mz.112-15a.P.bin 

    2   .D config   AF12EF9F  41C308    9   125547 Oct 16 1998 11:10:10 crashinfo 

    3   .D config   33DEAF65  43A950    9   124360 Oct 16 1998 11:15:50 crashinfo 


    3430064 bytes available (4172112 bytes used)


Router# undelete 2 bootflash: 

    Router#dir /all bootflash: 

    -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 

    1   .. unknown  FD38E5C7  3FD81C   25  3921820 Oct 02 1998 14:43:56 rsp-boot-mz.112-15a.P.bin 

    2   .. config   AF12EF9F  41C308    9   125547 Oct 16 1998 11:10:10 crashinfo 

    3   .D config   33DEAF65  43A950    9   124360 Oct 16 1998 11:15:50 crashinfo 


    3430064 bytes available (4172112 bytes used)

Monitoring and Maintaining the Cisco 12000 Series Internet Router

There are a number of show commands that can be used to monitor the Cisco 12000 Series Internet Router as it runs. A subset of the most useful of these commands is described here. For a complete discussion of all available show commands, refer to the Cisco IOS Command Reference.

•Monitoring the Router Configuration

•Additional System Monitoring

•Monitoring and Maintaining the PRP Software Configuration

Monitoring the Router Configuration

To monitor the router interface configuration, use the following show commands in EXEC mode:

Command
Purpose

Router# show version

Displays the Cisco IOS software version number, hardware installed in the router, the names and sources of the router image files, and the contents of the software configuration register.

Router> show gsr

Displays the statistics of each hardware module installed in the Cisco 12000 Series Internet Router.

Router> show interfaces

Displays information about the system interfaces.

Router> show interfaces type slot/port

Displays information about a specific interface in the system. Type indicates the interface type, for example, pos, srp, atm; slot/port indicates the interface location in the router.

Router> show diags slot

Displays specific hardware information for the card installed in the specified slot in your system, including the card serial number.

Router> show running-config

Displays the currently running configuration in RAM.

Router> show led

Displays the current LED status on all line cards.

Router> show ip interface [brief]

Displays the usability status of interfaces configured for IP.


The following sample display shows typical results from the show version command. Depending on the image version of the Cisco IOS software running on your router and the way the router is equipped, the results of your show version command might be different. 

Router# show version

Cisco Internetwork Operating System Software 

IOS (tm) GS Software (GSR-P-M), Experimental Version 12.0(20020822:053101) [ozarad-offLci 
151]

Copyright (c) 1986-2002 by cisco Systems, Inc.

Compiled Mon 26-Aug-02 14:20 by ozarad

Image text-base: 0x50010968, data-base: 0x52C44000


ROM: System Bootstrap, Version 11.2(20010625:183716) [bfr_112 181], DEVELOPMENT SOFTWARE

BOOTLDR: GS Software (GSR-BOOT-M), Version 12.0(8)S, EARLY DEPLOYMENT RELEASE SOFTWARE 
(fc1)


Q311 uptime is 1 day, 3 hours, 15 minutes

System returned to ROM by reload at 11:52:01 UTC Sun Aug 4 2002

System restarted at 11:28:14 UTC Sat Aug 10 2002

System image file is "tftp://172.16.16.254/gsr-p-mz.ME12_SRP_VER_13_08_28_02"


cisco 12406/GRP (R5000) processor (revision 0x05) with 131072K bytes of memory.

R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache

Last reset from power-on


1 Route Processor Card

2 Clock Scheduler Cards

3 Switch Fabric Cards

2 one-port OC48 SONET based SRP controllers (2 SRP).

1 OC12 POS controller (1 POS).

1 OC48 POS controller (1 POS).

1 two-port OC12 SONET based SRP Edge based controller (2 SRP).

1 Ethernet/IEEE 802.3 interface(s)

2 Packet over SONET network interface(s)

3 SRP network interface(s)

507K bytes of non-volatile configuration memory.


8192K bytes of Flash internal SIMM (Sector size 256K).

Configuration register is 0x2102

The following sample display shows typical results from the show gsr command. For each hardware module installed in the chassis, the state string describes its status. The state string generally corresponds to the value displayed on the alphanumeric LEDs on the hardware module, as shown in Table 3-6. 

Router> show gsr

Slot 0  type  = 2 Ports OC3 Channelized to DS1/E1

        state = IOS RUN   Line Card Enabled

Slot 1  type  = 3 Port Gigabit Ethernet

        state = IOS RUN   Line Card Enabled

Slot 5  type  = Route Processor

        state = ACTV RP   IOS Running  ACTIVE

Slot 17 type  = Clock Scheduler Card(6) OC-192

        state = Card Powered  PRIMARY CLOCK

Slot 18 type  = Switch Fabric Card(6) OC-192

        state = Card Powered

Slot 19 type  = Switch Fabric Card(6) OC-192

        state = Card Powered

Slot 20 type  = Switch Fabric Card(6) OC-192

        state = Card Powered

Slot 24 type  = Alarm Module(6)

        state = Card Powered

Slot 25 type  = Alarm Module(6)

        state = Card Powered

Slot 28 type  = Blower Module(6)

        state = Card Powered

Table 3-6 Alphanumeric LED Display vs. show gsr State String

Alphanumeric LED Display
show gsr State String

none

ABSENT Card absent

ACTV STRT

ACTVSTRT Active RP startup

ACTV RP

ACTV RP IOS Running ACTIVE

ADMN DOWN

ADMNDOWN Administratively down

ADMN OFF

ADMNOFF Administratively powered down

BWTH LOW

BWTHLOW Bring up suspended low bandwidth condition

CARV ERR

CARVERR Bring up suspended buffer carving error

DIAG F LD

DIAGF LD Downloading field diagnostics over fabric

DIAG HALT

DIAGHALT Cancel field diagnostics

DIAG LOAD

DIAGLOAD Downloading field diagnostics over MBus

DIAG PASS

DIAGPASS Field diagnostics ran successfully

DIAG STRT

DIAGSTRT Launching field diagnostics

DIAG TEST

DIAGTEST Running field diagnostic tests

DUMP DONE

DUMPDONE Completed data collection after failure

DUMP REQ

DUMPREQ Line Card or RP requesting core dump

DUMP RUN

DUMPRUN Line Card or RP core dumping

FABI WAIT

FABIWAIT Waiting for fabric inititialization to be complete for card

FABL DNLD

FABLDNLD Loading fabric downloader

FABL RUN

FABLRUN Fabric downloader ready for use

FABL STRT

FABLSTRT Launching fabric downloader

FABM WAIT

FABMWAIT Wait for fabric manager to report fabric usable

IN RSET

IN RSET In reset

IOS DNLD

IOSDNLD Downloading IOS

IOS FABW

IOSFABW IOS in startup waiting for fabric to be ready

IOS VGET

IOSVGET Getting IOS version number

IOS RUN

IOS RUN Line card enabled

IOS STRT

IOS STRT Starting IOS

IOS TRAN

IOS TRAN Transitioning to active

IOS UP

IOS UP IOS is running

MAL FUNC

MAL FUNC Card malfunction reported by field diagnostics

MISM ATCH

MISMATCH Card type mismatch with card in paired slot

none

POWERED Card powered

CYC

PWR CYC Card undergoing a power cycle

OFF

PWR OFF Card NOT powered

PWR STRT

PWR STRT Card newly powered

ROMI GET

ROMIGET Getting ROM images

ROM VGET

ROMVGET Getting ROM response

OFF

RP OFF Route processor not powered

RP RDY

RP RDY Route processor powered

WAIT

RTRYWAIT Waiting to retry download after persistent failures

SCFG PRES

SCFGPRES Incorrect "hw-module slot # srp" command present

SCFG REQD

SCFGREQD Required "hw-module slot # srp" command not present

STBY STRT

STBYSTRT Launching IOS (Standby)

STBY RP

STBY RP IOS Running STANDBY

none

UNKNSTAT Unknown

XS RP

XS RP GRP/PRP not required in chassis


Additional System Monitoring

The following additional commands can be used to monitor various system indicators:

Command
Purpose

Router# show controllers

Displays information about the hardware. There is a show controllers command for the RP and a separate show controllers command for line cards.

Router# show context

Displays information stored in NVRAM when the router crashes. This command is only useful to technical support representatives.

Router# show environment

Displays the current environmental specifications.

Router# show logging

Displays the state of the syslog error and event logging. Before using this command, you should configure the system to timestamp logging messages with the service timestamps command. To clear messages from the logging buffer, use the clear logging command.

Router# show memory

Displays memory pool statistics, including summary information about the activities of the system memory allocator and a block-by-block listing of memory use.

Router# show microcode

Displays the microcode bundled into the system image.

Router# show processes

Displays information about all active processes.

Router# show protocols

Displays the configured protocols.

Router# show stacks

Displays stack usage of processes and interrupt routines, including the reason for the last system reboot. This command is only useful to your technical support representative.

Router# show tcp

Displays the status of TCP connections.

Router# show tcp brief [all]

Displays a concise description of TCP connection endpoints.

Router# show tech-support [page] [password]

Displays general information about the router when reporting a problem.


Monitoring and Maintaining the PRP Software Configuration

To monitor the configuration of the PRP, use the following show commands in EXEC mode:

Command
Purpose

Router# show controllers ethernet

Displays the register values and status of the GT64260 Ethernet controllers.

Router# show controllers gt64260

Displays the register values of the GT64260 Discover System controller.

Router# show controllers psar

Displays statistics about the packets sent and received in the PRP packet segmentation and reassembly (PSAR) controllers.