3Com NETBuilder® Management Version 1.0.1 for the SunNetTM Manager System

Modified: 02/11/96

3Com NETBuilder® Management

Version 1.0.1 for the SunNetTM Manager System

Software Release Notes

For 3Com User Group Information
1-800-NET-3Com
or your local 3Com office

Part No. 86-0382-001
Published August 1992. Printed in the U.S.A.

3Com Corporation 5400 Bayfront Plaza Santa Clara California 95052-8145

© 3Com Corporation, 1992. All rights reserved. No part of this manual 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. 3Com Corporation reserves the right to revise this publication and to make changes in content from time to time without obligation on the part of 3Com Corporation to provide notification of such revision or change. 3Com Corporation provides this guide without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. 3Com may make improvements or changes in the product(s) and/or the program(s) described in this manual at any time. Use, duplication, or disclosure by the government shall be expressly subject to restrictions as set forth in subparagraph (c) (1) (ii) for restricted Rights in Technical Data and Computer Software clause at 252.227-7013 of the DOD FAR Supp. 3Com and NETBuilder are registered trademarks of 3Com Corporation. Open Windows, SunNet and SunOS are trademarks of Sun Microsystems, Inc.

3Com NETBuilder Management

Version 1.0.1 for the SunNet Manager System

Software Release Notes

These release notes accompany 3Com® NETBuilder® Management version 1.0.1, which is distributed on CD-ROM. Your CD contains two versions of 1.0.1: one runs with SunNetTM Manager 1.2 with OpenWindowsTM 2.0 and the other runs with SunNet Manager 2.0 with OpenWindows 3.0. Except for the installation procedure, these release notes describe version 1.0.1, which runs with SunNet Manager 2.0 unless otherwise stated.

If you are using SunNet Manager 1.2, refer to the NETBuilder Management for SunNet Manager Network Administrators Guide for additional information.

These release notes provide the following information on version 1.0.1:

n Compatibility information
n Changes since 3Com NetBuilder Management version 1.0
n Upgrading from SunNet Manager 1.2 to SunNet Manager 2.0
n 3Com NETBuilder Management version 1.0.1 preinstallation
n NETBuilder Management version 1.0.1 for SunNet Manager installation
n Known problems
n Limitations

NOTE: Whenever information in these release notes differs from information provided in the manual that accompanied your software, follow the release notes.

Compatibility

This section provides important compatibility information on the 3Com NETBuilder Management version 1.0.1 application.

n The NETBuilder Management application supports NETBuilder Bridge/Routers running version 5.0 software or later. It supports earlier versions of NETBuilder software to the extent of the MIB support provided. Most pre-5.0 versions of NETBuilder software are limited to MIB II support.

n The NETBuilder Management application operates with SunNet Manager version 1.2 with OpenWindows 2.0 or SunNet Manager version 2.0 with OpenWindows 3.0.

Changes Since 3Com NETBuilder Management Version 1.0

This section describes the changes in this version of 3Com NETBuilder Management from what is printed in the manual.

Installation Program

The following changes were made to the installation program:

n Some changes in the installation procedure have been made. These are fully described later in this release note in the section Installing 3Com NETBuilder Management for SunNet Manager Version 1.0.1.

n During installation, the 3Com NETBuilder Management and SunNet Manager versions are checked before any files are changed. If the version numbers do not match, or if SunNet Manager is not installed, you are notified. If the version numbers do match, installation proceeds.

n The Installer Graphical User Interface (GUI) for SunNet Manager is linked with OpenWindows 3.0 libraries instead of OpenWindows 2.0.

n The installation program now displays the following error message if the GUI cannot be launched because the X server is not running or the X server cannot be accessed:

3Com NETBuilder Management Version 1.0.1

Checking for OpenWindows ...

Xlib: connection to <machine name>:0.0 refused by server
Xlib: Internal error during connection authorization check
/usr/openwin/bin/xdpyinfor: unable to open display <machine name>

