Defining an fcoe network – HP Virtual Connect 4Gb Fibre Channel Module for c-Class BladeSystem User Manual
Page 129
Virtual Connect networks 129
e.
To add labels to the network, type a label in the Labels field, and then press Enter. Labels are used
as text-based identifiers for the network within VCM. Each label can contain up to 24 characters,
excluding spaces. Each network can have up to 16 labels.
f.
Select whether to enable (checked) or disable (unchecked) Smart Link (on page
g.
Select whether to designate (checked) or not designate (unchecked) the network as a private
network ("
" on page
h.
To set the preferred or maximum connection speed, select the Advanced Network Settings check
box.
To change these settings:
i.
Click the selection box.
ii.
Select a setting (100Mb to 10Gb):
Set preferred connection speed. This value is the default speed for server profile connections
mapped to this network. The server administrator can override this setting on an individual
profile connection.
Set maximum connection speed. This value is the maximum speed for server profile connections
mapped to this network. This speed limits the maximum port speed from the server to the network
connection associated with the multiple networks.
8.
Click Apply. The shared uplink and associated networks are now defined and available for use in
creating server profiles.
Defining an FCoE network
You can create an FCoE network by creating a Shared Uplink Set and then adding an FCoE network to it.
You cannot create an FCoE network independently outside of a Shared Uplink Set.
Dual-hop FCoE support
Prior to the VC v4.01 release, VCM support of FCoE did not extend outside of the enclosure. All FCoE traffic
was converted to native FC prior to reaching VC interconnect uplinks. This solution required a FC switch to
be connected to the VC interconnects. The Dual-hop FCoE feature of VC allows FCoE traffic to be propagated
out of the enclosure to an external FCoE-capable bridge, which handles the conversion of FCoE to FC traffic
and vice-versa. This allows server connections to use Ethernet transport and results in the following benefits:
•
Cable consolidation
•
Reduction in the number of per server adapters and interconnects required
•
Reduction in utilization of the upstream switch ports
•
Ease and simplification of management
This feature is called FCoE Dual Hop because 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 Modules and the external FCoE to FC bridge device. No additional external
FCoE bridges or gateways can be in this configuration. Introducing an additional external FCoE bridge or
gateway would make it impossible to guarantee the lossless handling of the traffic and ensure
congestion-free connectivity.
This feature is supported on VC FlexFabric or VC Flex-10/10D modules. VC FlexFabric modules support
FCoE on uplink ports X1-X4, while the VC Flex10/10D modules support FCoE on all uplink ports (X1-X10).
FCoE traffic is forwarded to the ToR device, which performs the FCoE to FC traffic conversion. The ToR device
must act as either a bridge to the native FC infrastructure or directly connect to FC-based storage devices.