| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 273.1 | brouter and TL have their own agents | NAC::SEAVER | Bill Seaver, HUBwatch Mktg | Mon Jul 05 1993 18:40 | 10 |
| The agent will not "see" either the TL or the brouter. They both have
integral SNMP agents and thus do not need (or sue the agent to talke
SNMP). HUBwatch (VMS2.0- September) will manage the brouter. Current
version of VMS will manage the TL. Windows 1.1 (September) will manage
both the brouter and the Tl thru raw SNMP, in fact V1.0 (out now) will
manage both as stand alone devices.
AS far as seeing the repeaters, did you have a bridge in the hub or
were you doing this thru the brouter? Thisis important to me because I
was told this was not supported in this release of the brouter.
|
| 273.2 | DECagent 90 V1.1 manages through DECbridges only | QUIVER::GAUDET | | Tue Jul 06 1993 13:13 | 18 |
| Ralph,
DECagent 90 (V1.1) will not manage the hub through a DECbrouter 90.
V1.1 supports auto-discovery and repeater management through the
DECbridges (90 and 90FL) only.
Since the DECbrouter 90 is not supported as the hub master, you should
not see any other modules in the hub other than the DECagent 90
(neither from HUBwatch nor from the agent console). However, if you
add a DECbridge to the hub and tell the agent about it (type, slot
number, MAC address), all the modules (including the repeaters,
DECbrouter and DECserver 90TL) should be discovered by the DECagent.
Note that if your DECserver 90TL is the 1-Meg version, it will
disappear from the hub unless you add it from HUBwatch with polling
disabled.
Roger Gaudet
DECagent 90 devo.
|
| 273.3 | HUBwatch and Brouter management | HGOV08::GUPTA | | Thu Aug 12 1993 00:31 | 19 |
| Ref .1:
Hi Bill,
What do you mean when you say "..in fact V1.0 will manage both as
STANDALONE devices" ? You mean Brouter, in order to be manageable by
HUBwatch, should be outside the DEChub ?
I have proposed to a customer three brouters in one DEChub (config
shown in note 321.0). Will HUBwatch manage these brouters ? If not,
which version of HUBwatch will have support for these multiple brouters
in one DEChub ?
I will appreciate if you can give me a pointer to some document which
describes the manageability aspects of DECbrouter 90.
Regards,
Surender
|
| 273.4 | the HUBwatch and DECbrouter story | NAC::FORREST | | Fri Aug 13 1993 14:06 | 27 |
|
> What do you mean when you say "..in fact V1.0 will manage both as
> STANDALONE devices" ? You mean Brouter, in order to be manageable by
> HUBwatch, should be outside the DEChub ?
HUBwatch for Windows V1.0 has no support for the DECbrouter 90;
however, since it includes a network map and generic SNMP support,
you can add the DECbrouter, or any other SNMP-manageable device,
to the network map as a generic device.
HUBwatch for Windows V1.1 will recognize all DEChub 90 modules
planned to ship through December 1993. You can do some management
with the MIB Browser - doesn't matter if it's in the hub or
standalone.
HUBwatch for ULTRIX or OpenVMS V1.1 does not support the DECbrouter.
HUBwatch for OpenVMS V2.0 in September will manage the DECbrouter
90 in the Hub or standalone.
> I will appreciate if you can give me a pointer to some document which
> describes the manageability aspects of DECbrouter 90.
The DECbrouter manuals are at
TIMBER::USER8:[FANTASIA.BROUTER$PUBLIC]*.PS
I think it is too complex to attempt to summarize here.
|