ERROR: installer must be run under OpenWindows

X server display: <machine name>:0
X Client: <machine name>
User: <user id>

If OpenWindows is not already running on the X server
start OpenWindows now and rerun this script: ./3Com_install

IF OpenWindows is already running on the X server and
you <user id> are not authorized to access the server, then

1. Add the magic cookie for the X server to your ~/.Xauthority
(See man xauth) OR

2. Ask the user logged in under the X server to run the command
xhost <machine name> to grant you access

/usr/tmp/unbundled/install_unbundled_3Com: installation aborted

extract_unbundled completed

n The following changes are made to the list of interface icons on p. 3-6 of the Network Administrator's Guide:

A new icon for SMDS interfaces has been added. It looks just like the PLG, X.25, and PPP icons, but has the letters "SMDS" instead.

The "unknown" icon, in case anybody was wondering, should not appear for current Brouter software. It will appear if future versions of the Brouter software (e.g., 5.2, 6.0) add additional interface types.

There is a bug in the SNM 1.2 version: the X.25, SMDS, and "unknown" icons do not appear when they should. No icon is shown at all for an X.25, SMDS, or unknown interface. This bug also occurs in BuildMan 1.0. This has been fixed in the SNM 2.0 version of BuildMan 1.0.1.

3COM Installation Program Window

These Installation Program Window selections function as follow:

n A new button, Modify SNM Console Properties, has been added to the 3Com Installation window. Use this button to update your ~/ .SNMdefaults file. This option allows other users besides the installer to configure their respective default files to include 3Com NETBuilder Management information.

n The Properties... button brings up the 3Com Installer:Properties window. This window specifies where you can save a recording of actions you have taken during installation and the actions taken by the the 3Com Installation Program. The log is saved to the file specified in the Properties window by the Destination and Logfile entries.

n The Install... button brings up the 3Com Installer:Install window, which allows you do one of the following:

Copy and integrate the selected 3Com UNIX® application with SunNet Manager.

Integrate the selected 3Com UNIX application with SunNet Manager after the application was copied to the hard disk. Use this option if you copied a 3Com application onto the hard disk and then loaded SunNet Manager. You may also use this option if you intend to install a different version of SunNet Manager. If you are using the default path, you can execute the installer from the following directory:

home/3Com.nm/common/install/

Copy the selected 3Com UNIX application onto the hard disk. Use this option if you do not have the right version of SunNet Manager installed but you want a 3Com application loaded onto the hard disk.

n The Uninstall option in the 3Com Installation window now backs up user files and removes selected script files; it did not do this previously. The Uninstall... button brings up the 3Com Installer:Uninstall window, which allows you do one of the following:

Remove the selected 3Com UNIX application and the corresponding SunNet Manager changes from the hard disk

Remove the SunNet Manager changes for the selected 3Com UNIX application from the hard disk

Remove the selected 3Com UNIX application from the hard disk

n The Run Diagnostics button provides information on system configuration, SunNet Manager, OpenWindows, Filesystem Usage, IPC usage, IPC status, Common SunNet Manager Modification checks, Product Dependency checks, and Product SunNet Manager Modification checks. Any detected errors or warnings are provided.

n The Modify SNM Console Properties button updates the .SNMdefaults file in the user's home directory to contain the user selections for the SNM Console Properties.

Customize

The following changes were made to the Customize feature in version 1.0.1. These changes apply only to version 1.0.1 running with SunNet Manager 2.0. These changes do not apply to version 1.0.1 running with SunNet Manager version 1.2.

n The SunNet Manager Customize feature no longer modifies the SNMP Proxys hosts file. The nb-snmp.all combined-schema file is no longer used.

n The Customize feature obtains community strings for SNMP requests from the SunNet Manager database, instead of the SNMP Proxys file.

n When you use the -u (uncustomize) command line option , NETBuilder units are converted to routers, not generic workstations.

n When an attempt to determine the system type does not succeed, the following error message is displayed:

