| From: TLSE01::SELLES "Pierre-Jean - EIS Toulouse - France" 4-OCT-1994 11:47:04.12
To: TLSE10::SELLES
CC:
Subj: HUBwatch for OSF/1 field test kit X3.1.54 available
From: NETCAD::FORINO "03-Oct-1994 1753" 3-OCT-1994 23:04:46.15
To: @PROJ$722:[ONEHUB.NETMGT]NETMGT-INTEREST,@[-.-]OSF_FT
CC:
Subj: HUBwatch for OSF/1 field test kit X3.1.54 available
+---------------------------+ TM
| | | | | | | |
| d | i | g | i | t | a | l | INTEROFFICE MEMORANDUM
| | | | | | | |
+---------------------------+
To: Distribution DATE: October 3, 1994
FROM: John Forino
DEPT: Networks Engineering/
HUB Product Engineering
DTN: 226-7585
LOC: LKG2-2/Y10
NETMAIL: QUIVER::FORINO
SUBJ: HUBwatch for OSF/1 available for system testing
The second field test version of HUBwatch for OSF/1 V3.1 is
now available for system testing. The kit can be obtained
by anonymous ftp on bhub (hubwatch_osf/HBWTCH310.tar). The
IP addresses of bhub is 16.21.16.156. This address has
recently changed so be aware of this in case you are having
trouble getting access. For those of you who need DECnet access
bhub has address 55.91 and the above tar file can be found at
/usr/users/ftp/hubwatch_osf/HBWTCH310.tar.
Be aware that this message is going out to two different audiences.
Primarily, it is meant for the HUBwatch System Test group so
they can formally begin testing and registering problems as they
are found. On the other hand there are a few internal DEC folks
who would like to use whatever is available on OSF because they
have no other options for running HUBwatch. Therefore, depending
on which group you are in there may be some sections of this
message that do not pertain to you.
This version of HUBwatch will be identified as X3.1.54 in the
running application. The "54" represents the software development
baselevel that is common with the HUBwatch for VMS V3.1 product.
Therefore, this product has all the same functionality as the
corresponding VMS V3.1 product with the following exceptions:
1. There will be no support for alarms/traps in the
OSF version. This functionality will not be available
in the OSF V3.1 product.
2. This product will provide the ability to be integrated
with POLYCENTER Manager on NetView for DEC OSF/1 AXP.
This functionality will not be available in this field
test baselevel, but will made available in a later field
test release.
Because the functionality is common with the VMS product, we have
just included a copy of the VMS release notes in with the OSF kit for
now. The notes should apply to OSF as well except in the cases
of VMS specific information or functionality not supported in
OSF (ie., alarms/traps).
PLEASE TAKE THE TIME TO READ THE RELEASE NOTES !!!
In addition to those release notes there are a few other notes
we want to add as well.
1. Cosmetically, some of the OSF views may not be quite
as clean as the VMS counterparts. You may find things
like sizings, word alignments, incomplete boxes,
etc. are not quite right. WE ARE AWARE OF THIS.
We thought it best to get as much functionality as
possible going initially and clean up the cosmetics over
the course of the field test. So please hold off on
reporting these type of problems for now.
2. While we have not tested all the different type
of hub modules extensively at this time, we have at least
tested them to some degree. Therefore, feel free to
test HUBwatch against whatever modules you have.
Note that the TELNET view to manage the brouter products
has not been tested yet.
3. The following are know problems in the views:
The Repeater Security view will sometimes crash HUBwatch.
This can happen when you are setting parameters or hit
a push button.
In the bridge view which contains the forwarding
database the option to dump the forwarding database
to a file is not working consistently.
If you are in a view that was invoked from the LAN
Interconnect view, you will encounter the following
unexpected behaviour. When you hit the APPLY button
in one of these views (for example, the Station
Configuration or LAN Interconnect Expanded views)
instead of keeping you in your current view when the
action is complete, HUBwatch will repaint the LAN
Interconnect view over your current view. To get back
to the current view you must first click on the LAN
Interconnect view and then click back on the current view.
Note that if you have polling turned on you will see
the same type of behaviour. When an updated MIB variable
for the LAN Interconnect view is received the LAN
Interconnect view will repaint over whatever is the
current view.
Documentation
The HUBwatch documentation for this kit can be found in
the following places. An updated Installation Guide
is now available on
TNPUBS::USER$653:[J_GOLDSTEIN.PUBLIC]HUBWATCH-V31-INSTALL-CONFIG.PS
The Use Guide has not changed since the previous kit notice. It can
be found on
TNPUBS::PUBLIC$DISK:[PUBLIC.ONEHUB]HUBWATCH_WORKSTATIONSV31_USE.PS
To install the kit use the following steps. The kit will install
on OSF/1 V2.0 or later systems with Motif.
1. Copy HBWTCH310.tar onto your system
2. Do a tar -xvf HBWTCH310.tar
This pulls the HUBwatch subset files out of
the HBWTCH310.tar file and puts then in your
current directory. You probably should make
a directory just for the HBWTCH310.tar file
before you do the tar command so the subset files
are all in one spot and not mixed in with your
other files. Use the mkdir command to create a
new directory.
3. Log in as superuser (use the su command).
4. Do a setld -l directory_name to load the kit.
The directory_name is the directory were the subset
files reside.
5. Do a setenv HUBWATCH_LIBRARY another_directory_name
This sets the directory where the hubwatch_agents file
will be located. You use the same directory as used in
step 4.
6. To start HUBwatch for OSF perform the following command
hubwatch -x IP-address \
-c community-string \
-r retry-count \
-t timeout
where only the -x IP-address is required.
IP address IP address of the hub.
Community string The name assigned to the community.
NOTE: This is a quoted string -
ie., "public".
Retry count The number of retries allowed.
Timeout The timeout period in seconds.
If you have any problems accessing any of the files mentioned in
this note, please let me know.
============================================================================
If you have some question as to the current revision levels of
the hub firmware and Network Access Software that are shipping,
the revisions out of the SSB as of September 27, 1994 are as
follows:
Firmware:
DEChub 900 MultiSwitch Hub Manager V3.1.0
DECagent 90 V2.1.3
DECbridge 90, 90FL V3.1
DECbridge 900MX v1.4.0
DECconcentrator 900MX V2.8.0
DECpacketprobe 90 V2.1
DECrepeater 90FS v1.1
DECrepeater 90TS v1.1.0
DECrepeater 900FP v1.1
DECrepeater 900GM v1.1
DECrepeater 900TM V1.1.0
Network Access Software:
DECserver 90TL, 90M, 900TM V1.4
|