Cisco IOS XR Getting Started Guide, Release 3.3
Chapter 2 - Bringing Up the Cisco IOS XR Software on a Standalone Router
Downloads: This chapterpdf (PDF - 220.0KB) The complete bookPDF (PDF - 6.76MB) | Feedback

Bringing Up the Cisco IOS XR Software on a Standalone Router

Table Of Contents

Bringing Up the Cisco IOS XR Software on a Standalone Router

Contents

Prerequisites

Software Requirements

Hardware Prerequisites and Documentation

Bringing Up and Configuring a Standalone Router

Examples

Verifying the System After Initial Bring-Up

Examples of show Commands

Where to Go Next


Bringing Up the Cisco IOS XR Software on a Standalone Router


This chapter provides instructions for bringing up the Cisco IOS XR software on a standalone router for the first time. This section applies to standalone routers that are delivered with Cisco IOS XR software installed.


Note If you are upgrading a Cisco 12000 Series Router from Cisco IOS software to Cisco IOS XR software, see the Cisco IOS XR software document titled Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco 12000 Series Router.


Contents

This chapter contains the following sections:

Prerequisites

Bringing Up and Configuring a Standalone Router

Verifying the System After Initial Bring-Up

Where to Go Next

Prerequisites

The following sections describe the software and hardware requirements for bringing up a standalone system.

Software Requirements

The multishelf system requires the following software:

Cisco IOS XR Software Release 3.3.1

ROMMON 1.40 or higher on each RP in the system


Caution The ROM Monitor software must be upgraded to version 1.40 or higher on all RPs before a Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 3.3.1 or higher release. If the router is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail to boot. For instructions to overcome a boot block in the standby RP in a single chassis system, see Cisco IOS XR ROM Monitor Guide. If a boot block occurs in a multishelf system, contact your Cisco Systems support representative for assistance. See Obtaining Technical Assistance.

Hardware Prerequisites and Documentation

The Cisco IOS XR software runs on the routers listed in the "Supported Standalone System Configurations" section. Before a router can be started, the following hardware management procedures must be completed:

Site preparation

Equipment unpacking

Router installation

For information on how to complete these procedures for your router equipment, see the hardware documents listed in the "Related Documents" section.


Note If you are upgrading a Cisco 12000 Series Router from Cisco IOS software to Cisco IOS XR software, you must first prepare the router. Refer to Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco 12000 Series Router for more information. See the "Related Documents" section for a complete listing of available documents.


Bringing Up and Configuring a Standalone Router

To bring up a standalone router, you need to connect to the router and configure root-system username and password as described in the following procedure:

SUMMARY STEPS

1. Establish a connection to the DSC Console port.

2. Type the username for the root-system login and press Return.

3. Type the password for the root-system login and press Return.

4. Log in to the router.

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Establish a connection to the DSC Console port.

Initiates communication with the router.

For instructions on connecting to the Console port, see the "Connecting to the Router Through the Console Port" section.

If the router has been configured, the router displays the prompt: Username:

If the Username prompt appears, skip this procedure and continue general router configuration as described in Chapter 4 "Configuring General Router Features."

Step 2 

Type the username for the root-system login and press Return.

Sets the root-system username, which is used to log in to the router.

Step 3 

Type the password for the root-system login and press Return.

Creates an encrypted password for the root-system username.

Step 4 

Retype the password for the root-system login and press Return.

Allows the router to verify that you have entered the same password both times.

If the passwords do not match, the router prompts you to repeat the process.

Step 5 

Log in to the router.

Establishes your access rights for the router management session.

Enter the root-system username and password that were created earlier in this procedure.

After you log in, the router displays the CLI prompt, which is described in the "CLI Prompt" section.

Examples

The following example shows the root-system username and password configuration for a new router, and it shows the initial log in:

--- Administrative User Dialog ---
 
   
 
   
  Enter root-system username: cisco
  Enter secret: 
  Enter secret again:
RP/0/0/CPU0:Jan 10 12:50:53.105 : exec[65652]: %MGBL-CONFIG-6-DB_COMMIT :
'Administration configuration committed by system'. Use 'show configuration
commit changes 2000000009' to view the changes.
Use the 'admin' mode 'configure' command to modify this configuration.
 
   
 
   
 
   
User Access Verification
 
   
Username: cisco
Password: 
RP/0/0/CPU0:ios#
 
   

The secret line in the configuration command script shows that the password is encrypted. When you enter the password during configuration and login, the password is hidden.

Verifying the System After Initial Bring-Up

To verify the status of the router, perform the following procedure:

SUMMARY STEPS

1. show version

2. admin
show
platform [node-id]
end

3. show redundancy

4. show environment

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show version

RP/0/RP0/CPU0:router# show version

Displays information about the router, including image names, uptime, and other system information.

Step 2 

admin
show
platform [node-id]
exit

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# show platform

RP/0/RP0/CPU0:router(admin)# exit