<system>: no response to SNMP queries

This message was previously displayed:

<system>: no response

Report Writer

The following changes were made to the Report Writer feature for NETBuilder Management version 1.0.1 running with SunNet Manager 2.0. These changes do not apply to version 1.0.1 running with SunNet Manager version 1.2.

n The event response fields in one property frame have changed to match the new event handling options in SunNet Manager 2.0.

n The 3Com.nm file and its man page have been changed to reflect the new event handling options.

n Report Writer has been linked with OpenWindows 3.0 libraries instead of OpenWindows 2.0.

NETBuilder Management Application

The following changes were made to the 3Com Management Applications for NETBuilder Management version 1.0.1 running with SunNet Manager 2.0. These changes do not apply to version 1.0.1 running with SunNet Manager version 1.2.

n Smart Telnet automatically invokes line-mode after you log into the NETBuilder application.

n Version 1.0.1 has been linked with OpenWindows 3.0 libraries instead of OpenWindows 2.0.

n The per-port Spanning Tree property frame now displays an error message in the frame footer if the attempt to use Apply fails.

n The per-port Source Routing list boxes have been correctly labeled. Non-source route ports are no longer listed. If you invoke the property frame from a non-source route port icon, an error message is displayed in the footer. The default MaxAreRDLimit is now 8.

n The option 3Com Customize has been added to the Tools menu for generic router, server, and workstation icons.

In version 1.0, the option 3Com Customize appeared only in the SunNet Manager menus for generic workstations, subnets, and clouds because the SunNet Manager 1.2 Discovery feature classified all 3Com products as generic workstation.

The SunNet Manager 2.0 Discovery feature classifies 3Com products more specifically as routers, servers, or client workstations.

n The abbreviated scroll buttons on the Interfaces field on the NB System Configuration Properties screen have been removed.

Upgrading From SunNet Manager 1.2 to SunNet Manager 2.0

You cannot upgrade to SunNet Manger 2.0 if you have NETBuilder Management version 1.0 or NETBuilder Management version 1.0.1 for SunNet Manger 1.2 installed on your machine. If you have either version of these applications installed and you would like to upgrade to SunNet Manager 2.0 from SunNet Manager 1.2, do the following:

1. You must remove NETBuilder Management and all other 3Com network management products for SunNet Manager 1.2.

Use the Installer programs Uninstall option from the 3Com Installation window. You must remove the entire NETBuilder Management application from the disk. It is not sufficient to just undo the SunNet Manager changes.

2. Install SunNet Manager 2.0.

Refer to the SunNet Manager documentation.

3. Install NETBuilder Management version 1.0.1 for SunNet Manager 2.0.

Refer to the Before Installing 3Com NETBuilder Management Version 1.0.1 section in these release notes.

Before Installing 3Com NETBuilder Management Version 1.0.1

This section provides information that is useful to know before you start the installation.

n You need to know the workstation superuser password.

Although it is possible to complete the installation without the superuser password, the superuser password may be necessary to complete an installation.

n When installing 3Com NETBuilder Management version 1.0.1 over version 1.0, you may receive a permission denied error when the new files are copied. This error also may occur if the user installing version 1.0.1 is not the same user that installed version 1.0, or if the user installing the software does not belong to the same user group. To correct this problem, you can do one of the following steps:

Install NETBuilder Management version 1.0.1 while you are logged in as the same user that installed version 1.0.

Log in as the user that installed version 1.0 or as root. Change the file permissions to give the user write access. To accomplish this task, change the directory to the 3Com Network Management applications directory with the following command:

cd /home/3Com.nm

NOTE: The default value for 3Com Network Management applications is /home/3Com.nm. This is the 3Com_default_directory for /etc/nmhome.nm. If you specify a different value as the default directory, then wherever /home/3Com.nm is referenced, you must substitute the value you entered in the file nmhome.nbm. If this application is not the first 3Com UNIX application installed then the 3Com_default_directory may be named something other than /home/#Com.nm.

