| Robert-
The basic philosophy for items in clause 30 was NOT to have a complete set for SNMP. Rather, it was to define the BASIC measurements from which gauges, meters, notification and alarms could be derived. That's one reason for the mismatch. The other is that cl. 30 hasn't been kept up to date because (in theory) it wasn't needed any more because Std 802.3.1 was being written in the 802.3 WG.
Geoff Thompson (Original clause editor for cl. 30)
Hi,
Quite a lot of useful Ethernet statistics (which seem to be
widely implemented, at least on our platforms) are defined in the
RMON MIB, rfc2819: I would like to consolidate these statistics with the ones
defined by the Etherlike MIB as part of the basic Ethernet
interface definition. However, there are not Clause 30 objects
for the counters below. How can this be resolved? Can we need to
define new clause 30 objects for these counters? Or do these
counters need to be standardized elsewhere (e.g. IETF)?
EtherStatsEntry ::= SEQUENCE {
etherStatsIndex Integer32,
etherStatsDataSource OBJECT IDENTIFIER,
etherStatsDropEvents Counter32,
etherStatsOctets Counter32,
etherStatsPkts Counter32,
etherStatsBroadcastPkts Counter32,
etherStatsMulticastPkts Counter32,
etherStatsCRCAlignErrors Counter32,
etherStatsUndersizePkts Counter32,
etherStatsOversizePkts Counter32,
etherStatsFragments Counter32,
etherStatsJabbers Counter32,
etherStatsCollisions Counter32,
etherStatsPkts64Octets Counter32,
etherStatsPkts65to127Octets Counter32,
etherStatsPkts128to255Octets Counter32,
etherStatsPkts256to511Octets Counter32,
etherStatsPkts512to1023Octets Counter32,
etherStatsPkts1024to1518Octets Counter32,
etherStatsOwner OwnerString,
etherStatsStatus EntryStatus
Thanks,
Rob
|