UNH-IOL FIBRE CHANNEL CONSORTIUM · INTRODUCTION Overview The University of New Hampshire’s InterOperability Laboratory (IOL) is an institution designed ... Fibre Channel Arbitrated

UNH-IOL FIBRE CHANNEL CONSORTIUM

Multi Target Loop

Interoperability Test Suite Version 1.1

Technical Document

Last Updated: September 18, 2006

Copyright 2006 University of New Hampshire InterOperability Lab

Fibre Channel Consortium 121 Technology Drive, Suite 2 InterOperability Laboratory Durham, NH 03824 University of New Hampshire Phone: (603) 862-0701 http://www.iol.unh.edu/consortiums/fc Fax: (603) 862-4181

http://www.iol.unh.edu/consortiums/fc

TABLE OF CONTENTS MODIFICATION RECORD..............................................................................................................2 ACKNOWLEDGMENTS .....................................................................................................................3 INTRODUCTION.......................................................................................................................................4 REFERENCES..............................................................................................................................................5 TEST SETUPS ..............................................................................................................................................6 GROUP 1: SCREENING ......................................................................................................................7 TEST 1.1: POWER UP OF INITIATOR.............................................................................................................................8 TEST 1.2: INITIATOR DISCONNECT AND REINSERT ......................................................................................................9 TEST 1.3: POWER CYCLE OF TARGET EMULATOR ....................................................................................................10 TEST 1.4: TARGET EMULATOR DISCONNECT AND REINSERT.....................................................................................11 GROUP 2: LOOP BUILD...................................................................................................................12 TEST 2.1: LOOP BUILD..............................................................................................................................................13 GROUP 3: LOOP DISRUPTIONS ..............................................................................................14 TEST 3.1: INITIATOR POWER CYCLE..........................................................................................................................15 TEST 3.2: INITIATOR CABLE REMOVAL AND REINSERTION........................................................................................16 TEST 3.3: TARGET POWER CYCLE ............................................................................................................................17 TEST 3.4: TARGET EMULATOR CABLE REMOVAL AND REINSERTION ........................................................................18 GROUP 4: APPLICATION LOAD .............................................................................................19 TEST 4.1: APPLICATION LOAD..................................................................................................................................20 APPENDIX A: PLOGI PAYLOAD.....................................................................................................................21 APPENDIX B: PRLI PAYLOAD ........................................................................................................................22 APPENDIX C: PLOGI_ACC PAYLOAD ..........................................................................................................23 APPENDIX D: PRLI_ACC PAYLOAD..............................................................................................................24 APPENDIX E: EXPECTED MANNER OF LOOP INITIALIZATION .........................................................25 APPENDIX F: INITIATOR’S CONNECTION WITH TARGET ...................................................................25 APPENDIX G: INITIATOR’S CONNECTION AFTER TARGET POWER CYCLE..................................26 APPENDIX H: TEST 3.1 POWER OFF OBSERVABLE RESULTS..............................................................26 APPENDIX I: TEST 3.1 POWER ON OBSERVABLE RESULTS .................................................................26 APPENDIX J: TEST 3.3 POWER OFF OBSERVABLE RESULTS...............................................................27 APPENDIX K: TEST 3.3 POWER ON OBSERVABLE RESULTS................................................................27

Fibre Channel Test Suite 1 Multi Target Loop Interoperability Test Suite Version 1.0

MODIFICATION RECORD

September 11, 2006 (Version 1.0 ) Mikkel Hagen September 18, 2006 (Version 1.1) Mikkel Hagen


ACKNOWLEDGMENTS The University of New Hampshire would like to acknowledge the efforts of the following individuals in the development of this test suite. Mikkel Hagen University of New Hampshire John Ogembo University of New Hampshire Ashish Palekar University of New Hampshire Dan Reynolds University of New Hampshire David Woolf University of New Hampshire


