Bay Networks Baystream 7 Software Manual
Nortel baystream 7 software: software guide
Hide thumbs
Also See for Baystream 7:
- Configuration and troubleshooting manual (186 pages) ,
- Notice (140 pages) ,
- Install manual (38 pages)
Related Manuals for Bay Networks Baystream 7
Summary of Contents for Bay Networks Baystream 7
- Page 1 Upgrading to BayStream 7.2 Part Number 115400-C Rev. A...
- Page 2 Bay Networks, Inc. The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that license. A summary of the Software License is included in this document.
- Page 3 Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein. Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms...
- Page 4 Software solely for backup purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely in support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend to Bay Networks Agent software or other Bay Networks software products.
- Page 5 Software will operate in the hardware or software combinations that the Licensee may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot be reproduced with the latest Software release.
- Page 6 U.S. Government: (i) export, re-export, transfer, or divert any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports are restricted or embargoed under United States export control laws and regulations,...
- Page 7 (ii) provide the Software or related technical data or information to any military end user or for any military end use, including the design, development, or production of any chemical, nuclear, or biological weapons.
- Page 9 Overview of BayStream Version 7.2 Upgrade Procedure This guide describes how to upgrade to BayStream™ Multiservice Software Version 7.2 from an earlier release, as follows: Task What You Do Review BayStream Site Manager system requirements. Upgrade BayStream Site Manager Software Version 7.2.
- Page 10 BayStream platforms. To run BayStream Site Manager Version 7.2, your PC or UNIX workstation must meet the hardware and software requirements listed in Refer to BayStream 7.2 Documentation Change Notice for the software image size for your BayStream platform. Table...
-
Page 11: System Requirements
32 MB of disk space (minimum) WinSock-compliant TCP/IP stack, including products such as NetManage Chameleon, Novell LAN Workplace, FTP Software PC/TCP for DOS, Sun PC-NFS, and Microsoft Windows 95 Network interface card (NIC) with a driver type of Packet, Network Driver Interface Specification (NDIS),... - Page 12 • • • • • • Hardware and Software Requirements Supported workstation: Sun Microsystems Sun4SPARCstation SunOS 4.1 or later, or Solaris 2.3 or later Sun OpenWindows 3.0 or later, or MIT X11 Window System 4.0 or later 16 MB of RAM (minimum)
- Page 13 Task 2: Upgrading to BayStream Site Manager Version 7.2 This section describes how to upgrade BayStream Site Manager software Version 7.2 on a PC, SPARCstation, or RS/6000. Instructions for upgrading on a SPARCstation begin on page Upgrading BayStream Site Manager on a PC...
- Page 14 Deleting Existing State Files Site Manager creates state files for all Site Manager tools you use. State files describe the state of the application when you last exited it. You must delete these files before you install the new version of Site Manager on your PC or Site Manager may not function properly when you restart it.
- Page 15 Caution: Installing Site Manager will overwrite any existing c:\windows\siteman.ini file. To run multiple versions of Site Manager on the same PC, make a copy of the current Site Manager initialization file, siteman.ini, before you install a new version of Site Manager. Be sure to rename the copy with a new file name.
- Page 16 Loading the BayStream Site Manager Software on a PC To load the Site Manager software onto a PC: 1. Insert the BayStream software CD into the CD-ROM drive. 2. Start Windows. 3. Double-click on the File Manager icon if you are using Windows 3.1 or later, or choose Start >...
- Page 17 Do you want to start Site Manager now? 10. Click on Yes to start Site Manager, or click on No to return to Windows. When you finish upgrading the Site Manager software on a PC, see “Task 3: Loading BayStream Multiservice Software onto a PC or UNIX Workstation”...
- Page 18 Deleting Existing State Files Site Manager creates state files for all Site Manager tools you use. State files describe the state of the application when you last exited it. You must delete these files before you install the new version of Site Manager on your SPARCstation or Site Manager may not function properly when you restart it.
- Page 19 SPARCstation To load the Site Manager software on your SPARCstation: 1. Insert the BayStream software CD into the CD-ROM drive. 2. If you have not created a CD-ROM mountpoint, log in as root and create a root-level directory. For example, type: mkdir /cdrom 3.
- Page 20 4. To change to the CD-ROM mountpoint, type: cd /cdrom or, if you use Solaris and are running the vold daemon, type: cd /cdrom/release_720_720 5. To start the script to load the Site Manager software, type: . / install.sh The installation process: •...
- Page 21 Additional messages about your SPARCstation environment may appear. 6. Press Control-D to exit the root account. When you finish upgrading the Site Manager software on the SPARCstation, see Software onto a PC or UNIX Upgrading BayStream Site Manager on an RS/6000...
- Page 22 Deleting Existing State Files Site Manager creates state files for all Site Manager tools you use. State files describe the state of the application when you last exited it. You must delete these files before you install the new version of Site Manager on your RS/6000 or Site Manager may not function properly when you restart it.
- Page 23 <device_number> is the number of the device assigned to the CD-ROM drive. 4. To change to the CD-ROM mountpoint, type: cd /cdrom 5. To start the script to load the Site Manager software, type the following command in all lowercase letters: . /install.sh...
- Page 24 Task 3: Loading BayStream Multiservice Software onto a PC or UNIX Workstation You can load the BayStream Multiservice Software from its CD onto either a PC or a UNIX workstation. See the section that applies to your BayStream platform type: •...
- Page 25 Loading the BayStream Multiservice Software onto a PC To load the BayStream Multiservice Software onto a PC: 1. Insert the BayStream software CD into the CD-ROM drive. 2. Start Windows. 3. Double-click on the File Manager icon if you are using Windows 3.1x or choose Start >...
- Page 26 Loading the BayStream Multiservice Software onto a UNIX Workstation To load the BayStream Multiservice Software onto a UNIX workstation: 1. Insert the BayStream software CD into the CD-ROM drive. 2. If you have not created a CD-ROM mountpoint, log in as root and create a root-level directory.
- Page 27 Manager Version 7.2, the CD-ROM will automatically be mounted as /cdrom/release_720_720. 4. Change directories by typing: cd /cdrom 5. Start the script to load the BayStream Multiservice Software using one of the following commands: • On a SPARCstation, type: ./COPY.SH •...
- Page 28 Task 4: Backing Up the Current BayStream Software Image File You should back up the BayStream software image files currently stored on the BayStream platform onto your PC or workstation. It is important to maintain backup copies of these files to ensure that you can restore platform operation in case malfunctions occur during the upgrade process.
- Page 29 Preparing the BayStream Platform to Receive a New Software Image Before you can transfer a new software image to the BayStream platform you want to upgrade, you must prepare a flash memory card (provides storage for installation and configuration files) to receive the image file.
- Page 30 You saved a copy of the current boot image when you performed Task 4: Backing Up the Current Software Image File. 2. Delete the current BayStream software image from the flash memory card. In the File Manager window, choose Commands > Delete.
- Page 31 You should use two flash memory cards in each BayStream platform you upgrade. This allows you to keep the active (for example, Version 7.1) software image on one flash card while you use the TFTP command in Site Manager to transfer the new (Version 7.2) image to another flash memory card designated for the upgrade.
- Page 32 You do this as a safeguard in case your flash card malfunctions. 3. Use the Router Files Manager to display the file names on the flash memory card on which you stored the upgraded software (referred to as the “upgrade flash memory card”).
- Page 33 6. Click on OK in the confirmation window. An hourglass appears for the duration of the file compaction. After several minutes, a window displays the following message, where x is the volume you are compacting: Last file system command, “compact x:”, finished successfully.
- Page 34 2. Choose File > TFTP > Put File(s). The TFTP Put File Selection window opens, invoking the TFTP software to execute file transfer. 3. In the Path field, type the path to the directory on the Site Manager workstation that contains the image file you want to transfer to the flash memory card.
- Page 35 5. Click on Add. The selected file appears in the Files to Put list. If you inadvertently add a file that you do not want to transfer, choose that file in the Files to Put window and click on Remove. 6.
- Page 36 The Router Files Manager transfers the file. If a file of the same name already exists in that directory, the transferred file overwrites it. If the file transfer fails, check your setup for the TFTP operation. Then try to transfer the file again. If you need assistance, call the Bay Networks Technical Solutions Center nearest you.
- Page 37 BayStream platform with the new configuration file. Note: If you are upgrading a configuration file from a version earlier than BayStream Version 7.1 (such as BNX Version 7.1), refer to Upgrading to BayStream 7.1 for instructions on saving and converting current configuration files.
- Page 38 Booting with a Version 7.1 Configuration File To upgrade a Version 7.1 configuration file to Version 7.2, boot it on a BayStream platform running the Version 7.2 software image. This software loads the configuration file currently in memory and updates the configuration file’s MIB stamp to match the Version 7.2 software.
- Page 39 3. Type a new file name to save the configuration file on the BayStream platform, using the following format: <filename>. cfg Where <filename> is the name you are assigning this file and .cfg specifies the file type. For example, type the file name, config7200.cfg. Caution: Do not use the file name config, which is the default configuration file name for BayStream.
- Page 40 1. Select Administration > Boot Switch. The Boot Switch window displays default file names for the software image and the configuration file. The default volume is the first available flash memory card (indicated by slot number).
- Page 41 Make sure you give the other configuration file a name other than config (for example, config7200_new.) Task 7: Distributing the Changes to Redundant Memory Cards After you establish confidence in running BayStream 7.2, distribute the image and configuration files to redundant memory cards.
- Page 43 BayStream platform rebooting with a new configuration file, 32 to 33 software image size, 2 WinSock compatibility, 2 BayStream Site Manager deleting state files PC, 6 RS/6000, 14 SPARCstation, 10 UNIX workstation, 10, 14 installing multiple versions, 7 loading on a PC, 8 to 9...
- Page 44 CD, 17 Index-2 rebooting the BayStream platform, 32 to 33 Router Files Manager backing up router software, 20 transferring a software image, router software backing up, 20 copying to a PC, 17 loading from CD, 16...
- Page 45 TCP/IP stack, upgrading on a PC, Technician Interface, backing up router software, 20 testing the customized image, 21 transferring software images, 26 to UNIX workstation deleting state files from, 10, 14 loading router software from CD, 16, 18 to 20...