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

51
 To reduce the risk of congestion, it is recommended to use FCoE Port Channeling.
 To increase the FCoE traffic identification and to better control the span of this traffic over the Ethernet network, it is
recommended to use different FCoE VLANs and VSANs numbers between the two fabrics.
 FCoE VLANs should be dedicated to FCoE traffic (i.e. they should not carry IP traffic).
 FCoE VLAN cannot be configured as a native VLAN (the VLAN that carries untagged traffic on trunk ports, by default
VLAN 1).
 Interfaces connecting to VC must be configured as trunk ports and STP edge ports.
 For each Blade server, one vfc interface with MAC Binding must be defined because Virtual Connect is running in FIP
snooping mode.
Virtual Connect configuration
Before you configure the upstream switches, Virtual Connect requires the creation of an Active/Active configuration of
two converged Shared Uplink Sets (SUS). Refer to the Virtual Connect configuration section.
If you need to improve the Ethernet traffic service level control, refer to the Quality of Service in the Virtual Connect
Domain section.
Nexus and MDS configuration
Current NX-OS limitations
There is currently an NX-OS limitation with FCoE Port Channels on Cisco Nexus 5000 and 5500 series. When a Port
Channel is carrying FCoE traffic, all interfaces of this port channel must belong to the same Nexus Unified Port Controller
(UPC) ASIC. At this time, it is not supported to configure an FCoE port channel across different Unified Port Controllers.
For more information, see Appendix A.
Note: These limitations will be removed in a future NX software release.
Details about the Nexus configuration:
 FCF mode is used.
 Interfaces eth1/5 and eth1/6 are connected to the VC modules through FCoE using a port channel po200.
 Interfaces eth1/19 and eth1/20 are connected to Cisco MDS 9506 switches through FCoE using a port channel po100
(VE_Ports).
 Interfaces eth1/17 are connected to the datacenter LAN.
 VLAN IDs 200, 300, 201 and 301 are used for the FCoE networks.
 VLAN 200 maps to VSAN 200, VLAN 300 to VSAN 300, VLAN 201 to VSAN 201 and VLAN 301 to VSAN 301.
 VLAN IDs 1, 10 and 20 are the standard Ethernet networks (non-FCoE networks).
 The virtual Fibre Channel interfaces vfc 2005 bind to the MAC addresses of the first Blade server.
 The virtual Fibre Channel interfaces vfc 2006 bind to the MAC addresses of the second Blade server.
 The virtual Fibre Channel interfaces vfc 1000 bind to the port channel po100 connected to the MDS 9506.
Details about the MDS 9506 configuration:
 FCF mode is used.
 A Cisco MDS 9000 10-Gbps 8-Port FCoE Module is required to enable FCoE on MDS switches.
 Interfaces Eth2/1-2 are connected to the Nexus switches thought FCoE using an Ethernet port channel epo100
(VE_Ports).
 VLAN IDs 200, 300, 201 and 301 are used for the FCoE networks.
 VLAN 200 maps to VSAN 200, VLAN 300 to VSAN 300, VLAN 201 to VSAN 201 and VLAN 301 to VSAN 301.
 The virtual Fibre Channel interfaces vfc 1000 bind to the port channel epo100 connected to the Nexus switches.