See if this helps any.
-----------------------------Ethernet STATISTICS-----------------------------
EthStatisticsGRP OBJECT IDENTIFIER ::= {atmelSys 7}
--OID: 1.3.6.1.4.1.410.1.1.7.1
EthRxStatistics OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (64))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Ethernet Rx Statistics
EthernetRxStatistics{
unsigned long TotalBytesRx;
unsigned long TotalPacketsRx;
unsigned long PacketCRCErrorRx;
unsigned long MulticastPacketRx;
unsigned long BroadcastPacketRx;
unsigned long ControlFramesRx;
unsigned long PauseFramesRx;
unsigned long UnknownOPCodeRx;
unsigned long AlignmentRxError;
unsigned long LengthOutOfRangeRx;
unsigned long CodeErrorRx;
unsigned long FalseCarrierRx;
unsigned long UndersizePacketsRx;
unsigned long OversizePacketsRx;
unsigned long TotalFragmentsRx;
unsigned long TotalJabberRx;
}"
::= {EthStatisticsGRP 1 }
-- TotalBytesRx(4) = Total bytes received including frame data.
-- TotalPacketsRx(4) = Total data packets received.
-- PacketCRCErrorRx(4) = Total frames received that had errors. Indicates
-- interference or faulty NIC.
-- MulticastPacketRx(4) = The number of well-formed multicast frames received.
-- BroadcastPacketRx(4) = The number of well-formed broadcast frames received.
-- ControlFramesRx(4) = The number of control frames, including pause and
-- unsupported frames.
-- PauseFramesRx(4) = Indicates that the device connected to the ether-
-- net port has become saturated and requested the
-- radio to stop sending frames for a moment.
-- UnknownOPCodeRx(4) = The number of unsupported control frames received.
-- AlinmentRxError(4) = The number of frames detected that contain
-- partial bytes and did not pass the CRC check.
--LengthOutOfRangeRx(4) = Number of frames received where the 802.3 length
-- field in the packet did not match the number of
-- bytes actually received.
-- CodeErrorRx(4) = Number of packets with bit codeing errors. See
-- a description of Manchester Encodeing or similar
-- for more details.
-- FalseCarrierRx(4) = Number of times that a packet preamble was received
-- and not followed by a data. Only used for
-- 100BaseTX and should remain 0.
--UndersizePacketsRx(4) = A frame less than 64 bits long was received. This
-- Usually is caused by collisions. If collisions are
-- low then it indicates faulty software or hardware in
-- the device attached to the Ethernet port.
-- OversizePacketsRx(4) = A frame more than 1518 was received. Usually
-- caused by a collision but could also mean that the
-- device connected to the Ethernet port is trying to
-- send a special frame, such as VLAN tagging, that is
-- not recognized by the APP.
-- TotalFragmentsRx(4) = The total number of packets that were larger than
-- allowed and were broken in to smaller packets before
-- being received.
-- TotalJabberRx(4) = Jabber is an error condition caused when the device
-- connected to the ethernet port continually transmits
-- random, meaningless data or a packet that exceeds
-- the maximum packet size allowed by IEEE 802.3.
--OID: 1.3.6.1.4.1.410.1.1.7.2
EthTxStatistics OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (56))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Ethernet Tx Statistics
EthernetTxStatistics{
unsigned long TotalBytesTx;
unsigned long TotalPacketsTx;
unsigned long PacketCRCErrorTx;
unsigned long MulticastPacketTx;
unsigned long BroadcastPacketTx;
unsigned long UnicastPacketTx;
unsigned long PauseFramesTx;
unsigned long SingleDeferPacketTx;
unsigned long MultiDeferPacketsTx;
unsigned long SingleCollisionsTx;
unsigned long MultiCollisionsTx;
unsigned long LateCollisionsTx;
unsigned long ExcessiveCollisionTx;
unsigned long TotalCollisionsTx;
}"
::= {EthStatisticsGRP 2 }
-- TotalBytesTx(4) = Total bytes transmitted including frame data.
-- TotalPacketsTx(4) = Total number of packets transmitted.
-- PacketCRCErrorTx(4) = Total number of packets that were reported as
-- having a bad check sum.
-- MulticastPacketTx(4) = The number of packets sent to multiple specific
-- addresses.
-- BroadcastPacketTx(4) = The number of packets sent to the broadcast
-- addresses.
-- UnicastPacketTx(4) = The number of packets sent to a single address.
-- PauseFramesTx(4) = The number of times that the AP has become
-- saturated and requested the device attached to the
-- ethernet port to delay transmission.
-- SingleDeferPacketTx(4) = The number of times a packet was defered from
-- transmitting one time before completion due to
-- busy medium. Does not included pacets involved in
-- collisions.
-- MultiDeferPacketTx(4) = The number of times a packet was defered from
-- transmitting multiple times before completion due
-- to busy medium. Does not include packets involved
-- in collisions.
-- SingleCollisionsTx(4) = The number of packets that had one collision
-- before successful transmision.
-- MultiCollisionsTx(4) = The number of packets that had between two and
-- fifteen collisions before successful transmission
-- LateCollisionsTx(4) = A late collision should never happen and indicates
-- to large of a network diameter. Check segment
-- cable lengths and total Ethernet network diameter.
--ExcessiveCollisionTx(4) = More than 16 collisions occurred in a row for the
-- same packet and it was dropped.
-- TotalCollision(4) = Total number of collisions including multiples.
--Detecting faulty adapters or ports:
--If OversizePacketsRX or TotalJabberRX (packets that are too long and
--misaligned) occur consistently on a port, the connected node may have a
--faulty adapter or port.
--If the adapter works properly in other computers, there are other possible
--causes you can check:
--Is the cable connecting the node too long? UTP cable can’t exceed 100
--meters and must be CAT 5 when running at 100 Mbps.
--Is there a duplex mismatch with the switch? If a switch port is set to full
--duplex and connected to a node set to half duplex, or vice versa, you could
--see problems.
--Detecting bad or poor quality cable:
--If a high percentage of PacketCRCErrorRx or PacketCRCErrorTx with respect
--to TotalPacketsRx or TotalPacketsTx, it could indicate poor quality cable
--or a noisy environment. Sweep test the cable with a cable tester or try a
--different cable.
--Detecting congested segments:
--If a high percentage of ExcessiveCollisionTx with respect to TotalPacketsTx
--occur, it could indicate a congested segment. Balance the traffic load by
--moving the destination devices to local segments
--Detecting speed mismatches:
--If a high amount of AlinmentRxError, UndersizePacketsRx, or
--OversizePacketsRx occur, it could indicate a speed mismatch. Check the
--speed of the port and all devices connected to that segment.
