Software Configuration Guide for MGX 8850 (PXM45) and MGX 8950, Release 2.1
Preparing RPM Cards and Lines for Communication
Downloads: This chapterpdf (PDF - 219.0KB) | Feedback

Preparing RPM-PR Cards for Operation

Table Of Contents

Preparing RPM-PR Cards for Operation

Configuration Quickstart

Locating RPM-PR Cards in the Switch

Understanding dspcds and dspcd Displays for RPM-PR

Initializing RPM-PR Cards

Verifying the Software Version in Use

Establishing Redundancy Between Two RPM-PR Cards

Configuring SNMP on the RPM-PR Card

Where to Go Next


Preparing RPM-PR Cards for Operation


This chapter describes how to do the following:

Determine which slots host the RPM-PR cards

Initialize RPM-PR cards that are installed in the switch

Verify the software version used on the RPM-PR cards

Configure backup cards for RPM-PR cards

Where to find additional information on configuring RPM-PR cards


Note Some of the procedures in this chapter require you to enter commands in the Cisco Internet Operating System (IOS) that runs on the RPM-PR cards. The procedures in this chapter do not describe how to use Cisco IOS, but they do include examples that list all the Cisco IOS commands needed to complete the procedure. For more information on any Cisco IOS command, refer to the documentation for Cisco IOS.


Configuration Quickstart

The quickstart procedure in this section provides a summary of the tasks required to prepare RPM-PR cards for operation. This procedure is provided as an overview and as a quick reference for those who have already configured the MGX 8850 and MGX 8950 switches.

 
Command
Purpose

Step 1 

username

<password>

Start a configuration session.

Note To perform all the procedures in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.

Step 2 

dspcds

dspcd

cc <slotnumber>

Locate RPM-PR cards that need to be configured.

See "Locating RPM-PR Cards in the Switch," which appears later in this chapter.

Step 3 

boot system c:<filename>

boot config e:auto_config_slot

copy run start

cc 7

resetcd slot

Related commands:

dspcds

Initialize RPM-PR cards by identifying a runtime software file and storing the configuration on the PXM45 hard disk.

See "Initializing RPM-PR Cards," which appears later in this chapter.

Step 4 

show version

Verify the software version for each RPM-PR card.

See "Verifying the Software Version in Use," which appears later in this chapter.

Step 5 

addred <options>

Define RPM-PR secondary cards that will operate as backup cards for RPM-PR primary cards.

See "Establishing Redundancy Between Two RPM-PR Cards," which appears later in this chapter.

Locating RPM-PR Cards in the Switch

You already have the location of the RPM-PR cards if you have completed the Hardware Configuration Worksheet (Table 2-9) in the "Verifying the Hardware Configuration" section of "Configuring General Switch Features." That section describes how to locate the RPM-PR cards, as well as other switch cards, and how to determine if the RPM-PR front and back cards are installed in the correct slots.

Understanding dspcds and dspcd Displays for RPM-PR

The dspcds and dspcd displays for RPM-PR cards are similar to those for other cards, but they contain the following differences:

RPM-PR cards are identified as RPM_PR cards.

If one or more RPM-PR back card are installed for an RPM-PR card, the status for the appropriate bay changes from Empty to Active. The switch does not detect and display the card type or software revision status.

The Standby status for the front card indicates that the card is either operating in boot mode, or that the card is operating as a standby card for another RPM-PR card.

The following example shows the dspcd command display for an RPM-PR card:

8850_NY.7.PXM.a > dspcd 9
8850_NY                          System Rev: 02.01   Mar. 01, 2001 13:59:41 PST
MGX8850                                              Node Alarm: NONE
Slot Number:   9    Redundant Slot: NONE 

                    Front Card          Upper Card          Lower Card
                    ----------          ----------          ----------

Inserted Card:      RPM_PR              UNKNOWN             ---                
Reserved Card:      UnReserved          UnReserved          UnReserved         
State:              Active              Active              Empty          
Serial Number:                                              ---         
Prim SW Rev:        ---                 ---                 ---
Sec SW Rev:         ---                 ---                 ---
Cur SW Rev:         ---                 ---                 ---
Boot FW Rev:        ---                 ---                 ---
800-level Rev:                                              ---  
800-level Part#:    ---                 000-00000-00        
CLEI Code:                                                  ---        
Reset Reason:       On Reset From Shell
Card Alarm:         NONE                
Failed Reason:      None                
Miscellaneous Information:

