[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

696.0. "Understanding hub management" by NWD002::MROTEK_MA () Sun Feb 06 1994 23:04

    I'm trying to understand how management is done with the DECagent,
    DECbridge, etc.
    
    Assumption #1
    
    DECagent manages terminal servers with the MOP protocol.  Thus the
    terminal server can be anywhere on the network (including standalone
    or in another hub from the DECagent; but not through a ROUTER) and the
    DECagent can manage it.
    
    Assumption #2
    
    DECagent manages bridges with RBMS protocol.  Thus the bridge can also
    be anywhere on the network (including standalone or in another hub from
    the DECagent; but not through a ROUTER) and the DECagent can manage it.
    
    Assumption #3
    
    The DECbridge (and DECagent v2.0) talks to repeaters through the
    serial management bus in the DEChub90.  Therefore, the repeaters MUST
    be in a DEChub with a DECbridge (or DECagent v2.0) in order for the 
    DECbridge to talk to it and send info to the DECagent.
    
    Questions:
    
    Are these assumptions correct?
    
    Can the DECagent manage even DECserver 200s, 300s and 700s?
    
    Did I miss anything?
    
    Thanks,
    Mary :)

T.R	Title	User	Personal Name	Date	Lines
696.1	Right so Far.	CGOS01::DMARLOWE	dsk dsk dsk (tsk tsk tsk)	`Mon Feb 07 1994 00:28`	26
	>> Assumption #1 Yes. Assumption #2 Yes. Its a RBMS subset I think. >> Assumption #3 Yes. >> Can the DECagent manage even DECserver 200s, 300s and 700s? The agent can only manage (and probably only understands) the DS 90L and L+. Don't foget how simple the 90L series is. Also the agent probably knows enough about the other 90 servers to identify them and thats it. dave
696.2		SLINK::HOOD	I'd rather be surfing	`Mon Feb 07 1994 11:13`	18
	>>> Can the DECagent manage even DECserver 200s, 300s and 700s? > > > The agent can only manage (and probably only understands) the DS > 90L and L+. Don't foget how simple the 90L series is. Also the > agent probably knows enough about the other 90 servers to identify > them and thats it. Right. It knows there's a 90TL or a 90M there. But it doesn't manage them. DS200, 300, 700 are not hub modules, so the agent never sees them. DECserver 90TL, 90M, 900TM have their own SNMP agents, and are only managed directly. You can't use the DECagent to manage them (other than knowing they're in a hub). Tom Hood HUBwatch