HP MSR series Command Reference Manual page 20

Field
CRC
frame
- overruns
aborts
ignored
- parity errors
Output (total): 1502 packets,
138924 bytes
- unicasts, 2 broadcasts, 406
multicasts, 0 pauses
Output (normal): - packets, - bytes
1094 unicasts, - broadcasts, -
multicasts, - pauses
output errors
- underruns
- buffer failures
aborts
deferred
Description
Total number of inbound frames that had a normal length, but
contained checksum errors.
Total number of inbound frames that contained checksum errors and a
non-integer number of bytes.
Number of packets dropped because the input rate of the port
exceeded the queuing capability.
Total number of illegal inbound packets:
•
Fragment frames—CRC error frames shorter than 64 bytes. The
length can be an integer or non-integer value.
•
Jabber frames—CRC error frames greater than the maximum frame
length supported on the Ethernet interface (with an integer or
non-integer length). For an Ethernet interface that does not permit
jumbo frames, jabber frames refer to CRC error frames greater than
1518 bytes (without VLAN tags) or 1522 bytes (with VLAN tags). For
an Ethernet interface that permits jumbo frames, jabber frames refer
to CRC error frames greater than the maximum size of Ethernet
frames that are allowed to pass through the interface (which is
configured when you configure jumbo frame support on the
interface).
•
Symbol error frames—Frames that contained at least one
undefined symbol.
•
Unknown operation code frames—Non-pause MAC control
frames.
•
Length error frames—Frames whose 802.3 length fields did not
accord with the actual frame length (46 to 1500 bytes).
Number of inbound frames dropped because the receive buffer of the
port ran low.
Total number of frames with parity errors.
Outbound traffic statistics (in packets and bytes) for the port. All
outbound normal and abnormal packets (including unicast, broadcast,
and multicast), and pause frames were counted.
Outbound normal traffic (including unicast, broadcast, and multicast)
and pause frame statistics (in packets and bytes) for the interface.
Outbound packets with errors.
Number of packets dropped because the output rate of the interface
exceeded the output queuing capability. This is a low-probability
hardware anomaly.
Number of packets dropped because the transmit buffer of the
interface ran low.
Number of packets that failed to be transmitted, for example, because
of Ethernet collisions.
Number of frames that the interface deferred to transmit because of
detected collisions.
11