3Com Water System ENTERPRISE OS 113 User Manual

Upgrading Enterprise OS

Softw are

Softw are version 11.3

http://w w w .3com.com/

Part No. 09-1551-001

Published May 1999

Download from Www.Somanuals.com. All Manuals Search And Download.

CONTENTS

A B O UT T HIS G UIDE

Con v e nt i o ns

Y e ar 2000 Comp l i a nce

1 O VERVIEW

U p grade T o o l s a nd P r o cess

H o w the U t i li t i e s Work 10

Pri m ar y , S e condar y , a nd T e st B o ot S o urces 10

A u tomat i c o r Manual R e co v e ry 10

R u l e s and S u pport L i m i t at i o ns 11

T a ke T i m e to P l a n 11

2 I NSTA L LI N G THE U TILITIES O N A N ET W O R K M ANAGEMENT S TATI O N

I n sta l li n g the U t i li t i e s on a W i n dows S ys t em 13

I n sta l li n g the U t i li t i e s on a U NIX Sys t em 14

Pr e par i n g for the I n sta l l a t i o n 14

Pr o cedure 14

S e tt i n g up for A u to S t artup 16

3 P L A NNING AND P REPARING THE U PGRADE

S e tt i n g up for T FTP File T r ansfers 17

S e tt i n g up for F TP File T r ansfers 17

A u tomat i c R e co v e ry 18

Manual R e co v e ry 19

Checking D R AM 2 0

Checking F l a sh Memory 20

Checking the Software V e rsion 21

Pl a nn i n g T a b l e s 21

4 U PGRADING U SING THE NETB UILDER U PGRADE L INK A PP L ICATI O N

S t atus and S e tt i n gs P a ges 27

S e tt i n gs P a ge 28

V e rifying for Upgrading 29

I n sta l li n g S o ftware on the N MS 29

Pr o cedure 30

U p grad i n g S o ftware 31

Download from Www.Somanuals.com. All Manuals Search And Download.

5 U PGRADING A B RIDGE /R OUTER U SING THE C OMMAND -L INE U TILITIES

Pr e par i n g for the U p grade 35

S e tt i n g up for T FTP File T r ansfers 36

S e tt i n g up for F TP File T r ansfers 36

Pr e d i a gnos i n g S ys t em P r o b l e ms 37

I n sta l li n g the S o ftware on the N MS 37

S o ftware Directories 38

Usi n g the B c msysupgrade Utility to Upgrade 39

Fil e names 40

NETB u i l d er I I B r idge/R o uter 40

S u per S t ack I I NETB u i l d er and OfﬁceConnect N E TB u i l d er B r idge/R o uters 41

P a th B u i l d er S 5 x x S e ries Switch 41

U p grad i n g S o ftware Only 41

A u tomat i c R e co v e ry 41

Manual R e co v e ry 43

If t he B r idge/R o uter or S w i t ch Does Not B o ot 44

U p grad i n g H a rdware and S o ftware 44

A u tomat i c R e co v e ry 44

Manual R e co v e ry 47

If t he B r idge/R o uter or S w i t ch Does Not B o ot 49

6 U PGRADING THE S O F T W ARE I MAGE O N L Y

Pr e par i n g for the U p grade 51

S e tt i n g up for T FTP File T r ansfers 52

S e tt i n g up for F TP File T r ansfers 52

Usi n g U p grade L i n k 53

V e rifying the B r idge/R o uter for U p grad i n g 54

U p grad i n g the I m age 54

Usi n g the Command-L i n e U t i li t i e s 57

I n sta l li n g the N ETB u i l d er S o ftware 57

Pr e d i a gnos i n g S ys t em P r o b l e ms 57

U p grad i n g U si n g A u tomat i c R e co v e ry 57

U p grad i n g U si n g Manual R e co v e ry 58

Usi n g the E n terpr i se OS User I n terface 59

7 B ACKING U P AND R EST O R ING S O F T W ARE

S e tt i n g U p for T FTP File T r ansfers 62

S e tt i n g U p for F TP File T r ansfers 62

B a cking Up the Software 63

Usi n g N ETB u i l d er U p grade L i n k 63

Usi n g the Command L i n e U t i li t i e s 63

V e rifying the Device for B a cking Up 63

B a cking Up the Software 64

Usi n g the Command-L i n e 64

Pr e d i a gnos i n g S ys t em P r o b l e ms 64

B a cking Up the Software 65

Download from Www.Somanuals.com. All Manuals Search And Download.

Dir e ctory Paths 65

R e storing Software from a B a ckup 66

Conﬁguring I P R o ut i n g 66

Conﬁguring SNMP 66

Mapp i n g H o stnames U si n g the etc/snmp.cfg F ile 6 7

R e storing the Software Using Upgrade L i n k 68

V e rifying the Device for R e storing 68

R e storing the Software 68

R e storing the Software Using the Command-L i n e 69

Pr e d i a gnos i n g S ys t em P r o b l e ms 69

R e storing the Software 69

8 R EFERENCE F O R T HE U PGRADE M ANAGEMENT U TILITIES

Accessing and Downloading the Utilities 71

D o wn l o ad i n g the U t i li t i e s 71

D o wn l o ad i n g U NIX Fil e s 71

D o wn l o ad i n g W i n dows F il e s 71

U p date L o g F ile 7 2

U t i li t y D e scriptions and Syntax 72

Overview 72

Gett i n g H e l p 7 3

bcm i n sta l l 7 8

U p grade L i n k 84

A T R O UB L ESH O O T ING

Gett i n g H e l p 8 5

Man Pages 85

HTML H e l p 8 5

General T r oub l e shoot i n g E r ror Messages 85

R e turn Codes from bcmd i a gnose 86

H a rdware-R e l a ted Messages 87

I n sta l l a t i o n T r oub l e shoot i n g Messages 87

I n sta l li n g the E n terpr i se OS Upgrade Management Utilities 87

D e term i n i n g Connect i vi t y 88

V a l i d at i n g the S NMP S e rvice Conﬁguration 88

Download from Www.Somanuals.com. All Manuals Search And Download.

T e st i n g the N MS/ TFTP C o nﬁgurat i o n 89

Creating an Upgrade F ile 8 9

U p l o ad i n g an U p grade F ile 9 0

D o wn l o ad i n g an U p grade F ile 9 1

B C HOOSING A S O F T W ARE P ACKAGE

NETB u i l d er I I U p grade M i g rat i o n P a th 93

S u per S t ack I I NETB u i l d er U p grade M i g rat i o n P a th 96

S u per S t ack I I NETB u i l d er S I U p grade M i g rat i o n P a th 98

OfﬁceConnect N E TB u i l d er U p grade M i g rat i o n P a th 99

P a th B u i l d er U p grade M i g rat i o n P a th 101

C M OUNTING THE CD-ROM ON A UNIX P L A TF O R M

Mount i n g the C D -ROM o n S o l a ris 2.5.x 103

Mount i n g a L o cal CD-R O M Drive 103

Mount i n g from a R e mote C D -ROM Drive 1 03

Mount i n g the C D -ROM o n H P-UX 1 0.x 105

Mount i n g from a L o cal CD-R O M Drive 105

Mount i n g from a R e mote C D -ROM Drive 1 05

Mount i n g the C D -ROM o n I BM AIX 4 .1.x T h rough 4.2.x 106

Mount i n g from a L o cal CD-R O M Drive 106

Mount i n g from a R e mote C D -ROM Drive 1 06

U n mount i n g the C D -ROM 1 07

D T ECHNICAL S UPPORT

Online T e chn i cal Services 109

World Wide Web Site 109

3Com K n ow l e dgebase Web S e rvices 109

3Com F TP Si t e 109

3Com B u l l e t i n B o ard Service 110

Access by Analog Modem 110

Access by Digital Modem 110

3Com F a cts A u tomated F a x S e rvice 110

S u pport from Y o ur N e twork S u pp l i e r 110

S u pport from 3Com 111

R e turn i n g P r o ducts for R e pa i r 1 12

G L O SSARY

I NDEX

3 C OM C O R PORATION L I M I TED W ARRANTY

Download from Www.Somanuals.com. All Manuals Search And Download.

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

OfﬁceConnect^®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

T a b l e 1 a nd T ab l e 2 list conventions that are used throughout this guide.

Table 1 Notice Icons

Icon

Notice Type

Description

Information note

Important features or instructions

Caution

Warning

Information to alert you to potential damage to a

program, system, or device

Information to alert you to potential personal injury

Download from Www.Somanuals.com. All Manuals Search And Download.

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 !<port> -RIPIP CONTrol = Listen

In this example, you must supply a port number for <port>.

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].

Menu commands

and buttons

Menu commands or button names appear in italics. Example:

From the Help menu, select Contents.

Words in italicized

type

Italics emphasize a point or denote new terms at the place where they

are defined in the text.

Year 2000 Compliance

For information on Year 2000 compliance and 3Com products, visit the

3Com Year 2000 Web page:

http://www.3com.com/products/yr2000.html

Download from Www.Somanuals.com. All Manuals Search And Download.

OVERVIEW

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

limitations.

Upgrade Tools and

Process

The upgrade procedures in this guide use the Enterprise OS Upgrade Management

Utilities on a UNIX or Windows network management station (NMS).

Deﬁnition of network An NMS is a UNIX or Windows system that has a TFTP/FTP server running in

management station

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

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 1: OVERVIEW

Fi g ure 1 shows the t y p i cal upgrade process.

Figure 1 Upgrade Process

Begin

Is hardware

upgrade

Back up config

required?

and boot files

Install software

from bridge/router

and utilities

Yes

Update

config files

to NMS

on NMS*

If hardware

upgrade, reinstall

old hardware

upgrade?

Restore old

software

version

Reboot bridge/router,

test software images

and config files

Verify

upgrade

Perform

hardware

upgrade

Reject

Yes

Do final cleanup

Copy config

and boot files

to bridge/router

Reset IP

config and

SNMP

Done!

*NMS = network management station

How the Utilities Work The software on your bridge/router or switch consists of a bootable image ﬁle and

conﬁguration ﬁles that store all your settings. The Enterprise OS Upgrade

Management Utilities update all your software ﬁles after copying them to a UNIX

or Windows NMS. Because the upgrade occurs on a copy of the ﬁles on the NMS,

the bridge/router remains operational during the upgrade. The utilities then copy

the new image and updated ﬁles 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 ﬁles.

Automatic or Manual Recovery

If your switch or bridge/router has enough ﬂash 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 ﬂash 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.

Download from Www.Somanuals.com. All Manuals Search And Download.

Rules and Support Limitations

Rules and Support

Limitations

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

■

The utilities do not support Remote Boot and Conﬁguration 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 OfﬁceConnect^®bridge/router to an OfﬁceConnect 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.

Take Time to Plan

Because networks today have become increasingly complex, upgrading your

network requires a systematic approach. 3Com recommends that you plan your

upgrade carefully before i m p l e ment i n g i t . S e e Chapter 3 to p l a n y o ur upgrade.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 1: OVERVIEW

Download from Www.Somanuals.com. All Manuals Search And Download.

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:

■

Solaris 2.x

HP-UX 10.x

IBM AIX 4.x or later

Windows NT 4.x

Windows 95/98

Installing the Utilities

on a Window s System

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:

Insert the CD-ROM into the CD-ROM drive.

b Open a command window.

Change to the CD-ROM directory.

For example, if E is the drive letter for the CD-ROM, enter:

3 If you download the utilities to your hard d i sk (see Chapter 8 for information

about downloading the utilities):

Decompress the utilities.

b Open a command window.

Change to the utilities directory using:

<drive>:\<path>\

Download from Www.Somanuals.com. All Manuals Search And Download.

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 deﬁnitions for use

with Transcend if required, use:

bcmsetup <drive>: all

Where <drive> 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 ﬁle:

<drive>:\usr\3com\bcm\bin\

<drive>:\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:

<drive>:\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

You can install the utilities from a CD-ROM or from utilities that you have

downloaded to your hard disk.

Preparing for the Before installing the utilities, verify the following items:

Installation

■

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

■

Your root password on the NMS (UNIX only).

Your NMS is running a TFTP/FTP server.

Procedure 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:

Mount the CD-ROM.

For more information on mounting instructions for each supported UNIX

operat i n g system, see Appendix C.

b Change to the appropriate directory on the CD-ROM for your operating system

using:

cd /<cd-rom path>/<os>

Where <os> is the directory for your operating system:

Download from Www.Somanuals.com. All Manuals Search And Download.

Installing the Utilities on a UNIX System

Table 1 UNIX Directories

Operating System

Solaris 2.5.x

Directory Name

sunos5

HP_UX

aix

HP-UX 10.x

IBM AIX 4.1.x, 4.2x

■

If you download the utilities to your hard d i sk (see Chapter 8 for information

about downloading the utilities):

Decompress the utilities.

b Change to the utilities directory on your hard disk using:

cd /<path>/

3 Run the setup program.

■

To install all packages from the CD-ROM, including the utilities and package

deﬁnitions 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 ﬁle to the .cshrc ﬁle

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 ﬁle to the

.proﬁle ﬁle for each user you want to have access to the utilities, including root:

/usr/3Com/common/data/.proﬁle-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

Download from Www.Somanuals.com. All Manuals Search And Download.

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.

Download from Www.Somanuals.com. All Manuals Search And Download.

PLANNING AND PREPARING THE

UPGRADE

This chapter describes setting up a ﬁle 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 ﬁll

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 ﬂash 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

v e rsion, see Appendix B .

Setting Up a File

Transfer Method

You can choose to transfer ﬁles using FTP or TFTP.

Setting up for TFTP File To use TFTP, you need to set up your NMS in preparation for TFTP ﬁle transfers.

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 ﬂag in all command line utilities which use ﬁle transfers

