3Com ENTERPRISE OS 11.3 Upgrading Software User Manual To The 97b02aa8 7839 4bed B13a Eac5b6a890e7

User Manual: 3Com ENTERPRISE OS 11.3 to the manual

Open the PDF directly: View PDF .
Page Count: 120

Download
Open PDF In Browser	View PDF

Upgrading Enterprise OS
Software

Software version 11.3

http://www.3com.com/
Part No. 09-1551-001
Published May 1999

3Com Corporation
5400 Bayfront Plaza
Santa Clara, California
95052-8145

© 3Com Corporation, 1999. All rights reserved. No part of this documentation may be reproduced in
any form or by any means or used to make any derivative work (such as translation, transformation, or
adaptation) without permission from 3Com Corporation.
3Com Corporation reserves the right to revise this documentation and to make changes in content from
time to time without obligation on the part of 3Com Corporation to provide notification of such revision
or change.
3Com Corporation provides this documentation without warranty of any kind, either implied or
expressed, including, but not limited to, the implied warranties of merchantability and fitness for a
particular purpose. 3Com may make improvements or changes in the product(s) and/or the program(s)
described in this documentation at any time.
UNITED STATES GOVERNMENT LEGENDS:
If you are a United States government agency, then this documentation and the software described
herein are provided to you subject to the following restricted rights:
For units of the Department of Defense:
Restricted Rights Legend: Use, duplication, or disclosure by the Government is subject to restrictions as
set forth in subparagraph (c) (1) (ii) for Restricted Rights in Technical Data and Computer Software Clause
at 48 C.F.R. 52.227-7013. 3Com Corporation, 5400 Bayfront Plaza, Santa Clara, California 95052-8145.
For civilian agencies:
Restricted Rights Legend: Use, reproduction, or disclosure is subject to restrictions set forth in
subparagraph (a) through (d) of the Commercial Computer Software - Restricted Rights Clause at 48
C.F.R. 52.227-19 and the limitations set forth in 3Com Corporation’s standard commercial agreement for
the software. Unpublished rights reserved under the copyright laws of the United States.
If there is any software on removable media described in this documentation, it is furnished under a
license agreement included with the product as a separate document, in the hard copy documentation,
or on the removable media in a directory file named LICENSE.TXT. If you are unable to locate a copy,
please contact 3Com and a copy will be provided to you.
Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or
may not be registered in other countries.
3Com, Boundary Routing, Net Age, NETBuilder, NETBuilder II, OfficeConnect, SuperStack, and Transcend
are registered trademarks of 3Com Corporation. 3TECH and PathBuilder are trademarks of 3Com
Corporation. 3ComFacts is a service mark of 3Com Corporation.
CompuServe is a registered trademark of CompuServe, Inc. Windows is a registered trademark of
Microsoft Corporation. Solaris is a registered trademark of Sun Microsystems, Inc. SunOS is a trademark
of Sun Microsystems, Inc. UNIX is a registered trademark of Xopen Company Limited. IBM, APPN, and
SNA are registered trademarks of International Business Machines Corporation. HP is a registered
trademark of Hewlett-Packard Company. Novell is a registered trademark of Novell, Inc. ProComm Plus
for Windows is a registered trademark of DataStorm Corporation. Crosstalk for Windows is a registered
trademark of Attachmate Corporation.
Other brand and product names may be registered trademarks or trademarks of their respective holders.
The software contained in this product may contain encrypted product which may not be
exported or transferred from the U.S. or Canada without an approved U.S. Department of
Commerce export license.
Printed on recycled paper.

CONTENTS

ABOUT THIS GUIDE
Conventions 7
Year 2000 Compliance

OVERVIEW
Upgrade Tools and Process 9
How the Utilities Work 10
Primary, Secondary, and Test Boot Sources
Automatic or Manual Recovery 10
Rules and Support Limitations 11
Take Time to Plan 11

INSTALLING THE UTILITIES ON A NETWORK MANAGEMENT STATION
Installing the Utilities on a Windows System 13
Installing the Utilities on a UNIX System 14
Preparing for the Installation 14
Procedure 14
Setting up for Auto Startup 16

PLANNING AND PREPARING THE UPGRADE
Setting up for TFTP File Transfers 17
Setting up for FTP File Transfers 17
Automatic Recovery 18
Manual Recovery 19
Checking DRAM 20
Checking Flash Memory 20
Checking the Software Version 21
Planning Tables 21

UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION
Status and Settings Pages 27
Settings Page 28
Verifying for Upgrading 29
Installing Software on the NMS
Procedure 30
Upgrading Software 31

UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES
Preparing for the Upgrade 35
Setting up for TFTP File Transfers 36
Setting up for FTP File Transfers 36
Prediagnosing System Problems 37
Installing the Software on the NMS 37
Software Directories 38
Using the Bcmsysupgrade Utility to Upgrade 39
Filenames 40
NETBuilder II Bridge/Router 40
SuperStack II NETBuilder and OfficeConnect NETBuilder Bridge/Routers
PathBuilder S5xx Series Switch 41
Upgrading Software Only 41
Automatic Recovery 41
Manual Recovery 43
If the Bridge/Router or Switch Does Not Boot 44
Upgrading Hardware and Software 44
Automatic Recovery 44
Manual Recovery 47
If the Bridge/Router or Switch Does Not Boot 49

UPGRADING THE SOFTWARE IMAGE ONLY
Preparing for the Upgrade 51
Setting up for TFTP File Transfers 52
Setting up for FTP File Transfers 52
Using Upgrade Link 53
Verifying the Bridge/Router for Upgrading 54
Upgrading the Image 54
Using the Command-Line Utilities 57
Installing the NETBuilder Software 57
Prediagnosing System Problems 57
Upgrading Using Automatic Recovery 57
Upgrading Using Manual Recovery 58
Using the Enterprise OS User Interface 59

BACKING UP AND RESTORING SOFTWARE
Setting Up for TFTP File Transfers 62
Setting Up for FTP File Transfers 62
Backing Up the Software 63
Using NETBuilder Upgrade Link 63
Using the Command Line Utilities 63
Verifying the Device for Backing Up 63
Backing Up the Software 64
Using the Command-Line 64
Prediagnosing System Problems 64
Backing Up the Software 65

Directory Paths 65
Restoring Software from a Backup 66
Configuring IP Routing 66
Configuring SNMP 66
Mapping Hostnames Using the etc/snmp.cfg File 67
Restoring the Software Using Upgrade Link 68
Verifying the Device for Restoring 68
Restoring the Software 68
Restoring the Software Using the Command-Line 69
Prediagnosing System Problems 69
Restoring the Software 69

REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES
Accessing and Downloading the Utilities
Downloading the Utilities 71
Downloading UNIX Files 71
Downloading Windows Files 71
Update Log File 72
Utility Descriptions and Syntax 72
Overview 72
Getting Help 73
bcmbackup 73
bcmconfig 74
bcmctrl 75
bcmdf 76
bcmdiagnose 77
bcminstall 78
bcmloadconfig 79
bcmnbrus 80
bcmrestore 80
bcmsetup 81
bcmsysupgrade 81
bcmuname 82
bcmupdate 83
UpgradeLink 84

TROUBLESHOOTING
Getting Help 85
Man Pages 85
HTML Help 85
General Troubleshooting Error Messages 85
Return Codes from bcmdiagnose 86
Hardware-Related Messages 87
Installation Troubleshooting Messages 87
Installing the Enterprise OS Upgrade Management Utilities
Determining Connectivity 88
Validating the SNMP Service Configuration 88

Testing the NMS/ TFTP Configuration 89
Creating an Upgrade File 89
Uploading an Upgrade File 90
Downloading an Upgrade File 91

CHOOSING A SOFTWARE PACKAGE
NETBuilder II Upgrade Migration Path 93
SuperStack II NETBuilder Upgrade Migration Path 96
SuperStack II NETBuilder SI Upgrade Migration Path 98
OfficeConnect NETBuilder Upgrade Migration Path 99
PathBuilder Upgrade Migration Path 101

MOUNTING THE CD-ROM ON A UNIX PLATFORM
Mounting the CD-ROM on Solaris 2.5.x 103
Mounting a Local CD-ROM Drive 103
Mounting from a Remote CD-ROM Drive 103
Mounting the CD-ROM on HP-UX 10.x 105
Mounting from a Local CD-ROM Drive 105
Mounting from a Remote CD-ROM Drive 105
Mounting the CD-ROM on IBM AIX 4.1.x Through 4.2.x
Mounting from a Local CD-ROM Drive 106
Mounting from a Remote CD-ROM Drive 106
Unmounting the CD-ROM 107

TECHNICAL SUPPORT
Online Technical Services 109
World Wide Web Site 109
3Com Knowledgebase Web Services 109
3Com FTP Site 109
3Com Bulletin Board Service 110
Access by Analog Modem 110
Access by Digital Modem 110
3Com Facts Automated Fax Service 110
Support from Your Network Supplier 110
Support from 3Com 111
Returning Products for Repair 112

GLOSSARY
INDEX
3COM CORPORATION LIMITED WARRANTY

106

ABOUT THIS GUIDE

This guide describes how to upgrade your NETBuilder® bridge/router to
Enterprise OS software version 11.3. This guide also describes how to upgrade
your PathBuilder™ S5xx series switch to Enterprise OS software version 11.3.
You can also use this guide to upgrade your NETBuilder bridge/router to previous
software versions (8.0 through 11.2) by specifying the correct options.
You can upgrade your bridge/router from software version 8.0 through 11.2 to
any software version after 8.0 through 11.3 on the following platforms:
■
■

NETBuilder II® bridge/router with DPE
NETBuilder II bridge/router with CEC — The CEC module is not supported after
software version 10.1, but you can use the 11.2 utilities to upgrade a CEC
module to a DPE module, or to upgrade the CEC module to software version
10.1 or earlier.

■

SuperStack® II NETBuilder SI bridge/router

■

SuperStack II NETBuilder Token Ring bridge/router

■

OfficeConnect® NETBuilder bridge/router

You can upgrade your PathBuilder S5xx series switch to Enterprise OS software
version 11.3 from version 11.1.1 and version 11.2.
This guide also describes how to complete an image-only upgrade for patches,
new packages, or software recovery. It also describes how to backup and restore
software on a network management station.
See the Enterprise OS Software Version 11.3 Release Notes for any changes or
additions to the information in this guide.

Conventions

Table 1 and Table 2 list conventions that are used throughout this guide.
Table 1 Notice Icons
Icon

Notice Type

Description

Information note

Important features or instructions

Caution

Information to alert you to potential damage to a
program, system, or device

Warning

Information to alert you to potential personal injury

ABOUT THIS GUIDE

Table 2 Text Conventions
Convention

Description

Syntax

The word “syntax” means you must evaluate the syntax provided and
supply the appropriate values. Placeholders for values you must supply
appear in angle brackets. Example:
Enable RIPIP using:
SETDefault ! -RIPIP CONTrol = Listen
In this example, you must supply a port number for .

Commands

The word “command” means you must enter the command exactly as
shown in text and press the Return or Enter key. Example:
To remove the IP address, enter:
SETDefault !0 -IP NETaddr = 0.0.0.0
This guide always gives the full form of a command in uppercase and
lowercase letters. However, you can abbreviate commands by entering
only the uppercase letters and the appropriate value. Commands are
not case-sensitive.

Screen displays

This typeface represents information as it appears on the screen.

The words “enter”
and “type”

When you see the word “enter” in this guide, you must type
something, and then press the Return or Enter key. Do not press the
Return or Enter key when an instruction simply says “type.”

[Key] names

Key names appear in text in one of two ways:
■

■

Referred to by their labels, such as “the Return key” or “the Escape
key”
Written with brackets, such as [Return] or [Esc].

If you must press two or more keys simultaneously, the key names are
linked with a plus sign (+). Example:
Press [Ctrl]+[Alt]+[Del].

Year 2000 Compliance

Menu commands
and buttons

Menu commands or button names appear in italics. Example:

Words in italicized
type

Italics emphasize a point or denote new terms at the place where they
are defined in the text.

From the Help menu, select Contents.

For information on Year 2000 compliance and 3Com products, visit the
3Com Year 2000 Web page:
http://www.3com.com/products/yr2000.html

OVERVIEW

This chapter provides an overview of the upgrade tools, process, and support
limitations.

Upgrade Tools and
Process
Definition of network
management station

