[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

1145.0. "standalone brouter management..." by ODIXIE::RICHARDSON (Are we there yet??) Wed Jun 22 1994 15:29

    I understand that an agent is not needed in order to manage a
    DECbrouter.  However, this customer has HUBwatch for Windows and
    several other Hubs with terminal servers and bridges in them so they are
    familiar with the Hubwatch "screens".  I would like to manage the
    Brouters (obviously) but am concerned that it willbe very limited
    management without them in a hub backplane with an agent installed.
    
    Is this a correct assumption.  I'm sure the customer would like to see
    the "picture" of the brouter on their windows screen and not have to do
    management fromthe console port or even from a terminal prompt...
    
    Will I need the hub as well as the agent or will just the hub do and
    another agent can also handle this hub (one agent can manage up to 4
    separate hubs?)?  Or - do I even need the hub?  Can I see a "picture"
    of the brouter from Hubwatch for windows using only the standalone
    version of the brouter?
    
    Thanks
    
    Cindy
T.RTitleUserPersonal
Name		DateLines
1145.1Definitely standalone management.SLINK::HOODI'd rather be at the KennebecWed Jun 22 1994 15:4830
>> I would like to manage the
>>    Brouters (obviously) but am concerned that it willbe very limited
>>    management without them in a hub backplane with an agent installed.

HUBwatch manages the DECbrouter directly.  There is no other agent involved.
It doesn't matter if you're a standalone module or plugged into a hub.

>>    Is this a correct assumption.  I'm sure the customer would like to see
>>    the "picture" of the brouter on their windows screen and not have to do
>>    management fromthe console port or even from a terminal prompt...

Cisco provided very marginal SNMP management for the brouter (both ours and 
theirs).  You can monitor traffic and do simple (mostly MIB-II) things through
HUBwatch (or any SNMP manager), but to do any real configuration, you must talk
to the brouter through the brouter console.  By pressing a button in the
HUBwatch brouter summary screen, you can launch a terminal window which
automatically sets up a TELNET connection to the brouter.  You can type Cisco
brouter console commands to it.

>>    Will I need the hub as well as the agent or will just the hub do and
>>    another agent can also handle this hub (one agent can manage up to 4
>>    separate hubs?)?  Or - do I even need the hub?  Can I see a "picture"
>>    of the brouter from Hubwatch for windows using only the standalone
>>    version of the brouter?
 
It doesn't matter.  Neither the DENMA nor the 900 hub manager are involved
in managing the DECbrouter 90's.  

Tom Hood
HUBwatch