[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

1873.0. "Problem with chained HUBs and HUBwatch (VMS 3.1)" by DECPRG::PRNET::Pilar () Wed Jan 11 1995 16:13

Hi,

I have problem with chained hub. The configuration is following:

First hub:

Slot:	Modul:
1	DECrepeater 90FL	V 1.0
2	DECrepeater 90FL	V 1.0
3	DECrepeater 90T		V 1.0
4	DECrepeater 90T		V 1.0
5	DECserver 90L+		V 2.0 BL 5.2
6	DECserver 90L+		V 2.0 BL 5.2
7	DECbridge 90FL		HW V 2.0, ROM V 2.0, SW V 3.1
8	DECagent90		HW V=D01, ROM=BL 05.00, SW=2.1.3

Second hub:

Slot:	Modul:
1 (9)	<empty>
2 (10)	<empty>
3 (11)	DECserver 90L+		V 2.0 BL 5.2
4 (12)	<empty>
5 (13)	<empty>
6 (14)	DECrepeater 90T		V 1.0
7 (15)	<empty>
8 (16)	<empty>

Hubs are connected by thinwire segment and serial cable. HUBwatch 
is able to discover all modules in first hub but nothing in second one. 
When I add manually both module terminal server was managable but repeater 
was not (no info about ports etc.)

DECagent has community "public" and additional four communities to manage 
four 8-slot hubs with DECbridge 90FL (F/W V 3.1). Those four hubs are 
managable  without problems (it was working even with F/W V 3.0 in 
DECbridge 90FL). 

Customer has second very similar chained hubs (containing modules with the 
same firmware version) but without DECbridge 90FL. This config is working 
without problems.

Does anybody have any suggestion ?

Thank you in advance

Jarry

T.R	Title	User	Personal Name	Date	Lines
1873.1	Tell the DECagent it is a 16-slot DEChub 90.	SLINK::HOOD	I'd rather be at the Penobscot	`Wed Jan 11 1995 17:03`	8
	You have to tell the DECagent that you are managing a 16-slot hub. You can do this in the Community->Manage Table window in HUBwatch. Use the bottom half of that window (DECagent 90 communities) and select the 16-slot (vs 8-slot) DEChub 90 icon. Tom Hood HUBwatch
1873.2	Serial cable was wrong	DECPRG::PRNET::Pilar		`Thu Jan 12 1995 15:27`	7
	Hi Tom, thank you for your suggestion. Agent was configured to manage 16-slot hub, but serial cable was wrong. I was today at the customer side and change the cable. Everything started to work immediately. Jarry
1873.3	Should not need HUBwatch to set the community type	ROGER::GAUDET	Because the Earth is 2/3 water	`Thu Jan 12 1995 15:58`	8
	With DECagent V2.1.3, you should not have to tell it what type of hub it is in. The agent should discover the 16-slot configuration automatically and then tell HUBwatch that it is managing a 16-slot hub. I'm glad it turned out to be a cabling problem, since this is a feature of the agent that has been working for quite some time now. ...Roger... Ex-DECagent_firmware_dude
1873.4	Yes, it was detected automaticaly	DECPRG::PRNET::Pilar		`Fri Jan 13 1995 08:47`	10
	Hi Roger, you are right. I did not have to enter hub type (16-slot) it was discovered automaticaly even with wrong serial cable. I saw also some small problem with DECrepeater 90 management (connected station value seems to be bad) but I'll put it to the different topic. Regards Jarry