|
HUBwatch for OSF/1 V3.1 is now available. The kit can be obtained
by anonymous ftp on bhub (hubwatch_osf/HBWTCH310.tar). The
IP addresses of bhub is 16.21.16.156. For those of you who need
DECnet access bhub has address 55.91 and the above tar file can
be found at /var/users/ftp/hubwatch_osf/HBWTCH310.tar.
You will need to obtain a PAK to run this software.
Note that all HUBwatch kits support the DEChub 90, DEChub 900
Multiswitch and GIGAswitch/FDDI devices. This point is made because
for all the supported platforms (PC Windows, VMS and OSF/1) the
documentation claims that HUBwatch supports the GIGAswitch. With
the introduction of the GIGAswitch/ATM "GIGAswitch" can now mean
two different devices. Note that no version of HUBwatch currently
supports GIGAswitch/ATM.
============================================================================
Documentation
The HUBwatch documentation for this kit can be found in directory
TNPUBS::PUBLIC$651:[PUBLIC.ONEHUB]
The files are
HUBWATCH_V31_INSTALL.PS Installation Guide
HUBWATCH_WORKSTATIONSV31_USE.PS Use Guide
============================================================================
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 \
-a agent-name \
-c community-string \
-r retry-count \
-t timeout
where only the -x IP-address is required.
IP-address IP address of the hub.
agent-name The name assigned to the agent
module
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.
============================================================================
Launching HUBwatch from NetView
If you have NetView, when installing HUBwatch be sure to answer
yes to the question regarding if you want to install the NetView
specific HUBwatch files.
In order to launch HUBwatch from NetView the hubwatch_agents file
will ALWAYS be required. Therefore, be sure to set HUBWATCH_LIBRARY
to where the hubwatch_agents file is located. Each hub in the NetView
map that you would like to launch HUBwatch against must have an entry
in the hubwatch_agents file.
When you are running NetView you can select HUBwatch from two
places:
1. as a pull-down application selection under the Monitor
entry in the Menu Bar
2. as a pull-down application selection under the Monitor
when hitting MB3 over a symbol in the map
Note that the "HUBwatch" application will be greyed out and
therefore not selectable. In order to launch HUBwatch against
a particular symbol in the NetView map, NetView must be instructed
that the symbol is a hub and therefore an acceptable device to
launch HUBwatch against.
HUBwatch defines a "isDEChub" field in NetView. In order to
launch HUBwatch for a particular hub on your NetView map you
need to have this field set. If this is not set, "HUBwatch" is
greyed out as an application selection. Once set "HUBwatch"
becomes selectable for that particular hub. To set this field
do the following:
In NetView, select the symbol representing the hub. Choose
Edit -->Modify/Describe --> Object.
IMPORTANT
Note the SelectionName in this window. The SelectionName is
what NetView passes as an input parameter when it tries to
launch HUBwatch. This SelectionName has to exactly
match the name field in the hubwatch_agents file entry for
that hub. Even if the SelectionName looks like an IP address
the name field must then be the IP address.
Double click on General Attributes and scroll down to IsDEChub.
Click on True. Click on OK on the various windows until you are
back to the map. At this point "HUBwatch" should be blackened
and therefore launchable.
There is one thing to note about the SelectionName that may
cause some confusion. The SelectionName of a hub will be
different based on what NetView map it is in when you attempt
to launch HUBwatch. For example, you may have a network map
where is hub is just one of many devices. In this case the
SelectionName may be something like "test.lkg.dec.com". If you
double click on that hub you may get an expanded map with
just two symbols - the hub itself and the OBM (out of band
managment). For this map the hub SelectionName may be
something like "test.lkg.dec.com:Hub". You would find that
you can launch HUBwatch from the first map but not the second.
This is because only one of the SelectionNames will match the
name field in the hubwatch_agents file.
|
|
The HUBwatch for OSF/1 AXP (Digital UNIX) and HUBwatch for Windows
Software Version 4.0 are available. When running, these applications
will identify themselves as V4.0.1.
Note that there is a standalone kit for the HUBloader for
Windows V1.0.0 available as well.
The HUBwatch V4.0 documentation is available in directory
TNPUBS::DSA1:[PUBLIC.ONEHUB]. TNPUBS has DECnet address 4.62.
The files are:
HUBWATCH_V40_INSTALL_SSB.PS;1
HUBWATCH_WINDOWSV40_USE_SSB.PS;1
HUBWATCH_WORKSTATIONV40_USE_SSB.PS;1
HUBWATCH_WINDOWSV40_QUICKSTART_SSB.PS;1
Functionality
-------------
HUBwatch, Version 4.0, is a network management application used to
manage the DEChub family of products including the DEChub 900
MultiSwitch, DEChub 90, DEChub ONE, and DEChub ONE-MX hubs, and
GIGAswitch/FDDI and GIGAswitch/ATM (ATM only available on Windows).
Refer to the HUBwatch for OSF/1 or HUBwatch for Windows, Version
4.0 Software Product Descriptions (SPD 46.65.02 and SPD 37.87.05
respectively) for a detailed description of these products,
including software and hardware prerequisites.
Also included with both versions of HUBwatch V4.0, is the HUBloader
application that can be used to upgrade your firmware. Please
refer to the release notes or READ_ME_.TXT file on the Windows
diskette #1 for more information. For Digital UNIX refer to the
release notes at /usr/kits/HUBwatch/hubloader.release_notes.
The detailed information concerning HUBloader functionality
is contained in the online help on both platforms.
HUBwatch Release Notes
----------------------
Before installing HUBwatch for OSF/1 AXP, read the release notes.
The release notes are on the HUBwatch distribution media. The
installation procedure copies the release notes to the directory
/usr/kits/HUBwatch. The release notes are the files
hubwatch.release_notes and hubloader.release_notes. The release
notes contain important information that is not included in the
printed manuals or the HUBwatch online help.
Before installing the HUBwatch for Windows, please read the READ_ME
files on diskette #1 of the HUBwatch distribution media. After in-
stalling HUBwatch, read the release notes. You access the release
notes by clicking on the Release Info option from the Hub Front
Panel Help pulldown menu. The READ_ME files and the release notes
contain important information that is not included in the printed
manuals.
We cannot stress enough the importance of reading the release
notes before using HUBwatch so
READ THE RELEASE NOTES BEFORE USING HUBWATCH!!!
Firmware Notes
--------------
HUBwatch software requires that each of your hubs, network
modules, and switches is running the most recently released
version of the firmware. To ensure that you have the latest
functionality and quality of firmware see note 2344 in this
notesfile. Please insure that your devices are at the latest
revision.
OSF/1 AXP Kit Locations for Internal Use Only
---------------------------------------------
The HUBwatch for OSF/1 AXP kit can be obtained by anonymous ftp on
bhub (16.21.16.156). For those of you who need DECnet access bhub
has address 55.91. The kit will need the HUBWATCH-FOR-OSF PAK to
run. PAKs for internal use can be obtained from VTX.
Using anonymous ftp the official HUBwatch for OSF/1 kit can
be copied (use binary mode) from
hubwatch_osf/HBWTCH400.tar
Using DECnet access this tar file can be found at
/var/users/ftp/hubwatch_osf/HBWTCH400.tar
To install this OSF kit use the following steps. The kit will
install on OSF/1 V2.0 or later systems with Motif. For more
details refer to the HUBwatch Installation and Configuration manual.
1. Copy HBWTCH400.tar onto your system
2. Do a tar -xvf HBWTCH400.tar
This pulls the HUBwatch subset files out of
the HBWTCH400.tar file and puts then in your
current directory. You probably should make
a directory just for the HBWTCH400.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. Delete the HUBwatch of OSF V3.1 kit by performing a
#setld -d HBWTCH310
5. Do a #setld -l directory_name to load the V4.0 kit.
The directory_name is the directory were the subset
files reside.
Windows Kit Locations for Internal Use Only
---------------------------------------------
The HUBwatch/Windows V4.0 diskettes can be copied from the
following directories:
NAC::NIPG:[MANAGE.WINDOWS.WINDOW40.DISK1] HUBwatch
NAC::NIPG:[MANAGE.WINDOWS.WINDOW40.DISK2] HUBwatch
NAC::NIPG:[MANAGE.WINDOWS.WINDOW40.DISK3] HUBwatch
NAC::NIPG:[MANAGE.WINDOWS.WINDOW40.DISK4] HUBwatch 900 demo
NAC::NIPG:[MANAGE.WINDOWS.WINDOW40.DISK5] GIGAswitch/FDDI demo
NAC::NIPG:[MANAGE.WINDOWS.WINDOW40]HW_WIN_V40_SPD.PS SPD
NAC::NIPG:[MANAGE.WINDOWS.WINDOW40]HW_WIN_V40_SPD.TXT SPD
Note that if you plan on installing from hard drive rather than
building diskettes, disk1-3 must be in a single directory.
HUBloader for Windows V1.0.0
----------------------------
The official version of the HUBloader for Windows V1.0.0 standalone
kit is now for use. This product will perform firmware
load upgrades of hub modules, hubs and the GIGAswitch/FDDI.
This standalone version of HUBloader for Windows will be
available through SSB as part of the DEChub Consolidated Firmware
kit. The HUBloader software will also be bundled in as part of
HUBwatch for Windows V4.0 kit.
(One minor nit:
The HUBloader READ_ME_.TXT included in the HUBwatch kit
has one note referring to a system error concerning
the AUX device. The READ_ME_.TXT included in the
standalone HUBloader kit does not contain this note.
This note was a mistake - please disregard it.)
The kit can be obtained by anonymous ftp on bhub. The files
that make up the kit are
hubloader/DISK.ID
hubloader/HUBLD100.001
hubloader/INSTALL.EXE
hubloader/LOAD100.INF
hubloader/LOGO.BMP
hubloader/READ_ME_.TXT
The IP addresses of bhub is 16.21.16.156. For those of you
who need DECnet access bhub has address 55.91 and the above
files can be found at /var/users/ftp/hubloader. If using
ftp to obtain the files, please copy the files over in binary mode.
IMPORTANT FOR FIRST TIME USERS
- No hardcopy documentation of HUBloader will be available.
Therefore, the only other documentation available is a
READ_ME_.TXT file as part of the HUBloader kit for
release notes and to explain installation. There is also
online help to explain the HUBloader functionality and its
interface.
READ THE READ_ME_.TXT FILE !!!!
- Loading modules requires a TFTP Server to perform the actual
file loads. The TFTP Server we provide is a seperate utility
from the HUBloader utility and must be up and running before you
attempt a load from the HUBloader utility. This is different
than what people who use NDU are familiar with.
This misunderstanding caused a lot of people trouble during
field test, so read the READ_ME_.TXT and online help to make
sure you have this utility running first.
|
|
The HUBwatch for Digital UNIX and HUBwatch for Windows V4.1 kits
are available. When running, these applications will identify
themselves as V4.1.1.
Note that besides being integrated as part of the above HUBwatch
kits there also is a standalone kit for the HUBloader for
Windows. HUBloader will now identify itself as V1.1.0.
For HUBwatch V4.1 the only documentation that has changed from
V4.0 is the HUBwatch Installation and Configuration Guide. All
the other documentation is available in directory
TNPUBS::DSA1:[PUBLIC.ONEHUB]. TNPUBS has DECnet address 4.62.
The files are:
HUBWATCH_WINDOWSV40_USE_SSB.PS;1
HUBWATCH_WORKSTATIONV40_USE_SSB.PS;1
HUBWATCH_WINDOWSV40_QUICKSTART_SSB.PS;1
A pointer will be added when the V4.1 HUBwatch Installation and
Configuration Guide becomes available. The previous V4.0 guide
can be used for the short term.
Functionality
-------------
HUBwatch, Version 4.1, is a network management application used to
manage the DEChub family of products including the DEChub 900
MultiSwitch, DEChub 90, DEChub ONE, and DEChub ONE-MX hubs, and
GIGAswitch/FDDI and GIGAswitch/ATM (ATM only available on Windows).
The main functionality add to HUBwatch for this release is
support for the Digital MultiStack System.
Refer to the HUBwatch for Digital UNIX or HUBwatch for Windows,
V4.1 Software Product Descriptions (SPD 46.65.xx and SPD 37.87.xx
respectively) for a detailed description of these products,
including software and hardware prerequisites.
Also included with both versions of HUBwatch V4.1, is the HUBloader
application that can be used to upgrade your firmware. Please
refer to the release notes or READ_ME_.TXT file on the Windows
diskette #1 for more information. For Digital UNIX refer to the
release notes at /usr/kits/HUBwatch/hubloader.release_notes.
The detailed information concerning HUBloader functionality
is contained in the online help on both platforms. The HUBloader
contains some minor bug fixes since the V1.0.0 release.
HUBwatch Release Notes
----------------------
Before installing HUBwatch for Digital UNIX, read the release notes.
The release notes are on the HUBwatch distribution media. The
installation procedure copies the release notes to the directory
/usr/kits/HUBwatch. The release notes are the files
hubwatch.release_notes and hubloader.release_notes. The release
notes contain important information that is not included in the
printed manuals or the HUBwatch online help.
Before installing the HUBwatch for Windows, please read the READ_ME
files on diskette #1 of the HUBwatch distribution media. After in-
stalling HUBwatch, read the release notes. You access the release
notes by clicking on the Release Info option from the Hub Front
Panel Help pulldown menu. The READ_ME (.TXT and .PS) files and the
release notes contain important information that is not included
in the printed manuals.
We cannot stress enough the importance of reading the release
notes before using HUBwatch so
READ THE RELEASE NOTES BEFORE USING HUBWATCH!!!
Firmware Notes
--------------
HUBwatch software requires that each of your hubs, network
modules, and switches is running the most recently released
version of the firmware. To ensure that you have the latest
functionality and quality of firmware see note 2 in this
notesfile. Please insure that your devices are at the latest
revision.
Kit Locations for Internal Use Only
-----------------------------------
The HUBwatch for Digital UNIX kit can be obtained by anonymous ftp
on bhub (16.21.16.156). For those of you who need DECnet access
bhub has address 55.91. The kit will need the HUBWATCH-FOR-OSF
PAK to run. PAKs for internal use can be obtained from VTX.
Using anonymous ftp the official HUBwatch for Digital UNIX kit can
be copied (use binary mode) from
hubwatch_osf/HBWTCH410.tar
Using DECnet access this tar file can be found at
/var/users/ftp/hubwatch_osf/HBWTCH410.tar
To install this OSF kit use the following steps. The kit will
install on Digital UNIX V2.0 or later systems with Motif. For more
details refer to the HUBwatch Installation and Configuration manual.
1. Copy HBWTCH410.tar onto your system
2. Do a tar -xvf HBWTCH410.tar
This pulls the HUBwatch subset files out of
the HBWTCH410.tar file and puts then in your
current directory. You probably should make
a directory just for the HBWTCH410.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. Delete previous HUBwatch kits by performing a
#setld -d HBWTCH310
and/or
#setld -d HBWTCH400
to remove V3.1 and/or V4.0 kits.
5. Do a #setld -l directory_name to load the V4.1 kit.
The directory_name is the directory were the subset
files reside.
The HUBwatch for Windows V4.0 files can be copied as
follows. Using anonymous ftp the files can be copied
(use binary mode) from directories
hubw_pc/disk1
(Files: DISK.ID, HUBV411.001, HUBW40.INF,
INSTALL.EXE, LOGO.BMP, READ_ME.PS,
READ_ME.TXT, READ_ME_.TXT)
hubw_pc/disk2
(Files: DISK.ID, HUBV411.002)
hubw_pc/disk3
(Files: DISK.ID, HUBV411.003)
Using DECnet access these files can be found in directories
/var/users/ftp/hubw_pc/disk1
/var/users/ftp/hubw_pc/disk2
/var/users/ftp/hubw_pc/disk3
Note that if you plan on installing from hard drive rather than
building diskettes, disk1-3 must be in a single directory.
HUBloader for Windows V1.1.0
----------------------------
The official version of the HUBloader for Windows V1.1.0 standalone
kit is also available for use. This product will perform firmware
load upgrades of hub modules, hubs and the GIGAswitch/FDDI.
This standalone version of HUBloader for Windows will be
available through SSB as part of the DEChub Consolidated Firmware
kit. The HUBloader software will also be bundled in as part of
HUBwatch for Windows V4.1 kit.
The kit can be obtained by anonymous ftp on bhub. The files
that make up the kit are
hubloader_pc/DISK.ID
hubloader_pc/HUBLD110.001
hubloader_pc/INSTALL.EXE
hubloader_pc/LOAD110.INF
hubloader_pc/LOGO.BMP
hubloader_pc/READ_ME_.TXT
The IP addresses of bhub is 16.21.16.156. For those of you
who need DECnet access bhub has address 55.91 and the above
files can be found at /var/users/ftp/hubloader_pc. If using
ftp to obtain the files, please copy the files over in binary mode.
IMPORTANT FOR FIRST TIME USERS
- No hardcopy documentation of HUBloader will be available.
Therefore, the only other documentation available is a
READ_ME_.TXT file as part of the HUBloader kit for
release notes and to explain installation. There is also
online help to explain the HUBloader functionality and its
interface.
READ THE READ_ME_.TXT FILE !!!!
- Loading modules requires a TFTP Server to perform the actual
file loads. The TFTP Server we provide is a seperate utility
from the HUBloader utility and must be up and running before you
attempt a load from the HUBloader utility. This is different
from what people who use NDU are familiar.
This misunderstanding causes a lot of people trouble,
so read the READ_ME_.TXT and online help to make
sure you have this utility running first.
|