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 |
In these days of SNMP management, there are many other software packages that allow a network manager to observe, graph, monitor and alarm on various MIB variables and combinations thereof. The problem is that no one really documents the important MIB variables to help inform network managers as to just which ones might help them detect or analyze problems. This sort of this requires specific device knowledge and must be found by trail an error, unless it is documented vendor by vendor specifically. Can anyone tell us if such MIB variables are discussed anywhere in the DEChub documentation or documentation specific to any of the DEChub components (i.e. bridges, repeaters, terminal servers, etc.). I've raised this point in open discussions outside of Digital and it appears to be a common problem in the industry. Thanks, Al
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2128.1 | HUBwatch Help is getting more and more of that | SLINK::HOOD | This is my new personal name for Notes | Tue Mar 21 1995 13:48 | 9 |
One source of documentation on MIB variables is the HUBwatch Help, especially for the newer devices. I've noticed the writers have been adding more info around counters, saying things like "If this variable gets to be high, it means you've potentially got such-and-such a problem in your network" It's probably not quite enough, but they are doing some nice work there. Tom Hood HUBwatch | |||||
2128.2 | Thanks, | NAC::LICAUSE | Wed Mar 22 1995 07:45 | 6 | |
Thanks Tom, I'll take a look. Sounds like just what we need. Al |