INTRODUCTION Overview The University of New Hampshire’s InterOperability Laboratory (IOL) is an institution designed to improve the interoperability of standards based products by providing an environment where a product can be tested against other implementations of a standard. This suite of tests has been developed to help vendors evaluate the functioning of their Fibre Channel Arbitrated Loop based products. Rather, they provide one method to isolate problems within a Fibre Channel device. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other all Fibre Channel devices. However, combined with satisfactory operation in the IOL’s semi-production environment, these tests provide a reasonable level of confidence that the Device Under Test (DUT) will function well in most multi-vendor Fibre Channel environments. Test Number and Title The test number is given based on the order of the test within the test group. Groups are arranged according to similar test setups or similar observable results. The title is a basic description of the test. Purpose The purpose is a short statement describing what the test attempts to achieve. The test is written at the functional level. References This section specifies all reference material that might be helpful in understanding the test methodology and/or test results. Resource Requirements The requirements section specifies the test hardware and/or software needed to perform the test. This is generally expressed in terms of minimum requirements; however in some cases, specific equipment manufacturer/model information may be provided. Last Modification This specifies the date of the last modification to this test. Discussion The discussion covers the assumptions made in the design or implementation of the test, as well as known limitations. Other items specific to the test are covered here as well. Test Setup The setup section describes the initial configuration of the test environment. Small changes in the configuration are not included here, and are generally covered in the test procedure section. Procedure The procedure section of the test description contains the systematic instructions for carrying out the test. It provides a cookbook approach to testing, and may be interspersed with observable results. Observable Results This section lists the specific observables that are examined by the tester in order to verify that the DUT is operating properly. When multiple values for an observable are possible, this section provides a short discussion on how to interpret them. The determination of a pass or fail outcome for a particular test is generally based on the successful (or unsuccessful) detection of a specific observable. Possible Problems


This section contains a description of known issues with the test procedure, which may affect test results in certain situations. It may also refer the reader to test suite appendices and/or other external sources that may provide more detail regarding these issues.

REFERENCES The following documents are referenced in this text:

[1] T11/Project 1513-DT/Rev 3.1 – Fibre Channel – Device Attach (FC-DA) [2] T11/Project 1133D/ Rev 7.0 Amendment – Fibre Channel Arbitrated Loop – (FC-AL-2) [3] T11/Project 1331-D/Rev 1.90 – Fibre Channel Framing and Signaling (FC-FS) [4] T10/Project 1560-D/Rev 4.0 – Fibre Channel Protocol for SCSI – 3 (FCP-3)


TEST SETUPS Test Setup 1: The Target Emulator is connected to the Initiator through the analyzer.

HBA

Fibre Channel Test Suite

A

B

Analyzer Target Emulator

6 Multi Target Loop Interoperability Test Suite Version 1.0

Group 1: Screening Overview: These tests are designed to verify basic interoperability of an Initiator with a Target Emulator. The following tests examine the behavior of an Initiator that is operating in an arbitrated loop with multiple Targets. The interaction between a SCSI Initiator and a Target in a Fibre Channel loop environment with real applications is complex. This interoperability procedure is designed to verify that the Initiator that is under test will operate properly with the Target Emulator. The procedure requires the ability to observe the behavior of the loop, and to understand the proper behavior of the applications using the SCSI services. The primary observable used to determine the “pass/fail” result of test cases is the successful operation of the SCSI based application. During each step, a trace is made and then examined. If the trace shows improper or unexpected behavior the tester may label the test as failing. During screening, the Initiator is checked for basic interoperability with the Target Emulator. The SCSI Initiator is tested in a pair configuration with the Target Emulator. The Initiator is connected to the analyzer with the Target Emulator. The analyzer is configured so that the input to the Initiator and the output from the Initiator can be observed. This testing document describes an interoperability procedure. Interoperability procedures require a high degree of analysis by the tester to ensure that the behavior is correct. For this reason the observable results section should be used as a guide. The guide may need to be modified to take into account specifics of the equipment being used in the testing.


Test 1.1: Power up of Initiator Purpose: To verify basic interoperability of the Initiator with the Target Emulator upon Initiator power up. References:

[1] FC-DA [2] FC-FS [3] FC-AL-2

Resource Requirements: • A SCSI Initiator. • A SCSI Target Emulator. • Monitor to capture frames, Primitive Signals, and Primitive Sequences • Applications or system software that allows the administrator to:

o Identify arbitrated loop resources o Perform read/write operations to Target resources o Configure Target resources

Modification Record: September 11, 2006 Discussion: It is expected that on power up an Initiator will discover an attached Target and make that Target resource available to the host operating system. During power on, signaling and power may fluctuate. It is expected that these fluctuations not affect the eventual operation of a SCSI Initiator-Target nexus. Test Setup: Test Setup 1. The Initiator and Target Emulator are powered off. Procedure:

