[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

4415.0. "Hubwatch & Auto healing" by KERNEL::WARDJO () Thu May 15 1997 10:03

    Hello,
    
    Can anyone remember if there were any problem with Hubwatch on Ultrix
    and auto healing.
    
    I have a customer running Hubwatch for unix V4.01, MAM V4.1 with a
    Decswitch 900EF V1.5.2. He is configuring a port on the 900EF and 
    switching it to the backplane and connecting it to a lan. He then
    enables autohealing.
    
    The customer then expects this config to be saved as long as autohealing
    remains enabled. He removes the switch from the hub 900 and then
    re-inserts it. When it has finished self test etc, hubwatch shows no
    ports configured to the back plane.
    
    Is this expected behaviour on these versions of software/firmware?
    
    What/where  is the latest kit for Unix.
    
    Any help appreciated.
    
    Regards,
    
    Jon

T.R	Title	User	Personal Name	Date	Lines
4415.1		NETCAD::DOODY	Michael Doody	`Thu May 15 1997 10:14`	7
	With MAM V4.x, Auto Healing is for FDDI only. So you must connect two FDDI modules to a backplane LAN in order for their connections to be restored. In MAM V5.0, Auto Healing has been expanded to all module/media types. -Mike
4415.2	FDDI ports went aswell.	KERNEL::WARDJO		`Fri May 16 1997 09:07`	7
	Thanks for the response Mike, We also tested FDDI links and found that FDDI ports switched to the backplane disappeared with auto healing enabled on this hub when the switch was power cycled. Jon
4415.3		NETCAD::DOODY	Michael Doody	`Fri May 16 1997 10:10`	8
	Was that with a pair of modules? With only one module you do not have any FDDI backplane connections. Just a painted line on the Lan interconnect window. That is the point-to-point nature of FDDI. You could also try MAM V4.2 -Mike
4415.4	There's more	KERNEL::WARDJO		`Fri May 16 1997 11:10`	12
	This is getting slightly stranger. Customer has several hubs and it is only on two of them that auto healing does'nt work. They are all running the same firware versions and are the same hw rev (F05). Example of Working hub serial number AY61504543 Example of failing hub serial number AY61510905 Anyone any ideas? Jon
4415.5		NETCAD::DOODY	Michael Doody	`Fri May 16 1997 17:08`	11
	Well, since Auto Healing is a firmware feature, the serial numbers don't matter. It could be a bug, it could be something they're doing wrong. It could depend on how the backplane connections are set up differently on those two hubs. My suggestion is to upgrade to mam V4.2. -Mike