Viavi Xgig User Manual page 199

Monitor Views
Frame errors counted are:
• CRC
• Jabbers
• Fragments
• FCoE Embedded CRC
Phy Errors Tab
The Phy Errors
monitoring was started. No count is provided for ports for which the physical error makes no
sense; for example, no count is made of 10Gbps O Code errors for SAS/SATA ports.
Physical errors counted are:
• Running Disparity
• Code Violation
• O Code Errors
• Control Character Errors
• Sync Error
• Block Type Errors
• Reserved Bit Errors
• FEC Parity Errors
For Xgig, Xgig5000, and Xgig1000 ports, columns for unselected physical error types (as
configured within the
tab of List View. For example, if Code Violation errors are not selected, the Code Violation Errors
column is not shown. For "state" errors, such as loss of signal or loss of sync, the current state will
appear in the
SAS/SATA Error Counters Tab
The
SAS/SATA Error Counters
(per port) since monitoring was started.
SAS/SATA errors counted are:
• Framing Errors
• Primitive Errors
• Primitive Sequence Errors
• Multiplexing Alignment Errors
• Any Errors
For the definitions of these errors, see Table 13. This tab will only be visible if SAS/SATA
analyzer ports appear in the Resource Browser.
Xgig Analyzer User's Guide
tab shows the cumulative number of common physical errors (per port) since
tab of the
Phy Errors
column.
Traffic Status
tab shows the cumulative number of common SAS/SATA errors
Chapter 10, Xgig Performance Monitor Configuration
dialog) are not shown in the
Preference Phy Errors
185