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

70
 Create a virtual Fibre Channel interface for the second Blade server and bind it to the MAC address of its FCoE adapter:
o interface vfc2006
o description vfc for server-2
o bind mac-address 00:17:a4:77:b8:a8
o no shutdown
 Assign the Fibre Channel interfaces and the Virtual Fibre Channel interfaces (vfc) to the appropriate FCoE VSANs:
o vsan database
o vsan 200
o vsan 200 interface fc2/1
o vsan 200 interface vfc 2005
o vsan 300
o vsan 300 interface fc2/2
o vsan 300 interface vfc 2006
Note: Alternatively, instead of dedicating one FC interface to one VSAN, you can use both FC interfaces to carry
the two VSANs:
o vsan 200 interface fc2/2
o vsan 300 interface fc2/1
Note: If there are multiple FC interfaces in the same VSAN, then it is not possible to assign an end device to a
specific interface.
 Configure the interface connected to the datacenter LAN:
o interface eth 1/17
o switchport mode trunk
o switchport trunk allowed vlan 1,10,20
Nexus switch-B configuration
 Upgrade the Nexus switch with minimum NX-OS supported version.
Note: Refer to SPOCK C-Series FCoE Switch Connectivity stream for additional information at
http://h20272.www2.hp.com/Pages/spock2Html.aspx?htmlFile=hw_switches.html
 Enable NPV:
o configure terminal
o feature npv
Note: Switching to NPV mode automatically performs a configuration erase and reloads the switch.
 Enable FCoE and LACP on the switch (disabled by default):
o configure terminal
o feature fcoe
o feature lacp
Note: The Nexus can require a reload.
 Configuring Quality of Service to provide lossless service for FCoE traffic and best-effort service for Ethernet traffic:
o Refer to the Quality of Service configuration section.