Viavi Xgig User Manual page 359

Using the Traffic Summary Pane
Traffic Summary SAS/SATA Speed Negotiation Counters
The following table describes the SAS/SATA Speed Negotiation counters within the Traffic
Summary pane of TraceView. TraceView uses timing values and other criterion to determine
events reported for speed negotiation using OOB signals.
Table 32: Traffic Summary SAS/SATA Speed Negotiation Counters
Speed Negotiation Counters
Valid Speed Negotiation
Valid SNW-1
Valid SNW-2
Valid SNW-3
Valid Final-SNW (1.5 Gbps)
Valid Final-SNW (3.0 Gbps)
Valid Train SNW
ATT (Actual Training time) within
spec
RCDT (Rate Change Delay Time)
within spec
SNTT (Speed Negotiation
Transmit time) within spec
SATA 1.5 Gbps speed detected
SATA 3.0 Gbps speed detected
SATA 6.0 Gbps speed detected
Xgig Analyzer User's Guide
Chapter 14, Using the Secondary Panes in Xgig TraceView
Description
This counter increments when the analyzer receives ALIGN(1)
primitives from both ends of a SAS link at 1.5 Gbps during SNW-1
window of the SAS speed negotiation sequence.
This counter increments when the analyzer receives ALIGN(1)
primitives from both ends of a SAS link at 3.0 Gbps during SNW-2
window of the SAS speed negotiation sequence.
This counter increments when the analyzer receives one or more
SAS-2 SNW-3 phy capabilities bits transmitted as COMWAKE OOB
signals during SNW-3 window of the SAS speed negotiation
sequence.
This counter increments when a Final-SNW event at 1.5 Gbps is
detected. A valid Final-SNW event is set when the analyzer receives
ALIGN(1) primitives from both ends of a SAS link at 1.5 Gbps rate
during Final-SNW window of the SAS speed negotiation sequence.
This counter increments when a Final-SNW event at 3.0Gbps is
detected. A valid Final-SNW event is set when the analyzer receives
ALIGN(1) primitives from both ends of a SAS link at 3.0 Gbps rate
during Final-SNW window of the SAS speed negotiation sequence.
This counter increments when any Valid Train SNW event is detected,
regardless of the speed or parameters set for the speed negotiation.
This counter increments when an ATT within spec event is detected.
An ATT within spec event is set when the measured value of ATT is
within TLT (Training Lock Time) which is defined to be 28497920 OOBI
or ~ 18.998613 ms.
This counter increments when an RDCT within spec event is detected.
A SAS device shall send D.C Idle for 750000 OOBI (nominal value =
500 us) during the RCDT phase of a SAS speed negotiation window
time. An RDCT within spec event is set when the measured RCDT
value lies within this range: 492.5 us < RCDT < 507.5 us.
This counter increments when an SNTT within spec event is detected.
A SAS device shall send ALIGN(0) or ALIGN(1) for 163840 OOBI
(nominal value = 109.2 us) during the SNTT phase of a SAS speed
negotiation window time. An SNTT within spec event is set when the
measured SNTT time lies within this range: 102.5 us < SNTT < 117.5
us
This counter increments when ALIGN(0) primitives are detected from
host and drive at 1.5 Gbps on a SATA link.
This counter increments when ALIGN(0) primitives are detected from
host and drive at 3.0 Gbps on a SATA link.
This counter increments when ALIGN(0) primitives are detected from
host and drive at 6.0 Gbps on a SATA link.
345