| 1. No Agent or HUBwatch, only DECmcc
The DECserver 90L, L+ and the DECbridge 90 are both manageable with
MOP/CC, and the DECrepeater 90s are manageable via the DECbridge 90
using MOP/CC.
The DECserver 90L, L+, and TL are all manageable using TSM or TSAM.
(I think the latest TSAM handles the L+). The TL supports MIB II
and the Character and RS232 groups using the SNMP AM.
The DECwanrouter 90 is manageable with NCL, and it supports MIB II
GETs using the SNMP AM.
The DECbridge 90 is manageable using the DECmcc ELAM, but you still
have to MOP to the bridge to manage the repeaters.
2. DECagent 90, but no HUBwatch
Adding the DECagent 90 would allow you to use the SNMP AM to manage
the DECserver 90L, L+, DECbridge 90, and DECrepeater 90s. It also
makes the hub configuration information kept in the bridge accessible
via SNMP. With a DECagent 90 on each LAN, you no longer need DECmcc
there, since SNMP runs over IP routers. MOP/CC, which TSM uses, and
RBMS, which the ELAM uses, are not routable. The DECagent 90 also
provides an out-of-band rs232 port, so you can do some management
with a terminal if your network goes down.
3. HUBwatch and DECagent 90
HUBwatch only makes all the management much more graphical and
intuitive. Most people, who've seen it, think it's well worth the
money. It also gives you the ability to manage the DEChub family
without buying the "cadillac", if you don't want the cadillac.
|