® Upgrading Enterprise OS Software Software version 11.3 http://www.3com.com/ Part No.
3Com Corporation 5400 Bayfront Plaza Santa Clara, California 95052-8145 © 3Com Corporation, 1999. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without permission from 3Com Corporation.
CONTENTS ABOUT THIS GUIDE Conventions 7 Year 2000 Compliance 1 8 OVERVIEW Upgrade Tools and Process 9 How the Utilities Work 10 Primary, Secondary, and Test Boot Sources Automatic or Manual Recovery 10 Rules and Support Limitations 11 Take Time to Plan 11 2 10 INSTALLING THE UTILITIES ON A NETWORK MANAGEMENT STATION Installing the Utilities on a Windows System 13 Installing the Utilities on a UNIX System 14 Preparing for the Installation 14 Procedure 14 Setting up for Auto Startup 16 3 PLANNING AND
5 UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES Preparing for the Upgrade 35 Setting up for TFTP File Transfers 36 Setting up for FTP File Transfers 36 Prediagnosing System Problems 37 Installing the Software on the NMS 37 Software Directories 38 Using the Bcmsysupgrade Utility to Upgrade 39 Filenames 40 NETBuilder II Bridge/Router 40 SuperStack II NETBuilder and OfficeConnect NETBuilder Bridge/Routers PathBuilder S5xx Series Switch 41 Upgrading Software Only 41 Automatic Recovery 41 Manual Re
Directory Paths 65 Restoring Software from a Backup 66 Configuring IP Routing 66 Configuring SNMP 66 Mapping Hostnames Using the etc/snmp.
Testing the NMS/ TFTP Configuration 89 Creating an Upgrade File 89 Uploading an Upgrade File 90 Downloading an Upgrade File 91 B CHOOSING A SOFTWARE PACKAGE NETBuilder II Upgrade Migration Path 93 SuperStack II NETBuilder Upgrade Migration Path 96 SuperStack II NETBuilder SI Upgrade Migration Path 98 OfficeConnect NETBuilder Upgrade Migration Path 99 PathBuilder Upgrade Migration Path 101 C MOUNTING THE CD-ROM ON A UNIX PLATFORM Mounting the CD-ROM on Solaris 2.5.
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.
ABOUT THIS GUIDE Table 2 Text Conventions Convention Description Syntax The word “syntax” means you must evaluate the syntax provided and supply the appropriate values. Placeholders for values you must supply appear in angle brackets. Example: Enable RIPIP using: SETDefault ! -RIPIP CONTrol = Listen In this example, you must supply a port number for . Commands The word “command” means you must enter the command exactly as shown in text and press the Return or Enter key.
1 OVERVIEW This chapter provides an overview of the upgrade tools, process, and support limitations. Upgrade Tools and Process Definition of network management station The upgrade procedures in this guide use the Enterprise OS Upgrade Management Utilities on a UNIX or Windows network management station (NMS). An NMS is a UNIX or Windows system that has a TFTP/FTP server running in addition to software, such as the Enterprise OS Upgrade Management Utilities, to manage your network.
CHAPTER 1: OVERVIEW Figure 1 shows the typical upgrade process.
Rules and Support Limitations Rules and Support Limitations Take Time to Plan 11 Before planning your upgrade, refer to the following rules and support limitations: ■ The utilities do not support Remote Boot and Configuration Services (RBCS) or network booting. ■ Upgrades from NETBuilder bridge/routers running version 7.x, or earlier, are not supported. ■ You cannot upgrade to a different platform. For example, you can only upgrade an OfficeConnect® bridge/router to an OfficeConnect bridge/router.
CHAPTER 1: OVERVIEW
2 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.
CHAPTER 2: INSTALLING THE UTILITIES ON A NETWORK MANAGEMENT STATION 4 Run the setup program for Windows: ■ To install all packages, including the utilities and package definitions for use with Transcend if required, use: bcmsetup : all Where is the drive you want to install the utilities on. The packages install in the default directory \usr\3Com\bcm\, and the following paths are added to the autoexec.
Installing the Utilities on a UNIX System 15 Table 1 UNIX Directories Operating System Directory Name Solaris 2.5.x sunos5 HP-UX 10.x HP_UX IBM AIX 4.1.x, 4.2x aix ■ If you download the utilities to your hard disk (see Chapter 8 for information about downloading the utilities): a Decompress the utilities. b Change to the utilities directory on your hard disk using: cd // 3 Run the setup program.
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.
3 PLANNING AND PREPARING THE UPGRADE This chapter describes setting up a file transfer method, choosing automatic or manual recovery, checking the required memory for each package, including instructions for checking the memory, and provides planning tables to copy and fill out for each bridge/router.
CHAPTER 3: PLANNING AND PREPARING THE UPGRADE On a UNIX NMS, follow these steps: 1 Create a user on your system with /tftpboot as the home directory. 2 When using the upgrade utilities via the command line or the Transcend Upgrade Manager, specify this user name and password in the BCMFTPUSER and BCMFTPPASS environment variables. Specify the -ftp flag in all command line utilities that use file transfers (bcmsysupgrade, bcmbackup, bcmrestore) if you want to use FTP file transfer.
Manual Recovery An upgrade with manual recovery (using the -m option with the bcmsysupgrade utility) formats the flash memory after backing up the current software, then copies the upgraded files to the bridge/router. If the upgrade is not successful, you must restore the software from the NMS. If you are upgrading your hardware as well as the software, you can easily recover your old hardware if the upgrade is not successful.
CHAPTER 3: PLANNING AND PREPARING THE UPGRADE Table 2 Version 11.
Checking the Software Version Checking the Software Version 21 To display the current software version and package you are running, use the bcmuname utility on the NMS: bcmuname -R Where is the IP address or hostname of the bridge/router.
Flash Memory NETBuilder II Planning Table IP Address or Name X Enough Flash Memory for Automatic Recovery? X Current Software Version and Two-Letter Code Planning Tables Check each appropriate option to use with the command-line utilities: Manual Recovery? Hardware Upgrade? -V: -V: -V: -V: -V: -V: -V:
IP Address or Name 8 MB Flash Memory X Enough Flash Memory for Automatic Recovery? X DRAM Current Software Version and Two-Letter Code New Software Version and Two-Letter Code ❑ -m ❑ -new_hw ❑ Planning Tables 23 -V: -V: -V: -V: -V: -V: -V: -V: -V:
CHAPTER 3: PLANNING AND PREPARING THE UPGRADE
4 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.
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.
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. Otherwise, only those client IP addresses listed in the/usr/3Com/common/data/allow file will be accepted by Upgrade Link.
CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION Table 3 Status page Buttons (continued) Settings Page Button Description Abort Exits Upgrade Link and aborts the process. Some processes may need to be completed even after clicking Abort. Upgrade Link displays a message about any ongoing processes. View Logs Opens a page listing the logs available for viewing. The Setting Page lets you establish basic settings. ■ You can choose the method of file transfers.
Verifying for Upgrading Verifying for Upgrading 29 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.
CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION Values Procedure tftpboot For UNIX: Directory specified in inetd or tftpd for tftpd files. %tftpboot% For Windows (using the default 3Com TFTP server): Directory specified in the 3Server configuration.
Upgrading Software 31 5 Click Apply. The Install page appears. 6 Enter the path for the software, or click Browse to use a file browse page. ■ For UNIX CD-ROM, use the following path: cdrom//image/ ■ For Windows CD-ROM, use the following path: :\image\ ■ For Archive, enter the entire path including the filename. ■ For an FTP site, enter the full URL 7 Click Apply to install the software. The Status page appears while the software is installing.
CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION 4 Select a software package from the pop-up list. The list includes all packages you have installed on the NMS for your platform. If your package is not listed, install the software by clicking New and see “Installing Software on the NMS” on page 29. CAUTION: When upgrading to a package containing encryption, you will be presented with an export restriction message.
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 replacing your bridge/router with a new system. For example, click New Hardware if you are replacing the CEC module with a DPE module. You cannot upgrade to a different platform. For example, you can only upgrade an OfficeConnect bridge/router to an OfficeConnect bridge/router.
CHAPTER 4: UPGRADING USING THE NETBUILDER UPGRADE LINK APPLICATION
5 UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES This chapter describes how to upgrade the software on a bridge/router or switch using the command-line Upgrade Management Utilities. 3Com recommends using the Upgrade Link application described in Chapter 4, but you can use the command-line utilities instead if you want to write scripts or if you do not have a web browser on your NMS. Use Transcend Enterprise Manager or Transcend Network Control Services to upgrade multiple bridge/routers.
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.
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.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.
CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES To check which version you have installed, enter: bcmdiagnose -h The version of the installed utilities is displayed in the following message: bcmdiagnose version 11.3. Copyright 3Com Corporation 1999 If the version of the utilities you have installed is not version 11.3, you must first install the 11.3 utilities according to Chapter 2. 4 Install the software.
Using the Bcmsysupgrade Utility to Upgrade Values tftpboot For UNIX: Directory specified in inetd or tftpd for tftpd files. %tftpboot% For Windows (using the default 3Com TFTP server): Directory specified in the Win.ini file in the “[3Com.nm] TFTPROOT=” section. The Win.ini file is located in the default Windows directory, for example C:\windows or C:\winnt4.
CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES For UNIX, after you have upgraded, check the /tftpboot/CLIENTS//tmp/stages.log file to ensure that the options were used consistently throughout the upgrade process. For Windows, after you have upgraded, check the \%tftpboot%\CLIENTS\\tmp\stages.log file to ensure that the options were used consistently throughout the upgrade process.
Upgrading Software Only ■ ccsmacro — file that contains predefined user macros. ■ fpupdate.29k (CEC Only) — file that updates the CEC module firmware. 41 You may also have several configuration files that will be upgraded by the utilities. SuperStack II NETBuilder and OfficeConnect NETBuilder Bridge/Routers ■ ■ boot.68k — image file that boots the system. sys — file that may be used during the upgrade process to determine the source or target software version.
CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES CAUTION: If you are running any other firmware version besides 2.0 or 2.1, you should upgrade the firmware after upgrading the software. To upgrade the CEC firmware, follow these steps: a Make sure there is a floppy diskette with write access in the floppy drive on the bridge/router. The diskette is formatted during the upgrade, so make sure that the contents of the diskette you intend to use can be overwritten.
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.1 or earlier.) If the upgrade is successful, and if you have not already done so in step 2, upgrade the CEC firmware by following these steps: a Make sure there is a floppy diskette with write access in the floppy drive on the bridge/router.
CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES The device reboots. 5 Verify that your upgrade completed successfully. To verify that the software is working properly, you can perform a set of operational integrity checks on the newly upgraded device. These may include: ■ Some standard checks based on services active. A basic service verification test can Ping to specific IP addresses. ■ Connectivity checks based on network topology.
Upgrading Hardware and Software 45 “bcmsysupgrade” on page 81 for a list of the options available to use with the bcmsysupgrade utility.
CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES Where is the port through which the bridge/router can be accessed by the NMS. d Enable IP routing by entering: SETDefault -IP CONTrol = ROute e Enable a route discovery protocol. For example, enable OSPF by using: SETDefault ! -OSPF CONTrol = Enable f Check your configuration by pinging the bridge/router from the NMS: ping Where is the IP address of the bridge/router. 7 Set up SNMP.
Upgrading Hardware and Software ■ ■ Testing typical device connections on terminals, printers, or hosts. ■ Testing the connectivity with specific bridge/routers. 47 Custom checks based on applications and typical network use. For instance, you can check normal operation over the network and perform file transfers, as well as run traces on specific routes or check routing tables. 11 Accept or reject the upgrade.
CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES CAUTION: When upgrading to a package containing encryption, you must specify the -EncyrptionLicenseRead option flag. If you attempt to upgrade to an encrypted package and you have not specified the -EncryptionLicenseRead option, the upgrade will fail. The bcmsysupgrade utility only backs up the files in the primary boot source. To archive both the primary and secondary boot sources, use bcmbackup instead of bcmsysupgrade.
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.213.224.1 7 Copy the upgraded software to the bridge/router using: bcmsysupgrade -s:to_nb -m -new_hw 8 Accept your upgrade using: bcmsysupgrade -s:accept -m -new_hw The bridge/router reboots. 9 Verify that your upgrade completed successfully.
CHAPTER 5: UPGRADING A BRIDGE/ROUTER USING THE COMMAND-LINE UTILITIES
6 UPGRADING THE SOFTWARE IMAGE ONLY An image-only upgrade is an upgrade that replaces the NETBuilder bridge/router or PathBuilder S5xx series switch boot image file but does not upgrade any configuration files. You can perform an image-only upgrade in the following cases: ■ You are installing a patch release for your current version of software. ■ You are upgrading to a different package of the same version. ■ Your new version does not require updated configuration files (for example, 10.1 to 10.3).
CHAPTER 6: UPGRADING THE SOFTWARE IMAGE ONLY . /usr/3Com/common/data/.profile-bcm ■ All configuration files are in the same directory as the boot image. ■ You have booted your bridge/router or switch from the primary boot source. ■ For Upgrade Link — You have a web browser installed with Java support, such as Netscape Navigator 4.5 or Internet Explorer 4.x or later, and it is in your path (UNIX). ■ There is sufficient disk space on the NMS for the amount of software you are installing.
Using Upgrade Link 53 On a UNIX NMS, follow these steps: 1 Create a user on your system with /tftpboot as the home directory. 2 When using the upgrade utilities via the command line or the Transcend Upgrade Manager, specify this user name and password in the BCMFTPUSER and BCMFTPPASS environment variables. Specify the -ftp flag in all command line utilities that use file transfers (bcmsysupgrade, bcmbackup, bcmrestore) if you want to use FTP file transfer.
CHAPTER 6: UPGRADING THE SOFTWARE IMAGE ONLY Verifying the Bridge/Router for Upgrading Before upgrading, run the diagnostic utility in Upgrade Link to verify connectivity to the bridge/router by following these steps: 1 Choose a bridge/router or switch from the pop-up list in the Console page, or click New to enter the IP address or hostname. The pop-up list contains bridge/routers or switches that you have upgraded or backed-up before. 2 Select Verify Upgrade Services (Diagnose) and click Apply.
Using Upgrade Link 55 3 Select Upgrade and click Apply. The Upgrade page appears. 4 Select a software package from the pop-up list. The list includes all packages you have installed on the NMS for your platform. If your package is not listed, install the software using the procedure in “Installing the Utilities on a Network Management Station” on page 13.
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.
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 You can upgrade from a CD-ROM, a tar file, or an image you have downloaded from 3Com. If you are installing the software from a CD-ROM, complete the procedure in “Installing the Software on the NMS” on page 37. You can choose to transfer files using FTP or TFTP.
CHAPTER 6: UPGRADING THE SOFTWARE IMAGE ONLY Examples of a connectivity verification include: ■ ■ Checking the connectivity between devices on different networks, through designated bridge/routers. ■ Testing typical device connections on terminals, printers, or hosts. ■ Testing the connectivity with specific bridge/routers or switches. Custom checks based on applications and typical network use.
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 different networks, through designated bridge/routers or switches. ■ Testing typical device connections on terminals, printers, or hosts. ■ Testing the connectivity with specific bridge/routers or switches. Custom checks based on applications and typical network use.
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.
7 BACKING UP AND RESTORING SOFTWARE You should always back up your software and configuration files to a network management station (NMS) in case your hardware or software fails. This chapter describes how to back up and restore the software using Upgrade Link or the command-line utilities. Prerequisites Confirm the following items: ■ You have installed the utilities according to Chapter 2. ■ You have set the path for the utilities (UNIX only).
CHAPTER 7: BACKING UP AND RESTORING SOFTWARE Setting Up a File Transfer Method Setting Up for TFTP File Transfers You can choose to transfer files using FTP or TFTP. To use TFTP, you need to set up your NMS in preparation for TFTP file transfers. Make sure your TFTP server is running. On a Windows workstation, 3Com’s 3CServer is shipped along with the utilities. Upgrade Link launches 3CServer during start up.
Backing Up the Software 63 On a Windows NMS, follow these steps: 1 Create a user in 3Com’s 3CServer FTP settings. 2 When using the upgrade utilities via command line or the Transcend Upgrade Manager, specify the ftp user name and password in the BCMFTPUSER and BCMFTPPASS environment variables. You can specify the -ftp flag in the utilities (bcmsysupgrade, bcmbackup, bcmrestore) if you want to use FTP file transfer. If no flag is used, TFTP is used by default for software release 11.
CHAPTER 7: BACKING UP AND RESTORING SOFTWARE 2 Select Verify Upgrade Services (Diagnose). A Status window appears showing the results of the diagnostic tests. 3 If the Status window shows a failure, check the SNMP read/write community string for FTP/TFTP file transfer permissions. If the Status window shows a success, click Home to continue with the backup. Backing Up the Software To back up the software, follow these steps: 1 Run Upgrade Link if you have not already done so.
Backing Up the Software 65 If bcmdiagnose shows a failure, check the SNMP read/write community string for FTP/TFTP file transfer permissions. Backing Up the Software To back up your software to an NMS, use: bcmbackup [both | primary | secondary] [-name:]] Values Directory Paths both Backs up both the primary and secondary boot source. This value is the default. primary Backs up the primary boot source. secondary Backs up the secondary boot source.
CHAPTER 7: BACKING UP AND RESTORING SOFTWARE Restoring Software from a Backup Configuring IP Routing If your bridge/router fails, you can restore software from a backup on the NMS. If your hardware fails or you lose IP and SNMP configuration, you must first reconfigure IP and SNMP on the bridge/router. If you still have connectivity, go to “Restoring the Software Using Upgrade Link” on page 68 or “Restoring the Software Using the Command-Line” on page 69.
Restoring Software from a Backup 67 2 With the Manager parameter, create a new manager with read/write access to the bridge/router. For security reasons, limit the number of network management stations by entering the IP address of the network management station that will have access. For example, enter: ADD -SNMP Manager “sysadm” 129.213.224.1 Mapping Hostnames Using the etc/snmp.cfg File /etc/snmp.cfg is used to configure a mapping between hostnames and/or IP addresses and SNMP community strings.
CHAPTER 7: BACKING UP AND RESTORING SOFTWARE Restoring the Software Using Upgrade Link Upgrade Link is an easy to use GUI for the utilities that runs in a web browser. Upgrade Link is an easy to use GUI for the utilities that runs in a web browser. See Chapter 4 for information on running Upgrade Link locally or remotely. Make sure you select and set up your file transfer method.
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 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.
CHAPTER 7: BACKING UP AND RESTORING SOFTWARE bcmrestore -new_hw [ -] If you are not replacing the hardware, use: bcmrestore [ -] Where is the name of the backup for the boot blocks.
8 REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES This chapter describes the syntax and options for each utility, as well as how to download the utilities, and where they are installed on your system. Accessing and Downloading the Utilities The Upgrade Management Utilities are provided on CD-ROM with every Enterprise OS software package. See Chapter 2 to install the utilities from CD-ROM. The upgrade utilities are installed into the directory /usr/3Com/bcm/.
CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES For instructions on how to decompress and install the utilities, see the ruu110.txt file. The following are the Windows files: Update Log File Utility Descriptions and Syntax Overview ruu113.zip Contains the utilities for Windows95, Window98, and Windows NT 4.0. ruu113.txt Contains the instructions for downloading and decompressing the utilities.
Utility Descriptions and Syntax 73 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.
CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES Values both Default value, which backs up both the primary and secondary boot sources. primary Backs up the primary boot source. secondary Backs up the secondary boot source. Indicates the IP address or hostname of the bridge/router. <-ftp | -tftp> Specifies the file transfer protocol to be used in the backup process. Specifies the name to be given to the backup file of the boot blocks.
Utility Descriptions and Syntax 75 Where is primary, secondary, test, or dump, the [options] are: -configp[ath]: Path to the configuration files. -fi[le]:* Name of boot file. -bo[otdevice]: (network | Boots from network. localA | Boots from local media A. localB) Boots from local media B. -configd[evice]: (bootdevice | local network) | Depends on -bootdevice. Local media configuration. Network configuration.
CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES Values Identifies the bridge/router that receives the changes specified by the bcmctrl utility. Options Specifies the slot where the I/O module is located that receives the changes specified by the bcmctrl utility. -u[pdate] Copies the complete set of boot parameters from the test boot source to the primary boot source.
Utility Descriptions and Syntax 77 bcmdiagnose Syntax Description bcmdiagnose [ -ftp | -tftp ] [] [-h] The bcmdiagnose utility identifies the most common installation and configuration problems. 3Com recommends that this utility be run immediately following bcmsetup and before running any other upgrade management utility.
CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES bcminstall Syntax bcminstall [-h | -cdrom [] | -tar | -r | -diskette | -image | ] Description The bcminstall utility installs bridge/router software and firmware onto a network management station from either a CD-ROM, tar files, an image file, a bridge/router, or a network management station floppy diskette. You must install all applicable Enterprise OS software packages before beginning the upgrade process.
Utility Descriptions and Syntax 79 bcmloadconfig Syntax bcmloadconfig [-s “ [...]” | -l ] [-i] -f / [-b] [-t:] Description You can execute multiple commands on the Enterprise OS user interface at once by entering the commands in a text file, then loading the file. The bcmloadconfig utility copies a specified configuration file to the bridge/router or switch and executes the commands in the file.
CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES -b Specifies that after the configuration file is copied to the bridge/router or switch a bcmctrl -reboot is executed. -t: Specifies a reboot time out period. If the device does not boot within the reboot timeout period (default: 600 seconds ) bcmloadconfig returns an error.
Utility Descriptions and Syntax -new_hw 81 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.
CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES -s:accept* Accepts the upgrade (cannot be used with -s:reject stage). -s:reject* Rejects the upgrade (cannot be used with -s:accept stage). -s:upgrade_cec_fw* Upgrades the NETBuilder II CEC firmware. -s:upgrade_io_fw* Upgrades the I/O firmware. Specifies 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.
Utility Descriptions and Syntax Description Values Options 83 The bcmuname utility displays system information about the specified bridge/router or switch or Intelligent I/O module (IIO). If no options are specified, all the device-level options are printed. Specifies either the hostname or the IP address of the bridge/router. Specifies slot of an I/O module within the bridge/router. This parameter is optional and is used only with the options marked with (IIO).
CHAPTER 8: REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES -V: Version to upgrade to. -p: Bridge/router platform type. -m Saves user macros. -n Prints trace messages. When using the bcmupdate option on a Windows95, Windows98, or Windows NT version 4.
TROUBLESHOOTING A 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: -h Help is available in HTML or (UNIX) man pages.
APPENDIX A: TROUBLESHOOTING The required file(s) ::/ could not be located. Meaning: The bcmtest utility was unable to verify the presence of a file or directory. Action: Make sure that the required files 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 0 The operation was successful.
Hardware-Related Messages Hardware-Related Messages 87 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 floppy drive and entering bt memupgrd.29k.
APPENDIX A: TROUBLESHOOTING There is a problem 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 directory does not contain all the required programs. Meaning: The installation process cannot find the utilities because it does not know where to look for them. Action: Check that a location for the utilities was specified in the path environment variable.
Installation Troubleshooting Messages 89 The bridge/router is not responding to SNMP set requests. Ensure that the SNMP service is configured on the bridge/router and that you have read and write access via SNMP. Also check the values of the community strings in the /etc/snmp.cfg file. They should match the bridge/router’s SNMP community strings. Meaning: The bcmdiagnose utility has attempted to verify whether the bridge/router specified by the value has been configured.
APPENDIX A: TROUBLESHOOTING Could not create "test3.com". Check that and subdirectories have full read/write/create file permissions. Meaning: The UNIX copy command could not create the test file. Action: Assign full read/write/create file access permissions to the directories. The file "test3.com" was not created with read access. Make sure has full read/write/create file permissions. Meaning: When the UNIX copy command created the file, read access was not assigned.
Installation Troubleshooting Messages 91 Downloading an Upgrade File $local TestFile could not be removed. Make sure and "test3.com" have full read/write/create file permissions. Meaning: The UNIX remove command could not delete the test file. Action: Assign full read/write/create file access permissions to the directories. The bcmcp command could not write the file "testfile" on the NMS. Check that the file access permissions are read/write/create in the TFTP server safe directory.
APPENDIX A: TROUBLESHOOTING
B 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 Table 7 outlines 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.
APPENDIX B: CHOOSING A SOFTWARE PACKAGE Table 7 NETBuilder II Software Package Migration to 11.3 Recommended Upgrade Notes 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. CX AC (DPE) A hardware upgrade to a DPE module is required. AP AC (DPE) A hardware upgrade to a DPE module is required. From Version 8.1 To Version 11.
NETBuilder II Upgrade Migration Path 95 Table 7 NETBuilder II Software Package Migration to 11.3 Recommended Upgrade Notes From Version 9.0/9.1 To Version 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. FF DW (DPE), DE (DPE) or DS (DPE) The DE package has all the features of DW plus 56-bit encryption.
APPENDIX B: CHOOSING A SOFTWARE PACKAGE Table 7 NETBuilder II Software Package Migration to 11.3 Recommended Upgrade Notes From Version 11.0 To Version 11.3 AC (DPE) AC (DPE) DW (DPE) DW (DPE) DE (DPE) DE (DPE) or DS (DPE) From Version 11.1 To Version 11.3 AC (DPE) AC (DPE) DW (DPE) DW (DPE) DE (DPE) DE (DPE) or DS (DPE) From Version 11.2 To Version 11.
SuperStack II NETBuilder Upgrade Migration Path 97 Table 8 SuperStack II NETBuilder Bridge/Router Software Package Migration to 11.3 Model Recommended Upgrade 22x Series From Version 8.0 To Version 11.3 BA, RB, BX, AR, CF or CX n/a From Version 8.1 To Version 11.3 BX, BF, AR, CF or CX n/a From Version 8.2/8.3 To Version 11.3 BX, BF, AA, AB, CF, CX n/a From Version 9.0/9.1/9.3/10.1 To Version 11.3 BX, BF, AA, AB, CF, CX n/a From Version 8.3/9.0/9.1/9.3 To Version 11.
APPENDIX B: CHOOSING A SOFTWARE PACKAGE SuperStack II NETBuilder SI Upgrade Migration Path Table 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 are currently using. Packages are identified by the two-letter designator of the version string, which is found on your product diskette label.
OfficeConnect NETBuilder Upgrade Migration Path 99 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 BF BF NW 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 NE or NS The NS package has all the features of NE plus 128-bit encryption.
APPENDIX B: CHOOSING A SOFTWARE PACKAGE Table 10 OfficeConnect Software Package Migration to 11.3 Recommended Upgrade Notes FD FD n/a VE From Version 10.1 To Version 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. OF 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.
PathBuilder Upgrade Migration Path PathBuilder Upgrade Migration Path 101 Table 11 outlines 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 identified by the two-letter designator of the version string, which is found on your product CD-ROM disk label.
APPENDIX B: CHOOSING A SOFTWARE PACKAGE
C 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 Mounting a Local CD-ROM Drive 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.
APPENDIX C: MOUNTING THE CD-ROM ON A UNIX PLATFORM a 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.
Mounting the CD-ROM on HP-UX 10.x Mounting the CD-ROM on HP-UX 10.x Mounting from a Local CD-ROM Drive 105 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.” To mount the CD-ROM from a local drive, follow these steps: 1 Open a command window.
APPENDIX C: MOUNTING THE CD-ROM ON A UNIX PLATFORM Mounting the CD-ROM on IBM AIX 4.1.x Through 4.2.x Mounting from a Local CD-ROM Drive 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 “Mounting from a Remote CD-ROM Drive.” To mount the CD-ROM from a local drive, follow these steps: 1 Open a command window. 2 Insert the CD-ROM.
Unmounting the CD-ROM Unmounting the CD-ROM 107 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.
APPENDIX C: MOUNTING THE CD-ROM ON A UNIX PLATFORM
D 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.
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 Service The 3Com BBS contains patches, software, and drivers for 3Com products. This 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.
Support from 3Com Support from 3Com 111 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 find out more about your support options, please the 3Com technical telephone support phone number at the location nearest you.
APPENDIX D: TECHNICAL SUPPORT Returning Products for Repair Before you send a product directly to 3Com for repair, 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.
GLOSSARY automatic recovery backup backup location 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 flash memory, is designated the secondary boot source. If the upgrade fails, the bridge/router automatically reboots from the original software.
GLOSSARY default directory structure dual-image FTP image file The default directory structure specifies where to find new installations of your bridge/router software and backups of your bridge/router software on the NMS. The ability of a bridge/router to store two sets of image and configuration files. File Transfer Protocol. Allows the transfer of files between a host and a client. See boot image.
GLOSSARY software package split image files Telnet TEM/TNCS A defined subset of bridge/router services and protocols that are appropriate for a particular model of the NETBuilder bridge/router family of products. 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).
GLOSSARY
INDEX 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 bcmctrl 72 syntax 75 bcmdf 72, 76 syntax 76, 77 bcmdiagnose 37, 72 return codes 86 syntax 77 bcminstall 72 syntax 78 bcmloadconfig 72, 79 bcmrestore 44, 49, 73 rejecting upgrade 44, 49, 59 syntax 80 bcmsetup 73 syntax 81 bcmsum syntax 81 bcmsysupgrade 40 repeating options 39 syntax 81 bcmuname 73 syntax 82 bcmupdate
INDEX network suppliers 110 product repair 112 TFTP file transfer setup 52 Transcend Enterprise Manager 25 Transcend Network Control Services 25 troubleshooting messages connectivity 88 creating an upgrade file 89 downloading an upgrade file 91 hardware-related 87 SNMP configuration 88 TFTP connection 89 uploading an upgrade file 90 utilities installation 87 validating safety 85 U update script function 72 upgrade bcmsysupgrade options 39, 40 identifying problems 72 migration paths NETBuilder II 93 P
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 Other hardware products *unless otherwise specified above 1 year* 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 op
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.
