FC - Multi Target Fabric Test Suite (v1.2)
FC - Multi Target Fabric Test Suite (v1.2)
Technical Document
ACKNOWLEDGMENTS .........................................................................................................................3
INTRODUCTION...........................................................................................................................................4
REFERENCES..................................................................................................................................................5
Purpose
The purpose is a short statement describing what the test attempts to achieve. The test is written at the
functional level.
References
The references section lists cross-references to the Fibre Channel standards and other documentation that
might be helpful in understanding and evaluating the test and results.
Resource Requirements
The requirements section specifies the software, hardware, and test equipment that will be needed to
perform the test. The items contained in this section are special test devices, software that must reside on
the DUT, or other facilities that may not be available on all devices.
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. It also contains additional information that
may be helpful in understanding the operation of the test.
Test Setup
The setup section describes in detail the configuration of the test environment and may include a block
diagram for clarification as well as information such as the interconnection of devices, what monitoring
equipment should capture, what the generation equipment should send, and any other configuration
information vital to carrying out the test. Small changes in the configuration are included in the procedure
section.
Procedure
The procedure section of the test description contains the step-by-step instructions for carrying out the test.
It provides a cookbook approach to testing, and will often be interspersed with observable results.
Observable Results
The observable results section lists observables that can be examined by the tester to verify that the DUT is
operating properly. When multiple values are possible for an observable, this section provides a short
discussion on how to interpret them.
Possible Problems
This section provides some clues to look for if the test does not yield the expected results.
Test Setup (example with switch connected to two port target emulator):
FC Switch
Initiator
Target
Emulator
References:
[1] FC-SW-4
[2] FC-AL-2
Resource Requirements:
• Analyzer to capture Primitive Signals, Primitive Sequences, FC-2 layer frames, and errors.
Discussion: It is expected that on power up the initiator and targets will login into the switch and the switch
will present each target to the initiator. The initiator is expected to present each target to the host operating
system.
Test Setup: Test Setup. All of the devices are powered off.
Procedure:
1. Power on the target emulator.
2. Create a single target on each port of the target emulator.
3. Power on the switch, followed by the initiator.
Observable results:
• Verify that each target was recognized in the host operating system of the initiator.
• Verify that SCSI operations succeeded to each of the targets.
Possible Problems: If either observable result fails, traces will need to be taken and further analysis done.
References:
[1] FC-SW-4
[2] FC-AL-2
Resource Requirements:
• Analyzer to capture Primitive Signals, Primitive Sequences, FC-2 layer frames, and errors.
Discussion: It is expected that after power disruptions the initiator and targets will re-initialize with the
switch, re-login to the switch and the switch will present each target to the initiator. The initiator is
expected to present each target to the host operating system.
Test Setup: Test Setup. All of the devices are powered on and each target emulator port has one target
created.
Procedure:
1. Power cycle the initiator.
2. Verify the observable results.
3. Power cycle the switch.
4. Verify the observable results.
5. Power cycle the target emulator.
6. Create a single target on each port of the target emulator.
7. Verify the observable results.
Observable results:
• Verify that each target was recognized in the host operating system of the initiator.
• Verify that SCSI operations succeeded to each of the targets.
Possible Problems: If either observable result fails, traces will need to be taken and further analysis done.
References:
[1] FC-SW-4
[2] FC-AL-2
Resource Requirements:
• Analyzer to capture Primitive Signals, Primitive Sequences, FC-2 layer frames, and errors.
Discussion: It is expected that after fiber disconnect/reconnect the initiator and targets will re-initialize
with the switch, re-login to the switch and the switch will present each target to the initiator. The initiator
is expected to present each target to the host operating system.
Test Setup: Test Setup. All of the devices are powered on and each target emulator port has one target
created.
Procedure:
1. Disconnect the initiator from the switch for two seconds then reconnect.
2. Verify the observable results.
3. Disconnect the target emulator port from the switch for two seconds then reconnect.
4. Verify the observable results.
5. Repeat steps three and four for each target emulator port connected to the switch.
Observable results:
• Verify that each target was recognized in the host operating system of the initiator.
• Verify that SCSI operations succeeded to each of the targets.
Possible Problems: If either observable result fails, traces will need to be taken and further analysis done.
References:
[1] FC-SW-4
[2] FC-AL-2
Resource Requirements:
• Analyzer to capture Primitive Signals, Primitive Sequences, FC-2 layer frames, and errors.
Discussion: It is expected that on power up the initiator and targets will login into the switch and the switch
will present each target to the initiator. The initiator is expected to present each target to the host operating
system.
Test Setup: Test Setup. All of the devices are powered off.
Procedure:
1. Power on the target emulator.
2. Create 125 targets on each port of the target emulator.
3. Power on the switch, followed by the initiator.
Observable results:
• Verify that each target was recognized in the host operating system of the initiator.
• Verify that SCSI operations succeeded to a target on each port of the target emulator.
Possible Problems: If either observable result fails, traces will need to be taken and further analysis done.
References:
[1] FC-SW-4
[2] FC-AL-2
Resource Requirements:
• Analyzer to capture Primitive Signals, Primitive Sequences, FC-2 layer frames, and errors.
Discussion: It is expected that after power disruptions the initiator and targets will re-initialize with the
switch, re-login to the switch and the switch will present each target to the initiator. The initiator is
expected to present each target to the host operating system.
Test Setup: Test Setup. All of the devices are powered on and each target emulator port has 125 targets per
port created.
Procedure:
1. Power cycle the initiator.
2. Verify the observable results.
3. Power cycle the switch.
4. Verify the observable results.
5. Power cycle the target emulator.
6. Create 125 targets on each port of the target emulator.
7. Verify the observable results.
Observable results:
• Verify that each target was recognized in the host operating system of the initiator.
• Verify that SCSI operations succeeded to a target on each port of the target emulator.
Possible Problems: If either observable result fails, traces will need to be taken and further analysis done.
In some cases, if errors occur in early steps, the entire system will need to be rebooted in order to complete
the test.
References:
[1] FC-SW-4
[2] FC-AL-2
Resource Requirements:
• Analyzer to capture Primitive Signals, Primitive Sequences, FC-2 layer frames, and errors.
Discussion: It is expected that after fiber disconnect/reconnect the initiator and targets will re-initialize
with the switch, re-login to the switch and the switch will present each target to the initiator. The initiator
is expected to present each target to the host operating system.
Test Setup: Test Setup. All of the devices are powered on and each target emulator port has 125 targets
created.
Procedure:
1. Disconnect the initiator from the switch for two seconds then reconnect.
2. Verify the observable results.
3. Disconnect the target emulator port from the switch for two seconds then reconnect.
4. Verify the observable results.
5. Repeat steps three and four for each target emulator port connected to the switch.
Observable results:
• Verify that each target was recognized in the host operating system of the initiator.
• Verify that SCSI operations succeeded to a target on each port of the target emulator.
Possible Problems: If either observable result fails, traces will need to be taken and further analysis done.
Purpose: To confirm proper continued operation of the initiator and switch during high load and
disruptions.
References:
[1] FC-SW-4
[2] FC-AL-2
Resource Requirements:
• Analyzer to capture Primitive Signals, Primitive Sequences, FC-2 layer frames, and errors.
Discussion: It is expected that after disruptions the initiator and targets will re-initialize with the switch, re-
login to the switch and the switch will present each target to the initiator. The initiator is expected to
present each target to the host operating system.
Test Setup: Test Setup. All of the devices are powered on and each target emulator port has 125 targets
created.
Procedure:
1. Generate application load from the initiator to all recognized targets.
2. If no errors have been reported by the SCSI application after a fifteen-minute period of time, then
instruct the target emulator to introduce a LIP and verify continued operation.
Observable results:
• Verify that each target was recognized in the host operating system of the initiator.
• Verify that SCSI operations succeeded to all targets on each port of the target emulator.
Possible Problems: The fifteen-minute time period is chosen to correspond to 3x1012 bits transmitted. If a
2G line rate is used a thirty–minute time period should be used. If either observable result fails, traces will
need to be taken and further analysis done.