| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 8.1 | HUBwatch Windows pointer | DELNI::BUZZELL | | Thu Aug 18 1994 13:49 | 10 |
|
17 June 94- NAC::NIPG:[MANAGE.WINDOWS]WINDOWS.TXT
HUBwatch for Windows 2.01 (includes Novell patch and release notes): Copy
NAC::NIPG:[MANAGE.WINDOWS.WINDOWS2.DISK1]*.* and .DISK2 onto two
separate disks and then type A:INSTALL with DISK1 in the A drive. Please let
us know about bugs by putting a note in NOTED::HUB_MGNT. Manuals can be found
on TNPUBS::PUBLIC$651:[PUBLIC.HUBWTWIN]. Please do a loan of products (see
NAC::MANAGEMENT:LOAN.TXT) if you plan to leave this version with a customer.
|
| 8.2 | HUBwatch for Windows V3.1 | SLINK::HOOD | I'd rather be at the Penobscot | Tue Nov 01 1994 10:03 | 19 |
| released version of HUBwatch for Windows 3.1 available
HUBwatch for Windows 3.1 can be found at:
NAC::NIPG:[MANAGE.WINDOWS.WINDOW31.DISK1]*.*
NAC::NIPG:[MANAGE.WINDOWS.WINDOW31.DISK2]*.*
NAC::NIPG:[MANAGE.WINDOWS.WINDOW31.DISK3]*.*
note: DISK3 is the HUBwatch tutorial.
The manuals can be copied from
TNPUBS::PUBLIC$651:[PUBLIC.ONEHUB]HUBWATCH_WINDOWS_V31_USE.PS;1
and
TNPUBS::PUBLIC$651:[PUBLIC.ONEHUB]HUBWATCH-V31-INSTALL-CONFIG.PS;1
FDDI hub devices are now managed - DECbridge 900MX/DECswitch 900EF,EE,
DECconcentrator 900MX, and PEswitch 900EF. This version also manages
the DECrepeaters 900FP, 90FS and 90TS. GIGAswitch will be managed from Windows
in the next version. Currently it is only manageable from VAX/VMS and OSF1
AXP. See NAC::NIPG:[MANAGE.CONFG]HUBWATCH.TXT for more details.
|
| 8.3 | correction? | AIMTEC::ZANIEWSKI_D | Why would CSC specialists need training? | Tue Nov 15 1994 11:08 | 12 |
| There is no
TNPUBS::PUBLIC$651:[PUBLIC.ONEHUB]HUBWATCH-V31-INSTALL-CONFIG.PS
file, but there is a
TNPUBS::PUBLIC$651:[PUBLIC.ONEHUB]HUBWATCH_V31_INSTALL.PS
-and-
NAC::NIPG:[MANAGE.CONFG]HUBWATCH.TXT
should be
NAC::NIPG:[MANAGE.CONFIG]HUBWATCH.TXT
Dave Zaniewski
|
| 8.4 | New location for HUBwatch Use and Installation and Configuration manuals | TNPUBS::F_BUTLER | | Fri Mar 17 1995 14:44 | 12 |
| You can now print the manuals from this location:
DSA1:[PUBLIC.ONEHUB]
HUBWATCH_V31_INSTALL.PS;1
HUBWATCH_WINDOWS_V31_USE.PS;
HUBWATCH_WINDOWS_V31_QUICK_START.PS;1
HUBWATCH_WORKSTATIONSV31_USE.PS;2
Sorry for any inconvenience.
Lee
|
| 8.5 | | TENNIS::KAM | Kam USDS (714)261-4133 (DTN 535) IVO | Wed Aug 23 1995 19:36 | 16 |
| The Integrated Repository indicates the following for HUBwatch, see
below, however, I can't seem to find 4.0 on the net?
Regards,
kam
Date Document
Posted Title/Description ID
1 24-Jun-95 HUBwatch for SunOS, Version 3.1 SP6403
2 07-Jun-95 HUBwatch for Digital UNIX, Version 4.0 SP4665
3 02-Jun-95 HUBwatch for Windows, Version 4.0 SP3787
4 01-Sep-94 HUBwatch for OpenVMS VAX, Version 3.1 SP4574
5 24-Feb-93 HUBwatch for ULTRIX, Version 1.1 SP4064
|
| 8.6 | HUBwatch for Windows V4.0 | NETCAD::FORINO | | Thu Sep 14 1995 18:03 | 199 |
|
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.
|
| 8.7 | HUBwatch for Windows V4.1 | NETCAD::FORINO | | Thu Sep 14 1995 18:04 | 211 |
|
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.
|
| 8.8 | V4.1 Installation Guide Pointer | NETCAD::FORINO | | Wed Oct 18 1995 15:35 | 18 |
| Folks,
The Installation Guide for HUBwatch V4.1 is now available on
TNPUBS::DSA1:[PUBLIC.ONEHUB]. Due to problems with the documentation
tools the guide is not available as one file. The guide is composed of
the following files:
HUBWATCH_V41_INSTALL_SSB01.PS;1 HUBWATCH_V41_INSTALL_SSB02.PS;1
HUBWATCH_V41_INSTALL_SSB03.PS;1 HUBWATCH_V41_INSTALL_SSB04.PS;1
HUBWATCH_V41_INSTALL_SSB05.PS;1 HUBWATCH_V41_INSTALL_SSB06.PS;1
HUBWATCH_V41_INSTALL_SSB07.PS;1 HUBWATCH_V41_INSTALL_SSB08.PS;1
HUBWATCH_V41_INSTALL_SSB09.PS;1 HUBWATCH_V41_INSTALL_SSB10.PS;1
HUBWATCH_V41_INSTALL_SSB11.PS;1 HUBWATCH_V41_INSTALL_SSB12.PS;1
HUBWATCH_V41_INSTALL_SSB13.PS;1 HUBWATCH_V41_INSTALL_SSB14.PS;1
John
|