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

Requirements

Refer to SPOCK C-Series FCoE Switch Connectivity stream at

http://h20272.www2.hp.com/Pages/spock2Html.aspx?htmlFile=hw_switches.html for information on:

 Minimum NX-OS version

 Minimum Virtual Connect firmware version

 HP FlexFabric Adapter Firmware and driver

Note: FCoE requires the Nexus Storage Protocols Services license (FC_FEATURES_PKG). This license is an option which

is activated when the Nexus switch is shipped from Cisco.

Guidelines

 Nexus switches must either directly connect to FC-based or FCoE-based Storage devices. Refer to the Cisco Nexus or

Storage vendor interoperability Matrix.

 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.

 The FCoE VLAN should be dedicated to FCoE traffic (i.e. it should not carry IP traffic).

 The FCoE VLAN must not 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 configuration

Details about the configuration:

 FCF mode is used.

 Interfaces eth1/5 are connected to the VC modules.

 Interfaces eth1/1 are connected to an FCoE-based storage device (EVA).

 Interfaces eth1/17 are connected to the datacenter LAN.

 Interfaces fc2/1 are directly connected to a FC-based storage device (3PAR).

 VLAN IDs 200 and 201 are used for the FCoE networks.

 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 2007 bind to eth1/1 for the FCoE-based storage target FCoE connection.