T.R | Title | User | Personal Name | Date | Lines |
---|
888.1 | Already supported in V2.0 | QUIVER::HAROKOPUS | | Thu Apr 07 1994 12:45 | 8 |
| You can manage the DECbrouter 90 with HUBwatch V2.0.
However, the Brouters SNMP support is limited. Most of the
heavy duty configuration needs to be done from the console.
HUBwatch provides a telnet window so you can invoke the console
from the management station
-Bob
|
888.2 | DECbrouter 90's and Cisco IGS | SLINK::HOOD | I'd rather be surfing | Thu Apr 07 1994 14:02 | 2 |
| The same screens that can be used for the DECbrouter 90's can also be used
for the Cisco IGS (HUBwatch for Windows V2.0, OpenVMS V3.0).
|
888.3 | decbrouter managed by ciscoworks? | NWD002::KOPEC_ST | Squash:Racketball::Chess:Checkers | Thu Sep 01 1994 16:09 | 5 |
| For customers who already own Ciscoworks (in this case it is running
on SUNNET MGR), are there any limitations in managing the DECbrouter 90
this way, as opposed to via Hubwatch?
Thx, Stan
|
888.4 | CiscoWorks is the way to go. | SLINK::HOOD | I'd rather be at the Penobscot | Thu Sep 01 1994 16:46 | 8 |
| CiscoWorks is an ideal platform to manage DECbrouter 90's, assuming
it supports the DECbrouter 90's. As near as I can tell, CiscoWorks uses
TELNET to setup and control the brouters. It gives far more control and
status than you can get through HUBwatch (or any SNMP manager) because the
brouters' support for SNMP is pretty limited.
Tom Hood
HUBwatch.
|
888.5 | DECbrouter agent & Monitoring | CUJO::HILL | Dan Hill-NetConsultant-Denver-553-3624 | Fri Sep 02 1994 15:21 | 7 |
| What statistics and counters can be monitored using the agent on the
DECbrouter 90?
Can someone give me a pointer to documentation for this?
Thanks,
Dan
|
888.6 | Extracted from SYS$HELP:HUBWATCH.DECW$BOOK | SLINK::HOOD | I'd rather be at the Penobscot | Tue Sep 06 1994 19:47 | 47 |
| Table 2-14: Brouter Information Box Counters
Name Meaning
Module Uptime The time since the brouter was last initialized
Free Buffers The number of free buffer elements
Buffer Misses The number of buffer element misses
Buffer Hits The number of buffer element hits
Free Memory The amount of free memory in bytes
% CPU busy The 5-minute average of the CPU busy percentage
Table 2-15: Total Interface Error Counters
Name Meaning
Total Input Errors The sum of input errors for all ports on the brouter
Total Output Errors The sum of output errors for all ports on the brouter
Table 2-16: SNMP Counters
Name Meaning
Total Inbound Pkts The number of SNMP packets received by the brouter
Total Outbound Pkts The number of SNMP packets sent by the brouter
GET requests received The number of SNMP Get-Request PDUs that have been
accepted and processed by the brouter SNMP agent
GET NEXT requests The number of SNMP Get-Next PDUs that have been
received accepted and processed by the brouter SNMP agent.
SET requests received The number of SNMP Set-Request PDUs that have been
accepted and processed by the brouter SNMP agent
Traps Sent The number of SNMP Trap PDUs generated by the brouter
Total Inbound Errors The number of SNMP packets that contained errors that
prevented further processing
Total Outbound Errors The number of SNMP packets that could not be
transmitted because of errors
Table 2-13: Brouter Port Information Displayed
Window Information
Summary Port state, port name, port status,
and performance data
Port Summary Port state, port name, port status,
performance data, and protocol traffic
|
888.7 | Thanks! | CUJO::HILL | Dan Hill-NetConsultant-Denver-553-3624 | Wed Sep 07 1994 11:40 | 1 |
|
|