Teledyne LeCroy SAS Suite User Manual - Manual (Page 265)

SASSuite User Manual Version 6.25
LeCroy Corporation
255
Chapter 14: SASTracker Systems
The SASTracker Command Analyzer option for SASTracer systems is designed to track
commands in a SAS or SATA network that can involve up to 8 initiators and up to 128
targets. Within this matrix, SASTracker will track all commands issued and completed,
included queue depths up to the full 16 bit depth provided for in the SAS specification.
Product Configurations
SASTracker capability is supported on the same hardware modules that support
SASTracer systems (see “Analyzer Hardware Description” on page 7). Running the
SATracer option uses a different BusEngine and cannot operate simultaneously with
SASTracer on the same CATC 10K system. A simple menu selection converts back and
forth between the two capabilities.
Theory of Operation
The SASTracker Command Analyzer option monitors traffic and identifies all new
commands issued and command completions sent in an active SAS/SATA environment.
Every command issued is tracked, and when any command exceeds a user-defined
timeout (which can vary based on command type), the system triggers and provides a
Command Log File of up to the last 8 million commands issued.
SASTracker monitors live traffic in a SAS or SATA network, and each time a command is
issued SASTracker records information on that command and begins to track that
command to determine when it is completed, how it is completed, and to trigger on any
command that fails to complete within user-defined timeout periods.
The Command Log File generated by SASTracker will contain information about every
command initiated and completed during the session. In addition, the Command Log File
will contain "command fragments" of two types:
Incompletes: Command Start Events that were not completed during the recording
session. These may include commands which exceeded the
user-defined timeout, or simply commands that were issued near the
end of the recording and did not have time to complete before
recording was stopped.
Orphans: Command End Events that do not correspond to any issued command
that is present in the recording. Called "orphans", these typically occur
when recording is started during live traffic, resulting in command
completions being observed for commands that were issued prior to
the start of recording. Orphans also occur in recordings that "wrap",
where the available memory space has been exceeded and the user
has specified that the recording should continue until a trigger
condition is encountered.
For command timeout purposes, the SASTracker Analyzer actively tracks all commands
which have been issued, but for which no Command End Event has yet occurred. Once
a Command End Event that terminates that command has occurred, the command is no