Places the router in administration EXEC mode, displays information about the status of cards and modules installed in the router, and terminates administration EXEC mode.

Some cards support a CPU module and service processor (SP) module. Other cards support only a single module.

A card module is also called a node. When a node is working properly, the status of the node in the State column is IOS XR RUN.

Type the show platform node-id command to display information for a specific node. Replace node-id with a node name from the show platform command Node column.

Note To view the status of all cards and modules, the show platform command must be executed in administration EXEC mode.

Step 3 

show redundancy

Example:

RP/0/RP0/CPU0:router# show redundancy

Displays the state of the primary (active) and standby (inactive) RPs, including the ability of the standby to take control of the system.

If both RPs are working correctly, one node displays active role, the Partner node row displays standby role, and the Standby node row displays Ready.

Step 4 

show environment

Example:

RP/0/RP0/CPU0:router# show environment

Displays information about the hardware attributes and status.

Examples of show Commands

The following sections provide examples of show commands:

show version Command

show environment Command

show platform Command

show redundancy Command

show version Command

To display basic information about the router configuration, type the show version command in EXEC mode, as shown in the following example:

RP/0/RP1/CPU0:CRS-8_P1# show version
 
   
Cisco IOS XR Software, Version 3.3.0[2I]
Copyright (c) 2006 by cisco Systems, Inc.
 
   
ROM: System Bootstrap, Version 1.38(20050525:193559) [CRS-1 ROMMON],  
 
   
CRS-8_P1 uptime is 1 week, 1 day, 17 hours, 1 minute
System image file is "disk0:hfr-os-mbi-3.3.0/mbihfr-rp.vm"
 
   
cisco CRS-8/S (7457) processor with 4194304K bytes of memory.
7457 processor at 1197Mhz, Revision 1.2
 
   
16 Packet over SONET/SDH network interface(s)
16 SONET/SDH Port controller(s)
2 Ethernet/IEEE 802.3 interface(s)
16 GigabitEthernet/IEEE 802.3 interface(s)
2043k bytes of non-volatile configuration memory.
38079M bytes of hard disk.
1000592k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).
1000640k bytes of ATA PCMCIA card at disk 1 (Sector size 512 bytes).
 
   
Package active on node 0/1/SP:
hfr-diags, V 3.3.0[2I], Cisco Systems, at disk0:hfr-diags-3.3.0
    Built on Mon Mar 13 12:58:02 UTC 2006
    By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8
 
   
hfr-admin, V 3.3.0[2I], Cisco Systems, at disk0:hfr-admin-3.3.0
    Built on Mon Mar 13 11:46:36 UTC 2006
    By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8
 
   
hfr-base, V 3.3.0[2I], Cisco Systems, at disk0:hfr-base-3.3.0
    Built on Mon Mar 13 11:43:22 UTC 2006
    By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8
 
   
hfr-os-mbi, V 3.3.0[2I], Cisco Systems, at disk0:hfr-os-mbi-3.3.0
    Built on Mon Mar 13 11:27:02 UTC 2006
    By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8
 
   
 --More--
 
   

show environment Command

To display environmental monitor parameters for the system, use the show environment command in EXEC or administration EXEC mode. The following command syntax is used:

show environment [options]

Enter the show environment ? command to display the command options.

In the following example, temperature information for a Cisco CRS-1 router is shown:

RP/0/RP0/CPU0:router# show environment temperatures
 
   
R/S/I   Modules         Inlet           Exhaust         Hotspot
                        Temperature     Temperature     Temperature
                        (deg C)         (deg C)         (deg C)
 
   
