SAS: SL_CC state machine
chipalgernon at hotmail.com
Thu Mar 11 11:46:23 PST 2004
* From the T10 Reflector (t10 at t10.org), posted by:
* "Chip Algernon" <chipalgernon at hotmail.com>
(1) in sas1.1, r03 page 206, it says
22.214.171.124 SL_CC3:Connected state
126.96.36.199.1 State description
A CLOSE Received message may be received at any time while in this state,
but shall be ignored during SSP and SMP connections. If a CLOSE Received
(Clear Affiliation) is received during an STP connection, this state shall
clear any affiliation (see 7.17.4).
Can a CLOSE received message really be ignored? Can I assume this message
is latched so it is still a valid message to check in SL_CC4:DisconnectWait
For example, is the following sequence of events correct to close a SSP
assume a SSP connection open between device X and Y, then later
X sent DONE,
Y sent DONE,
Y sent CLOSE,
X sent CLOSE.
For X, if the CLOSE from Y is ignored, without register it as a valid CLOSE,
X would be in SL_CC4:DisconnectWait state and waiting for another CLOSE. I
don't think that's what the spec means when it says 'ignore'.
But if Y sent CLOSE before the DONEs are exchanged, for X, this CLOSE should
be "completely" ignored.
Do we need some clarificartion on this in the spec.?
here is 'message' definition in SAS pg8, doesn't help me on above question.
3.1.74 message: Information sent between state machines.
(2) In sas1.1 r03, page 202, it says,
188.8.131.52 SL_CC state machine overview
The state machine consists of the following states:
a) SL_CC0:Idle (see 184.108.40.206)(initial state);
b) SL_CC1:ArbSel (see 220.127.116.11);
c) SL_CC2:Selected (see 18.104.22.168);
d) SL_CC3:Connected (see 22.214.171.124);
e) SL_CC4:DisconnectWait (see 126.96.36.199);
f) SL_CC5:BreakWait (see 188.8.131.52); and
g) SL_CC6:Break (see 184.108.40.206).
SL_CC7:CLoseSTP is missing from above list.
Get business advice and resources to improve your work life, from bCentral.
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
More information about the T10