1. Power on the SCSI Target Emulator. 2. Create a single target on the Target Emulator. 3. Power on the SCSI Initiator. 4. Start SCSI application on Initiator.

Observable Results:

1. SCSI application runs properly. 2. Loop is operational and initialized in expected manner as described in Appendix E 3. Initiator establishes connections to Target Emulator as shown in Appendix F

Possible Problems: None


Test 1.2: Initiator disconnect and reinsert Purpose: To verify proper operations of the Target Emulator and the Initiator after the Initiator is disconnected and reinserted. References:

[1] FC-DA [2] FC-FS [3] FC-AL-2

Resource Requirements:

• A SCSI Initiator. • A SCSI Target Emulator. • Monitor to capture frames, Primitive Signals, and Primitive Sequences • Applications or system software that allows the administrator to:


Modification Record: September 11, 2006 Discussion: The SCSI Initiator is tested in a pair configuration with the Target Emulator. The Initiator is disconnected from the Target Emulator. The monitor is configured so that the input to the Initiator and the output from the Initiator can be observed. This screening process is then performed for the SCSI Initiator. The Initiator is then reattached to the Target Emulator. Test Setup: Test Setup 1. The Initiator and Target Emulator are powered on. One Target is created on the Target Emulator. Procedure:

1. Remove the cable for a copper Initiator, or the receiver fiber for an optical Initiator. 2. Reconnect the cable to the SCSI Initiator. 3. Verify the continued operation of the SCSI application, or for an application that requires re-

initialization verify that the application will restart.

Observable Results: 1. SCSI applications resume normally. 2. Loop is operational and reinitialized in expected manner as shown in Appendix E 3. Initiator establishes connections to Target as shown in Appendix F and G

Possible Problems: None.


Test 1.3: Power Cycle of Target Emulator Purpose: To verify proper operations of the Target Emulator and the Initiator after the Target Emulator is power cycled. References:

[1] FC-DA [2] FC-FS [3] FC-AL-2




Modification Record: September 11, 2006 Discussion: The SCSI Initiator is tested in a pair configuration with the Target Emulator. The Target Emulator is power cycled. The monitor is configured so that the input to the Initiator and the output from the Initiator can be observed. This screening process is then performed for the SCSI Initiator. Test Setup: Test Setup 1. The Initiator and Target Emulator are powered on. Procedure:

1. Power off the Target Emulator. 2. Power on the Target Emulator. 3. Create a single target on the Target Emulator. 4. Start SCSI application on the Host System.

Observable Results:

1. SCSI applications resume normally. 2. Loop is operational and reinitialized in expected manner as shown in Appendix E 3. Initiator establishes connections to Target Emulator as shown in Appendix F



Test 1.4: Target Emulator Disconnect and Reinsert Purpose: To verify proper operations of the Target Emulator and the Initiator after the Target Emulator is disconnected and reinserted. References:

[1] FC-DA [2] FC-FS [3] FC-AL-2




Modification Record: September 11, 2006 Discussion: The SCSI Initiator is tested in a pair configuration with the Target Emulator. The Target Emulator is disconnected and reinserted. The monitor is configured so that the input to the Initiator and the output from the Initiator can be observed. This screening process is then performed for the SCSI Initiator. Test Setup: Test Setup 1. The Initiator and Target Emulator are powered on. One Target is created on the Target Emulator. Procedure:

1. Remove the cable or the receive fiber for the Target Emulator. 2. Reconnect the cable to the Target Emulator. 3. Verify the continued operation of the SCSI application, or for an application that requires re

initialization verify that the application will restart. Observable Results:

1. SCSI applications resume normally. 2. Loop is operational and reinitialized in expected manner as shown in Appendix E 3. Initiator establishes connections to Target Emulator as shown in Appendix F



Group 2: Loop Build Overview: 125 SCSI Targets are created on the SCSI Target Emulator and low-level SCSI activity is started on the Initiator. A Fibre Channel Initiator should be able to handle an arbitrated loop that is near capacity. These tests are designed to verify an Initiator’s capacity to identify and operate with 125 targets on an arbitrated loop.


Test 2.1: Loop build Purpose: To verify proper operation of the Initiator during loop build. References:

[1] FC-DA [2] FC-FS [3] FC-AL-2




