[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

210.0. "hubwatch DB90 not hub manager errors" by GIDDAY::DRANSFIELD (Mike Dransfield, Sydney RSSG) Thu Apr 22 1993 08:06

    I have a problem getting hubwatch for VMS to work with a dual hub.
    Versions are:
    HUBWATCH T1.1.8
    DENMA - latest 1.1 copied from DIRT::DENMA$FT: two days yesterday
    DB90 - 3.1
    DS90TL - 1.0 BL34.10
    
    HUBwatch comes up and can talk to the agent and bridge (which I 
    added manually) but can't talk to any of the repeater 90T's.
    
    If I connect to the bridge and do a
    SHOW REP
    it returns
    bridge is not the hub manager...I suspect this is the heart of the
    problem.
    Also SHOW ADDRESS
    returns multiple addresses for some slots and addresses for empty
    slots.
    It seems like it might be the DB90 3.1 code which is flakey.....
    
    This is a demo for a potentially large site, so some urgent
    suggestions would be welcomed.
    We are going to  try 29b DB90 code which seemed more reliable with
    the address info....
    
    thanks for any suggestions,
    Mike

T.R	Title	User	Personal Name	Date	Lines
210.1	Hub Management enabled?	WOTVAX::HATTOS	I think, Therefore I'm paid less	`Tue Apr 27 1993 06:48`	3
	If you connect via NCP to the Bridge, is Hub Management enabled? Stuart
210.2	enbled	GIDDAY::DRANSFIELD	Mike Dransfield, Sydney RSSG	`Wed Apr 28 1993 00:55`	3
	re: .1 yes Mike
210.3	still wrong!!!!!@#$%%!	GIDDAY::DRANSFIELD	Mike Dransfield, Sydney RSSG	`Tue May 04 1993 04:19`	13
	what gives here? I have this on three different bridges running V3.1 code. Resetting one bridge made the bridge think it was the hub manager again. This is happening on both 16 and 8 slot hubs. They have been reset to factory settings. What does it mean? How do I get rid of it? It makes hubwatch not find the repeaters as the bridge thinks it can't manage them!!! This does not make hubwatch look good (along with the repeater address's being wrong I am beginning to feel that I am flogging a dead horse here!!!!!!!) thanks, Mike
210.4	Bridge V 3.1 OK here	CGOS01::DMARLOWE	dsk dsk dsk (tsk tsk tsk)	`Tue May 04 1993 13:51`	8
	I upgraded my bridge (in hub) to V3.1 from V3.0. After it came back online it took about 1-2 minutes to become the bus master and then all was fine. Very clean. Are you running more than 1 bridge in the hub or a bridge in each hub if daisy chained? dave
210.5	correctly configured...	GIDDAY::DRANSFIELD	Mike Dransfield, Sydney RSSG	`Tue May 04 1993 20:07`	19
	re: .4 thanks for the reply. this has happened on three hubs. Two of them are daisy chained 16 port hubs, one is a single 8 port hub. All are corretly configured. i.e one bridge in slot 8, agent in slot 7 (there is only one and it has been tried in a couple of hubs due to problems with one agent hanging and having to be replaced). The management cable and thinwire connect the two hubs in the daisy chained configuration. I have seen the "Bridge is not the hub master" a few times. I saw it at another site soon after a power up on a show repeater command, but when I reentered the command, it returned the info. The site with the hubs described above is the only one where I have seen it repeatedly fail with the not hub master message. And I still have no idea why the bridge should think it isn't the master. Is it some signal on the management bus? Is there a command to ask who IS the master? thanks, Mike