Qlogic Storage Networking (Unified Fabric Pilot), Руководство по установке

Страница: 35 / 76

5–Validation Methods for DCB and FCoE
Validation Step 1—Verify PFC and ETS Parameters
51031-00 A 5-5
From the trace, you can verify the following:

DCBX Oper_Version is 0 for all devices.

ER bit is OFF in all TLVs for all devices.

EN bit is ON in all TLVs for all devices messages.

W bit is ON for the adapter and target, and OFF for the switch.

pfc_enable value is 0x08 for all devices, which means PFC is enabled for
priority 3.

Application TLV for FCoE contains a user_priority_map of 0x08 for all
devices with FCoE traffic running at priority 3.

Priority Group TLV is the same for the switch and all devices. The pgid_3
(priority 3) is assigned the pg_percentage[1], which has 50 percent of the
bandwidth allocation. All other priorities are assigned to pg_percentage[0],
and they share the remaining 50 percent of the bandwidth.
If the switch cannot propagate its DCB parameters to the peer devices, then use
the JDSU Load Tester to negotiate different versions of the DCBX protocol
(
Figure 5-4 ). The Load Tester displays the DCBX settings advertised by the switch
at its console. While the Load Tester is negotiating DCBX parameters with the
switch, capture the traffic between the Load Tester and the switch using the JDSU
Analyzer, and then view the exchanges using TraceView. In TraceView, you can
compare the DCBX exchanges with those captured when the switch is connected
to the adapter or target.
Figure 5-4. FCoE Switch Validation with Emulator Setup
If end devices do not accept the DCB parameters from the switch, configure the
same DCB parameters manually on the switches, adapters, and target devices
using their configuration consoles. After configuring the parameters, continue to
“Validation Step 2—FIP Validation” on page 5-6 .
4Gbps
10Gbps