Type <CR> to continue, Q<CR> to stop: 
8850_NY                          System Rev: 02.01   Mar. 01, 2001 13:59:41 PST
MGX8850                                              Node Alarm: CRITICAL

Crossbar Slot Status:      No Crossbar

Alarm Causes
------------
    NO ALARMS

Notice that the dspcd command display does not display the software versions for the RPM-PR card. To display the software version in use on the RPM-PR card, see "Verifying the Software Version in Use," which appears later in this chapter.

Also notice that the Reserved Card status of the front card is UnReserved. This status changes to Reserved when either an MPLS or a PNNI partition is defined on the RPM card.

Initializing RPM-PR Cards

RPM-PR cards are shipped with the latest software installed on the card and will operate as soon as the card is installed. After you install the card, however, you should initialize the card. Initializing the card does the following:

Configures the card to use the runtime RPM-PR software image stored on the PXM45 hard disk.

Configures the card to store the configuration file on the PXM45 hard disk.

Storing the configuration on the hard disk is essential for the following reasons:

If an active RPM-PR card fails and the configuration is not stored on the disk, the standby RPM-PR card cannot become active.

The switch saveallcnf command cannot store configuration information that is not on the PXM45 hard disk.

When the RPM-PR card starts or reboots, it searches for the configuration file in the following sequence:

If there is a configuration file only on the PXM45 hard disk, the RPM-PR card uses the configuration stored on the hard disk.

If there is no configuration file on the hard disk, then the NVRAM version is used.

If configuration files exist on both the hard drive and bootflash, the switch examines a timestamp tag in each file. If the timestamp tag is the same in both files, the RPM-PR card uses the configuration file stored in bootflash. If the timestamp tag is different, the RPM-PR card uses the configuration file stored on the hard drive.

To initialize an RPM-PR card, use the following procedure.


Step 1 Establish a configuration session with the switch using a user name at any access level.


Note Access to the RPM-PR configuration is secured by the Cisco IOS software running on the card.


Step 2 To display the files that can be used to start RPM-PR cards, use the cd command to select the E:RPM directory, and enter the ll command to display the directory contents. For example:

pop20two.7.PXM.a > cd E:RPM

pop20two.7.PXM.a > ll
  size          date       time       name
--------       ------     ------    --------
     512    NOV-17-2000  20:01:10   .                 <DIR>
     512    NOV-17-2000  20:01:10   ..                <DIR>
 2334044    DEC-08-2000  02:17:46   rpm-boot-mz_122-4.T 
 7695500    DEC-08-2000  02:18:52   rpm-js-mz_122-4.T 

In the file system : 
    total space :  102400 K bytes
    free  space :  92334 K bytes

The file that contains the word boot is for booting the card when the regular runtime image, rpm-js-mz_122-4.T in this example, cannot load. The boot file is stored in bootflash on the card, and loaded from that location. The switch never loads the boot code from the PXM45 hard disk. However, it is common practice to store the boot code on the hard disk in preparation for a bootflash upgrade.

Write down the filename for the runtime image. You will have to enter this filename later in this procedure.


Note If the runtime file is missing, you can transfer the correct file to the switch. This procedure is described in "Downloading and Installing Software Upgrades."


Step 3 Use the cc command to select the card slot in which the RPM-PR card is installed. For example:

pop20two.7.PXM.a > cc 9

(session redirected)

Router>

As shown in the example, the switch displays the prompt for the Cisco IOS software on the RPM-PR card.

Step 4 Verify the configuration status of the RPM-PR card by entering the show bootflash: command. For example:

Router>show bootflash:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1   .. image    BAC7D50E  2B80EC   27  2588780 Jul 12 2001 23:05:26 rpm-boot-mz_122-4.T
2   .. config   0EC2C678  2B84F0   18      898 Jul 12 2001 16:04:41 auto_config_slot09

30178064 bytes available (2589936 bytes used)

The bootflash contents should contain only the boot file and no configuration files. The example above contains a configuration file (auto_config_slot09), which must be deleted before you initialize the card. Instructions for deleting files appear later in this procedure.

Step 5 Enter enable mode. For example:

Router>enable
Password: 
Router#


