Instruction/ maintenance manual of the product ENTERPRISE OS 11.3 3Com
Go to page of 120
® http://www.3com.com/ Upgrading Enterprise OS Softwar e Software version 11.3 Part No. 09-1551-001 Published May 1999.
ii 3Com Corporation 5400 Bayfront Plaza Santa Clara, California 95052-8145 © 3Com Corporation, 1999. All rights reserved. No part of this documentation may be r eproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without permission from 3Com Corporation.
C ONTENTS A BOUT T HIS G UIDE Conventions 7 Y ear 2000 Compliance 8 1 O VERVIEW Upgrade T ools and Process 9 How the Utilities Work 10 Primary , Secondary , and T est Boot Sources 10 Automatic or Manu.
5 U PGRADING A B RIDGE /R OUTER U SING THE C OMMAND -L INE U TILITIES Preparing for the Upgrade 35 Setting up for TFTP File T ransfers 36 Setting up for FTP File T ransfers 36 Prediagnosing System Pr .
Directory Paths 65 Restoring Software fr om a Backup 66 Configuring IP Routing 66 Configuring SNMP 66 Mapping Hostnames Using the etc/snmp.cfg File 67 Restoring the Software Using Upgrade Link 68 V .
T esting the NMS/ TFTP Configuration 89 Creating an Upgrade File 89 Uploading an Upgrade File 90 Downloading an Upgrade File 91 B C HOOSING A S OFTWARE P ACKAGE NETBuilder II Upgrade Migration Path 9.
A BOUT T HIS G UIDE 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.
8 A BOUT T HIS G UIDE Y ear 2000 Compliance For information on Y ear 2000 compliance and 3Com products, visit the 3Com Y ear 2000 Web page: http://www.3com.com/products/yr2000.html T able 2 T ext Conventions Convention Description Syntax The word “syntax” means you must evaluate the syntax provided and supply the appropriate values.
1 O VERVIEW This chapter provides an overview of the upgrade tools, pr ocess, and support limitations. Upgrade T ools and Process The upgrade pr ocedures in this guide use the Enterprise OS Upgrade Management Utilities on a UNIX or W indows network management station (NMS).
10 C HAPTER 1: O VERVIEW Figure 1 shows the typical upgrade pr ocess. Figure 1 Upgrade Pr ocess How the Utilities Work The softwar e on your bridge/r outer or switch consists of a bootable image file and configuration files that store all your settings.
Rules and Support Limitations 11 Rules and Support Limitations Before planning your upgrade, r efer to the following rules and support limitations: ■ The utilities do not support Remote Boot and Configuration Services (RBCS) or network booting. ■ Upgrades from NETBuilder bridge/r outers running version 7.
12 C HAPTER 1: O VERVIEW.
2 I NSTALLING THE U TILITIES ON A N ETWORK M ANAGEMENT S TATION Before you start the upgrade pr ocess, you must install the Enterprise OS Upgrade Management Utilities on a network management station (NMS).
14 C HAPTER 2: I NSTALLING THE U TILITIES ON A N ETWORK M ANAGEMENT S TATION 4 Run the setup program for Windows: ■ T o install all packages, including the utilities and package definitions for use with T ranscend if requir ed, use: bcmsetup <drive>: all Where <drive> is the drive you want to install the utilities on.
Installing the Utilities on a UNIX System 15 ■ If you download the utilities to your hard disk (see Chapter 8 for information about downloading the utilities): a Decompress the utilities. b Change to the utilities directory on your har d disk using: cd /<path>/ 3 Run the setup program.
16 C HAPTER 2: I NSTALLING THE U TILITIES ON A N ETWORK M ANAGEMENT S TATION Setting up for Auto Startup On a UNIX NMS, after you have completed the previous setup pr ocedures you need to set up the BootP server .
3 P LANNING AND P REPARING THE U PGRADE This chapter describes setting up a file transfer method, choosing automatic or manual recovery , checking the required memory for each package, including instructions for checking the memory , and provides planning tables to copy and fill out for each bridge/router .
18 C HAPTER 3: P LANNING AND P REPARING THE U PGRADE On a UNIX NMS, follow these steps: 1 Create a user on your system with /tftpboot as the home dir ectory . 2 When using the upgrade utilities via the command line or the T ranscend Upgrade Manager , specify this user name and password in the BCMFTPUSER and BCMFTPP ASS environment variables.
19 Manual Recovery An upgrade with manual recovery (using the -m option with the bcmsysupgrade utility) formats the flash memory after backing up the current softwar e, then copies the upgraded files to the bridge/router . If the upgrade is not successful, you must restor e the software fr om the NMS.
20 C HAPTER 3: P LANNING AND P REPARING THE U PGRADE Checking DRAM T o 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 addr ess or hostname of the switch or bridge/router .
Checking the Software Version 21 Checking the Software V ersion T o display the current software version and package you ar e running, use the bcmuname utility on the NMS: bcmuname -R <device> Where <device> is the IP addr ess or hostname of the bridge/router .
Planning Tables 22 NETBuilder II Planning Table Check each appropriate option to use with the command-line utilities: IP Address or Name Flash Memory Enough Flash Memory for Automatic Recovery? Enough Flash Memory for Manual Recovery? CEC Only: Firmware Version (pre-10.
Planning Tables 23 SuperStack II NETBuilder, SuperStack II NETBuilder SI, and OfficeConnect NETBuilder Planning Table Check each appropriate option to use with the command-line utilities: IP Address o.
24 C HAPTER 3: P LANNING AND P REPARING THE U PGRADE.
4 U PGRADING U SING THE NETB UILDER U PGRADE L INK A PPLICATION This chapter describes how to upgrade the software on a NETBuilder bridge/r outer 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 .
26 C HAPTER 4: U PGRADING U SING THE NETB UILDER U PGRADE L INK A PPLICATION Minimal disk storage requir ements depend on the number of differ ent software versions that ar e stored on the disk drive.
Status and Settings Pages 27 where port is the TCP socket on which the client can communicate with the server . On UNIX systems, you can add this command to cron. On Windows 95/98/NT systems, this command can be run as a console application. When NoSecurity is specified, the bcmnbrus command allows connections from all IP addresses.
28 C HAPTER 4: U PGRADING U SING THE NETB UILDER U PGRADE L INK A PPLICATION Settings Page The Setting Page lets you establish basic settings. ■ Y ou can choose the method of file transfers. TFTP is used by default for NETBuilder bridge/router softwar e release 11.
Verifying for Upgrading 29 V erifying 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 fr om the pop-up list in the Console page, or click New to enter the IP address or hostname.
30 C HAPTER 4: U PGRADING U SING THE NETB UILDER U PGRADE L INK A PPLICATION V alues Procedur e T o install the new software on the NMS, follow these steps: Y ou must be logged in as root for this procedure (UNIX). 1 Y ou can install the software fr om a CD-ROM, a tar archive, or a boot image (image-only upgrade).
Upgrading Software 31 5 Click Apply . The Install page appears. 6 Enter the path for the software, or click Browse to use a file br owse page. ■ For UNIX CD-ROM, use the following path: cdrom/<m.
32 C HAPTER 4: U PGRADING U SING THE NETB UILDER U PGRADE L INK A PPLICATION 4 Select a software package fr om the pop-up list. The list includes all packages you have installed on the NMS for your platform. If your package is not listed, install the software by clicking New and see “Installing Softwar e on the NMS” on page 29.
Upgrading Software 33 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 r eplacing your bridge/router with a new system. For example, click New Hardware if you are r eplacing the CEC module with a DPE module.
34 C HAPTER 4: U PGRADING U SING THE NETB UILDER U PGRADE L INK A PPLICATION.
5 U PGRADING A B RIDGE /R OUTER U SING THE C OMMAND -L INE U TILITIES This chapter describes how to upgrade the software on a bridge/r outer or switch using the command-line Upgrade Management Utilities.
36 C HAPTER 5: U PGRADING A B RIDGE /R OUTER U SING THE C OMMAND -L INE U TILITIES Minimal disk storage requir ements depend on the number of differ ent software versions that ar e stored on the disk drive.
Prediagnosing System Problems 37 If no flag is used, TFTP is used by default for software release 11.0 and lower , but FTP is used by default for software release 11.1 and higher . If the -ftp flag is specified on a bridge/router running software version 11.
38 C HAPTER 5: U PGRADING A B RIDGE /R OUTER U SING THE C OMMAND -L INE U TILITIES T o 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.
Using the Bcmsysupgrade Utility to Upgrade 39 V alues 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.
40 C HAPTER 5: U PGRADING A B RIDGE /R OUTER U SING THE C OMMAND -L INE U TILITIES For UNIX, after you have upgraded, check the /tftpboot/CLIENTS/<IP address or mac address>/tmp/stages.log file to ensure that the options were used consistently throughout the upgrade process.
Upgrading Software Only 41 ■ ccsmacro — file that contains pr edefined user macros. ■ fpupdate.29k (CEC Only) — file that updates the CEC module firmware. Y ou may also have several configuration files that will be upgraded by the utilities.
42 C HAPTER 5: U PGRADING A B RIDGE /R OUTER U SING THE C OMMAND -L INE U TILITIES CAUTION: If you are running any other firmware version besides 2.0 or 2.
Upgrading Software Only 43 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.
44 C HAPTER 5: U PGRADING A B RIDGE /R OUTER U SING THE C OMMAND -L INE U TILITIES The device reboots. 5 V erify that your upgrade completed successfully . T o verify that the software is working properly , you can perform a set of operational integrity checks on the newly upgraded device.
Upgrading Hardware and Software 45 “bcmsysupgrade” on page 81 for a list of the options available to use with the bcmsysupgrade utility . T o upgrade the bridge/router software and har dware, foll.
46 C HAPTER 5: U PGRADING A B RIDGE /R OUTER U SING THE C OMMAND -L INE U TILITIES Where <port> is the port thr ough which the bridge/router can be accessed by the NMS. d Enable IP routing by entering: SETDefault -IP CONTrol = ROute e Enable a route discovery pr otocol.
Upgrading Hardware and Software 47 ■ T esting typical device connections on terminals, printers, or hosts. ■ T esting the connectivity with specific bridge/routers.
48 C HAPTER 5: U PGRADING A B RIDGE /R OUTER U SING THE C OMMAND -L INE U TILITIES CAUTION: When upgrading to a package containing encryption, you must specify the -EncyrptionLicenseRead option flag. If you attempt to upgrade to an encrypted package and you have not specified the -Encr yptionLicenseRead option, the upgrade will fail.
Upgrading Hardware and Software 49 management stations by entering the IP address of the network management station that will have access. For example, enter: ADD -SNMP MANager “sysadm” 129.
50 C HAPTER 5: U PGRADING A B RIDGE /R OUTER U SING THE C OMMAND -L INE U TILITIES.
6 U PGRADING THE S OFTWARE I MAGE O NLY An image-only upgrade is an upgrade that replaces the NETBuilder bridge/r outer or PathBuilder S5xx series switch boot image file but does not upgrade any configuration files.
52 C HAPTER 6: U PGRADING THE S OFTWARE I MAGE O NLY . /usr/3Com/common/data/.profile-bcm ■ All configuration files are in the same dir ectory as the boot image.
Using Upgrade Link 53 On a UNIX NMS, follow these steps: 1 Create a user on your system with /tftpboot as the home dir ectory . 2 When using the upgrade utilities via the command line or the T ranscend Upgrade Manager , specify this user name and password in the BCMFTPUSER and BCMFTPP ASS environment variables.
54 C HAPTER 6: U PGRADING THE S OFTWARE I MAGE O NLY V erifying the Bridge/Router for Upgrading Before upgrading, run the diagnostic utility in Upgrade Link to verify connectivity to the bridge/router.
Using Upgrade Link 55 3 Select Upgrade and click Apply . The Upgrade page appears. 4 Select a software package fr om the pop-up list. The list includes all packages you have installed on the NMS for your platform.
56 C HAPTER 6: U PGRADING THE S OFTWARE I MAGE O NLY 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 r eplacing your bridge/router with a new system.
Using the Command-Line Utilities 57 Using the Command-Line Utilities Use the command-line utilities within a script or execute the commands manually . Otherwise, use Upgrade Link as described on page 53. Installing the NETBuilder Software Y ou can upgrade from a CD-ROM, a tar file, or an image you have downloaded from 3Com.
58 C HAPTER 6: U PGRADING THE S OFTWARE I MAGE O NLY Examples of a connectivity verification include: ■ Checking the connectivity between devices on differ ent networks, through designated bridge/routers. ■ T esting typical device connections on terminals, printers, or hosts.
Using the Enterprise OS User Interface 59 ■ Connectivity checks based on network topology . Examples of a connectivity verification include: ■ Checking the connectivity between devices on differ ent networks, through designated bridge/routers or switches.
60 C HAPTER 6: U PGRADING THE S OFTWARE I MAGE O NLY 7 Reboot the system by entering: ReBoot If the reboot is unsuccessful, the bridge/r outer or switch enters the monitor utility .
7 B ACKING U P AND R ESTORING S OFTWARE Y ou should always back up your software and configuration files to a network management station (NMS) in case your hardwar e or software fails. This chapter describes how to back up and restor e the software using Upgrade Link or the command-line utilities.
62 C HAPTER 7: B ACKING U P AND R ESTORING S OFTWARE Setting Up a File T ransfer Method Y ou can choose to transfer files using FTP or TFTP . Setting Up for TFTP File T ransfers T o use TFTP , you need to set up your NMS in preparation for TFTP file transfers.
Backing Up the Software 63 On a W indows 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 T ranscend Upgrade Manager , specify the ftp user name and password in the BCMFTPUSER and BCMFTPP ASS environment variables.
64 C HAPTER 7: B ACKING U P AND R ESTORING S OFTWARE 2 Select V erify 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 r ead/write community string for FTP/TFTP file transfer permissions.
Backing Up the Software 65 If bcmdiagnose shows a failure, check the SNMP r ead/write community string for FTP/TFTP file transfer permissions. Backing Up the Software T o back up your software to an .
66 C HAPTER 7: B ACKING U P AND R ESTORING S OFTWARE Restoring Software from a Backup If your bridge/router fails, you can r estore softwar e from a backup on the NMS. If your hardwar e fails or you lose IP and SNMP configuration, you must first reconfigur e IP and SNMP on the bridge/router .
Restoring Software from a Backup 67 2 W ith 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.
68 C HAPTER 7: B ACKING U P AND R ESTORING S OFTWARE Restoring the Software Using Upgrade Link Upgrade Link is an easy to use GUI for the utilities that runs in a web browser . Upgrade Link is an easy to use GUI for the utilities that runs in a web browser .
Restoring Software from a Backup 69 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 r estore. The boxes on the right show information about the backups, including the names directories and dates.
70 C HAPTER 7: B ACKING U P AND R ESTORING S OFTWARE bcmrestore -new_hw [ -<backname>] <device> If you are not r eplacing the hardwar e, use: bcmrestore [ -<backname>] <device> Where <backname> is the name of the backup for the boot blocks.
8 R EFERENCE FOR THE U PGRADE M ANAGEMENT U TILITIES This chapter describes the syntax and options for each utility , as well as how to download the utilities, and where they ar e installed on your system. Accessing and Downloading the Utilities The Upgrade Management Utilities are pr ovided on CD-ROM with every Enterprise OS software package.
72 C HAPTER 8: R EFERENCE FOR THE U PGRADE M ANAGEMENT U TILITIES For instructions on how to decompress and install the utilities, see the ruu110.txt file. The following are the Windows files: Update Log File The bcmsysupgrade utility cr eates log files in the tftpboot/CLIENTS/<mac_address>/tmp dir ectory .
Utility Descriptions and Syntax 73 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 T o access the man pages for a specific utility , use: man <NMU_name> where <NMU_name> is the name of the upgrade utility .
74 C HAPTER 8: R EFERENCE FOR THE U PGRADE M ANAGEMENT U TILITIES V alues Options No available options. Example For example, to backup the primary boot block as MyBackup01 using FTP , enter: bcmbackup primary -ftp -name:MyBackup01 199.
Utility Descriptions and Syntax 75 Where <boot sour ce> is primary , secondary , test, or dump, the [options] are: bcmctrl Syntax bcmctrl <device>[:<slot>] [-<option>[:<value>]] Description The bcmctrl utility does the following tasks: ■ Reboots a bridge/router .
76 C HAPTER 8: R EFERENCE FOR THE U PGRADE M ANAGEMENT U TILITIES V alues Options 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.
Utility Descriptions and Syntax 77 bcmdiagnose Syntax bcmdiagnose [ -ftp | -tftp ] [<device>] [-h] Description The bcmdiagnose utility identifies the most common installation and configuration problems. 3Com r ecommends that this utility be run immediately following bcmsetup and before running any other upgrade management utility .
78 C HAPTER 8: R EFERENCE FOR THE U PGRADE M ANAGEMENT U TILITIES bcminstall Syntax bcminstall [-h | -cdrom [<path>] | -tar <path> | -r | -diskette | -image <path> | <device>] .
Utility Descriptions and Syntax 79 bcmloadconfig Syntax bcmloadconfig [-s “<service1> [<service2>...]” | -l <line number>] [-i] -f <config file path>/<filename> <.
80 C HAPTER 8: R EFERENCE FOR THE U PGRADE M ANAGEMENT U TILITIES bcmnbrus Syntax bcmnbrus <port> [-NoSecurity] [-NoAuthentication] Description The bcmnbrus utility launches the Upgrade Link application backend process.
Utility Descriptions and Syntax 81 bcmsetup Syntax For UNIX: bcmsetup <packages> [install_directory] For W indows: 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.
82 C HAPTER 8: R EFERENCE FOR THE U PGRADE M ANAGEMENT U TILITIES Stages with an asterisk may reboot the bridge/router . The -s:accept stage only reboots manual and patch upgrades. Options bcmuname Syntax bcmuname [options] <device>[:<slot> | <drive>] -s:accept* Accepts the upgrade (cannot be used with -s:reject stage).
Utility Descriptions and Syntax 83 Description The bcmuname utility displays system information about the specified bridge/router or switch or Intelligent I/O module (IIO). If no options ar e specified, all the device-level options are printed. V alues Options If an option is required, it must be specified in very stage of the upgrade process.
84 C HAPTER 8: R EFERENCE FOR THE U PGRADE M ANAGEMENT U TILITIES When using the bcmupdate option on a W indows95, W indows98, or W indows NT version 4.0 system, the following files are copied but not converted or changed: The filenames are numbers in the es dir ectory , and the text files are located in the filter directory .
A T ROUBLESHOOTING This appendix describes error codes and messages that may be displayed during the upgrade process as a r esult of running the bcmdiagnose utility or when network dependencies have not been met.
86 A PPENDIX A: T ROUBLESHOOTING The requir ed file(s) <ipaddress>:<drive>:/<config file path> could not be located. Meaning: The bcmtest utility was unable to verify the presence of a file or directory . Action: Make sur e that the requir ed files and directories are available to the bcmtest utility .
Hardware-Related Messages 87 Hardwar e-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.
88 A PPENDIX A: T ROUBLESHOOTING There is a pr oblem with the installation of the Enterprise OS Upgrade Utilities. The location of the Enterprise OS Upgrade Utilities was not added to the path environment variable or the dir ectory does not contain all the requir ed programs.
Installation Troubleshooting Messages 89 The bridge/router is not r esponding to SNMP set r equests. Ensur e that the SNMP service is configured on the bridge/r outer and that you have read and write access via SNMP . Also check the values of the community strings in the /etc/snmp.
90 A PPENDIX A: T ROUBLESHOOTING Could not create "test3.com". Check that <tftpboot_dir> and subdirectories have full r ead/write/create file permissions. Meaning: The UNIX copy command could not create the test file. Action: Assign full r ead/write/create file access permissions to the dir ectories.
Installation Troubleshooting Messages 91 Downloading an Upgrade File $local T estFile could not be removed. Make sure <tftpboot_dir> and "test3.com" have full read/write/cr eate file permissions. Meaning: The UNIX remove command could not delete the test file.
92 A PPENDIX A: T ROUBLESHOOTING.
B C HOOSING A S OFTWARE P ACKAGE This chapter lists software packages fr om 8.0 through 11.2 and pr ovides recommended equivalent packages in 11.3. NETBuilder II Upgrade Migration Path T able 7 outlines the recommended migration path fr om previous softwar e packages to the latest packages supported in version 11.
94 A PPENDIX B: C HOOSING A S OFTWARE P ACKAGE FF 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.
NETBuilder II Upgrade Migration Path 95 From V ersion 9.0/9.1 T o V ersion 11.3 CP 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.
96 A PPENDIX B: C HOOSING A S OFTWARE P ACKAGE SuperStack II NETBuilder Upgrade Migration Path T able 8 outlines 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 ar e currently using.
SuperStack II NETBuilder Upgrade Migration Path 97 T able 8 SuperStack II NETBuilder Bridge/Router Softwar e Package Migration to 11.3 Model Recommended Upgrade Notes 22x Series From V ersion 8.0 T o V ersion 11.3 BA, RB, BX, AR, CF or CX n/a There is no equivalent package in version 11.
98 A PPENDIX B: C HOOSING A S OFTWARE P ACKAGE SuperStack II NETBuilder SI Upgrade Migration Path T able 9 outlines 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 ar e currently using.
OfficeConnect NETBuilder Upgrade Migration Path 99 OfficeConnect NETBuilder Upgrade Migration Path T able 10 outlines the recommended migration path from pr evious software package versions to the latest packages supported in version 11.
100 A PPENDIX B: C HOOSING A S OFTWARE P ACKAGE FD FD n/a VE VE has 56-bit encryption. From V ersion 10.1 T o V ersion 11.3 BX BF BF BF AB 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.
PathBuilder Upgrade Migration Path 101 PathBuilder Upgrade Migration Path T able 11 outlines the recommended migration path fr om previous softwar e 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 ar e currently using.
102 A PPENDIX B: C HOOSING A S OFTWARE P ACKAGE.
C M OUNTING THE CD-ROM ON A UNIX P LATFORM 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.
104 A PPENDIX C: M OUNTING THE CD-ROM ON A UNIX P LATFORM a At the command prompt on the r emote system, enter: /usr/bin/su b At the Password pr ompt, enter your root passwor d. Solaris 2.5.x uses a V olume Management Utility that by default mounts the CD-ROM under the /cdrom dir ectory .
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 fr om 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.
106 A PPENDIX C: M OUNTING THE CD-ROM ON A UNIX P LATFORM Mounting the CD-ROM on IBM AIX 4.1.x Through 4.2.x If you are mounting the CD-ROM fr om a drive that is directly connected to the network management station, enter the commands in this section.
Unmounting the CD-ROM 107 Unmounting the CD-ROM T o unmount the CD-ROM, follow these steps: 1 Make sure that no pr ocesses (shelltool, commandtool or any other application) have /cdrom as the curr ent working directory . 2 Make sure that you have Superuser (r oot) access.
108 A PPENDIX C: M OUNTING THE CD-ROM ON A UNIX P LATFORM.
D T ECHNICAL S UPPORT 3Com provides easy access to technical support information thr ough 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 r ecommends that you access the 3Com Corporation World Wide Web site.
110 A PPENDIX D: T ECHNICAL S UPPORT Y ou do not need a user name and password with Web browser software such as Netscape Navigator and Internet Explorer . 3Com Bulletin Board Service The 3Com BBS contains patches, software, and drivers for 3Com pr oducts.
Support from 3Com 111 Support from 3Com If you ar e unable to obtain assistance from the 3Com online technical r esour ces or from your network supplier , 3Com offers technical telephone support services. T o find out more about your support options, please the 3Com technical telephone support phone number at the location nearest you.
112 A PPENDIX D: T ECHNICAL S UPPORT Retur ning Products for Repair Before you send a pr oduct directly to 3Com for r epair , you must first obtain an authorization number . Products sent to 3Com without authorization numbers will be returned to the sender unopened, at the sender’ s expense.
G LOSSARY automatic recovery An upgrade method that copies the primary boot source to the NMS, then copies the upgraded software back to the bridge/r outer as the test boot source.
114 G LOSSARY default directory structure The default dir ectory structure specifies wher e to find new installations of your bridge/router softwar e and backups of your bridge/router softwar e on the NMS. dual-image The ability of a bridge/router to stor e two sets of image and configuration files.
G LOSSARY 115 software package A defined subset of bridge/router services and protocols that ar e appropriate for a particular model of the NETBuilder bridge/router family of pr oducts.
116 G LOSSARY.
I NDEX Numbers 3Com bulletin board service (3Com BBS) 110 3Com Knowledgebase Web Services 109 3Com URL 109 3ComFacts 110 B Back up verification 63 bcmbackup 72 syntax 73 bcmconfig 72 syntax 74 bcmct.
118 I NDEX network suppliers 110 product repair 112 TFTP file transfer setup 52 T ranscend Enterprise Manager 25 T ranscend Network Control Services 25 troubleshooting messages connectivity 88 creati.
3Com Corporation L IMITED W ARRANTY H ARDWARE 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 .
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.
An important point after buying a device 3Com ENTERPRISE OS 11.3 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought 3Com ENTERPRISE OS 11.3 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data 3Com ENTERPRISE OS 11.3 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, 3Com ENTERPRISE OS 11.3 you will learn all the available features of the product, as well as information on its operation. The information that you get 3Com ENTERPRISE OS 11.3 will certainly help you make a decision on the purchase.
If you already are a holder of 3Com ENTERPRISE OS 11.3, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime 3Com ENTERPRISE OS 11.3.
However, one of the most important roles played by the user manual is to help in solving problems with 3Com ENTERPRISE OS 11.3. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device 3Com ENTERPRISE OS 11.3 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
