Cisco Cisco IOS Software Release 12.2

If Step 

 worked, you need not perform the rest of this recovery procedure. Instead, you should boot the 

Cisco IOS software and proceed to Step 

If Step 

 did not work, the rommon prompt is returned and you must proceed to Step 

 to continue with 

the recovery procedure.

If the correct dboot2 image is not in bootflash or the image is corrupt, perform the following steps to 
use the xmodem command to download a valid dboot2 image to use to boot the DSLAM:

Open a terminal emulation window (such as Hyper Terminal) on a PC that is connected to the 
DSLAM through a console port.

Configure the following terminal emulation settings: port = com1 or com2, data rate = 9600, bits = 8, 
parity = none, stop bits = 1. You must use these values for the recovery procedure to work.

Make sure that the PC contains a valid dboot2 image or is connected to a network where a dboot2 
image is stored on a server.

On the DSLAM, issue the following command to copy the dboot2 image to the specified filename. 
The command creates a temporary copy of the dboot2 image on the DSLAM; therefore, you must copy 
the image to bootflash or it will be lost when you reload the DSLAM (Step 

).

rommon> xmodem filename

Wait for a prompt indicating that rommon is ready to receive the file.

In the Hyper Terminal window on the PC, click Transfer in the menu bar at the top of the window 
and select Send File.

Select Xmodem as the protocol, and specify the name of the dboot2 image to copy to the DSLAM. 

Click Send to start the copy.

It may take 1 hour or more for the copy to complete.

When the download completes, the DSLAM boots automatically.

To complete the recovery procedure, copy the dboot2 image to bootflash memory (for example, 
using TFTP). If you do not perform this step, the dboot2 image will be lost when you reload the DSLAM.

To finish booting the DSLAM, issue the following command:

DSLAM> reload

The following sections describe the limitations and restrictions for Cisco IOS software DSLAM releases.

When using NI-2 cards in a redundant fashion, we recommend that you issue the command redundancy 
reload-peer on the active NI-2 card after the system has loaded. This causes the redundant NI-2 to reload 
and ensures that the redundant configuration is operational.