Note The default password for Enable mode is supplied with your switch. To secure access to your RPM-PR cards, you should change this password. For information on changing the Enable password, refer to the Cisco IOS documentation.


Step 6 If the bootflash contains any configuration commands, use the delete command to mark them for deletion. For example:

Router#delete bootflash:auto_config_slot09
Delete filename [auto_config_slot09]? 
Delete bootflash:auto_config_slot09? [confirm]y

This command marks files for deletion, but it does not delete them. The next step removes any files marked for deletion.

Step 7 If the bootflash contains configuration files marked for deletion, remove these files by entering the squeeze command. For example:

Router#squeeze bootflash:
All deleted files will be removed. Continue? [confirm]y
Squeeze operation may take a while. Continue? [confirm]y                     
Squeeze of bootflash complete

To verify the current bootflash contents, enter the show bootflash: command.

Step 8 Enter global configuration mode. For example:

Router#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.

Step 9 Enter the boot system command using the format:

Router(config)# boot system c:<filename>

For example:

Router(config)#boot system c:rpm-js-mz.122-4.T

Step 10 To configure the RPM-PR card to store its configuration on the PXM45 hard disk, enter the boot config command as follows:

RPM-PR_LA_9(config)#boot config e:auto_config_slot

The RPM-PR configuration file is named: auto_config_slot. The slot portion of the name must match the slot number that corresponds to the RPM-PR card.


Note The configuration is also stored in NVRAM using the name startup-config.


Step 11 Exit global configuration mode and save your changes with the copy run start command. For example:

Router(config)#^Z
Router#copy run start
Building configuration...
[OK]
Router#

This step ensures that your configuration change will not be lost when the router restarts. It also saves the configuration to the PXM45 hard disk. The following directory listing shows the configuration file that is saved:

pop20two.7.PXM.a > cd E:RPM

pop20two.7.PXM.a > ll
  size          date       time       name
--------       ------     ------    --------
     512    NOV-17-2000  20:01:10   .                 <DIR>
     512    NOV-17-2000  20:01:10   ..                <DIR>
 2334044    DEC-08-2000  02:17:46   rpm-boot-mz.122-4.T
 7695500    DEC-08-2000  02:18:52   rpm-js-mz.122-4.T
     553    DEC-16-2000  20:40:24   auto_config_slot09  

In the file system : 
    total space :  102400 K bytes
    free  space :  92334 K bytes


Caution If you do not save the configuration changes, you will have to repeat this procedure.

Step 12 To begin using the new configuration, reset the card from the active PXM45 card. For example:

Router#cc 7

(session redirected)

8850_NY.7.PXM.a > resetcd 9
The card in slot number 9, will be reset. Please confirm action
resetcd: Do you want to proceed (Yes/No)? y

When the dspcds command display shows that the RPM-PR card is active, the initialization is complete.


Verifying the Software Version in Use

To verify which version of software an RPM-PR card is using, you need to use IOS commands at the router prompt for the RPM-PR card. The following example shows how to do this with the show version command:

Router#show version
Cisco Internetwork Operating System Software 
IOS (tm) RPM Software (RPM-JS-M), Experimental Version 12.1(20001205:224609) 
[swtools-rpm21a 242]
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Fri 09-Feb-01 01:17 by 
Image text-base: 0x60008960, data-base: 0x61326000

ROM: System Bootstrap, Version 12.1(20001003:080040) [swtools-rommon400 102], DEVELOPMENT 
SOFTWARE
BOOTFLASH: RPM Software (RPM-BOOT-M), Experimental Version 12.1(20001010:121621) 
[swtools-rpm21.nightly 323]

Router uptime is 0 minutes
System returned to ROM by reload
System image file is "c:rpm-js-mz.122-4.T"

cisco RPM (NPE400) processor with 229376K/32768K bytes of memory.
R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 4096KB L3 Cache
Last reset from s/w peripheral
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
1 FastEthernet/IEEE 802.3 interface(s)
1 ATM network interface(s)
125K bytes of non-volatile configuration memory.

32768K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x2

The following line in the example above is most important:

System image file is "c:rpm-js-mz.122-4.T"

The system image file line indicates which file was used to load the software currently in use. In this example, the software was loaded from the c: drive, which corresponds to E:/RPM on the switch. The filename shown identifies the source file for the running image. This filename is configured in IOS global configuration mode with the boot system command.

Establishing Redundancy Between Two RPM-PR Cards

