Maintaining the MGX RPM
This appendix describes maintenance procedures you might need to perform as your internetworking needs change. It contains the following sections:
•Reading Front Panel LEDs
•Recovering a Lost Password
•Following is an overview of the steps in the password recovery procedure:
•Virtual Configuration Register Settings
•Copying a Cisco IOS Image to Flash Memory
Reading Front Panel LEDs
The LEDs on the front panel of the RPM indicate the current operating condition of the RPM. You can observe the LEDs, note the fault condition the RPM is encountering. Contact your system administrator or TAC, if necessary.
Figure A-1 shows the front panel and LEDs of the RPM. Table A-1 shows how to interpret front-panel LED activity.
Figure A-1 MGX 8850 RPM Front Panel LEDs
The LEDs are labeled and indicate overall status and activity on ports by flickering. When there is heavy activity on a port, the LED might be on constantly. If an LED is not on when the port is active and the cable is connected correctly, there might be a problem with the port.
Table A-1 Front Panel LEDs
|
|
|
CPU STATUS |
OFF |
CPU is not operational |
GREEN |
CPU is running |
BC1 STATUS |
OFF |
Port Adapter one is not present |
GREEN |
Port Adapter one is present and enabled |
BC2 STATUS |
OFF |
Port Adapter two is not present |
GREEN |
Port Adapter two is present and enabled |
CB RX CELLS |
GREEN |
Cells are being received from the cellbus |
CB TX CELLS |
GREEN |
Cells are being transmitted to the cellbus |
Recovering a Lost Password
This section describes how to recover a lost enable or console login password, and how to replace a lost enable secret password on your RPM.
Note It is possible to recover the enable or console login password. The enable secret password is encrypted, however, and must be replaced with a new enable secret password.
Following is an overview of the steps in the password recovery procedure:
•If you can log in to the RPM, enter the show version command to determine the existing configuration register value.
•Press the Break key to get to the bootstrap program prompt (ROM monitor). You might need to reload the system image by power cycling the RPM.
•Change the configuration register so the following functions are enabled: Break; ignore startup configuration; boot from Flash memory.
Note The key to recovering a lost password is to set the configuration register bit 6 (0x0040) so that the startup configuration (usually in NVRAM) is ignored. This will allow you to log in without using a password and to display the startup configuration passwords.
•Power cycle the RPM by turning power off and then back on.
•Log in to the RPM and enter the privileged EXEC mode.
•Enter the show startup-config command to display the passwords.
–Recover or replace the displayed passwords.
–Change the configuration register back to its original setting.
Note To recover a lost password if Break is disabled on the RPM, you must have physical access to the RPM.
Password Recovery Procedure
Complete the following steps to recover or replace a lost enable, enable secret, or console login password.
Step 1 Attach an ASCII terminal to the console port on your RPM.
Step 2 Configure the terminal to operate at 9600 baud, 8 data bits, no parity, and 2 stop bits.
Step 3 If you can log in to the RPM as a nonprivileged user, enter the show version command to display the existing configuration register value. Note the value for use later. If you cannot log in to the RPM at all, go to the next step.
Step 4 Press the Break key or send a Break from the console terminal.
If Break is enabled, the RPM enters the ROM monitor, indicated by the ROM monitor prompt (rommon1>). Proceed to Step 6.
If Break is disabled, power cycle the RPM (turn the RPM off or unplug the power cord, and then restore power). Then proceed to Step 5.
Step 5 Within 60 seconds of restoring the power to the RPM, press the Break key or send a Break. This action causes the RPM to enter the ROM monitor and display the ROM monitor prompt (rommon1>).
Step 6 To set the configuration register on a RPM, use the configuration register utility by entering the confreg command at the ROM monitor prompt, as follows.
Answer yes to the enable "ignore system config info"? question and note the current configuration register settings.
Step 7 Initialize the RPM by entering the reset command as follows: rommon2> reset
The RPM will initialize, the configuration register will be set to 0x142, and the RPM will boot the system image from Flash memory and enter the system configuration dialog (setup), as follows.
--- System Configuration Dialog --
Step 8 Enter no in response to the system configuration dialog prompts until the following message is displayed:
Press RETURN to get started!
Step 9 Press Return. The user EXEC prompt is displayed as follows:
Step 10 Enter the enable command to enter the privileged EXEC mode. Then enter the show startup-config command to display the passwords in the configuration file, as follows.
Step 11 Scan the configuration file display looking for the passwords (the enable passwords are usually near the beginning of the file, and the console login or user EXEC password is near the end). The passwords displayed will look something like this:
enable secret 5 $1$ORPP$s9syZt4uKn3SnpuLDrhuei
enable password 23skiddoo
The enable secret password is encrypted and cannot be recovered; it must be replaced. The enable and console passwords may be encrypted or clear text. Proceed to the next step to replace an enable secret, console login, or enable password. If there is no enable secret password, note the enable and console login passwords if they are not encrypted and proceed to Step 16.
Caution
Do not execute the next step unless you determine you must change or replace the enable, enable secret, or console login passwords. Failure to follow the steps as shown may cause you to erase your RPM configuration.
Step 12 Enter the configure memory command to load the startup configuration file into running memory. This action allows you to modify or replace passwords in the configuration.
Step 13 Enter the privileged EXEC command configure terminal to enter configuration mode.
Hostname# configure terminal
Step 14 To change all three passwords, enter the following commands.
Hostname(config)# enable secret newpassword1
Hostname(config)# enable password newpassword2
Hostname(config)# line con 0
Hostname(config-line)# password newpassword3
Change only the passwords necessary for your configuration. You can remove individual passwords by using the no form of the above commands. For example, entering the no enable secret command will remove the enable secret password.
Step 15 You must configure all interfaces to be not administratively shutdown, as follows.
Hostname(config)# interface fastethernet 0/0
Hostname(config-int)# no shutdown
Enter the equivalent commands for all interfaces that were originally configured. If you omit this step, all interfaces will be administratively shutdown and unavailable when the RPM is restarted.
Step 16 Use the config-register command to set the configuration register to the original value noted in Step 3 or Step 7, or to the factory default value 0x2102, as follows.
Hostname(config)# config-register 0x2102
Step 17 Press Ctrl-Z or enter end to exit configuration mode and return to the EXEC command interpreter.
Caution
Do not execute the next step unless you have changed or replaced a password. If you skipped Step 12 through Step 15, skip to Step 19. Failure to observe this caution will cause you to erase your RPM configuration file.
Step 18 Enter the copy running-config startup-config command to save the new configuration to nonvolatile memory.
Step 19 Enter the reload command to reboot the RPM.
Step 20 Log in to the RPM with the new or recovered passwords.
This completes the steps for recovering or replacing a lost enable, enable secret, or console login password.
Virtual Configuration Register Settings
The RPM has a 16-bit virtual configuration register, which is written into NVRAM. You might want to change the virtual configuration register settings for the following reasons:
•Set and display the configuration register value.
•Force the system into the ROM monitor or boot ROM.
•Select a boot source and default boot filename.
•Enable or disable the Break function.
•Control broadcast addresses.
•Set the console terminal baud rate.
•Recover a lost password (ignore the configuration file in NVRAM).
•Enable Trivial File Transfer Protocol (TFTP) server boot.
Table A-2 lists the meaning of each of the virtual configuration memory bits and defines the boot field names.
Caution
To avoid confusion and possibly halting the RPM, remember that valid configuration register settings might be combinations of settings and not just the individual settings listed in
Table A-2. For example, the factory default value of 0x2102 is a combination of settings.
Table A-2 Virtual Configuration Register Bit Meaning
|
|
|
00-03 |
0x0000-0x000F |
Boot field |
06 |
0x0040 |
Causes system software to ignore the contents of NVRAM (startup-config) |
07 |
0x0080 |
OEM bit is enabled |
08 |
0x0100 |
Break is disabled |
10 |
0x0400 |
IP broadcast with all zeros |
11-12 |
0x0800-0x1000 |
Console line speed |
13 |
0x2000 |
Load the boot ROM software if a Flash boot fails five times |
14 |
0x4000 |
IP broadcasts do not have network numbers |
15 |
0x8000 |
Enable diagnostic messages and ignore the contents of NVRAM |
Changing Configuration Register Settings
Perform the following steps to change the configuration register while running Cisco IOS software.
Step 1 Enter the enable command and your password to enter privileged mode.
Step 2 Enter the configure terminal command at the privileged-level system prompt (#).
MGX 8850-RPM# configure terminal
Step 3 To set the contents of the configuration register, enter the configuration command config-register value, where value is a hexadecimal number preceded by 0x (refer to Table A-2 and Table A-3).
MGX 8850-RPM(config)# config-register 0xvalue
(The virtual configuration register is stored in NVRAM.)
Table A-3 Explanation of Boot Field (Configuration Register Bits 00 to 03)
|
|
0x0 |
Stops the boot process in the ROM monitor. |
0x1 |
Stops the boot process in the boot ROM monitor. |
0x2 |
Full boot process, which loads the Cisco IOS image in Flash memory. |
0x3-0xF |
Specifies a default filename for booting over the network from a TFTP server. Enables boot system commands that override the default filename for booting over the network from a TFTP server. |
Step 4 Press Ctrl-Z to exit configuration mode.
The new settings will be saved to memory; however, the new settings are not effective until the system software is reloaded by rebooting the RPM.
Step 5 To display the configuration register value currently in effect and the value that will be used at the next reload, enter the show version EXEC command. The value displays on the last line of the screen display:
Configuration register is 0x142 (will be 0x102 at next reload)
Step 6 Reboot the RPM.
The new value takes effect. Configuration register changes take effect only when the RPM restarts, which occurs when you turn the system on, or when you enter the reload command.
Virtual Configuration Register Bit Meanings
The lowest four bits of the virtual configuration register (bits 3, 2, 1, and 0) form the boot field (see Table A-3). The boot field specifies a number in binary form. If you set the boot field value to 0, you must boot the operating system manually by entering the b command at the bootstrap prompt, as follows:
> b [ tftp ] flash filename
The b command options are as follows:
•b—Boots the default system software from ROM
•b flash—Boots the first file in Flash memory
•b filename [host]—Boots from the network using a TFTP server
•b flash [filename]—Boots the file filename from Flash memory
For more information about the command b [tftp] flash filename, refer to the Cisco IOS configuration publications.
If you set the boot field value to a value of 0x2 through 0xF, and a valid system boot command is stored in the configuration file, the RPM boots the system software as directed by that value. If you set the boot field to any other bit pattern, the RPM uses the resulting number to form a default boot filename for booting from the network using a TFTP server (see Table A-4).
Table A-4 Default Boot Filenames
|
|
|
|
|
bootstrap mode |
0 |
0 |
0 |
0 |
ROM software |
0 |
0 |
0 |
1 |
cisco2-igs |
0 |
0 |
1 |
0 |
cisco3-igs |
0 |
0 |
1 |
1 |
cisco4-igs |
0 |
1 |
0 |
0 |
cisco5-igs |
0 |
1 |
0 |
1 |
cisco6-igs |
0 |
1 |
1 |
0 |
cisco7-igs |
0 |
1 |
1 |
1 |
cisco10-igs |
1 |
0 |
0 |
0 |
cisco11-igs |
1 |
0 |
0 |
1 |
cisco12-igs |
1 |
0 |
1 |
0 |
cisco13-igs |
1 |
0 |
1 |
1 |
cisco14-igs |
1 |
1 |
0 |
0 |
cisco15-igs |
1 |
1 |
0 |
1 |
cisco16-igs |
1 |
1 |
1 |
0 |
cisco17-igs |
1 |
1 |
1 |
1 |
In the following example, the virtual configuration register is set to boot the RPM from Flash memory and to ignore Break at the next reboot of the RPM.
Enter configuration commands, one per line.
Edit with DELETE, CTRL/W, and CTRL/U; end with CTRL/Z
boot system flash [filename]
The RPM creates a default boot filename as part of the automatic configuration processes. The boot filename consists of cisco plus the octal equivalent of the boot field number, a hyphen, and the processor type.
Note A boot system configuration command in the RPM configuration in NVRAM overrides the default boot filename.
Bit 8 controls the console Break key. Setting bit 8 (the factory default) causes the processor to ignore the console Break key. Clearing bit 8 causes the processor to interpret the Break key as a command to force the system into the bootstrap monitor, thereby halting normal operation. A break can be sent in the first 60 seconds while the system reboots, regardless of the configuration settings.
Bit 10 controls the host portion of the IP broadcast address. Setting bit 10 causes the processor to use all zeros; clearing bit 10 (the factory default) causes the processor to use all ones. Bit 10 interacts with bit 14, which controls the network and subnet portions of the broadcast address (see Table A-5).
Table A-5 Configuration Register Settings for Broadcast Address Destination
|
|
|
Off |
Off |
<ones> <ones> |
Off |
On |
<zeros> <zeros> |
On |
On |
<net> <zeros> |
On |
Off |
<net> <ones> |
Bits 11 and 12 in the configuration register determine the baud rate of the console terminal. Table A-6 shows the bit settings for the four available baud rates. (The factory-set default baud rate is 9600.)
Table A-6 System Console Terminal Baud Rate Settings
|
|
|
9600 |
0 |
0 |
4800 |
0 |
1 |
1200 |
1 |
0 |
2400 |
1 |
1 |
Bit 13 determines the server response to a bootload failure. Setting bit 13 causes the server to load operating software from ROM after five unsuccessful attempts to load a boot file from the network. Clearing bit 13 causes the server to continue attempting to load a boot file from the network indefinitely. By factory default, bit 13 is set to 1.
Enabling Booting from Flash Memory
To disable Break and enable the boot system flash command, enter the config-register command with the value shown in the following example:
MGX 8850-RPM# config tRPM
Enter configuration commands, one per line.
Edit with DELETE, CTRL/W, and CTRL/U; end with CTRL/Z
Copying a Cisco IOS Image to Flash Memory
You may need to copy a new Cisco IOS image to Flash memory whenever a new image or maintenance release becomes available. Enter the copy tftp flash command for the copy procedure.
Perform the following steps to copy a new image to Flash memory from a TFTP server.
Step 1 Enter the show flash command to ensure that there is enough space available before copying a file to Flash memory. Compare the size of the file you want to copy to the amount of available Flash memory displayed.
Step 2 Make a backup copy of the current image. Enter enable mode and then enter the copy flash tftp command. Ensure that the filename of the current image is different from the new image so that you do not overwrite it.
Step 3 Enter the copy tftp flash command to copy the new image into Flash memory:
MGX 8850-RPM# copy tftp flash
The following message displays:
This process will accept the copy options and then terminate
the current system image to use the ROM based image for the copy.
Routing functionality will not be available during that time.
If you are logged in via telnet, this connection will terminate.
Users with console access can see the results of the copy operation.
Step 4 Press Return to confirm.
If there is an image already in Flash memory, the RPM displays the name and size of the file. The RPM prompts you for the IP address or name of the remote host.
Address or name of remote host [hostname]?
The remote host can be a server or another RPM with a valid Flash system software image.
Step 5 Enter the IP address or name of the remote host. The RPM then prompts you for the name of the source file.
Step 6 Enter the name of the source file. The following prompt displays:
Destination file name [filename]?
Step 7 Press Return to accept the default filename or enter a different filename. Messages similar to the following ones display.
Accessing file 'master/igs-j-l.110-4.2' on hostname...
Loading master/igs-j-l.110-4.2 from 172.16.72.1 (via Ethernet0): ! [OK]
Erase flash device before writing? [confirm] yes
Step 8 Enter yes to erase the contents of Flash memory. The following message displays.
Flash contains files. Are you sure you want to erase? [confirm] yes
Step 9 Enter yes to confirm that you want to erase the contents of Flash memory. Messages similar to the following display.
%SYS-5-RELOAD: Reload requested
%FLH: master/igs-j-l.110-4.2 from 172.16.72.1 to flash ...
1 3459776 username/igs-i-l
[3459840 bytes used, 4928768 available, 8388608 total]Configuration mapped ip address
172.16.72.1 to hostname
Accessing file 'master/igs-j-l.110-4.2' on hostname...
Loading master/igs-j-l.110-4.2 from 172.16.72.1 (via Ethernet0): ! [OK]
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Loading master/igs-j-l.110-4.2 from 172.16.72.1 (via Ethernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 6196336/8388608 bytes]
Verifying checksum... OK (0x2997)
Flash copy took 0:03:38 [hh:mm:ss]
%FLH: Re-booting system after download
The system reboots using the new image in Flash memory.
Note For more information on the copy tftp flash command and other related commands, refer to the Cisco IOS command reference publications.