32NETBUILDER SOFTWARE VERSION 11.1 RELEASE NOTES
Upgrade Management This section contains known upgrade management issues.
Known Issues
bcmdiagnose Error When you execute bcmdiagnose on
/etc/passwd. You must add an entry" can be ignored.
Installation of a new version of the Remote Upgrade Utilities onto a UNIX NMS saves an existing /usr/3Com/bcmutil.conf, into /etc/3Com/bcmutil.conf.backup. This file is used by the Transcend Enterprise Manager for UNIX (TEM/U). If a user has made modifications to this file, they must either restore their original file or add the changes to the new file.
If you are using the Remote Upgrade Utilities in
Unreleased Netscape The NETBuilder software version 11.1 Upgrade Management Utilities requires an Communicator Version unreleased version of Netscape Communicator, 4.05 Preview Release 1 (AWT
1.1.5). This version may be obtained from the following Netscape web site:
http://home.netscape.com/download
SuperStack II NETBuilder If SuperStack II NETBuilder systems that are running software version 8.3 have a Token Ring Upgrades boot image named “bundle.68K,” the SuperStack II NETBuilder Token Ring system
is not upgradable to software version 11.1 unless the sys file is present on the flash drive. To work around this, either rename the image to “boot.68k,” or copy the 8.3 sys file to the primary boot directory on the NETBuilder bridge/router.
Sysupgrade Not Sysupgrade is no longer a supported upgrade management utility. Use of the files Supported upgrade.29k and upgrade.68k is not supported in this release.
IP Address Link When using the Upgrade Management Utilities in a hardware replacement upgrade, you must use the same IP address as previously used for the router if you have already backed up your software onto the network management station. Using a different IP address causes the upgrade to fail.
Concurrent Usage The NETBuilder Upgrade Management Utilities are currently designed to run sequentially. Running multiple simultaneous instances of bcmbackup, bcmsysupgrade, bcmrestore, and bcmdiagnose is not supported at this time.
bcmdiagnose and
tftp::510:200:,,,:/tftpboot:/bin/false
See the
bcmfdinteg Read the following warning regarding the bcmfdinteg utility.