- About This Guide
- Overview of the RPM-XF
- Preparing to Install the MGX RPM-XF
- Installing the MGX RPM-XF Front and Back Cards
- Installing and Configuring the MGX-XF-UI Management Back Card
- Installing and Configuring the MGX-1OC12POS-IR Back Card
- Installing and Configuring the MGX-1GE Gigabit Ethernet Back Card
- Configuring the MGX RPM-XF
- Configuring PNNI Communications
- Configuring MPLS Features
- Configuring Quality of Service
- Maintaining the MGX RPM-XF
- Cable and Connector Specifications
- Cisco IOS and Configuration Basics
- Command Summary
RPM-XF Installation and Configuration Guide, Release 3
Chapter: Configuring the MGX RPM-XF
- Accessing the RPM-XF Command Line Interface
- Booting the RPM-XF
- RPM-XF Bootflash Precautions
- Verifying the Cisco IOS Files on Bootflash
- Verifying the Cisco IOS Files in the PXM45 C:FW Directory
- Verifying the Cisco IOS Configuration Files in the PXM45 E:RPM Directory
- Initializing the RPM-XF Card
- Assigning an IP Address to the Switch Interface
- Booting RPM-XF Using TFTP from a TFTP Server
- RPM-XF Boot-up Sequence
- Verifying the Configuration
Configuring the MGX RPM-XF
This chapter describes how to complete a basic configuration of the MGX Route Processor Module (RPM-XF). The chapter contains the following sections:
•
Accessing the RPM-XF Command Line Interface
•Establishing 1:N Redundancy Between Two or More RPM-XF Cards
This chapter provides information necessary to get the RPM-XF up and running. Detailed command information is available in the Cisco IOS command reference publications.
Accessing the RPM-XF Command Line Interface
To configure the RPM-XF, you must access the command line interface (CLI) of the RPM-XF.
The RPM-XF CLI can be accessed using any of the following methods:
•Console port on the MGX-XF-UI management back card of the RPM-XF
If you configure the RPM-XF on site, connect a console terminal (an ASCII terminal or a PC running terminal emulation software) directly to the console port on your MGX-XF-UI back card using an RS-232 to RJ-45 rollover cable for CLI access (see "Installing the MGX RPM-XF Front and Back Cards").
Note It is recommended that you always set the line speed on the console port of the MGX-XF-UI back card to 9600 baud. See "Configuring the Console and Auxiliary Ports" in Chapter 4.
•cc from another MGX 8850 card
After initial configuration, you can also configure the RPM-XF through the PXM45. You can access the RPM-XF 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-XF remotely via Telnet. After the RPM-XF is installed and has PVCs to other RPM-XFs or routers in the network, you can Telnet to access the RPM-XF CLI remotely from these other devices.
You can also telnet through the Fast Ethernet ports on the MGX-XF-UI management back card. See Chapter 4, "Installing and Configuring the MGX-XF-UI Management Back Card," to see how to assign IP address to the FE interface.
Note Connecting a modem to the auxiliary port on the MGX-XF-UI is not supported.
Booting the RPM-XF
The RPM-XF bootflash is used to store boot image, configuration and run-time image files. A valid RPM-XF boot image must be present in the bootflash to successfully boot the card.
RPM-XF Bootflash Precautions
The RPM-XF boot image that comes loaded on the Flash will work for all RPM-XF IOS images. Therefore, there is no reason to delete or move the factory installed boot image.
If you accidently delete or corrupt the bootflash, you will need to use the ROM Monitor to recover the bootflash. In the ROM Monitor mode, use the tftpdnld utility described in the "Using the tftpdnld Command" section in Appendix A.
Verifying the Cisco IOS Files on Bootflash
Enter the show bootflash command to verify the Cisco IOS files on the bootflash. The following screen displays the RPM-XF command sequence.
router-slot14#show bootflash:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image D7F765BC 306604 20 2647428 Apr 22 2002 11:22:47 rpmxf-boot-mz.020405
2 .D config 65AD67B1 327CE0 18 136795 Apr 26 2002 05:02:06 auto_config_slot14
3 .. config C3CBD7D7 34937C 18 136732 Apr 30 2002 02:15:24 auto_config_slot14
62614660 bytes available (2921340 bytes used)
Verifying the Cisco IOS Files in the PXM45 C:FW Directory
On the PXM45 hard drive, the RPM-XF image files are stored in the C:FW directory. To see these files, change the directory to C:FW and enter the ll command. You can also enter x: to view the C:FW directory on the PXM hard disk. You should see a file with a name beginning with rpmxf-p12-mz, which is the Cisco IOS image.
Tip FTP the RPM-XF Cisco IOS image into the C:FW directory of the PXM45 hard disk with the filename specified in the RPM-XF boot system command.
The following screen displays the PXM, AXSM, and RPM-XF images displayed after entering the ll command.
Unknown.7.PXM.a > cd C:FW
Unknown.7.PXM.a > ll
Listing Directory .:
drwxrwxrwx 1 0 0 13312 Apr 29 18:45 ./
drwxrwxrwx 1 0 0 13312 Apr 29 14:42 ../
-rwxrwxrwx 1 0 0 7438480 Apr 8 17:18 rpmxf-p12-mz.020405
-rwxrwxrwx 1 0 0 6049940 Apr 4 17:48 pxm45_003.000.000.026-A_mgx.fw
-rwxrwxrwx 1 0 0 3121648 Mar 29 18:16 axsm_003.000.000.234-P1.fw
-rwxrwxrwx 1 0 0 6049444 Apr 2 16:09 pxm45_003.000.000.000-D_mgx.fw
-rwxrwxrwx 1 0 0 6043924 Mar 22 14:04 pxm45_003.000.000.001-A_mgx.fw
-rwxrwxrwx 1 0 0 6043892 Mar 20 18:51 pxm45_003.000.000.239-A_mgx.fw
-rwxrwxrwx 1 0 0 2654768 Mar 29 18:14 axsme_003.000.000.234-P1.fw
-rwxrwxrwx 1 0 0 6050100 Mar 29 17:15 pxm45_003.000.000.009-A_mgx.fw
In the file system :
total space : 818961 K bytes
free space : 470713 K bytes
Verifying the Cisco IOS Configuration Files in the PXM45 E:RPM Directory
On the PXM45 hard disk, RPM-XF configuration files are stored in the E:RPM directory. To see these files, enter the dir E:RPM command on the PXM.
The following screen displays the RPM-XF configuration files stored in the E:RPM directory on the PXM hard disk.
Unknown.8.PXM.a > dir E:RPM
Listing Directory E:RPM:
drwxrwxrwx 1 0 0 2048 May 13 12:41 ./
drwxrwxrwx 1 0 0 2048 May 13 11:24 ../
-rwxrwxrwx 1 0 0 627 Feb 5 13:33 zen10.conf.svenki
-rwxrwxrwx 1 0 0 806 Feb 6 20:01 rpm12.conf.svenki
-rwxrwxrwx 1 0 0 632 Feb 4 23:16 zenith10.conf.svenki
-rwxrwxrwx 1 0 0 5747 Apr 16 14:34 slot05
-rwxrwxrwx 1 0 0 77849 Feb 13 01:07 zen14.conf.svenki021202
-rwxrwxrwx 1 0 0 59697 Feb 13 00:53 zen3.conf.svenki021202
-rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot05
-rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot13
-rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot03
-rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot01
-rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot06
-rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot09
-rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot12
-rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot14
-rwxrwxrwx 1 0 0 842 Apr 25 18:25 zen
In the file system :
total space : 102140 K bytes
free space : 89446 K bytes
Initializing the RPM-XF Card
The first time you boot the RPM-XF card, it comes up in boot mode (Boot-Hold). Refer to the Cisco MGX 8850 Switch Software Configuration Guide for instructions on copying files.
Step 1 From the switch CLI, enter cc <RPM-XF 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 dir to display the flash memory directory as shown here. Note the boot image software version.
router2-slot14#dir
Directory of bootflash:/
1 -rw- 2647428 Apr 22 2002 11:22:47 rpmxf-boot-mz.020405
3 -rw- 136732 Apr 30 2002 02:15:24 auto_config_slot14
65536000 bytes total (62614660 bytes free)
Step 4 Enter dir x: to display the contents of the C:FW directory on the PXM45 hard drive. Note the runtime image filename for Step 7.
router2-slot14#dir x:
Directory of x:/
0 -rw- 7438480 Apr 09 2002 01:18:34 rpmxf-p12-mz.020405
0 -rw- 6049940 Apr 05 2002 01:48:02 pxm45_003.000.000.026-A_mgx.fw
0 -rw- 3121648 Mar 30 2002 02:16:02 axsm_003.000.000.234-P1.fw
0 -rw- 6049444 Apr 03 2002 00:09:12 pxm45_003.000.000.000-D_mgx.fw
0 -rw- 6043924 Mar 22 2002 22:04:12 pxm45_003.000.000.001-A_mgx.fw
0 -rw- 6043892 Mar 21 2002 02:51:20 pxm45_003.000.000.239-A_mgx.fw
0 -rw- 2654768 Mar 30 2002 02:14:22 axsme_003.000.000.234-P1.fw
0 -rw- 6050100 Mar 30 2002 01:15:30 pxm45_003.000.000.009-A_mgx.fw
838616064 bytes total (482072752 bytes free)
To boot the runtime image from the bootflash, copy the image to the bootflash, as follows.
Router#copy x:rpmxf-p12-mz.1228T_XT1 bootflash:
Destination filename [rpmxf-p12-mz.1228T_XT1]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
:
:
:
:
:
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
7445832 bytes copied in 84.180 secs (88640 bytes/sec)
Step 5 Enter configure terminal at the prompt to enable the RPM-XF interface.
Router#configure terminal
Step 6 Enter no boot system to clear any existing boot system commands.
Router(config)#no boot system
Step 7 The RPM-XF can be booted from either the bootflash or PXM45 hard disk, by entering either,
boot system bootflash:< filename> to load the runtime software from the bootflash
or
boot system x:< filename> to load the runtime software from the PXM45 hard disk
Step 8 Enter end or press Ctrl Z to exit the configuration interface mode.
Router(config-if)#end
Step 9 Enter copy run start to save the configuration.
Router#copy run start
Step 10 Enter reload on the RPM-XF.
Router#reload
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-XF 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-XF on the ATM switch from your system administrator or consult your network plan to determine correct addresses before you continue to configure the RPM-XF.
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
Switch0 unassigned YES unset up up
Switch1 unassigned YES unset up up
FastEthernet2/0 unassigned YES unset administratively down down
FastEthernet2/1 unassigned YES unset administratively down down
Note The switch0 interface can not be assigned an 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
Step 6 Enter show ip int brief to display the IP address assigned to the ATM switch. For example,
Router#show ip int brief
Interface IP-Address OK? Method Status Protocol
Switch0 unassigned YES unset up up
Switch1 1.1.1.1 YES manual up up
Note The newly added interface address appears in the display.
Step 7 Enter show run to verify the configuration of the RPM-XF, as shown in the following example screen.
Router#show run
Building configuration...
Current configuration :687 bytes
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Router
!
boot system x:rpmxf-p12-mz.020405
boot config e:auto_config_slot02
no logging console
enable password cisco
!
ip subnet-zero
!
!
!
interface Switch1
ip address 1.1.1.1 255.255.255.0
switch auto_synch off
!
ip classless
no ip http server
ip pim bidir-enable
!
snmp-server engineID local 80000009FF0000A100000000
snmp-server community public RO
snmp-server community private RW
snmp-server ifindex persist
!
!
line con 0
exec-timeout 0 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
exec-timeout 0 0
no login
!
end
Step 8 Enter copy run start at the prompt to write the configuration to the router NVRAM memory.
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 8, "Configuring PNNI Communications," the "Creating and Configuring a Switch Subinterface" section.
Booting RPM-XF Using TFTP from a TFTP Server
Once you add the IP address on the FastEthernet port, you can configure the RPM-XF card to load runtime software from the TFTP server.
Note This procedure is optional. The preferred procedure for loading the runtime software from the PXM45 hard drive is described earlier in "Initializing the RPM-XF Card."
Use the following procedure to configure the RPM-XF card to load runtime software from a TFTP server:
Step 1 Enter cc <RPM-XF 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 image name and address of the server from which you want to download the boot file as shown in this example.
Router(config)#boot system tftp://171.69.1.129/tftpboot/shrinath/rpmxf-p12-mz
Step 5 Enter end or press Ctrl-Z to exit configuration mode.
Router(config)#end
Step 6 Enter show run to view your configuration. The configuration is similar to the following examply..
Router#show run
Building configuration...
Current configuration : 710 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 tftp://171.69.1.129/tftpboot/shrinath/rpmxf-p12-mz
boot config e: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
Step 7 Enter copy run start at the prompt to write the configuration to the router NVRAM memory.
Router#copy run start
Building configuration...
[OK]
Step 8 To load the runtime image from the TFTP server, enter the reload command on the RPM-XF.
Router#reload
You can also reboot the RPM-XF by entering the resetcd <slot #> command on the PXM.
Note Omitting the card number resets the entire system or causes PXM switchover.
RPM-XF Boot-up Sequence
Each time you turn on power to the RPM-XF, by inserting the RPM-XF into the MGX 8850, it goes through the following boot sequence:
1. The RPM-XF 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-XF runtime software.
The source of the Cisco IOS image is determined by the configuration register setting. To verify 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 of 0x2102, the RPM-XF will come up and stay in boot mode until a run-time image is specified in the configuration. Entering the dspcds command on the PXM will show the card in Boot-Hold state.
3. The RPM-XF will look for the runtime image either in bootflash or in the C:FW directory on the PXM hard disk. The search for runtime image is determined by the boot system command entered.
•Entering the boot system x:<runtime_image_name> command will result in a search for a runtime image in the PXM C:FW directory on the PXM hard disk.
•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-XF reverts to the Boot-Hold state.
5. If a valid Cisco IOS image is found, then the RPM-XF searches for a valid configuration, which can reside in NVRAM or as a configuration file either in the PXM E:RPM directory 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 e:<config_file> command.
6. For normal RPM-XF operation, there must be a valid Cisco IOS image in the PXM45 C:FW directory or in bootflash, and a configuration in NVRAM. in bootflash, or in the PXM45 E:RPM directory on the PXM disk.
The first time you boot the RPM-XF, configure the RPM-XF interfaces and save the configuration to a file in NVRAM. Then follow the procedure described in "Initializing the RPM-XF Card." For information on the Cisco IOS instructions, see "Cisco IOS and Configuration Basics."
Verifying the Configuration
Enter the show commands to display the status of the all interfaces.
Using the show Commands to Verify the Interface Status
In the following procedure, enter the show commands to verify that interfaces are configured and operating correctly.
Step 1 Enter the show interface switch <number> command to specify one of the interfaces. Verify that the interface is up. When the interface and line protocol are up, this indicates that you have working interfaces as shown in the following examples.
Cell bus interface:
Router#show interfaces Switch 0
Switch0 is up, line protocol is up
Hardware is Mxt4400 Based ATM PA
MTU 4470 bytes, sub MTU 4470, BW 149760 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Encapsulation(s):AAL5, PVC mode
249 maximum active VCs, 16 current VCCs
VC idle disconnect time:300 seconds
Last input never, output never, output hang never
Last clearing of "show interface" counters 1d22h
Input queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0
Queueing strategy:fifo
Output queue :0/40 (size/max)
5 minute input rate 0 bits/sec, 1 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
267611 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
183681 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Serial bus interface:
Router#show interfaces Switch1
Switch1 is up, line protocol is up
Hardware is Mxt4700 Based ATM PA
MTU 4470 bytes, sub MTU 4470, BW 1197656 Kbit, DLY 100 usec,
reliability 255/255, txload 204/255, rxload 209/255
Encapsulation ATM, loopback not set
Encapsulation(s):AAL5, PVC mode
15743 maximum active VCs, 2009 current VCCs
VC idle disconnect time:300 seconds
Last input never, output never, output hang never
Last clearing of "show interface" counters 1d22h
Input queue:0/75/2/0 (size/max/drops/flushes); Total output drops:0
Queueing strategy:fifo
Output queue :0/40 (size/max)
5 minute input rate 982254000 bits/sec, 558113 packets/sec
5 minute output rate 958783000 bits/sec, 544781 packets/sec
354773033 packets input, 712453604 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
2 input errors, 1 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1464016596 packets output, 4226118672 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Step 2 Enter the show protocols command to display the protocols configured for the entire system and for the specific interfaces.
If necessary, return to configuration mode to add or remove protocol routing on the system or specific interfaces.
Verify that the line protocol is up. When the interface and line protocol are up, this indicates that you have a working interface, as shown below.
router2-slot14#show protocols
Global values:
Internet Protocol routing is enabled
Switch0 is up, line protocol is up
Switch1 is up, line protocol is up
Switch1.40 is up, line protocol is up
Internet address is 2.2.2.2/24
Switch1.41 is up, line protocol is up
Internet address is 3.3.3.3/24
Switch1.42 is up, line protocol is up
FastEthernet2/0 is administratively down, line protocol is down
FastEthernet2/1 is administratively down, line protocol is down
Step 3 Enter the show running-config command to display the running configuration file.
Step 4 Enter the show startup-config command to display the configuration stored in NVRAM.
Verify that the configuration is accurate for the system and that each interface is the same. If they are different from running-config, you may have forgotten to enter a copy run start command.
If the interface is down and you have configured it to be up, or if the displays indicate that the hardware is not functioning properly, be sure that the network interface is properly connected and terminated. If you still have problems bringing the interface up, contact a system administrator or TAC for assistance.
For detailed software configuration information, refer to the Cisco IOS configuration and command reference publications. These publications are available on the Documentation CD-ROM that came with your RPM-XF, or you can order printed copies.
Viewing the Hardware Configuration
The show version (or show hardware) command displays the configuration of the system hardware, for example, the number of each back card type installed, the software version, the names and sources of configuration files, and the boot images.
Note You may not be able to view hardware configuration information entering show version from a remote location.
The following is an example of the show version command output.
router2-slot14#show version
Cisco Internetwork Operating System Software
IOS (tm) RPMXF Software (RPMXF-P12-M), Experimental Version 12.2(20020418:192730) [swtools-zenith_fcs1_throttle.nightly 112]
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Mon 29-Apr-02 04:20 by
Image text-base:0x4000A940, data-base:0x41000000
ROM:System Bootstrap, Version 12.2(20020127:182207) [swtools-ROMMON 113], DevTest Software
BOOTLDR:RPMXF Software (RPMXF-BOOT-M), Experimental Version 12.2(20020321:034801) [swtools-zenith1.nightly 192]
router2-slot14 uptime is 5 hours, 38 minutes
System returned to ROM by reload
System image file is "x:rpmxf-p12-mz_fcs1.020429"
cisco RPM-XF (RPM-XF1) processor with 487424K/32768K bytes of memory.
R7000 CPU at 400Mhz, Implementation 39, Rev 3.3, 256KB L2, 4096KB L3 Cache
Last reset from service module reset
PXF processor tmc0 is running.
PXF processor tmc1 is running.
2 FastEthernet/IEEE 802.3 interface(s)
2 ATM network interface(s)
509K bytes of non-volatile configuration memory.
65536K bytes of Flash internal SIMM (Sector size 512KB).
Configuration register is 0x2
WARNING:Image contains R7k watch exception code.
Viewing the Boot Variable
The show bootvar command displays the boot variable, as shown in the following example.
Router#show bootvar
BOOT variable = x:rpmxf-p12-mz.1228T_XT1,12;
CONFIG_FILE variable = e:auto_config_slot02
BOOTLDR variable = bootflash:rpmxf-boot-mz.1228T_XT1
Configuration register is 0x2
Using show Commands to Display Back Card Information
To determine which type of back card is installed in your system, enter the show rpm command. In the following example, back card information is displayed for the RPM-XF card in slot 11.
Router>enable
Password:
Router#show rpm
RPM is in chassis slot 11
PXM has ip address 172.29.5.248
Active PXM is in slot 7
Network IO Interrupt Throttling:
throttle count=0, timer count=0
active=0, configured=1
netint usec=4000, netint mask usec=1000
RPM-XF IO FPGA Registers:
flash_watchdog_enable (0x14200000) : 0x00000033
flash_size (0x14200004) : 0x00000006
lev1_watchdog (0x14200008) : 0x0000FA00
led_control (0x14200014) : 0x00000002
lev2_watchdog (0x14200018) : 0x000FFFFF
int_status_0 (0x1420001C) : 0x00001000
int_mask_0 (0x14200024) : 0xC3CEFC81
masked_int_status_0 (0x1420006C) : 0x00000000
int_mask_1 (0x14200028) : 0x00000004
reset (0x1420002C) : 0x00000002
power_adjust (0x14200054) : 0x00000000
slot_id (0x14200058) : 0x0000000B
RPM EEPROM contents:
Hardware Revision :0.4
Part Number :73-5426-03
Board Revision :04
Deviation Number :0-0
Fab Version :02
PCB Serial Number :SAG06112DYF
RMA Test History :00
RMA Number :0-0-0-0
RMA History :00
Top Assy. Part Number :800-09307-03
Management Back Card EEPROM contents:
Hardware Revision :0.1
Part Number :73-5822-01
Board Revision :A0
Deviation Number :0-0
Fab Version :01
PCB Serial Number :SAK0519002H
RMA Test History :00
RMA Number :0-0-0-0
RMA History :00
Top Assy. Part Number :800-09492-01
zen2-slot14#sh rpm card-info
PXM Supports Redundancy :Yes
RPM Physical Slot Number :14
RPM Logical Slot Number :14
RPM Selftest :Disabled
RPM Selftest Period :0
RPM Backcard Type [Upper Slot] :MGX-XF-OC12
RPM Backcard Type [Lower Slot] :MGX-XF-UI
RPM Card State :ACTIVE
RPM Internal Card State :ACTIVE
RPM skipped initial configuration in the NVRAM:Yes
Configuration file was received from PXM:Yes
Auto Configuration File Used :None
RPM Redundancy Mode:Linked
RPM Redundancy Link Type:Primary
See "Verifying Ethernet Connectivity" in Chapter 4 to verify that each interface port is functioning properly.
Establishing 1:N Redundancy Between Two or More RPM-XF Cards
RPM-XF cards support 1:N redundancy, whereby one RPM-XF card can be configured as a redundant or secondary (backup) card for one or multiple primary RPM-XF cards, forming a redundant group. There can be multiple redundant groups in one shelf. RPM-XF 1:N redundancy is a warm redundancy, in which the configuration of a failed primary card is copied to the standby secondary card. All traffic to and from the primary RPM-XF card is switched to the secondary card after it becomes active. Because this is a warm redundancy solution, service interruption is expected. As with other service modules, the layer 2 state is restored when the secondary card becomes active. However, RPM-XF also performs layer 3 functionality, such as maintaining routing tables. The routing tables are created manually or by routing protocols, such as IGRP, BGP, or OSPF. Because routing protocols are used, the layer 3 state is restored within three to five minutes, depending on the protocol used and the size of the configuration.
RPM-XF 1:N redundancy supports the following features:
•Increases availability by decreasing the DPM of the network by reducing boot-up, switchover, and upgrade times.
•Supports L2 redundancy and restores L3 state via reconvergence.
•Support for up to 11 active (primary) RPM-XF cards per single redundant (standby or secondary) RPM-XF.
•Support for a maximum of 6 redundant groups per MGX 8850.
The redundant card must be present and active and must not have any resource partitions configured. Any connection configuration will cause the addred command to be rejected.
To establish a backup card for an RPM-XF card, use the following procedure.
Step 1 Log on to the switch.
Step 2 If you have not done so already, initialize both cards as described earlier in this chapter in the "Initializing the RPM-XF Card" section.
Step 3 Enter the dspcds command to verify that the primary and secondary RPM-XF card are in the "Active" state.
Step 4 Verify that there is an auto_config_slot# file on the E:RPM directory of PXM disk for the slot corresponding to the primary RPM-XF card. If not, do the following:
a. log onto the primary RPM-XF card and
b. add boot config e:auto_config_slot# to the configuration and
c. enter a write mem. With RPM-XF redundancy, configuration is always stored in the auto_config file on the PXM disk.
Step 5 Enter the addred command.
Switch.7.PXM.a > addred <redPrimarySlotNum> <redSecondarySlotNum> <redType>
Note After you enter the addred command, the switch resets the secondary card; therefore, the secondary card will be unavailable for a few minutes.
Step 6 When the reset is complete, enter the dspcds command to show the primary and secondary cards in the active and standby states, respectively.
The redundant RPM cards are shown in slots 2 and 10 with the standby card in slot 10.
Unknown.8.PXM.a > dspcds
Unknown System Rev:03.00 May. 13, 2002 18:55:56 GMT
Chassis Serial No: SCA0444006R Chassis Rev:E0 GMT Offset:0
Node Alarm:MAJOR
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----
01 Empty --- --- --- ---
02 Active/Active RPM_XF NONE 10 PRIMARY SLOT
03 Empty --- --- --- ---
04 Active/Empty RPM_PR NONE NA NO REDUNDANCY
05 Empty --- --- --- ---
06 Empty --- --- --- ---
07 Standby/Active PXM45B NONE 08 PRIMARY SLOT
08 Active/Active PXM45B NONE 07 SECONDARY SLOT
09 Empty --- --- --- ---
10 Standby/Active RPM_XF NONE 00 SECONDARY SLOT
11 Active/Empty RPM_XF NONE NA NO REDUNDANCY
12 Empty --- --- --- ---
13 Empty --- --- --- ---
14 Empty --- --- --- ---
15 Empty --- --- --- ---
Step 7 To display the redundancy relationship between all cards in the switch, enter the dspred command.
Redundant cards are displayed as shown below, indicating primary and secondary slot numbers, card types, card states, and redundancy type. Observe that the standby card's front panel CPU OK LED is Yellow.
Unknown.8.PXM.a > dspred
Unknown System Rev:03.00 May. 13, 2002 18:57:26 GMT
MGX8850 Node Alarm:MAJOR
Logical Primary Secondary Card Redundancy
Slot Slot Card Slot Red Type Type
State State
----- ----- ----------- ---- ------------ ------------ ----------
2 2 Active 10 Standby RPM-XF 1:n
7 7 Standby 8 Active PXM45 1:1
15 15 Empty 16 Empty SRM 1:1
31 31 Empty 32 Empty SRM 1:1
Note The standby card must not have any configurations and must not be configured. Therefore, do not provision the standby card.
Using switchredcd Command to Switch from Active to Standby Card
Enter the switchredcd command to manually change the active card to the standby card. You may want to do this if you need to remove the original active card from the MGX 8850 shelf. Before you begin this procedure, make sure that the destination card is in Standby mode. To change the active cards, follow the steps below. The primary or active card in slot 2 is switched to standby or secondary, and the standby card in slot 10 is switched to primary or active.
Step 1 Enter the switchredcd command.
Unknown.7.PXM.a > switchredcd 2 10
switchredcd: Do you want to proceed (Yes/No)? y
|
|
|
|---|---|
2 |
Active or primary card. |
10 |
Standby or secondary card. |
The card in slot 10 is now the active RPM-XF card, and the RPM-XF card in slot 2 is reset. It comes up in standby mode after a couple of minutes.
The new active card will not revert to standby mode automatically. Enter switchredcd to manually switch over the active card back to standby mode. This procedure is the only way the active card will switch over to standby, unless the active card fails.
Step 2 Enter the same command to switch the active card back to the original RPM-XF.
Unknown.7.PXM.a > switchredcd 10 2
switchredcd: Do you want to proceed (Yes/No)? y
|
|
|
|---|---|
10 |
Active or primary card. |
2 |
Standby or secondary card. |
Deleting Redundancy
To delete card redundancy, the primary card must be active, otherwise this command will be rejected.
Step 1 Enter the delred command followed by the primary card's slot number. For example,
Unknown.8.PXM.a > delred 2
Step 2 After deleting a card redundancy, enter the dspred command to display the redundancy relationship between the remaining redundant cards in the switch, as shown in the following example.
The remaining redundant cards are displayed as shown below, indicating primary and secondary slot numbers, card types, card states, and redundancy type.
Unknown.8.PXM.a > dspred
Unknown System Rev:03.00 May. 13, 2002 18:58:45 GMT
MGX8850 Node Alarm:MAJOR
Logical Primary Secondary Card Redundancy
Slot Slot Card Slot Red Type Type
State State
----- ----- ----------- ---- ------------ ------------ ----------
7 7 Standby 8 Active PXM45 1:1
15 15 Empty 16 Empty SRM 1:1
31 31 Empty 32 Empty SRM 1:1
Step 3 The secondary card is reset and comes back up as an active normal RPM-XF card (if it is the last primary card) that can be used for any other purpose. Note in the example below that the card in slot 10 is now active.
Unknown.8.PXM.a > dspcds
Unknown System Rev:03.00 May. 13, 2002 19:00:33 GMT
Chassis Serial No: SCA0444006R Chassis Rev:E0 GMT Offset:0
Node Alarm:MAJOR
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----
01 Empty --- --- --- ---
02 Active/Active RPM_XF NONE NA NO REDUNDANCY
03 Empty --- --- --- ---
04 Active/Empty RPM NONE NA NO REDUNDANCY
05 Empty --- --- --- ---
06 Empty --- --- --- ---
07 Standby/Active PXM45B NONE 08 PRIMARY SLOT
08 Active/Active PXM45B NONE 07 SECONDARY SLOT
09 Empty --- --- --- ---
10 Active/Active RPM_XF NONE NA NO REDUNDANCY
11 Active/Empty RPM_XF NONE NA NO REDUNDANCY
12 Empty --- --- --- ---
13 Empty --- --- --- ---
14 Empty --- --- --- ---
15 Empty --- --- --- ---
Adding Additional Primary Cards
You can add one or more additional RPM-XF cards as primary cards backed up by the secondary card by entering the addred command as follows.
Switch.7.PXM.a > addred <redPrimarySlotNum> <redSecondarySlotNum> <redType>
Repeat this command for each additional card you want to add to the secondary card backup protection. In the following example, the primary cards in slots 2, 3, and 4 are being backed up by the secondary RPM-XF in slot 10.
Note The secondary card does not get reset when adding additional primary cards to a redundancy group.
switch.7.PXM.a > addred 2 10 2
switch.7.PXM.a > addred 3 10 2
switch.7.PXM.a > addred 4 10 2
Upgrading Redundant RPM-XF Cards
The following procedure describes how to upgrade redundant RPM-XF cards.
Note Redundancy must be established as described above, before you use this procedure.
Step 1 Copy the new RPM-XF image to the location from which you want to boot the card. (PXM disk or bootflash or tftp server).
Step 2 On the primary/active RPM-XF card, modify the running configuration to boot from the new upgrade software.
Step 3 Enter the write memory or wr mem command to save the configuration.
Step 4 Enter the switchredcd command, as follows, to switch to the secondary card.
switch.7.PXM.a > switchredcd <fromSlot> <toSlot>
This step makes the secondary card active and resets the primary RPM-XF card. When the primary card resets, it loads the upgraded software defined in Step 1.
Step 5 Modify the configuration of the secondary card to boot from the new upgrade software and enter wr mem to save the configuration.
Step 6 Enter the switchredcd command, as follows, to switch to the primary card from the secondary card. This command is entered only after the primary card has booted and is in the standby state.
switch.7.PXM.a > switchredcd <fromSlot> <toSlot>
This step makes the upgraded primary card active and resets the secondary card. When the reset is complete, the secondary card runs the upgrade software and is now in the standby state.
Step 7 Continue this procedure from Step 2 for all remaining cards.
Upgrading Non-redundant RPM-XF Cards
The following procedure describes how to upgrade non-redundant RPM-XF cards.
Step 1 Copy the new RPM-XF image to the location from which you want to boot the card. (PXM disk or bootflash or tftp server).
Step 2 Configure the RPM-XF card to store its configuration on the PXM hard disk by entering the boot config e:auto_config_slot# command, or save it in NVRAM by entering the wr mem (write memory) command.
Step 3 Modify the running configuration to boot from the new upgrade software by entering the boot system command.
Step 4 Enter wr mem to save the configuration.
Step 5 Reset the RPM-XF card by entering the resetcd command from the PXM or the reload command from the RPM-XF.
Feedback