Inhaltszusammenfassung zur Seite Nr. 1
Upgrading Enterprise OS
®
Software
Software version 11.3
http://www.3com.com/
Part No. 09-1551-001
Published May 1999
Inhaltszusammenfassung zur Seite Nr. 2
3Com Corporation © 3Com Corporation, 1999. All rights reserved. No part of this documentation may be reproduced in 5400 Bayfront Plaza any form or by any means or used to make any derivative work (such as translation, transformation, or Santa Clara, California adaptation) without permission from 3Com Corporation. 95052-8145 3Com Corporation reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of 3Com C
Inhaltszusammenfassung zur Seite Nr. 3
CONTENTS ABOUT THIS GUIDE Conventions 7 Year 2000 Compliance 8 1 OVERVIEW Upgrade Tools and Process 9 How the Utilities Work 10 Primary, Secondary, and Test Boot Sources 10 Automatic or Manual Recovery 10 Rules and Support Limitations 11 Take Time to Plan 11 2 INSTALLING THE UTILITIES ON A NETWORK MANAGEMENT STATION Installing the Utilities on a Windows System 13 Installing the Utilities on a UNIX Sy
Inhaltszusammenfassung zur Seite Nr. 4
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
Inhaltszusammenfassung zur Seite Nr. 5
Directory Paths 65 Restoring Software from a Backup 66 Configuring IP Routing 66 Configuring SNMP 66 Mapping Hostnames Using the etc/snmp.cfg File 67 Restoring the Software Using Upgrade Link 68 Verifying the Device for Restoring 68 Restoring the Software 68 Restoring the Software Using the Command-Line 69 Prediagnosing System Problems 69 Restoring the Software 69 8 REFERENCE FOR THE UPGRADE MANAGEMENT UTILITIES Accessing and Download
Inhaltszusammenfassung zur Seite Nr. 6
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
Inhaltszusammenfassung zur Seite Nr. 7
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 versio
Inhaltszusammenfassung zur Seite Nr. 8
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. Examp
Inhaltszusammenfassung zur Seite Nr. 9
OVERVIEW 1 This chapter provides an overview of the upgrade tools, process, and support limitations. Upgrade Tools and The upgrade procedures in this guide use the Enterprise OS Upgrade Management Process Utilities on a UNIX or Windows network management station (NMS). Definition 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 Windo
Inhaltszusammenfassung zur Seite Nr. 10
10 CHAPTER 1: OVERVIEW Figure 1 shows the typical upgrade process. Figure 1 Upgrade Process Begin Is hardware upgrade Back up config required? and boot files Install software Yes Update from bridge/router and utilities ? config files to NMS on NMS* No Accept If hardware upgrade? Restore old No Reboot bridge/router, upgrade, reinstall Verify ? software Perform test software images old hardware upgrade Reject version Yes hardware and config files upgrade Do final cleanup Copy config Reset IP and
Inhaltszusammenfassung zur Seite Nr. 11
Rules and Support Limitations 11 Rules and Support Before planning your upgrade, refer to the following rules and support limitations: Limitations n The utilities do not support Remote Boot and Configuration Services (RBCS) or network booting. n Upgrades from NETBuilder bridge/routers running version 7.x, or earlier, are not supported. n You cannot upgrade to a different platform. For example, you can only ® upgrade an OfficeConnect bridge/router to an OfficeConnect bridge/router. ® You cannot
Inhaltszusammenfassung zur Seite Nr. 12
12 CHAPTER 1: OVERVIEW
Inhaltszusammenfassung zur Seite Nr. 13
INSTALLING THE UTILITIES ON A 2 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 Utilit
Inhaltszusammenfassung zur Seite Nr. 14
14 CHAPTER 2: INSTALLING THE UTILITIES ON A NETWORK MANAGEMENT STATION 4 Run the setup program for Windows: n To install all packages, including the utilities and package definitions for use with Transcend if required, use: bcmsetup : all Where is the drive you want to install the utilities on. The packages install in the default directory \usr\3Com\bcm\, and the following paths are added to the autoexec.bat file: :\usr\3com\bcm\bin\ :\usr\3com\common\bin\ 5 Reboot y
Inhaltszusammenfassung zur Seite Nr. 15
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 n 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. n To install all packages from the CD-ROM, including the utilities and package definitions
Inhaltszusammenfassung zur Seite Nr. 16
16 CHAPTER 2: INSTALLING THE UTILITIES ON A NETWORK MANAGEMENT STATION Setting up for Auto On a UNIX NMS, after you have completed the previous setup procedures you Startup 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.
Inhaltszusammenfassung zur Seite Nr. 17
PLANNING AND PREPARING THE 3 UPGRADE This chapter describes setting up a file transfer method, choosing automatic or manual recovery, checking the required memory for each package, including instructions for checking the memory, and provides planning tables to copy and fill out for each bridge/router. If you are upgrading multiple bridge/routers using Transcend Enterprise Manager or Transcend Network Control Services, or are using the command-line utilities, you should make sure each bridge/
Inhaltszusammenfassung zur Seite Nr. 18
18 CHAPTER 3: PLANNING AND PREPARING THE UPGRADE On a UNIX NMS, follow these steps: 1 Create a user on your system with /tftpboot as the home directory. 2 When using the upgrade utilities via the command line or the Transcend Upgrade Manager, specify this user name and password in the BCMFTPUSER and BCMFTPPASS environment variables. Specify the -ftp flag in all command line utilities that use file transfers (bcmsysupgrade, bcmbackup, bcmrestore) if you want to use FTP file transfer. For example
Inhaltszusammenfassung zur Seite Nr. 19
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 software, then copies the upgraded files to the bridge/router. If the upgrade is not successful, you must restore the software from the NMS. If you are upgrading your hardware as well as the software, you can easily recover your old hardware if the upgrade is not successful. However, because you erased the flash memory on the new hardware
Inhaltszusammenfassung zur Seite Nr. 20
20 CHAPTER 3: PLANNING AND PREPARING THE UPGRADE Table 2 Version 11.2 Software Packages (continued) Flash Memory Required for: Software Package Model DRAM Required Automatic Recovery Manual Recovery OfficeConnect NETBuilder: (FD) - FRAD 120 8 MB 4 MB 4 MB (NW) - IP/IPX/AT Router 112, 122, 132, 142 8 MB 4 MB 4 MB for 132 2 MB for all others (BF) - Boundary Router 113, 123, 143 8 MB 8 MB 4 MB (OF) - Multiprotocol Router 117, 127, 137, 147 12 MB 8 MB 4 MB (AF) - APPN 116, 126, 146 12 MB 8 MB 4 MB