Modification Record: September 11, 2006 Discussion: In the loop build phase the Initiator and the Target Emulator are operational on the loop and 125 Targets are created on the Target Emulator. After the addition of the targets, the loop is examined to see if it is still operating properly. SCSI applications are checked or started to verify proper operation from the application level. Test Setup: Test Setup 1. The Initiator and Target are powered off. Procedure:

1. Power on the Target Emulator. 2. Create 125 targets on the Target Emulator. 3. Ensure the loop is in a stable state with SCSI traffic between the Initiator and a target on the loop. 4. Verify the proper operation of applications running on the SCSI Initiator.

Observable Results:

1. SCSI applications continue to operate. 2. Loop is operational and reinitialized in expected manner as shown in Appendix E. 3. The Initiator establishes connections to all targets as shown in Appendix F. 4. The Initiator’s SCSI applications are operational. 5. There is no exchange of frames or primitives between Initiator and Target Emulator that results in

continuous frame generation or re-initialization of the loop. Possible problems: It is often necessary to repeat a test step with different trigger conditions or with different monitoring points to isolate a problem.


Group 3: Loop Disruptions Overview: The functioning loop consisting of the SCSI Initiator and multiple SCSI Targets is subjected to disruptions including power cycles and cable disconnects while SCSI Traffic is being transmitted on the loop.


Test 3.1: Initiator power cycle Purpose: To verify proper operations of the Initiator and the Target Emulator with loop disruptions during initial power cycle. References:

[1] FC-DA [2] FC-FS [3] FC-AL-2




Modification Record: September 11, 2006 Discussion: During this phase of testing, the initiator is removed and reinserted into the operational loop to examine the stability of the configuration. Test Setup: Test Setup 1. The Initiator and Target are powered on. 125 Targets are created on the Target Emulator. Procedure:

1. Remove the Initiator from the loop by shutting the host down and powering it off. 2. Power on the Initiator and bring up the operating environment and SCSI application. 3. Verify that the host detects all 125 Targets and the SCSI application continues to run on a Target.

Observable Results:

1. Power off observable results as shown in Appendix H. 2. Power on observable results as shown in Appendix I.

Possible problems: None


Test 3.2: Initiator cable removal and reinsertion Purpose: To verify proper operations of the Initiator and the Target Emulator during Initiator cable removal and reinsertion References:

[1] FC-DA [2] FC-FS [3] FC-AL-2




Modification Record: September 11, 2006 Discussion: The Initiator is removed and reinserted into the operational loop to examine the stability of the configuration. Test Setup: Test Setup 1. The Initiator and Target are powered on. 125 Targets are established on the Target Emulator. Procedure:

1. Remove the receive fiber or the complete cable of the Initiator. 2. Reinsert the connector. 3. Verify that the loop is stable, SCSI applications are running properly on all Targets, and all

Targets are properly detected by the host system. Observable Results:

1. Loop is operational and reinitialized in expected manner as shown in Appendix E 2. Added Initiator establishes connections to Targets as shown in Appendix F 3. Verify that the host detects all 125 Targets and SCSI applications continue to run on a Target.



Test 3.3: Target Power Cycle Purpose: To verify proper operations of the Initiator and the Target Emulator during Target Emulator power cycle. References:

[1] FC-DA [2] FC-FS [3] FC-AL-2




Modification Record: September 11, 2006 Discussion: The Target Emulator is power cycled in an operational loop to examine the stability of the configuration. Test Setup: Test Setup 1. The Target and the Initiators are powered on. 125 Targets are established on the Target Emulator. Procedure:

1. Remove the Target from the loop by powering it off. 2. Verify that SCSI applications abort or time out on the Initiator. 3. Verify that the loop is operational. 4. Power on the Target Emulator. 5. Create 125 Targets on the Target Emulator. 6. Restart applications that require intervention. 7. Verify that the host detects all 125 Targets and the SCSI application continues to run on a Target.

Observable Results:

1. Power off observable results as shown in Appendix J. 2. Power on observable results as shown in Appendix K. 3. Initiator established connection with Target as shown in Appendix G.



Test 3.4: Target Emulator cable removal and reinsertion Purpose: To verify proper operations of the Target Emulator and the Initiator during cable removal and reinsertion. References:

[1] FC-DA [2] FC-FS [3] FC-AL-2




Modification Record: September 11, 2006 Discussion: The Target Emulator cable is removed and reinserted in an operational loop to examine the stability of the configuration. Test Setup: Test Setup 1. The Initiator and Target Emulator are powered on. 125 Targets are established on the Target Emulator. Procedure:

1. Remove and reinsert the Target’s connector, if an optical connection, remove only the receive fiber of the Target Emulator.

2. Verify that SCSI applications continue to operate or can be restarted. Observable Results:

1. Loop is operational and reinitialized in expected manner as shown in Appendix E 2. Initiator establishes connections to Target as shown in Appendix F. 3. Initiator’s applications are operational or can be restarted. 4. There is no exchange of frames or primitives between Initiator and Targets that result in

continuous frame generation or re-initialization of the loop. Possible Problems: None


Group 4: Application Load Overview: The level of SCSI activity is increased and disruptions are introduced again. A Fibre Channel Initiator should be able to continue to operate properly while on an arbitrated loop that is near capacity with periodic interruptions. These test are designed to verify that while operating at a high load and disruptions are introduced, that an Initiator continues to identify and operate with 125 targets on an arbitrated loop.


Test 4.1: Application Load Purpose: To verify proper operations of the Target Emulator and the Initiator during application load. References:

[1] FC-DA [2] FC-FS [3] FC-AL-2




Modification Record: September 11, 2006 Discussion: The final phase of testing in the Multi Target SCSI Loop environment involves increasing the application load and monitoring the loop for errors. It is assumed that all devices participate in loop access fairness. Test Setup: Test Setup 1. The Initiator and Target Emulator are powered on. 125 Targets are established on the Target Emulator. Procedure:

1. Generate application load from Initiator to all 125 Targets. 2. If no problems have been observed after a thirty-minute period generate LIP from the Target

Emulator and verify continued operation of applications and loop recovery. Observable Results:

1. No unexpected loop initialization 2. Proper operation of applications 3. Proper recovery from LIP

• Loop is operational and reinitialized in expected manner as shown in Appendix E • Initiator establishes connections to Target as shown in Appendix F. • Buffer to buffer credit is available

Possible Problems: Many factors can compromise the testing process. Listed below are some of the problem areas:

1. Inconsistent results due to GBIC or cable plant issues. 2. Inability to control application on the Initiator. 3. Host based loop re-initializations that are application dependent 4. Complexity introduced by multiple failure modes makes analysis difficult.


Appendix A: PLOGI Payload

Field Size Value or Value range Standard reference Notes LS_Command code

4 bytes PLOGI = 0x03000000 FC-FS rev 1.9 Table 61 and table 251

Common Service Parameters

16 bytes

FC-PH High 1 byte 20h FC-DA Table 10 Obsoleted my FC-FS, mandated by FC-DA

FC-PH Low 1 byte 20h FC-DA Table 10 Obsoleted my FC-FS, mandated by FC-DA

B to B credit 2 bytes X FC-DA Table 10 CIO, RRO, VVV, N/F, BBM

2 bytes X, X, 0, 0, X FC-DA Table 10

Rcv field size 2 bytes 256 <= n <= 2112, multiple of 4 FC-DA Table 10 Total Concurrent Sequences

2 bytes 1 <= n <= 255 00000000 XXXXXXXX

FC-DA Table 10

Relative Offset by category

2 bytes X FC-DA Table 10

E_D_TOV 4 bytes Don’t care FC-DA Table 10 Field is ignored. E_D_TOV is 2 sec.

N_Port_Name 8 bytes Don’t care FC-DA Table 10 NAA 4 bits 0001 or 0010 expected FC-FS rev 1.9 table 38 Rest of address 7.5 bytes Don’t care FC-FS rev 1.9clause 14.2 Node Name 8 bytes Same as N_Port_Name Class 1 Service Parameters

16 bytes V=0 FC-FS rev 1.9 clause 15.6.5.3

Class 2 Service Parameters


Class 3 service parameters

16 bytes See below FC-DA Table 13

Service Options VISSQDCB PEEEEEEE

2 bytes 10000000 00000000 00000 0XX0 (80 00)

FC-DA Table 13

Initiator Control XXPPZNGC CCEDDDDD

2 bytes 0000000000X00000 (00 00 or 00 10)

FC-DA Table 13

Recipient Control 2 bytes 00000000 000XX000 (00 [08 18 10 00])

FC-DA Table 13

Rcv data field size 2 bytes 256 <= n <= 2112, multiple of 4 FC-DA Table 13 Concurrent Sequences

