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 |
HUBWATCH FOR WINDOWS 3.X LB200 MANAGEMENT What capabilities will there be in the Hubwatch for Windows product to manage the previous range of Digital LAN bridge products , eg. LB200 ? Will hubwatch only be capable of SNMP management only, meaning as above that the LB200 can only be SNMP managed ? If SNMP management only is the method of managing the LB200, can Hubwatch for Win. have the functionality to SET the address and protocol filters, or some equivalence to RBMS/ELMS ? Tony
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
75.1 | HUBwatch for Windows will partially manage a LANbridge 200 | MEMIT::FORREST | Fri Nov 13 1992 12:36 | 10 | |
HUBwatch for Windows only supports SNMP as a management protocol. In addition to full DECbridge 90 management, it supports the new IETF Bridge MIB. I believe the LANbridge 200 also supports this. So you can do at least partial management. You can manage Spanning Tree and some forwarding parameters, but not protocol or source address filtering. I think the authors (2 were from DEC) decided that filtering is too different among vendor implementations to standardize a filter group. |