HP Virtual Connect 4Gb Fibre Channel Module for c-Class BladeSystem - Manual (Page 130)

Virtual Connect networks 130
The following FCoE capable ToR switches have been tested and are supported with this feature:
• Cisco Nexus 50x0 switch operating as either NPV Gateway or FC Forwarder (FCF). In FCF mode, FC
SAN switches must be Cisco MDS family for interoperability.
• Cisco Nexus 55xx switch operating as either NPV Gateway or FC Forwarder (FCF). In FCF mode, FC
SAN switches must be Cisco MDS family for interoperability.
The following figure shows a high-level topology configuration using a Cisco Nexus 5xxx switch:
Restrictions
• No congestion notification (QCN) support is implemented. Only direct connections between VC
modules and external FCoE bridge ports are supported.
• Only one FCoE network can be associated with any single set of uplink ports.
• FCoE traffic does not cross stacking links, and a configuration using uplinks from different bays is not
allowed.
• FCoE is not supported on c3000 enclosures. You cannot create an FCoE network on a c3000
enclosure.
• Double-dense server blades are not supported by this feature.
• FCoE networks are not supported on uplink ports with SFP-LR transceivers.
HP recommends that you add any FCoE networks before adding ports. If you add the ports first, the port
selection must be eligible for an FCoE network. Otherwise, the FCoE network Add button is disabled. The
selected ports are eligible for an FCoE network if all of the ports are FCoE capable and belong to the same
bay. If you are using multiple enclosures, the same port on all enclosures must be selected.
To define an FCoE network:
1. Click Add in the Associated FCoE Network section.