| 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 the only devices in the DEChub 90 are DECserver 90M, is there a need
    for the DECagent 90 or can HUBwatch manage the 90M since it is SNMP
    capable already.
    
    Thanks.
    
    Frank
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 393.1 | Stand-alone DECserver 90M mgmt thru HUBwatch | SLINK::HOOD | I'd rather be surfing | Mon Sep 20 1993 13:51 | 19 | 
| > If the only devices in the DEChub 90 are DECserver 90M, is there a need > for the DECagent 90 No, not really. You will be able to completely manage your DECserver 90M's (or 90TL's) as standalone agents through HUBwatch without a DECagent 90. The only information HUBwatch will not be able to get without a DECagent 90 is the slot number of each DECserver. Otherwise, HUBwatch does not use the DECagent 90 at all when managing the 90M. (or 90TL or brouters) $ watch /agent /ip=<ip of decserver> On the other hand, I suspect we do make some amount of profit from each DECagent 90 that is sold... :-) Tom Hood HUBwatch | |||||