R3204P16-HP Load Balancing Module Network Management Command Reference-6PW101

9
Field Descri
p
tion
CRC
Total number of inbound frames that had a normal length, but
contained checksum errors.
frame
Total number of inbound frames that contained checksum errors and a
non-integer number of bytes.
- overruns
Number of packet drops because the input rate of the port exceeded
the queuing capability.
aborts
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 (the frame length may or
may not be integers). 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).
ignored
Number of inbound frames dropped because the receive buffer of the
port ran low.
- parity errors Total number of frames with parity errors.
Output(total): 0 packets, 0 bytes
0 broadcasts, 0 multicasts, 0
pauses
Outbound traffic statistics (in packets and bytes) for the port. All
outbound normal and abnormal packets, and pause frames were
counted.
Output(normal): - packets, - bytes
- broadcasts, - multicasts, -
pauses
Outbound normal traffic and pause frame statistics (in packets and
bytes) for the interface.
output errors Outbound packets with errors.
- underruns
Number of packet drops because the output rate of the interface
exceeded the output queuing capability. This is a low-probability
hardware anomaly.
- buffer failures
Number of packets dropped because the transmit buffer of the
interface ran low.
aborts
Number of packets that failed to be transmitted, for example, because
of Ethernet collisions.
deferred
Number of frames that the interface deferred to transmit because of
detected collisions.
collisions
Number of frames that the interface stopped transmitting because
Ethernet collisions were detected during transmission.