[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

245.0. "HUBwatch 1.1 Problem accessing DB90 and repeaters" by SAC::HERBERT (Paul Herbert UK Govt A/cs) Fri May 21 1993 10:51

	I have set up the following configuration :

	HUB #1 (ports 1-8)
	DECrepeater90C
	DECrepeater90C
	DECrepeater90C
	DECserver90TL
	blank
	DECrepeater90FA  (fibre link to HUB #2)
	DECbridge90 (v3.1)
	DECagent90 (X1.77)

	HUB #2 (ports 1-8)
	DECrepeater90C
	DECrepeater90C
	DECserver90TL
	DECrepeater90FL (fibre link to HUB #1)
	blank
	blank
	blank
	DECbridge90 (v3.1)

	Using HUBwatch v1.1 (ULTRIX) I can look at the DECagent details and 
	autodiscovery has correctly found all the modules (DS90TL modules 
	added manually). However, I cannot look at the HUB #1 DB90 or repeater 
	details and no port LEDs are lit on the display. Double clicking on 
	the HUB #1 DB90 results in the HUBwatch error message :

	"Failed to get bridge management information"
	
	I can access the HUB #1 DB90 using ccr and hub_management is enabled.

	Accessing HUB #2 works correctly, ie port LEDs are lit and double-
	clicking on all modules works.

	I have three other hub/agents with the same software and differing
	modules. Two behave as described above but one works correctly!

	Any suggetions?

	Thanks, Paul.

T.R	Title	User	Personal Name	Date	Lines
245.1	some suggestions	GIDDAY::DRANSFIELD	Mike Dransfield, Sydney RSSG	`Sat May 22 1993 06:55`	10
	re; .0 Is the thinwire port on the side of hub 1 terminated? Have you reset the DECbridge in hub 1 to factory default? Hold in the recessed button on the front and power cycle. Have you reset the DECagent to factory defaults and tried configuring agina? same procedure as DECbridge. Have you swapped the DECagent (I have seen a high failure rate) thats everything I've ever tried... mike
245.2	Termination and bridge password?	QUIVER::GAUDET		`Tue May 25 1993 13:00`	13
	Yes, Mike's suggestions are good ones. I would also add that you should make sure there is a properly terminated connection on the bridge's backbone (front panel) port (whichever one is selected by the switch). I've seen some strange behavior when you select the BNC with the switch but leave the connector unterminated. A T-connector with two terminators is the proper way to terminate that port. It almost sounds like there is a password set on the bridge which is preventing the agent from getting the information that HUBwatch is requesting. Resetting the bridge to factory settings will clear any password that may be set. ...Roger...
245.3	Still a Problem	SAC::HERBERT	Paul Herbert UK Govt A/cs	`Thu Jun 24 1993 08:30`	19
	I've tried everything in the previous replies except replacing the Agent hardware. Surely the h/w isn't so flaky that I get 4 out of 5 faulty ;^) I still can't manage the bridge. In the command line window I get the following messages when I select an Agent/community and want to "look into" the bridge. (W) status poll: can't reach slot 1 . . . (W) status poll: can't reach slot 5 (E) Failed to get IF interface A terminal connected to the Agent has no problem managing the community. This would appear to be similar to the problem #1 in 284.0 Paul.
245.4	1.1 agent?	GIDDAY::DRANSFIELD	Mike Dransfield, Sydney RSSG	`Thu Jun 24 1993 21:27`	12
	re: .last ARe you using DECagent T1.1 firmware? I just tried using HUBwatch V1.1 with DECagent T1.1 and DECbridge 90 V3.1 (or 3.0) and get the same symptoms. If I connect to the bridge, I get a "bridge is not hub manager" message when I do a show repeater. If I use a DECagent with V1.0, or I use a DECagent with no bridge, then I can manage the repeaters. I can't find a combination that will work to manage both bridges, and repeaters and fibre stuff... :-( Mike