For Cisco CRS-1 Multishelf Systems, when the RP of the DSC boots up, if the RP or shelf controller (SC) on other chassis are configured to autoboot (for example, they are in a loop sending minimum boot image [MBI] requests), they boot automatically. If they have not been configured to autoboot, enter reset at the ROM Monitor (ROMMON) prompt.

3. Verify that the value of the configuration register (confreg) is 0x102. Enter confreg at the ROMMON prompt to display the configuration register value. If the configuration register value is not set to 0x102, see Cisco IOS XR Getting Started Guide for information on changing the configuration register value.

4. It takes approximately 20 minutes for the cards on all chassis to be displayed in the Cisco IOS XR software show commands. Managed nodes (service processor [SP], line card [LC], and distributed route processor [DRP]) are booted by shelfmgr, mbimgr, and instdir automatically when ROMMON is set to autoboot.

Use the following chassis numbering guidelines when numbering the chassis in a Cisco CRS-1 Multishelf System:

Note It is recommended that the line card chassis containing the active DSC be numbered 0, the second line card chassis be numbered 1, and the fabric card chassis be numbered F0. See Cisco IOS XR Getting Started Guide for more information on recommended chassis numbering.

•The line card chassis (LCC) numbering must be in the range of 0 to 127.

•The fabric card chassis (FCC) numbering must be in the range of 240 to 255.

•In a multishelf configuration, all racks must have a unique number.

Verifying Successful Bootup

For information on verifying the status of the router, see Cisco IOS XR Getting Started Guide. It contains detailed procedures for verifying a standalone router and multishelf system.

The show platform command displays the state transitions when a node is booting:

•SP RMON—The service processor (SP) is starting and the basic code is being loaded on the SP (LC only).

•ROMMON—Once the SP has started, the LC CPU is on and the LC ROMMON software is started (LC only).

•MBI BOOT—The minimum boot image code is loading on the LC CPU from disk or the DSC (LC only).

•MBI RUNNING—The required processes on the LC are starting. The normal transition from this state is to start the Cisco IOS XR operating system.

•IOS XR—The Cisco IOS XR software is running.

Verifying and Troubleshooting the Console Connection

The default configuration selects the route processor (RP) in the lowest numbered slot. For the Cisco CRS-1 Multishelf System, the RP in the lowest numbered slot in the LCC configured as Rack 0 is selected as the primary RP and the designated shelf controller (DSC).

To determine the primary RP on routers running Cisco IOS XR software:

•On Cisco CRS-1 RPs, the primary RP is identified by a lighted Primary LED on the RP front panel. The primary RP is also identified by "ACTV RP" in the alphanumeric display on the card. The console port is located on the primary RP.

The console connection through the DSC provides a communications path to the routing system. The console port is designed for a serial cable connection to a terminal or computer running a terminal emulation program. See Cisco IOS XR Getting Started Guide for information on connecting to the console port.

To verify and troubleshoot the console connection on the DSC, perform the following procedures.

SUMMARY STEPS

1. Check the cable between the console port on the DSC and the terminal or computer.

2. Open the terminal emulation application, select the correct COM port and verify the settings.

3. Swap cables.

4. Test the cable on another console port.

5. Contact Cisco Technical Support if the problem is not resolved.

DETAILED STEPS

Command or Action

Purpose

Step 1

Check the cable between the console port on the DSC and the terminal or computer.

Ensure that there is a serial cable connection from a terminal or computer running a terminal emulation program to the console port on the active RP of the DSC. See Cisco IOS XR Getting Started Guide for information on connecting to the console port.

Step 2

Open the terminal emulation application, select the correct COM port and verify the settings.

Verify that the terminal settings are as follows:

•Bits per second: 9600/9600

•Data bits: 8

•Parity: None

•Stop bit: 2

•Flow control: None

If the correct settings are not applied, the console port outputs garbage characters or no output at all. This makes the router appear as if it is hanging or not responding.

The following variables add verbosity to certain ROMMON functions and to bypass auxiliary authentication in Cisco IOS XR:

TFTP_VERBOSE=2

AUX_AUTHEN_LEVEL=0

The following variables are used by the Config Manager to immediately apply the configuration after bootup:

IOX_ADMIN_CONFIG_FILE=nvram:startup-config-admin.00

IOX_CONFIG_FILE=nvram:startup-config-lr.00

The following variables above may be specified may be displayed as follows if a path has not been specified:

IOX_CONFIG_FILE=

IOX_ADMIN_CONFIG_FILE=

The following variable may be displayed before the system has been Turbobooted:

TURBOBOOT=on,format,disk0

The following variables may be displayed after a system has been Turbobooted. A 'boot' variable is saved to indicate where the minimum boot image (MBI) is stored and the turboboot variable is set to NULL:

BOOT=disk0:hfr-os-mbi-3.3.96/mbihfr-rp.vm,1

TURBOBOOT=

The following variable is Reboot/Reload code saved after any kind of shutdown, failover, and so on:

ReloadReason=0

The following variable is saved to NVRAM.

BSI=0

Step 3

Remove then reinsert the SC or RP.

See the following documents for information on removing then reinserting the SC (or RP):

•Use the show controllers switch switch-instancestatistics location 0/RP0/CPU0 command in administration mode to verify the switch statistics. Repeat this command for switches on each shelf in the system.

If the shelf controller (SC) or route processor (RP) in the remote line card chassis fails to boot correctly, messages are displayed on the console of either device, indicating that it is waiting for information from the designated shelf controller (DSC).

SUMMARY STEPS

1. Verify the physical system control plane Ethernet network connection between the DSC in the LCC to the Catalyst switch.

2. Connect to the Catalyst switch console port.

3. Verify the physical system control plane Ethernet network connection between the SC in the FCC to the Catalyst switch.

4. show spanning-tree

5. Contact Cisco Technical Support if the problem is not resolved.

DETAILED STEPS

Command or Action

Purpose

Step 1

Verify the physical system control plane Ethernet network connection between the DSC in the LCC and the Catalyst switch.

Verify the physical connectivity between the DSC and Catalyst switch. See Cisco CRS-1 Carrier Routing System Multishelf System Interconnection and Cabling Guide for details on cabling between the DSC and the Catalyst switch.

Step 2

Connect to the Catalyst switch console port.

Provides connection to the system control plane Ethernet network.

See Cisco CRS-1 Carrier Routing System Multishelf System Interconnection and Cabling Guide for details on connecting to the external switch.