PROM address:
00A026700000
Speed:
10 Mbps
Input statistics:
failed, frame too long
0
failed, FCS error
1
failed, alignment error
0
failed, FIFO overrun
1
internal MAC rcv error
1
packets missed
1
Output statistics:
deferred transmission
0
single collision
0
multiple collisions
0
total collisions
0
failed, excess collisions
0
failed, FIFO underrun
0
failed, carrier sense err
0
SQE test error
0
late collision
0
internal MAC trans errors
0
Ethernet MAC code release 1
+
The meaning of each field is as follows:
Interface
Interface name.
CSR
Control/status and physical interface data register address.
Vect
Interrupt vector associated to the interface, written in hexadecimal format.
Auto-test valids
Number of successful auto-tests.
Auto-test failures
Number of unsuccessful auto-tests.
Maintenance failures
Number of maintenance failures.
Physical address
MAC address used in the Ethernet interface in canonical format.
PROM address
MAC address for the Ethernet interface provided by the manufacturer.
Speed
Speed (in Mbps) at which the Ethernet interface operates. It can range from 10 to
100.
Input statistics:
failed, frame too long
The interface received a frame exceeding the maximum size of 1,518 bytes for an
Ethernet frame. This data is exported via SNMP as the dot3StatsFrameTooLongs
counter.
failed, FCS error
The interface received a packet with a CRC error. This data is exported via SNMP
as the dot3StatsFCSErrors counter.
failed, alignment error
The interface received a frame whose size in bits is not a multiple of eight.
failed, FIFO overrun
The Ethernet chipset is unable to store bytes in the local packet buffer as fast as
they come off the cable.
packets missed
The interface tries to receive a packet but the local packet buffer is full. This indic-
ates that traffic in the network surpasses what the interface can handle.
internal MAC rcv error
Received errors not due to excessive collisions or to carrier detection. This data is
exported via SNMP as the dot3StatsInternalMacReceiveErrors counter.
Output statistics:
deferred transmission
The carrier detection mechanism detects activity on the line that causes the inter-
face to defer transmission. This data is exported via SNMP as the
dot3StatsDeferredTransmission counter.
single collision
Increases when a frame collides on the first transmission attempt but is then suc-
cessfully sent on the second. This data is exported via SNMP as the
dot3StatsSingleCollisionFrames counter.
multiple collisions
Increases when a frame has multiple collisions before being successfully transmit-
ted. This data is exported via SNMP as the dot3StatsMultipleCollisionFrames
counter.
total collisions
Total number of collisions.
failed, excess collisions
Increases when a frame transmission fails due to 16 or more successive colli-
sions. This error indicates a high volume of network traffic or hardware problems
with the network. This data is exported via SNMP as the
dot3StatsExcessiveCollisions counter.
failed, FIFO underrun
Increases when packet transmission fails due to the inability of the interface to re-
trieve packets from the local packet buffer fast enough to transmit them onto the
network.
failed, carrier sense err
Increases when a frame collides because the carrier detector is disabled. This er-
ror indicates a problem between the interface and its Ethernet transceiver. This
data is exported via SNMP as the dot3StatsCarrierSenseErrors counter.
4 Monitoring Ethernet Interfaces
Teldat SA
28
LAN Interfaces