2 bytes 1 <= n <= 255 (00 [01-FF])

FC-DA Clause 4.6.7 Table 13

N Port End to End credit

2 bytes 0x0000 FC-FS rev 1.9 clause 15.6.5.9

Open Sequences /Exchange (X)

2 bytes 00000000 XXXXXXXX (00 [01-FF])

FC-FS rev 1.9 clause 15.6.5.10

Class 6 Multicast RX_ID

2 bytes XXXXXXXX XXXXXXXX FC-FS rev 1.9 clause 23.3


16 bytes V=0


Vendor version level

16 bytes Don’t care FC-FS rev 1.9 clause 15.6.6

Appendix B: PRLI Payload

Field Size Value or Value range Standard reference

Command code 1 byte PRLI=0x20 FC-FS rev 1.9 clause 12.3.2.24

Page length 1 byte 0x10 FC-FS rev 1.9 clause 12.3.2.24

Payload length 2 bytes 20 <= n <= 65532, multiple of 4


Service Parameter Page(s) – up to 16 possible

N*0x10 where N is the number of pages


Type code 1 byte 0x08 FC-FS rev 1.9 clause 12.3.2.24

Type code extension 1 byte 0x00 FC-FS rev 1.9 clause 12.3.2.24

OPA validity 1 bit 0 FC-FS rev 1.9 clause 12.3.2.24

RPA validity 1 bit 0 FC-FS rev 1.9 clause 12.3.2.24

Establish image pair 1 bit (0-1) FC-FS rev 1.9 clause 12.3.2.24

Reserved 13 bits 0000000000000 FC-FS rev 1.9 clause 12.3.2.24

OPA 4 bytes 0xXXXXXXXX FC-FS rev 1.9 clause 12.3.2.24

RPA 4 bytes 0xXXXXXXXX FC-FS rev 1.9 clause 12.3.2.24

Service Parameters 4 bytes Reserved Bits 31-7 000000000000000000000

0000 FC-FS rev 1.9 clause 12.3.2.24

Data overlay allowed Bit 6 X FCP-3 Clause 6.3.4 Initiator function 1 bit 1 FCP-3 Clause 6.3.4 Target Function 1 bit X FCP-3 Clause 6.3.4 Read XFER_RDY disabled

1 bit 1 FCP-3 Clause 6.3.4

Write XFER_RDY disabled

1 bit X FCP-3 Clause 6.3.4


Appendix C: PLOGI_ACC Payload

Field Size Value or Value range Standard reference Notes LS_Command code 4 bytes ACC = 0x02000000 FC-FS rev 1.9 Table 61 and

table 251

Common Service Parameters

16 bytes FC-FS rev 1.9 Table 251,

FC-PH High 1 byte 0x20 FC_DA Table 10 FC-PH Low 1 byte 0x20 FC_DA Table 10 B to B credit 2 bytes 0x0000 FC-FS rev 1.9 clause 15.6.2.3 CIO, RRO, VVV, N/F, BBM

2 bytes 10X1 1X00 0X00 0XXX FC-FS rev 1.9 Table 216 Clause 15.6.2.4

Rcv field size 2 bytes 256 <= n <= 2112, multiple of 4

FC_DA Table 10

Total Concurrent Sequences

2 bytes 1 <= n <= 255 00000000 XXXXXXXX

FC_DA Table 10

Relative Offset by category

2 bytes XXXX XXXX XXXX XX1X

FC_DA Table 10

E_D_TOV 4 bytes Don’t care FC_DA Table 10 Field is ignored. E_D_TOV is 2 sec.

N_Port_Name 8 bytes Don’t care FC_DA Table 10 NAA 4 bits 0001 or 0010 expected FC_DA Table 10 Rest of address 7.5 bytes Don’t care FC-FS rev 1.9clause 14.2 Node Name 8 bytes Same as N_Port_Name Class 1 Service Parameters


Class 2 Service Parameters



16 bytes See below FC_DA Table 13

Service Options VISSQDCB PEEEEEEE

2 bytes 10000000 00000000 (80 00)

FC-DA Table 13 FC-PH-3 table 101 pg 55, figure 62A

Initiator Control XXPPZNGC CCEDDDDD

2 bytes 0000000000X00000 (00 00 or 00 10)

FC_DA Table 13

