[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

312.0. "standalone DECbridge management?" by MLN08::MALACRIDA () Fri Jul 23 1993 09:05

    I'm quite new to this stuff so ...
    
    What do I need to graphically manage a standalone DECbridge 90FL
    connected to a standalone DECrepeater 90FA?
    Is at least 1 DECagent 90 needed somewhere on the LAN?
    
    Thanks,
    
    giovanni

T.R Title User Personal
Name Date Lines

312.1 standalone DECbridge and DECserver 90L+'s manageable using DECagent 90 NAC::FORREST Mon Jul 26 1993 21:46 10

T.R	Title	User	Personal Name	Date	Lines
312.1	standalone DECbridge and DECserver 90L+'s manageable using DECagent 90	NAC::FORREST		`Mon Jul 26 1993 21:46`	10
	Standalone DECrepeater 90Cs, 90Ts, 90FLs, and 90FAs are not manageable in any way, other than looking at the LEDs. The DECbridge 90FL is graphically manageable, if you have a DECagent 90 on the same LAN. Basically "on the same LAN" means that the RBMS protocol has to get through, and the delay from the DECagent to the DECbridge has to be small - i.e. no lower speed WAN links.

	Standalone DECrepeater 90Cs, 90Ts, 90FLs, and 90FAs are not 
	manageable in any way, other than looking at the LEDs.

	The DECbridge 90FL is graphically manageable, if you have a DECagent 
	90 on the same LAN. Basically "on the same LAN" means that the 
	RBMS protocol has to get through, and the delay from the DECagent 
	to the DECbridge has to be small - i.e. no lower speed WAN links.