HP 6125G HP 6125G & 6125G/XG Blade Switches Layer 2 - LAN Switching Co - Page 17

Field giants - throttles frame - overruns 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 Description Inbound frames larger than the maximum frame length supported on the interface. • For an Ethernet interface that does not permit jumbo frames, giants refer to frames larger than 1536 bytes (without VLAN tags) or 1540 bytes (with VLAN tags). • For an Ethernet interface that permits jumbo frames, giants refer to frames larger than the maximum length of Ethernet frames that are allowed to pass through, which is configured when you configure jumbo frame support on the interface. Number of times that the port shut down due to buffer or CPU overload. Total number of inbound frames that contained checksum errors and a non-integer number of bytes. Number of packet drops 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 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. 9