[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

137.0. "HOW many DEcAgents on network" by WEORFI::RICKETTS () Thu Jan 28 1993 15:45

    How many DECagent90 will I need in a network will muliple DEChubs
    filled with DECrepeaters 90t and DECRepeaters FL.
    We are planning to propose a DECMCC solution on a VMS platform.Th
    The way I read it the DERcagent can only manage up to 120 UTP ports.
    The network that is planned has excess of 500 ports, combination of
    Fiber and 10baseT.
     All help is appreciated

T.R	Title	User	Personal Name	Date	Lines
137.1	Rule of thumb - 1 agent per 4 hubs	MEMIT::FORREST		`Fri Jan 29 1993 14:47`	24
	One DECagent 90 should support up to 4 daisy-chained hubs full of repeaters, so that's 480 10BT ports per DECagent 90. The number 4 is our rule of thumb - to ensure acceptable performance. This does not translate to 8 single hubs, since there would now be 8 bridges instead of 4. The 4 extra bridges put on extra load that would degrade performance. The number of terminal servers in those hubs also affects performance. So the number of hubs per agent is configuration dependent. The proximity of the agent to the devices it is managing is also a factor, since the agent regularly polls each device that it knows about. The faster it can send RBMS to a DECbridge 90 or MOP to a DECserver 90L and get a response, the faster it can return the SNMP response, and the faster it can process the next request in the input queue. (We also have a queue to wait for responses from the bridge or terminal server). We've also tried to allow some margin for multiple management stations making requests and bridges or terminal servers not responding. There are just too many variables to come up with hard no-margin rules for the number of devices supported by 1 agent. You will need V1.1 of the DECagent to support the fiber stuff. We hope to release it sometime this quarter. jack
137.2	More on the 1 agent per 4 hubs rule	MEMIT::FORREST		`Fri Jan 29 1993 14:52`	8
	Oh yeah, The 1 per 4 rule assumes the 4 devices aren't separated from the agent by remote bridges connected by slow links and of course no routers in the path blocking MOP or RBMS. The agent should be able to handle many more than 4 standalone bridges or terminal servers.
137.3	Theoretically 62 stand alone servers	EMDS::SEAVER	LENAC Net Mgnt Mktg 223-4573	`Fri Jan 29 1993 18:00`	6
	The theoretical limit to the agent is it can handle 63 stand alone devices. The agent counts as one so the number goes down to 62 bridges or terminal servers (can't handle repeaters stand alone). Our guess is the actual limit is somewhat below this due to traffic considerations. I would like to hear what experience people have had with managing multiple terminal servers stand alone.
137.4	Practical limit??	CGOS01::DMARLOWE	dsk dsk dsk (tsk tsk tsk)	`Mon Feb 01 1993 10:37`	5
	But how does this relate to other comments about the DECagent locking up when too many communities have been added? I think one person had 6 communities and the agent quit. dave
137.5	I hope bug gets resloved.	EMDS::SEAVER	Bill Seaver, HUBwatch Mktg	`Thu Feb 04 1993 14:09`	3
	the 6 communities is a bug. I am talking about the design limiet as the usual corporate type how is not grounded in reality and also as someone who hopes we can get this bug resolved.