Recipient Control 2 bytes 00000000 000XX000 (00 [08 18 10 00])

FC_DA Table 13

Rcv data field size 2 bytes 256 <= n <= 2112, multiple of 4

FC_DA Table 13

Concurrent Sequences 2 bytes 1 <= n <= 255 (00 [01-FF])

FC_DA Table 13

N Port End to End credit

2 bytes 0x0000 FC-FS rev 1.9 clause 15.6.5.9

Open Sequences /Exchange (X)

2 bytes 00000000 XXXXXXXX (00 [01-FF])


Class 6 Multicast RX_ID

2 bytes XXXXXXXX XXXXXXXX

FC-FS rev 1.9 clause 23.3


16 bytes V=0

Vendor version level 16 bytes Don’t care FC-FS rev 1.9 clause 15.6.6


Appendix D: PRLI_ACC Payload

Field Size Value or Value range Standard reference Command code 1 byte PRLI=0x20 FC-FS rev 1.9 clause

12.3.2.24 Page length 1 byte 0x10 FC-FS rev 1.9 clause

12.3.2.24 Payload length 2 bytes 20 <= n <= 65532,

multiple of 4 FC-FS rev 1.9 clause 12.3.2.24

Service Parameter Page(s) – up to 16 possible

N*0x10 where N is the number of pages


Type code 1 byte 0x08 FC-FS rev 1.9 clause 12.3.2.24

Type code extension 1 byte 0x00 FC-FS rev 1.9 clause 12.3.2.24

OPA validity 1 bit 0 FC-FS rev 1.9 clause 12.3.2.24

RPA validity 1 bit 0 FC-FS rev 1.9 clause 12.3.2.24

Establish image pair 1 bit (0-1) FC-FS rev 1.9 clause 12.3.2.24

Reserved 13 bits 0000000000000 FC-FS rev 1.9 clause 12.3.2.24

OPA 4 bytes 0xXXXXXXXX FC-FS rev 1.9 clause 12.3.2.24

RPA 4 bytes 0xXXXXXXXX FC-FS rev 1.9 clause 12.3.2.24

Service Parameters 4 bytes Reserved Bits 31-7 000000000000000000000

0000 FC-FS rev 1.9 clause 12.3.2.24

Data overlay allowed Bit 6 0 FCP-3 Clause 6.3.4 Initiator function 1 bit 0 FCP-3 Clause 6.3.4 Target Function 1 bit 1 FCP-3 Clause 6.3.4 Read XFER_RDY disabled


Write XFER_RDY disabled



Appendix E: Expected manner of Loop Initialization When the loop is initialized in the expected manner, the following should be observed:

a. No unexplained cycles through loop initialization – Neither device should issue LIP for unexplained reasons. In the ideal case only one LIP sequence is observed.

b. Proper device becomes Loop Master. c. Target selects AL_PA in LIPA frame. d. Initiator selects AL_PA in LIHA or LISA frame.

Appendix F: Initiator’s connection with Target The following should be observed whenever the Initiator establishes a connection with the Target:

a. Discovers device in some manner b. Arbitrates and issues OPN properly c. Issues ARB(F0) after OPN if using fairness algorithm d. Waits for R_RDY primitive before transmitting PLOGI e. Initiator transmits properly formed PLOGI frame as follows:

• The bits listed below for the F_CTL field must be set as indicated: i.) Exchange Context (word 2 bit 23) – reset

ii.) Sequence Context (word 2 bit 22) – reset iii.) First Sequence (word 2 bit 21) – set iv.) Last Sequence (word 2 bit 20) – reset v.) End Sequence (word 2 bit 19) – set

vi.) Sequence Initiative (word 2 bit 16) – set • The PLOGI payload fields and values are shown in Appendix A.

f. Initiator transmits CLS (and IDLE after receptions of ARB(F0)) g. Initiator removes OPN addressed to it from the Target. h. Initiator issues R_RDY frames to the Target after the OPN is received i. Initiator removes PLOGI ACC frame generated by Target from loop j. Initiator transmits a properly formed PRLI frame as follows:

• The bits listed below for the F_CTL field must be set as indicated: i.) Exchange Context (word 2 bit 23) – reset

ii.) Sequence Context (word 2 bit 22) – reset iii.) First Sequence (word 2 bit 21) – set iv.) Last Sequence (word 2 bit 20) – reset v.) End Sequence (word 2 bit 19) - set

