FCoE Cookbook for HP Virtual Connect Version 4.20 Firmware Enhancements May 2014

13
 For each FCoE VLAN, a unique FC VSAN must be created on the switch and association between the two must be
strictly configured as 1-to-1 (i. e. VLAN x maps with VSAN y and to increase the FCoE traffic identification, we
recommend to use x=y, e.g. VLAN 200 maps with VSAN 200).
Figure 5: VSAN Support when using multi-FCoE networks
Virtual Connect
(FIP Snooping mode)
FCoE
FC
Storage
Target 1
FCF
Switch
Storage
Target 2
Storage
Target 3
Server 3
Server 2
Server 1
FCoE
vnet 200
(VLAN 200)
FCoE
vnet 300
(VLAN 300)
FCoE
vnet 400
(VLAN 400)
Shared
UplinkSet
Eth1
Eth2
Map
VLAN 200 >
VSAN 200
Map
VLAN 300 >
VSAN 300
Map
VLAN 400 >
VSAN 400
VSAN Trunk
200,300,400
X1
X2
SAN
Switch
VSAN Trunk
200,300,400
FC Port for
VSAN 200
FC Port for
VSAN 300
FC Port for
VSAN 400
VSAN
Membership
control
Note: Mapping of a single VLAN into multiple VSANs is not supported.
Note: Like all other vendors, Virtual Connect supports a single lossless Priority Flow Control (PFC) queue for all FCoE
networks that are defined on any specific shared uplink set. Sharing PFC queue between multiple VSANs will make it
possible that traffic from one VSAN may have impact on traffic from other VSANs. For that reason, it is highly
recommended to create enough SAN subscription to avoid any over-subscription issues that would prevent SAN to
pause and therefore to impact other VSANs.