[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

853.0. "Managing Terminal Server with HUBwatch?" by HGRNCC::FARADAYCHONG (Faraday Chong@hgo 852-8053590) Wed Mar 23 1994 03:49

    Can someone summarize to what extent the HUBwatch for Windows can
    manage Terminal Servers in DEChub 90/900?
    
    E.g. Do we need Terminal Server Manager (TSM) in addition to HUBwatch,
    i.e. important management functions that are in and not in HUBwatch.
    
    Faraday
T.RTitleUserPersonal
Name
DateLines
853.1Terminal server management functions in HUBwatchSLINK::HOODI'd rather be surfingWed Mar 23 1994 10:3223
Everything you can manage in a terminal server through SNMP you can manage
through HUBwatch for (OpenVMS | Windows | OSF/1), (V2.0 | V3.0)

On the other hand, that means you cannot manage anything having to do with LAT.

With HUBwatch, you can:
	- Enable or Disable individual ports
	- Display session information per port.
	- Disconnect one or more sessions. (900TM/90TL/90M)
	- Enable or disable IP forwarding (900TM/90TL/90M)
	- Reset a port (900TM/90TL/90M)
	- Reset the server (90L/90L+)
	- Change the port characteristics (speed, flow control, etc)
	- Display the server's counters (LAT only available in 90L/90L+)
	- Determine if flow has been disabled on a port (ie: someone hit XOFF)
				(900TM/90TL/90M)
	- Display/modify other MIB-II info.

For the 900TM/90TL/90M, a system manager could also TELNET to the server and
do all the other setup as well, through a console session.

Tom Hood
HUBwatch
853.2What it can't do.CGOS01::DMARLOWEHave you been HUBbed lately?Wed Mar 23 1994 15:214
    HUBWATCH can't save the server setup to a config file or restore
    same.
    
    dave
853.3CRONIC::LEMONSAnd we thank you for your support.Mon Jun 26 1995 00:3711
    I'd like to re-activate this thred, with a few newbie questions of my
    own.
    
    It seems that I can't set characteristics in all ports at once via
    SNMP, but can do a SET|DEFINE|CHANGE PORT ALL xxx via TSM or the Telnet
    interface.  Also, it seems that, using SNMP/Hubwatch, I can set / view
    only a subset of the DECservers characteristics.  Is this true?  Any
    plans to chang it, if true?
    
    tl
    
853.4SLINK::HOODMaine State Bird: The black flyMon Jun 26 1995 10:4210
>    interface.  Also, it seems that, using SNMP/Hubwatch, I can set / view
>    only a subset of the DECservers characteristics.  Is this true?  Any
>    plans to chang it, if true?

True.  A lot of the control of DECservers is not available through SNMP.

For DECserver issues, you want to use the TOOK::TERMINAL_SERVERS notesfile.

Tom Hood
HUBwatch
853.5TOOK::D_NELSONDave Nelson LKG1-3/A11 226-5358Mon Jun 26 1995 16:5317
    RE: .0
    
    I observe that you raise questions in two basic categories: (1) not
    all DECserver variables are visible in HUBwatch, and (2) those that are
    visible cannot be operated on as groups, e.g. all ports.
    
    To fix problem (1) the DECserver first must implement additional MIBS,
    some of them proprietary, and then HUBwatch must do likewise.  To fix
    problem (2) I would advocate a layered application, that understands the
    nature of the DECserver variables.  This could be implemented within 
    HUBwatch itself, or it could be a launchable "TSM-like" configurator 
    application, that integrates with HUBwatch.
    
    Regards,
    
    Dave