vi.) Sequence Initiative (word 2 bit 16) – set • The format of the PRLI payload is shown in Appendix B.

k. Target removes OPN generated by Initiator from loop l. Target generates R_RDY sequences for Initiator m. Target removes PLOGI frame generated by Initiator from loop n. Target arbitrates and issues OPN properly o. Target issues ARB (F0) after OPN if using fairness algorithm p. Target waits for R_RDY primitive before transmitting PLOGI ACC frame q. Target transmits properly formed PLOGI_ACC frame as follows:

• The bits listed below for the F_CTL field must be set as indicated: i.) Exchange Context (word 2 bit 23) – set

ii.) Sequence Context (word 2 bit 22) – reset iii.) First Sequence (word 2 bit 21) – reset iv.) Last Sequence (word 2 bit 20) – set v.) End Sequence (word 2 bit 19) - set

• The PLOGI_ACC Payload has the values defined in Appendix C. (Note: This is identical to the PLOGI with the exception of the command code).

r. Target transmits CLS (and IDLE after reception of ARB (F0))


s. Target transmits properly formed PRLI_ACC as follows: • The bits listed below for the F_CTL field must be set as indicated:

i.) Exchange Context (word 2 bit 23) – reset ii.) Sequence Context (word 2 bit 22) – reset

iii.) First Sequence (word 2 bit 21) – set iv.) Last Sequence (word 2 bit 20) – reset v.) End Sequence (word 2 bit 19) - set

vi.) Sequence Initiative – (word 2 bit 16) – set • The format of the PRLI_ACC payload is shown in Appendix D.

t. The Target responds to the PLOGI within 4 seconds u. The Target responds to the PRLI within 4 seconds v. Initiator transmits SCSI Inquiry for LUN numbers w. Target transmits FC4Data frames for SCSI LUN Inquire

• The Peripheral Qualifier field (word 0, bits 31-29) shall be set to: i.) 000b for valid LUNs

ii.) 011b for invalid LUNs x. Initiator transmits Read Capacity y. Target transmits Read Capacity response

Appendix G: Initiator’s connection after Target power cycle The following should be observed during the Initiator’s connection after Target power cycle:

a. Initiator transmits properly formed PDISC frame • Exchange, sequence, and delimiter stuff • PLOGI specific bits to check

b. Target transmits properly formed PDSIC reject • Exchange, sequence, and delimiter stuff • PLOGI_ACC specific fields

c. Initiator transmits PLOGI d. Target transmits PLOGI_ACC e. Initiator transmits PRLI f. Target transmits PRLI_ACC

Appendix H: Test 3.1 power off observable results The following is observed during initial power cycle of Loop disruption:

a. Loop operational • No unexpected cycles in loop initialization • Proper selection of AL_PA

b. The Initiator’s SCSI application is operational c. The Initiator performs PDISC with Target and get PDISC_ACC if LIP generated d. There is no exchange of frames or primitives that results in continuous frame generation or re-

initialization of the loop. Appendix I: Test 3.1 power on observable results The following is observed during the power on of Loop disruption:


b. The Initiator’s SCSI application is operational c. The Initiator established connection to Target properly

• Initiator transmits PLOGI to Target


• Target responds to PLOGI with PLOGI_ACC

• Initiator transmits PRLI to Target • Target responds with PRLI_ACC

d. The Initiator performs PDISC with Target and get PDISC_ACC e. There is no exchange of frames or primitives that results in continuous frame generation or re-

initialization of the loop.

Appendix J: Test 3.3 power off observable results The following is observed during the power off of the Target Emulator during loop disruptions:


b. The Initiator’s application is not operational. Appendix K: Test 3.3 power on observable results The following is observed during the power on of the Target Emulator during loop disruptions:


b. The Initiator’s application is operational or can be restarted c. The Initiator establishes connection to Target properly

• Initiator transmits PDISC • Target responds with LS-reject • Initiator transmits PLOGI • Target responds with PLOGI_ACC • Initiator transmits PRLI to Target • Target responds with PRLI_ACC

d. There is no exchange of frames or primitives that result in continuous frame generation or re-initialization of the loop.


UNH-IOL FIBRE CHANNEL CONSORTIUM · INTRODUCTION Overview The University of New Hampshire’s InterOperability Laboratory (IOL) is an institution designed ... Fibre Channel Arbitrated

Documents