If version 1.0 was installed to a directory other than the default directory /home/3Com.nm, use the cd command to change to that install directory.

Use the following command to change to the install directory:

cd install

If the new user is not part of the same user group, use the following command:

chown_dir <owner>.<group> /home/3Com.nm

n Installation should be performed by the same user who will run the application, or at least by a member of the same user group. Otherwise, the chgrp command is required.

n Only users in the original installers group can install other 3Com network management applications. Otherwise, the chgrp command is required.

n When 3Com NETBuilder Management is installed, the user performing the installation becomes the owner of all files. This users default group, as it appears in /etc/passwd, or NIS, becomes the group owner of all files.

n The installation and customization procedures described in Chapter 2 of the NETBuilder Management Network Administrators Guide modify the SunNet Manager files, /etc/snm.conf and /var/adm/snm/snmp.hosts, only on the local workstation. If you want to configure SunNet Manager to use a remote SNMP proxy, refer to the SunNet Manager documentation to configure the remote /etc/snm.conf and /var/adm/snm/snmp.hosts files manually. This action informs the remote SNMP proxy about NETBuilder MIBs.

NOTE: The /var/adm/snm directory is the default directory that is created when SunNet Manager is installed. The SunNet Manager files may not be located in this directory if you specify a different location for the SunNet Manager files during installation.

n After you install the NETBuilder Management application, do not change the last modified date of files in the /home/3Com.nm/common and /home/3Com.nm/install directories or subdirectories, where /home/3Com.nm is the directory specified for installing 3Com management applications (/home/3Com.nm by default).

If you install another 3Com management application, such as LinkBuilder 3GH MS, the dates of the common files already installed are compared with the common files from the new application. If the dates of the NETBuilder Management files have been changed, the older files may not be replaced by the newer files from the new application.

File Permissions Required by the Installer

n Before the software is installed, the superuser should be sure that the installer has write permission to these files and directories:

/etc/snm.conf
/var/adm/snm/oid.dbase
/usr/snm
/usr/snm/defaults
/var/adm/snm/snmp.hosts (required for version 1.0.1 running with SunNet Manager 1.2 only)

If the default name and location of the files, oid.dbase.hosts or snmp.hosts, have been changed and are not as listed here, the installer needs write permission to the renamed and/or relocated files.

n The installer also needs write permission to the directory /usr/tmp/unbundled.

n If this is the first 3Com network management application to be installed on your workstation, the installer also needs write permission to the /etc directory to create the file /etc/nmhome.3Com. The application trees location will be placed into this file during installation.

Installing NETBuilder Management Version 1.0.1 for SunNet Manager

NETBuilder Management for SunNet Manager is distributed on CD-ROM. The CD contains two versions of 3Com NETBuilder Management for SunNet Manager: one that runs with SunNet Manager 1.2 and one that runs with SunNet Manager 2.0. During the installation, select the version you need when prompted.

The following procedure describes how to install NETBuilder Management version 1.0.1 for SunNet Manager. Use this procedure whether you are installing the software from a directly connected or remotely accessed CD drive. This procedure assumes that you are familiar with SunNet Manager and OpenWindows.NETBuilder Management applicationinstalling

NOTE: You must repeat this procedure for each 3Com network management software program you are installing (for example, LB3GH MS or RBCS 2.0). You can install the programs in any combination and in any order. installing NETBuilder Management application

Installing NETBuilder Management for SunNet Manager involves the following five main procedures. Complete the following sections in sequence:

n Save the existing SunNet Manager database

n Mount the CD-ROM

n Install the 3Com Installer program

n Install the NETBuilder Management application

n Modify SunNet Manager

n Reinitialize SunNet Manager

If you encounter problems during the installation, refer to the section Troubleshooting the Installation later in this chapter.

Saving the Existing SunNet Manager Database

Because the installation process makes changes to SunNet Manager schema files, you need to save the database so that SunNet Manager can be reinitialized with the new schemas. The saved database also acts as a backup in case of an unsuccessful installation.

