Maintenance Commands
555-233-143
7-180 Issue 1 May 2002
list measurements clan ethernet
This command provides a 24-hour history of important packet-level statistics from
which you can infer some LAN performance characteristics. For example:
■ high collision counts could indicate high traffic on the LAN segment
(congestion on the bus).
■ high Cyclic Redundancy Check (CRC—detects and corrects errors on
every frame) errors could suggest that
— the LAN connection may be “noisy”
— a wire connection is loose
— a wire is frayed or broken.
The 24-hour history gives the ability to look back at these measures if the trouble
cleared.
The data is collected at 15-minute intervals over 24 hours for the CRC (Cyclic
Redundancy Check) and collisions for ethernet connections. If the data cannot be
retrieved for the 15-minute interval,
N/A displays in the field. The delta (the
change from the last inquiry) and the total are provided for each error count. After
the occurrence of “N/A” (not available), the delta equals the total.
The primary use of this command is to quickly and unambiguously determine
whether the fault lies within the Avaya-provided equipment or with the LAN or LAN
administration to which the system is connected.