RPM-PR cards support one-to-n (1:n) card redundancy. With 1:n redundancy, one RPM-PR card can serve as a secondary or backup card for multiple RPM-PR cards.


Note Primary and secondary cards can run on incompatible software images. However, the software image on the secondary card must be at the same level or higher than the software image on the primary card.


To establish a backup card for an RPM-PR card, use the following procedure.


Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher.

Step 2 If you have not done so already, initialize both cards as described earlier in "Initializing RPM-PR Cards."

Step 3 Use the dspcds command to verify that both RPM-PR cards are in the "Active" state.


Note The secondary RPM card must not have any configured connections when it is configured for redundancy.


Step 4 Enter the addred command as follows:

pop20one.7.PXM.a > addred <redPrimarySlotNum> <redSecondarySlotNum> <redType>

Replace <redPrimarySlotNum> with the slot number of the primary RPM-PR card, and replace <redSecondarySlotNum> with the slot number of the secondary RPM-PR card. Replace <redType> with the number 2 for 1:n redundancy.

After you enter the addred command, the switch resets the secondary card; thus, the secondary card will be unavailable for a couple of minutes. When the reset is complete, a dspcds command will show the primary and secondary cards in the active and standby states, respectively.


Note The switch only supports RPM-PR cards. If you insert another card type, such as the RPM/B, the addred command will not work.


Step 5 Use the cc command to select the card slot in which the primary RPM-PR card is installed. For example:

pop20two.7.PXM.a > cc 9

Step 6 Enter global configuration mode. For example:

Router>enable
Password: 
Router#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.

Step 7 Configure the RPM-PR card to store its configuration on the PXM45 hard disk by entering the boot config command as follows:

Router>boot config e:auto_config_slot#


Note This step is required. When switchover occurs, the secondary RPM-PR card must be able to load the configuration from the auto_config file on the PXM45 hard disk. If this command is already configured in the startup configuration file, you do not need to repeat this command.


Step 8 Enter the copy run start command on the primary RPM-PR card to save the configuration changes.

Router> copy run start

Step 9 To display the redundancy relationship between all cards in the switch, enter the dspred command.

For information on managing redundant cards, refer to "Managing Redundant Cards," in Chapter 7, "Switch Operating Procedures."


Configuring SNMP on the RPM-PR Card

To configure the SNMP community string on an RPM-PR card, you need to use IOS commands at the router prompt for the RPM-PR card. The following example shows how to do this.


Step 1 Login to the RPM card to determine whether the switch interface is active.

Router# enable
Router>(enable):show interfaces

Step 2 If the switch interface is not active, enter the config terminal command to activate it. The following example shows you how to do this.

Router# config terminal
Router(config)#int switch 1
Router(config)#no shut
end

Step 3 Enter the show run command to display the running configuration and verify SNMP information.

Router# show run
....
....
snmp-server community public RW
snmp-server community private RW
....
....

Step 4 To change the read-write community string, enter the config terminal command. The following example shows you how to do this.

Router#config terminal
Router(config) snmp-server community POPEYE RW 

Step 5 Enter the exit command to get out of config terminal mode.

Router(config)#exit

Step 6 Enter the copy run start command to save the configuration for use at startup.

RPM-PR_LA_9#copy run start
Destination filename [startup-config]? 
Building configuration...
[OK]
RPM-PR_LA_9#


Note The copy run start command performs the same function as the older write mem command.



Where to Go Next

After the RPM-PR card is initialized and any required redundancy is established, you can configure the RPM-PR card to operate in either of the following roles:

Label Switch Controller (LSC)

Label Edge Router (LER)

In either the LSC or the LER role, the RPM-PR communicates with other ATM switches using MPLS AXSM communications links. For instructions on configuring AXSM trunks and lines to support MPLS, refer to "Provisioning AXSM Communication Links."

When operating in the LER role, the RPM-PR card can use Ethernet connections on the RPM-PR back cards to connect to IP networks. The LSC and LER roles, and the RPM-PR Ethernet connections, are all defined using Cisco IOS, which runs on the RPM-PR card. To start using Cisco IOS from a switch CLI session, use the cc command to change cards to the RPM-PR slot. For instructions on configuring the RPM-PR card with Cisco IOS, refer to the Cisco MGX Route Processor Module Installation and Configuration Guide, Release 2.1.