Follow these steps to save the SunNet Manager database:

1. Make sure that you are in OpenWindows.

If you need to enter OpenWindows and it has not been moved from its default directory, enter the following command from any directory to start it:

/usr/openwin/bin/openwin

2. Run SunNet Manager from OpenWindows.

If SunNet Manager is in its default location, enter the following command from any directory to run it:

/usr/snm/bin/snm

The SunNet Manager window appears as follows:

Figure 2-2. SunNet Manager Base Window

3. Press MENU on File and choose Load/Save (SunNet Manager 1.2) or Save... (SunNet Manger 2.0).

The SunNet Manager Load/Save or Save window is displayed.

4. Enter a temporary destination directory, or use the default directory and filename for the saved database.

In Figure 2-3, the database file has been saved in a file called saved.file in the directory /home/bmm.

Figure 2-3. SunNet Manager 2.0 Save Window

5. Click SELECT on Save.

6. Exit SunNet Manager.

Choose Quit from the Window options to exit the application.

Mounting the CD-ROM

If you are using a directly accessed workstation, continue to the next section Mounting the CD-ROM from a Directly Connected CD Player. CD-ROMmounting for installation

If you are accessing CD-ROM from another workstation, proceed to the section Mounting the CD-ROM from a Remotely Accessed CD player.

Mounting the CD-ROM from a Directly Connected CD Player

Follow these steps to mount the CD-ROM from a directly connected CD player:

1. Open a command tool window.

2. Place the CD containing the SunNet Manager software in the caddy and insert the caddy into the CD player.

3. Check whether the CD-ROM is mounted by typing the following command:

mount | grep cdrom

If you receive no output (for example, 1:iomm @kuna%) from the command, you must mount the CD-ROM. Use the following commands:

su
mkdir /cdrom
mount -r /dev/sr0 /cdrom

Perform the second command only if the /cdrom subdirectory does not already exist.

Continue to Installing the Installation Program from CD-ROM.

Mounting the CD-ROM from a Remotely Accessed CD Player

If you are accessing a CD-ROM on another workstation, follow this procedure:

On the remote workstation, complete the following steps:

1. From a command tool window, enter the following commands:

su
mkdir /cdrom
mount -r /dev/sr0 /cdrom

2. If the /etc/exports file exists, edit it by adding the following line:

/cdrom -ro

If the /etc/exports file does not exist, create it.

3. If the /etc/exports file existed previously, enter the following command:

/usr/etc/exportfs /cdrom

If the /etc/exports file did not exist previously, reboot the workstation to become an NFS server.

4. On the local workstation (the workstation on which you are installing NETBuilder Management for SunNet Manager), enter the following commands to mount the CD-ROM:

su
mkdir /cdrom
mount -r <remote_workstation>:/cdrom /cdrom

Installing the Installation Program from CD-ROM

The installation program must be run from OpenWindows. Complete the following steps to install the installation program:

1. At the system prompt, enter the following command: CD-ROMinstalling from

cd /cdrom/bin

2. Start the installation process by entering the following command:

./extract_unbundled

The system displays some messages in the command tool window and then prompts you as follows to specify whether your workstation is running SunNet Manager 1.2 or 2.0:

Products on this CD-ROM:

1. NB_Manager_SNM1.2--3Com NETBuilder Management Version 1.0.1 for SunNet Manager 1.2

2. NB_Manager_SNM2.0--3Com NETBuilder Management Version 1.0.1 for SunNet Manager 2.0

Select product (1 to 2, <cr> to abort):

3. Enter 1 if you are using SunNet Manager 1.2, or 2 if you are using SunNet Manager 2.0.

The system then displays copyright information and prompts you as follows to continue:

Do you want to continue (y|n)?

4. Enter y to continue in response to the prompt.

The following message appears:

I am going to remove /usr/tmp/unbundled and its contents. Continue (y|n)?

5. Enter y to continue.

