Cisco Systems 78-12510-02 User Manual
CHAPTER
5
Configuring the MGX RPM-PR
This chapter describes how to complete a basic configuration of the MGX Route Processor Module
(RPM-PR). It provides procedures for configuring ATM, Ethernet, and Fast Ethernet interfaces, as well
as, permanent virtual circuits (PVCs).It also details how to make connections between an RPM-PR and
a PXM-45 and between other service modules or other RPM-PRs. The chapter contains the following
sections:
• Accessing the RPM-PR Command Line Interface
• Booting the RPM-PR
• Verifying the Configuration
• Establishing 1:N Redundancy Between Two or More RPM-PR Cards
This chapter provides information necessary to get the RPM-PR up and running. Detailed command
information is available in the Cisco IOS command reference publications.
Note The back cards used in conjunction with the RPM-PR are equivalent to port adapters in Cisco routers.
Accessing the RPM-PR Command Line Interface
To configure the RPM-PR, you must access the command line interface (CLI) of the RPM-PR.
The RPM-PR CLI can be accessed using any of the following methods:
• Console port on the front of the RPM-PR
The RPM-PR has an RJ-45 connector on the front of the card module. If you configure the RPM-PR
on site, connect a console terminal (an ASCII terminal or a PC running terminal emulation software)
directly to the console port on your RPM-PR using an RS-232 to RJ-45 rollover cable for CLI access
(see Chapter 3, “Installing the MGX RPM-PR”).
• cc from another MGX 8850 or MGX 8950 card
After initial configuration, you can also configurethe RPM-PR through the PXM-45. Youaccess the
RPM-PR CLI by entering the cc (change card) command from any of the other cards in the switch.
• Telnet from a workstation, PC, or another router
After initial configuration, you can also configure the RPM-PR remotely via Telnet. After the
RPM-PR is installed and has PVCs to other RPM-PRs or routers in the network, you can Telnet to
access the RPM-PR CLI remotely from these other devices.
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide
Release 2.1, Part Number 78-12510-02 Rev. C1, August 31, 2004
5-1
Booting the RPM-PR
To connect a modem to the auxiliary port on the RPM-PR, see Chapter 3, “Installing the MGX
RPM-PR.”
Booting the RPM-PR
When the RPM-PR is booted, the boot image must be the first file in the bootflash. If the bootflash does
not have a valid boot image as a first file, the card may not be able to boot and can result in bootflash
corruption. If the bootflash is corrupted, you will have to send the card back for an external burn with a
valid boot image.
You can reboot the RPM-PR from the PXM by entering the command resetcd <card_number> from the
switch CLI, where card_number is the slot number of the RPM-PR that is being rebooted.
Note Omitting the card number resets the entire system.
Also, you can reboot the RPM-PR from the RPM-PR using the RPM-PR console port and entering the
reload command.
Each time you turn on power to the RPM-PR, by inserting the RPM-PR into the MGX 8850 or the
MGX 8950, it goes through the following boot sequence:
1. The RPM-PR runs diagnostics on the CPU, memory, and interfaces.
2. The system boot software, which is the boot image, executes and searches for a valid Cisco IOS
image, which is the RPM-PR runtime software.
The source of the Cisco IOS image is determined by the configuration register setting. Toverify this
setting, you can enter either the show version or show bootvar command. (See the “Viewing the
Hardware Configuration” section later in this chapter.)
• If the configuration register is set to the factory-default setting of 0x01, RPM-PR will come up and
stay in boot mode.
• If the configuration register is 0x2, the RPM-PR will look for the runtime image either in bootflash
or on the PXM C:FW drive.
3. The search for runtime image is determined by which boot system command is entered.
• Entering the boot system x:<runtime_image_name> command will result in a search for a runtime
image on the PXM C:FW drive.
• Entering the boot system bootflash:<runtime_image_name> command will result in a search for a
run time image in the bootflash.
4. If the runtime software is not found after three attempts, the RPM-PR reverts to the boot mode.
5. Ifa valid Cisco IOS image is found, then the RPM-PR searches for a valid configuration,which can
reside in NVRAM or as a configuration file either on the PXM hard disk x: drive or in bootflash.
If you want to load from a specific configuration file, you should enter either the
boot config bootflash:<config_file> command or the boot config x:<config_file> command.
6. For normal RPM-PR operation, there must be a valid Cisco IOS image on the PXM-45 x: drive or
in bootflash, and a configuration in NVRAM or configuration file in bootflash or on the PXM disk.
The first time you boot the RPM-PR, configure the RPM-PR interfaces and save the configuration
to a file in NVRAM. Then follow the procedure described in “Initializing the RPM-PR Card.” For
information on the Cisco IOS instructions, see Appendix C, “IOS and Configuration Basics.”
Chapter 5 Configuring the MGX RPM-PR
5-2
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide
Release 2.1, Part Number 78-12510-02 Rev. C1, August 31, 2004
Chapter 5 Configuring the MGX RPM-PR
RPM-PR Bootflash Precautions
The RPM-PR bootflash is used to store boot image, configuration and “run time” files. The Flash stores
and accesses data sequentially, and the RPM-PR boot image must be the first file stored to successfully
boot the card. Erasing the boot image or moving it from the first position on the Flash will cause the card
to not boot.
The RPM boot image, which comes loaded on the Flash, will work for all RPM IOS images. Therefore,
there is no reason to ever delete or move the factory installed boot image.
Note Erasing or moving the boot image can cause RPM-PR boot failure. When this happens, the RPM must
be returned to Cisco and reflashed.
In order to avoid this unnecessary failure, requiring card servicing, you should
• Never erase the boot file from the RPM Flash
• Never change the position of the boot file on the RPM Flash
• Use care when “squeezing” the Flash to clean it up.
As long as the boot file remains intact in the first position on the flash, the RPM will successfully boot.
Booting the RPM-PR
Verifying the IOS Files on Bootflash
Enter the show bootflash command to verify the IOS files on the bootflash. The following screen
displays the RPM-PR command sequence.
Router#show bootflash:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image AB6CF374 2BAFB4 11 2600756 Jul 25 2001 02:41:41 rpm-boot-mz
2 .. config 44E48EC2 34712C 18 573685 Aug 07 2001 23:03:42 auto_config_slot16
3 .. config 7B53E8DC 40E368 18 815547 Aug 08 2001 19:28:03 auto_config_slot15
28777624 bytes available (3990376 bytes used)
Router#
Verifying the IOS Files on the PXM-45 x: Drive
The IOS image can be stored on the PXM-45 hard drive. To confirm this, make sure you are in the C:FW
directory. Enter the ll command to list the contents of the directory. You should see a file with a name
beginning with rpm-js-mz, which is the IOS image.
Tip Copy the RPM-PR Cisco IOS image into the RPM C: directory (not the E: directory) of the PXM-45
hard disk with the filename specified in the RPM-PR boot command.
The following screen displays the PXM C:FW content listing.
M8850_LA.8.PXM.a > cd FW
M8850_LA.8.PXM.a > ll
Listing Directory .:
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide
Release 2.1, Part Number 78-12510-02 Rev. C1, August 31, 2004
5-3
Booting the RPM-PR
Chapter 5 Configuring the MGX RPM-PR
drwxrwxrwx 1 0 0 13312 May 11 15:47 ./
drwxrwxrwx 1 0 0 13312 May 11 17:10 ../
-rwxrwxrwx 1 0 0 2253552 May 11 15:47 mpsm_t1e1_030.000.004.016-P2.fw
-rwxrwxrwx 1 0 0 10655280 Apr 2 08:46 rpm-js-mz.123-2.T5
-rwxrwxrwx 1 0 0 3350304 Apr 2 08:46 rpm-boot-mz.123-2.T5
-rwxrwxrwx 1 0 0 1431512 May 11 15:47 mpsm_t1e1_030.000.004.016-P1_bt.fw
-rwxrwxrwx 1 0 0 1030532 May 11 15:46 frsm_vhs_022.000.005.019-A.fw
-rwxrwxrwx 1 0 0 891552 May 11 15:46 frsm_8t1e1_022.000.005.019-A.fw
-rwxrwxrwx 1 0 0 303936 May 11 15:46 cesm_t3e3_CE8_BT_1.0.02.fw
-rwxrwxrwx 1 0 0 641312 May 11 15:46 cesm_t3e3_022.000.005.019-A.fw
-rwxrwxrwx 1 0 0 743136 May 11 15:46 cesm_8t1e1_022.000.005.019-A.fw
-rwxrwxrwx 1 0 0 826392 May 11 15:38 vxsm_005.000.004.034-A_bt.fw
-rwxrwxrwx 1 0 0 10528336 May 11 15:38 vxsm_005.000.004.034-A.fw
-rwxrwxrwx 1 0 0 7939476 May 11 15:38 pxm45_005.000.004.034-A_mgx.fw
-rwxrwxrwx 1 0 0 1160328 May 11 15:37 pxm45_005.000.004.034-A_bt.fw
-rwxrwxrwx 1 0 0 468388 May 11 15:46 frsm_vhs_VHS_BT_1.0.06.fw
-rwxrwxrwx 1 0 0 1245112 May 11 15:37 mpsm155_005.000.004.034-P1_bt.fw
-rwxrwxrwx 1 0 0 4069552 May 11 15:37 mpsm155_005.000.004.034-P1.fw
-rwxrwxrwx 1 0 0 737896 May 11 15:37 frsm12_005.000.004.034-A_bt.fw
-rwxrwxrwx 1 0 0 2490064 May 11 15:37 frsm12_005.000.004.034-A.fw
-rwxrwxrwx 1 0 0 3674368 May 11 15:36 axsmxg_005.000.004.034-P1.fw
-rwxrwxrwx 1 0 0 838840 May 11 15:36 axsmxg_005.000.004.034-A_bt.fw
-rwxrwxrwx 1 0 0 742168 May 11 15:36 axsme_005.000.004.034-A_bt.fw
-rwxrwxrwx 1 0 0 297988 May 11 15:46 frsm_8t1e1_FR8_BT_1.0.02.fw
-rwxrwxrwx 1 0 0 264592 May 11 15:46 cesm_8t1e1_CE8_BT_1.0.02.fw
-rwxrwxrwx 1 0 0 3111904 May 11 15:36 axsme_005.000.004.034-A.fw
-rwxrwxrwx 1 0 0 744600 May 11 15:36 axsm_005.000.004.034-A_bt.fw
-rwxrwxrwx 1 0 0 3267520 May 11 15:36 axsm_005.000.004.034-A.fw
-rwxrwxrwx 1 0 0 248686 May 11 15:32 vism_8t1e1_VI8_BT_3.2.00.fw
-rwxrwxrwx 1 0 0 4135448 May 11 15:32 vism_8t1e1_003.053.103.007-I.fw
-rwxrwxrwx 1 0 0 4135000 May 11 15:32 vism_8t1e1_003.003.103.007-I.fw
In the file system :
total space : 818961 K bytes
free space : 704028 K bytes
M8850_LA.8.PXM.a >
Initializing the RPM-PR Card
To initialize the RPM-PR card, please refer to the Cisco MGX 8850 (PXM1E/PXM45), MGX 8950, MGX
8830, and MGX 8880 Configuration Guide, Release 5.
To verify the version, enter the show version or show bootvar commands. See the “Verifying the
Configuration” section later in this chapter.
Assigning an IP Address to the Switch Interface
You need to assign an IP address for the RPM-PR on the ATM switch. This procedure tells you how to
configure the ATM switch interface with the IP address.
Timesaver Obtain the correct IP and ATM network addresses for your RPM-PR on the ATM switch from your
system administrator or consult your network plan to determine correct addresses before you
continue to configure the RPM-PR.
5-4
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide
Release 2.1, Part Number 78-12510-02 Rev. C1, August 31, 2004
Chapter 5 Configuring the MGX RPM-PR
Step 1 Enter show ip int brief to display your router IP interfaces.
Router#show ip int brief
Interface IP-Address OK? Method Status Protocol
Switch1 unassigned YES NVRAM up up
Note that the switch does not have an assigned IP address.
Step 2 Enter conf terminal to enter global configuration mode.
Router#conf terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 3 To enter interface configuration mode for the ATM interface, enter interface switch1 at the prompt.
Router(config)#interface switch1
Step 4 Enter ip address followed by the IP address to be assigned to the ATM switch.
Router(config-if)#ip address 1.1.1.1 255.255.255.0
Step 5 Enter end or press Ctrl-Z to exit the configuration interface mode.
Router(config-if)#end
Booting the RPM-PR
Step 6 Enter show ip int brief to display the IP address assigned to the ATM switch. The following screen is
an example.
Router#show ip int brief
Interface IP-Address OK? Method Status Protocol
Switch1 1.1.1.1 YES manual up up
Note that the newly added interface address appears in the display.
Step 7 Enter show run to verify the configuration of the RPM-PR, as shown in the following example screen.
Router#show run
Building configuration...
Current configuration : 729 bytes
!
version 12.1
no service single-slot-reload-enable
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Router
!
boot system x:rpm-js-mz_002.001.000.057
boot config c:auto_config_slot11
logging rate-limit console 10 except errors
enable password cisco
!
ip subnet-zero
no ip finger
!
no ip dhcp-client network-discovery
!
!
!
interface Switch1
ip address 1.1.1.1 255.255.255.0
no atm ilmi-keepalive
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide
Release 2.1, Part Number 78-12510-02 Rev. C1, August 31, 2004
5-5
Booting the RPM-PR
Step 8 Enter copy run start at the prompt to write the configuration to the router NVRAM memory.
Chapter 5 Configuring the MGX RPM-PR
switch autoSynch off
!
ip kerberos source-interface any
ip classless
no ip http server
!
!
!
line con 0
transport input none
line aux 0
line vty 0 4
no login
!
end
Router#copy run start
Building configuration...
[OK]
The IP address is now active and ready to use.
Note The ATM interface can be further configured with logical subinterfaces as needed. To see how to
configure subinterfaces on the ATM switch interface, see Chapter 6, “Configuring PNNI
Communications,” the “Creating and Configuring a Switch Subinterface” section.
Booting RPM-PR Using TFTP from a TFTP Server
Once you add the IP address, you can configure the RPM-PR card to load runtime software from a TFTP
server.
Note This procedure is optional. The preferred procedure for loading the runtime software from the
PXM-45 hard drive is described earlier in “Initializing the RPM-PR Card.”
Use the following procedure to configure the RPM-PR card to load runtime software from a TFTP
server:
Step 1 Enter cc <RPM-PR card slot #> to access the router card.
The router prompt (>) appears.
Step 2 Enter enable and your password, when prompted, so that you can enter privileged commands.
Step 3 Enter config terminal to enter global configuration mode.
Step 4 Enter boot system tftp followed by the address of the server from which you want to download the boot
file as shown in this example.
Router(config)#boot system tftp /tftpboot/balbalas/rpm-js-mz 171.69.1.129
5-6
Step 5 Enter end or press Ctrl-Z to exit configuration mode.
Router(config)#end
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide
Release 2.1, Part Number 78-12510-02 Rev. C1, August 31, 2004
Loading...