| The DECrepeater 90FL and DECrepeater 90FA products can not detect/count any
errors at the port level. They can report whether or not a port is
auto-partitioned and the auto-partition reason (e.g. excessive
collisions, jabber, etc.), but they cannot count things like crc
errors, short events, runts, etc., on a per port basis. The Basic
Groups of the IETF repeater MIB (RFC 1516) and Digital's extended repeater
MIB outline the DECrepeaters' 90FL/90FA capabilities.
The DECrepeater 90FS, on the other hand, can detect and count a wide
range of errors on a per-port basis. These are fully outlined in the
Monitor Group of the IETF repeater MIB. The DECrepeater 90FS's
Installation and Configuration Guide lists exactly which MIBs the
repeater supports.
Regards,
Rich
|
| For the record, the currently shipping version of the DECagent 90 uses
the "DECagent 90 and DEChub 90 Vendor MIB Document for SNMP V1
Implementation" to manage DECrepeaters 90FL, 90FA. Specifically, this
MIB's drpt90 Group outlines the repeaters' management capabilities.
The DEChub 900 Hub Manager uses the IETF repeater MIB (RFC 1516) and
"Digital Equipment Corporation's DEChub 900 Extensions to the
Definitions of Managed Objects for IEEE 802.3 Repeater Devices" to
manage DECrepeaters 90FL, 90FA. As stated in .1, the hub manager
supports the Basic Groups of both MIBs, and the IETF repeater MIB's
Address Tracking group on behalf of these repeaters.
The DECrepeater 90FS has its own embedded SNMP agent. This product
supports MIB II, Ethernet MIB, DEChub 900 Public Common MIB, IETF
repeater MIB, and Digital's repeater MIB extensions.
Regards,
Rich
|