Alert Types - HP ProCurve Series 4100GL Management And Configuration Manual

Using the HP Web Browser Interface
Status Reporting Features
Table 5-1. Alert Strings and Descriptions
Alert String
First Time Install
Too many undersized/
giant packets
Excessive jabbering
Excessive CRC/alignment
errors
Excessive late collisions
High collision or drop rate A large number of collisions or packet drops have occurred on the port. Possible causes
Excessive broadcasts
Loss of Link
Loss of stack member
5-20

Alert Types

The following table lists the types of alerts that can be generated.
Alert Description
Important installation information for your switch.
A device connected to this port is transmitting packets shorter than 64 bytes or longer than
1518 bytes (longer than 1522 bytes if tagged), with valid CRCs (unlike runts, which have invalid
CRCs).
A device connected to this port is incessantly transmitting packets ("jabbering"), detected as
oversized packets with CRC errors.
A high percentage of data errors has been detected on this port. Possible causes include:
• Faulty cabling or invalid topology.
• Duplex mismatch (full-duplex configured on one end of the link, half-duplex configured on
the other)
• A malfunctioning NIC, NIC driver, or transceiver
Late collisions (collisions detected after transmitting 64 bytes) have been detected on this
port. Possible causes include:
• An overextended LAN topology
• Duplex mismatch (full-duplex configured on one end of the link, half-duplex configured on
the other)
• A misconfigured or faulty device connected to the port
include:
• A extremely high level of traffic on the port
• Duplex mismatch
• A misconfigured or malfunctioning NIC or transceiver on a device connected to this port
• A topology loop in the network
An extremely high percentage of broadcasts was received on this port. This degrades the
performance of all devices connected to the port. Possible causes include:
• A network topology loop—this is the usual cause
• A malfunctioning device, NIC, NIC driver, or software package
Lost connection to one or multiple devices on the port.
The Commander has lost the connection to a stack member.