If this is the first 3Com management application that you have installed, you will be prompted as follows to accept the default directory nmhome.nm for the /home/3Com.nm directory as the location for the installed application:

Accept default /<3Com_default_directory> (y|n)?

You have not specified where to install 3Com NETBuilder Management version 1.0.1. If you want to install the NETBuilder Management application in a different directory, type n and enter that directory when prompted.

It is recommended that you do not specify a path that is very long because of a SunNet Manager 1.2 maximum pathname character limitation.

6. Enter y to continue.

If a previous version of this software exists, the following message is displayed:

I will use the value found in /etc/nmhome.3Com <3Com_default_directory>
It looks like 3Com NETBuilder Management Version 1.0.1 (or an earlier version) has already been installed there.
Do you want to install over it (y|n)?

7. Enter y at the prompt to continue.

The following message is displayed:

3Com NETBuilder Management Version 1.0.1 will be installed in <3Com_default_directory>, OK (y|n)?

8. Enter y at the prompt to continue.

The installation program needs to create a file called /etc/nmhome.3Com if it does not already exist.

If this file already exists, the 3Com Installation window appears. Continue to Using the 3Com Installation Window to Install the NETBuilder Management Application.

If this file does not exist and you do not have write permission for the /etc directory, the system displays a message stating that you do not have write permission to some files needed for installation and ends as follows:

The <3Com_default_directory>/install/grant script/program must be run as user root.

Do you have the root password (y|n)?

9. If you do not know the root password, enter n and the installation will continue without write permission to the necessary files.

Continue to Using the 3Com Installation Window to Install the NETBuilder Management Application.

If you know the superuser password, enter y to continue. You are prompted as follows to enter the superuser password:

Password:

If you enter the incorrect password, you will be prompted to reenter the password.

10. Enter the superuser password.

You are prompted to grant write permission to a number of files as they are listed on the screen.

11. Enter y as prompted after each file to continue.

After you give write permission to the last file, the 3Com Installation program window appears. Go to the next procedure.

Using the 3Com Installation Window to Install the NETBuilder Management Application

After you complete the installation described in previous procedure, the 3Com Installation program window should be displayed on your workstation screen (Figure 2-5).

Figure 2-5. 3Com Installation Program Window

Complete these steps to install the NETBuilder Management application:

1. Check that NETBuilder Management for SunNet Manger 1.0.1 is selected; if not, select it.

2. Click SELECT on the Install button.

The 3Com Installer Install pop-up window is displayed (Figure 2-6).

Figure 2-6. 3Com Installer Pop-up Window

3. Select the option Copy to disk and integrate with SunNet Manager if it is not already selected.

NOTE: If you do not have SunNet Manager installed, you can load NETBuilder Management by selecting Copy to disk only. After installing the SunNet Manager version you want, start the 3Com Installer and select Integrate with SunNet Manager only.

4. Click SELECT on the Install button.

The installation program displays messages on the screen and prompts you as follows (Figure 2-7):

Figure 2-7. Installation Directory Prompt

5. Enter y to continue.

More messages are displayed on the screen ending with the following prompt:

***Please insert the CD into the CD player if you have not done so already. Press return when ready...

6. Press [Return] to continue.

Copyright information about the product is displayed and then you are prompted as follows:

Do you want to continue (y|n)?

7. Enter y to continue.

The program then extracts the application from CD-ROM, listing the files as they are extracted. After all the files have been extracted, the installation program generates some messages on the screen, ending with the following message:

./nb_install:3Com NETBuilder Management Version 1.0.1 installed successfully
...
SunNet Manager modification takes about 2 minutes.
I am going to use <3Com_default_directory>, OK (y|n)?

8. Enter y to continue.

The system reminds you to save your SunNet Manager database with a message that ends in the following prompt:

Do you want to continue (y|n)?

9. Enter y to continue.

The installation program continues displaying messages as it modifies the SunNet Manager files.

