HP 3600 v2 Series Command Reference Manual page 19

Field
aborts
ignored
- parity errors
Output (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0
multicasts, 0 pauses
Output (normal): 0 packets, - bytes
0 unicasts, 0 broadcasts, 0
multicasts, 0 pauses
output errors
- underruns
- buffer failures
aborts
deferred
collisions
late collisions
lost carrier
- no carrier
Description
Total number of illegal inbound packets:
•
Fragment frames—CRC error frames shorter than 64 bytes. The
length can be an integral or non-integral value.
•
Jabber frames—CRC error frames greater than the maximum frame
length supported on the Ethernet interface (with an integral or
non-integral 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 length 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 packet drops 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.
Number of frames that the interface stopped transmitting because
Ethernet collisions were detected during transmission.
Number of frames that the interface deferred to transmit after
transmitting their first 512 bits, because of detected collisions.
Number of carrier losses during transmission. This counter applies to
serial WAN interfaces.
Number of times that the port failed to detect the carrier when attempting
to send frames. This counter applies to serial WAN interfaces.
11