[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

1488.0. "900 and 90 agent configuration" by MSDOA::LOVE (Do it with DNA) Tue Sep 27 1994 23:56

After a search on AGENT in this conferance, I discovered my understanding
of how HUBwatch works is limited. My customer has four floors with a DEChub 90
pair in the IPD closet on each floor.  Each pair has a Bridge 90 connecting
them to the computer room via thickwire hose.  What the costomer is proposing
is to replace the thickwire with DEChub 900 connected via fiber in a star
type of connection.  The computer rooms DEChub 900 is the center with a
90L repeater connected to the IPD rooms DEChub 900 to a Bridge 90FL.  Each
IPD room DEChub 900 will have a Repeater 90C to connect to the existing
DEChub 90s Bridge 90.  The customer will need at least one DECagent 90 to
manage all of the repeaters in the four DEChub 90 pairs, the four Bridge 90s
and the four Bridge 90FLs with HUBwatch windows?  The four 90Cs in the four
IPD hubs and the 90L in the computer room should be managed by the "MAM" in
the 900s via HUBwatch Windows?

Norm

T.R	Title	User	Personal Name	Date	Lines
1488.1	All the pieces are there	ROGER::GAUDET	Because the Earth is 2/3 water	`Wed Sep 28 1994 10:24`	26
	Norm, I presume that the "90L repeater" you refer to is really a DECrepeater 90FL, correct? Just making sure I understand the configuration. I'll take your questions one by one: >> The customer will need at least one DECagent 90 to manage all of the >> repeaters in the four DEChub 90 pairs, the four Bridge 90s and the four >> Bridge 90FLs with HUBwatch windows? One DECagent 90 will suffice. It should reside in one of the DEChub 90s (although it could be standalone on the LAN if you prefer). From HUBwatch you will need to configure the DECagent with the four DEChub 90 communities (three of them if you install the DECagent in one of those hubs). Also add each DECbridge 90FL to the DECagent as a standalone community. Then add each DECbridge 90FL to the HUBwatch agents table, specifying the DECagent's IP address, the DECbridge 90FL's MAC address and the standalone community string you specified when you added it to the DECagent. >> The four 90Cs in the four IPD hubs and the 90L in the computer room should be >> managed by the "MAM" in the 900s via HUBwatch Windows? This is correct. ...Roger...
1488.2	What do you mean - Standalone.	MSDOA::LOVE	Do it with DNA	`Wed Sep 28 1994 21:50`	5
	Thanks for the quick response. Yes, I meant 90FL. What do you mean by stand alone on the LAN. Does that mean it can not be in one of the HUB 900's? Perhaps the TOP HUB which does not contain a Bridge. Norm
1488.3	Standalone = on the ThinWire	ROGER::GAUDET	Because the Earth is 2/3 water	`Thu Sep 29 1994 09:52`	10
	By standalone on the LAN, I mean that you can connect a standalone power supply (H7827-AA) to the DECagent and connect a ThinWire connection to the BNC connector on the top of the module (following proper termination rules, etc.). Then you can manage the DEChub 90s through their respective DECbridge 90. You can place the DECagent in one of the DEChub 900s if you wish. Remember, though, that it will not manage the repeaters in that hub unless you deny the hub manager an IP address so the DECagent can be the hub master. ...Roger...
1488.4		NETCAD::SLAWRENCE		`Mon Oct 03 1994 16:31`	8
	Putting the DECagent in the 900 that is the backbone connecting your 90 hubs would have the advantage that if you have a failure in one 90 hub you'll still be able to reach the others. Similarly, you probably want your NMS to be connected as centrally as possible.