|
HUBwatch for HP-UX V4.0, Release Notes
This document contains information not included elsewhere in the HUBwatch
for HP-UX V4.0 product documentation.
PLEASE READ THESE NOTES BEFORE INSTALLING OR USING THE SOFTWARE.
July 17, 1995
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is
subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights
in Technical Data and Computer Software clause at DFARS 252.227-7013.
Copyright 1995, Digital Equipment Corporation All rights reserved.
The following are trademarks of Digital Equipment Corporation: Alpha AXP,
AXP, Bookreader, DEC, DECagent, DECbridge, DECbrouter, DECconcentrator,
DEChub, DEChub ONE, DECmcc, DECnet, DEC SunOS, DECpacketprobe90, DECrepeater,
DECserver, DECswitch, DECwindows, GIGAswitch, GIGAswitch/FDDI, HUBwatch,
LAT, OpenVMS, PEswitch, POLYCENTER, RoamAbout, ThinWire, VAX, VAX DOCUMENT,
VMS, and the Digital logo.
The following are third-party trademarks:
Motif, OSF, and OSF/1 are registered trademarks of the Open Software
Foundation, Inc.
SunOS and SunNet Manager are trademarks of Sun Microsystems, Inc.
OpenView is a registered trademark of Hewlett-Packard Company for
computer programs with network systems and user manuals supplied therein.
HyperHelp and Xprinter are trademarks of Bristol Technology Inc.
Contents_______________________________________________
1 Introduction.............................................................1
2 User Information.........................................................1
3 Firmware Requirements....................................................1
4 Software Requirements....................................................2
5 HUBwatch Files...........................................................2
5.1 Setting Environment Variables..........................................6
5.2 Resource Files.........................................................6
5.3 Agent File.............................................................7
6 Launching HUBwatch from HP OpenView......................................7
7 Warnings, Known Problems, and Restrictions...............................8
7.1 Agent Setup and Configuration Issues...................................8
7.2 General HUBwatch Use Issues............................................8
7.3 LAN Interconnect and NMS Connectivity Issues..........................10
7.4 Module Specific Issues................................................12
7.4.1 DECagent Issues.....................................................12
7.4.2 DECmau 900TH Issues.................................................13
7.4.3 DECbridge/DECswitch/PEswitch Issues.................................13
7.4.4 DECrepeater/PORTswitch Issues.......................................13
7.4.5 DECserver Issues....................................................15
7.4.6 GIGAswitch/FDDI Issues..............................................16
7.4.7 RouteAbout Access Issues............................................16
7.4.8 DECpacketprobe/PROBEwatch Issues....................................16
8 Known Errors in the Documentation.......................................17
8.1 Errors in the HUBwatch Installation and Configuration Manual..........17
8.2 Errors in the HUBwatch Use Manual.....................................17
HUBwatch for HP-UX V4.0, Release Notes iii
iv HUBwatch for HP-UX V4.0, Release Notes
1 Introduction
Version 4.0 of the HUBwatch for HP-UX is the first release of the HUBwatch
application on HP-UX.
2 User Information
The HUBwatch for HP-UX user information set consists
of both hardcopy and online information.
o The HUBwatch Installation and Configuration manual describes how to
install and configure HUBwatch software and how to configure the
network modules in the DEChub 90 and DEChub 900 MultiSwitch hubs.
______________________________Important ____________________________
Important setup and configuration information about the DEChub 90,
the DEChub 900 MultiSwitch, and the DEChub modules is contained in
the HUBwatch Installation and Configuration manual.
____________________________________________________________________
o The HUBwatch Use manual describes how to use the HUBwatch graphical
user interface and the network module management windows and provides
some troubleshooting information.
o The HUBwatch online hyperhelp contains all the information provided
in the HUBwatch Use manual plus descriptions of the management windows,
step-by-step management procedures, context sensitive help for labels
and fields on the management windows, and a tutorial for getting
started.
______________________________Important ____________________________
HUBwatch for HP-UX V4.0 uses hyperhelp files that are common with
HUBwatch for Windows V4.0. Therefore, there will be references to
Windows-specific information that does not apply
to HUBwatch for OSF/1 V4.0.
____________________________________________________________________
3 Firmware Requirements
The revision firmware supported by HUBwatch for HP-UX V4.0 software is listed
below.
DECagent 90 ....................... V3.0.0
DECbridge 90/90FL ................. V4.0
DECbridge 900MX ................... V1.5.0
DECbrouter 90T1/90T2/90T2a ........ 9.14(1)
HUBwatch for HP-UX V4.0, Release Notes 1
DECconcentrator 900MX ............. V3.0.0
DECconcentrator 900TH ............. V3.0.0
DEChub 900 MultiSwitch Hub Manager V4.0.0
DECmau 900TH ...................... V1.1.0
DECmau 900TL ...................... V1.1.0
DECrepeater 90FS .................. V1.1
DECrepeater 90TS .................. V1.1.0
DECrepeater 90T-16 ................ V1.0
DECrepeater 900FL ................. V1.1.0
DECrepeater 900SL ................. V1.1.0
DECrepeater 900TL ................. V1.1.0
DECrepeater 900FP ................. V1.1
DECrepeater 900GM ................. V1.1
DECrepeater 900TM ................. V1.1
DECserver 90M ..................... NAS V1.3.
DECserver 90TL .................... BL44, or NAS V1.3
DECserver 900TM ................... NAS V1.3, BL80-29
DECserver 900GM ................... NAS V1.3, BL80-29
DECswitch 900EE ................... V1.1.0
DECswitch 900EF ................... V1.5.0
GIGAswitch/FDDI SCP Card .......... V2.20 DL1.00 BB2.00
GIGAswitch/FDDI Clock Card ........ V2.10
GIGAswitch/FDDI FGL-2 Line Card ... V2.20
GIGAswitch/FDDI FGL-4 Line Card ... V2.00
PEswitch 900TX .................... V1.1.0
PORTswitch 900CP .................. V2.0
PORTswitch 900TP .................. V2.0
PORTswitch 900FP .................. V1.2.0
RoamAbout Access Point ............ V1.0.0
It is recommended that the DEChub 900 MultiSwitch Hub Manager firmware be
upgraded before the DEChub 900 modules are upgraded.
4 Software Requirements
HUBwatch for HP-UX V4.0 requires the following software installed and
operating:
o HP V9.0 (or higher) operating system including the following
subsets:
o Motif 1.2
5 HUBwatch Files
The following files are provided with HUBwatch for HP-UX V4.0.
In directory <hubwatch_root_path>:
install_hubwatch
release_notes
question.txt
2 HUBwatch for HP-UX V4.0, Release Notes
The file release_notes is the Release Notes file for HUBwatch for HP-UX V4.0
in ASCII text format (this document).
In directory <hubwatch_root_path>/lib:
Hubwatch_gray Hubloader_gray
Hubwatch_salmon Hubloader_salmon
Hubwatch_tan Hubloader_tan
Hubwatch_teal Hubloader_teal
hubwatch_agents
In directory <hubwatch_root_path>/mib:
hubwatch_mib_master
lib/OV:
hubwatch.50.m
hubwatch.50.p
hubwatch.38.p
hubwatch.sym
hubwatch_fields
hubwatch_reg
oid_to_sym.hw
oid_to_type.hw
readme.hw
The HUBwatch resource files are Hubwatch_gray, Hubwatch_salmon,
Hubwatch_tan and Hubwatch_teal. The file hubwatch_agents is the HUBwatch
agents file template. The file hubwatch_mib_master is the HUBwatch MIB
variable translation database. The files in the OV directory are the files
needed to support HP OpenView.
The HUBloader resource files are Hubloader_gray, Hubloader_salmon,
Hubloader_tan and Hubloader_teal.
In directory <hubwatch_root_path>/bin:
hubwatch - The primary HUBwatch image.
hubloader - The HUBloader application.
In directory <hubwatch_root_path>/uid:
hub_gsw_gui_filter_sum.uid hub_gui_fp_phys_90bezels.uid
hub_gsw_gui_front_panel.uid hub_gui_fp_phys_900bezels.uid
hub_gsw_gui_lc_sum.uid hub_gui_loader.uid
hub_gsw_gui_sys_sum.uid
hub_gui_agent_sum.uid
hub_gui_alarms.uid
hub_gui_brut_counters.uid
hub_gui_brut_port.uid
hub_gui_brut_sum.uid
hub_gui_comm_table.uid
hub_gui_db900.uid
hub_gui_db90_detail.uid
hub_gui_db90_fdb.uid
hub_gui_db90_filter.uid
hub_gui_db90_port_sum.uid
hub_gui_db90_spanning_tree.uid
hub_gui_db90_sum.uid
hub_gui_db90_trfc.uid
hub_gui_dsvr90_sum.uid
HUBwatch for HP-UX V4.0, Release Notes 3
hub_gui_dsvr_counters.uid
hub_gui_dsvr_port.uid
hub_gui_dsvr_sum.uid
hub_gui_dsvr_tl_counters.uid
hub_gui_dsvr_tl_port.uid
hub_gui_dsvr_tl_sessions.uid
hub_gui_find.uid
hub_gui_front_panel.uid
hub_gui_interconn.uid
hub_gui_mod_add_del.uid
hub_gui_poll_int.uid
hub_gui_rpt900_counters.uid
hub_gui_rpt900_dpr.uid
hub_gui_rpt900_port.uid
hub_gui_rpt900_sec.uid
hub_gui_rpt900_sum.uid
hub_gui_rpt90_port.uid
hub_gui_rpt90_sum.uid
hub_gui_sum.uid
hub_gui_tr900th.uid
hub_gui_wc900.uid
hub_msg.cat
These are the HUBwatch Motif user interface (UID) files.
In directory <hubwatch_root_path>/hyperhelp:
app-defaults
bin
help
hoh.hlp
xprinter
hyperhelp/bin:
hyperhelp
hyperhelp/help:
about.hlp agentwin.hlp bridman.hlp
bridwin.hlp brutman.hlp brutwin.hlp
cfg_list.hlp conman.hlp conwin.hlp
frontwin.hlp gabout.hlp gigman.hlp
gigawin.hlp gigfiltr.hlp gtrouble.hlp
howto.hlp lanman.hlp menus.hlp
relinfo.hlp reptman.hlp reptwin.hlp
snmpman.hlp switch.hlp termman.hlp
termwin.hlp trouble.hlp hubload.hlp
hyperhelp/xprinter:
FontMetrics
PSstd.fonts
Xprinter.prolog
rgb.txt
4 HUBwatch for HP-UX V4.0, Release Notes
hyperhelp/xprinter/FontMetrics:
AFM
hyperhelp/xprinter/FontMetrics/AFM:
ACaslon-AltSemibold.afm ACaslon-Italic.afm
ACaslon-Regular.afm ACaslon-Semibold.afm
ACaslon-SemiboldItalic.afm AGaramond-Bold.afm
AGaramond-BoldItalic.afm AGaramond-Italic.afm
AGaramond-Regular.afm AGaramond-Semibold.afm
AGaramond-SemiboldItalic.afm AGaramond-Titling.afm
Americana-ExtraBold.afm Americana.afm
AvantGarde-Book.afm AvantGarde-BookOblique.afm
AvantGarde-Demi.afm AvantGarde-DemiOblique.afm
Barmeno-ExtraBold.afm Bembo-Bold.afm
Bembo-BoldItalic.afm Bembo-Italic.afm
Bembo.afm Blackoak.afm
Bookman-Demi.afm Bookman-DemiItalic.afm
Bookman-Light.afm Bookman-LightItalic.afm
Carta.afm Courier-Bold.afm
Courier-BoldOblique.afm Courier-Oblique.afm
Courier.afm Formata-Italic.afm
Formata-Medium.afm Formata-MediumItalic.afm
Formata-Regular.afm Garamond-Bold.afm
Garamond-BoldItalic.afm Garamond-Light.afm
Garamond-LightItalic.afm GillSans-Bold.afm
GillSans-BoldItalic.afm GillSans-Italic.afm
GillSans.afm Helvetica-Black.afm
Helvetica-BlackOblique.afm Helvetica-Bold.afm
Helvetica-BoldOblique.afm Helvetica-Condensed-Bold.afm
Helvetica-Condensed-BoldObl.afm Helvetica-Condensed-Oblique.afm
Helvetica-Condensed.afm Helvetica-Light.afm
Helvetica-LightOblique.afm Helvetica-Narrow-Bold.afm
Helvetica-Narrow-BoldOblique.afm Helvetica-Narrow-Oblique.afm
Helvetica-Narrow.afm Helvetica-Oblique.afm
Helvetica.afm Kaufmann.afm
Korinna-Bold.afm Korinna-KursivBold.afm
Korinna-KursivRegular.afm Korinna-Regular.afm
Lithos-Black.afm Lithos-Regular.afm
LubalinGraph-Book.afm LubalinGraph-BookOblique.afm
LubalinGraph-Demi.afm LubalinGraph-DemiOblique.afm
LucidaSans-Bold.afm LucidaSans-BoldItalic.afm
LucidaSans-Italic.afm LucidaSans.afm
NewCenturySchlbk-Bold.afm NewCenturySchlbk-BoldItalic.afm
NewCenturySchlbk-Italic.afm NewCenturySchlbk-Roman.afm
Palatino-Bold.afm Palatino-BoldItalic.afm
Palatino-Italic.afm Palatino-Roman.afm
Parisian.afm ParkAvenue.afm
Rockwell-Bold.afm Rockwell-BoldItalic.afm
Rockwell-Italic.afm Rockwell.afm
Souvenir-Demi.afm Souvenir-DemiItalic.afm
Souvenir-Light.afm Souvenir-LightItalic.afm
Symbol.afm Tekton-Bold.afm
HUBwatch for HP-UX V4.0, Release Notes 5
Tekton.afm Times-Bold.afm
Times-BoldItalic.afm Times-Italic.afm
Times-Roman.afm Trajan-Bold.afm
WoodtypeOrnaments-Two.afm ZapfChancery-MediumItalic.afm
ZapfDingbats.afm
These are the HUBwatch Hyperhelp-based on-line help files. On-line help is
invoked through the HUBwatch "Help" pull-down or any of the "Help" push
buttons on the HUBwatch management windows.
In directory <hubwatch_root_path>/man/man1:
hubwatch.1 - This is the HUBwatch man page.
5.1 Setting Environment Variables
The environment variables HUBWATCH_SYSTEM, HUBWATCH_LIBRARY and HHHOME must
be defined before invoking HUBwatch. HUBWATCH_SYSTEM is the root directory
for the HUBwatch installation and HUBWATCH_LIBRARY and HHHOME point to the
'lib' and 'hyperhelp' directories under HUBWATCH_SYSTEM.
HUBloader requires the following environment variables to be set:
HUBWATCH_LIBRARY, HUBWATCH_LOAD and HUBWATCH_HUBLOADER. The directory
HUBWATCH_LIBRARY should contain the file 'hubwatch_agents', and the
directory HUBWATCH_LOAD should contain the file 'dcffiles.dat'. The
user must have permission to write to the directory HUBWATCH_HUBLOADER
since HUBloader creates the status file in that directory.
In the example below, the root directory is assumed to be the default
location, /usr/kits/hubwatch.
The syntax for csh users,
% setenv HUBWATCH_SYSTEM /usr/kits/hubwatch
% setenv HUBWATCH_LIBRARY $HUBWATCH_SYSTEM/lib
% setenv HHHOME $HUBWATCH_SYSTEM/hyperhelp
The syntax for Bourne Shell users
$ HUBWATCH_SYSTEM=/usr/kits/hubwatch
$ export HUBWATCH_SYSTEM
$ HUBWATCH_LIBRARY=HUBWATCH_SYSTEM/lib
$ export HUBWATCH_LIBRARY
$ HHHOME=HUBWATCH_SYSTEM/hyperhelp
$ export HHHOME
5.2 Resource Files
The HUBwatch resource files Hubwatch_gray, Hubwatch_salmon, Hubwatch_tan
and Hubwatch_teal contain alternate color palettes for the HUBwatch windows.
When HUBwatch starts it locates the resource file by first looking for the
file "Hubwatch" in the user login directory. If HUBwatch does not find the
file, then, by default, it uses $MOTIFHOME/lib/X11/app-defaults/Hubwatch as
the resource file, where MOTIFHOME is the root directory of your Motif
installation.
To set up HUBloader resource files, replace Hubwatch with Hubloader in the
section above. Note that HUBWATCH_LIBRARY remains the same.
6 HUBwatch for HP-UX V4.0, Release Notes
To set up your HUBwatch resource file, do the following:
ln -s $HUBWATCH_LIBRARY/Hubwatch_teal ~/Hubwatch
OR
ln -s $HUBWATCH_LIBRARY/Hubwatch_teal
$MOTIFHOME/lib/X11/app-defaults/Hubwatch
To use a different resource file, replace Hubwatch_teal with Hubwatch_gray,
Hubwatch_salmon or Hubwatch_tan in the statements above.
5.3 Agent File
The environment variable HUBWATCH_LIBRARY must be defined in order for
HUBwatch to locate the agents file. If an agents file is to be shared among
HUBwatch users, then the HUBWATCH_LIBRARY directory should be accessible to
all sharing HUBwatch users. Users who will add agents will need write access
to that directory and to $HUBWATCH_LIBRARY/hubwatch_agents.
A template of the agents file is kept in $HUBWATCH_LIBRARY/hubwatch_agents.
You will need to change the protection on this file before adding the desired
list of agents to it.
6 Launching HUBwatch from HP OpenView
The HUBwatch installation procedure copies the following files into your
OpenView root directory (called OVHOME, typically /usr/OV):
OVHOME/registration/C/hubwatch_reg : registration file for HUBwatch
OVHOME/fields/C/hubwatch_fields : fields file for HUBwatch
OVHOME/symbols/C/hubwatch.sym : symbol file for HUBwatch
OVHOME/bitmaps/C/hubwatch.50.p : HUBwatch icon
OVHOME/bitmaps/C/hubwatch.50.m : HUBwatch icon mask
OVHOME/config/C/oid_to_sym.hw : HUBwatch-specific oid_to_sym entries
OVHOME/config/oid_to_type.hw : HUBwatch-specific oid_to_type entries
OVHOME/bitmaps/c/hubwatch.38.p :HUBwatch icon
1. Back up OVHOME/config/C/oid_to_sym and OVHOME/config/oid_to_type.
2. Append oid_to_sym.hw and oid_to_type.hw, respectively, to the above files.
If the previous steps did not succeed, they should be executed manually as
shown below. It is assumed that HUBwatch for HP-UX has been installed at
HUBWATCH_SYSTEM and that HUBWATCH_LIBRARY is also defined.
cd $OVHOME
cp $HUBWATCH_LIBRARY/OV/hubwatch_reg $OVHOME/registration/C/hubwatch
cp $HUBWATCH_LIBRARY/OV/hubwatch_fields $OVHOME/fields/C/hubwatch
cp $HUBWATCH_LIBRARY/OV/hubwatch.50.p $OVHOME/bitmaps/C/hubwatch.50.p
cp $HUBWATCH_LIBRARY/OV/hubwatch.50.m $OVHOME/bitmaps/C/hubwatch.50.m
cp $HUBWATCH_LIBRARY/OV/hubwatch.sym $OVHOME/symbols/C/hubwatch.sym
cp $HUBWATCH_LIBRARY/OV/oid_to_sym.hw $OVHOME/conf/C/oid_to_sym.hw
cp $HUBWATCH_LIBRARY/OV/oid_to_type.hw $OVHOME/conf/oid_to_type.hw
cp $HUBWATCH_LIBRARY/OV/hubwatch.38.p $OVHOME/bitmaps/c/hubwatch.38.p
HUBwatch for HP-UX V4.0, Release Notes 7
If you are installing HUBwatch for HP-UX for the FIRST TIME, you need to
execute steps 1 and 2 below. Skip to step 3 if this is NOT the first
time you are installing HUBwatch for HP-UX.
1. Type the following command and press <Return>:
cd $OVHOME/conf/C; cp oid_to_sym oid_to_sym.BAK;
cat oid_to_sym.hw >> oid_to_sym
2. Type the following command and press <Return>:
cd $OVHOME/conf; cp oid_to_type oid_to_type.BAK;
cat oid_to_type.hw >> oid_to_type
3. After copying the files, do the following:
Start OpenView with the -fields option:
ovw -fields
This option ensure that OpenView adds the HUBwatch field entry to the
OVW object database.
4. The SNMP devices that can be monitored by HUBwatch will appear with
HUBwatch icons. You can double-click on any of them to invoke HUBwatch.
Subsequent invocations of OpenView will automatically cause the
HUBwatch-related information to be read during startup and HUBwatch will
be launchable as indicated in step 4 above.
7 Warnings, Known Problems, and Restrictions
The following are warnings, known problems, or restrictions with HUBwatch
for HP-UX V4.0:
7.1 Agent Setup and Configuration Issues
o If a user changes the community name of any agent displayed in the
HUBwatch Front Panel window, the HUBwatch application must be restarted.
o If the user changes the community name of the DEChub 900 Hub Manager,
then the Hub Manager must be reset with current defaults.
o While upgrading the firmware in a DEChub module, do not use HUBwatch
(or any SNMP manager) to communicate with the module during the
firmware upgrade. Doing so could cause the firmware load to fail.
7.2 General HUBwatch Use Issues
o Use caution when connecting twisted pair wiring in your network.
o Connecting an Ethernet twisted pair cable to an FDDI twisted pair
network will disrupt Ethernet traffic.
8 HUBwatch for HP-UX V4.0, Release Notes
o Ethernet twisted pair ports on DECrepeater, PORTswitch, and PEswitch
modules should be wired to end stations using a straight through cable.
Ethernet twisted pair ports on DECswitch and DECbridge modules should
be wired to end stations using a cross-connect cable, or wired to
repeaters using a straight-through cable. Consult the installation and
use manuals supplied with the DECrepeater, PORTswitch, PEswitch,
DECbridge, and DECswitch devices for more information.
o By default the polling timer interval is set to 10 seconds. If you plan
to enable polling, Digital recommends not to take this default but to
use a polling time interval of one minute instead.
o If the value of either the timeout or retry field is zero, the HUBwatch
software uses the default value. For timeout, the default value is 5
seconds. For retry, the default value is 2 retries.
o If you use very large timeout or retry values, the HUBwatch application
may appear to hang for long periods of time.
o After pressing either the [Reset] or [Factory] button in many HUBwatch
windows, HUBwatch issues a reset or reset-to-factory request to the
device, then tries to update the information in the window. Because the
device may be still resetting, it is not uncommon for the update SNMP
requests to time-out. This is expected behavior. To verify the updated
contents of the screen you may need to wait up to a minute before
pressing the [Refresh] button on the window.
o You cannot use the HUBwatch software to change device passwords for the
DECbridge 90, DECbridge 90FL, DECserver 90L and DECserver 90L+ modules
after adding the modules. You must first change the password in the
module, then add the module. Enter the module password (if used) in the
"Current Password" field of the Add Module window. If you set a password
in the module and then you fail to enter the current password in the Add
Module window, you will not be able to do sets on the module. If this
happens, delete the module then add it again with Add Module window
being sure to enter the current password.
o Note that the HUBwatch agents file restricts the use of comment lines
to the beginning of the file. Any full line comment edited into the
file after the first agent entry will be removed whenever HUBwatch
updates the file due to agent modification, addition or deletion.
However, comments included on the same line with an agent entry will
be preserved.
o If HUBwatch polling is enabled for some time, performance degradation
in HUBwatch may result. If this problem is seen, exit, then re-enter
HUBwatch.
o For any HUBwatch window that uses a paned window (including the
DECbridge 90 filter window, the 900-series Bridge/Switch Module Summary
window, the Repeater Module Summary window, and the Repeater Port
Summary window), do not attempt to resize a pane while the watch cursor
is displayed. Doing so may result in a HUBwatch crash.
HUBwatch for HP-UX V4.0, Release Notes 9
o In the Logical Front Panel window, a module may show up initially with
no ports or with insufficient ports. The module may eventually be
re-painted in its entirety once the LED states are updated. Resizing
the window usually causes the missing ports to appear. (DECbridge 90,
DECbridge 90FL, DECbrouter 90T's, DECbridge 900MX, DECswitch 900's,
PEswitch 900TX)
o If you replace a module in a particular slot with an identical type of
module in that same slot, always exit and re-entered HUBwatch before
trying to manage that module.
o When using the Physical Front Panel window, select a module by clicking
on an area of the bezel without text. Clicking over text will not select
the module.
o For the Find Address function HUBwatch allocates a fixed size space to
store the local system's ARP cache. If the ARP cache size on the local
system exceeds this fixed size space, the Find Address function will
fail.
o In the window from where the HUBwatch command is run you may receive the
following warning from Motif. This is just a warning.
X Toolkit Warning: XtRemoveGrab asked to remove a widget not on the list
o When running a number of Motif based applications simultaneously you may
have insufficient resources available to run HUBwatch as well. If this is
the case, you should exit from one or more of these applications and then
restart HUBwatch. If you have insufficient resources, you may receive
the following types of warnings from Motif.
X Toolkit Warning: Cannot allocate colormap entry for '#-'
X Toolkit Warning: Urm__RealizeColorTable: Couldn't covert RGB color/pixel
X Toolkit Warning: Urm__CW_ConvertValue: Couldn't covert RGB color/pixel
7.3 LAN Interconnect and NMS Connectivity Issues
o Only one manager shall configure the DEChub 900 MultiSwitch backplane
LANs at a time.
o It is imperative that older versions of HUBwatch NOT be used with hubs
and modules that have been upgraded to the revisions listed above.
If older versions of HUBwatch are used with hubs and modules that have
been upgraded to the revisions listed, and if such a hub contains an
FDDI tree or 802.5 Token Ring, unpredictable results will be obtained.
o HUBwatch will not automatically disconnect/connect groups on the LAN
Interconnect and Expanded LAN Interconnect windows in response to changes
in the Group window. After modifications to the Group window the user
will need to disconnect/connect the corresponding groups from the
appropriate Interconnect windows as a second step.
10 HUBwatch for HP-UX V4.0, Release Notes
o In the LAN interconnect window, the first connection made to an FDDI
segment is called a "virtual connection". Since FDDI is by nature a
point-to-point topology, a single module connected to an FDDI segment
does not constitute an FDDI LAN.
Once you have made a virtual connection, you should without intervening
operations proceed to make a second connection to that same FDDI
segment, (or delete that virtual connection). Do not perform other
LAN interconnect, station configuration, or port switching operations
in the intervening time. Failure to heed this warning may result, in
some cases, in HUBwatch crashing.
If you cancel the LAN interconnect window with virtual connections,
those virtual connections will be lost.
o If virtual connections are present in the LAN interconnect window, a
refresh will cause the cursor to change to the "watch cursor" for about
1-2 seconds, and then prematurely change-back to the normal cursor; the
refresh does not actually complete for another 5-15 seconds. Please be
patient, and be careful what you click on during that time.
o This version of HUBwatch (and related DEChub 900 MultiSwitch firmware)
supports Auto Healing of FDDI trees and rings. For an explanation of
Auto Healing, refer to the HUBwatch Use manual. That manual contains a
reference which reads: "For Auto Healing's impact on Ethernet ports,
refer to the HUBwatch release notes." What follows is that additional
information:
When a patch-in operation occurs, any Ethernet port(s) on the slot being
patched-in will be restored to what those port(s) were just before the
preceding patch-out operation.
While such a device is patched-out, HUBwatch will only show the FDDI
connection as being patched-out. Even if that module had Ethernet
connections to the hub backplane, HUBwatch will not illustrate those
connections.
o This version of HUBwatch has improved Ethernet loop detection. While
enabling loop detection may increase the time it takes to perform port
grouping operations, Digital strongly recommends that you keep loop
detection enabled.
This version is accurate in foreseeing Ethernet repeater loops. If after
being warned that an operation will cause a loop you proceed with the
operation, a loop will certainly result. Digital recommends that you
never proceed with an operation after being warned of an impending loop,
unless you are managing the hub or module out of band.
o After inserting or removing modules in a hub for which the HUBwatch LAN
Interconnect window is still invoked or if the LAN Interconnect window
has been opened for an extended period of time, you should first refresh
the Front Panel window and then the LAN Interconnect window before
performing any LAN interconnect, station configuration, or port
switching operations.
HUBwatch for HP-UX V4.0, Release Notes 11
o Occasionally the LAN Interconnect window may not accurately reflect
the DEChub 900 MultiSwitch hub manager's database. If previously-made
connections do not appear in the window, or the window does not match
the actual network configuration then resynchronize the display by
pressing the [Refresh] button in the LAN Interconnect window.
o The DECrepeater 90FS and DECrepeater 90TS can only connect to one
flexible Ethernet channel and the backplane ThinWire. Multiple
DECrepeater 90FS's and 90TS's must be connected to the same flexible
Ethernet channel. In order to move a DECrepeater 90FS or DECrepeater 90TS
between flexible Ethernet channels it must be disconnected and
reconnected.
o In order to use HUBwatch software to manage any 90-series modules
(except DECrepeater 90 series modules) installed in the DEChub 900
MultiSwitch, the dedicated Ethernet ThinWire segment on the DEChub 900
MultiSwitch backplane must be reachable over the network from the NMS.
o Before changing a network building block for a port, disconnect that
port from the backplane.
o In the LAN Interconnect window if there are enough LANs to warrant a
scroll bar, then pulling down a connector too quickly can cause the
screen to oscillate until the user releases the mouse button. To avoid
this problem either enlarge the window so that the scroll bar goes away,
or pull down connections slowly.
o In the LAN Interconnect window, moving an FDDI connection is disabled.
To move an FDDI connection, first delete the existing connection, then
reconnect it to the desired FDDI LAN.
o In the LAN Interconnect window, moving a connection between the ThinWire
segment and an Ethernet flexible channel is disabled. To move a
connection between the ThinWire and a flexible segment, first delete the
existing connection, then reconnect it to the desired Ethernet LAN.
o LAN Interconnect segment names in the LAN interconnect window can now
be up to 31 characters in length; (8 characters was the previous
maximum).
7.4 Module Specific Issues
7.4.1 DECagent Issues
o The [Apply] or [OK] buttons are not selected in the agent Summary window
of the DECagent 90 when the field sytem name, Location & Contact fields
are deleted by duble clicking the mouse. In order to delete long text
one has to always use delete key.
o Version 3.0 of the DECagent 90 will support a maximum of forty-eight
modules. Previous versions supported a maximum of sixty-four modules.
o In the Agent Summary selecting an unsupported Hub Type wll default the
Hub Type to a double DEChub 90.
12 HUBwatch for HP-UX V4.0, Release Notes
7.4.2 DECmau 900TH Issues
o The first entry of the Ring Information box within the Ring Error
Monitor window is labeled "Ring Poller Process" - it should be "Ring
Error Monitor". This is used to enable/disable the ring error monitor
process.
o In the Ring Map window the "AP Interval" value is labeled as "hours" -
it should be "seconds".
7.4.3 DECbridge/DECswitch/PEswitch Issues
o If the PEswitch 900TX, DECswitch 900EF, or DECbridge 900MX is managed
as a standalone device (either in a DEChub ONE or via its own IP
address and community string), on some monitors the FDDI button in the
"More Information" box in the Bridging Summary window may not appear.
If the FDDI More Information button does not appear, resize the Bridging
Summary window to make the window wider.
o The Station configuration display icon on the FDDI summary window is
not supported for DECbridge, DECswitch and PEswitch modules.
o Be cautious when using the DECbridge 900MX to provide IP services for
the hub. If the bridge is in learning mode when it receives SNMP
requests from HUBwatch, the requests may be lost and HUBwatch may
encounter SNMP timeouts without any real indication of the problem to
the user. Because of these timeouts the HUBwatch window that made the
requests may be corrupted. If you can determine that the window is
corrupted, a refresh will bring the window up to date.
7.4.4 DECrepeater/PORTswitch Issues
o For PORTswitches 900CP and 900TP only: Repeater ports that are
disconnected in the Port Switching window are automatically disabled
and cannot be enabled in the Repeater Port Summary window. Repeater
ports that are connected in the Port Switching window are enabled and
cannot be disabled in the Repeater Port Summary window. To enable a
port that was disconnected using the Port Switching window, you must
open the Port Switching window and connect the port.
o On the Repeater Port Summary window, the connected stations list will
be empty, when the window is invoked. To populate the table, press the
[Stations] button at the bottom of the window.
o The Internal LAN LEDs displayed on the HUBwatch Main Physical window
will only be displayed as blinking by HUBwatch if there is activity on
that Internal LAN which is sourced from the PORTswitch. If the only
activity on that Internal LAN is sourced entirely from the DEChub 900
Backplane, then the PORTswitch's Internal LAN LED for that Internal
LAN will show activity, but this state will not be shown by HUBwatch.
o With HUBwatch Polling enabled, the Repeater Summary window does not
update either Port Names or Connected Stations. Users should always
perform a [Refresh] of a HUBwatch window prior to making a critical
decision based on window data.
HUBwatch for HP-UX V4.0, Release Notes 13
o The DECrepeater 90FS Dual-Port Redundancy Enabled LED is not currently
supported by HUBwatch.
o The Module OK LED is not currently supported by HUBwatch for
DECrepeaters and PORTswitches other than the PORTswitch 900CP and
PORTswitch 900TP.
o On DECrepeaters and PORTswitches which support Security, there is a
limit of either 2 or 4 Authorized Station Addresses per port. If a
station is using DECnet, then the station's Ethernet Hardware Address
as well as the DECnet Physical Address must be authorized for the
station to operate properly.
o On the Repeater Summary window for DECrepeater 90s in a DEChub 900,
there are radio buttons for Auto-partition Algorithm, Auto-partition
Reconnect Algorithm, and Jam Bits. When these are set and [OK] or
[Apply] pressed a "BadValue SNMP response" error will result. This
error can be ignored. This error will not occur with the DECrepeater
90T-16.
o The Repeater Summary window will show the AUI port for a DECrepeater
90T-16 when it is present in a DEChub. The AUI port is not physically
accessible in this configuration, although the internal port can be
managed.
o On the Repeater Security Summary window, the [Enable], [Disable], and
[Clear] buttons are applied immediately when pressed. There is no need
to press [OK] or [Apply]. The Address Learning Status field on this
window is not currently updated after being Enabled, Disabled, or
Cleared until a [Refresh] of the window is performed by the user.
Please note that this [Refresh] will also cause changes to any
modifications which were made on the window and were not applied using
the [Apply] button, so you may want to perform any desired changes to
the Address Learning Status prior to other modifications.
o On the Repeater Port Details window the Link Test Admin. Status
Enable/Disable Buttons are not properly desensitized for the AUI and
BP (Backplane) ports of those DECrepeaters and PORTswitches which have
ports supporting the Link Test Admin. feature. Selecting Enable for
these ports will result in a BadValue SNMP response error message.
This error can be ignored.
o The LAN Segment Name Field on Repeater windows is not currently
supported.
o The Group Name Field on Repeater windows is not currently supported.
o In some situations involving DECrepeater 90T-16 modules in a DEChub 900,
the Administration Status for a port may not be reported as expected
immediately after an Enable, Disable, or Enet-Reset. In such cases
performing a [Refresh] of the Repeater window after a short while
should display the proper status.
14 HUBwatch for HP-UX V4.0, Release Notes
o On the Repeater Security Summary window, if the user selects the All
Front Panel Ports button and then enables and disables Prevent
Eavesdropping, pressing [Apply] or [OK] will result in the enabling of
Prevent Eavesdropping (ie the initial enable value sticks). If the user
wishes to disable Prevent Eavesdropping, do not set the Prevent
Eavesdropping to enable prior to setting it back to disable, leaving it
at its initial value of disable. If Prevent Eavesdropping is enabled and
a setting of disabled is desired, exit and re-enter the window.
o On the Repeater Summary window the Station Configuration button is
incorrectly sensitized for a DECrepeater 90TS in a DEChub. This feature
is only applicable when the DECrepeater 90TS is in a standalone
configuration.
o On the Repeater Summary window the MAU type icons for the BP (Backplane)
and AUI ports of a DECrepeater 90T-16 do not show up correctly. They
show up as 10BaseT type connectors rather than AUI or ThinWire type
connectors.
o On the Security Summary window if you select a single port or All Front
Panel Ports, make changes to the window data, and then select another
port or All Front Panel Ports, a pop-up message will be displayed warning
you about modifications that have not been applied. Currently this
warning pop-up message box does not allow you to cancel changing the
selected port(s).
o The Online Help for 900-Series Repeaters states that the Port Table
Administration Status "red dashed arrow" icon signifies that the port
is enabled but either in dual-port redundancy standby mode or
non-operational due to an error. This is correct. However, this icon
will also be displayed for a port which is enabled, if the entire
repeater has been disabled through management action (ie. [Disable]
button on Repeater Summary window). Those ports on the repeater whose
Administration Status is set to be disabled, will display the usual
disabled port icon ("red open arrow" icon).
The "red dashed arrow" icon is also displayed for an enabled backplane
Thinwire port (BP) of a repeater, which has been disconnected from the
Thinwire backplane segment of the DEChub 900MS via the LAN Interconnect
View.
7.4.5 DECserver Issues
o For the DECserver 90TL, 134 baud is displayed in the speed menus in both
the Terminal Server Summary window and the Port Summary window, but it
is not a legal speed for the module. Do not select it.
o For the DECserver 90TL, DECserver 90M, DECserver 900TM and
DECserver 900GM certain values (such as Port Speed, Parity and Character
Size) shown in the Terminal Server Port window are not necessarily the
same values displayed by the terminal server LIST PORT command if the
port speed is set to Autobaud.
HUBwatch for HP-UX V4.0, Release Notes 15
o The DECserver 900TM and 900GM are not manageable in the DEChub 900
MultiSwitch from the HUBwatch application unless the backplane port
connector number 1 is on the same LAN as the NMS station, or the server
is otherwise reachable over the network from the NMS station.
7.4.6 GIGAswitch/FDDI Issues
Note that this product only supports the GIGAswitch/FDDI. It does not
support the GIGAswitch/ATM product.
o New functionality incorporated into the V2.2 release of the
GIGAswitch/FDDI is not supported through HUBwatch for HP-UX V4.0.
o The Logical Front Panel is not supported for the GIGAswitch/FDDI. The
Physical Front Panel window is always displayed.
o In the GIGAswitch/FDDI FDDI MAC Summary window, GIGAswitch/FDDI
firmware reports the wrong value for the UN DA Flag. Also, the firmware
does not correctly support the Restricted Token Timeout function.
o In the GIGAswitch/FDDI Line Card Summary window, the GIGAswitch/FDDI
firmware does not currently allow either the Connection Policy or the
Timer Setup to be set.
o For the FGL-4 line card, all ports on the module are shown as the same
PMD type of the first port of the module.
7.4.7 RouteAbout Access Issues
o When a RouteAbout Access module is installed in a DEChub managed by
HUBwatch, double-clicking on the module's bezel in the HUBwatch front
panel will invoke a DECterm window with a TELNET connection to the
module. HUBwatch will attempt to use the highest numbered IP address
assigned to the RouteAbout module as the TELNET destination address.
If that address is not reachable from the workstation running HUBwatch,
then HUBwatch will default to the IP address assigned to the DEChub 900
management. This will invoke the DECterm, but will not produce a
successful TELNET connection. As a workaround, enter the "telnet"
command at another DECterm on the workstation, using one of the other
IP addresses assigned to the RouteAbout module.
7.4.8 DECpacketprobe/PROBEwatch Issues
o HUBwatch will attempt to load PROBEwatch when a user double clicks on
the DECpacketprobe 90 or 90RR. HUBwatch does not use the NSHOME
environment variable to locate the PROBEwatch application. Instead it
always tries to launch it from /use/kits/PROBEwatch/bin/nsman. If
PROBEwatch was installed on your system in a different directory than
/use/kits/PROBEwatch/bin/nsman, you may wish to set up a link between
/use/kits/PROBEwatch/bin /nsman and where nsman was installed.
16 HUBwatch for HP-UX V4.0, Release Notes
8 Known Errors in the Documentation
The documentation errors are grouped in the following categories:
o HUBwatch Installation and Configuration manual
o HUBwatch Use manual
8.1 Errors in the HUBwatch Installation and Configuration Manual
The following new modules are not documented in the manual.
- RoamAbout Access Point
- GIGAswitch/FDDI FGL-4
To configure the access point module, use the configuration instructions
for the DECbridge 900MX.
8.2 Errors in the HUBwatch Use Manual
The following new module is not documented in the manual.
- GIGAswitch/FDDI FGL-4
For descriptions and management information, refer to the online help.
HUBwatch for HP-UX V4.0, Release Notes 17
18 HUBwatch for HP/UX V4.0, Release Notes
|
|
HUBwatch for SunOS V4.0, Release Notes
This document contains information not included elsewhere in the HUBwatch
for SunOS V4.0 product documentation.
PLEASE READ THESE NOTES BEFORE INSTALLING OR USING THE SOFTWARE.
July 17, 1995
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is
subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights
in Technical Data and Computer Software clause at DFARS 252.227-7013.
Copyright 1995, Digital Equipment Corporation All rights reserved.
The following are trademarks of Digital Equipment Corporation: Alpha AXP,
AXP, Bookreader, DEC, DECagent, DECbridge, DECbrouter, DECconcentrator,
DEChub, DEChub ONE, DECmcc, DECnet, DEC SunOS, DECpacketprobe90, DECrepeater,
DECserver, DECswitch, DECwindows, GIGAswitch, GIGAswitch/FDDI, HUBwatch,
LAT, OpenVMS, PEswitch, POLYCENTER, RoamAbout, ThinWire, VAX, VAX DOCUMENT,
VMS, and the Digital logo.
The following are third-party trademarks:
Motif, OSF, and OSF/1 are registered trademarks of the Open Software
Foundation, Inc.
SunOS and SunNet Manager are trademarks of Sun Microsystems, Inc.
OpenView is a registered trademark of Hewlett-Packard Company for
compute programs with network systems and user manuals supplied therein.
HyperHelp and Xprinter are trademarks of Bristol Technology Inc.
Contents_______________________________________________
1 Introduction.............................................................1
2 User Information.........................................................1
3 Firmware Requirements....................................................2
4 Software Requirements....................................................3
5 HUBwatch Files...........................................................3
5.1 Setting Environment Variables..........................................6
5.2 Resource Files.........................................................7
5.3 Agent File.............................................................7
6 Launching HUBwatch from HP OpenView......................................8
7 Launching HUBwatch from SunNet Manager...................................9
8 Warnings, Known Problems, and Restrictions..............................11
8.1 Agent Setup and Configuration Issues..................................11
8.2 General HUBwatch Use Issues...........................................11
8.3 LAN Interconnect and NMS Connectivity Issues..........................13
8.4 Module Specific Issues................................................15
8.4.1 DECagent Issues.....................................................15
8.4.2 DECmau 900TH Issues.................................................15
8.4.3 DECbridge/DECswitch/PEswitch Issues.................................15
8.4.4 DECrepeater/PORTswitch Issues.......................................16
8.4.5 DECserver Issues....................................................18
8.4.6 GIGAswitch/FDDI Issues..............................................18
8.4.7 RouteAbout Access Issues............................................19
8.4.8 DECpacketprobe/PROBEwatch Issues....................................19
9 Known Errors in the Documentation.......................................19
9.1 Errors in the HUBwatch Installation and Configuration Manual..........19
9.2 Errors in the HUBwatch Use Manual.....................................20
HUBwatch for SunOS V4.0, Release Notes iii
iv HUBwatch for SunOS V4.0, Release Notes
1 Introduction
Version 4.0 of the HUBwatch for SunOS is the second release of the HUBwatch
application on SunOS. Version 4.0 of HUBwatch for SunOS provides all
the functions of the V3.1 release and adds support for the following
network modules:
DECconcentrator 900TH
DECmau 900TH and 900TL
DECrepeater 90T-16 (Ethernet repeater)
DECrepeater 900FL, 900SL and 900TL (Token ring repeaters)
DECserver 900GM
PORTswitch 900CP, 900TP and 900FP
The HUBwatch V4.0 software also recognizes the following modules when they
are installed in the DEChub 900MS:
DECpacketprobe 90 and 900RR RouteAbout Access
HUBwatch displays these modules in the Hub Front Panel window but does not
provide management facilities for these modules. However, in the case of the
DECpacketprobe 90 and 900RR, HUBwatch has the ability to launch the
PROBEwatch application, if available, to manage these modules.
In addition, HUBwatch contains a firmware upgrade application called
HUBloader to upgrade modules, hubs, and the GIGAswitch/FDDI. Note that the
HUBloader application has it own release notes.
2 User Information
The HUBwatch for SunOS V4.0 user information set consists of both hardcopy
and online information.
o The HUBwatch Installation and Configuration manual describes how to
install and configure HUBwatch software and how to configure the
network modules in the DEChub 90 and DEChub 900 MultiSwitch hubs.
______________________________Important ____________________________
Important setup and configuration information about the DEChub 90,
the DEChub 900 MultiSwitch, and the DEChub modules is contained in
the HUBwatch Installation and Configuration manual.
____________________________________________________________________
o The HUBwatch Use manual describes how to use the HUBwatch graphical
user interface and the network module management windows and provides
some troubleshooting information.
o The HUBwatch online hyperhelp contains all the information provided
in the HUBwatch Use manual plus descriptions of the management windows,
step-by-step management procedures, context sensitive help for labels
and fields on the management windows, and a tutorial for getting
started.
HUBwatch for SunOS V4.0, Release Notes 1
______________________________Important ____________________________
HUBwatch for SunOS V4.0 uses hyperhelp files that are common with
HUBwatch for Windows V4.0. Therefore, there will be references to
Windows-specific information that does not apply to HUBwatch for
OSF/1, V4.0.
____________________________________________________________________
3 Firmware Requirements
The revision firmware supported by HUBwatch for SunOS V4.0 software is listed
below.
DECagent 90 ....................... V3.0.0
DECbridge 90/90FL ................. V4.0
DECbridge 900MX ................... V1.5.0
DECbrouter 90T1/90T2/90T2a ........ 9.14(1)
DECconcentrator 900MX ............. V3.0.0
DECconcentrator 900TH ............. V3.0.0
DEChub 900 MultiSwitch Hub Manager V4.0.0
DECmau 900TH ...................... V1.1.0
DECmau 900TL ...................... V1.1.0
DECrepeater 90FS .................. V1.1
DECrepeater 90TS .................. V1.1.0
DECrepeater 90T-16 ................ V1.0
DECrepeater 900FL ................. V1.1.0
DECrepeater 900SL ................. V1.1.0
DECrepeater 900TL ................. V1.1.0
DECrepeater 900FP ................. V1.1
DECrepeater 900GM ................. V1.1
DECrepeater 900TM ................. V1.1
DECserver 90M ..................... NAS V1.3.
DECserver 90TL .................... BL44, or NAS V1.3
DECserver 900TM ................... NAS V1.3, BL80-29
DECserver 900GM ................... NAS V1.3, BL80-29
DECswitch 900EE ................... V1.1.0
DECswitch 900EF ................... V1.5.0
GIGAswitch/FDDI SCP Card .......... V2.20 DL1.00 BB2.00
GIGAswitch/FDDI Clock Card ........ V2.10
GIGAswitch/FDDI FGL-2 Line Card ... V2.20
GIGAswitch/FDDI FGL-4 Line Card ... V2.00
PEswitch 900TX .................... V1.1.0
PORTswitch 900CP .................. V2.0
PORTswitch 900TP .................. V2.0
PORTswitch 900FP .................. V1.2.0
RoamAbout Access Point ............ V1.0.0
It is recommended that the DEChub 900 MultiSwitch Hub Manager firmware be
upgraded before the DEChub 900 modules are upgraded.
2 HUBwatch for SunOS V4.0, Release Notes
4 Software Requirements
HUBwatch for SunOS V4.0 requires the following software installed and
operating:
o SunOS V4.1.3 (or higher) operating system including the following
subsets:
o xnews
o Motif 1.2
5 HUBwatch Files
The following files are provided with HUBwatch for SunOS V4.0.
In directory <hubwatch_root_path>:
install_hubwatch
release_notes
question.txt
The file release_notes is the Release Notes file for HUBwatch for
SunOS V4.0 in ASCII text format (this document).
In directory <hubwatch_root_path>/lib:
Hubwatch_gray Hubloader_gray
Hubwatch_salmon Hubloader_salmon
Hubwatch_tan Hubloader_tan
Hubwatch_teal Hubloader_teal
hubwatch_agents
In directory <hubwatch_root_path>/mib:
hubwatch_mib_master
lib/OV:
hubwatch.50.m
hubwatch.50.p
hubwatch.38.p
hubwatch.sym
hubwatch_fields
hubwatch_reg
oid_to_sym.hw
oid_to_type.hw
readme.hw
lib/snm:
hub.schema
hubwatch.icon
hubwatch.iconmask
hubwatch.oid
hubwatch.schema
hw.oid
hw.schema
readme.hw
HUBwatch for SunOS V4.0, Release Notes 3
The HUBwatch resource files are Hubwatch_gray, Hubwatch_salmon,
Hubwatch_tan and Hubwatch_teal. The file hubwatch_agents is the
HUBwatch agents file template. The file hubwatch_mib_master is the
HUBwatch MIB variable translation database. The files in OV directory are
the files needed to support HP OpenView. The files in the snm directory are
the files needed to support SunNet Manager.
The HUBloader resource files are Hubloader_gray, Hubloader_salmon,
Hubloader_tan and Hubloader_teal.
In directory <hubwatch_root_path>/bin:
hubwatch - The primary HUBwatch image.
hubloader - The HUBloader application.
In directory <hubwatch_root_path>/uid:
hub_gsw_gui_filter_sum.uid hub_gui_fp_phys_90bezels.uid
hub_gsw_gui_front_panel.uid hub_gui_fp_phys_900bezels.uid
hub_gsw_gui_lc_sum.uid hub_gui_loader.uid
hub_gsw_gui_sys_sum.uid
hub_gui_agent_sum.uid
hub_gui_alarms.uid
hub_gui_brut_counters.uid
hub_gui_brut_port.uid
hub_gui_brut_sum.uid
hub_gui_comm_table.uid
hub_gui_db900.uid
hub_gui_db90_detail.uid
hub_gui_db90_fdb.uid
hub_gui_db90_filter.uid
hub_gui_db90_port_sum.uid
hub_gui_db90_spanning_tree.uid
hub_gui_db90_sum.uid
hub_gui_db90_trfc.uid
hub_gui_dsvr90_sum.uid
hub_gui_dsvr_counters.uid
hub_gui_dsvr_port.uid
hub_gui_dsvr_sum.uid
hub_gui_dsvr_tl_counters.uid
hub_gui_dsvr_tl_port.uid
hub_gui_dsvr_tl_sessions.uid
hub_gui_find.uid
hub_gui_front_panel.uid
hub_gui_interconn.uid
hub_gui_mod_add_del.uid
hub_gui_poll_int.uid
hub_gui_rpt900_counters.uid
hub_gui_rpt900_dpr.uid
hub_gui_rpt900_port.uid
hub_gui_rpt900_sec.uid
hub_gui_rpt900_sum.uid
hub_gui_rpt90_port.uid
hub_gui_rpt90_sum.uid
hub_gui_sum.uid
hub_gui_tr900th.uid
hub_gui_wc900.uid
hub_msg.cat
4 HUBwatch for SunOS V4.0, Release Notes
These are the HUBwatch Motif user interface (UID) files.
In directory <hubwatch_root_path>/hyperhelp:
app-defaults
bin
help
hoh.hlp
xprinter
hyperhelp/bin:
hyperhelp
hyperhelp/help:
about.hlp agentwin.hlp bridman.hlp
bridwin.hlp brutman.hlp brutwin.hlp
cfg_list.hlp conman.hlp conwin.hlp
frontwin.hlp gabout.hlp gigman.hlp
gigawin.hlp gigfiltr.hlp gtrouble.hlp
howto.hlp lanman.hlp menus.hlp
relinfo.hlp reptman.hlp reptwin.hlp
snmpman.hlp switch.hlp termman.hlp
termwin.hlp trouble.hlp hubload.hlp
hyperhelp/xprinter:
FontMetrics
PSstd.fonts
Xprinter.prolog
rgb.txt
hyperhelp/xprinter/FontMetrics:
AFM
hyperhelp/xprinter/FontMetrics/AFM:
ACaslon-AltSemibold.afm ACaslon-Italic.afm
ACaslon-Regular.afm ACaslon-Semibold.afm
ACaslon-SemiboldItalic.afm AGaramond-Bold.afm
AGaramond-BoldItalic.afm AGaramond-Italic.afm
AGaramond-Regular.afm AGaramond-Semibold.afm
AGaramond-SemiboldItalic.afm AGaramond-Titling.afm
Americana-ExtraBold.afm Americana.afm
AvantGarde-Book.afm AvantGarde-BookOblique.afm
AvantGarde-Demi.afm AvantGarde-DemiOblique.afm
Barmeno-ExtraBold.afm Bembo-Bold.afm
Bembo-BoldItalic.afm Bembo-Italic.afm
Bembo.afm Blackoak.afm
Bookman-Demi.afm Bookman-DemiItalic.afm
Bookman-Light.afm Bookman-LightItalic.afm
Carta.afm Courier-Bold.afm
Courier-BoldOblique.afm Courier-Oblique.afm
Courier.afm Formata-Italic.afm
Formata-Medium.afm Formata-MediumItalic.afm
Formata-Regular.afm Garamond-Bold.afm
HUBwatch for SunOS V4.0, Release Notes 5
Garamond-BoldItalic.afm Garamond-Light.afm
Garamond-LightItalic.afm GillSans-Bold.afm
GillSans-BoldItalic.afm GillSans-Italic.afm
GillSans.afm Helvetica-Black.afm
Helvetica-BlackOblique.afm Helvetica-Bold.afm
Helvetica-BoldOblique.afm Helvetica-Condensed-Bold.afm
Helvetica-Condensed-BoldObl.afm Helvetica-Condensed-Oblique.afm
Helvetica-Condensed.afm Helvetica-Light.afm
Helvetica-LightOblique.afm Helvetica-Narrow-Bold.afm
Helvetica-Narrow-BoldOblique.afm Helvetica-Narrow-Oblique.afm
Helvetica-Narrow.afm Helvetica-Oblique.afm
Helvetica.afm Kaufmann.afm
Korinna-Bold.afm Korinna-KursivBold.afm
Korinna-KursivRegular.afm Korinna-Regular.afm
Lithos-Black.afm Lithos-Regular.afm
LubalinGraph-Book.afm LubalinGraph-BookOblique.afm
LubalinGraph-Demi.afm LubalinGraph-DemiOblique.afm
LucidaSans-Bold.afm LucidaSans-BoldItalic.afm
LucidaSans-Italic.afm LucidaSans.afm
NewCenturySchlbk-Bold.afm NewCenturySchlbk-BoldItalic.afm
NewCenturySchlbk-Italic.afm NewCenturySchlbk-Roman.afm
Palatino-Bold.afm Palatino-BoldItalic.afm
Palatino-Italic.afm Palatino-Roman.afm
Parisian.afm ParkAvenue.afm
Rockwell-Bold.afm Rockwell-BoldItalic.afm
Rockwell-Italic.afm Rockwell.afm
Souvenir-Demi.afm Souvenir-DemiItalic.afm
Souvenir-Light.afm Souvenir-LightItalic.afm
Symbol.afm Tekton-Bold.afm
Tekton.afm Times-Bold.afm
Times-BoldItalic.afm Times-Italic.afm
Times-Roman.afm Trajan-Bold.afm
WoodtypeOrnaments-Two.afm ZapfChancery-MediumItalic.afm
ZapfDingbats.afm
These are the HUBwatch Hyperhelp-based on-line help files. On-line help
is invoked through the HUBwatch "Help" pull-down or any of the "Help"
push buttons on the HUBwatch management windows.
In directory <hubwatch_root_path>/man/man1:
hubwatch.1 - This is the HUBwatch man page.
5.1 Setting Environment Variables
The environment variables HUBWATCH_SYSTEM, HUBWATCH_LIBRARY and HHHOME
must be defined before invoking HUBwatch. HUBWATCH_SYSTEM is the root
directory for the HUBwatch installation and HUBWATCH_LIBRARY and HHHOME
point to the 'lib' and 'hyperhelp' directories under HUBWATCH_SYSTEM.
HUBloader requires the following environment variables to be set:
HUBWATCH_LIBRARY, HUBWATCH_LOAD and HUBWATCH_HUBLOADER. The directory
HUBWATCH_LIBRARY should contain the 'hubwatch_agents' file, and the
directory HUBWATCH_LOAD should contain the 'dcffiles.dat' file. The
user must have permission to write to the directory HUBWATCH_HUBLOADER
since HUBloader creates the status file in that directory.
6 HUBwatch for SunOS V4.0, Release Notes
In the example below, the root directory is assumed to be the default
location, /usr/kits/hubwatch.
The syntax for csh users
% setenv HUBWATCH_SYSTEM /usr/kits/hubwatch
% setenv HUBWATCH_LIBRARY $HUBWATCH_SYSTEM/lib
% setenv HHHOME $HUBWATCH_SYSTEM/hyperhelp
The syntax for Bourne Shell users
$ HUBWATCH_SYSTEM=/usr/kits/hubwatch
$ export HUBWATCH_SYSTEM
$ HUBWATCH_LIBRARY=HUBWATCH_SYSTEM/lib
$ export HUBWATCH_LIBRARY
$ HHHOME=HUBWATCH_SYSTEM/hyperhelp
$ export HHHOME
5.2 Resource Files
The HUBwatch resource files Hubwatch_gray, Hubwatch_salmon, Hubwatch_tan
and Hubwatch_teal contain alternate color palettes for the HUBwatch windows.
When HUBwatch starts it locates the resource file by first looking for the
file "Hubwatch" in the user login directory. If HUBwatch does not find the
file, then, by default, it uses $MOTIFHOME/lib/X11/app-defaults/Hubwatch as
the resource file, where MOTIFHOME is the root directory of your Motif
installation.
To set up your HUBwatch resource file, do the following:
ln -s $HUBWATCH_LIBRARY/Hubwatch_teal ~/Hubwatch
OR
ln -s $HUBWATCH_LIBRARY/Hubwatch_teal
$MOTIFHOME/lib/X11/app-defaults/Hubwatch
To use a different resource file, replace Hubwatch_teal with Hubwatch_gray,
Hubwatch_salmon or Hubwatch_tan in the statements above.
To set up HUBloader resource files, replace Hubwatch with Hubloader in the
statements above. Note that HUBWATCH_LIBRARY remains the same.
5.3 Agent File
The environment variable HUBWATCH_LIBRARY must be defined in order for
HUBwatch to locate the agents file. If an agents file is to be shared among
HUBwatch users, then the HUBWATCH_LIBRARY directory should be accessible to
all sharing HUBwatch users. Users who will add agents will need write access
to that directory and to $HUBWATCH_LIBRARY/hubwatch_agents.
A template of the agents file is kept in $HUBWATCH_LIBRARY/hubwatch_agents.
You will need to change the protection on this file before adding the
desired list of agents to it.
HUBwatch for SunOS V4.0, Release Notes 7
6 Launching HUBwatch from HP OpenView
The HUBwatch installation procedure copies the following files into your
OpenView root directory (called OVHOME, typically /usr/OV):
OVHOME/registration/C/hubwatch_reg : registration file for HUBwatch
OVHOME/fields/C/hubwatch_fields : fields file for HUBwatch
OVHOME/symbols/C/hubwatch.sym : symbol file for HUBwatch
OVHOME/bitmaps/C/hubwatch.50.p : HUBwatch icon
OVHOME/bitmaps/C/hubwatch.50.m : HUBwatch icon mask
OVHOME/config/C/oid_to_sym.hw : HUBwatch-specific oid_to_sym entries
OVHOME/config/oid_to_type.hw : HUBwatch-specific oid_to_type entries
OVHOME/bitmaps/c/hubwatch.38.p : HUBWATCH icon
1. Back up OVHOME/config/C/oid_to_sym and OVHOME/config/oid_to_type.
2. Append oid_to_sym.hw and oid_to_type.hw, respectively, to the above files.
If the previous steps did not succeed, they should be executed manually as
shown below. It is assumed that HUBwatch for SunOS has been installed at
HUBWATCH_SYSTEM and that HUBWATCH_LIBRARY is also defined.
cd $OVHOME
cp $HUBWATCH_LIBRARY/OV/hubwatch_reg $OVHOME/registration/C/hubwatch
cp $HUBWATCH_LIBRARY/OV/hubwatch_fields $OVHOME/fields/C/hubwatch
cp $HUBWATCH_LIBRARY/OV/hubwatch.50.p $OVHOME/bitmaps/C/hubwatch.50.p
cp $HUBWATCH_LIBRARY/OV/hubwatch.50.m $OVHOME/bitmaps/C/hubwatch.50.m
cp $HUBWATCH_LIBRARY/OV/hubwatch.sym $OVHOME/symbols/C/hubwatch.sym
cp $HUBWATCH_LIBRARY/OV/oid_to_sym.hw $OVHOME/conf/C/oid_to_sym.hw
cp $HUBWATCH_LIBRARY/OV/oid_to_type.hw $OVHOME/conf/oid_to_type.hw
cp $HUBWATCH_LIBRARY/OV/hubwatch.38.p $OVHOME/bitmaps/c/hubwatch.38.p
If you are installing HUBwatch for SunOS for the FIRST TIME, you need to
execute steps 1 and 2 below. Skip to step 3 if this is NOT the first
time you are installing HUBwatch for SunOS.
1. Type the following command and press <Return>:
cd $OVHOME/conf/C; cp oid_to_sym oid_to_sym.BAK;
cat oid_to_sym.hw >> oid_to_sym
2. Type the following command and press <Return>:
cd $OVHOME/conf; cp oid_to_type oid_to_type.BAK;
cat oid_to_type.hw >> oid_to_type
3. After copying the files, do the following:
Start OpenView with the -fields option:
ovw -fields
This option ensure that OpenView adds the HUBwatch field entry to the
OVW object database.
8 HUBwatch for SunOS V4.0, Release Notes
4. The SNMP devices that can be monitored by HUBwatch will appear with
HUBwatch icons. You can double-click on any of them to invoke HUBwatch.
Subsequent invocations of OpenView will automatically cause the
HUBwatch-related information to be read during startup and HUBwatch will
be launchable as indicated in step 4 above.
7 Launching HUBwatch from SunNet Manager
The HUBwatch installation procedure copies the following files into your
SunNet Manager root directory (called SNMHOME, typically /usr/snm):
SNMHOME/struct/hw.schema : schema file to detect HUBwatch agents
SNMHOME/agents/hw.oid : oid file corresp. to hw.schema
SNMHOME/agents/hubwatch.schema : description for component HUBwatch
SNMHOME/icons/hubwatch.icon : HUBwatch icon
SNMHOME/icons/hubwatch.iconmask: HUBwatch icon mask
If the previous step did not succeed, it should be executed manually using
the commands shown below. It is assumed that HUBwatch for SunOS has been
installed at HUBWATCH_SYSTEM and that HUBWATCH_LIBRARY is also defined.
Type the following commands and press <Return>:
cd $SNMHOME
cp $HUBWATCH_LIBRARY/snm/hw.schema $SNMHOME/struct
cp $HUBWATCH_LIBRARY/snm/hw.oid $SNMHOME/agents
cp $HUBWATCH_LIBRARY/snm/hubwatch.schema $SNMHOME/agents
cp $HUBWATCH_LIBRARY/snm/hubwatch.icon $SNMHOME/icons
cp $HUBWATCH_LIBRARY/snm/hubwatch.iconmask $SNMHOME/icons
Some additional steps are required to make HUBwatch launchable from the
SunNet Manager. They have been tested on V2.0 and V2.2.1 of SunNet Manager.
Because there are numerous differences between those versions of SunNet
Manager, the steps below are designed to work with either version.
1. Start SunNet Manager with the -i option:
snm -i
Ensure that both the hw.schema and hubwatch.schema files get loaded.
There are two options (2a or 2b) to proceed. The later steps (3 onwards)
are common to both options. Select an option (2a or 2b) and then
continue on with step3.
2a Start the 'Discover' tool from the 'Tools' menu. This opens a window
listing all the entities discovered by the tool.
1. Open the 'SNMP Devices' window.
2. Click the right button after pointing to any device in that window.
A menu will be displayed.
HUBwatch for SunOS V4.0, Release Notes 9
3. Go to the item 'Change Type' and click the right button. Another menu
will be displayed.
4. Go to the item 'Hubwatch' and click the right button. The menus will
disappear and the icon for the device will be changed to the HUBwatch
icon.
2b From the 'Edit' menu, go to the item 'Create' and click the right
button. A menu will be displayed.
1. Go to the item 'Component' and click the right button. Another menu
will be displayed.
2. Go to the item 'Hubwatch' and click the right button. A form will be
opened.
3. Fill in the following fields corresponding to the network device you
want to manage with HUBwatch:
IP Address (mandatory if entry does not exist in hubwatch_agents)
Name (mandatory, associated with the icon)
Community (optional, 'public' is usual))
Timeout (optional, 5 is usual)
Retry (optional, 1 is usual)
Select 'Apply'. The form will disappear and a HUBwatch icon with
the given name will appear.
3. Click the right button on the HUBwatch icon. A menu is displayed.
4. Go to the item 'Tools' and click the right button. Another menu is
displayed.
5. Click the 'HUBwatch for SunOS' icon. HUBwatch for SunOS will now be
launched to manage the specified SNMP device.
To save the setup for later use:
--------------------------------
1. From the 'File' menu, go to the item 'Save...' and click the right
button. A window will be opened.
2. Type the name of a file to save the changes you have made. Exit the
SunNet Manager after the changes have been saved.
3. Restart SunNet Manager with the 'snm' command. The HUBwatch icons that
you saved will be displayed in the appropriate view (HOME or 'SNMP
Devices'). Launch HUBwatch following steps 3-5 above.
---------------------------------
10 HUBwatch for SunOS V4.0, Release Notes
8 Warnings, Known Problems, and Restrictions
The following are warnings, known problems, or restrictions with HUBwatch
for SunOS V4.0:
8.1 Agent Setup and Configuration Issues
o If a user changes the community name of any agent displayed in the
HUBwatch Front Panel window, the HUBwatch application must be restarted.
o If the user changes the community name of the DEChub 900 Hub Manager,
then the Hub Manager must be reset with current defaults.
o While upgrading the firmware in a DEChub module, do not use HUBwatch
(or any SNMP manager) to communicate with the module during the
firmware upgrade. Doing so could cause the firmware load to fail.
8.2 General HUBwatch Use Issues
o Use caution when connecting twisted pair wiring in your network.
o Connecting an Ethernet twisted pair cable to an FDDI twisted pair
network will disrupt Ethernet traffic.
o Ethernet twisted pair ports on DECrepeater, PORTswitch, and PEswitch
modules should be wired to end stations using a straight through cable.
Ethernet twisted pair ports on DECswitch and DECbridge modules should
be wired to end stations using a cross-connect cable, or wired to
repeaters using a straight-through cable. Consult the installation and
use manuals supplied with the DECrepeater, PORTswitch, PEswitch,
DECbridge, and DECswitch devices for more information.
o By default the polling timer interval is set to 10 seconds. If you plan
to enable polling, Digital recommends not to take this default but to
use a polling time interval of one minute instead.
o If the value of either the timeout or retry field is zero, the HUBwatch
software uses the default value. For timeout, the default value is 5
seconds. For retry, the default value is 2 retries.
o If you use very large timeout or retry values, the HUBwatch application
may appear to hang for long periods of time.
o After pressing either the [Reset] or [Factory] button in many HUBwatch
windows, HUBwatch issues a reset or reset-to-factory request to the
device, then tries to update the information in the window. Because the
device may be still resetting, it is not uncommon for the update SNMP
requests to time-out. This is expected behavior. To verify the updated
contents of the screen you may need to wait up to a minute before
pressing the [Refresh] button on the window.
HUBwatch for SunOS V4.0, Release Notes 11
o You cannot use the HUBwatch software to change device passwords for the
DECbridge 90, DECbridge 90FL, DECserver 90L and DECserver 90L+ modules
after adding the modules. You must first change the password in the
module, then add the module. Enter the module password (if used) in the
"Current Password" field of the Add Module window. If you set a password
in the module and then you fail to enter the current password in the Add
Module window, you will not be able to do sets on the module. If this
happens, delete the module then add it again with Add Module window
being sure to enter the current password.
o Note that the HUBwatch agents file restricts the use of comment lines
to the beginning of the file. Any full line comment edited into the
file after the first agent entry will be removed whenever HUBwatch
updates the file due to agent modification, addition or deletion.
However, comments included on the same line with an agent entry will
be preserved.
o If HUBwatch polling is enabled for some time, performance degradation
in HUBwatch may result. If this problem is seen, exit, then re-enter
HUBwatch.
o For any HUBwatch window that uses a paned window (including the
DECbridge 90 filter window, the 900-series Bridge/Switch Module Summary
window, the Repeater Module Summary window, and the Repeater Port
Summary window), do not attempt to resize a pane while the watch cursor
is displayed. Doing so may result in a HUBwatch crash.
o In the Logical Front Panel window, a module may show up initially with
no ports or with insufficient ports. The module may eventually be
re-painted in its entirety once the LED states are updated. Resizing
the window usually causes the missing ports to appear. (DECbridge 90,
DECbridge 90FL, DECbrouter 90T's, DECbridge 900MX, DECswitch 900's,
and PEswitch 900TX)
o If you replace a module in a particular slot with an identical type of
module in that same slot, always exit and re-enter HUBwatch before
trying to manage that module.
o When using the Physical Front Panel window, select a module by clicking
on an area of the bezel without text. Clicking over text will not select
the module.
o For the Find Address function HUBwatch allocates a fixed size space to
store the local system's ARP cache. If the ARP cache size on the local
system exceeds this fixed size space, the Find Address function will
fail.
o In the window from where the hubwatch command is run you may receive the
following warning from Motif. This is just a warning.
X Toolkit Warning: XtRemoveGrab asked to remove a widget not on the list
12 HUBwatch for SunOS V4.0, Release Notes
o When running a number of Motif based applications simultaneously you
may have insufficient resources available to run HUBwatch as well. If
so, you should exit from one or more of these applications and then
restart HUBwatch. If you have insufficient resources, you may receive
the following types of warnings from Motif.
X Toolkit Warning: Cannot allocate colormap entry for '#-'
X Toolkit Warning: Urm__RealizeColorTable: Couldn't covert RGB color/pixel
X Toolkit Warning: Urm__CW_ConvertValue: Couldn't covert RGB color/pixel
8.3 LAN Interconnect and NMS Connectivity Issues
o Only one manager shall configure the DEChub 900 MultiSwitch backplane
LANs at a time.
o It is imperative that older versions of HUBwatch NOT be used with hubs
and modules that have been upgraded to the revisions listed above.
If older versions of HUBwatch are used with hubs and modules that have
been upgraded to the revisions listed, and if such a hub contains an
FDDI tree or 802.5 Token Ring, unpredictable results will be obtained.
o HUBwatch will not automatically disconnect/connect groups on the LAN
Interconnect and Expanded LANInterconnect windows in response to changes
in the Group window. After modifications to the Group window the user
will need to disconnect/connect the corresponding groups from the
appropriate Interconnect windows as a second step.
o In the LAN interconnect window, the first connection made to an FDDI
segment is called a "virtual connection". Since FDDI is by nature a
point-to-point topology, a single module connected to an FDDI segment
does not constitute an FDDI LAN.
Once you have made a virtual connection, you should without intervening
operations proceed to make a second connection to that same FDDI
segment, (or delete that virtual connection). Do not perform other
LAN interconnect, station configuration, or port switching operations
in the intervening time. Failure to heed this warning may result, in
some cases, in HUBwatch crashing.
If you cancel the LAN interconnect window with virtual connections,
those virtual connections will be lost.
o If virtual connections are present in the LAN interconnect window, a
refresh will cause the cursor to change to the "watch cursor" for about
1-2 seconds, and then prematurely change-back to the normal cursor; the
refresh does not actually complete for another 5-15 seconds. Please be
patient, and be careful what you click on during that time.
HUBwatch for SunOS V4.0, Release Notes 13
o This version of HUBwatch (and related DEChub 900 MultiSwitch firmware)
supports Auto Healing of FDDI trees and rings. For an explanation of
Auto Healing (refer to the HUBwatch Use manual). The manual contains a
reference which reads: "For Auto Healing's impact on Ethernet ports,
refer to the HUBwatch release notes." What follows is that additional
information:
When a patch-in operation occurs, any Ethernet port(s) on the slot
being patched-in will be restored to what those port(s) were just before
the preceding patch-out operation.
While such a device is patched-out, HUBwatch will only show the FDDI
connection as being patched-out. Even if that module had Ethernet
connections to the hub backplane, HUBwatch will not illustrate those
connections.
o This version of HUBwatch has improved Ethernet loop detection. While
enabling loop detection may increase the time it takes to perform port
grouping operations, Digital strongly recommends that you keep loop
detection enabled.
This version is accurate in foreseeing Ethernet repeater loops. If
after being warned that an operation will cause a loop you proceed with
the operation, a loop will certainly result. Digital recommends that
you never proceed with an operation after being warned of an impending
loop, unless you are managing the hub or module out of band.
o After inserting or removing modules in a hub for which the HUBwatch
LAN Interconnect window is still invoked or if the LAN Interconnect
window has been opened for an extended period of time, you should first
refresh the Front Panel window and then the LAN Interconnect window
before performing any LAN interconnect, station configuration, or port
switching operations.
o Occasionally the LAN Interconnect window may not accurately reflect
the DEChub 900 MultiSwitch hub manager's database. If previously-made
connections do not appear in the window, or the window does not match
the actual network configuration then resynchronize the display by
pressing the [Refresh] button in the LAN Interconnect window.
o The DECrepeater 90FS and DECrepeater 90TS can only connect to one
flexible Ethernet channel and the backplane ThinWire. Multiple
DECrepeater 90FS's and 90TS's must be connected to the same flexible
Ethernet channel. In order to move a DECrepeater 90FS or DECrepeater
90TS between flexible Ethernet channels it must be disconnected and
reconnected.
o In order to use HUBwatch software to manage any 90-series modules
(except DECrepeater 90 series modules) installed in the DEChub 900
MultiSwitch, the dedicated Ethernet ThinWire segment on the DEChub 900
MultiSwitch backplane must be reachable over the network from the NMS.
o Before changing a network building block for a port, disconnect that
port from the backplane.
14 HUBwatch for SunOS V4.0, Release Notes
o In the LAN Interconnect window if there are enough LANs to warrant a
scroll bar, then pulling down a connector too quickly can cause the
screen to oscillate until the user releases the mouse button. To avoid
this problem either enlarge the window so that the scroll bar goes away,
or pull down connections slowly.
o In the LAN Interconnect window, moving an FDDI connection is disabled.
To move an FDDI connection, first delete the existing connection, then
reconnect it to the desired FDDI LAN.
o In the LAN Interconnect window, moving a connection between the
ThinWire segment and an Ethernet flexible channel is disabled. To move
a connection between the ThinWire and a flexible segment, first delete
the existing connection, then reconnect it to the desired Ethernet LAN.
o LAN Interconnect segment names in the LAN interconnect window can now
be up to 31 characters in length; (8 characters was the previous
maximum).
8.4 Module Specific Issues
8.4.1 DECagent Issues
o The [Apply] or [OK] buttons are not selected in the agent Summary
window of the DECagent 90 when the field sytem name, Location & Contact
fields are deleted by duble clicking the mouse. In order to delete long
text one has to always use delete key.
o Version 3.0 of the DECagent 90 will support a maximum of forty-eight
modules. Previous versions supported a maximum of sixty-four modules.
o In the Agent Summary selecting an unsupported Hub Type wll default the
Hub Type to a double DEChub 90.
8.4.2 DECmau 900TH Issues
o The first entry of the Ring Information box within the Ring Error
Monitor window is labeled "Ring Poller Process" - it should be "Ring
Error Monitor". This is used to enable/disable the ring error monitor
process.
o In the Ring Map window the "AP Interval" value is labeled as "hours" -
it should be labeled "seconds".
8.4.3 DECbridge/DECswitch/PEswitch Issues
o If the PEswitch 900TX, DECswitch 900EF, or DECbridge 900MX is managed
as a standalone device (either in a DEChub ONE or via its own IP
address and community string), on some monitors the FDDI button in the
"More Information" box in the Bridging Summary window may not appear.
If the FDDI More Information button does not appear, resize the
Bridging Summary window to make the window wider.
o The Station configuration display icon on the FDDI summary window is
not supported for DECbridge, DECswitch and PEswitch modules.
HUBwatch for SunOS V4.0, Release Notes 15
o Be cautious when using the DECbridge 900MX to provide IP services for
the hub. If the bridge is in learning mode when it receives SNMP
requests from HUBwatch, the requests may be lost and HUBwatch may
encounter SNMP timeouts without any real indication of the problem to
the user. Because of these timeouts the HUBwatch window that made the
requests may be corrupted. If you can determine that the window is
corrupted, a refresh will bring the window up to date.
8.4.4 DECrepeater/PORTswitch Issues
o For PORTswitches 900CP and 900TP only: Repeater ports that are
disconnected in the Port Switching window are automatically disabled
and cannot be enabled in the Repeater Port Summary window. Repeater
ports that are connected in the Port Switching window are enabled and
cannot be disabled in the Repeater Port Summary window. To enable a
port that was disconnected using the Port Switching window, you must
open the Port Switching window and connect the port.
o On the Repeater Port Summary window, the connected stations list will
be empty, when the window is invoked. To populate the table, press the
[Stations] button at the bottom of the window.
o The Internal LAN LEDs displayed on the HUBwatch Main Physical window
will only be displayed as blinking by HUBwatch if there is activity on
that Internal LAN which is sourced from the PORTswitch. If the only
activity on that Internal LAN is sourced entirely from the DEChub 900
Backplane, then the PORTswitch's Internal LAN LED for that Internal
LAN will show activity, but this state will not be shown by HUBwatch.
o With HUBwatch Polling enabled, the Repeater Summary window does not
update either Port Names or Connected Stations. Users should always
perform a [Refresh] of a HUBwatch window prior to making a critical
decision based on window data.
o The DECrepeater 90FS Dual-Port Redundancy Enabled LED is not currently
supported by HUBwatch.
o The Module OK LED is not currently supported by HUBwatch for
DECrepeaters and PORTswitches other than the PORTswitch 900CP and
PORTswitch 900TP.
o On DECrepeaters and PORTswitches which support Security, there is a
limit of either 2 or 4 Authorized Station Addresses per port. If a
station is using DECnet, then the station's Ethernet Hardware Address
as well as the DECnet Physical Address must be authorized for the
station to operate properly.
o On the Repeater Summary window for DECrepeater 90s in a DEChub 900,
there are radio buttons for Auto-partition Algorithm, Auto-partition
Reconnect Algorithm, and Jam Bits. When these are set and [OK] or
[Apply] pressed a "BadValue SNMP response" error will result. This
error can be ignored. This error will not occur with the DECrepeater
90T-16.
16 HUBwatch for SunOS V4.0, Release Notes
o The Repeater Summary window will show the AUI port for a DECrepeater
90T-16 when it is present in a DEChub. The AUI port is not physically
accessible in this configuration, although the internal port can be
managed.
o On the Repeater Security Summary window, the [Enable], [Disable], and
[Clear] buttons are applied immediately when pressed. There is no need
to press [OK] or [Apply]. The Address Learning Status field on this
window is not currently updated after being Enabled, Disabled, or
Cleared until a [Refresh] of the window is performed by the user.
Please note that this [Refresh] will also cause changes to any
modifications which were made on the window and were not applied using
the [Apply] button, so you may want to perform any desired changes to
the Address Learning Status prior to other modifications.
o On the Repeater Port Details window the Link Test Admin. Status
Enable/Disable Buttons are not properly desensitized for the AUI and
BP (Backplane) ports of those DECrepeaters and PORTswitches which have
ports supporting the Link Test Admin. feature. Selecting Enable for
these ports will result in a BadValue SNMP response error message.
This error can be ignored.
o The LAN Segment Name Field on Repeater windows is not currently
supported.
o The Group Name Field on Repeater windows is not currently supported.
o In some situations involving DECrepeater 90T-16 modules in a DEChub
900, the Administration Status for a port may not be reported as
expected immediately after an Enable, Disable, or Enet-Reset. In such
cases performing a [Refresh] of the Repeater window after a short
while should display the proper status.
o On the Repeater Security Summary window, if the user selects the All
Front Panel Ports button and then enables and disables Prevent
Eavesdropping, pressing [Apply] or [OK] will result in the enabling of
Prevent Eavesdropping (ie the initial enable value sticks). If the user
wishes to disable Prevent Eavesdropping, do not set the Prevent
Eavesdropping to enable prior to setting it back to disable, leaving it
at its initial value of disable. If Prevent Eavesdropping is enabled
and a setting of disabled is desired, exit and re-enter the window.
o On the Repeater Summary window the Station Configuration button is
incorrectly sensitized for a DECrepeater 90TS in a DEChub. This feature
is only applicable when the DECrepeater 90TS is in a standalone
configuration.
o On the Repeater Summary window the MAU type icons for the BP
(Backplane) and AUI ports of a DECrepeater 90T-16 do not show up
correctly. They show up as 10BaseT type connectors rather than AUI or
ThinWire type connectors.
HUBwatch for SunOS V4.0, Release Notes 17
o On the Security Summary window if you select a single port or All
Front Panel Ports, make changes to the window data, and then select
another port or All Front Panel Ports, a pop-up message will be
displayed warning you about modifications that have not been applied.
Currently this warning pop-up message box does not allow you to cancel
changing the selected port(s).
o The Online Help for 900-Series Repeaters states that the Port Table
Administration Status "red dashed arrow" icon signifies that the port
is enabled but either in dual-port redundancy standby mode or
non-operational due to an error. This is correct. However, this icon
will also be displayed for a port which is enabled, if the entire
repeater has been disabled through management action (ie. [Disable]
button on Repeater Summary window). Those ports on the repeater whose
Administration Status is set to be disabled, will display the usual
disabled port icon ("red open arrow" icon).
The "red dashed arrow" icon is also displayed for an enabled backplane
Thinwire port (BP) of a repeater, which has been disconnected from the
Thinwire backplane segment of the DEChub 900MS via the LAN Interconnect
View.
8.4.5 DECserver Issues
o For the DECserver 90TL, 134 baud is displayed in the speed menus in
both the Terminal Server Summary window and the Port Summary window,
but it is not a legal speed for the module. Do not select it.
o For the DECserver 90TL, DECserver 90M, DECserver 900TM and
DECserver 900GM certain values (such as Port Speed, Parity and
Character Size) shown in the Terminal Server Port window are not
necessarily the same values displayed by the terminal server LIST
PORT command if the port speed is set to Autobaud.
o The DECserver 900TM and 900GM are not manageable in the DEChub 900
MultiSwitch from the HUBwatch application unless the backplane port
connector number 1 is on the same LAN as the NMS station, or the
server is otherwise reachable over the network from the NMS station.
8.4.6 GIGAswitch/FDDI Issues
Note that this product only supports the GIGAswitch/FDDI. It does not
support the GIGAswitch/ATM product.
o Functional support for the GIGAswitch/FDDI has not changed since
the HUBwatch for SunOS V3.1 release. New functionality incorporated
into the V2.2 release of the GIGAswitch/FDDI is not supported
through HUBwatch for SunOS V4.0.
o The Logical Front Panel is not supported for the GIGAswitch/FDDI. The
Physical Front Panel window is always displayed.
18 HUBwatch for SunOS V4.0, Release Notes
o In the GIGAswitch/FDDI FDDI MAC Summary window, GIGAswitch/FDDI
firmware reports the wrong value for the UN DA Flag. Also, the firmware
does not correctly support the Restricted Token Timeout function.
o In the GIGAswitch/FDDI Line Card Summary window, the GIGAswitch/FDDI
firmware does not currently allow either the Connection Policy or the
Timer Setup to be set.
o For the FGL-4 line card, all ports on the module are shown as the same
PMD type of the first port of the module.
8.4.7 RouteAbout Access Issues
o When a RouteAbout Access module is installed in a DEChub managed by
HUBwatch, double-clicking on the module's bezel in the HUBwatch front
panel will invoke a DECterm window with a TELNET connection to the
module. HUBwatch will attempt to use the highest numbered IP address
assigned to the RouteAbout module as the TELNET destination address.
If that address is not reachable from the workstation running HUBwatch,
then HUBwatch will default to the IP address assigned to the DEChub 900
management. This will invoke the DECterm, but will not produce a
successful TELNET connection. As a workaround, enter the "telnet"
command at another DECterm on the workstation, using one of the other
IP addresses assigned to the RouteAbout module.
8.4.8 DECpacketprobe/PROBEwatch Issues
o HUBwatch will attempt to load PROBEwatch when a user double clicks on
the DECpacketprobe 90 or 90RR. HUBwatch does not use the NSHOME
environment variable to locate the PROBEwatch application. Instead it
always tries to launch it from /use/kits/PROBEwatch/bin/nsman. If
PROBEwatch was installed on your system in a different directory than
/use/kits/PROBEwatch/bin/nsman, you may wish to set up a link between
/use/kits/PROBEwatch/bin /nsman and where nsman was installed.
9 Known Errors in the Documentation
The documentation errors are grouped in the following categories:
o HUBwatch Installation and Configuration manual
o HUBwatch Use manual
9.1 Errors in the HUBwatch Installation and Configuration Manual
The following new modules are not documented in the manual.
- RoamAbout Access Point
- GIGAswitch/FDDI FGL-4
To configure the access point module, use the configuration instructions
for the DECbridge 900MX.
HUBwatch for SunOS V4.0, Release Notes 19
9.2 Errors in the HUBwatch Use Manual
The following new module is not documented in the manual.
- GIGAswitch/FDDI FGL-4
For descriptions and management information, refer to the online help.
20 HUBwatch for SunOS V4.0, Release Notes
|