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

6
Purpose
This guide provides concept, deployment guidelines and use case scenarios for HP Virtual Connect when using Fibre
Channel over Ethernet through FIP Snooping under the T11 FC-BB-5 specification.
Overview
Fibre Channel over Ethernet (FCoE) through FIP Snooping under the T11 FC-BB-5 specification is supported on the HP
Virtual connect modules since VC 4.01, this feature allows the FCoE traffic to be propagated out of the enclosure to an
external bridge which will handle the conversion of FCoE to FC traffic or back to FCoE traffic if the bridge is either directly
connected to an FCoE storage target or to an FCoE Forwarder in a Multi-Hop FCoE implementation.
The traditional model of completely parallel, autonomous data and storage networks with dedicated interface cards,
switches, and cabling plants can be costly and inefficient. Enterprises are looking to consolidate server and storage
connectivity to reduce equipment and operations expenses, decrease clutter and complexity, and make more efficient
use of shared networking resources while ensuring continuity of service.
In addition to having the potential to reduce complexity at the network edge with Dual-Hop scenarios, FCoE also
promises to reduce equipment costs beyond the access layer by enabling, with Multi-Hop scenarios, convergence in the
extended network.
Requirements and support
Supported Designs
Dual Hop FCoE designs are supported.
SAN
LAN
FCoE
FCoE
Dual Hop FCoE means there are two FCoE ‘hops’ between the server and the conversion point from FCoE to FC. The first
hop is between the server CNA adapter and the VC Module. The second hop is between the VC Module and the external
FCoE to FC bridge device.