[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

1235.0. "What do we need in the hub to manage ?" by STROP::LAYLAND (The good die young, the wealthy stay healthy.) Tue Jul 19 1994 13:38

I am revisiting the hub 90, and I have a question concerning the manageability
of the hub90 and what is required in the backplane. 

My customer has a number of remote and local hubs, he requires to be able to 
see all the modules in the hubs in particular if any are removed. The remote hubs
are connected by Brouters. Does he require an agent in each hub, or can he 
provide the same functionallity with the 90FL bridge ?

Thanks in advance John Layland

T.R	Title	User	Personal Name	Date	Lines
1235.1	It can be done	ROGER::GAUDET	Because the Earth is 2/3 water	`Tue Jul 19 1994 14:17`	14
	Using a DECagent 90 running V2.1.3 firmware, you can manage the hubs with a single DECagent 90, provided that the configuration is within the limitations set forth by the DECagent 90 (16 hubs or 64 total modules being managed). However, you will need a DECbridge 90/90FL in the remote hubs. The DECagent 90 cannot manage the remote hubs through the brouters. Or you can install a DECagent 90 in each hub. Remember that older DECserver 90/90L/90L+ modules cannot be auto-discovered and undiscovered. These devices must be manually added to a community and become "unreachable" but do not "go away" when removed. This applies to both the local (to the DECagent) community and remotely managed communities through a DECbridge. ...Roger...
1235.2	A little more ...	WELLIN::MCCALLUM		`Wed Jul 20 1994 08:46`	14
	Further clarification is needed I think, If you dont mind bridging MOP in the WAN ( ie the Brouters) then a central DECagent 90 can talk MOP to a remote DECbridge to manage the components in the remote hub. If you dont like bridging MOP and only want to route IP, then a separate DECagent 90 would be needed in each hub, but no local bridge would then be needed for management. Dave.
1235.3	It works	STROP::LAYLAND	The good die young, the wealthy stay healthy.	`Thu Jul 21 1994 14:42`	6
	Hi all Thanks for the responses. It was a customer error. He had manually entered the remote 90TL in the community, hence it would not auto-undiscover . Regards John