[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

1506.0. "Bridge 90 not hub manager - why?" by KERNEL::WARDJO () Fri Sep 30 1994 08:02

    Hello,
    
    I have a customer who is having problems manageing repeaters in a
    DEChub90. He has a central DEChub900 containing a DECbridge 900MX whch
    connects his 4300 running hubwatch V3. Also in the Dechub900 is a
    Decrepeater 900FP which has connections to 2 Dechub90s. Both
    Dechub90s connect to the Dechub900 via a bridge 90.
    
    In the first Dechub90 there is also a decagent 90 and 2 decrepeater
    90C. These repeaters are picked up and can be displayed by Hubwatch. In
    the second Dechub90, aswell as the bridge there is also a decrepeater
    90c & 90FA. Both these repeaters are not seen by hubwatch (althogh the
    bridge is).
    
    If I connect to the second bridge via NCP and do a >SHOW REPEATER we
    get the error that the bridge is not the Hub manager, even though hub
    management is enabled.
    
    Can anyone suggest a reason for this?
    
    Decagent 90 V2.1.3
    Decbridge 90FL V3.1
    
    If my understanding is correct, you should be able to manage remote
    hub90 (repeaters) useing the Decagent 90 V2.1.3 if you have a Bridge in
    that hub (the agent can be anywhere on the lan). Is there sumething
    that can stop the bridge becoming the hub manager?
    
    Any help appreciated.
    
    Jon

T.R	Title	User	Personal Name	Date	Lines
1506.1	Some possibilities	ROGER::GAUDET	Because the Earth is 2/3 water	`Fri Sep 30 1994 10:43`	13
	Jon... I do not know why that bridge has relinquished mastership of the backplane, but it should take about 2 minutes before it re-establishes mastership. Given your configuration, there are no other devices in that hub which would assume mastership of the backplane, so it doesn't make sense that the bridge gave it up. If you can afford to reset the bridge, do it. I have occasionally seen the DECbridge 90/90FL go into that state for no apparent reason. You might also check to make sure that there are no bent pins on the backplane connector of the bridge. It's a long shot but worth checking. ...Roger...
1506.2	another long shot...	NETCAD::SLAWRENCE		`Tue Oct 04 1994 17:14`	5
	Is there by any chance a DECserver 90L+ in the hub with the non-master DECbridge 90? There was a problem with a rev of the firmware that caused the bridge to give up mastership. The latest ROM 5.4 fixes it.
1506.3	Still not working	KERNEL::WARDJO		`Wed Oct 05 1994 12:27`	24
	Thanks for the replies, The only things in this hub are the bridge & 2 repeaters. I have tried factory resetting the bridge. I have tried 2 other bridges. I have put an agent in the hub and cannot see the repeaters from the show community of the console. I have disabled back plane management on the agent & enabling on the bridge. Non of this makes any difference, the bridge does not become the hub manager. I have even replaced the backplane but it makes no difference. I can't help feeling there is something simple I am missing here. Anyone have any more ideas? Thanks, Jon.
1506.4	You want simple, I've got simple	ROGER::GAUDET	Because the Earth is 2/3 water	`Wed Oct 05 1994 14:21`	1
	Is there a terminator on the side of the hub?
1506.5	Yes - there is a terminator	KERNEL::WARDJO		`Thu Oct 06 1994 07:19`	5
	Yes, The hub does have a terminator. Jon
1506.6	Grasping at straws	ROGER::GAUDET	Because the Earth is 2/3 water	`Thu Oct 06 1994 12:07`	21
	Jon, it really sounds like one of the repeaters is not working properly. Something is causing problems on the management bus of that hub to cause the bridge and DECagent to not see the repeaters. A few more things to check: 1) Is there anything connected to the MMJ connector on the side of the hub? If this hub is not daisy-chained to another hub, there should be nothing connected. 2) Did you remove the bridge when you tried to "see" the repeaters with the DECagent you inserted in that hub? If so, then this is more support for my claim that one of the repeaters is the cause of the trouble. That is, if you had only a DECagent and the repeaters in the hub and you still could not see the repeaters from the agent's Show Community menu selection, then something is wrong with one of the repeaters. 3) Can you remove one of the repeaters from the problem hub and insert it into the working hub? If you can, does it appear in that community? If so, then it might be working OK. The DECagent is a bit more lenient on the timing of backplane responses than the DECbridge, so although it appears in the agent's hub it may not necessarily be working 100%. But it's a start. ...Roger...