Validation Step 5-Ets Verification; Validation Process - Qlogic Storage Networking (Unified Fabric Pilot Installation Manual

5–Validation Methods for DCB and FCoE
Validation Step 5—ETS Verification
Table 5-2
PFC functions and performance. The sample data indicates that there 33 frames
were received during PFC pauses, and as a result, the link may not guarantee
lossless traffic for the FCoE application. Furthermore, the large variance between
the maximum and minimum exchange completion time is caused by the PFC
pause.
Table 5-2. FCoE Application Performance Statistics Evaluated by Expert
Average
Throughput,
Exchange
any to any
Completion
(MBps)
Time (ms)
384 4.6
Validation Step 5—ETS Verification
The purpose of this test is to verify that the switch can continuously adjust
bandwidth with different traffic priorities. This test verifies that the unified fabric
manages congestion between TCP, iSCSI, and FCoE traffic, and measures
application performance.

Validation Process

The test assumes that the hosts have mapped storage device LUNs and can
generate I/O to storage devices. The test should include two traffic classes: one
for FCoE and one for combined traffic, including iSCSI and others. If you want to
isolate and validate the switch by itself, you can also replace the Converged
Network Adapter hosts and storage targets with the Load Tester, which acts as a
traffic generator on both sides of the switch.
1. Configure ETS parameters so that:



5-18
shows some of the statistics reported by Expert software for evaluating
Maximum Minimum
Exchange Exchange
Completion Completion
time (ms) time (ms)
7.4 1.3
FCoE traffic has its own priority.
PFC is enabled.
Bandwidth is assigned to the FCoE priority. You can also allow the
FCoE switch to operate at its default value (50/50).
Average Maximum
Pause Pause Time
Time (s) (s)
28.35 38.31
Frames
Received PFC
while PFC Request
Class Count
Paused
33 41
51031-00 A