[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

2346.0. "HUBwatch V4.0 available for OSF, Windows" by STEVEV::VINGERHOET () Tue Jun 06 1995 12:42


           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.

T.RTitleUserPersonal
Name
DateLines
2346.1Need Version 4 :^(DPDMAI::WISEEPobodys NerfectTue Aug 08 1995 14:44105
    I should have been a little more exact in my request. Where is al copy 
    of VERSION 4 of HUBwatch?
    
    An edited copy of 2346.0 is attached. HUBloader is at an FTP location
    
    HUBwatch is not at this location... at least that I have been able to
    find!
    
    At location 'bhub' (16.21.16.156) I see the following dirs..
    
    bin (bin their no HW )  	dcf_unix (Don't use the U word with Windows)  	
    ect (Not here either )	hubloader (has hubloader in it DUH )
    hubw_pc (EMPTY)		hubw312 (Need version 4)
    hubwatch (.tar files)	hubwatch osf (Not on my PC)
    ov (openView?)		pub (no Subdirs)
    tmp (no Subdirs)	
    
    	That stated. Where is a FTP able copy of HUBwatch V4.*?
    
    	Efw
    P.S. re .1 Thanks for your prompt reply!
    
    
            <<< NETCAD::KALI$USER3:[NOTES$LIBRARY]HUB_MGNT.NOTE;1 >>>
                   -< DEChub/HUBwatch/PROBEwatch CONFERENCE >-
================================================================================
Note 2346.0         HUBwatch V4.0 available for OSF, Windows          No replies
STEVEV::VINGERHOET                                  199 lines   6-JUN-1995 11:42
--------------------------------------------------------------------------------
	   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.

2346.2Hubwatch 4.0 Still neededJULIET::CABREIRA_ROBobby CabreiraFri Sep 29 1995 18:509
    Hi.  I have a need for Hubwatch 4.0.  I understand that 4.1 is already
    released, but we still need 4.0.  Does anybody have a pointer to where
    the files may be?  
    
    
    thanks in advance,
    
    
    Bobby C.