The upgrade procedures in this guide use the Enterprise OS Upgrade Management
Utilities on a UNIX or Windows network management station (NMS).
An NMS is a UNIX or Windows system that has a TFTP/FTP server running in
addition to software, such as the Enterprise OS Upgrade Management Utilities, to
manage your network. For Windows, the utilities include the 3Com® TFTP/FTP
server.
If you are upgrading multiple bridge/routers, you can install and use the Network
Admin Tools utilities in the Transcend® Enterprise Manager or Transcend Network
Control Services, available separately. See the Transcend user guide for more
information.
You can use the NETBuilder Upgrade Link application that comes with the utilities
provides an easy to use graphical user interface (GUI) to upgrade one or more
bridge/routers. Or you can access the utilities directly using the command-line.
When upgrading multiple bridge/routers simultaneously using command line
utilities, the topology of the network should be considered and the bridge/routers
should be upgraded in a sequence that will not disrupt the network.
If you are performing an image-only upgrade, you can use the utilities or
applications, or you can copy the software manually using the Enterprise OS user
interface.
The utilities are shipped with your software package on a CD-ROM and must be
installed on an NMS on the same network as the bridge/router. You can also
download the utilities from the 3Com web, FTP, or BBS sites.
The utilities run on the following operating systems:
■

Solaris 2.x

■

HP-UX 10.x

■

IBM AIX 4.x or later

■

Windows NT 4.x

■

Windows 95/98

CHAPTER 1: OVERVIEW

Figure 1 shows the typical upgrade process.
Figure 1 Upgrade Process
Begin

Install software
and utilities
on NMS*
Restore old
software
version

If hardware
upgrade, reinstall
old hardware

Accept
upgrade?
No
?
Reject
Yes

Back up config
and boot files
from bridge/router
to NMS

Verify
upgrade

Do final cleanup

Done!

How the Utilities Work

Is hardware
upgrade
required?
Yes
Update
?
config files
No

Reboot bridge/router,
test software images
and config files

Copy config
and boot files
to bridge/router

Perform
hardware
upgrade
Reset IP
config and
SNMP

*NMS = network management station

The software on your bridge/router or switch consists of a bootable image file and
configuration files that store all your settings. The Enterprise OS Upgrade
Management Utilities update all your software files after copying them to a UNIX
or Windows NMS. Because the upgrade occurs on a copy of the files on the NMS,
the bridge/router remains operational during the upgrade. The utilities then copy
the new image and updated files back to the bridge/router.
Primary, Secondary, and Test Boot Sources
The NETBuilder bridge/router or PathBuilder switch boots from a default directory,
called the primary boot source, which can be set using the SysconF command in
the Enterprise OS user interface. If you have more than one set of boot images,
you can specify a backup directory, called the secondary boot source. There is also
a test boot source, which the utilities use to test a new upgrade before making it
the primary boot source. Because the boot sources are only pointers to particular
directories, the utilities can dynamically change the boot sources without having
to move any files.
Automatic or Manual Recovery
If your switch or bridge/router has enough flash memory, you can have both sets
of software: the old version and the new version. After a successful test boot with
the new software, the primary boot source is changed to the new version. If the
test boot is not successful, the system automatically reboots with the old version.
Dual-image support is described in the procedures for automatic recovery.
If you have only enough flash memory for the new version, you can still recover
the old version from the NMS using the utilities. Single-image support is described
in the procedures for manual recovery.
For memory requirements for automatic or manual recovery, see Chapter 3.

Rules and Support Limitations

Rules and Support
Limitations

Take Time to Plan

Before planning your upgrade, refer to the following rules and support limitations:
■

The utilities do not support Remote Boot and Configuration Services (RBCS) or
network booting.

■

Upgrades from NETBuilder bridge/routers running version 7.x, or earlier, are not
supported.

■

You cannot upgrade to a different platform. For example, you can only
upgrade an OfficeConnect® bridge/router to an OfficeConnect bridge/router.
You cannot upgrade a SuperStack® II NETBuilder bridge/router to a
SuperStack II NETBuilder SI bridge/router. The only exception is an upgrade
from a NETBuilder II® CEC module to a DPE module.

Because networks today have become increasingly complex, upgrading your
network requires a systematic approach. 3Com recommends that you plan your
upgrade carefully before implementing it. See Chapter 3 to plan your upgrade.

CHAPTER 1: OVERVIEW

INSTALLING THE UTILITIES ON A
NETWORK MANAGEMENT STATION

Before you start the upgrade process, you must install the Enterprise OS Upgrade
Management Utilities on a network management station (NMS). If you are using
Transcend Enterprise Manager or Transcend Network Control Services, which has
the utilities bundled, you should install the latest utilities to take advantage of new
features and version support.
This chapter describes how to install the Enterprise OS Upgrade Management
Utilities on the following platforms:

Installing the Utilities
on a Windows System

■

Solaris 2.x

■

HP-UX 10.x

■

IBM AIX 4.x or later

■

Windows NT 4.x

■

Windows 95/98

You can install the utilities from a CD-ROM or from utilities that you have
downloaded to your hard disk. To install the utilities on a Windows system, follow
these steps:
1 If you have installed utilities before or have Transcend, check the version by
entering:
bcmdiagnose

If the version is earlier than 11.3, continue to the next step. If you already have
11.3, you do not need to reinstall the utilities.
2 Change to the utilities directory.
■

If you are using the CD-ROM:

a Insert the CD-ROM into the CD-ROM drive.
b Open a command window.
c Change to the CD-ROM directory.
For example, if E is the drive letter for the CD-ROM, enter:
E:

3 If you download the utilities to your hard disk (see Chapter 8 for information
about downloading the utilities):
a Decompress the utilities.
b Open a command window.
c Change to the utilities directory using:
:\\

CHAPTER 2: INSTALLING THE UTILITIES ON A NETWORK MANAGEMENT STATION

4 Run the setup program for Windows:
■

To install all packages, including the utilities and package definitions for use
with Transcend if required, use:
bcmsetup : all

Where is the drive you want to install the utilities on.
The packages install in the default directory \usr\3Com\bcm\, and the following
paths are added to the autoexec.bat file:
:\usr\3com\bcm\bin\
:\usr\3com\common\bin\
5 Reboot your system to use the path, which is required for all utility commands. Or,
if you do not want to reboot, you can enter the path manually at the command
prompt:
:\usr\3com\common\data\profile

6 Use the bcmdiagnose utility to ensure that your installation is correct by entering:
bcmdiagnose

Installing the Utilities
on a UNIX System
Preparing for the
Installation

You can install the utilities from a CD-ROM or from utilities that you have
downloaded to your hard disk.
Before installing the utilities, verify the following items:
■

Your NMS is running one of the supported operating systems.
Check the operating system you are running by entering:
uname -a

The version message may refer to Solaris 2.5 as SunOS 5.5.
■

You need to upgrade utilities you have already installed. The utilities come
bundled with Transcend. To check the version, enter:
bcmdiagnose

Procedure

■

Your root password on the NMS (UNIX only).

■

Your NMS is running a TFTP/FTP server.

To install the utilities on a UNIX system, follow these steps:
1 Log on as root.
2 Change to the utilities directory.
■

If you are using the CD-ROM:

a Mount the CD-ROM.
For more information on mounting instructions for each supported UNIX
operating system, see Appendix C.
b Change to the appropriate directory on the CD-ROM for your operating system
using:
cd //

Where is the directory for your operating system:

Installing the Utilities on a UNIX System

Table 1 UNIX Directories
Operating System

Directory Name

Solaris 2.5.x

sunos5

HP-UX 10.x

HP_UX

IBM AIX 4.1.x, 4.2x

aix

■

If you download the utilities to your hard disk (see Chapter 8 for information
about downloading the utilities):

a Decompress the utilities.
b Change to the utilities directory on your hard disk using:
cd //

3 Run the setup program.
■

To install all packages from the CD-ROM, including the utilities and package
definitions for use with Transcend, enter:
./bcmsetup all

■

To install only the upgrade utilities, enter:
./bcmsetup bcm

The utilities are installed in the default directory /usr/3Com/bcm/.
If you are working in an HP-UX operating system, the bcmsetup command must
be uppercase, that is, BCMSETUP. The options that follow remain lowercase.
4 Complete the following step for your UNIX shell:
■

For a C-shell installation, add the contents of the following file to the .cshrc file
for each user you want to have access to the utilities, including root:
/usr/3Com/common/data/.login-bcm
Or you can enter the path after every logon:
source /usr/3Com/common/data/.login-bcm

■

For a Bourne shell installation, add the contents of the following file to the
.profile file for each user you want to have access to the utilities, including root:
/usr/3Com/common/data/.profile-bcm
Or you can enter the path after every logon:
. /usr/3Com/common/data/.profile-bcm

5 Return to normal privilege by entering:
exit

6 Use the bcmdiagnose utility to ensure that your installation is correct by entering:
bcmdiagnose

CHAPTER 2: INSTALLING THE UTILITIES ON A NETWORK MANAGEMENT STATION

Setting up for Auto
Startup

On a UNIX NMS, after you have completed the previous setup procedures you
need to set up the BootP server.
To set up the BootP server, enter:
bcmsteup -bootp

This command does not need to be used when you are operating on a
Windows 95/98/NT-based NMS.

PLANNING AND PREPARING THE
UPGRADE

This chapter describes setting up a file transfer method, choosing automatic or
manual recovery, checking the required memory for each package, including
instructions for checking the memory, and provides planning tables to copy and fill
out for each bridge/router.
If you are upgrading multiple bridge/routers using Transcend Enterprise Manager
or Transcend Network Control Services, or are using the command-line utilities,
you should make sure each bridge/router has enough flash memory and DRAM for
the software package you have chosen. The Upgrade Link application
automatically checks the memory of the bridge/router.
For a list of all software packages and the recommended upgrade path for your
version, see Appendix B.

Setting Up a File
Transfer Method
Setting up for TFTP File
Transfers

You can choose to transfer files using FTP or TFTP.

