![[previous]](../../../graphics/l_arrow.gif){kind=icon}
![[next]](../../../graphics/r_arrow.gif){kind=icon}
This chapter explains how to download software to the EME and EMC modules. The procedures for downloading software depend on how many of each module are loaded in the chassis and whether you are using an in-band or out-of-band process.
The chapter covers these topics:
This section describes how to download software in-band (over the network) onto EME and EMC modules in various chassis configurations.
To download software in-band, you must first load all software images onto a file server. This section assumes that you have already done this. Your source for software images can be the software CD-ROM or the 3Com Web site:
http://support.3com.com/infodeli/swlib/index.htm
You can download software to a chassis that contains:
In this configuration, there is no redundancy. See "Single EME Chassis Configuration" next for procedures.
In this configuration, both the controller and management functions have redundancy. See "Dual EME Chassis Configuration" later in this chapter for procedures.
In this configuration, only the controller function has redundancy. See "EMC Configuration" later in this chapter for procedures.
CAUTION: Always download the boot software first and then download the operational software. If you do not follow this specified order, the modules may not function properly.
Downloading boot or operational software on the active EMC causes the EME and the EMC to automatically reset. (The active EMC and all of the EMEs automatically reset.) If you are using the console interface to the EME, the login prompt appears after the reset is complete. If you are using a Telnet connection to the EME, you need to reestablish the Telnet connection after the reset.
These instructions assume that you have only one EME (3CB9EME) module in the chassis and that it is installed in the lower-numbered slot.
CAUTION: Always download the boot software first and then download the operational software. If you do not follow this specified order, the modules may not function properly.
Downloading software to the EME or the EMC causes the modules to reset. If you are using the console interface to the EME, the following message and prompt appear:
This will cause the eme to reset.
Are you sure you want to continue download? (y, n):
If you enter y, the login prompt appears after the download is complete. If you are using a Telnet link to the EME, then you have to reestablish the link after you determine that the EME has completed its reset process.
To download the boot code to a single EME, enter the following commands at the prompts. You must enter the server IP address where the new code resides in the set tftp command along with the proper filename.
To download boot code to an EME located in slot 17, subslot 1, enter:
CB9000> download eme 17.1 boot_image <server address> <filename>.bt
The following messages appear after you enter this command:
Please stand by for download:
(Target will reset upon successful download completion)
(Target reset will cause this device to reset)
(All remote sessions will be terminated when this device resets)
(You will need to log back in):
Wait until the EME fully reboots. Then you can log in and enter the next set of commands.
To download operational code to the EME in slot 17, subslot 1, enter:
CB9000> download module 17.1 oper_image <server address> <filename>.op
Where <server address> is the IP address of the server where the software image resides and <filename> is the operational code file name.
At the reset prompt, enter y (yes) to continue with the download procedure. The following messages appear:
File transfer request pending.
Downloading file from external file server to eme - 000149992
Downloading file from eme to emc - 000149992
File transfer completed successfully.
The active emc and all of the emes will automatically reset.
These instructions assume that you have two EME (3CB9EME) modules in your chassis. The EMEs are labeled Primary and Secondary when you enter the show module all command.
In a two-EME configuration, you load all software on the Secondary EME first, then you load all software on the Primary EME. This approach minimizes disruption to your network and provides the most efficient way to ensure that the EME in the lower-numbered slot remains Primary.
Figure 2 shows a sample display for a 16-slot chassis, where the Primary EME is installed in slot 17.02 and the Secondary EME is installed in slot 18.02.
Figure 2 Sample Display from a 16-slot Chassis with Two EMEs Installed
To download boot software on the secondary EME, enter:
CB9000> download module 18.2 boot_image <server address> <filename>.bt
Where <server address> is the IP address of the server where the software image resides and <filename> is the name of the bootcode file.
The following messages and prompt appear:
This will cause the backup eme to reset.
Are you sure you want to continue the download? (y/n): y
File transfer request pending.
Downloading file from external file server to eme - 000105972
Downloading file from eme to backup eme - 000105972
File transfer completed successfully.
Module 18.2 will automatically reset.
To download operational software to the Secondary EME, enter:
CB9000> download module 18.2 oper_image <server address> <filename>.op
Where <server address> is the IP address of the server where the software image resides and <filename> is the name of the operational code file.
The following messages and prompt appear:
This will cause the backup eme to reset.
Are you sure you want to continue the download? (y/n): y
File transfer request pending.
Downloading file from external file server to eme - 000105972
Downloading file from eme to backup eme - 000105972
File transfer completed successfully.
Module 18.2 will automatically reset.
To verify that the correct versions of EME code were downloaded, enter the show module <slot.subslot> verbose command.
Example:
CB9000> show module 18.2 verbose
To download boot software to the Primary EME, enter:
CB9000> download eme boot_image <server address> <filename>.bt
Where <server address> is the IP address of the server where the software image resides and <filename> is the boot code file name.
The following messages and prompt appear:
This will cause the EME to reset.
Are you sure you want to continue the download? (y/n): y
File transfer request pending.
Additional text appears on the screen to indicate that download procedure has successfully completed.
To download operational software to the Primary EME, enter:
CB9000> download eme oper_image <server address>
<filename>.op
Where <server address> is the IP address of the server where the software image resides and <filename> is the operational code file name.
The system displays the following messages and prompt:
This will cause the EME to reset.
Are you sure you want to continue download? (y/n): y
File transfer request pending.
Additional text appears on the screen to indicate that the download procedure has successfully completed.
These instructions assume that you have one EME (3CB9EME) module and one EMC (3CB9EMC) module in your chassis and you have already downloaded the boot and operational software to the EME module.
To download boot software to the EMC, enter:
CB9000> download module 17.1 boot_image <server address> <filename>.bt
Where <server address> is the IP address of the server where the software image resides and <filename> is the name of the bootcode file.
The following message and prompt appear:
This will cause the active emc and all of the emes to reset.
Are you sure you want to continue the download? (y/n): y
Enter y (yes) to continue with the download procedure. The following messages appear:
File transfer request pending.
Downloading file from external file server to eme - 000105972
Downloading file from eme to emc - 000105972
File transfer completed successfully.
The active emc and all of the emes will automatically reset.
To download operational software to the EMC, enter:
CB9000> download module 17.1 oper_image <server address> <filename>.op
Where <server address> is the IP address of the server where the software image resides and <filename> is the name of the operational code file.
The following message and prompt appear:
This will cause the active emc and all of the emes to reset.
Are you sure you want to continue the download? (y/n): y
Enter y (yes) to continue with the download procedure. The following messages appear:
File transfer request pending.
Downloading file from external file server to eme - 000105972
Downloading file from eme to emc - 000105972
File transfer completed successfully.
The active emc and all of the emes will automatically reset.
To verify that the correct versions of EMC code was downloaded, enter the show module <slot.subslot> verbose command.
Additional text appears on the screen to indicate that the download procedure has successfully completed.
The EME module includes an out-of-band port, which provides an alternative download mechanism if the EME's operational code becomes corrupted and you cannot connect to the EME in-band.
EME software can become corrupted if a power cycle on the chassis occurs during the software download process. If the download does not complete or if the software becomes corrupted, the EME displays the following messages while it is resetting after you have performed a download:
Welcome to Boot Services version v3.0
8192 kBytes flash memory installed.
ERROR: Checksum failed for operational code.
Enter download out_of_band command to initiate download.
Boot>
To perform an out-of-band download, have the following items available:
Next, follow these steps:
1 . From the EME console interface, set the terminal baud rate:
Boot> set terminal console baud 38400
3Com recommends that you use a high rate when you set the terminal baud rate.
2 . After you have reestablished your console connection at this baud rate, enter:
Boot> download out_of_band eme operational
Confirm with carriage return.
Erasing flash...done
Please initiate file transfer sequence.
Enter ~C to get>Local command? prompt.
3 . Enter the following command using the correct pathname to your image file:
>Local command? xmodem -sbp emev20001.op
The system displays the following message. (This is an example of an image file from the directory tftpboot.)
XMODEM Version 3.0 (July 1999) -- Unix-Microcomputer File Transfer Facility
File /tftpboot/emev20001.op Ready to send in Binary mode
Estimated File Size 1038K, 8300 Sectors, 1062376 Bytes
Can't change TTY mode
----
XMODEM Send Function
File Name: /tftpboot/emev20001.op
File Size 1038K, 8300 Records, 1062376 Bytes
Estimated transmission time 2 hours 43 minutes 56 seconds
The system reboots and then you can log in and continue.
The number of bytes in the previous example are not accurate. This is only a sample of what appears.