0/1/*
        host              32, 30         26, 27         35           
        cpu                                             34           
        fabricq0                                        27           
        fabricq1                                        32           
        ingressq                                        37           
        egressq                          32             27           
        ingresspse                                      35           
        egresspse                                       29           
        jacket            25             24             25           
        spa0              19                            25, 32       
        spa5              25                            24           
0/6/*
        host              32, 26         27, 25         33           
        cpu                                             35           
        fabricq0                                        27           
        fabricq1                                        32           
        ingressq                                        37           
        egressq                          30             25           
        ingresspse                                      31           
        egresspse                                       29           
        jacket            24             25             26           
        spa0              19                            25, 31       
        spa4              22                            33, 35       
        spa5              24                            24           
0/RP0/*
        host              23             24             24, 33, 26,  
                                                            24, 27        
0/RP1/*
        host              23             24             24, 32, 26,  
                                                            24, 26 
 
   

In the following example, LED status of the nodes in a Cisco CRS-1 router is shown:

RP/0/RP0/CPU0:router# show environment leds
 
   
0/1/*: Module (host) LED status says: OK
0/1/*: Module (jacket) LED status says: OK
0/1/*: Module (spa0) LED status says: OK
0/1/*: Module (spa5) LED status says: OK
0/6/*: Module (host) LED status says: OK
0/6/*: Module (jacket) LED status says: OK
0/6/*: Module (spa0) LED status says: OK
0/6/*: Module (spa4) LED status says: OK
0/6/*: Module (spa5) LED status says: OK
0/RP0/*: Module (host) LED status says: OK
0/RP0/*: Alarm LED status says: NONE
0/RP1/*: Module (host) LED status says: OK
0/RP1/*: Alarm LED status says: NONE
 
   

See the Cisco IOS XR Interface and Hardware Component Command Reference for more information.

show platform Command

The show platform command displays information on router resources. In EXEC mode, the show platform command displays the resources assigned to the secure domain router (SDR) you are managing. In administration EXEC mode, the show platform command displays all router resources.


Note SDRs are introduced in Chapter 4 "Configuring General Router Features."


The following EXEC mode sample output displays the nodes assigned to the default SDR, which is called the owner SDR:

RP/0/RP0/CPU0:router# show platform
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/1/CPU0        MSC             Jacket Card     IOS XR RUN      PWR,NSHUT,MON
0/1/0           MSC(SPA)        4XOC3-POS       OK              PWR,NSHUT,MON
0/1/5           MSC(SPA)        8X1GE           OK              PWR,NSHUT,MON
0/6/CPU0        MSC             Jacket Card     IOS XR RUN      PWR,NSHUT,MON
0/6/0           MSC(SPA)        4XOC3-POS       OK              PWR,NSHUT,MON
0/6/4           MSC(SPA)        8XOC3/OC12-POS  OK              PWR,NSHUT,MON
0/6/5           MSC(SPA)        8X1GE           OK              PWR,NSHUT,MON
0/RP0/CPU0      RP(Active)      N/A             IOS XR RUN      PWR,NSHUT,MON
0/RP1/CPU0      RP(Standby)     N/A             IOS XR RUN      PWR,NSHUT,MON
 
   

The following administration EXEC mode sample output displays all router nodes:

RP/0/RP0/CPU0:router# admin
 
   
RP/0/RP0/CPU0:router(admin)# show platform
 
   
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/1/SP          MSC(SP)         N/A             IOS XR RUN      PWR,NSHUT,MON
0/1/CPU0        MSC             Jacket Card     IOS XR RUN      PWR,NSHUT,MON
0/1/0           MSC(SPA)        4XOC3-POS       OK              PWR,NSHUT,MON
0/1/5           MSC(SPA)        8X1GE           OK              PWR,NSHUT,MON
0/6/SP          MSC(SP)         N/A             IOS XR RUN      PWR,NSHUT,MON
0/6/CPU0        MSC             Jacket Card     IOS XR RUN      PWR,NSHUT,MON
0/6/0           MSC(SPA)        4XOC3-POS       OK              PWR,NSHUT,MON
0/6/4           MSC(SPA)        8XOC3/OC12-POS  OK              PWR,NSHUT,MON
0/6/5           MSC(SPA)        8X1GE           OK              PWR,NSHUT,MON
0/RP0/CPU0      RP(Active)      N/A             IOS XR RUN      PWR,NSHUT,MON
0/RP1/CPU0      RP(Standby)     N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM0/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
 
   
RP/0/RP0/CPU0:router# end
 
   

Note Line cards in Cisco CRS-1 routers are called modular services cards (MSCs). The show platform command output is different for Cisco CRS-1 routers and Cisco XR 12000 Series Routers.


In the following example, information is shown for a single node in a Cisco CRS-1 router:
 
   
RP/0/RP0/CPU0:CRS-8_P1# show platform 0/1/CPU0
 
   
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/1/CPU0        MSC             Jacket Card     IOS XR RUN      PWR,NSHUT,MON
 
   

For more information on node IDs, see the "Displaying SDR Node IDs and Status" section.

For more information on the show platform command, see the Cisco IOS XR Interface and Hardware Component Command Reference.

show redundancy Command

To display information about the active and standby (inactive) RPs, enter the show redundancy command as follows:

RP/0/RP0/CPU0:CRS-8_P1# show redundancy
 
   
Redundancy information for node 0/RP0/CPU0:
==========================================
Node 0/RP0/CPU0 is in ACTIVE role
Partner node (0/RP1/CPU0) is in STANDBY role
Standby node in 0/RP1/CPU0 is ready
 
   
Reload and boot info
----------------------
RP reloaded Wed Feb 15 13:58:32 2006: 1 week, 6 days, 22 hours, 49 minutes ago
Active node booted Wed Feb 15 13:58:32 2006: 1 week, 6 days, 22 hours, 49 minuto
Standby node boot Wed Feb 15 13:59:00 2006: 1 week, 6 days, 22 hours, 49 minuteo
Standby node last went not ready Wed Mar  1 07:40:00 2006: 5 hours, 8 minutes ao
Standby node last went ready Wed Mar  1 07:40:00 2006: 5 hours, 8 minutes ago
There have been 0 switch-overs since reload
 
   

Where to Go Next

For information on configuring basic router features, see Chapter 4 "Configuring General Router Features."