To use TFTP, you need to set up your NMS in preparation for TFTP file transfers.
Make sure your TFTP server is running. On a Windows workstation, 3Com’s
3CServer is shipped along with the utilities. Upgrade Link launches 3CServer
during start up.
Specify the -tftp flag in all command line utilities which use file transfers
(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use TFTP file transfer. For
example, to specify TFTP file transfer use:
bcmsysupgrade -s:from_nb -tftp

If neither flag is used, TFTP is used by default for software release 11.0 and lower,
but FTP is used by default for software release 11.1 and higher. If the -ftp flag is
specified on a bridge/router running software version 11.0 or lower, the FTP
password is overwritten with the following text string:
****

Setting up for FTP File
Transfers

To use FTP, you need to set up your NMS in preparation for FTP file transfers.
For Upgrade Link, the user name and password is specified in the Setting Page, as
shown on page 23.

CHAPTER 3: PLANNING AND PREPARING THE UPGRADE

On a UNIX NMS, follow these steps:
1 Create a user on your system with /tftpboot as the home directory.
2 When using the upgrade utilities via the command line or the Transcend Upgrade
Manager, specify this user name and password in the BCMFTPUSER and
BCMFTPPASS environment variables.
Specify the -ftp flag in all command line utilities that use file transfers
(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use FTP file transfer. For
example, to specify FTP file transfer use:
bcmsysupgrade -s:from_nb -ftp

If no flag is used, TFTP is used by default for software release 11.0 and lower, but
FTP is used by default for software release 11.1 and higher. If the -ftp flag is
specified on a bridge/router running software version 11.0 or lower, the FTP
password is overwritten with the following text string:
****

On a Windows NMS, follow these steps:
1 Create a user in 3Com’s 3CServer FTP settings.
2 When using the upgrade utilities via command line or the Transcend Upgrade
Manager, specify the ftp user name and password in the BCMFTPUSER and
BCMFTPPASS environment variables.
You can specify the -ftp flag in the utilities (bcmsysupgrade, bcmbackup,
bcmrestore) if you want to use FTP file transfer.
If no flag is used, TFTP is used by default for software release 11.0 and lower, but
FTP is used by default for software release 11.1 and higher. If the -ftp flag is
specified on a bridge/router running software version 11.0 or lower, the FTP
password is overwritten with the following text string:
****

Choosing Automatic
Recovery or Manual
Recovery

Automatic Recovery

If you have enough flash memory for dual-image support, complete your upgrade
using automatic recovery. If you have only enough memory for single-image
support, complete the upgrade using manual recovery. The following sections
describe the difference between automatic and manual recovery and the memory
requirements for each platform.
The default upgrade procedure uses automatic recovery. After backing up the
current software to the network management station (NMS), the new software is
copied into a test directory while the current software remains in the primary
directory. If you accept the upgrade after booting from the test directory, the new
software becomes the primary boot source, and the old software becomes the
secondary boot source.
If you are upgrading your hardware as well as the software, the procedure for
automatic recovery saves the software package that was originally on the new
hardware as the secondary boot source.

Manual Recovery

An upgrade with manual recovery (using the -m option with the bcmsysupgrade
utility) formats the flash memory after backing up the current software, then
copies the upgraded files to the bridge/router. If the upgrade is not successful, you
must restore the software from the NMS.
If you are upgrading your hardware as well as the software, you can easily recover
your old hardware if the upgrade is not successful. However, because you erased
the flash memory on the new hardware, you will need to restore the original
software from the NMS if you want to return the new hardware to its original
state.
Table 2 lists the memory requirements for each software package on the platform
you are upgrading to. If you are upgrading to an earlier version of software, see
the guides that came with that version for the memory requirements.

Table 2 Version 11.2 Software Packages
Flash Memory Required for:
Software Package

Model

DRAM Required

NETBuilder II with DPE:

Automatic Recovery Manual Recovery
(The standard flash memory card from 3Com
is 20 MB)

(AC) - APPN/Connection Services

DPE

(DW) - Multiprotocol Router

DPE

(DE) - Multiprotocol Router with
56-bit Encryption

DPE

(DS) - Multiprotocol Router with
128-bit Encryption

DPE

All DPE modules
40 MB
ship with enough
40 MB
DRAM for all
software packages.

20 MB

All DPE modules
ship with enough
DRAM.

40 MB

20 MB

40 MB

20 MB

8 MB

4 MB

20 MB

SuperStack II NETBuilder Token Ring:
(TE) - Multiprotocol Router with
Encryption

327, 527

12 MB

(NW) - IP/IPX/AT Router

432, 442, 452, 462
532, 542, 552, 562

All SuperStack II NETBuilder SI bridge/routers ship with enough
DRAM (16 MB) and flash memory (8 MB) for automatic recovery.

(BF) - Boundary Router

433, 443, 453, 463
533, 543, 553, 563

(CF) - Multiprotocol Router

437, 447, 457, 467
537, 547, 557, 567

(AX) - APPN/Connection Services

438, 448, 458, 468
538, 548, 558, 568

(NE) - IP/IPX/AT Router with 56-bit
Encryption

432, 442, 452, 462
532, 542, 552, 562

(NS) - IP/IPX/AT Router with 128-bit
Encryption

432, 442, 452, 462
532, 542, 552, 562

(CE) - Multiprotocol Router with
56-bit Encryption

437, 447, 457, 467
537, 547, 557, 567

(CS) Multiprotocol Router with
128-bit Encryption

437, 447, 457, 467
537, 547, 557, 567

SuperStack II NETBuilder SI:

CHAPTER 3: PLANNING AND PREPARING THE UPGRADE

Table 2 Version 11.2 Software Packages (continued)
Flash Memory Required for:
Software Package

Model

DRAM Required

Automatic Recovery Manual Recovery

(FD) - FRAD

120

8 MB

4 MB

(NW) - IP/IPX/AT Router

112, 122, 132, 142

8 MB

4 MB

4 MB for 132

OfficeConnect NETBuilder:

2 MB for all others
(BF) - Boundary Router

113, 123, 143

8 MB

4 MB

(OF) - Multiprotocol Router

117, 127, 137, 147

12 MB

8 MB

4 MB

(AF) - APPN

116, 126, 146

12 MB

8 MB

4 MB

(NE) - IP/IPX/AT Router with 56-bit
Encryption

112, 122, 132, 142

8 MB

4 MB

4 MB for 132

(NS) - IP/IPX/AT Router with 128-bit
Encryption

112, 122, 132, 142

(VE) - VPN IP/IPX/AT Router with
Quick Step VPN and 56-bit
Encryption

115, 125, 135, 145

8 MB

4 MB

(OE) - Multiprotocol Router with
56-bit Encryption

117, 127, 137, 147

12 MB

8 MB

4 MB

(OS) - Multiprotocol Router with
128-bit Encryption

117, 127, 137, 147

12 MB

8 MB

4 MB

(VW)- Multiprotocol Rou;r

147

12 MB

8 MB

4MB

(PW) - Multiprotocol Router

S500, S580, S593,
S594

160 MB

16 MB

4 MB

(PE) - Multiprotocol Router with
56-bit Encryption

S500, S580, S593,
S594

160 MB

16 MB

4 MB

(PS) - Multiprotocol Router with
128-bit Encryption

S500, S580, S593,
S594

160 MB

16 MB

4 MB

2 MB for all others
8 MB

4 MB

4 MB for 132
2 MB for all others

PathBuilder S5xx Switch

Checking DRAM

To check how much DRAM you have installed on the switch or bridge/router, on
the NMS use:
bcmuname -M

Where is the IP address or hostname of the switch or bridge/router.
Checking Flash Memory

To check how much flash memory you have installed on the switch or
bridge/router, on the NMS use:
bcmdf [:]

Where is the hostname or the IP address of the switch or bridge/router.
Specify drive A for NETBuilder II bridge/routers or PathBuilder switches.
Do not specify a drive for SuperStack II or OfficeConnect bridge/routers.

Checking the Software Version

Checking the
Software Version

To display the current software version and package you are running, use the
bcmuname utility on the NMS:
bcmuname -R

Where is the IP address or hostname of the bridge/router.
To display the current software version and package using the Enterprise OS user
interface, enter:
SHow -SYS VERSion

Planning Tables

Photocopy the following planning tables, and fill out background information
about your bridge/routers before starting the upgrade process. The NETBuilder II
table is on page 22. The SuperStack II NETBuilder, SuperStack II NETBuilder SI,
OfficeConnect NETBuilder, and PathBuilder switch table is on page 23.
If you are upgrading both software and hardware, write down the information for
the new hardware. For example, if you are replacing a CEC 20 with a DPE module,
write down the information for the DPE module.

Flash
Memory

NETBuilder II Planning Table

IP Address or Name

Enough Flash Memory for
Automatic Recovery?

Current Software Version
and Two-Letter Code

Planning Tables

Check each appropriate option to use with the command-line utilities:

Manual Recovery?

Hardware Upgrade?

-V:

❑

-k:

Upgrading to a Software Upgrading Unlike
Version Other than 11.0? Packages?

11.1 CF ❑ -m ❑ -new_hw ❑

New Software Version
and Two-Letter Code

n/a 11.0 CF

CEC Only: Firmware Version
(pre-10.3 upgrade only)

10.1.3.24

20
MB

Enough Flash Memory for
Manual Recovery?

❑ -m ❑ -new_hw ❑
❑ -m ❑ -new_hw ❑
❑ -m ❑ -new_hw ❑
❑ -m ❑ -new_hw ❑
❑ -m ❑ -new_hw ❑
❑ -m ❑ -new_hw ❑
❑ -m ❑ -new_hw ❑
❑ -m ❑ -new_hw ❑
❑ -m ❑ -new_hw ❑

IP Address or Name

8 MB

Flash
Memory

Enough Flash Memory for
Automatic Recovery?

DRAM

Current Software Version
and Two-Letter Code
New Software Version
and Two-Letter Code

❑ -m ❑ -new_hw ❑

Planning Tables

-V:

❑

-k:

Manual Recovery?

Upgrading to a Software Upgrading Unlike
Version Other than 11.0? Packages?

11.0 BF

Hardware Upgrade?

8 9.3 BF
MB

Check each appropriate option to use with the command-line utilities:

SuperStack II NETBuilder, SuperStack II NETBuilder SI, and OfficeConnect NETBuilder Planning Table

10.1.3.24

Enough Flash Memory for
Manual Recovery?

CHAPTER 3: PLANNING AND PREPARING THE UPGRADE

UPGRADING USING THE NETBUILDER
UPGRADE LINK APPLICATION

This chapter describes how to upgrade the software on a NETBuilder bridge/router
or a PathBuilder switch using the Upgrade Link application. Upgrade Link is an
easy to use GUI for the upgrade utilities that runs in a web server. Access to the
server is available via a web browser. If you are upgrading multiple bridge/routers,
you should use Transcend Enterprise Manager or Transcend Network Control
Services instead. Contact your network supplier for more information about
Transcend. Or if you want to write scripts, you can use the command-line utilities
as described in Chapter 5. Use the command-line utilities if you do not have a web
browser on your network management station (NMS).
An NMS is a UNIX or Windows system that has a FTP/TFTP server running in
addition to software, such as the Upgrade Management Utilities, to manage your
network. For Windows, the utilities include the 3Com FTP/TFTP server called
3CServer.

Preparing for the
Upgrade

Before upgrading your system, confirm the following items:
■

You have installed the utilities according to Chapter 2.

■

You have set the path for the utilities (UNIX only). If you have not set the path,
complete the following step for your UNIX shell:
■

For a C-shell installation, add the contents of the following file to the .cshrc
file for each user you want to have access to the utilities, including root:
/usr/3Com/common/data/.login-bcm
Or you can enter the path after every logon:
source /usr/3Com/common/data/.login-bcm

■

For a Bourne shell installation, add the contents of the following file to the
.profile file for each user you want to have access to the utilities, including
root:
/usr/3Com/common/data/.profile-bcm
Or you can enter the path after every logon:
. /usr/3Com/common/data/.profile-bcm

■

All configuration files are in the same directory as the boot image.

■

You have booted your bridge/router from the primary boot source.

■

You have a web browser installed with Java support, such as Netscape
Navigator 4.5 or Internet Explorer 4.x, and you have it in your path (UNIX).

CAUTION: Only one client at a time should access the Upgrade Link Server.
■

There is sufficient disk space on the NMS for the amount of software you are
installing.

CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION

Minimal disk storage requirements depend on the number of different
software versions that are stored on the disk drive. Calculate:
■

■

6 MB for each version of the NETBuilder II bridge/router or PathBuilder
switch image
4 MB for each version of the SuperStack II, SuperStack II SI, or
OfficeConnect NETBuilder bridge/router image

While you must purchase one copy of software for each device, you only need
to install one copy of a version of software on the NMS.

Running Upgrade Link
Locally

Upgrade Link contains its own web server. Client access to the web server is
available locally or remotely via a web browser. Running the Upgrade Link
application locally means that the web browser and the web server are running on
the same NMS.
To run Upgrade Link locally on a UNIX NMS, use:
UpgradeLink [-NoAuthentication] [-NoSecurity]

This command starts the NETBuilder Upgrade Server and the default browser. Two
command options are available.
■

When NoAuthentication is specified, Upgrade Link will allow a remote client to
access the server without user authentication, see “Settings Page” for a
description of the available settings.

■

When you specify NoSecurity, Upgrade Link starts and will accept connections
from all IP addresses. Otherwise, only those client IP addresses listed in the
/usr/3Com/common/data/allow file will be accepted by Upgrade Link.

For security, an administrator can enter the IP addresses of only those clients who
will be allowed to upgrade devices. An allow file is an ASCII text file containing the
IP addresses of clients to upgrade devices. The allow file looks like the following:
129.213.100.151
129.213.100.152
139.87.172.100

To run Upgrade Link locally on a Windows NMS, click the Start menu, then choose
Programs⇒ Remote Upgrade Utilities⇒Upgrade Link.
Your default browser is launched. On Windows, the 3Com FTP/TFTP server is also
launched.
When you exit Upgrade Link, you will also exit the browser and, for Windows, the
FTP/TFTP server.

Running Upgrade Link
Remotely

You can access the NETBuilder Upgrade Server remotely using a browser.
■

Start the NETBuilder Upgrade Server on the NMS using:
bcmnbrus [-NoSecurity | -NoAuthentication]

Status and Settings Pages

where port is the TCP socket on which the client can communicate with the
server. On UNIX systems, you can add this command to cron. On Windows
95/98/NT systems, this command can be run as a console application.
When NoSecurity is specified, the bcmnbrus command allows connections from all
IP addresses. Otherwise, only those client IP addresses listed in
the/usr/3Com/common/data/allow file will be accepted by Upgrade Link.
For security, an administrator can enter the IP addresses of only those clients who
will be allowed to upgrade devices. An allow file is an ASCII text file containing the
IP addresses of clients to upgrade devices. The allowed file looks like the following:
129.213.100.151
129.213.100.152
139.87.172.100

When NoAuthentication is specified, the bcmnbrus command allows the remote
client to access the server without user authentication, see “Settings Page” on
page 28 for a description of the available settings.
■

Then, to access Upgrade Link from a web browser, enter the following URL:
http://:/

Do not resize the browser window while the Upgrade Link application is running.
CAUTION: Only one client at a time should access the Upgrade Link Server.

Status and Settings
Pages

After each procedure described in this section, the Status or Settings page
appears. Table 3 describes the buttons on the bottom of the Status page.

Table 3 Status page Buttons
Button

Description

History

Shows the last 20 successful operations performed on the
bridge/router or switch.

Home

Returns to the Console page.

CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION

Table 3 Status page Buttons (continued)

Settings Page

Button

Description

Abort

Exits Upgrade Link and aborts the process. Some processes may need
to be completed even after clicking Abort. Upgrade Link displays a
message about any ongoing processes.

View Logs

Opens a page listing the logs available for viewing.

The Setting Page lets you establish basic settings.

■

You can choose the method of file transfers. TFTP is used by default for
NETBuilder bridge/router software release 11.0 and lower while FTP is used by
default for NETBuilder bridge/router software release 11.1 and higher and
Enterprise OS version 11.3.

■

Enter an SNMP read/write string and the NETBuilder bridge/router or
PathBuilder switch user name and password.

■

If -noAuthentication was not specified in Upgrade Link or on the bcmnbrus
command line, authentication will be used and you must enter the NETBuilder
or PathBuilder username and password.

■

If -noAuthentication was specified in Upgrade Link or on the bcmnbrus
command line, no authentication is required and any user name and password
entries are ignored.

■

If using FTP, enter the FTP client user name and password.

Verifying for Upgrading

Verifying for
Upgrading

Before upgrading, run the diagnostic utility in Upgrade Link to verify connectivity
to the switch or bridge/router by following these steps:
1 Choose a switch or bridge/router from the pop-up list in the Console page, or click
New to enter the IP address or hostname. The pop-up list contains devices that
you have upgraded or backed-up before.

2 Select Verify Upgrade Services (Diagnose) and click Apply.
The Settings Page appears. Select the appropriate settings as described in on
“Settings Page” on page 28 and click OK to close that window.
The Status page appears showing the results of the diagnostic tests.
3 If the Status page shows a failure, check the SNMP read/write community string
and FTP/TFTP server settings.
If the Status page shows a success, click Home to continue with the upgrade and
return to the Console page.

Installing Software on
the NMS

Upgrade Link installs the software on the NMS in the following directory:
Windows:
\%tftpboot%\image\\SW|FW\\
UNIX:
/tftpboot/image//SW|FW//
For UNIX, if there is not enough space on the disk, you can link /tftpboot to
another disk. For example, to link /tftpboot to the usr directory, enter:
ln -s /usr/tftpboot /tftpboot/

The utilities work only with the default directory names and structures.

CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION

Values

Procedure

tftpboot

For UNIX: Directory specified in inetd or tftpd for tftpd files.

%tftpboot%

For Windows (using the default 3Com TFTP server): Directory
specified in the 3Server configuration.

NETBuilder II with CEC Module:

NBII

NETBuilder II with DPE Module:

NBDPE

SuperStack II NETBuilder SI bridge/router:

NBSI

SuperStack II NETBuilder Ethernet
bridge/router:

NBRO

SuperStack II NETBuilder Token Ring
bridge/router:

NBR2T

SuperStack II NETBuilder Ethernet/ISDN
bridge/router:

NBRI

SuperStack II NETBuilder Token Ring/ISDN
bridge/router:

NBR2TI

OfficeConnect NETBuilder bridge/router:

NBOCF

PathBuilder S5xx switch:

NBPB500

Two letter designator shown on the CD-ROM label.

[SW | FW]

The software or firmware directory.

Software version 9.0 through 11.3.

To install the new software on the NMS, follow these steps:
You must be logged in as root for this procedure (UNIX).
1 You can install the software from a CD-ROM, a tar archive, or a boot image
(image-only upgrade). If you are installing from a CD-ROM, mount the CD-ROM
on the NMS.
See Appendix C for information on how to mount the CD-ROM on a UNIX system.
2 For UNIX, log in as root.
3 Run Upgrade Link if you have not already done so.
4 Select Install a SW Package on NMS from the Console page.

Upgrading Software

5 Click Apply.
The Install page appears.

6 Enter the path for the software, or click Browse to use a file browse page.
■

For UNIX CD-ROM, use the following path:
cdrom//image/

■

For Windows CD-ROM, use the following path:
:\image\

■

For Archive, enter the entire path including the filename.

■

For an FTP site, enter the full URL

7 Click Apply to install the software.
The Status page appears while the software is installing.
8 Select a package from the list that you want to uninstall. Click Delete to begin
uninstalling the package. Confirm you selection when prompted.
9 When the installation is complete, click Home to continue with the upgrade.

Upgrading Software

To upgrade the software, follow these steps:
1 Run Upgrade Link if you have not already done so.
2 Choose a bridge/router from the pop-up list in the Console page, or click New to
enter the IP address or hostname. The pop-up list contains bridge/routers and
switches that you have upgraded or backed-up previously.
3 Select Upgrade and click Apply.
The Settings Page appears. Select the appropriate settings as described in
“Settings Page” on page 28 and click OK to close the window.
The Upgrade page appears.

CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION

4 Select a software package from the pop-up list. The list includes all packages you
have installed on the NMS for your platform. If your package is not listed, install
the software by clicking New and see “Installing Software on the NMS” on
page 29.
CAUTION: When upgrading to a package containing encryption, you will be
presented with an export restriction message. To upgrade to an encrypted
package, you must acknowledge this restriction notice, otherwise the upgrade will
not continue.
The Upgrade page shows information about your system, including the flash
memory requirements for a manual or automatic recovery upgrade.
5 Click Next.

6 The recommended upgrade method is selected based on the amount of memory
you have installed. If you do not wish to perform a customized upgrade, go to
step 12.
CAUTION: If you override the Upgrade Link selection, your upgrade may fail.
7 Click on the Advanced button if you want to customize the upgrade process, that
is, you do not want to perform all of the upgrade stages at this time.
The Advanced page appears.

Upgrading Software

8 Click the check box for each of the stages you want to complete in the current
operation.
9 Click New Hardware if you are replacing your bridge/router with a new system.
For example, click New Hardware if you are replacing the CEC module with a DPE
module.
You cannot upgrade to a different platform. For example, you can only upgrade
an OfficeConnect bridge/router to an OfficeConnect bridge/router. You cannot
upgrade a SuperStack II NETBuilder bridge/router to a SuperStack II NETBuilder SI
bridge/router. The only exception is an upgrade from a NETBuilder II CEC module
to a DPE module.
10 If you want to alter the Reboot Timeout, enter a new number in the box. The
default setting is appropriate for most networks.
11 Click OK.
12 Click Apply to begin the upgrade.
The Status page appears.
13 If you are performing a hardware upgrade, replacing a CEC module with a DPE
module for example, a message to replace the hardware appears after the
software has been backed up to the NMS. Replace the hardware at this time.
14 When the upgrade is complete, the bridge/router reboots from the new software.
If the boot is not successful:
■

For automatic recovery, the bridge/router reboots from the original software
after the reboot timeout (default = 10 minutes).

■

For manual recovery, you must configure the bridge/router at the local
console to reestablish IP connectivity. Once connectivity is established, you can
restore the software to return the bridge/router to a preupgrade state. See
Chapter 7 for the procedure to restore connectivity and the software.

15 Click Home then Exit on the Console page to exit Upgrade Link.

CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION

UPGRADING A BRIDGE/ROUTER USING
THE COMMAND-LINE UTILITIES

This chapter describes how to upgrade the software on a bridge/router or switch
using the command-line Upgrade Management Utilities. 3Com recommends
using the Upgrade Link application described in Chapter 4, but you can use the
command-line utilities instead if you want to write scripts or if you do not have a
web browser on your NMS. Use Transcend Enterprise Manager or Transcend
Network Control Services to upgrade multiple bridge/routers.
You can perform the following types of upgrades:
■

■

Preparing for the
Upgrade

Upgrading Software Only
■

Automatic Recovery

■

Manual Recovery

Upgrading Hardware and Software
■

Automatic Recovery

■

Manual Recovery

Before upgrading your system, confirm the following items:
■

You have installed the utilities according to Chapter 2.

■

You have set the path for the utilities (UNIX only). If you have not set the path,
complete the following step for your UNIX shell:
■

For a C-shell installation, add the contents of the following file to the .cshrc
file for each user you want to have access to the utilities, including root:
/usr/3Com/common/data/.login-bcm
Or you can enter the path after every logon:
source /usr/3Com/common/data/.login-bcm

■

For a Bourne shell installation, add the contents of the following file to the
.profile file for each user you want to have access to the utilities, including
root:
/usr/3Com/common/data/.profile-bcm
Or you can enter the path after every logon:
. /usr/3Com/common/data/.profile-bcm

■

All configuration files are in the same directory as the boot image.

■

You have booted your bridge/router from the primary boot source.

■

There is sufficient disk space on the NMS for the amount of software you are
installing.

CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES

Minimal disk storage requirements depend on the number of different
software versions that are stored on the disk drive. Calculate:
■

6 MB for each version of the NETBuilder II bridge/router image

■

6 MB for each version of the PathBuilder S5xx switch image

■

4 MB for each version of the SuperStack II, SuperStack II SI, or
OfficeConnect bridge/router image

While you must purchase one copy of software for each bridge/router or
switch, you only need to install one copy of a version of software on the NMS.

Setting Up a File
Transfer Method

You can choose to transfer files using FTP or TFTP.
Setting up for TFTP File Transfers
To use TFTP, you need to set up your NMS in preparation for TFTP file transfers.
Make sure your TFTP server is running. On a Windows workstation 3Com’s
3CServer is shipped along with the utilities. Upgrade Link launches 3CServer
during start up.
Specify the -tftp flag in all command line utilities which use file transfers
(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use TFTP file transfer. For
example, to specify TFTP file transfer use:
bcmsysupgrade -s:from_nb -tftp

If neither flag is used, TFTP is used by default for software release 11.0 and lower,
but FTP is used by default for software release 11.1 and higher. If the -ftp flag is
specified on a NETBuilder bridge/router running software version 11.0 or lower,
the FTP password is overwritten with the following text string:
****

Setting up for FTP File Transfers
To use FTP, you need to set up your NMS in preparation for FTP file transfers.
For Upgrade Link, the user name and password is specified in the Setting Page, as
shown on page 23.
On a UNIX NMS, follow these steps:
1 Create a user on your system with /tftpboot as the home directory.
2 When using the upgrade utilities via the command line or the Transcend Upgrade
Manager, specify this user name and password in the BCMFTPUSER and
BCMFTPPASS environment variables.
Specify the -ftp flag in all command line utilities that use file transfers
(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use FTP file transfer. For
example, to specify FTP file transfer use:
bcmsysupgrade -s:from_nb -ftp

Prediagnosing System Problems

Prediagnosing System
Problems

Before you begin your upgrade, 3Com recommends that you run the
bcmdiagnose utility specifying the file transfer utility, FTP, or TFTP and the IP
address or hostname of the bridge/router you are upgrading.
Before using the bcmdiagnose utility, you should set the BCMFTPUSER and
BCMFTPPASS environment variables. When using FTP, an error message is
generated and the file transfer is aborted if these variables are not set.
The bcmdiagnose utility helps detect any problems with SNMP, FTP or TFTP
connectivity.
To run the bcmdiagnose utility on your NMS, use:
bcmdiagnose [ -ftp | -tftp ] [ | -h]

Where is the IP address or hostname of the bridge/router you are
upgrading. The -ftp and -tftp flags force the specified file transfer types. See
Appendix A for more information about any error messages that may appear.

Installing the
Software on the NMS

To install the NETBuilder software, follow these steps:
1 For UNIX, login as root.
2 If you are using a CD-ROM, insert the CD-ROM into the CD-ROM drive on the
NMS.
a Mount the CD-ROM (UNIX only).
See Appendix C for information on how to mount the CD-ROM.
3 Make sure you are using version 11.3 of the Enterprise OS Upgrade Management
Utilities.

CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES

To check which version you have installed, enter:
bcmdiagnose -h

The version of the installed utilities is displayed in the following message:
bcmdiagnose version 11.3. Copyright 3Com Corporation 1999

If the version of the utilities you have installed is not version 11.3, you must first
install the 11.3 utilities according to Chapter 2.
4 Install the software.
■

From a CD-ROM:
For UNIX, enter:
bcminstall

The path option may be used to install the utilities on an NMS that has two
or more CD-ROM drives or to install from a remote CD-ROM drive. You
must explicitly specify the second or remote CD-ROM drive using:
bcminstall -cdrom []

For example, to install software from a second CD-ROM drive on a Solaris
machine, enter:
bcminstall -cdrom /cdrom/cdrom1/image

After the installation is complete, the screen shows an inventory of all
bridge/router packages installed, including previous versions you have
installed.
For Windows, open a command window and use:
bcminstall -cdrom :\image
■

From a Tarred File, use:
bcminstall -tar /

■

From an Image File, use:
bcminstall -image /

The image file is the NETBuilder bridge/routers boot file, for example, boot.29K or
boot.68k.
Software Directories

The bcminstall utility installs the software on the NMS in the following directory:
Windows:
\%tftpboot%\image\\SW|FW\\
UNIX:
/tftpboot/image//SW|FW//
For UNIX, if there is not enough space on the disk, you can link /tftpboot to
another disk. For example, to link /tftpboot to the usr directory enter:
ln -s /usr/tftpboot /tftpboot

The utilities work only with the default directory names and structures.

Using the Bcmsysupgrade Utility to Upgrade

Values

tftpboot

For UNIX: Directory specified in inetd or tftpd for tftpd files.

%tftpboot%

For Windows (using the default 3Com TFTP server): Directory
specified in the Win.ini file in the “[3Com.nm] TFTPROOT=”
section. The Win.ini file is located in the default Windows
directory, for example C:\windows or C:\winnt4.

NETBuilder II with CEC Module:

NBII

NETBuilder II with DPE Module:

NBDPE

SuperStack II NETBuilder SI bridge/router:

NBSI

SuperStack II NETBuilder Ethernet
bridge/router:

NBRO

SuperStack II NETBuilder Token Ring
bridge/router:

NBR2T

SuperStack II NETBuilder Ethernet/ISDN
bridge/router:

NBRI

SuperStack II NETBuilder Token Ring/ISDN
bridge/router:

NBR2TI

OfficeConnect NETBuilder bridge/router:

NBOCF

PathBuilder S5xx Switch:

NBPB500

Two letter designator shown on the CD-ROM label.

[SW | FW]

The software or firmware directory.

Software version 9.0 through 11.3.

Use the bcmuname utility to display your current platform, package, and version.

Using the
Bcmsysupgrade Utility
to Upgrade

This section describes how to use the bcmsysupgrade utility for the most common
software upgrades.
The command syntax for the bcmsysupgrade utility is:
bcmsysupgrade [options]

See “bcmsysupgrade” on page 81 for more information.
The procedures described in the following sections assume you are performing a
like-package upgrade to version 11.3 with automatic recovery (see “Choosing
Automatic Recovery or Manual Recovery” on page 18 for more information).
An example of a like-package upgrade is from the CF package to the CF package.
A like-package upgrade is an upgrade where the software package in the version
you are upgrading from and the version you are upgrading to have the same
two-letter designator.
If your upgrade is not a like-package upgrade with automatic recovery, or you are
upgrading to a version other than the default, you must use the bcmsysupgrade
utility with other options. Be sure to use the same options during each stage of
the upgrade process. See Table 4 for a description of the options.

CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES

For UNIX, after you have upgraded, check the /tftpboot/CLIENTS//tmp/stages.log file to ensure that the options were used
consistently throughout the upgrade process.
For Windows, after you have upgraded, check the \%tftpboot%\CLIENTS\\tmp\stages.log file to ensure that the options were used
consistently throughout the upgrade process.
Table 4 lists the most common bcmsysupgrade options.
Table 4 Common Options for Bcmsysupgrade
Task

Option

Image-only upgrade
or
Upgrading to a software version other than 11.1

-V:

Upgrading unlike packages

-k:

Upgrading with Manual Recovery

-m

Specifying encryption license agreement.

-EncryptionLicenseRead

Using TFTP file transfer.

-tftp

Using FTP file transfer.

-ftp

Whenever you specify an option with bcmsysupgrade, you must repeat that
option for all steps in the procedure.
Example

To upgrade a bridge/router from the SW/NBII-WA,8.3 package to the SW/NBII-FF,
10.1005 package (unlike packages, manual recovery, and a different package
from 11.0), use:
bcmsysupgrade -s:from_nb -k:FF -V:101005 -m

The same options must be used to upgrade configuration files:
bcmsysupgrade -s:update -k:FF -V:101005 -m

See Chapter 8 for more information about how to use bcmsysupgrade for
specialized cases.

Filenames

The following sections list the files that may be used when you upgrade a
NETBuilder system.
NETBuilder II Bridge/Router
■

boot.29k — image file that boots the main processor module.

■

mp6e.29k — image file that boots the MP 6-port Ethernet module.

■

mpatm.29k — image file that boots the MP ATMLink module.

■

mbri.68k — image file that boots the HSS 8-Port BRI module.

■

4portwan.860 — image file that boots the HSS 4-Port WAN module.

■

iofw_upd.29k — file that updates the firmware for HSS 3-port, HSS 4-port,
HSS 8-port, and MP modules.

■

sys — file that is used during the upgrade process to determine the source OT
target software version.

Upgrading Software Only

■

ccsmacro — file that contains predefined user macros.

■

fpupdate.29k (CEC Only) — file that updates the CEC module firmware.

You may also have several configuration files that will be upgraded by the utilities.
SuperStack II NETBuilder and OfficeConnect NETBuilder Bridge/Routers
■
■

boot.68k — image file that boots the system.
sys — file that may be used during the upgrade process to determine the
source or target software version.

You may also have several configuration files that will be upgraded by the utilities.
PathBuilder S5xx Series Switch
■
■

Upgrading Software
Only

Automatic Recovery

boot.ppc — image file that boots the system.
sys — file that may be used during the upgrade process to determine the
source or target software version.

This section describes how to upgrade the software on your existing hardware
using either automatic or manual recovery. If you are upgrading or replacing your
bridge/router, switch or main processor module (NETBuilder II), follow the
procedure in “Upgrading Hardware and Software” on page 44.
This section describes how to perform an upgrade of the Enterprise OS software
that does not include a hardware upgrade. See Chapter 3 for the memory
requirements for automatic recovery.
Whenever you specify an option with bcmsysupgrade, 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 software to the default version, follow these steps:
1 Back up your current software to the NMS using:
bcmsysupgrade [options] -s:from_nb

CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES

CAUTION: If you are running any other firmware version besides 2.0 or 2.1, you
should upgrade the firmware after upgrading the software.
To upgrade the CEC firmware, follow these steps:
a Make sure there is a floppy diskette with write access in the floppy drive on the
bridge/router. The diskette is formatted during the upgrade, so 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.
b Upgrade your firmware to version 2.6 using:
bcmsysupgrade -s:upgrade_cec_fw -V:

After the firmware has been upgraded, the bridge/router reboots.
3 Update your configuration files using:
bcmsysupgrade -s:update

4 Copy the upgraded software to the bridge/router using:
bcmsysupgrade -s:to_nb

5 Test your new software using:
bcmsysupgrade -s:test_boot

The bridge/router is rebooted, and the utilities confirm IP connectivity and that the
expected version of software is running.
6 Verify that your upgrade completed successfully.
To verify that the software is working properly, you can perform a set of
operational integrity checks on the newly upgraded device. These may include:
■

Some standard checks based on services active.
A basic service verification test can Ping to specific IP addresses.

■

Connectivity checks based on network topology.
Examples of a connectivity verification include:
■

■

Checking the connectivity between devices on different networks, through
designated bridge/routers.

■

Testing typical device connections on terminals, printers, or hosts.

■

Testing the connectivity with specific bridge/routers.

Custom checks based on applications and typical network use.
For instance, you can check normal operation over the network and perform
file transfers, as well as run traces on specific routes or check routing tables.

7 Accept or reject the upgrade.
■

If your upgrade completed successfully, accept your upgrade using:
bcmsysupgrade -s:accept

■

If the upgrade process failed to meet your verification criteria, reject your
upgrade using:
bcmsysupgrade -s:reject

The bridge/router is rebooted using the previous version of software.

Upgrading Software Only

8 NETBuilder 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.
b Upgrade your firmware to version 2.6 using:
bcmsysupgrade -s:upgrade_cec_fw -V:

After the firmware has been upgraded, the bridge/router reboots.
9 NETBuilder 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

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:
1 Back up your current software to the NMS using:
bcmsysupgrade [-options] -s:from_nb -m

3 Copy the upgraded software to the bridge/router using:
bcmsysupgrade -s:to_nb -m

4 Accept your upgrade using:
bcmsysupgrade -s:accept -m

CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES

The device reboots.
5 Verify that your upgrade completed successfully.
To verify that the software is working properly, you can perform a set of
operational integrity checks on the newly upgraded device. These may include:
■

Some standard checks based on services active.
A basic service verification test can Ping to specific IP addresses.

■

Connectivity checks based on network topology.
Examples of a connectivity verification include:
■

■

Checking the connectivity between devices on different networks, through
designated bridge/routers.

■

Testing typical device connections on terminals, printers, or hosts.

■

Testing the connectivity with specific NETBuilder bridge/router.

6 If you determine that the new software does not meet your requirements, you can
reject the upgrade and revert to the software version you were running before the
upgrade by using the bcmrestore utility.
To reject your upgrade, use:
bcmrestore

7 NETBuilder 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

The bridge/router reboots after the firmware is upgraded.
If the Bridge/Router or Switch Does Not Boot
If a failure causes the bridge/router or switch not to boot, or if the bridge/router or
switch is inaccessible using Telnet, you must configure the bridge/router at the
local console to reestablish IP connectivity. After connectivity is reestablished, you
can use the bcmrestore utility to return the bridge/router or switch to a
preupgrade state. See Chapter 7 for connectivity and recovery procedures.

Upgrading Hardware
and Software

Automatic Recovery

This section describes how to upgrade the software on a bridge/router on which
you are upgrading or replacing your bridge/router or switch or main processor
module (NETBuilder II) using either automatic or manual recovery. If you are
upgrading only the software, follow the procedure in “Upgrading Software Only”
on page 41.
This section describes how to perform a software and hardware upgrade with
automatic recovery. See Chapter 3 for the memory requirements for automatic
recovery.
Whenever you specify an option with bcmsysupgrade (such as -new_hw), you
must repeat that option for all steps in the procedure. See Table 4 on page 40 or

Upgrading Hardware and Software

“bcmsysupgrade” on page 81 for a list of the options available to use with the
bcmsysupgrade utility.
To upgrade the bridge/router software and hardware, follow these steps:
1 Back up your current software to the NMS using:
bcmsysupgrade [options] -s:from_nb -new_hw

where [-options] lets you specify the -EncryptionLicenseRead flag that indicates
you have read and understand the encryption license agreement notice and
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.
2 NETBuilder II with CEC only — (The CEC module is not supported in software
version 11.1. However, you can use the utilities to upgrade your CEC module to
software version 10.1 or earlier.) If you are running CEC firmware versions 2.0 or
2.1, which are standard with NETBuilder II software versions 8.0, 8.1, and 8.2, you
must upgrade your CEC firmware before proceeding to the next step.
CAUTION: If you are running any other firmware version besides 2.0 or 2.1, you
should upgrade the firmware after upgrading the software.
To upgrade the CEC firmware, follow 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.
b Upgrade your firmware to version 2.6 using:
bcmsysupgrade -s:upgrade_cec_fw -V:

After the firmware has been upgraded, the bridge/router reboots.
3 Update your configuration files using:
bcmsysupgrade -s:update -new_hw

4 Swap your hardware.
5 Attach a console to the Console port on the bridge/router.
6 Set up IP routing by following these steps:
a Log on to the bridge/router as root and press the Return key.
The password prompt is displayed.
b At the password prompt, press the Return key.
The network manager prompt (Enterprise OS #) is displayed.
c Set up an IP address and subnet mask using:
SETDefault ! -IP NETaddr = []

CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES

Where is the port through which the bridge/router can be accessed by
the NMS.
d Enable IP routing by entering:
SETDefault -IP CONTrol = ROute

e Enable a route discovery protocol. For example, enable OSPF by using:
SETDefault ! -OSPF CONTrol = Enable

f Check your configuration by pinging the bridge/router from the NMS:
ping

Where is the IP address of the bridge/router.
7 Set up SNMP.
This guide does not describe in detail how to set up the SNMP Service. See Using
Enterprise OS Software and Reference for Enterprise OS Software for more
information.
To enable SNMP read/write access, you need to modify two parameters in the
SNMP Service: COMmunity and MANager.
a The COMmunity parameter modifies the list of communities. For information
on how to use the COMmunity parameter, See Using Enterprise OS Software
and Reference for Enterprise OS Software.
By default all bridge/router configuration files are accessible to an SNMP-based
manager with read privileges. To change SNMP access to configuration files to
read/write for a network management station for a community named public,
enter:
ADD -SNMP COMmunity "public" RW

b With the MANager parameter, create a new manager with read/write access to
the bridge/router. For security reasons, limit the number of network
management stations by entering the IP address of the network management
station that will have access. For example, enter:
ADD -SNMP MANager “sysadm” 129.213.224.1

8 Copy the upgraded software to the bridge/router using:
bcmsysupgrade -s:to_nb -new_hw

9 Test your new software using:
bcmsysupgrade -s:test_boot -new_hw

The bridge/router is rebooted, and the utilities confirm IP connectivity and that the
expected version of software is running.
10 Verify that your upgrade completed successfully.
To verify that the software is working properly, you can perform a set of
operational integrity checks on the newly upgraded device. These may include:
■

Some standard checks based on services active.
A basic service verification test can Ping to specific IP addresses.

■

Connectivity checks based on network topology.
Examples of a connectivity verification include:
■

Checking the connectivity between devices on different networks, through
designated bridge/routers.

Upgrading Hardware and Software

■

Testing typical device connections on terminals, printers, or hosts.

■

Testing the connectivity with specific bridge/routers.

11 Accept or reject the upgrade.
■

If your software upgrade completed successfully, accept your upgrade using:
bcmsysupgrade -s:accept -new_hw

■

If the upgrade process failed to meet your verification criteria, reject your
upgrade using:
bcmsysupgrade -s:reject -new_hw

The bridge/router is rebooted using the previous version of software.
12 NETBuilder II with CEC only — (The CEC module is not supported in software
version 11.1. 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.
b Upgrade your firmware to version 2.6 using:
bcmsysupgrade -s:upgrade_cec_fw -V:

After the firmware has been upgraded, the bridge/router reboots.
13 NETBuilder 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

The bridge/router reboots after the firmware is upgraded.
Manual Recovery

This section describes how to perform a software and hardware upgrade with
manual recovery. See Chapter 3 for the memory requirements for manual
recovery.
Whenever you specify an option with bcmsysupgrade (such as -m and -new_hw),
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:
1 Back up your current software to the NMS using:
bcmsysupgrade [options] -s:from_nb -m -new_hw

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

CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES

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.
2 Update your configuration files using:
bcmsysupgrade -s:update -m -new_hw

3 Upgrade your hardware.
4 Attach a console to the Console port on the bridge/router.
5 Set up IP routing by following these steps:
a Log on to the bridge/router as root and press the Return key.
The password prompt is displayed.
b At the password prompt, press the Return key.
The network manager prompt (Enterprise OS #) is displayed.
c Set up an IP address and subnet mask using:
SETDefault ! -IP NETaddr = []

Where is the port through which the bridge/router can be accessed by
the NMS.
d Enable IP routing by entering:
SETDefault -IP CONTrol = ROute

e Enable a routing protocol. For example, enable RIP by using:
SETDefault ! -RIPIP CONTrol = (TAlk, LIsten)

f Check your configuration by verifying that the bridge/router is accessible by
using the following at the network management station:
PING

is the IP address of the bridge/router.
6 Set up SNMP.
This guide does not describe in detail how to set up the SNMP Service. See Using
Enterprise OS Software and Reference for Enterprise OS Software for more
information.
To enable SNMP read/write access, you need to modify two parameters in the
SNMP Service: COMmunity and MANager.
a The COMmunity parameter modifies the list of communities. For information
on how to use the COMmunity parameter, see Using Enterprise OS Software
and Reference for Enterprise OS Software.
By default all configuration files are accessible to an SNMP-based manager
with read privileges. To change SNMP access to configuration files to read/write
for a network management station for a community named public, enter:
ADD -SNMP COMmunity "public" RW

b With the MANager parameter, create a new manager with read/write access to
the bridge/router. For security reasons, limit the number of network

Upgrading Hardware and Software

management stations by entering the IP address of the network management
station that will have access.
For example, enter:
ADD -SNMP MANager “sysadm” 129.213.224.1

7 Copy the upgraded software to the bridge/router using:
bcmsysupgrade -s:to_nb -m -new_hw

8 Accept your upgrade using:
bcmsysupgrade -s:accept -m -new_hw

The bridge/router reboots.
9 Verify that your upgrade completed successfully.
To verify that the software is working properly, you can perform a set of
operational integrity checks on the newly upgraded bridge/router. These may
include:
■

Some standard checks based on services active.
A basic service verification test can Ping to specific IP addresses.

■

Connectivity checks based on network topology.
Examples of a connectivity verification include:
■

■

Checking the connectivity between devices on different networks, through
designated bridge/routers.

■

Testing typical device connections on terminals, printers, or hosts.

■

Testing the connectivity with specific NETBuilder bridge/routers.

10 If you determine that the new software does not meet your requirements, you can
reject the upgrade, and revert to the software version you were running before
the upgrade, by using the bcmrestore utility.
To reject your upgrade, use:
bcmrestore -new_hw

11 NETBuilder 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

The bridge/router reboots after the firmware is upgraded.
If the Bridge/Router or Switch Does Not Boot
If a failure causes the bridge/router not to boot, or if the bridge/router or switch is
inaccessible using Telnet, you must configure the bridge/router or switch at the
local console to reestablish IP connectivity. After connectivity is reestablished, you
can use the bcmrestore utility to return the bridge/router or switch to a
preupgrade state. See Chapter 7 for connectivity and recovery procedures.

CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES

UPGRADING THE SOFTWARE IMAGE
ONLY

An image-only upgrade is an upgrade that replaces the NETBuilder bridge/router
or PathBuilder S5xx series switch boot image file but does not upgrade any
configuration files. You can perform an image-only upgrade in the following
cases:
■

You are installing a patch release for your current version of software.

■

You are upgrading to a different package of the same version.

■

Your new version does not require updated configuration files (for example,
10.1 to 10.3).

■

You are upgrading a PathBuilder S5xx series switch.

You can upgrade:
■

Using Upgrade Link

■

Using the Command-Line Utilities

■

Using the Enterprise OS User Interface

You can also use Transcend Enterprise Manager or Transcend Network Control
Services to perform an image-only upgrade. See the guide that came with
Transcend for more information.
3Com recommends using the utilities instead of the Enterprise OS user interface.
The utilities automatically back up the software and perform all the necessary
copying and boot source settings automatically.

Preparing for the
Upgrade

If you are using Upgrade Link or the command-line, confirm the following items:
■

You have installed the utilities according to Chapter 2.

■

You have set the path for the utilities (UNIX only). If you have not set the path,
complete the following step for your UNIX shell:
■

For a C-shell installation, add the contents of the following file to the .cshrc
file for each user you want to have access to the utilities, including root:
/usr/3Com/common/data/.login-bcm
Or you can enter the path after every logon:
source /usr/3Com/common/data/.login-bcm

■

For a Bourne shell installation, add the contents of the following file to the
.profile file for each user you want to have access to the utilities, including
root:
/usr/3Com/common/data/.profile-bcm
Or you can enter the path after every logon:

CHAPTER 6: UPGRADING THE SOFTWARE IMAGE ONLY

. /usr/3Com/common/data/.profile-bcm
■

All configuration files are in the same directory as the boot image.

■

You have booted your bridge/router or switch from the primary boot source.

■

For Upgrade Link — You have a web browser installed with Java support, such
as Netscape Navigator 4.5 or Internet Explorer 4.x or later, and it is in your path
(UNIX).

■

There is sufficient disk space on the NMS for the amount of software you are
installing.
Minimal disk storage requirements depend on the number of different
software versions that are stored on the disk drive. Calculate:
■

6 MB for each version of NETBuilder II bridge/router images

■

6 MB for each version of PathBuilder S5xx series switch images.

■

4 MB for each version of SuperStack II, SuperStack II SI, or OfficeConnect
bridge/router images

While you must purchase one copy of software for each bridge/router or
switch, you only need to install one copy of a version of software on the NMS.

Setting Up a File
Transfer Method
Setting up for TFTP File
Transfers

You can choose to transfer files using FTP or TFTP.

If neither flag is used, TFTP is used by default for software release 11.0 and lower,
but FTP is used by default for software release 11.1 and higher. If the -ftp flag is
specified on a NETBuilder bridge/router running software version 11.0 or lower,
the FTP password is overwritten with the following text string:
****

Setting up for FTP File
Transfers

To use FTP, you need to set up your NMS in preparation for FTP file transfers.

For Upgrade Link, the user name and password is specified in the Setting Page, as
shown on page 23.

Using Upgrade Link

If no flag is used, TFTP is used by default for software release 11.0 and lower, but
FTP is used by default for software release 11.1 and higher. If the -ftp flag is
specified on a NETBuilder bridge/router running software version 11.0 or lower,
the FTP password is overwritten with the following text string:
****

On a Windows NMS, follow these steps:
1 Create a user in 3Com’s 3CServer FTP settings.
2 When using the upgrade utilities via command line or the Transcend Upgrade
Manager, specify the ftp user name and password in the BCMFTPUSER and
BCMFTPPASS environment variables.
You can specify the -ftp flag in the utilities (bcmsysupgrade, bcmbackup,
bcmrestore) if you want to use FTP file transfer.
If no flag is used, TFTP is used by default for software release 11.0 and lower, but
FTP is used by default for software release 11.1 and higher. If the -ftp flag is
specified on a NETBuilder bridge/router running software version 11.0 or lower,
the FTP password is overwritten with the following text string:
****

Using Upgrade Link

Upgrade Link contains its own web server. Client access to the web server is
available locally or remotely via a web browser. Running the Upgrade Link
application locally means that the web browser and the web server are running on
the same NMS.
See Chapter 4 for information on starting and using the Upgrade Link application.

CHAPTER 6: UPGRADING THE SOFTWARE IMAGE ONLY

Verifying the
Bridge/Router for
Upgrading

Before upgrading, run the diagnostic utility in Upgrade Link to verify connectivity
to the bridge/router by following these steps:
1 Choose a bridge/router or switch from the pop-up list in the Console page, or click
New to enter the IP address or hostname. The pop-up list contains bridge/routers
or switches that you have upgraded or backed-up before.

2 Select Verify Upgrade Services (Diagnose) and click Apply.
The Settings Page appears. Select the appropriate settings and click OK to close
the window.
The Status page appears showing the results of the diagnostic tests.
3 If the Status page shows a failure, check the SNMP read/write community string
and FTP/TFTP server settings.
If the Status page shows a success, click Home to continue with the upgrade and
return to the console page.
Upgrading the Image

To upgrade the image, follow these steps:
1 Run Upgrade Link if you have not already done so.
2 Choose a bridge/router or switch from the pop-up list in the Console page, or click
New to enter the IP address or hostname. The pop-up list contains bridge/routers
or switches that you have upgraded or backed-up before.

Using Upgrade Link

3 Select Upgrade and click Apply.
The Upgrade page appears.

4 Select a software package from the pop-up list. The list includes all packages you
have installed on the NMS for your platform. If your package is not listed, install
the software using the procedure in “Installing the Utilities on a Network
Management Station” on page 13.
CAUTION: If you select a NETBuilder bridge/router or PathBuilder switch software
package that includes encryption, a message regarding the license agreement
appears. To proceed with the installation you must accept this agreement.
The Upgrade window shows information about your system, including the flash
memory requirements for a manual or automatic recovery upgrade.
5 Click Next.

CHAPTER 6: UPGRADING THE SOFTWARE IMAGE ONLY

7 Click on the Advanced button if you want to customize the upgrade process, that
is you do not want to perform all of the upgrade at this time.
The Advanced Dialog box appears.

8 Click New Hardware if you are replacing your bridge/router with a new system. For
example, click New Hardware if you are replacing the CEC module with a DPE
module.
You cannot upgrade to a different platform. For example, you can only upgrade
an OfficeConnect bridge/router to an OfficeConnect bridge/router. You cannot
upgrade a SuperStack II NETBuilder bridge/router to a SuperStack II NETBuilder SI
bridge/router. The only exception is an upgrade from a NETBuilder II CEC module
to a DPE module.
9 If you want to alter the Reboot Timeout, enter a new number in the box. The
default setting is appropriate for most networks.
10 Click the check box for each of the stages you want to complete in the current
operation.
11 Click OK.
12 Click Apply to begin the upgrade.
The Status page appears.
13 If you are performing a hardware upgrade, replacing a CEC module with a DPE
module for example, a message to replace the hardware appears after the
software has been backed up to the NMS. Replace the hardware at this time.
14 When the upgrade is complete, the bridge/router reboots from the new software.
If the boot is not successful:
■

For automatic recovery, the bridge/router reboots from the old software.

■

15 Click Home then Exit to exit Upgrade Link.

Using the Command-Line Utilities

Using the
Command-Line
Utilities

Use the command-line utilities within a script or execute the commands manually.
Otherwise, use Upgrade Link as described on page 53.

Installing the NETBuilder
Software

You can upgrade from a CD-ROM, a tar file, or an image you have downloaded
from 3Com. If you are installing the software from a CD-ROM, complete the
procedure in “Installing the Software on the NMS” on page 37.
You can choose to transfer files using FTP or TFTP. Complete the procedure in
“Setting Up a File Transfer Method” on page 17.

Prediagnosing System
Problems

Detect any problems with SNMP or FTP/TFTP connectivity using:
bcmdiagnose

Where is the IP address or hostname of the bridge/router you are
diagnosing.
Upgrading Using
Automatic Recovery

To perform an image-only upgrade using automatic recovery, follow these steps.
See Chapter 3 for the memory requirements for automatic recovery.
Whenever you specify an option with bcmsysupgrade, you must repeat that
option for all steps in the procedure.
1 Back up your current software to the NMS using:
bcmsysupgrade [-options] -s:from_nb -I -V:

where [-options] lets you specify the EncryptionLicenseRead option that indicates
you have read and understand the encryption license agreement notice and
is the IP address or hostname of the bridge/router or switch 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.
2 Copy the configuration files into the new software directory on the NMS using:
bcmsysupgrade -s:update -I -V:

3 Copy the upgraded software to the bridge/router using:
bcmsysupgrade -s:to_nb -I -V:

4 Test your new software using:
bcmsysupgrade -s:test_boot -I -V:

The bridge/router is rebooted, and the utilities confirm IP connectivity and that the
expected version of software is running.
5 Verify that your upgrade completed successfully.
To verify that the software is working properly, you can perform a set of
operational integrity checks on the newly upgraded network. These may include:
■

Some standard checks based on services active.
A basic service verification test can Ping to specific IP addresses.

■

Connectivity checks based on network topology.

CHAPTER 6: UPGRADING THE SOFTWARE IMAGE ONLY

Examples of a connectivity verification include:
■

■

Checking the connectivity between devices on different networks, through
designated bridge/routers.

■

Testing typical device connections on terminals, printers, or hosts.

■

Testing the connectivity with specific bridge/routers or switches.

6 Accept or reject the upgrade.
■

If your software upgrade completed successfully, accept your upgrade using:
bcmsysupgrade -s:accept -I -V:

■

If the upgrade process failed to meet your verification criteria, reject your
upgrade using:
bcmsysupgrade -s:reject -I -V:

The bridge/router or switch is rebooted using the previous version of software.
Upgrading Using
Manual Recovery

To perform an image-only upgrade using manual recovery, follow these steps. See
Chapter 3 for the memory requirements for manual recovery.
Whenever you specify an option with bcmsysupgrade, you must repeat that
option for all steps in the procedure.
1 Back up your current software to the NMS using:
bcmsysupgrade [-options] -s:from_nb -m -I -V:

where [-options] lets you specify the EncryptionLicenseRead option that indicates
you have read and understand the encryption license agreement notice and
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.
2 Copy the configuration files into the new software directory on the NMS using:
bcmsysupgrade -s:update -m -I -V:

3 Copy the new software to the bridge/router using:
bcmsysupgrade -s:to_nb -m -I -V:

4 Accept the upgrade using:
bcmsysupgrade -s:accept -I -m -V:

The bridge/router reboots.
5 Verify that your upgrade completed successfully.
To verify that the software is working properly, you can perform a set of
operational integrity checks on the newly upgraded network. These may include:
■

Some standard checks based on services active.
A basic service verification test can Ping to specific IP addresses.

Using the Enterprise OS User Interface

■

Connectivity checks based on network topology.
Examples of a connectivity verification include:
■

■

Checking the connectivity between devices on different networks, through
designated bridge/routers or switches.

■

Testing typical device connections on terminals, printers, or hosts.

■

Testing the connectivity with specific bridge/routers or switches.

6 If you determine that the new software does not meet your requirements, you can
reject the upgrade, and revert to the software version you were running before
the upgrade, by using the bcmrestore utility.
To reject your upgrade, use:
bcmrestore

Using the
Enterprise OS User
Interface

If you have not installed the utilities, you can copy the boot image to the
bridge/router or switch using the Enterprise OS user interface. To copy the boot
image to the bridge/router or switch, follow these steps:
1 Install the software on a FTP/TFTP server on the LAN.
2 Attach a console or Telnet to the bridge/router or switch.
3 Log in with Network Manager privilege.
4 Change to the primary boot source directory using:
ChangeDir [:]

The default device is drive A.
5 Complete one of the following procedures:
■

If you have enough room on the bridge/router for both the current and new
image files, change the name of the current boot image using:
ReName

For example:
ReName boot.68k oldboot
■

If you do not have enough room on the bridge/router for both images, copy
the current image to the FTP/TFTP server for backup using:
COpy :

Then delete the image on the bridge/router or switch using:
RemoveFile

6 Copy the new boot file from the FTP/TFTP server to the current (primary boot)
directory using:
COpy :

For example:
COpy 129.142.10.10:image/NBSI/SW/110/CF/boot.68k boot.68k

CHAPTER 6: UPGRADING THE SOFTWARE IMAGE ONLY

7 Reboot the system by entering:
ReBoot

If the reboot is unsuccessful, the bridge/router or switch enters the monitor utility.
Boot from the old boot file using:
BT //

For example:
BT /primary/oldboot

BACKING UP AND RESTORING
SOFTWARE

You should always back up your software and configuration files to a network
management station (NMS) in case your hardware or software fails. This chapter
describes how to back up and restore the software using Upgrade Link or the
command-line utilities.

Prerequisites

Confirm the following items:
■

You have installed the utilities according to Chapter 2.

■

You have set the path for the utilities (UNIX only). If you have not set the path,
complete the following step for your UNIX shell:
■

For a C-shell installation, add the contents of the following file to the .cshrc
file for each user you want to have access to the utilities, including root:
/usr/3Com/common/data/.login-bcm
Or you can enter the path after every logon:
source /usr/3Com/common/data/.login-bcm

■

For a Bourne shell installation, add the contents of the following file to the
.profile file for each user you want to have access to the utilities, including
root:
/usr/3Com/common/data/.profile-bcm
Or you can enter the path after every logon:
. /usr/3Com/common/data/.profile-bcm

■

For NETBuilder II with DPE — All boot sources (primary, secondary, and test) are
on drive A. The DPE module has flash memory drives A and B, but the
NETBuilder Upgrade Management Utilities only support drive A. Use the
bcmconfig utility or the SysconF command on the NETBuilder II user interface
to set up the boot sources if they are not on drive A.

■

All configuration files are in the same directory as the boot image.

■

You have booted your bridge/router from the primary boot source.

■

For Upgrade Link — You have a web browser installed with Java support, such
as Netscape Navigator 4.5 or Internet Explorer 4.x, and it is in your path (UNIX).

CHAPTER 7: BACKING UP AND RESTORING SOFTWARE

Setting Up a File
Transfer Method
Setting Up for TFTP File
Transfers

You can choose to transfer files using FTP or TFTP.

If neither flag is used, TFTP is used by default for software release 11.0 and lower,
but FTP is used by default for software release 11.1 and higher. If the -ftp flag is
specified on a NETBuilder bridge/router running software version 11.0 or lower,
the FTP password is overwritten with the following text string:
****

Setting Up for FTP File
Transfers

To use FTP, you need to set up your NMS in preparation for FTP file transfers.

For Upgrade Link, the user name and password is specified in the Setting Page, as
shown on page 23.
On a UNIX NMS, follow these steps:
1 Create a user on your system with /tftpboot as the home directory.
2 When using the upgrade utilities via the command line or the Transcend Upgrade
Manager, specify this user name and password in the BCMFTPUSER and
BCMFTPPASS environment variables.
Specify the -ftp flag in all command line utilities that use file transfers
(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use FTP file transfer. For
example, to specify FTP file transfer use:
bcmsysupgrade -s:from_nb -ftp

Backing Up the Software

On a Windows NMS, follow these steps:
1 Create a user in 3Com’s 3CServer FTP settings.
2 When using the upgrade utilities via command line or the Transcend Upgrade
Manager, specify the ftp user name and password in the BCMFTPUSER and
BCMFTPPASS environment variables.
You can specify the -ftp flag in the utilities (bcmsysupgrade, bcmbackup,
bcmrestore) if you want to use FTP file transfer.
If no flag is used, TFTP is used by default for software release 11.0 and lower, but
FTP is used by default for software release 11.1 and higher. If the -ftp flag is
specified on a NETBuilder bridge/router running software version 11.0 or lower,
the FTP password is overwritten with the following text string:
****

Backing Up the
Software

Back up your software using Upgrade Link or the command-line utilities.

Using NETBuilder
Upgrade Link

Upgrade Link is an easy to use GUI for the utilities that runs in a web browser. See
Chapter 4 for information on running Upgrade Link locally or remotely. Make sure
you select and set up your file transfer method.

Using the Command
Line Utilities

You can use the command-line utilities if you want to write scripts or if you do not
have a web browser on your NMS. See “Upgrading a Bridge/Router Using the
Command-Line Utilities”on page 63 for information on using the command-line
utilities. Make sure you select and set up your file transfer method.

Verifying the Device for
Backing Up

Before backing up, run the diagnostic utility in Upgrade Link to verify connectivity
to the device by following these steps:
1 Choose a bridge/router from the pop-up list in the Console page, or click New to
enter the IP address or hostname. The pop-up list contains devices that you have
upgraded or backed-up before.

CHAPTER 7: BACKING UP AND RESTORING SOFTWARE

2 Select Verify Upgrade Services (Diagnose).
A Status window appears showing the results of the diagnostic tests.
3 If the Status window shows a failure, check the SNMP read/write community
string for FTP/TFTP file transfer permissions.
If the Status window shows a success, click Home to continue with the backup.
Backing Up the Software
To back up the software, follow these steps:
1 Run Upgrade Link if you have not already done so.
2 Choose a bridge/router from the pop-up list in the Console page, or click New to
enter the IP address or hostname. The pop-up list contains bridge/routers that you
have upgraded or backed-up before.
3 Select Backup and click Apply.
The Settings page appears.
4 Select the appropriate settings and click OK.
The Backup page appears.

5 Select the boot source you want to back up.
The box on the right shows information about the previous backups.
Assign a name to the current backup by entering a name in the edit box. Names
can be only eight characters long and may only contain alphanumeric characters.
6 Click Apply to begin the backup.
The Status window shows when the backup is complete.
7 Click Home then Exit to exit Upgrade Link.
Using the
Command-Line

Use the command-line utilities if you have a script or if you do not have a web
browser. Otherwise, use Upgrade Link as described on page 63.
Prediagnosing System Problems
Detect any problems with SNMP or FTP/TFTP connectivity using:
bcmdiagnose [-ftp | -tftp] [ | -h]

Where is the IP address or hostname of the bridge/router or switch you
are diagnosing.

Backing Up the Software

If bcmdiagnose shows a failure, check the SNMP read/write community string for
FTP/TFTP file transfer permissions.
Backing Up the Software
To back up your software to an NMS, use:
bcmbackup [both | primary | secondary] [-name:]]

Values

Directory Paths

both

Backs up both the primary and secondary boot source. This
value is the default.

primary

Backs up the primary boot source.

secondary

Backs up the secondary boot source.

Specifies the name of the backup for the boot blocks.

The IP address or hostname of the bridge/router.

All backups and upgrades use the following directory paths.
For UNIX:
/tftpboot/CLIENTS//bcm//

For example:
/tftpboot/CLIENTS/0800020A399E/bcm/name/primary/

For Windows:
\%tftpboot%\CLIENTS\\bcm\\\

For example:
\tftpboot\CLIENTS\0800020A399E\bcm\name\primary\

Values

tftpboot

For UNIX: Directory specified in inetd or tftpd for tftpd files.

%tftpboot%

CLIENTS

Name of the directory.

The MAC address of the bridge/router or switch.

switch. If the primary boot source is set to “/,” the name of
the current version of software is used instead. If the
secondary boot source is set to “/,” then the directory is
called “secondar”.

CHAPTER 7: BACKING UP AND RESTORING SOFTWARE

Restoring Software
from a Backup

Configuring IP Routing

If your bridge/router fails, you can restore software from a backup on the NMS. If
your hardware fails or you lose IP and SNMP configuration, you must first
reconfigure IP and SNMP on the bridge/router. If you still have connectivity, go to
“Restoring the Software Using Upgrade Link” on page 68 or “Restoring the
Software Using the Command-Line” on page 69.
If the bridge/router failure interrupted IP connectivity, you must set up IP routing
before restoring software.
To set up IP routing, follow these steps:
1 Attach a console to the Console port on the bridge/router.
2 Log on as root and press the Return key.
The password prompt is displayed.
3 At the password prompt, press the Return key.
The network manager prompt (Enterprise OS #) is displayed.
4 Set up an IP address and subnet mask using:
SETDefault ! -IP NETaddr = []

For more information on IP configuration, see Using Enterprise OS Software.
5 Enable IP routing by entering:
SETDefault -IP CONTrol = ROute

6 Enable a routing protocol. For example, enable OSPF using:
SETDefault ! -OSPF CONTrol = Enable

7 Ensure your configuration by verifying that the bridge/router is accessible from the
NMS using:
PING

Where is the IP address of the bridge/router.
Configuring SNMP

This chapter does not describe in detail how to set up the SNMP Service. See Using
Enterprise OS Software and Reference for Enterprise OS Software for more
information.
To enable SNMP read/write access, you need to modify two parameters in the
SNMP service: Community Manager and Manager.
1 The Community Manager parameter modifies the list of communities. For
information on how to use the COMmunity parameter, see Using Enterprise OS
Software and Reference for Enterprise OS Software.
By default all bridge/router configuration files are accessible to an SNMP-based
manager with read privileges. To change SNMP access to configuration files to
read/write for a network management station with a community named “public,”
enter:
ADD -SNMP COMmunity “public” RW

Restoring Software from a Backup

2 With the Manager parameter, create a new manager with read/write access to the
bridge/router. For security reasons, limit the number of network management
stations by entering the IP address of the network management station that will
have access. For example, enter:
ADD -SNMP Manager “sysadm” 129.213.224.1

Mapping Hostnames Using the etc/snmp.cfg File
/etc/snmp.cfg is used to configure a mapping between hostnames and/or IP
addresses and SNMP community strings. If the NETBuilder bridge/routeris
configured to accept a community string other than "public", you need to update
this file with the new community string. Follow the examples in the file when
adding your own entries.
The following is an example file showing how community strings are mapped to a
device.
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#

This file indicates which community strings are to be used
with a particular device. Follow the examples below
Timeout values are given in seconds.
Name
foo

read
write
Timeout [Platform]
public private 10
netbuilder

[platform] is optional, and must be one of:
netbuilder
netbuilder2
netbuilderro
netbuilder+
lanplex5004
lanplex5012
lanplex6004
lanplex6004R4
lanplex6012
lanplex6012R4
lanplex2500
lanplex2016
fms
fmsII
fmsbridge
fmstp8i
linkswitch
linkswitch1000
linkswitch2200
linkswitch3000
msh
msh4bridge
mshfddi
mshlinkswitch
mshtrbridge
linkconverter
Example:
192.0.10.4 private private 10

CHAPTER 7: BACKING UP AND RESTORING SOFTWARE

Restoring the Software
Using Upgrade Link

Upgrade Link is an easy to use GUI for the utilities that runs in a web browser.
Upgrade Link is an easy to use GUI for the utilities that runs in a web browser. See
Chapter 4 for information on running Upgrade Link locally or remotely. Make sure
you select and set up your file transfer method.
Verifying the Device for Restoring
Before restoring, you should run the diagnostic utility in Upgrade Link to verify
connectivity to the bridge/router or switch by following these steps:
1 Choose a device from the pop-up list in the Console page, or click New to enter
the IP address or hostname. The pop-up list contains bridge/routers that you have
upgraded or backed-up before.

2 Select Verify Upgrade Services (Diagnose) then click Apply.
A Status window appears showing the results of the diagnostic tests.
3 If the Status window shows a failure, check the SNMP read/write community
string for TFTP file transfer permissions.
If the Status window shows a success, click Home to continue with the
restoration.
Restoring the Software
To restore the software, follow these steps:
1 Access Upgrade Link if you have not already done so.
2 Choose a bridge/router or switch from the pop-up list in the Console page, or click
New to enter the IP address or hostname. The pop-up list contains bridge/routers
and switches that you have upgraded or backed-up before.

Restoring Software from a Backup

3 Select Restore and click Next.
The Setting page appears.
4 Select the appropriate settings and click OK.
The Restore page appears.

5 Select the boot source you want to restore.
The boxes on the right show information about the backups, including the names
directories and dates. You can select a backup by double-clicking it, or by entering
the name in the edit box.
6 Check the appropriate options:
■

Format the Flash — formats the flash memory before restoring the software. If
you uncheck this option, Upgrade Link will attempt to restore the software in
the available space. If there is not enough space for the image, the restoration
will fail.

■

Reboot — automatically reboots when the restoration is complete.

■

New Hardware — must be checked if you are replacing the hardware.

7 Click Apply to begin the restoration.
The Status window shows when the restoration is complete.
8 Click Home then Exit to exit Upgrade Link.
Restoring the Software
Using the
Command-Line

Use the command-line utilities if you have a script or if you do not have a web
browser. Otherwise, use Upgrade Link as described on page 68.
Prediagnosing System Problems
Detect any problems with SNMP or TFTP connectivity using:
bcmdiagnose [ -ftp | -tftp] [ | -h]

Where is the IP address or hostname of the bridge/router you are
diagnosing.
If bcmdiagnose shows a failure, check the SNMP read/write community string for
FTP/TFTP file transfer permissions.
Restoring the Software
If you are replacing the hardware, restore the software using:

CHAPTER 7: BACKING UP AND RESTORING SOFTWARE

bcmrestore -new_hw [ -]

If you are not replacing the hardware, use:
bcmrestore [ -]

Where is the name of the backup for the boot blocks.

REFERENCE FOR THE
UPGRADE MANAGEMENT UTILITIES

This chapter describes the syntax and options for each utility, as well as how to
download the utilities, and where they are installed on your system.

Accessing and
Downloading the
Utilities

The Upgrade Management Utilities are provided on CD-ROM with every
Enterprise OS software package. See Chapter 2 to install the utilities from
CD-ROM.
The upgrade utilities are installed into the directory /usr/3Com/bcm/.

Downloading the
Utilities

You can download the latest utilities from the following locations:
■

FTP — ftp.3Com.com

■

World Wide Web — http://www.infodeli.3Com.com/

■

3Com Bulletin Board Service (3ComBBS) — See Appendix D for local BBS
numbers.

See the ruu112.txt file accompanying the utilities for instructions on
decompression and installation of the utilities.
Downloading UNIX Files
The UNIX files compressed with the UNIX compress utility. To use the downloaded
files, you must first expand the files using the UNIX decompress utility. For
instructions on how to download and decompress the utilities, see the
ruu111.txt file.
The following are the UNIX files:
ruusol113.Z

Contains the utilities for Solaris 2.x.

ruuhp113.Z

Contains the utilities for HP-UX 9.0.5, 10.10, and 10.20.

ruuaix113.Z

Contains the utilities for IBM AIX 3.2.5, 4.1.4, and 4.2.

ruu112.txt

Contains the instructions for downloading and decompressing
the utilities.

Downloading Windows Files
The Windows files are compressed with a compression utility. To use the
downloaded files, you must first expand them using the decompress utility
PKUNZip. PKUNZip can be downloaded from the following URLs:
■

http://www.pkware.com/

or
■

http://infodeli.3com.com/infodeli/swlib

CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES

For instructions on how to decompress and install the utilities, see the
ruu110.txt file.
The following are the Windows files:

Update Log File

Utility Descriptions
and Syntax

Overview

ruu113.zip

Contains the utilities for Windows95, Window98, and
Windows NT 4.0.

ruu113.txt

Contains the instructions for downloading and decompressing
the utilities.

The bcmsysupgrade utility creates log files in the
tftpboot/CLIENTS//tmp directory. These log files include the
following:
■

bcmsysupgrade.log. — contains a detailed listing of transactions
executed for a stage.

■

stages.log — contains a history of bcmsysupgrade, bcmbackup, and
bcmrestore commands for all successfully completed stages and operations.
This file acts as an upgrade record of completed stages, and includes the date
and time of execution.

■

bcmupdate.log — contains a list of the configuration files converted during
the upgrade process. The file contains all stderr and stdout text, the log and
stage files. This file is appended to the bcmsysupgrade.log file when the
upgrade procedure is completed.

This section describes each of the Upgrade Management Utilities as well as the
syntax and options. The error codes for individual Enterprise OS Upgrade
Management Utilities are accessible in the man pages for the utilities. Utilities are
in alphabetical order.
Table 5 summarizes the functions of the upgrade utilities.
Table 5 Network Management Utilities Functions
Utility

Function

bcmbackup

Backs up the current bridge/router operational state and files to the network
management station.

bcmconfig

Manages the bridge/router boot source parameters.

bcmctrl

Manipulates the bridge/router boot sources. Performs booting-related
functions. Queries or waits on file transfer states.

bcmdf

Checks the media and displays the amount of used and free space.

bcmdiagnose

Identifies the most common network management station installation and
bridge/router configuration problems.

bcmftp

Sets the FTP username and password and initializes the FTP client on the
bridge/router.

bcminstall

Installs bridge/router software and firmware on a network management
station.

bcmloadconfig

Allows you to execute commands in a text file.

(continued)

Utility Descriptions and Syntax

Table 5 Network Management Utilities Functions (continued)
Utility

Function

bcmrestore

Restores a bridge/router to a previous operational state by copying files from
the network management station to the bridge/router and setting the boot
sources.

bcmsetup

Places the latest version of the Enterprise OS Upgrade Management Utilities
on the network management station. Integrates the Upgrade Management
Utilities with Transcend.

bcmsysupgrade

Performs all upgrade functions on NETBuilder bridge/routers and PathBuilder
Switches.

bcmuname

Displays general information about the bridge/router.

bcmupdate

Converts configuration files on the network management station for use with
a newer version of software.

UpgradeLink

Launches Upgrade Link.

Getting Help
Help is available in HTML or (UNIX) man pages.
Man Pages On a UNIX system, access the man pages by entering:
man bcm-intro

To access the man pages for a specific utility, use:
man

where is the name of the upgrade utility.
HTML Help To access the HTML help, enter the following URL in your browser:
/usr/3Com/bcm/gui/hlp/bcm-intro.html

Or to access help for a specific utility, use:
/usr/3Com/bcm/gui/hlp/.html

bcmbackup
Syntax

bcmbackup [both | primary | secondary] <-ftp | -tftp> [-name: ]

Description

You can use this utility to prepare a network management station as a secondary
boot source, to archive the configuration as a backup copy, to obtain a baseline
configuration, or to perform an off-line configuration. The bcmbackup utility
copies the primary and secondary boot sources from a bridge/router or switch to a
network management station. The bcmbackup utility can be used instead of the
-s:from_nb stage of bcmsysupgrade, which captures only the primary boot source.
You can assign names to the backup directories, which allows you to maintain
multiple backups of the primary and secondary boot blocks. This symbolic name is
applicable to both the primary and secondary boot blocks. The default boot block
names are supported to maintain backward compatibility.

CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES

Values

both

Default value, which backs up both the primary and
secondary boot sources.

primary

Backs up the primary boot source.

secondary

Backs up the secondary boot source.

Indicates the IP address or hostname of the bridge/router.

<-ftp | -tftp>

Specifies the file transfer protocol to be used in the backup
process.

Specifies the name to be given to the backup file of the
boot blocks.

Options

No available options.

Example

For example, to backup the primary boot block as MyBackup01 using FTP, enter:
bcmbackup primary -ftp -name:MyBackup01 199.199.199.2

bcmconfig
Syntax
Description

bcmconfig [:] [] [options]

The bcmconfig utility performs EEPROM configuration of the device and retrieves
or sets the following parameters for each boot source:
■

Path and name for load image

■

Path and name for configuration files

The bcmconfig utility does not alter the running state of the bridge/router or
switch. It only determines what happens the next time the bridge/router or switch
is rebooted. The utility also detects the following error and warning conditions:

Values

■

Files/paths not present locally to the box or locally to this server.

■

Inconsistency with other configurations in other blocks (such as subnet masks).

Indicates the name or IP address of the bridge/router.

Indicates the slot number of an I/O module. (Use options marked
with *.)

Designates type of boot source: master, primary, secondary, test,
dump, or all.
Options

Where is master, the [options] are:
-st[artup (once

Attempts to boot once.

forever |

Attempts to boot forever.

local)

Forces boot from local media.

Utility Descriptions and Syntax

Where is primary, secondary, test, or dump, the [options] are:
-configp[ath]:

Path to the configuration files.

-fi[le]:*

Name of boot file.

-bo[otdevice]:

(network

Boots from network.

localA

Boots from local media A.

localB)

Boots from local media B.

-configd[evice]: (bootdevice |
local
network)

Depends on -bootdevice.
Local media configuration.
Network configuration.

-fo[rmat]:(canonical | noncanonical) Address format.
-cl[ock]:(internal | external)

Internal/external clocking.

-conn[ector]:(v35 | rs232)

Connector type.

-ba[udrate]:

<9.6KB | 19.2KB | 38.4KB | 56KB | 64KB |
128KB | 256KB | 448KB | 1536KB | 2048KB |
4MB | 16MB>

-sl[ot]:1..8

Boot slot.

-in[terface]:(a | b)

Interface number.

-pa[ssword]:

A character string from 0–5 characters.

-di[scovery]:( | ) Address discovery.
-ga[teway]:

Default gateway IP address.

-lo[calip]:

Bridge/router IP address.

-se[rver]:

TFTP boot server IP address.

-cf[gserver]:

Server where configuration files are stored.

-ma[sk]:

Bridge/router subnet mask.

-notraps

Disables the sending of SNMP traps useful
during upgrading.

-re[tries]:0..255

Number of retries from 0–255.

-traps

Enables the sending of SNMP traps; useful
after upgrade completes.

bcmctrl
Syntax
Description

bcmctrl [:] [-

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.2
Linearized                      : Yes
Create Date                     : 1999:05:10 12:40:30
Producer                        : Acrobat Distiller 3.01 for Power Macintosh
Author                          : 
Title                           : Upgrading Enterprise OS Software
Creator                         : FrameMaker 5.5.3
Subject                         : 09-1551-001
Modify Date                     : 1999:05:11 13:05:40
Page Count                      : 120
Page Mode                       : UseOutlines

EXIF Metadata provided by EXIF.tools

3Com ENTERPRISE OS 11.3 Upgrading Software User Manual To The 97b02aa8 7839 4bed B13a Eac5b6a890e7

Navigation menu

Versions of this User Manual:

Views

Navigation