| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| 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 |
If I have a configuration with remote sites having DECbrouter 90's,
DECserver 90TL's and DECrepeater 90T's, do I need an agent in here to
manage all these, or does the DECbrouter 90 handle the management of
the repeaters? I plan on proposing HUBwatch for Windows...
With new versions of firmware coming out as well as the new modules,
it's getting very difficult to keep up with this. Exactly when do I
need an agent anymore?
Thanks....
Cindy
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 911.1 | DECrepeater 90T's need a DECagent 90 | SLINK::HOOD | I'd rather be surfing | Wed Apr 20 1994 11:21 | 21 |
You need an agent for the DECrepeater 90T's. In either a DEChub 90 or DEChub 900, you need a DECagent 90 to manage: - DECbridge 90 - DECbridge 90FL - DECserver 90L - DECserver 90L+ - DECrepeater 90C - DECrepeater 90T (and a few other old repeaters) The above list of devices do not speak SNMP. Anything designed in the past year or so doesn't need a DECagent 90, UNLESS you've got a DEChub 90 and want to manage the *hub* as an entity. So, you could have a DEChub 90 with DECserver 90M, DECbrouter 90, and the new 90 repeaters without a DECagent 90. You would be able to manage each module as a standalone module (ie: WATCH/AGENT <termserv-ip>), but would not be able to see the hub configuration without the DECagent 90. Tom Hood HUBwatch | |||||
| 911.2 | minor correction | QUIVER::HAROKOPUS | Wed Apr 20 1994 15:38 | 7 | |
> - DECrepeater 90C
> - DECrepeater 90T (and a few other old repeaters)
In a 900 hub you do not need a DENMA to manage any repeaters.
The MAM acts as the agent for the old 90 repeaters.
-Bob
| |||||