3Com ENTERPRISE OS 11.3 manual b Upgrade your firmware to version 2.6 using

Upgrading Software Only 43

8NETBuilder II with CEC only — (The CEC module is not supported in software version 11.3. However, you can use the utilities to upgrade your CEC module to software version 10.1 or earlier.) If the upgrade is successful, and if you have not already done so in step 2, upgrade the CEC firmware by following these steps:

a Make sure there is a floppy diskette with write access in the floppy drive on the bridge/router. Make sure that the contents of the diskette you intend to use can be overwritten. Perform a manually recoverable firmware upgrade using the option -m if you do not want the floppy diskette formatted.

bUpgrade your firmware to version 2.6 using:

bcmsysupgrade -s:upgrade_cec_fw -V:<version you are upgrading to>

<device>

After the firmware has been upgraded, the bridge/router reboots.

9NETBuilder II only — If the upgrade is successful, and the NETBuilder II bridge/router has a multiport HSS module or an MP module, upgrade the firmware for all these modules using:

bcmsysupgrade -s:upgrade_io_fw -m <device>

The bridge/router reboots after the firmware is upgraded.

Manual Recovery This section describes how to perform a software upgrade with manual recovery of a bridge/router that does not include a hardware upgrade. See Chapter 3 for the memory requirements for manual recovery.

Whenever you specify an option with bcmsysupgrade (such as -m), you must repeat that option for all steps in the procedure. See Table 4 on page 40 or “bcmsysupgrade” on page 81 for a list of the options available to use with the bcmsysupgrade utility.

To upgrade the bridge/router, follow these steps:

1Back up your current software to the NMS using:

bcmsysupgrade [-options] -s:from_nb -m <device>

where [-options] lets you specify the -EncryptionLicenseRead flag that indicates you have read and understand the encryption license agreement notice and <device> is the IP address or hostname of the bridge/router you are upgrading.

CAUTION: When upgrading to a package containing encryption, you must specify the -EncyrptionLicenseRead option flag. If you attempt to upgrade to an encrypted package and you have not specified the -EncryptionLicenseRead option, the upgrade will fail.

The bcmsysupgrade utility only backs up the files in the primary boot source. To archive both the primary and secondary boot sources, use bcmbackup instead of bcmsysupgrade. See “bcmbackup” on page 73 for more information.

2Update your configuration files using:

bcmsysupgrade -s:update -m <device>

3Copy the upgraded software to the bridge/router using:

bcmsysupgrade -s:to_nb -m <device>

4Accept your upgrade using:

bcmsysupgrade -s:accept -m <device>