(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use TFTP ﬁle transfer. For

example, to specify TFTP ﬁle transfer use:

bcmsysupgrade -s:from_nb -tftp <device>

If neither ﬂag 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 ﬂag is

speciﬁed 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 To use FTP, you need to set up your NMS in preparation for FTP ﬁle transfers.

Transfers

For Upgrade Link, the user name and password is speciﬁed in the Setting Page, as

shown on page 23.

Download from Www.Somanuals.com. All Manuals Search And Download.

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 ﬂag in all command line utilities that use ﬁle transfers

(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use FTP ﬁle transfer. For

example, to specify FTP ﬁle transfer use:

bcmsysupgrade -s:from_nb -ftp <device>

If no ﬂag 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 ﬂag is

speciﬁed 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 ﬂag in the utilities (bcmsysupgrade, bcmbackup,

bcmrestore) if you want to use FTP ﬁle transfer.

If no ﬂag 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 ﬂag is

speciﬁed 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

If you have enough ﬂash 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.

Automatic Recovery 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.

Download from Www.Somanuals.com. All Manuals Search And Download.

Manual Recovery An upgrade with manual recovery (using the -m option with the bcmsysupgrade

utility) formats the ﬂash memory after backing up the current software, then

copies the upgraded ﬁles 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 ﬂash 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.

T a b l e 2 lis t s 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:

Softw are Package

Model

DRAM Required

Automatic Recovery Manual Recovery

NETBuilder II w ith DPE:

(The standard flash memory card from 3Com

is 20 MB)

(AC) - APPN/Connection Services

(DW) - Multiprotocol Router

DPE

All DPE modules

ship with enough

DRAM for all

40 MB

20 MB

software packages.

(DE) - Multiprotocol Router with

56-bit Encryption

DPE

All DPE modules

ship with enough

DRAM.

40 MB

20 MB

(DS) - Multiprotocol Router with

128-bit Encryption

SuperStack II NETBuilder Token Ring:

(TE) - Multiprotocol Router with

Encryption

327, 527

12 MB

8 MB

4 MB

SuperStack II NETBuilder SI:

(NW) - IP/IPX/AT Router

432, 442, 452, 462 All SuperStack II NETBuilder SI bridge/routers ship with enough

532, 542, 552, 562 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

(AX) - APPN/Connection Services

437, 447, 457, 467

537, 547, 557, 567

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 432, 442, 452, 462

Encryption

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

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 3: PLANNING AND PREPARING THE UPGRADE

Table 2 Version 11.2 Software Packages (continued)

Flash Memory Required for:

Softw are Package

OfﬁceConnect NETBuilder:

(FD) - FRAD

Model

DRAM Required

Automatic Recovery Manual Recovery

120

8 MB

4 MB

(NW) - IP/IPX/AT Router

112, 122, 132, 142 8 MB

4 MB for 132

2 MB for all others

(BF) - Boundary Router

(OF) - Multiprotocol Router

(AF) - APPN

113, 123, 143

117, 127, 137, 147 12 MB

116, 126, 146 12 MB

112, 122, 132, 142 8 MB

8 MB

4 MB

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

Encryption

4 MB for 132

2 MB for all others

(NS) - IP/IPX/AT Router with 128-bit 112, 122, 132, 142 8 MB

Encryption

4 MB

8 MB

4 MB for 132

2 MB for all others

(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

4MB

(OS) - Multiprotocol Router with

128-bit Encryption

(VW)- Multiprotocol Rou;r

PathBuilder S5xx Sw itch

(PW) - Multiprotocol Router

147

12 MB

S500, S580, S593, 160 MB

S594

16 MB

4 MB

(PE) - Multiprotocol Router with

56-bit Encryption

S500, S580, S593, 160 MB

S594

(PS) - Multiprotocol Router with

128-bit Encryption

S500, S580, S593, 160 MB

S594

Checking DRAM To check how much DRAM you have installed on the switch or bridge/router, on

the NMS use:

bcmuname -M <device>

Where <device> is the IP address or hostname of the switch or bridge/router.

Checking Flash Memory To check how much ﬂash memory you have installed on the switch or

bridge/router, on the NMS use:

bcmdf <device>[:<drive:>]

Where <device> 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 OfﬁceConnect bridge/routers.

Download from Www.Somanuals.com. All Manuals Search And Download.

Checking the Software Version

Checking the

Softw are Version

To display the current software version and package you are running, use the

bcmuname utility on the NMS:

bcmuname -R <device>

Where <device> 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 ﬁll out background information

about your bridge/routers before starting the upgrade process. The NETBuilder II

tab l e is o n page 22. T h e S u per S t ack I I NETB u i l d e r, SuperStack II NETBuilder SI,

OfﬁceConnect NETBuilder, and P a th B u i l d er sw i t ch tab l e is o n 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.

Download from Www.Somanuals.com. All Manuals Search And Download.

A u t o m a t i c R e c o v e r y ?

E n o u g h F l a s h M e m o r y f o r

M a n u a l R e c o v e r y ?

E n o u g h F l a s h M e m o r y f o r

( p r e - 1 0 . 3 u p g r a d e o n l y )

C E C O n l y : F i r m w a r e V e r s i o n

a n d T w o - L e t t e r C o d e

C u r r e n t S o f t w a r e V e r s i o n

a n d T w o - L e t t e r C o d e

N e w S o f t w a r e V e r s i o n

M a n u a l R e c o v e r y ?

H a r d w a r e U p g r a d e ?

Download from Www.Somanuals.com. All Manuals Search And Download.

A u t o m a t i c R e c o v e r y ?

E n o u g h F l a s h M e m o r y f o r

M a n u a l R e c o v e r y ?

E n o u g h F l a s h M e m o r y f o r

D R A M

a n d T w o - L e t t e r C o d e

C u r r e n t S o f t w a r e V e r s i o n

a n d T w o - L e t t e r C o d e

N e w S o f t w a r e V e r s i o n

M a n u a l R e c o v e r y ?

H a r d w a r e U p g r a d e ?

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 3: PLANNING AND PREPARING THE UPGRADE

Download from Www.Somanuals.com. All Manuals Search And Download.

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, conﬁrm the following items:

■

You have installed the utilities accord i n g 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 ﬁle to the .cshrc

ﬁle 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 ﬁle to the

.proﬁle ﬁle for each user you want to have access to the utilities, including

root:

/usr/3Com/common/data/.proﬁle-bcm

Or you can enter the path after every logon:

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

■

All conﬁguration ﬁles 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 sufﬁcient disk space on the NMS for the amount of software you are

installing.

Download from Www.Somanuals.com. All Manuals Search And Download.

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

OfﬁceConnect 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 speciﬁed, Upgrade Link will allow a remote client to

access the server without user authent i cation, see “S e tt i n gs P a ge” 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 ﬁle 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 ﬁle is an ASCII text ﬁle containing the

IP addresses of clients to upgrade devices. The allow ﬁle 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 <port> [-NoSecurity | -NoAuthentication]

Download from Www.Somanuals.com. All Manuals Search And Download.

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 speciﬁed, the bcmnbrus command allows connections from all

IP addresses. Otherwise, only those client IP addresses listed in

the/usr/3Com/common/data/allow ﬁle 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 ﬁle is an ASCII text ﬁle containing the

IP addresses of clients to upgrade devices. The allowed ﬁle looks like the following:

129.213.100.151

129.213.100.152

139.87.172.100

When NoAuthentication is speciﬁed, the bcmnbrus command allows the remote

cli e nt to access the server without user authent i cation, see “S e tt i n gs P a ge” on

page 28 for a descr i p t i o n of the a v a i l a b l e settings.

■

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

http://<server_nam>:<port>/

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. T a b l e 3 d escribes the buttons on the bottom of the S t atus 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.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION

Table 3 Status page Buttons (continued)

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.

Settings Page The Setting Page lets you establish basic settings.

■

You can choose the method of ﬁle 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 speciﬁed 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 speciﬁed 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.

Download from Www.Somanuals.com. All Manuals Search And Download.

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

“S e tt i n gs P a ge” on page 28 and c l ick 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 Softw are on

the NMS

Upgrade Link installs the software on the NMS in the following directory:

Windows:

\%tftpboot%\image\<platform>\SW|FW\<version>\<pkg>

UNIX:

/tftpboot/image/<platform>/SW|FW/<version>/<pkg>

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.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION

Values

tftpboot

For UNIX: Directory speciﬁed in inetd or tftpd for tftpd ﬁles.

% tftpboot% For Windows (using the default 3Com TFTP server): Directory

speciﬁed in the 3Server conﬁguration.

NETBuilder II with CEC Module:

NETBuilder II with DPE Module:

NBII

NBDPE

SuperStack II NETBuilder SI bridge/router: NBSI

SuperStack II NETBuilder Ethernet

bridge/router:

NBRO

NBR2T

NBRI

SuperStack II NETBuilder Token Ring

bridge/router:

SuperStack II NETBuilder Ethernet/ISDN

bridge/router:

SuperStack II NETBuilder Token Ring/ISDN NBR2TI

bridge/router:

OfﬁceConnect NETBuilder bridge/router:

PathBuilder S5xx switch:

NBOCF

NBPB500

[SW | FW]

Two letter designator shown on the CD-ROM label.

The software or ﬁrmware directory.

Software version 9.0 through 11.3.

Procedure 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.

S e e A p pend i x C for information on how to mount the CD-R O M on a UN I X s ystem.

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.

Download from Www.Somanuals.com. All Manuals Search And Download.

Upgrading Software

5 Click Apply.

The Install page appears.

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

■

For UNIX CD-ROM, use the following path:

cdrom/<mount path>/image/

■

For Windows CD-ROM, use the following path:

<CD-ROM drive>:\image\

■

For Archive, enter the entire path including the ﬁlename.

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. Conﬁrm you selection when prompted.

9 When the installation is complete, click Home to continue with the upgrade.

Upgrading Softw are

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

“S e tt i n gs P a ge” on page 28 and c l ick OK to close the window.

The Upgrade page appears.

Download from Www.Somanuals.com. All Manuals Search And Download.

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 “I n sta l li n g S o ftware on the N MS” o n

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 ﬂash

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.

Download from Www.Somanuals.com. All Manuals Search And Download.

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 OfﬁceConnect bridge/router to an OfﬁceConnect 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 conﬁgure 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.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION

Download from Www.Somanuals.com. All Manuals Search And Download.

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 L i n k app l ic a t i o n 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:

■

U p grad i n g S o ftware Only

■

A u tomat i c R e co v e ry

Manual R e co v e ry

■

U p grad i n g H a rdware and S o ftware

■

A u tomat i c R e co v e ry

Manual R e co v e ry

■

Preparing for the

Upgrade

Before upgrading your system, conﬁrm the following items:

■

You have installed the utilities accord i n g 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 ﬁle to the .cshrc

ﬁle 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 ﬁle to the

.proﬁle ﬁle for each user you want to have access to the utilities, including

root:

/usr/3Com/common/data/.proﬁle-bcm

Or you can enter the path after every logon:

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

■

All conﬁguration ﬁles are in the same directory as the boot image.

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

There is sufﬁcient disk space on the NMS for the amount of software you are

installing.

Download from Www.Somanuals.com. All Manuals Search And Download.

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

OfﬁceConnect 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 ﬁles using FTP or TFTP.

Setting up for TFTP File Transfers

To use TFTP, you need to set up your NMS in preparation for TFTP ﬁle 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 ﬂag in all command line utilities which use ﬁle transfers

(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use TFTP ﬁle transfer. For

example, to specify TFTP ﬁle transfer use:

bcmsysupgrade -s:from_nb -tftp <device>

If neither ﬂag 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 ﬂag is

speciﬁed 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 ﬁle transfers.

For Upgrade Link, the user name and password is speciﬁed 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 ﬂag in all command line utilities that use ﬁle transfers

(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use FTP ﬁle transfer. For

example, to specify FTP ﬁle transfer use:

bcmsysupgrade -s:from_nb -ftp <device>

Download from Www.Somanuals.com. All Manuals Search And Download.

Prediagnosing System Problems

If no ﬂag 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 ﬂag is

speciﬁed 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 ﬂag in the utilities (bcmsysupgrade, bcmbackup,

bcmrestore) if you want to use FTP ﬁle transfer.

If no ﬂag 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 ﬂag is

speciﬁed on a bridge/router running software version 11.0 or lower, the FTP

password is overwritten with the following text string:

****

Prediagnosing System

Problems

Before you begin your upgrade, 3Com recommends that you run the

bcmdiagnose utility specifying the ﬁle 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 ﬁle 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 ] [<device> | -h]

Where <device> is the IP address or hostname of the bridge/router you are

upgrading. The -ftp and -tftp ﬂags force the speciﬁed ﬁle transfer types. See

A p pend i x A for more information about any error messages that may appear.

Installing the

To install the NETBuilder software, follow these steps:

Softw are on the NMS

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.

Mount the CD-ROM (UNIX only).

S e e A p pend i x C for information on how to mount the CD-R O M.

3 Make sure you are using version 11.3 of the Enterprise OS Upgrade Management

Utilities.

Download from Www.Somanuals.com. All Manuals Search And Download.

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 ﬁrst

install the 11.3 utilities accord i n g 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 [<path>]

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 Window s, open a command window and use:

bcminstall -cdrom <CD-ROM drive>:\image

From a Tarred File, use:

■

bcminstall -tar <path>/<filename>

From an Image File, use:

bcminstall -image <path>/<filename>

The image ﬁle is the NETBuilder bridge/routers boot ﬁle, for example, boot.29K or

boot.68k.

Softw are Directories The bcminstall utility installs the software on the NMS in the following directory:

Windows:

\%tftpboot%\image\<platform>\SW|FW\<version>\<pkg>

UNIX:

/tftpboot/image/<platform>/SW|FW/<version>/<pkg>

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.

Download from Www.Somanuals.com. All Manuals Search And Download.

Using the Bcmsysupgrade Utility to Upgrade

Values

tftpboot

For UNIX: Directory speciﬁed in inetd or tftpd for tftpd ﬁles.

% tftpboot% For Windows (using the default 3Com TFTP server): Directory

speciﬁed in the Win.ini ﬁle in the “[3Com.nm] TFTPROOT=”

section. The Win.ini ﬁle is located in the default Windows

directory, for example C:\windows or C:\winnt4.

NETBuilder II with CEC Module:

NETBuilder II with DPE Module:

NBII

NBDPE

SuperStack II NETBuilder SI bridge/router: NBSI

SuperStack II NETBuilder Ethernet

bridge/router:

NBRO

NBR2T

NBRI

SuperStack II NETBuilder Token Ring

bridge/router:

SuperStack II NETBuilder Ethernet/ISDN

bridge/router:

SuperStack II NETBuilder Token Ring/ISDN NBR2TI

bridge/router:

OfﬁceConnect NETBuilder bridge/router:

PathBuilder S5xx Switch:

NBOCF

NBPB500

[SW | FW]

Two letter designator shown on the CD-ROM label.

The software or ﬁrmware 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] <stage> <device>

S e e “bcms y supgrade” 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 reco v e ry (see “C hoosing

A u tomat i c R e co v e ry or Manual R e co v e ry” 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 T a b l e 4 for a description of the options.

Download from Www.Somanuals.com. All Manuals Search And Download.

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

For UNIX, after you have upgraded, check the /tftpboot/CLIENTS/<IP address or

mac address>/tmp/stages.log ﬁle to ensure that the options were used

consistently throughout the upgrade process.

For Windows, after you have upgraded, check the \%tftpboot%\CLIENTS\<IP

address or mac address>\tmp\stages.log ﬁle to ensure that the options were used

consistently throughout the upgrade process.

T a b l e 4 lis t s the most common bcms y supgrade opt i o ns.

Table 4 Common Options for Bcmsysupgrade

Task

Option

Image-only upgrade

-V:<version you are upgrading to>

Upgrading to a software version other than 11.1

Upgrading unlike packages

Upgrading with Manual Recovery

Specifying encryption license agreement.

Using TFTP file transfer.

-k:<package you are upgrading to>

-m

-EncryptionLicenseRead

-tftp

-ftp

Using FTP file transfer.

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

The same options must be used to upgrade conﬁguration ﬁles:

bcmsysupgrade -s:update -k:FF -V:101005 -m <device>

S e e Chapter 8 for more information about how to use bcmsysupgrade for

specialized cases.

Filenames

The following sections list the ﬁles that may be used when you upgrade a

NETBuilder system.

NETBuilder II Bridge/Router

■

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

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

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

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

4portw an.860 — image ﬁle that boots the HSS 4-Port WAN module.

iofw _upd.29k — ﬁle that updates the ﬁrmware for HSS 3-port, HSS 4-port,

HSS 8-port, and MP modules.

■

sys — ﬁle that is used during the upgrade process to determine the source OT

target software version.

Download from Www.Somanuals.com. All Manuals Search And Download.

Upgrading Software Only

■

ccsmacro — ﬁle that contains predeﬁned user macros.

fpupdate.29k (CEC Only) — ﬁle that updates the CEC module ﬁrmware.

You may also have several conﬁguration ﬁles that will be upgraded by the utilities.

SuperStack II NETBuilder and OfﬁceConnect NETBuilder Bridge/Routers

■

boot.68k — image ﬁle that boots the system.

■

sys — ﬁle that may be used during the upgrade process to determine the

source or target software version.

You may also have several conﬁguration ﬁles that will be upgraded by the utilities.

PathBuilder S5xx Series Sw itch

■

boot.ppc — image ﬁle that boots the system.

■

sys — ﬁle that may be used during the upgrade process to determine the

source or target software version.

Upgrading Softw are

Only

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 “U p grad i n g H a rdware and S o ftware” on page 44.

Automatic Recovery This section describes how to perform an upgrade of the Enterprise OS software

that does not include a hardware upgrade. S e e Chapter 3 for the memory

requirements for automatic recovery.

Whenever you specify an option with bcmsysupgrade, you must repeat that

opt i o n for a l l steps in the procedure. See T a b l e 4 o n page 40 or “bcms y supgrade”

on page 81 for a l ist o f the opt i o ns a v a i l a b l e t o use w i t h the bcms y supgrade utilit y.

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

where [-options] lets you specify the -EncryptionLicenseRead ﬂag that indicates

you have read and understand the encryption license agreement notice and

<device> is the IP address or hostname of the bridge/router you are upgrading.

CAUTION: When upgrading to a package containing encryption, you must specify

the -EncyrptionLicenseRead option ﬂag. If you attempt to upgrade to an

encrypted package and you have not speciﬁed the -EncryptionLicenseRead option,

the upgrade will fail.

The bcmsysupgrade utility only backs up the ﬁles 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.3. However, you can use the utilities to upgrade your CEC module to

software version 10.1 or earlier.) If you are running CEC ﬁrmware 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 ﬁrmware before proceeding to the next step.

Download from Www.Somanuals.com. All Manuals Search And Download.

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

CAUTION: If you are running any other ﬁrmware version besides 2.0 or 2.1, you

should upgrade the ﬁrmware after upgrading the software.

To upgrade the CEC ﬁrmware, follow these steps:

Make sure there is a ﬂoppy diskette with write access in the ﬂoppy 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 ﬁrmware upgrade using the option -m if you do not want

the ﬂoppy diskette formatted.

b Upgrade your ﬁrmware to version 2.6 using:

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

After the ﬁrmware has been upgraded, the bridge/router reboots.

3 Update your conﬁguration ﬁles using:

bcmsysupgrade -s:update <device>

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

bcmsysupgrade -s:to_nb <device>

5 Test your new software using:

bcmsysupgrade -s:test_boot <device>

The bridge/router is rebooted, and the utilities conﬁrm 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 veriﬁcation test can Ping to speciﬁc IP addresses.

Connectivity checks based on network topology.

Examples of a connectivity veriﬁcation 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 speciﬁc bridge/routers.

■

Custom checks based on applications and typical network use.

For instance, you can check normal operation over the network and perform

ﬁle transfers, as well as run traces on speciﬁc routes or check routing tables.

7 Accept or reject the upgrade.

■

If your upgrade completed successfully, accept your upgrade using:

bcmsysupgrade -s:accept <device>

■

If the upgrade process failed to meet your veriﬁcation criteria, reject your

upgrade using:

bcmsysupgrade -s:reject <device>

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

Download from Www.Somanuals.com. All Manuals Search And Download.

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 i n step 2, upgrade the C E C ﬁ rmware by following these steps:

Make sure there is a ﬂoppy diskette with write access in the ﬂoppy drive on the

bridge/router. Make sure that the contents of the diskette you intend to use

can be overwritten. Perform a manually recoverable ﬁrmware upgrade using

the option -m if you do not want the ﬂoppy diskette formatted.

b Upgrade your ﬁrmware to version 2.6 using:

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

After the ﬁrmware 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

ﬁrmware for all these modules using:

bcmsysupgrade -s:upgrade_io_fw -m <device>

The bridge/router reboots after the ﬁrmware 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. S e e Chapter 3 for

the memory requirements for manual recovery.

Whenever you specify an option with bcmsysupgrade (such as -m), you must

repeat that opt i o n for a l l steps in the procedure. See T a b l e 4 o n 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 <device>

where [-options] lets you specify the -EncryptionLicenseRead ﬂag that indicates

you have read and understand the encryption license agreement notice and

<device> is the IP address or hostname of the bridge/router you are upgrading.

CAUTION: When upgrading to a package containing encryption, you must specify

the -EncyrptionLicenseRead option ﬂag. If you attempt to upgrade to an

encrypted package and you have not speciﬁed the -EncryptionLicenseRead option,

the upgrade will fail.

The bcmsysupgrade utility only backs up the ﬁles 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 conﬁguration ﬁles using:

bcmsysupgrade -s:update -m <device>

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

bcmsysupgrade -s:to_nb -m <device>

4 Accept your upgrade using:

bcmsysupgrade -s:accept -m <device>

Download from Www.Somanuals.com. All Manuals Search And Download.

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 veriﬁcation test can Ping to speciﬁc IP addresses.

Connectivity checks based on network topology.

Examples of a connectivity veriﬁcation 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 speciﬁc NETBuilder bridge/router.

■

Custom checks based on applications and typical network use.

For instance, you can check normal operation over the network and perform

ﬁle transfers, as well as run traces on speciﬁc routes or check routing tables.

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

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

ﬁrmware for all these modules using:

bcmsysupgrade -s:upgrade_io_fw -m <device>

The bridge/router reboots after the ﬁrmware is upgraded.

If the Bridge/Router or Sw itch 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 conﬁgure 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. S e e Chapter 7 for connect i vi t y and recovery procedures.

Upgrading Hardw are

and Softw are

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 “U p grad i n g S o ftware Only”

on page 41.

Automatic Recovery This section describes how to perform a software and hardware upgrade with

automatic recovery. S e e Chapter 3 for the memory requirements for automatic

recovery.

Whenever you specify an option with bcmsysupgrade (such as -new_hw), you

must repeat that opt i o n for a l l steps in the procedure. See T a b l e 4 o n page 40 or

Download from Www.Somanuals.com. All Manuals Search And Download.

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

where [-options] lets you specify the -EncryptionLicenseRead ﬂag that indicates

you have read and understand the encryption license agreement notice and

<device> is the IP address or hostname of the bridge/router you are upgrading.

CAUTION: When upgrading to a package containing encryption, you must specify

the -EncyrptionLicenseRead option ﬂag. If you attempt to upgrade to an

encrypted package and you have not speciﬁed the -EncryptionLicenseRead option,

the upgrade will fail.

The bcmsysupgrade utility only backs up the ﬁles 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 ﬁrmware 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 ﬁrmware before proceeding to the next step.

CAUTION: If you are running any other ﬁrmware version besides 2.0 or 2.1, you

should upgrade the ﬁrmware after upgrading the software.

To upgrade the CEC ﬁrmware, follow these steps:

Make sure there is a ﬂoppy diskette with write access in the ﬂoppy drive on the

bridge/router. Make sure that the contents of the diskette you intend to use

can be overwritten. Perform a manually recoverable ﬁrmware upgrade using

the option -m if you do not want the ﬂoppy diskette formatted.

b Upgrade your ﬁrmware to version 2.6 using:

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

After the ﬁrmware has been upgraded, the bridge/router reboots.

3 Update your conﬁguration ﬁles using:

bcmsysupgrade -s:update -new_hw <device>

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:

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.

Set up an IP address and subnet mask using:

SETDefault !<port> -IP NETaddr = <IP address> [<subnet mask>]

Download from Www.Somanuals.com. All Manuals Search And Download.

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

Where <port> is the port through which the bridge/router can be accessed by

the NMS.

d Enable IP routing by entering:

SETDefault -IP CONTrol = ROute

Enable a route discovery protocol. For example, enable OSPF by using:

SETDefault !<port> -OSPF CONTrol = Enable

Check your conﬁguration by pinging the bridge/router from the NMS:

ping <IP address>

Where <IP address> 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.

The COMmunity parameter modiﬁes 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 conﬁguration ﬁles are accessible to an SNMP-based

manager with read privileges. To change SNMP access to conﬁguration ﬁles 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 <device>

9 Test your new software using:

bcmsysupgrade -s:test_boot -new_hw <device>

The bridge/router is rebooted, and the utilities conﬁrm 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 veriﬁcation test can Ping to speciﬁc IP addresses.

Connectivity checks based on network topology.

Examples of a connectivity veriﬁcation include:

■

Checking the connectivity between devices on different networks, through

designated bridge/routers.

Download from Www.Somanuals.com. All Manuals Search And Download.

Upgrading Hardware and Software

■

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

Testing the connectivity with speciﬁc bridge/routers.

■

Custom checks based on applications and typical network use.

For instance, you can check normal operation over the network and perform

ﬁle transfers, as well as run traces on speciﬁc routes or check routing tables.

11 Accept or reject the upgrade.

■

If your software upgrade completed successfully, accept your upgrade using:

bcmsysupgrade -s:accept -new_hw <device>

■

If the upgrade process failed to meet your veriﬁcation criteria, reject your

upgrade using:

bcmsysupgrade -s:reject -new_hw <device>

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 i n step 2, upgrade the C E C ﬁ rmware by following these steps:

Make sure there is a ﬂoppy diskette with write access in the ﬂoppy drive on the

bridge/router. Make sure that the contents of the diskette you intend to use

can be overwritten. Perform a manually recoverable ﬁrmware upgrade using

the option -m if you do not want the ﬂoppy diskette formatted.

b Upgrade your ﬁrmware to version 2.6 using:

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

After the ﬁrmware 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

ﬁrmware for all these modules using:

bcmsysupgrade -s:upgrade_io_fw -m <device>

The bridge/router reboots after the ﬁrmware is upgraded.

Manual Recovery This section describes how to perform a software and hardware upgrade with

manual recovery. S e e Chapter 3 for the memory requirements for manual

recovery.

Whenever you specify an option with bcmsysupgrade (such as -m and -new_hw),

y o u must repeat that opt i o n for a l l steps in the procedure. See T a b l e 4 o n page 40

or “bcmsysupgrade” on page 81 for a l ist o f the opt i o ns a v a i l a b l e t o use w i t h 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 <device>

where [-options] lets you specify -EncryptionLicenseRead that indicates you have

read and understand the encryption license agreement notice and <device> is the

IP address or hostname of the bridge/router you are upgrading.

Download from Www.Somanuals.com. All Manuals Search And Download.

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 ﬂag. If you attempt to upgrade to an

encrypted package and you have not speciﬁed the -EncryptionLicenseRead option,

the upgrade will fail.

The bcmsysupgrade utility only backs up the ﬁles 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 conﬁguration ﬁles using:

bcmsysupgrade -s:update -m -new_hw <device>

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:

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.

Set up an IP address and subnet mask using:

SETDefault !<port> -IP NETaddr = <IP address> [<subnet mask>]

Where <port> is the port through which the bridge/router can be accessed by

the NMS.

d Enable IP routing by entering:

SETDefault -IP CONTrol = ROute

Enable a routing protocol. For example, enable RIP by using:

SETDefault !<port> -RIPIP CONTrol = (TAlk, LIsten)

Check your conﬁguration by verifying that the bridge/router is accessible by

using the following at the network management station:

PING <IP address>

<IP address> 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.

The COMmunity parameter modiﬁes 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 conﬁguration ﬁles are accessible to an SNMP-based manager

with read privileges. To change SNMP access to conﬁguration ﬁles 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

Download from Www.Somanuals.com. All Manuals Search And Download.

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

8 Accept your upgrade using:

bcmsysupgrade -s:accept -m -new_hw <device>

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 veriﬁcation test can Ping to speciﬁc IP addresses.

Connectivity checks based on network topology.

Examples of a connectivity veriﬁcation 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 speciﬁc NETBuilder bridge/routers.

■

Custom checks based on applications and typical network use.

For instance, you can check normal operation over the network and perform

ﬁle transfers, as well as run traces on speciﬁc routes or check routing tables.

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

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

ﬁrmware for all these modules using:

bcmsysupgrade -s:upgrade_io_fw -m <device>

The bridge/router reboots after the ﬁrmware is upgraded.

If the Bridge/Router or Sw itch 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 conﬁgure 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. S e e Chapter 7 for connect i vi t y and recovery procedures.

Download from Www.Somanuals.com. All Manuals Search And Download.

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

Download from Www.Somanuals.com. All Manuals Search And Download.

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 ﬁle but does not upgrade any

conﬁguration ﬁles. 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 conﬁguration ﬁles (for example,

10.1 to 10.3).

■

You are upgrading a PathBuilder S5xx series switch.

You can upgrade:

■

Using Upgrade Link

Usi n g the Command-L i n e U t i li t i e s

Usi n g the E n terpr i se OS User I n terface

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, conﬁrm the following items:

■

You have installed the utilities accord i n g 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 ﬁle to the .cshrc

ﬁle 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 ﬁle to the

.proﬁle ﬁle for each user you want to have access to the utilities, including

root:

/usr/3Com/common/data/.proﬁle-bcm

Or you can enter the path after every logon:

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 6: UPGRADING THE SOFTWARE IMAGE ONLY

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

■

All conﬁguration ﬁles 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 sufﬁcient 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 OfﬁceConnect

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

You can choose to transfer ﬁles using FTP or TFTP.

Setting up for TFTP File To use TFTP, you need to set up your NMS in preparation for TFTP ﬁle transfers.

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 ﬂag in all command line utilities which use ﬁle transfers

(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use TFTP ﬁle transfer. For

example, to specify TFTP ﬁle transfer use:

bcmsysupgrade -s:from_nb -tftp <device>

If neither ﬂag 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 ﬂag is

speciﬁed 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 To use FTP, you need to set up your NMS in preparation for FTP ﬁle transfers.

Transfers

For Upgrade Link, the user name and password is speciﬁed in the Setting Page, as

shown on page 23.

Download from Www.Somanuals.com. All Manuals Search And Download.

Using Upgrade Link

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 ﬂag in all command line utilities that use ﬁle transfers

(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use FTP ﬁle transfer. For

example, to specify FTP ﬁle transfer use:

bcmsysupgrade -s:from_nb -ftp <device>

If no ﬂag 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 ﬂag is

speciﬁed 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 ﬂag in the utilities (bcmsysupgrade, bcmbackup,

bcmrestore) if you want to use FTP ﬁle transfer.

If no ﬂag 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 ﬂag is

speciﬁed 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.

S e e Chapter 4 for i n format i o n on start i n g and us i n g the U p grade L i n k app l ic a t i o n.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 6: UPGRADING THE SOFTWARE IMAGE ONLY

Verifying the Before upgrading, run the diagnostic utility in Upgrade Link to verify connectivity

Bridge/Router for to the bridge/router by following these steps:

Upgrading

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.

Download from Www.Somanuals.com. All Manuals Search And Download.

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 “I n sta l li n g the U t i li t i e s on a N e twork

Management S t at i o n” 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 ﬂash

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.

Download from Www.Somanuals.com. All Manuals Search And Download.

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 OfﬁceConnect bridge/router to an OfﬁceConnect 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.

■

For manual recovery, you must conﬁgure 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 to exit Upgrade Link.

Download from Www.Somanuals.com. All Manuals Search And Download.

Using the Command-Line Utilities

Using the

Command-Line

Utilities

Use the command-line utilities within a script or execute the commands manually.

Otherw i se, use Upgrade L i n k as described on page 53.

Installing the NETBuilder You can upgrade from a CD-ROM, a tar ﬁle, or an image you have downloaded

Softw are from 3Com. If you are installing the software from a CD-ROM, complete the

procedure in “I n sta l li n g the S o ftware on the N MS” o n page 37.

You can choose to transfer ﬁles using FTP or TFTP. Complete the procedure in

“S e tt i n g U p a File T r ansfer Method” on page 17.

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

Problems

bcmdiagnose <device>

Where <device> is the IP address or hostname of the bridge/router you are

diagnosing.

Upgrading Using To perform an image-only upgrade using automatic recovery, follow these steps.

Automatic Recovery S e e 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:<software version> <device>

where [-options] lets you specify the EncryptionLicenseRead option that indicates

you have read and understand the encryption license agreement notice and

<device> 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 ﬂag. If you attempt to upgrade to an

encrypted package and you have not speciﬁed the -EncryptionLicenseRead option,

the upgrade will fail.

2 Copy the conﬁguration ﬁles into the new software directory on the NMS using:

bcmsysupgrade -s:update -I -V:<software version> <device>

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

bcmsysupgrade -s:to_nb -I -V:<software version> <device>

4 Test your new software using:

bcmsysupgrade -s:test_boot -I -V:<software version> <device>

The bridge/router is rebooted, and the utilities conﬁrm 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 veriﬁcation test can Ping to speciﬁc IP addresses.

Connectivity checks based on network topology.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 6: UPGRADING THE SOFTWARE IMAGE ONLY

Examples of a connectivity veriﬁcation 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 speciﬁc bridge/routers or switches.

■

Custom checks based on applications and typical network use.

For instance, you can check normal operation over the network and perform

ﬁle transfers, as well as run traces on speciﬁc routes or check routing tables.

6 Accept or reject the upgrade.

■

If your software upgrade completed successfully, accept your upgrade using:

bcmsysupgrade -s:accept -I -V:<software version> <device>

■

If the upgrade process failed to meet your veriﬁcation criteria, reject your

upgrade using:

bcmsysupgrade -s:reject -I -V:<software version> <device>

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

Upgrading Using To perform an image-only upgrade using manual recovery, follow these steps. See

Manual Recovery 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:<software version> <device>

where [-options] lets you specify the EncryptionLicenseRead option that indicates

you have read and understand the encryption license agreement notice and

<device> is the IP address or hostname of the bridge/router you are upgrading.

CAUTION: When upgrading to a package containing encryption, you must specify

the -EncyrptionLicenseRead option ﬂag. If you attempt to upgrade to an

encrypted package and you have not speciﬁed the -EncryptionLicenseRead option,

the upgrade will fail.

2 Copy the conﬁguration ﬁles into the new software directory on the NMS using:

bcmsysupgrade -s:update -m -I -V:<software version> <device>

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

bcmsysupgrade -s:to_nb -m -I -V:<software version> <device>

4 Accept the upgrade using:

bcmsysupgrade -s:accept -I -m -V:<software version> <device>

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 veriﬁcation test can Ping to speciﬁc IP addresses.

Download from Www.Somanuals.com. All Manuals Search And Download.

Using the Enterprise OS User Interface

■

Connectivity checks based on network topology.

Examples of a connectivity veriﬁcation 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 speciﬁc bridge/routers or switches.

■

Custom checks based on applications and typical network use.

For instance, you can check normal operation over the network and perform

ﬁle transfers, as well as run traces on speciﬁc routes or check routing tables.

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

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 [<device>:]<path>

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 ﬁles, change the name of the current boot image using:

ReName <image name> <new name>

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 <image name> <IP address of server>:<path/>

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

RemoveFile <image name>

6 Copy the new boot ﬁle from the FTP/TFTP server to the current (primary boot)

directory using:

COpy <IP address of server>:<path/><image name>

For example:

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

Download from Www.Somanuals.com. All Manuals Search And Download.

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 ﬁle using:

BT /<path>/<old name>

For example:

BT /primary/oldboot

Download from Www.Somanuals.com. All Manuals Search And Download.

BACKING UP AND RESTORING

SOFTWARE

You should always back up your software and conﬁguration ﬁles 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

Conﬁrm the following items:

■

You have installed the utilities accord i n g 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 ﬁle to the .cshrc

ﬁle 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 ﬁle to the

.proﬁle ﬁle for each user you want to have access to the utilities, including

root:

/usr/3Com/common/data/.proﬁle-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 ﬂash memory drives A and B, but the

NETBuilder Upgrade Management Utilities only support drive A. Use the

bcmconﬁg 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 conﬁguration ﬁles 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).

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 7: BACKING UP AND RESTORING SOFTWARE

Setting Up a File

Transfer Method

You can choose to transfer ﬁles using FTP or TFTP.

Setting Up for TFTP File To use TFTP, you need to set up your NMS in preparation for TFTP ﬁle transfers.

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 ﬂag in all command line utilities which use ﬁle transfers

(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use TFTP ﬁle transfer. For

example, to specify TFTP ﬁle transfer use:

bcmsysupgrade -s:from_nb -tftp <device>

If neither ﬂag 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 ﬂag is

speciﬁed 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 To use FTP, you need to set up your NMS in preparation for FTP ﬁle transfers.

Transfers

For Upgrade Link, the user name and password is speciﬁed 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 ﬂag in all command line utilities that use ﬁle transfers

(bcmsysupgrade, bcmbackup, bcmrestore) if you want to use FTP ﬁle transfer. For

example, to specify FTP ﬁle transfer use:

bcmsysupgrade -s:from_nb -ftp <device>

If no ﬂag 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 ﬂag is

speciﬁed on a NETBuilder bridge/router running software version 11.0 or lower,

the FTP password is overwritten with the following text string:

****

Download from Www.Somanuals.com. All Manuals Search And Download.

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 ﬂag in the utilities (bcmsysupgrade, bcmbackup,

bcmrestore) if you want to use FTP ﬁle transfer.

If no ﬂag 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 ﬂag is

speciﬁed 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

Softw are

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

Using NETBuilder Upgrade Link is an easy to use GUI for the utilities that runs in a web browser. See

Upgrade Link Chapter 4 for i n format i o n on runn i n g U p grade L i n k l o ca l ly o r remotely. Make sure

you select and set up your ﬁle transfer method.

Using the Command You can use the command-line utilities if you want to write scripts or if you do not

Line Utilities have a web browser on y o ur N MS. S e e “U p grad i n g a B r idge/R o uter U si n g the

Command-L i n e U t i li t i e s”on page 63 for i n format i o n on us i n g the command-l i n e

utilities. Make sure you select and set up your ﬁle transfer method.

Verifying the Device for Before backing up, run the diagnostic utility in Upgrade Link to verify connectivity

Backing Up 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.

Download from Www.Somanuals.com. All Manuals Search And Download.

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 ﬁle transfer permissions.

If the Status window shows a success, click Home to continue with the backup.

Backing Up the Softw are

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 Use the command-line utilities if you have a script or if you do not have a web

Command-Line browser. Otherw i se, use Upgrade L i n k as described on page 63.

Prediagnosing System Problems

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

bcmdiagnose [-ftp | -tftp] [<device> | -h]

Where <device> is the IP address or hostname of the bridge/router or switch you

are diagnosing.

Download from Www.Somanuals.com. All Manuals Search And Download.

Backing Up the Software

If bcmdiagnose shows a failure, check the SNMP read/write community string for

FTP/TFTP ﬁle transfer permissions.

Backing Up the Softw are

To back up your software to an NMS, use:

bcmbackup [both | primary | secondary] [-name:<backname>]<device>]

Values

both

Backs up both the primary and secondary boot source. This

value is the default.

primary

Backs up the primary boot source.

Backs up the secondary boot source.

secondary

<backname> Speciﬁes the name of the backup for the boot blocks.

<device> The IP address or hostname of the bridge/router.

Directory Paths All backups and upgrades use the following directory paths.

For UNIX:

/tftpboot/CLIENTS/<mac_address>/bcm/<backname><directory name on

bridge/router>/

For example:

/tftpboot/CLIENTS/0800020A399E/bcm/name/primary/

For Window s:

\%tftpboot%\CLIENTS\<mac_address>\bcm\<backname>\<directory name on

bridge/router>\

For example:

\tftpboot\CLIENTS\0800020A399E\bcm\name\primary\

Values

tftpboot

For UNIX: Directory speciﬁed in inetd or tftpd for tftpd ﬁles.

% tftpboot%

For Windows (using the default 3Com TFTP server): Directory

speciﬁed in the Win.ini ﬁle in the “[3Com.nm] TFTPROOT=”

section. The Win.ini ﬁle is located in the default Windows

directory, for example C:\windows or C:\winnt4.

CLIENTS

Name of the directory.

<mac_ address>

The MAC address of the bridge/router or switch.

The name of the boot directory on the bridge/router or

<directory name

on bridge/router> 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”.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 7: BACKING UP AND RESTORING SOFTWARE

Restoring Softw are

from a Backup

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 conﬁguration, you must ﬁrst

reconﬁgure IP and SNMP on the bridge/router. If you still have connectivity, go to

“R e storing the Software Using Upgrade L i n k” on page 68 or “R e storing the

S o ftware Using the Command-L i n e” on page 69.

Conﬁguring IP Routing 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 !<port> -IP NETaddr = <IP address> [<subnet mask>]

For more information on IP conﬁguration, 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 !<port> -OSPF CONTrol = Enable

7 Ensure your conﬁguration by verifying that the bridge/router is accessible from the

NMS using:

PING <IP address>

Where <IP address> is the IP address of the bridge/router.

Conﬁguring 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 modiﬁes 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 conﬁguration ﬁles are accessible to an SNMP-based

manager with read privileges. To change SNMP access to conﬁguration ﬁles to

read/write for a network management station with a community named “public,”

enter:

ADD -SNMP COMmunity “public” RW

Download from Www.Somanuals.com. All Manuals Search And Download.

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 conﬁgure a mapping between hostnames and/or IP

addresses and SNMP community strings. If the NETBuilder bridge/routeris

conﬁgured to accept a community string other than "public", you need to update

this ﬁle with the new community string. Follow the examples in the ﬁle when

adding your own entries.

The following is an example ﬁle 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

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 7: BACKING UP AND RESTORING SOFTWARE

Restoring the Softw are Upgrade Link is an easy to use GUI for the utilities that runs in a web browser.

Using Upgrade Link

Upgrade Link is an easy to use GUI for the utilities that runs in a web browser. See

Chapter 4 for i n format i o n on runn i n g U p grade L i n k l o ca l ly o r remotely. Make sure

you select and set up your ﬁle 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 ﬁle transfer permissions.

If the Status window shows a success, click Home to continue with the

restoration.

Restoring the Softw are

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.

Download from Www.Somanuals.com. All Manuals Search And Download.

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 ﬂash 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 Softw are Use the command-line utilities if you have a script or if you do not have a web

Using the browser. Otherw i se, use Upgrade L i n k as described on page 68.

Command-Line

Prediagnosing System Problems

Detect any problems with SNMP or TFTP connectivity using:

bcmdiagnose [ -ftp | -tftp] [<device> | -h]

Where <device> 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 ﬁle transfer permissions.

Restoring the Softw are

If you are replacing the hardware, restore the software using:

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 7: BACKING UP AND RESTORING SOFTWARE

bcmrestore -new_hw [ -<backname>] <device>

If you are not replacing the hardware, use:

bcmrestore [ -<backname>] <device>

Where <backname> is the name of the backup for the boot blocks.

Download from Www.Somanuals.com. All Manuals Search And Download.

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

Dow nloading the

Utilities

The Upgrade Management Utilities are provided on CD-ROM with every

Enterprise OS software package. S e e Chapter 2 to i n sta l l t he ut i li t i e s from

CD-ROM.

The upgrade utilities are installed into the directory /usr/3Com/bcm/.

Dow nloading the You can download the latest utilities from the following locations:

Utilities

■

FTP — ftp.3Com.com

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

3Com Bulletin Board S e rvice (3Com B BS) — S e e A p pend i x D for local B BS

numbers.

See the ruu112.txt ﬁle accompanying the utilities for instructions on

decompression and installation of the utilities.

Dow nloading UNIX Files

The UNIX ﬁles compressed with the UNIX compress utility. To use the downloaded

ﬁles, you must ﬁrst expand the ﬁles using the UNIX decompress utility. For

instructions on how to download and decompress the utilities, see the

ruu111.txt ﬁle.

The following are the UNIX ﬁles:

ruusol113.Z

ruuhp113.Z

ruuaix113.Z

ruu112.txt

Contains the utilities for Solaris 2.x.

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

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

Contains the instructions for downloading and decompressing

the utilities.

Dow nloading Window s Files

The Windows ﬁles are compressed with a compression utility. To use the

downloaded ﬁles, you must ﬁrst expand them using the decompress utility

PKUNZip. PKUNZip can be downloaded from the following URLs:

■ http://www.pkware.com/

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

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES

For instructions on how to decompress and install the utilities, see the

ruu110.txt ﬁle.

The following are the Windows ﬁles:

ruu113.zip

ruu113.txt

Contains the utilities for Windows95, Window98, and

Windows NT 4.0.

Contains the instructions for downloading and decompressing

the utilities.

Update Log File

The bcmsysupgrade utility creates log ﬁles in the

tftpboot/CLIENTS/<mac_address>/tmp directory. These log ﬁles include the

following:

■

bcmsysupgrade.log.<stage> — 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 ﬁle acts as an upgrade record of completed stages, and includes the date

and time of execution.

■

bcmupdate.log — contains a list of the conﬁguration ﬁles converted during

the upgrade process. The ﬁle contains all stderr and stdout text, the log and

stage ﬁles. This ﬁle is appended to the bcmsysupgrade.log ﬁle when the

upgrade procedure is completed.

Utility Descriptions

and Syntax

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.

Overview

T a b l e 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

bcmctrl

Manages the bridge/router boot source parameters.

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.

bcmd i a gnose

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.

bcm i n sta l l

Installs bridge/router software and firmware on a network management

station.

bcm l o adconf i g

(continued)

Allows you to execute commands in a text file.

Download from Www.Somanuals.com. All Manuals Search And Download.

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

bcmupdate

Displays general information about the bridge/router.

Converts configuration files on the network management station for use with

a newer version of software.

U p grade L i n k

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 speciﬁc utility, use:

man <NMU_name>

where <NMU_name> 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 speciﬁc utility, use:

/usr/3Com/bcm/gui/hlp/<utility>.html

bcmbackup

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

Description You can use this utility to prepare a network management station as a secondary

boot source, to archive the conﬁguration as a backup copy, to obtain a baseline

conﬁguration, or to perform an off-line conﬁguration. 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.

Download from Www.Somanuals.com. All Manuals Search And Download.

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> Speciﬁes the ﬁle transfer protocol to be used in the backup

process.

<backname> Speciﬁes the name to be given to the backup ﬁle 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

bcmconﬁg

Syntax bcmconfig <device>[:<slot>] [<boot_source>] [options]

Description The bcmconﬁg utility performs EEPROM conﬁguration of the device and retrieves

or sets the following parameters for each boot source:

■

Path and name for load image

■

Path and name for conﬁguration ﬁles

The bcmconﬁg 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:

■

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

■

Inconsistency with other conﬁgurations in other blocks (such as subnet masks).

Values

<slot>

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

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

with *.)

<boot_source> Designates type of boot source: master, primary, secondary, test,

dump, or all.

Options Where <boot source> is master, the [options] are:

-st[artup (once

forever

Attempts to boot once.

Attempts to boot forever.

Forces boot from local media.

local)

Download from Www.Somanuals.com. All Manuals Search And Download.

Utility Descriptions and Syntax

Where <boot source> is primary, secondary, test, or dump, the [options] are:

-conﬁgp[ath]:<ﬁle_path>

-ﬁ[le]:<ﬁle_name>*

Path to the conﬁguration ﬁles.

Name of boot ﬁle.

-bo[otdevice]:

(network

localA

Boots from network.

Boots from local media A.

Boots from local media B.

Depends on -bootdevice.

Local media conﬁguration.

Network conﬁguration.

localB)

-conﬁgd[evice]: (bootdevice

local

network)

-fo[rmat]:(canonical | noncanonical) Address format.

-cl[ock]:(internal | external)

-conn[ector]:(v35 | rs232)

-ba[udrate]:

Internal/external clocking.

Connector type.

<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]:<wan_password>

A character string from 0–5 characters.

-di[scovery]:(<localaddr> | <bootp>) Address discovery.

-ga[teway]:<IPADDRESS>

-lo[calip]:<IPADDRESS>

-se[rver]:<IPADDRESS>

-cf[gserver]:<IPADDRESS>

-ma[sk]:<IPADDRESS>

-notraps

Default gateway IP address.

Bridge/router IP address.

TFTP boot server IP address.

Server where conﬁguration ﬁles are stored.

Bridge/router subnet mask.

Disables the sending of SNMP traps useful

during upgrading.

-re[tries]:0..255

-traps

Number of retries from 0–255.

Enables the sending of SNMP traps; useful

after upgrade completes.

bcmctrl

Syntax bcmctrl <device>[:<slot>] [-<option>[:<value>]]

Description The bcmctrl utility does the following tasks:

■

Reboots a bridge/router. This follows a normal boot sequence, where the load

image and conﬁguration ﬁles are found in the primary boot source.

■

Performs a test reboot.

Copies all the parameters in the test boot source to the primary boot source.

Reports reboot and ﬁle transfer states.

Reboots a speciﬁed multiprocessor module.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES

Values

<device> Identiﬁes the bridge/router that receives the changes speciﬁed by the

bcmctrl utility.

<slot>

Speciﬁes the slot where the I/O module is located that receives the

changes speciﬁed by the bcmctrl utility.

Options

-u[pdate]

Copies the complete set of boot parameters from the test boot

source to the primary boot source.This operation is typically

performed after a successful test reboot to ensure that the next

normal reboot uses the same parameters.

-s[wap]

Swaps the parameters in the primary and secondary boot sources.

-c[ommit]

Cancels the test reboot countdown timer. This stops the automatic

test reboot begun by the test reboot parameter.

-r[eboot]*

Reboots the bridge/router or switch or the I/O module speciﬁed by

the <slot> parameter.

-t[estreboot]: Reboots the bridge/router or switch from the test boot source so

[<seconds>]* that if this command is not used again with the -c option, the

bridge/router automatically reboots with its primary conﬁguration.

The optional seconds parameter indicates the length of time in

seconds the bridge/router should count down before automatically

rebooting. If you do not supply a value for <seconds>, the default

value of 120 seconds is used.

-q:r[eboot]

Queries the reboot status of the bridge/router or switch or I/O

module speciﬁed by the <slot> parameter.

-q:t[ransfer]

-w:r[eboot]

Queries the transfer status of the bridge/router or switch.

Waits for the bridge/router or switch to reboot.

-w:t[ransfer] Waits for the last requested transfer to complete.

The options marked with an asterisk will reboot the bridge/router or individual

modules.

bcmdf

Syntax bcmdf <device>[:<drive:>]

Description The bcmdf utility displays the amount of total and available disk space.

Values

<drive:>

The hostname or the IP address of the bridge/router or

switch.

The device drive that holds the disk for which the amount of

total and available disk space will be counted and displayed.

Options No available options

Download from Www.Somanuals.com. All Manuals Search And Download.

Utility Descriptions and Syntax

bcmdiagnose

Syntax bcmdiagnose [ -ftp | -tftp ] [<device>] [-h]

Description The bcmdiagnose utility identiﬁes the most common installation and conﬁguration

problems. 3Com recommends that this utility be run immediately following

bcmsetup and before running any other upgrade management utility. The

bcmdiagnose utility validates that the upgrade management installation process

went as expected, and tests that the bridge/router or switch and network

management station are conﬁgured correctly. The bcmdiagnose utility validates

that:

■

The upgrade utilities are installed correctly on the NMS.

The bridge/router or switch is reachable over IP.

The bridge/router SNMP Service is correctly conﬁgured.

The TFTP server and ﬁle permissions are correctly conﬁgured.

The boot images and the conﬁguration ﬁles are in the same directory on

drive A.

■

The software is compatible with the ﬁrmware (NETBuilder II bridge/router with

CEC only).

When FTP is speciﬁed for ﬁle transfer, the FTP user name and password must

be correctly conﬁgured by setting the BCMFTPUSER and BCMFTPPASS

environment variables.

The bcmdiagnose utility displays troubleshooting messages and has two error

return codes:

■

0 for success

1 for failure

■

Values

<device> Indicates the hostname or the IP address of the bridge/router or switch.

If bcmdiagnose is invoked without the bridge/router IP address or host

name, only the installation tests of the Enterprise OS Upgrade

Management Utilities is executed. If the device is speciﬁed, the

installation test is skipped, but the utility performs the IP, SNMP, and

TFTP server conﬁguration tests.

Options

-ftp

-tftp

[-h]

Speciﬁes FTP as the ﬁle transfer protocol to be used. FTP is the

default protocol for Enterprise OS software versions 11.1 and

higher.

Speciﬁes TFTP as the ﬁle transfer protocol to be used. TFTP is the

default protocol for Enterprise OS software versions 11.0 and

lower.

Displays help message.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES

bcminstall

<path> | <device>]

Description The bcminstall utility installs bridge/router software and ﬁrmware onto a network

management station from either a CD-ROM, tar ﬁles, an image ﬁle, a

bridge/router, or a network management station ﬂoppy diskette. You must install

all applicable Enterprise OS software packages before beginning the upgrade

process. On a UNIX system, you must have superuser privileges to run the

bcminstall utility.

The default method of installing a Enterprise OS package is to install it from a

CD-ROM drive on the network management station. The bcminstall utility copies

the ﬁles on the CD-ROM into a directory under /% tftpboot% /image. Using the

path option allows installation from a network management station that has two

or more CD-ROM drives, or from a remote CD-ROM drive. On a UNIX system, you

must specify the path if you are installing from a CD-ROM that is not cdrom0. For

example, to install a Enterprise OS software package from a second CD-ROM on

Solaris, enter:

bcminstall -cdrom /cdrom/cdrom1/image

The following example shows how to install a boot image for an image-only

upgrade from the directory /tmp/:

bcminstall -image /tmp/boot.68k

Options

-h

Displays a usage message. Installs using the ﬁrst CD-ROM on

the network management station.

-cdrom [<path>] Installs using the CD-ROM from a directory path. Required for

Windows.

-tar <path>

-r

Installs a tarred package ﬁle.

Reports all installed bridge/router packages on the network

management station.

-diskette

Installs from the network management station ﬂoppy drive

(version 9.1 and earlier).

-image <path>

Installs an image ﬁle (for image-only upgrades only).

The IP address of the bridge/router from which the

over-the-network installation occurs.

Default If no command line options are speciﬁed, the bcminstall utility uses the network

management station local CD-ROM drive.

Download from Www.Somanuals.com. All Manuals Search And Download.

Utility Descriptions and Syntax

bcmloadconﬁg

Syntax bcmloadconfig [-s “<service1> [<service2>...]” | -l <line number>] [-i] -f

<config file path>/<filename> <device> [-b] [-t:<reboot timeout>]

Description You can execute multiple commands on the Enterprise OS user interface at once

by entering the commands in a text ﬁle, then loading the ﬁle. The bcmloadconﬁg

utility copies a speciﬁed conﬁguration ﬁle to the bridge/router or switch and

executes the commands in the ﬁle.

The utility can execute only the SETDefault, SHow, SHowDefault, ADD, DELete,

and SAVEbgp commands. Blank lines and comment lines (lines beginning with the

# character) are allowed in the ﬁle. If the command requires more than one line,

the backslash (\) can be used to terminate the current line and to indicate that the

command continues on the next line. A line cannot contain more than one

command.

If you specify one or more services, only the commands belonging to those

services are executed. Up to 10 services can be speciﬁed. Instead of specifying a

service, you can specify a line number to indicate the starting line number within

the ﬁle to execute.

By default, the bcmloadconﬁg utility terminates whenever it detects a bad

command, a command that is not supported by the bcmloadconﬁg utility, or a

command that fails to execute successfully on the bridge/router. If -i is speciﬁed,

the utility continues execution when an error is encountered.

All commands and comments and any generated messages are written to the

CONFIG.LOG ﬁle in the /tftpboot/CLIENTS/<MAC address>/cfg/ directory on the

NMS. Any passwords speciﬁed in the commands are replaced by a string of

asterisks. Skipped commands are not written to the CONFIG.LOG ﬁle.

Values

-s “<service1> [<service2>...]”

Only commands found for these services are

executed. Up to 10 services may be speciﬁed.

The default is to execute the conﬁguration

commands for all services.

-l <line number>

The Line in the conﬁguration ﬁle to be

executed. Comments and blank lines are

considered lines in the ﬁle.

-s and -l are mutually exclusive.

-i

Continue executing commands even when

errors are detected.

-f <conﬁg ﬁle path>

The directory containing the command ﬁle that

is to be executed. The default path is the

current working directory.

<ﬁlename>

The name of the command ﬁle that is to be

executed. There is no default ﬁlename. This

parameter is required.

The IP address or hostname of the

bridge/router that will execute the commands.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES

-b

Speciﬁes that after the conﬁguration ﬁle is

copied to the bridge/router or switch a bcmctrl

-reboot is executed.

-t:<reboot timeout>

Speciﬁes a reboot time out period. If the device

does not boot within the reboot timeout

period (default: 600 seconds ) bcmloadconﬁg

returns an error.

bcmnbrus

Syntax bcmnbrus <port> [-NoSecurity] [-NoAuthentication]

Description The bcmnbrus utility launches the Upgrade Link application backend process.

Values

<port>

Speciﬁes the TCP socket on which the client communicates with

the server. On UNIX systems you can add this command to cron

and on Windows 95/98/NT systems this command can be running

as a service.

Options

-NoSecurity

Indicates that the bcmnbrus utility will allow connections from all

IP addresses.

-NoAuthentica Speciﬁes that bcmnbrus will not prompt for a user name and

tion password.

bcmrestore

Syntax bcmrestore [both | primary | secondary] [options] <device>

Description The bcmrestore utility restores the Enterprise OS software from a backup on the

network management station to the bridge/router or switch. The software,

including the image and conﬁguration ﬁles, is copied to the bridge/router, and the

primary boot source is set to the restored directory.

Values

both

Restores both the primary and secondary boot sources. This value

is the default.

primary

Restores the primary boot source.

Restores the secondary boot source.

secondary

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

switch.

Options

-ftp | -tftp

Speciﬁes the ﬁle transfer protocol to be used in the restore

process.

-NoF[ormat]

-NoR[eboot]

-U[naccept]

Does not format the drive before restore.

Does not reboot when restoration is complete.

Rejects a previously accepted automatically recoverable upgrade

by swapping the primary and test boot sources.

Download from Www.Somanuals.com. All Manuals Search And Download.

Utility Descriptions and Syntax

-new_hw

Used to restore software to a new bridge/router or switch. Use

this option when a failed bridge/router or switch is exchanged for

a new one. After IP and SNMP connectivity is established, use this

option to copy the original software to the new bridge/router or

switch.

bcmsetup

Syntax For UNIX:

bcmsetup <packages> [install_directory]

For Windows:

bcmsetup <drive:> [all | bcm | nat]

Description The bcmsetup utility places the latest version of the Enterprise OS Upgrade

Management Utilities on the network managment station. It also sets up the initial

package deﬁnitions for use by Transcend. You must be root to run the bcmsetup

utility.

Values

all

Installs both the utilities and package deﬁnitions (bcm and

nat).

bcm

nat

Enterprise OS Upgrade Management Utilities.

Package deﬁnitions for use by Transcend.

Options

[Install_directory] Deﬁnes the directory where the utilities and other ﬁles set up

UNIX only with bcmsetup are to be located.

Default For UNIX, unless an alternate installation directory is speciﬁed, the utilities are

installed in the /usr/3Com/bcm directory.

For Windows, the utilities are always installed in \usr\3Com\bcm.

<drive:>

Identiﬁes the target drive where the utilities and other ﬁles set

up with bcmsetup are to be located.

bcmsysupgrade

Syntax bcmsysupgrade [options] <stage> <device>

Description The bcmsysupgrade utility is a master script that assists you in upgrading a

bridge/router to the latest version of software and/or ﬁrmware. The

bcmsysupgrade utility uses many of the other Enterprise OS Upgrade Utilities to

perform a complete upgrade of a bridge/router over the network.

Values

<stage>

-s:from_nb

-s:update

Downloads conﬁguration ﬁles from the bridge/router.

Upgrades conﬁguration ﬁles on the network

management station.

-s:to_nb

Uploads conﬁguration and image ﬁles to the

bridge/router.

-s:test_boot *

Test boots the upgraded conﬁguration.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES

-s:accept*

-s:reject*

Accepts the upgrade (cannot be used with -s:reject

stage).

Rejects the upgrade (cannot be used with -s:accept

stage).

-s:upgrade_cec_fw* Upgrades the NETBuilder II CEC ﬁrmware.

-s:upgrade_io_fw* Upgrades the I/O ﬁrmware.

Speciﬁes the IP address or hostname of the target

bridge/router.

Stages with an asterisk may reboot the bridge/router. The -s:accept stage only

reboots manual and patch upgrades.

Options

-EncryptionLicenseRead Speciﬁes that the encryption license agreement has

been read and accepted. This ﬂag must be used when

upgrading to any package with encryption.

-ftp | -tftp

Speciﬁes the ﬁle transfer protocol to be used in the

backup process. The default is FTP for bridge/routers

running Enterprise OS software version 11.1 or above.

The default is TFTP for bridge/routers running

Enterprise OS software version 11.0 or lower.

-d

-f

Runs bcmdiagnose utlility ﬁrst.

Forces action, and ignores warnings. Use with extreme

caution!

-I

Upgrades boot image only. The default is images and

conﬁgurations.

-k:<package>

Package type to upgrade to. For <package>, use the

two-letter designator printed on the CD-ROM. The

default is to use the package being upgraded from.

-m

Speciﬁes a manually recoverable upgrade. The default

is automatic recovery.

-t

Timeout value in seconds (defaults to 600, the range is

480 to 720 seconds).

-new_hw

Indicates the replacement with like hardware.

(Examples, CEC with DPE, OCNB with OCNB)

-V:<version upgrading

to>

When upgrading to a software version other than the

default, you must enter the software version you are

upgrading to. The default version is the same as the

version of the upgrade software. Run “bcmdiagnose”

to determine the version.

bcmuname

Syntax bcmuname [options] <device>[:<slot> | <drive>]

Download from Www.Somanuals.com. All Manuals Search And Download.

Utility Descriptions and Syntax

Description The bcmuname utility displays system information about the speciﬁed

bridge/router or switch or Intelligent I/O module (IIO). If no options are speciﬁed,

all the device-level options are printed.

Values

<slot>

Speciﬁes either the hostname or the IP address of the

bridge/router.

Speciﬁes slot of an I/O module within the bridge/router. This

parameter is optional and is used only with the options

marked with (IIO).

<drive>

Speciﬁes the storage device (usually a ﬂash drive) attached to

a bridge/router. This parameter is optional. When you specify

letters A: or B: they are assumed to be drive letters, any

numeric character is assumed to be a slot designator.

Options

-2

-a

Prints the @m mac address (used in bcmcp) (IIO).

Prints the @M mac address (used in bcmcp) (IIO).

Prints all the above information (IIO).

-c

Prints the contact information.

-d

Prints the tftp directory that will be used by bcmcp.

-f:<sys_ﬁlename> Displays system information based on the contents of the

speciﬁed <path>/sys ﬁle.

-l

-M

-m

-n

-r

Prints the machine location.

Prints the memory type.

Prints the machine platform name (IIO).

Prints the node name.

Prints the software release (IIO).

Prints the major software release.

Prints the software system name.

Prints the software or ﬁrmware type.

Prints the ﬁrmware release.

-R

-s

-t

-w

If an option is required, it must be speciﬁed in very stage of the upgrade process.

bcmupdate

Syntax bcmupdate -f:<from_path> -t:<to_path> [options]

Description The bcmupdate utility converts the bridge/router or switch conﬁguration ﬁles that

work with an older version of software to ﬁles that work with the newer version of

software. 3Com recommends that this utility only be invoked with the

bcmsysupgrade utility script.

Values

-f:<path>

-t:<path>

Path to upgrade from.

Path to upgrade to.

Options

-v:<version>

Version to upgrade from.

Download from Www.Somanuals.com. All Manuals Search And Download.

CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES

-V:<version>

Version to upgrade to.

-p:<platform>

Bridge/router platform type.

Saves user macros.

-m

-n

Prints trace messages.

When using the bcmupdate option on a Windows95, Windows98, or

Windows NT version 4.0 system, the following ﬁles are copied but not converted

or changed:

bgp

bgpnet

dir

bgpol

bgppeer

dua

smt

bgpas

egp

iineighb

iistuff

user

ipns

area

systemna

name

iicurcui

NatMap

The ﬁlenames are numbers in the es directory, and the text ﬁles are located in the

ﬁlter directory.

UpgradeLink

Syntax UpgradeLink [-NoSecurity | -NoAuthentication]

Description The Upgrade Link utility runs the Upgrade Link application and launches your

default web browser. On Windows, it launches the 3Com TFTP server that is

installed with the utilities.

Upgrade Link is an easy to use GUI for upgrading, backing up, or restoring

software on a single bridge/router.

Options

-NoSecurity

Indicates that the bcmnbrus utility will allow connections

from all IP addresses.

-NoAuthentication Speciﬁes that bcmnbrus will not prompt for a user name

and password.

Download from Www.Somanuals.com. All Manuals Search And Download.

TROUBLESHOOTING

This appendix describes error codes and messages that may be displayed during

the upgrade process as a result of running the bcmdiagnose utility or when

network dependencies have not been met.

Getting Help

For UNIX, to obtain help information about a utility, use:

<utility> -h

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 speciﬁc utility, use:

man <NMU_name>

where <NMU_name> 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 speciﬁc utility, use:

/usr/3Com/bcm/gui/hlp/<NMU_name>.html

For more information about using the Enterprise OS Upgrade Management

U t i li t i e s, see Chapter 8.

General

Troubleshooting Error

Messages

The master boot block startup value is set to monitor. This is not a

supported value.

Meaning: The master boot block startup value is set to monitor.

Action:

Make sure that your bcmconﬁg <ipaddr> master -startup value is set

to try boot once or try forever.

The primary boot block must access the boot ﬁle locally. That is, all ﬁles

must physically reside on the NETBuilder.

Meaning: The primary boot source is set to boot from the network.

Action:

Set the primary boot source to local. Make sure the bcmconﬁg

<ipaddr> primary -bootdevice value is set to either localA or localB.

Download from Www.Somanuals.com. All Manuals Search And Download.

APPENDIX A: TROUBLESHOOTING

The required ﬁle(s) <ipaddress>:<drive>:/<conﬁg ﬁle path> could not be

located.

Meaning: The bcmtest utility was unable to verify the presence of a ﬁle or

directory.

Action:

Make sure that the required ﬁles and directories are available to the

bcmtest utility.

Return Codes from

bcmdiagnose

The bcmdiagnose utility can display the following exit return codes:

Table 6 bcmdiagnose Return Codes

Code Meaning

The operation was successful.

A command line parsing error occurred.

A command line argument is invalid.

A installation error occurred.

A Enterprise OS Upgrade Management utility failed.

The device is not responding.

Internal parsing error.

A UNIX command failed.

The device conﬁguration is incompatible with the operation.

The attempted operation is unsafe.

No arguments in a function call.

No sys ﬁle was found.

The boot image was not found.

The boot image is bad.

The module upgrade failed.

The module failed to reboot.

The boot image is not set.

Missing device address (DNS name or IP address).

The Enterprise OS software is not installed.

Error installing a Enterprise OS SW or FW package.

An error occurred during a UNIX ﬁle copy.

Enterprise OS software installation not performed.

Failed to perform a software upgrade.

Failed to perform ﬁrmware upgrade.

Test-Boot and/or reboot timed-out.

The Upgrade of the device and image is not supported.

A critical ﬁle was missing or corrupted in a ﬁle transfer.

Download from Www.Somanuals.com. All Manuals Search And Download.

Hardware-Related Messages

Hardw are-Related

Messages

The XX package must have 20 MB of memory installed on the CEC or DPE

module. There is only 12 MB available.

Meaning: The bcmsysupgrade utility cannot continue because it does not detect

a CEC 20 or DPE in the system. The software package requires a

CEC 20 or DPE module.

Action:

If you have a CEC 20 module, run the Memory Expansion Board utility

supplied with the memory upgrade by putting the diskette in the

ﬂoppy drive and entering bt memupgrd.29k. The program updates

the EPROM.

The hardw are conﬁguration of this NETBuilder could not be conﬁrmed.

Meaning: Your hardware may not support the software package you are

upgrading to. The bcmsysupgrade script allows the upgrade to

proceed even if the hardware conﬁguration is not recommended.

Action:

Ensure that the bridge/router meets the hardware requirements for

the package you are upgrading to, and that it is on the recommended

upgrade migration path.

The NETBuilder hardw are w ill not safely support the upgrade.

Meaning: The hardware is not sufﬁcient to safely support the software upgrade,

and the bridge/router conﬁguration is not on the upgrade migration

path.

Action:

Contact your 3Com supplier for information about a hardware

upgrade.

Installation

The troubleshooting messages in this section are displayed during installation.

Troubleshooting

Messages

Installing the Testing the Enterprise OS Upgrade Utilities installation.

Enterprise OS Upgrade Meaning: This is an introductory message displayed when the bcmdiagnose

Management Utilities

utility is initiated.

None.

Action:

There is a problem w ith the installation of the Enterprise OS Upgrade

Utilities. The path /usr/3Com/bcm/bin and usr/3Com/common/bin should

be in the PATH environment variable.

Meaning: The installation process has searched for certain utilities in

/usr/3Com/bcm/bin and /usr/3Com/common/bin directories but

cannot ﬁnd them unless the path /usr/3Com/bcm/bin is ﬁrst.

Action:

Check that /usr/3Com/bcm/bin and /usr/3Com/common/bin have

been added in the path environment variable.

There is a problem w ith the installation of the Enterprise OS Upgrade

Utilities. The path /usr/3Com/bcm/bin should be ﬁrst in the PATH

environment variable.

Meaning: The installation process cannot ﬁnd the necessary directories unless

the path /usr/3Com/bcm/bin is ﬁrst.

Action:

Check that /usr/3Com/bcm/bin is ﬁrst in the path environment

variable.

Download from Www.Somanuals.com. All Manuals Search And Download.

APPENDIX A: TROUBLESHOOTING

There is a problem w ith the installation of the Enterprise OS Upgrade

Utilities. The location of the Enterprise OS Upgrade Utilities w as not added

to the path environment variable or the directory does not contain all the

required programs.

Meaning: The installation process cannot ﬁnd the utilities because it does not

know where to look for them.

Action:

Check that a location for the utilities was speciﬁed in the path

environment variable.

There is a problem w ith the installation of the Enterprise OS Upgrade

Utilities. The version numbers of the Enterprise OS Upgrade Utilities are

not consistent.

Meaning: The bcmdiagnose utility has assumed that the version of the

Enterprise OS Upgrade Management Utilities in bcmcommon.sh is

correct and has checked that each executable utility has the same

version number. At least one utility is different.

Action:

Check that you have speciﬁed version number for the utilities you are

installing correctly.

Determining Pinging <IP address>

Connectivity Meaning: This is an introductory message that appears when the utilities are

attempting to reach a bridge/router with an IP address speciﬁed on

the command line.

Action:

None.

The NETBuilder did not respond to a ping. Make sure the IP address or host

name is correct and that the NETBuilder is reachable via IP.

Meaning: The device that the utilities were trying to reach did not respond.

Action:

Ensure the device can be reached using IP.

The NETBuilder responded to ping.

Meaning: The device which was speciﬁed in the IP address is reachable.

Action:

None.

Validating the SNMP Testing SNMP read access

Service Conﬁguration Meaning: This is an introductory message. Check to see if the SNMP Service is

active on the bridge/router.

Action:

None.

The NETBuilder is not responding to SNMP get requests. Ensure that the

SNMP Service is conﬁgured on the NETBuilder and that you have read and

w rite access via SNMP. Also check the values of the community strings in

the /etc/snmp.cfg ﬁle. They should match the NETBuilder’s SNMP

community strings.

Meaning: The bcmdiagnose utility has attempted to verify whether the

bridge/router speciﬁed by the <IP address> value has been conﬁgured.

Action:

Conﬁgure the SNMP server on your bridge/router to allow read access

to your network management station. See the Network Management

chapter in Using NETBuilder Family Software.

Download from Www.Somanuals.com. All Manuals Search And Download.

Installation Troubleshooting Messages

The bridge/router is not responding to SNMP set requests. Ensure that the

SNMP service is conﬁgured on the bridge/router and that you have read

and w rite access via SNMP. Also check the values of the community strings

in the /etc/snmp.cfg ﬁle. They should match the bridge/router’s SNMP

community strings.

Meaning: The bcmdiagnose utility has attempted to verify whether the

bridge/router speciﬁed by the <IP address> value has been conﬁgured.

Action:

Conﬁgure the SNMP server on your bridge/router to allow write

access to your network management station. See the Network

Management chapter in Using NETBuilder Family Software.

SNMP read access OK

Meaning: There is no problem with SNMP conﬁguration on the bridge/router.

Action:

None.

Testing SNMP w rite access

Meaning: This is an introductory message. Check to see if SNMP Service is active

on the bridge router.

Action:

None.

SNMP w rite access OK

Meaning: There is no problem with SNMP conﬁguration on the bridge/router.

Action:

None.

Testing the NMS/ TFTP Creating an Upgrade File

Conﬁguration

Testing ﬁle transfers using TFTP

Meaning: This is an introductory message displayed as the bcmdiagnose utility

begins its test.

None.

Action:

The TFTP safe directory is <tftpboot_dir>. Make sure that the TFTP safe dir

exists.

Meaning: The TFTP safe directory is the root directory under which the utilities

will store your bridge/router ﬁles.

Action:

Check that your TFTP safe directory exists.

The directory <tftpboot_dir> does not exist. Create <tftpboot_dir> w ith

full read/w rite/create ﬁle permissions. Make sure that this directory has

the proper ﬁle access permissions and is being used by the TFTP server.

Meaning: The bcmdiagnose utility has attempted to create a test ﬁle using the

TFTP safe directory and has failed.

Action:

Assign full read/write/create ﬁle access permissions to the TFTP

directory.

Creating "test3.com"

Meaning: This information message is displayed while the UNIX copy command

tries to create the test ﬁle.

Action:

None.

Could not remove "test3.com". Check that <tftpboot_dir> and

subdirectories have full read/w rite/create ﬁle permissions

Meaning: The UNIX remove command could not delete the test ﬁle.

Action:

Assign full read/write/create ﬁle access permissions to the directories.

Download from Www.Somanuals.com. All Manuals Search And Download.

APPENDIX A: TROUBLESHOOTING

Could not create "test3.com". Check that <tftpboot_dir> and

subdirectories have full read/w rite/create ﬁle permissions.

Meaning: The UNIX copy command could not create the test ﬁle.

Action:

Assign full read/write/create ﬁle access permissions to the directories.

The ﬁle "test3.com" w as not created w ith read access. Make sure

<tftpboot_dir> has full read/w rite/create ﬁle permissions.

Meaning: When the UNIX copy command created the ﬁle, read access was

not assigned.

Action:

Assign full read/write/create ﬁle access permissions to the directories.

The ﬁle "test3.com" w as not created w ith w rite access. Make sure

<tftpboot_dir> has full read/w rite/create ﬁle permissions.

Meaning: When the UNIX copy command created the ﬁle, write access was

not assigned.

Action:

Assign full read/write/create ﬁle access permissions to the directories.

Uploading an Upgrade File

Could not remove "<ipaddress> | DNSname>:a:/test3.com". Check that the

NETBuilder media is not w rite protected and that "<ipaddress> |

DNSname>:a:/test3.com" is not the name of a directory on the NETBuilder.

Meaning: The bcmrm utility could not delete the ﬁle on the bridge/router.

Action:

Make sure that your ﬂoppy disk write protect tab allows writing to

the diskette.

Copying TestFile from the NMS to "<ipaddress> | DNSname>:a:/test3.com".

Meaning: This is a status message.

Action:

None.

The bcmcp command could not w rite the ﬁle "testﬁle" on NBAddress or

DNS name. Make sure there is a ﬂash or ﬂoppy drive installed and that it is

not w rite protected.

Meaning: The bcmcp utility has been denied write access to the bridge/router.

Action:

Make sure there is a ﬂash or ﬂoppy diskette installed and that it is not

write-protected.

The ﬁle "<ipaddress> | DNSname>:a:/test3.com" is not present on the

brouter even though bcmcp did not report an error.

Meaning: The bcmtest utility could not locate the ﬁle on the bridge/router.

Action:

Check with your systems administrator.

The checksums of "test3.com" and "<ipaddress> | DNSname>:a:/test3.com"

are different even though bcmcp did not report an error.

Meaning: The bcmsum utility reported differing checksums on the local and

remote test ﬁles.

Action:

Check your network connection for possible corruption on the line.

The bcmcp command could not reliably copy the "test3.com" ﬁle to the

bridge/router.

Meaning: This is an information message.

Action:

None.

Download from Www.Somanuals.com. All Manuals Search And Download.

Installation Troubleshooting Messages

Dow nloading an Upgrade File

$local TestFile could not be removed. Make sure <tftpboot_dir> and

"test3.com" have full read/w rite/create ﬁle permissions.

Meaning: The UNIX remove command could not delete the test ﬁle.

Action:

Assign full read/write/create ﬁle access permissions to the directories.

The bcmcp command could not w rite the ﬁle "testﬁle" on the NMS. Check

that the ﬁle access permissions are read/w rite/create in the TFTP server

safe directory. Make sure there is enough space available.

Meaning: The bcmcopy utility could not write the test ﬁle.

Action:

Assign full read/write/create ﬁle access permissions to the

directories.The ﬁle “test3Com” is not present on the NMS even

though bcmcp did not report an error.

The ﬁle “test3Com” is not present on the NMS even though bcmcp did not

report an error.

Meaning: The UNIX test command could not validate that the test ﬁle exists on

the TFTP safe directory.

Action:

Check with your systems administrator.

The checksums of "test3.com" and "<ipaddress> | DNSname>:a:/test3.com"

are different even though bcmcp did not report an error.

Meaning: The bcmsum utility reported differing checksums on the local and

remote test ﬁles.

Action:

Check with your systems administrator.

The bcmcp command could not reliably copy the ﬁle "testﬁle" to the NMS.

Meaning: This is an information message.

Action:

None.

Could not remove ﬁle "<ipaddress> | DNSname>:a:/test3.com". Check that

the NETBuilder media is not w rite protected and that "<ipaddress> |

DNSname>:a:/test3.com" is not the name of a directory on the NETBuilder.

Meaning: The bcmrm utility could not delete the test ﬁle.

Action:

Check with your systems administrator.

"test3.com" could not be removed. Make sure <tftpboot_dir> and

"test3.com" have full read/w rite/create permissions.

Meaning: The UNIX remove command could not delete the test ﬁle.

Action:

Assign full read/write/create ﬁle access permissions to the directories.

File transfers using TFTP are OK.

Meaning: No problem was found with TFTP ﬁle transfers between the network

management station and bridge/router.

Action:

None.

Download from Www.Somanuals.com. All Manuals Search And Download.

APPENDIX A: TROUBLESHOOTING

Download from Www.Somanuals.com. All Manuals Search And Download.

CHOOSING A SOFTWARE PACKAGE

This chapter lists software packages from 8.0 through 11.2 and provides

recommended equivalent packages in 11.3.

NETBuilder II Upgrade

Migration Path

T a b l e 7 o ut l i n es the recommended migration path from previous software

packages to the latest packages supported in version 11.3. Use this table to

identify the new software package that is most similar to the package you are

currently using. Packages are identiﬁed by the two-letter designator of the version

string, which is found on your product CD-ROM disk label.

You can also identify the software package using:

bcmuname -R <device>

Where <device> is the IP address or hostname of the system you are planning to

upgrade. Or enter the Enterprise OS user interface command:

SHow -SYS VERsion

Table 7 NETBuilder II Software Package Migration to 11.3

Recommended Upgrade

Notes

From Version 8.0

To Version 11.3

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

(continued)

Download from Www.Somanuals.com. All Manuals Search And Download.

APPENDIX B: CHOOSING A SOFTWARE PACKAGE

Table 7 NETBuilder II Software Package Migration to 11.3

Recommended Upgrade

Notes

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

AC (DPE)

A hardware upgrade to a DPE module is required.

AC (DPE)

From Version 8.1

To Version 11.3

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

AC (DPE)

A hardware upgrade to a DPE module is required.

AC (DPE)

From Version 8.2/8.3

To Version 11.3

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

AC (DPE)

A hardware upgrade to a DPE module is required.

AC (DPE)

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

(continued)

Download from Www.Somanuals.com. All Manuals Search And Download.

NETBuilder II Upgrade Migration Path

Table 7 NETBuilder II Software Package Migration to 11.3

Recommended Upgrade

Notes

From Version 9.0/9.1

To Version 11.3

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

AC (DPE)

A hardware upgrade to a DPE module is required.

AC (DPE)

From Version 9.3/9.3.1

To Version 11.3

DW (DPE), DE (DPE) or DS (DPE)

DW (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

CP (CEC)

FF (CEC)

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

CX (DPE)

AC (DPE)

AP (DPE)

AC (DPE)

From Version 10.1

DW (DPE)

To Version 11.3

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption.

CP (CEC)

FP (CEC)

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption. A hardware upgrade to a

DPE module is required.

CX (DPE)

AC (DPE)

IA (CEC)

AC (DPE)

A hardware upgrade to a DPE module is required.

AP (DPE)

AC (DPE)

From Version 10.3

DW (DPE)

To Version 11.3

DW (DPE), DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption.

(continued)

Download from Www.Somanuals.com. All Manuals Search And Download.

APPENDIX B: CHOOSING A SOFTWARE PACKAGE

Table 7 NETBuilder II Software Package Migration to 11.3

Recommended Upgrade

Notes

From Version 11.0

AC (DPE)

To Version 11.3

AC (DPE)

DW (DPE)

DE (DPE)

DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption.

From Version 11.1

AC (DPE)

To Version 11.3

AC (DPE)

DW (DPE)

DE (DPE)

DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption.

From Version 11.2

AC (DPE)

To Version 11.3

AC (DPE)

DW (DPE)

DE (DPE)

DE (DPE) or DS (DPE)

The DE package has all the features of DW plus 56-bit

encryption. The DS package has all the features of

DW plus 128-bit encryption.

SuperStack II

NETBuilder Upgrade

Migration Path

T a b l e 8 o ut l i n es the recommended migration path from prior version

software packages to the latest packages supported in version 11.3. Use this table

to identify the new software package that is most similar to the package you are

currently using.

Packages are identiﬁed by the two-letter designator of the version string, which is

found on your product diskette label.

You can also identify the package using:

bcmuname -R <device>

Where <device> is the IP address or hostname of the system you are planning to

upgrade. Or enter the Enterprise OS user interface command:

SHow -SYS VERsion

Download from Www.Somanuals.com. All Manuals Search And Download.

SuperStack II NETBuilder Upgrade Migration Path

Table 8 SuperStack II NETBuilder Bridge/Router Software Package Migration to 11.3

Model Recommended Upgrade Notes

22x Series From Version 8.0

BA, RB, BX, AR, CF or CX

To Version 11.3

n/a

There is no equivalent package in version 11.3.

From Version 8.1

To Version 11.3

BX, BF, AR, CF or CX

From Version 8.2/8.3

BX, BF, AA, AB, CF, CX

n/a

To Version 11.3

n/a

From Version 9.0/9.1/9.3/10.1 To Version 11.3

BX, BF, AA, AB, CF, CX

n/a

32x Series From Version 8.3/9.0/9.1/9.3

To Version 11.3

FD, BF

n/a

From Version 10.1

AF, BF

To Version 11.3

n/a

There is no equivalent package in version 11.3.

From Version 11.0

To Version 11.3

42x Series From Version 8.0/8.1

BX, AR, CF

To Version 11.3

n/a

There is no equivalent package in version 11.3.

From Version 8.2/8.3

BX, BF, AB, or CF

From Version 9.0/9.1/9.3

BX, BF, AB, or CF, EE

From Version 10.1

BX, BF, AB, AA, CF

From Version 11.0

To Version 11.3

n/a

To Version 11.3

n/a

To Version 11.3

n/a

There is no equivalent package in version 11.3.

To Version 11.3

n/a

There is no equivalent package in version 11.3.

52x Series From Version 8.3/9.0/9.1/9.3

BF, CF

To Version 11.3

n/a

There is no equivalent package in version 11.3.

From Version 10.1

AF, CF

To Version 11.3

n/a

From Version 11.0

To Version 11.3

n/a

Download from Www.Somanuals.com. All Manuals Search And Download.

APPENDIX B: CHOOSING A SOFTWARE PACKAGE

SuperStack II

NETBuilder SI Upgrade

Migration Path

T a b l e 9 o ut l i n es the recommended migration path from prior version

software packages to the latest packages supported in version 11.3. Use this table

to identify the new software package that is most similar to the package you are

currently using.

Packages are identiﬁed by the two-letter designator of the version string, which is

found on your product diskette label.

You can also identify the package using:

bcmuname -R <device>

Where <device> is the IP address or hostname of the system you are planning to

upgrade. Or enter the Enterprise OS user interface command:

SHow -SYS VERsion

Table 9 SuperStack II NETBuilder SI Bridge/Router Software Package Migration to 11.3

Recommended Upgrade

Notes

From Version 10.0

To Version 11.3

NW or NE

The NE package has all the features of NW plus encryption.

The CE package has all the features of CF plus encryption.

CF or CE

From Version 11.0

To Version 11.3

NW, NE or NS

The NE package has all the features of NW plus 56-bit encryption. The NS

package has all the features of NW plus 128-bit encryption.

NE or NS

The NS package has all the features of NE plus 128-bit encryption.

CF, CE or CS

The CE package has all the features of the CF package plush 56-bit

encryption. The CS package has all the features of the CF package plus

128-bit encryption.

CE or CS

The CS package has all the features of the CE package plus 128-bit

encryption.

From Version 11.1

To Version 11.3

NW, NE or NS

The NE package has all the features of NW plus 56-bit encryption. The NS

package has all the features of NW plus 128-bit encryption.

NE or NS

The NS package has all the features of NE plus 128-bit encryption.

CF, CE or CS

The CE package has all the features of the CF package plush 56-bit

encryption. The CS package has all the features of the CF package plus

128-bit encryption.

CE or CS

The CS package has all the features of the CE package plus 128-bit

encryption.

Download from Www.Somanuals.com. All Manuals Search And Download.

OfficeConnect NETBuilder Upgrade Migration Path

Table 9 SuperStack II NETBuilder SI Bridge/Router Software Package Migration to 11.3 (continued)

Recommended Upgrade

Notes

From Version 11.2

To Version 11.3

NW, NE or NS

The NE package has all the features of NW plus 56-bit encryption. The NS

package has all the features of NW plus 128-bit encryption.

NE or NS

The NS package has all the features of NE plus 128-bit encryption.

CF, CE or CS

The CE package has all the features of the CF package plush 56-bit

encryption. The CS package has all the features of the CF package plus

128-bit encryption.

CE or CS

The CS package has all the features of the CE package plus 128-bit

encryption.

OfﬁceConnect

NETBuilder Upgrade

Migration Path

T a b l e 1 0 out l i n es the recommended migration path from previous software

package versions to the latest packages supported in version 11.3. Use this table

to identify the new software package that is most similar to the package you are

currently using.

Packages are identiﬁed by the two-letter designator of the version string, which is

found on your product diskette label.

You can also identify the package using:

bcmuname -R <device>

Where <device> is the IP address or hostname of the system you are planning to

upgrade. Or enter the Enterprise OS user interface command:

SHow -SYS VERsion

Table 10 OfﬁceConnect Software Package Migration to 11.3

Recommended Upgrade

Notes

From Version 9.2

To Version 11.3

NW, NE, or NS

The NE package has all the features of NW plus 56-bit encryption. The NS

package has all the features of NW plus 128-bit encryption.

OF, OE, or OS

The OE package has all the features of OF plus 56-bit encryption. The OS

package has all the features of the OF package plus 128-bit encryption.

n/a

The VE package has 56-bit encryption.

From Version 9.3

To Version 11.3

NW, NE, or NS

The NE package has all the features of NW plus 56-bit encryption. The NS

package has all the features of NW plus 128-bit encryption.

OF, OE, or OS

The OE package has all the features of OF plus 56-bit encryption. the OS

package has all the features of OF plus 128-bit encryption.

Download from Www.Somanuals.com. All Manuals Search And Download.

100

APPENDIX B: CHOOSING A SOFTWARE PACKAGE

Table 10 OfﬁceConnect Software Package Migration to 11.3

Recommended Upgrade

Notes

n/a

VE has 56-bit encryption.

From Version 10.1

To Version 11.3

NW, NE or NS

The NE package has all the features of NW plus 56-bit encryption. the NS

package has all the features of NW plus 128-bit encryption.

OF, OE or OS

The OE package has all the features of OF plus 56-bit encryption. The OS

package has all the features of OF plus 128-bit encryption.

n/a

The VE package has 56-bit encryption.

From Version 10.2 (model To Version 11.3

13x only)

NW, NE, or NS

The NE package has all the features of NW plus 56-bit encryption. The NS

package has all the features of NW plus 128-bit encryption.

OF, OE, or OS

The OE package has all the features of OF plus 56-bit encryption. the OS

package has all the features of OF plus 128-bit encryption.

n/a

The VE package has 56-bit encryption.

From Version 11.0

To Version 11.3

NW or NE

NW, NE, or NS

The NE package has all the features of NW plus 56-bit encryption. The NS

package has all the features of NW plus 128-bit encryption.

OF or OE

OF, OE, or OS

The OE package has all the features of OF plus 56-bit encryption. the OS

package has all the features of OF plus 128-bit encryption.

The VE package has 56-bit encryption.

From Version 11.1

To Version 11.3

NW or NE

NW, NE, or NS

The NE package has all the features of NW plus 56-bit encryption. The NS

package has all the features of NW plus 128-bit encryption.

OF or OE

OF, OE, or OS

The OE package has all the features of OF plus 56-bit encryption. the OS

package has all the features of OF plus 128-bit encryption.

The VE package has 56-bit encryption.

From Version 11.2

To Version 11.3

NW or NE

NW, NE, or NS

The NE package has all the features of NW plus 56-bit encryption. The NS

package has all the features of NW plus 128-bit encryption.

OF or OE

OF, OE, or OS

The OE package has all the features of OF plus 56-bit encryption. the OS

package has all the features of OF plus 128-bit encryption.

The VE package has 56-bit encryption.

Download from Www.Somanuals.com. All Manuals Search And Download.

PathBuilder Upgrade Migration Path 101

PathBuilder Upgrade

Migration Path

T a b l e 1 1 out l i n es the recommended migration path from previous software

packages to the latest packages supported in version 11.3. Use this table to

identify the new software package that is most similar to the package you are

currently using. Packages are identiﬁed by the two-letter designator of the version

string, which is found on your product CD-ROM disk label.

You can also identify the software package using:

bcmuname -R <device>

Where <device> is the IP address or hostname of the system you are planning to

upgrade. Or enter the Enterprise OS user interface command:

SHow -SYS VERsion

Table 11 PathBuilder Software Package Migration to 11.3

Recommended Upgrade

From Version 11.1.1

To Version 11.3

From Version 11.2

To Version 11.3

Download from Www.Somanuals.com. All Manuals Search And Download.

102

APPENDIX B: CHOOSING A SOFTWARE PACKAGE

Download from Www.Somanuals.com. All Manuals Search And Download.

MOUNTING THE CD-ROM ON A

UNIX PLATFORM

This appendix describes how to mount the CD-ROM for UNIX Solaris 2.5.x, HP-UX

10.x and IBM AIX 4.1.x through 4.2.x operating systems.

Mounting the

CD-ROM on

Solaris 2.5.x

If you are mounting the CD-ROM from a drive that is directly connected to the

network management station where you have installed the Enterprise OS Upgrade

Management Utilities, enter the commands in this section. If you are mounting the

CD-ROM remotely, proceed to “Mounting from a Remote CD-ROM Drive.”

Mounting a Local To mount the CD-ROM from a local drive, follow these steps:

CD-ROM Drive

1 Insert the CD-ROM containing the bridge/router software into the CD-ROM drive.

2 Mount the CD-ROM in a directory in your ﬁle system. You must have Superuser

(root) access throughout the installation process.

At the command prompt, enter:

/usr/bin/su

b At the Password prompt, enter your root password.

Solaris 2.5.x uses a Volume Management Utility that by default mounts the

CD-ROM under the /cdrom directory.

3 Verify that the mount occurred by entering:

ls /cdrom

The display shows the cdrom0 directory.

4 If Solaris Volume Management is not installed, or has been deactivated, mount the

CD-ROM drive by entering:

mkdir /cdrom/cdrom0 (if you have not already done so)

mount -r -F hsfs /dev/sr0 /cdrom/cdrom0

After your CD-ROM has been mounted, you are ready to begin installing the

software.

Mounting from a On the remote system, make sure that the CD-ROM is properly connected and

Remote CD-ROM Drive powered up. To allow other systems to access the remote system, follow these

steps:

1 Insert the CD-ROM containing the bridge/router software into the CD-ROM drive.

2 Mount the CD-ROM in a directory in your ﬁle system. You must have Superuser

(root) access to complete the installation process.

Download from Www.Somanuals.com. All Manuals Search And Download.

104

APPENDIX C: MOUNTING THE CD-ROM ON A UNIX PLATFORM

At the command prompt on the remote system, enter:

/usr/bin/su

b At the Password prompt, enter your root password.

Solaris 2.5.x uses a Volume Management Utility that by default mounts the

CD-ROM under the /cdrom directory.

3 Verify that the mount occurred by entering:

ls /cdrom

The display shows the cdrom0 directory.

4 Verify that Solaris Volume Management is installed by entering:

ps -aux | grep vold

ps -ef | grep vold

If /usr/sbin/vold is displayed, then Volume Management is installed. Proceed to

step 5.

If Solaris Volume Management is not installed, or has been deactivated, mount the

CD-ROM drive by entering:

mkdir /cdrom (if you have not already done so)

mount -r -F hsfs /dev/sr0 /cdrom/cdrom0

5 Make the CD-ROM directory (/cdrom/cdrom0) available for Network File System

(NFS) clients.

Edit the /etc/dfs/dfstab ﬁle by adding the following line:

share -F nfs -o ro /cdrom/cdrom0

Change directories to /etc/init.d and enter:

./nfs.server start

b Enter:

shareall

exportfs -a

You may need to start the NFS daemons.

6 On the local network management station (the one where you are installing the

software), at the command prompt, enter:

mkdir /cdrom/remote (if you have not already done so)

mount -r <remote_system>:/cdrom/cdrom0 /cdrom/remote

For <remote_system>, enter the IP address or host name of the remote system

that does not have a CD-ROM drive.

7 You can verify that the mount occurred by entering:

cd /cdrom

8 To display a directory of the CD-ROM, enter:

After your CD-ROM has been mounted, you are ready to begin installing the

software.

Download from Www.Somanuals.com. All Manuals Search And Download.

Mounting the CD-ROM on HP-UX 10.x 105

Mounting the

CD-ROM on HP-UX

10.x

If you are mounting the CD-ROM from a drive that is directly connected to the

network management station where you have installed the Enterprise OS Upgrade

Management Utilities, enter the commands in this section. If you will mount the

CD-ROM remotely, proceed to “Mounting from a Remote CD-ROM Drive.”

Mounting from a Local To mount the CD-ROM from a local drive, follow these steps:

CD-ROM Drive

1 Open a command window.

2 Insert the CD-ROM.

3 Conﬁrm that the CD-ROM is mounted by entering:

mount | grep cdrom

If you receive no output command, you must mount the CD-ROM by entering:

mkdir /cdrom (if you have not already done so)

If you are running HP-UX 10.10, enter:

mount -r -t cdfs /dev/dsk/c0t2d0 /cdrom

If you are running HP-UX 10.20, enter:

mount -r /dev/dsk/c0t2d0 /cdrom

Mounting from a To mount the CD-ROM from a remote drive, follow these steps:

Remote CD-ROM Drive

1 Open a command window.

2 Insert the CD-ROM.

3 Mount the CD-ROM by entering:

mkdir /cdrom (if you have not already done so)

If you are running HP-UX 10.x, enter:

mount -r /dev/dsk/c0t2d0 /cdrom

4 Create the /etc/exports ﬁle if it does not already exist.

5 Add the following line to the /etc/exports ﬁle, if you have not already done so:

/cdrom -ro

6 If the /etc/exports ﬁle existed previously, enter:

/usr/etc/exportfs -a

7 If the /etc/exports ﬁle did not exist previously, reboot to become an NFS server.

8 On the local machine (the machine on which you are installing the bridge/router

software), enter:

mkdir /cdrom (if you have not already done so)

mount -r <remote machine>:/cdrom /cdrom

For <remote_system>, enter the IP address or host name of the remote system

that does not have a CD-ROM drive.

Download from Www.Somanuals.com. All Manuals Search And Download.

106

APPENDIX C: MOUNTING THE CD-ROM ON A UNIX PLATFORM

Mounting the

CD-ROM on IBM AIX

4.1.x Through 4.2.x

If you are mounting the CD-ROM from a drive that is directly connected to the

network management station, enter the commands in this section. If you will

mount the CD-ROM remotely, proceed to “Mount i n g from a R e mote C D -ROM

Driv e .”

Mounting from a Local To mount the CD-ROM from a local drive, follow these steps:

CD-ROM Drive

1 Open a command window.

2 Insert the CD-ROM.

3 Conﬁrm that the CD-ROM is mounted by entering:

mount | grep cdrom

If you receive no output command, you must mount the CD-ROM by entering:

mkdir /cdrom (if you have not already done so)

mount -v cdrfs -r /dev/cd0 /cdrom

Mounting from a To mount the CD-ROM from a remote drive, follow these steps:

Remote CD-ROM Drive

1 Open a command window.

2 Insert the CD-ROM.

3 Enter:

mkdir /cdrom (if you have not already done so)

mount -v cdrfs -r /dev/cd0 /cdrom

4 Create the /etc/exports ﬁle if it does not already exist.

5 Add the following line to the /etc/exports ﬁle, if you have not already done so:

/cdrom -ro

6 If the /etc/exports ﬁle existed previously, enter:

/usr/sbin/exportfs -a

7 If the /etc/exports ﬁle did not exist previously, reboot to become an NFS server.

8 On the local machine (the machine on which you are installing the bridge/router

utilities), enter:

mkdir /cdrom/remote (if you have not already done so)

mount -n <remote machine>:/cdrom /cdrom/remote

For <remote_system>, enter the IP address or host name of the remote system

that does not have a CD-ROM drive.

Download from Www.Somanuals.com. All Manuals Search And Download.

Unmounting the CD-ROM 107

Unmounting the

CD-ROM

To unmount the CD-ROM, follow these steps:

1 Make sure that no processes (shelltool, commandtool or any other application)

have /cdrom as the current working directory.

2 Make sure that you have Superuser (root) access. If you do not have this access, at

the command prompt enter:

/usr/bin/su

3 Unmount the CD-ROM as root.

On Solaris 2.5.x with or without “vold” running, at the # prompt enter:

umount /cdrom/cdrom0

eject /cdrom

Download from Www.Somanuals.com. All Manuals Search And Download.

108

APPENDIX C: MOUNTING THE CD-ROM ON A UNIX PLATFORM

Download from Www.Somanuals.com. All Manuals Search And Download.

TECHNICAL SUPPORT

3Com provides easy access to technical support information through a variety of

services. This appendix describes these services.

Information contained in this appendix is correct at time of publication. For the

most recent information, 3Com recommends that you access the 3Com

Corporation World Wide Web site.

Online Technical

Services

3Com offers worldwide product support 24 hours a day, 7 days a week, through

the following online systems:

■

World Wide Web site

3Com Knowledgebase Web Services

3Com FTP site

3Com Bulletin Board Service (3Com BBS)

3Com Facts Automated Fax Service

World Wide Web Site To access the latest networking information on the 3Com Corporation World Wide

Web site enter this URL into your Internet browser:

http://www.3com.com/

This service provides access to online support information such as technical

documentation and software library, as well as support options that range from

technical education to maintenance and professional services.

3Com Know ledgebase This interactive tool contains technical product information compiled by 3Com

Web Services expert technical engineers around the globe. Located on the World Wide Web at

http://knowledgebase.3com.com, this service gives all 3Com customers and

partners complementary, round-the-clock access to technical information on most

3Com products.

3Com FTP Site Download drivers, patches, software, and MIBs across the Internet from the 3Com

public FTP site. This service is available 24 hours a day, 7 days a week.

To connect to the 3Com FTP site, enter the following information into your FTP

client:

■

Hostname: ftp.3com.com

Username: anonymous

Password: <your Internet e-mail address>

Download from Www.Somanuals.com. All Manuals Search And Download.

110

APPENDIX D: TECHNICAL SUPPORT

You do not need a user name and password with Web browser software such as

Netscape Navigator and Internet Explorer.

3Com Bulletin Board The 3Com BBS contains patches, software, and drivers for 3Com products. This

Service service is available through analog modem or digital modem (ISDN) 24 hours a

day, 7 days a week.

Access by Analog Modem

To reach the service by modem, set your modem to 8 data bits, no parity, and

1 stop bit. Call the telephone number nearest you:

Country

Australia

Brazil

Data Rate

Telephone Number

Country

Japan

Data Rate

Telephone Number

Up to 14,400 bps 61 2 9955 2073

Up to 28,800 bps 55 11 5181 9666

Up to 14,400 bps 33 1 6986 6954

Up to 28,800 bps 4989 62732 188

Up to 14,400 bps 852 2537 5601

Up to 14,400 bps 39 2 27300680

Up to 14,400 bps 81 3 5977 7977

Up to 28,800 bps 52 5 520 7835

Up to 14,400 bps 86 10 684 92351

Up to 14,400 bps 886 2 377 5840

Up to 28,800 bps 44 1442 438278

Up to 53,333 bps 1 847 262 6000

Mexico

France

P.R. of China

Taiwan, R.O.C.

U.K.

Germany

Hong Kong

Italy

U.S.A.

Access by Digital Modem

ISDN users can dial in to the 3Com BBS using a digital modem for fast access up to

64 Kbps. To access the 3Com BBS using ISDN, call the following number:

1 847 262 6000

3Com Facts Automated The 3Com Facts automated fax service provides technical articles, diagrams, and

Fax Service troubleshooting instructions on 3Com products 24 hours a day, 7 days a week.

Call 3Com Facts using your Touch-Tone telephone:

1 408 727 7021

Support from Your

Netw ork Supplier

If you require additional assistance, contact your network supplier. Many suppliers

are authorized 3Com service partners who are qualiﬁed to provide a variety of

services, including network planning, installation, hardware maintenance,

application training, and support services.

When you contact your network supplier for assistance, have the following

information ready:

■

Product model name, part number, and serial number

A list of system hardware and software, including revision levels

Diagnostic error messages

Details about recent conﬁguration changes, if applicable

If you are unable to contact your network supplier, see the following section on

how to contact 3Com.

Download from Www.Somanuals.com. All Manuals Search And Download.

Support from 3Com 111

Support from 3Com

If you are unable to obtain assistance from the 3Com online technical resources or

from your network supplier, 3Com offers technical telephone support services. To

ﬁnd out more about your support options, please the 3Com technical telephone

support phone number at the location nearest you.

When you contact 3Com for assistance, have the following information ready:

■

Product model name, part number, and serial number

A list of system hardware and software, including revision levels

Diagnostic error messages

Details about recent conﬁguration changes, if applicable

Here is a list of worldwide technical telephone support numbers:

Country

Telephone Number

Country

Telephone Number

Asia Paciﬁc Rim

Australia

Hong Kong

India

Indonesia

Japan

Malaysia

New Zealand

Pakistan

Philippines

1 800 678 515

800 933 486

P.R. of China

10800 61 00137 or

021 6350 1590

800 6161 463

+61 2 9937 5085

001 800 61 009

0031 61 6439

1800 801 777

0800 446 398

+61 2 9937 5085

1235 61 266 2602

Singapore

S. Korea

From anywhere in S. Korea:

From Seoul:

Taiwan, R.O.C.

Thailand

00798 611 2230

(0)2 3455 6455

0080 611 261

001 800 611 2000

Europe

From anywhere in Europe, call: +31 (0)30 6029900 phone

+31 (0)30 6029999 fax

Europe, South Africa, and Middle East

From the following countries, you may use the toll-free numbers:

Austria

Belgium

Denmark

Finland

France

Germany

Hungary

Ireland

Israel

0800 297468

0800 71429

800 17309

0800 113153

0800 917959

0800 1821502

00800 12813

1800 553117

1800 9453794

1678 79489

Netherlands

Norway

Poland

Portugal

South Africa

Spain

Sweden

Switzerland

U.K.

0800 0227788

800 11376

00800 3111206

0800 831416

0800 995014

900 983125

020 795482

0800 55 3072

0800 966197

Italy

Latin America

Argentina

Brazil

Chile

Colombia

AT&T +800 666 5065

0800 13 3266

1230 020 0645

98012 2127

Mexico

Peru

Puerto Rico

Venezuela

01 800 CARE (01 800 2273)

AT&T +800 666 5065

800 666 5065

AT&T +800 666 5065

North America

1 800 NET 3Com

(1 800 638 3266)

Enterprise Customers:

1 800 876-3266

Download from Www.Somanuals.com. All Manuals Search And Download.

112

APPENDIX D: TECHNICAL SUPPORT

Returning Products

for Repair

Before you send a product directly to 3Com for repair, you must ﬁrst obtain an

authorization number. Products sent to 3Com without authorization numbers will

be returned to the sender unopened, at the sender’s expense.

To obtain an authorization number, call or fax:

Country

Telephone Number

+65 543 6500

Fax Number

Asia, Pacific Rim

+65 543 6348

+31 30 6029999

Europe, South Africa, and

Middle East

+31 30 6029900

Latin America

1 408 326 2927

1 408 326 3355

From the following countries, you may call the toll-free numbers; select option 2 and then

option 2:

Austria

0800 297468

0800 71429

800 17309

Belgium

Denmark

Finland

0800 113153

0800 917959

0800 1821502

00800 12813

1800 553117

1800 9453794

1678 79489

0800 0227788

800 11376

00800 3111206

0800 831416

0800 995014

900 983125

020 795482

0800 55 3072

0800 966197

France

Germany

Hungary

Ireland

Israel

Italy

Netherlands

Norway

Poland

Portugal

South Africa

Spain

Sweden

Switzerland

U.K.

U.S.A. and Canada

1 800 NET 3Com

(1 800 638 3266)

1 408 326 7120

(not toll-free)

Enterprise Customers:

1 800 876 3266

23 MAR 99

Download from Www.Somanuals.com. All Manuals Search And Download.

GLOSSARY

automatic recovery An upgrade method that copies the primary boot source to the NMS, then copies

the upgraded software back to the bridge/router as the test boot source. After a

successful test boot, the upgraded software is designated as the primary boot

source while the original software still present on the ﬂash memory, is designated

the secondary boot source. If the upgrade fails, the bridge/router automatically

reboots from the original software. Automatic recovery requires enough ﬂash

memory to hold two software sets.

backup Copying the software, including the images and conﬁguration ﬁles, from the

bridge/router to the NMS using Upgrade Link or the bcmbackup utility.

backup location See default directory structure.

baseline A copy of the bridge/router conﬁguration ﬁles stored in a directory on the network

management station. Baselining establishes a known good conﬁguration set by

checking for consistency between similar conﬁguration ﬁles on the network

management station and the NETBuilder bridge/router. Baselining assumes that

the versions of software and ﬁrmware running on the NETBuilder system have not

changed since the baseline was established.

BCM Boot Change Management. Individual command-line utilities and scripts that use

SNMP to perform EEPROM boot block and ﬁle manipulation operations on the

NETBuilder bridge/router and between the NETBuilder bridge/router and Network

Management Stations. This includes ﬁle transfer using TFTP.

bcm utilities See NETBuilder Upgrade Management Utilities.

bcmupdate An upgrade management utility that is used to upgrade conﬁguration ﬁles on a

network management station.

boot image A software ﬁle that is loaded into DRAM and executed by a bridge/router. The

main boot image ﬁles are named boot.29k and boot.68k.

BOOTP Bootstrap Protocol. Allows a bridge/router to obtain its IP address dynamically

from a network management station instead of from local EEPROM.

boot source A reference to a directory on the bridge/router where the boot and conﬁguration

ﬁles are stored. You can set and view boot source information using the

bcmconﬁg utility or the Sysconf command.

CCS Compact Conﬁguration Storage. An ASN.1-based ﬁle format used to store

bridge/router conﬁguration information.

conﬁguration ﬁles Files on the bridge/router that store parameter values and settings you have set in

the software.

Download from Www.Somanuals.com. All Manuals Search And Download.

114

GLOSSARY

default directory The default directory structure speciﬁes where to ﬁnd new installations of your

structure bridge/router software and backups of your bridge/router software on the NMS.

dual-image The ability of a bridge/router to store two sets of image and conﬁguration ﬁles.

FTP File Transfer Protocol. Allows the transfer of ﬁles between a host and a client.

image ﬁle See boot image.

manual recovery An upgrade method that copies the primary boot source to the NMS, formats the

ﬂash memory on the bridge/router, then copies the upgraded software back to the

bridge/router. If the upgrade fails, you must restore the software from the backup

on the NMS. Manual recovery requires enough ﬂash memory to hold one software

set, compared to automatic recovery which must have enough memory for two

sets.

netw ork management A UNIX or Windows system that has a TFTP server running in addition to software,

station such as the NETBuilder Upgrade Management Utilities, to manage your network.

NMS See network management station.

ofﬂine upgrade A method of copying conﬁguration ﬁles to a network management station,

updating those ﬁles to the latest release, and then copying them back to the

bridge/router with the new images while the bridge/router remains operational.

primary boot source The default boot source used to boot the bridge/router.

primary image The boot image speciﬁed in the primary boot directory.

restore A method of copying a software backup from the network management station

to a bridge/router using Upgrade Link or the bcmrestore utility and returning a

bridge/router to its previous operational state. Restoring can be used when

different versions of software have been installed on the bridge/router.

Remote Upgrade BCM utilities expressly used for remote upgrading. These utilities allow you to

Utilities manipulate NETBuilder bridge/router boot blocks and the NETBuilder bridge/router

ﬁle system via the SNMP protocol. These utilities also allow you to reboot the

NETBuilder bridge/router and to obtain accurate status information.

secondary boot source The boot source used in the event of primary boot source failure.

secondary image The software image designated for use by the bridge/router if the primary image is

inaccessible or cannot be booted. The secondary image is speciﬁed as the local

boot ﬁle in the secondary boot directory.

single-image The capability of a bridge/router to store only one set of software images and

conﬁguration ﬁles.

SNMP Simple Network Management Protocol. An Internet protocol that deﬁnes a way to

monitor and set conﬁguration and runtime parameters.

softw are set A combination of bootable images for a particular version of bridge/router

software along with the conﬁguration ﬁles that have been created for the

operation of the bridge/router. For version 11.0 and later, the software includes

web application ﬁles like Quick Step VPN.

Download from Www.Somanuals.com. All Manuals Search And Download.

GLOSSARY 115

softw are package A deﬁned subset of bridge/router services and protocols that are appropriate for a

particular model of the NETBuilder bridge/router family of products.

split image ﬁles A boot image that spans multiple diskettes. Split images occur on a few

SuperStack II NETBuilder bridge/router packages (for example, the CF package

prior to 9.1). If you are upgrading to one of these older packages, bcminstall will

automatically recombine the split image before performing your upgrade.

Telnet Terminal Emulation Link Protocol.

TEM/TNCS 3Com’s Transcend Enterprise Manager/Transcend Network Control Service, which

runs on Windows NT, Windows 95, Solaris, HP, and IBM platforms.

test boot source The boot source used during the test boot process.

test boot image The software image speciﬁed as the local boot ﬁle in the test source.

TFTP Trivial File Transfer Protocol. Allows ﬁle transfer between an IP host and an IP

client.

upgrade A method to bring a bridge/router up-to-date with later versions of software and

ﬁrmware without the need for reconﬁguring individual bridge/router parameters

and settings. The upgrade is performed using the NETBuilder Upgrade

Management Utilities or Transcend.

Upgrade Management A set of utilities to upgrade bridge/routers or switches. Some functions performed

Utilities by the utilities include copying software, ﬁrmware, and conﬁguration ﬁles from

the bridge/router, and upgrading conﬁguration ﬁles. In addition, the utilities can

conﬁgure the boot sources on the bridge/router, execute the test boot, and

conﬁgure the bridge/router boot sources to use the software in standard boot

situations.

Upgrade Link Backend The server application that fetches HTML and Java class ﬁles, runs the PERl scripts,

and accesses the ﬁle system.

Upgrade Link Front end The JAVA applet that runs in a browser. All the GUI components are part of the

front end.

Upgrade Migration Path The 3Com supported package for upgrading a bridge/router.

WINTEL All windows on INTEL platforms including Windows 95, Windows 98 and

Windows NT.

Download from Www.Somanuals.com. All Manuals Search And Download.

116

GLOSSARY

Download from Www.Somanuals.com. All Manuals Search And Download.

INDEX

backing up 72

locations 38

log ﬁles 72

network management station

disk storage requirements 26, 36, 52

network supplier support 110

Numbers

3Com bulletin board service (3Com

BBS) 110

ﬁrmware

I/O module upgrade 43, 44, 47, 49

installing on network management

station 72

monitoring bcm status 72

parameters, managing 72

rebooting 72

3Com Knowledgebase Web Services 109

3Com URL 109

3ComFacts 110

online technical services 109

test booting 72

Back up veriﬁcation 63

bcmbackup 72

syntax 73

patch upgrade

test media storage 72

testing media storage 72

upgrade 41, 45

installation with auto recovery 58

patch upgrade,installation with auto

recovery 57

bcmconﬁg 72

syntax 74

bcmctrl 72

FTP ﬁle transfer setup 52

PathBuilder

image-only upgrade 51

migration paths 101

upgrading 73

syntax 75

bcmdf 72, 76

syntax 76, 77

bcmdiagnose 37, 72

return codes 86

syntax 77

hardware

PathBuilder upgrade

disk storage requirements 26

privilege level

replacing

setting up SNMP 66

setting up IP address 66

troubleshooting messages 87

changing SNMP access 46, 48

changing SNMP access to ﬁles 66

bcminstall 72

syntax 78

bcmloadconﬁg 72, 79

bcmrestore 44, 49, 73

rejecting upgrade 44, 49, 59

syntax 80

bcmsetup 73

syntax 81

identifying upgrade problems 72

images

restoring bridge/router to previous

operational state 73

returning products for repair 112

updating ﬁles 10

IP address

bcmsum

setting up 66

syntax 81

bcmsysupgrade 40

repeating options 39

syntax 81

bcmuname 73

syntax 82

bcmupdate 73

syntax 83

bulletin board service 110

Si m p l e N e twork Management P rotocol. See

SNMP

log ﬁle 72

SNMP

logging function 72

changing ﬁle access 66

changing manager access 46, 48

setting up 66

for N E TB u i l d er I I u pgrade

software

manual recovery

NETBuilder II upgrade 47

manual recovery,NETBuilder II upgrade 43

MIBs 109

converting ﬁles on network

management station 73

displaying information 73

installing on network management

station 72

patch installation with auto

recovery 57, 58

conﬁguration,updating ﬁles 10

conventions

migration paths

NETBuilder II 93

OfﬁceConnect 99

PathBuilder 101

notice icons, About This Guide

text, About This Guide

SuperStack II 96, 98

rules and support limitations 11

upgrading 31

SuperStack II,upgrading 73

disk storage requirements

network management station 26, 36,

NETBuilder II

migration paths 93

remote upgrade 43, 47

upgrading 73

technical support

3Com Knowledgebase Web

Services 109

using bcmdiagnose 37

NETBuilder Upgrade Management Utilities

ﬁles location 38

fax service (3ComFacts) 110

ﬁles

3Com URL 109

bulletin board service 110

fax service 110

Download from Www.Somanuals.com. All Manuals Search And Download.

118

INDEX

network suppliers 110

product repair 112

TFTP ﬁle transfer setup 52

Transcend Enterprise Manager 25

Transcend Network Control Services 25

troubleshooting messages

connectivity 88

creating an upgrade ﬁle 89

downloading an upgrade ﬁle 91

hardware-related 87

SNMP conﬁguration 88

TFTP connection 89

uploading an upgrade ﬁle 90

utilities installation 87

validating safety 85

update script function 72

upgrade

bcmsysupgrade options 39, 40

identifying problems 72

migration paths

NETBuilder II 93

PathBuilder 101

patch installation

with auto recovery 57, 58

upgrading with bcmsysupgrade

utility 73

Upgrade Link

running locally 26

running remotely 26

Settings page 27

Status page 27

Upgrade Link application 25

Upgrade Management Utilities

accessing and downloading 71

accessing MAN pages 73, 85

commands 72

installation

troubleshooting messages 87

with bcmsetup 73

syntax 72

Upgrade veriﬁcation 29

URL 109

World Wide Web (WWW) 109

Download from Www.Somanuals.com. All Manuals Search And Download.

3Com Corporation LIMITED WARRANTY

HARDWARE

3Com warrants its hardware products to be free from defects in workmanship and materials, under normal use and service, for

the following lengths of time from the date of purchase from 3Com or its authorized reseller:

Network Interface Cards

Lifetime

1 year*

Other hardware products

*unless otherwise specified above

Spare parts and spares kits

90 days

If a product does not operate as warranted above during the applicable warranty period, 3Com shall, at its option and expense,

repair the defective product or part, deliver to Customer an equivalent product or part to replace the defective item, or refund

to Customer the purchase price paid for the defective product. All products that are replaced will become the property of

3Com. Replacement products may be new or reconditioned. Any replaced or repaired product or part has a ninety (90) day

warranty or the remainder of the initial warranty period, whichever is longer.

SOFTWARE

3Com warrants that the software programs licensed from it will perform in substantial conformance to the program

specifications therefor for a period of ninety (90) days from the date of purchase from 3Com or its authorized reseller. 3Com

warrants the media containing software against failure during the warranty period. No updates are provided. 3Com’s sole

obligation with respect to this express warranty shall be (at 3Com’s discretion) to refund the purchase price paid by Customer

for any defective software products, or to replace any defective media with software which substantially conforms to applicable

3Com published specifications. Customer assumes responsibility for the selection of the appropriate applications program and

associated reference materials. 3Com makes no warranty or representation that its software products will meet Customer’s

requirements or work in combination with any hardware or applications software products provided by third parties, that the

operation of the software products will be uninterrupted or error free, or that all defects in the software products will be

corrected. For any third party products listed in the 3Com software product documentation or specifications as being

compatible, 3Com will make reasonable efforts to provide compatibility, except where the non-compatibility is caused by a

“bug” or defect in the third party's product.

YEAR 2000 WARRANTY

In addition to the Hardware Products Warranty and Software Products Warranty identified above, 3Com warrants that all

Heritage 3Com products sold or licensed to Customer on and after January 1, 1998 that are date sensitive will continue

performing properly with regard to such date data on and after January 1, 2000, provided that all other products used by

Customer in connection or combination with the 3Com products, including hardware, software, and firmware, accurately

exchange date data with the 3Com products, with the exception of those products identified at 3Com’s Web site,

http://www.3com.com/products/yr2000.html, as not meeting this standard. A product is considered a “Heritage 3Com product”

if it is a member of a product family which was manufactured by 3Com prior to its merger with US Robotics Corporation. This

Year 2000 limited warranty does not apply to Heritage US Robotics Corporation products. If it appears that any such product

does not perform properly with regard to such date data on and after January 1, 2000, and Customer notifies 3Com before the

later of April 1, 2000, or ninety (90) days after purchase of the product from 3Com or its authorized reseller, 3Com shall, at its

option and expense, provide a software update which would effect the proper performance of such product, repair such

product, deliver to Customer an equivalent product to replace such product, or if none of the foregoing is feasible, refund to

Customer the purchase price paid for such product.

Any software update or replaced or repaired product will carry a Year 2000 Warranty for ninety (90) days or until April 1, 2000,

whichever is later.

OBTAINING WARRANTY

SERVICE

Customer must contact 3Com’s Corporate Service Center or an Authorized 3Com Service Center within the applicable

warranty period to obtain warranty service authorization. Dated proof of purchase may be required. Products returned to

3Com’s Corporate Service Center must be pre-authorized by 3Com with a Return Material Authorization (RMA) number

marked on the outside of the package, and sent prepaid and packaged appropriately for safe shipment, and it is recommended

that they be insured. The repaired or replaced item will be shipped to Customer, at 3Com’s expense, not later than thirty (30)

days after receipt of the defective product by 3Com.

Dead- or Defective-on-Arrival. In the event a product completely fails to function or exhibits a defect in materials or

workmanship within the first forty-eight (48) hours of installation but no later than thirty (30) days after the date of purchase,

and this is verified by 3Com, it will be considered dead- or defective-on-arrival (DOA) and a replacement shall be provided by

advance replacement. The replacement product will normally be shipped not later than three (3) business days after 3Com’s

verification of the DOA product, but may be delayed due to export or import procedures. When an advance replacement is

provided and Customer fails to return the defective product to 3Com within fifteen (15) days after shipment of the

replacement, 3Com will charge Customer for the replacement product, at list price.

3Com shall not be responsible for any software, firmware, information, or memory data of Customer contained in, stored on,

or integrated with any products returned to 3Com for repair, whether under warranty or not.

WARRANTIES EXCLUSIVE

IF A 3COM PRODUCT DOES NOT OPERATE AS WARRANTED ABOVE, CUSTOMER’S SOLE REMEDY FOR BREACH OF THAT

WARRANTY SHALL BE REPAIR, REPLACEMENT, OR REFUND OF THE PURCHASE PRICE PAID, AT 3COM’S OPTION. TO THE FULL

EXTENT ALLOWED BY LAW, THE FOREGOING WARRANTIES AND REMEDIES ARE EXCLUSIVE AND ARE IN LIEU OF ALL OTHER

WARRANTIES, TERMS, OR CONDITIONS, EXPRESS OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR

OTHERWISE, INCLUDING WARRANTIES, TERMS, OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

PURPOSE, AND SATISFACTORY QUALITY. 3COM NEITHER ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR

IT ANY OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE OR USE OF ITS PRODUCTS.

3COM SHALL NOT BE LIABLE UNDER THIS WARRANTY IF ITS TESTING AND EXAMINATION DISCLOSE THAT THE ALLEGED

DEFECT IN THE PRODUCT DOES NOT EXIST OR WAS CAUSED BY CUSTOMER’S OR ANY THIRD PERSON'S MISUSE, NEGLECT,

IMPROPER INSTALLATION OR TESTING, UNAUTHORIZED ATTEMPTS TO REPAIR OR MODIFY, OR ANY OTHER CAUSE BEYOND

THE RANGE OF THE INTENDED USE, OR BY ACCIDENT, FIRE, LIGHTNING, OR OTHER HAZARD.

LIMITATION OF LIABILITY

TO THE FULL EXTENT ALLOWED BY LAW, 3COM ALSO EXCLUDES FOR ITSELF AND ITS SUPPLIERS ANY LIABILITY, WHETHER

BASED IN CONTRACT OR TORT (INCLUDING NEGLIGENCE), FOR INCIDENTAL, CONSEQUENTIAL, INDIRECT, SPECIAL, OR

PUNITIVE DAMAGES OF ANY KIND, OR FOR LOSS OF REVENUE OR PROFITS, LOSS OF BUSINESS, LOSS OF INFORMATION OR

DATA, OR OTHER FINANCIAL LOSS ARISING OUT OF OR IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE,

Download from Www.Somanuals.com. All Manuals Search And Download.

USE, PERFORMANCE, FAILURE, OR INTERRUPTION OF ITS PRODUCTS, EVEN IF 3COM OR ITS AUTHORIZED RESELLER HAS BEEN

ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND LIMITS ITS LIABILITY TO REPAIR, REPLACEMENT, OR REFUND OF THE

PURCHASE PRICE PAID, AT 3COM’S OPTION. THIS DISCLAIMER OF LIABILITY FOR DAMAGES WILL NOT BE AFFECTED IF ANY

REMEDY PROVIDED HEREIN SHALL FAIL OF ITS ESSENTIAL PURPOSE.

DISCLAIMER

Some countries, states, or provinces do not allow the exclusion or limitation of implied warranties or the limitation of incidental

or consequential damages for certain products supplied to consumers or the limitation of liability for personal injury, so the

above limitations and exclusions may be limited in their application to you. When the implied warranties are not allowed to be

excluded in their entirety, they will be limited to the duration of the applicable written warranty. This warranty gives you

specific legal rights which may vary depending on local law.

GOVERNING LAW

This Limited Warranty shall be governed by the laws of the State of California, U.S.A. excluding its conflicts of laws principles

and excluding the United Nations Convention on Contracts for the International Sale of Goods.

3Com Corporation, 5400 Bayfront Plaza, Santa Clara, CA 95052-8145 (408) 764-5000

Download from Www.Somanuals.com. All Manuals Search And Download.

3M Welding System 16961 Rev 7A User Manual
Acer Personal Computer 4949C02001 User Manual
Acu Rite Weather Radio 01098CDI User Manual
AEG Washer 70730 User Manual
AMD Washer Dryer 30925 User Manual
American Standard Hot Tub 047186 0070A User Manual
AVerMedia Technologies Security Camera EB1304 User Manual
Backyard Storage Solutions Outdoor Storage 16702 User Manual
Banner American Products Laminator PL135 4 User Manual
Behringer Musical Instrument Amplifier GTX30 User Manual