You may be prompted here to become superuser and grant permission to files that are listed on the screen. If this occurs, enter the superuser password and grant permission to the files as instructed in steps 9, 10, and 11 of the previous procedure Installing the Install Program from CD ROM.

The system indicates as follows that the installation has been completed:

SunNet Manager modified successfully for 3Com NETBuilder Management Version 1.0.1.

10. Quit the 3Com Installation Program window.

Click SELECT in the 3Com Installation Program header and select Quit.

11. Make the following changes to the .login and .cshrc (C-shell) and .profile files (Bourne shell) files.

These changes allow you to use the man pages for the 3Com application and execute the 3Com application from the command line:

n Add source <3Com.nm directory name>/nbapp.login to the .login file.
n Add source <3Com.nm directory name>/nbapp.csh to the .cshrc file.
n Add <3Com.nm directory name>/nbapp.sh to the .profile file. The 3Com.nm directory name is the value in /etc/nmhome.3Com.

Reinitializing SunNet Manager SunNet Managerreinitializing

Follow these steps to reinitialize SunNet Manager:

1. Restart SunNet Manager.

Enter the following command in a command tool window if SunNet Manager is installed in its default location:

/usr/snm/bin/snm -i &

The system displays messages and filenames while it restarts SunNet Manager and reloads the SunNet Manager schema files so the 3Com modifications can take effect. After it has finished, the SunNet Manager window is displayed.

2. Restore the saved SunNet Manager database.

Press MENU on File and choose Load/Save (SunNet Manager 1.2) or Load (SunNet Manager 2.0). If you are running SunNet Manager 1.2, the Load/Save window is displayed. If you are running SunNet Manager 2.0, the Load window is displayed.

Figure 2-10. SunNet Manager 2.0 Load Window

3. Enter the name under which you saved the database in step 4 of the procedure Saving the Existing SunNet Manager Database. Or, in SunNet Manager 2.0, click on the proper name in the list box.

4. Click SELECT on Load.

The SunNet Manager database is restored.

If all of your NETBuilder Bridge/Routers are already present in the SunNet Manager database, you have completed the installation of NETBuilder Management for SunNet Manager.

Known Problems

The following known problems exist in the NETBuilder Management version 1.0.1 operating with both SunNet Manager 1.2 and SunNet Manager 2.0, unless otherwise stated:

n Property windows in the NETBuilder Management application are not automatically updated if the parameter in question is set using a different method. For example, if you are displaying OSPF interface metrics, and another user changes an OSPF metric through a Telnet session, your NETBuilder Management application does not display the new value until the OSPF interface metrics window is closed and reopened, or until you use the Refresh Data option from the Tools menu.

n When you enter a numeric value in a range field, the validity of the entry is not checked until you click on the Apply button. If the value is invalid, the setting does not take effect and an error message is displayed.

n When using pre-5.0 NETBuilder software, be careful not to exceed the number of characters specified for the SysLocation and SysNAMe parameters. If you exceed this number, the NETBuilder Bridge/Router may reboot.

Limitations

The following is a limitation of the NETBuilder Management application:

n Only one Smart Telnet session to a NETBuilder Bridge/Router at a time is permitted. If you want to hold more than one Telnet session with the same NETBuilder Bridge/Router, use the standard SunOS Telnet feature for the additional sessions. Refer to the SunOS documentation for more information on how to use this feature.

Only NETBuilder Bridge/Routers running software version 5.0 or later can support more than one Telnet session.

The following limitation exists in SunNet Manager 1.2 but does not occur in SunNet Manager 2.0. This limitation occurs when using the NETBuilder Management application:

n If you attempt to display an event report or data report using attributes from the OSPF LinkState Table (group name ospfLsdbTable), SunNet Manager 1.2 generates the following error message:

invalid key type for ospfLsdbTable: THIRTEEN

SunNet Manager 1.2 cannot read the OSPF link state table.

This limitation does not apply to version 1.0.1 running with SunNet Manager 2.0.

© 3Com Corporation