Extreme 3804 Supplementary Manual
32
Advanced System Diagnostics and Troubleshooting Guide
Packet Errors and Packet Error Detection
Error Message Format
Error messages take the following form:
mm/dd/yyyy hh:mm.ss <level:from> Sys-health-check [TYPE] error condition on location
where:
level
The severity level, either CRIT or WARN. CRIT indicates a critical failure in the system that
requires corrective action. WARN indicates that the error is most likely an isolated checksum
occurrence and should not be considered a critical failure to the system.
requires corrective action. WARN indicates that the error is most likely an isolated checksum
occurrence and should not be considered a critical failure to the system.
from
TYPE
The type of test packet involved, possibly pointing to the packet origin and the diagnostic
subsystem involved. Supported packet type descriptors are: CPU, DIAG, EDP, EXT, and INT.
subsystem involved. Supported packet type descriptors are: CPU, DIAG, EDP, EXT, and INT.
•
CPU, DIAG, and EDP refer to packets generated within the CPU health-checking
subsystem of the switch.
subsystem of the switch.
CPU packet types include DIAG and EDP packets, as well as data packets destined for
the CPU.
the CPU.
DIAG packet types refer to the CPU diagnostics packets generated by the health-checking
subsystem.
subsystem.
EDP packet types refer to the backplane health-checks used to test the communication
paths between the CPU and the I/O blades.
paths between the CPU and the I/O blades.
•
EXT and INT packet types refer to a checksum that is appended to each and every packet
that enters (ingresses) and exits (egresses) the switch fabric MACs.
that enters (ingresses) and exits (egresses) the switch fabric MACs.
(Extreme switches pro-actively scan for fault conditions throughout the switch architecture, and
these packet types are all part of this effort. A checksum on one of these packet types could
have its root in packet memory, because all of these test packet types are stored for a time in
the packet memory. If the failure is within the packet memory and is repeatable, run the
packet memory scan to isolate and correct the failure.)
these packet types are all part of this effort. A checksum on one of these packet types could
have its root in packet memory, because all of these test packet types are stored for a time in
the packet memory. If the failure is within the packet memory and is repeatable, run the
packet memory scan to isolate and correct the failure.)
error condition
The reason the sys-health-check error was logged:
•
checksum error
•
bad SNAP
•
bad OUI
•
bad version
•
bad length
•
First 16 bytes of unknown pkt
•
pkt corruption
•
pkt missed
location
Defines the slot number for the error location, where:
•
M-BRD is the main board of a Summit system.
•
BPLANE is the backplane of an Alpine system.
•
MSM-A, MSM-B, MSM-C, and MSM-D represent the MSM modules of a BlackDiamond
system.
system.
•
Slot-<n> is the slot designation for an I/O module in a BlackDiamond system.