HP 5920 Series Command Reference Manual page 25

Usage guidelines
To make a VFC interface work, bind it to a physical Ethernet interface. The VFC interface sends and
receives packets through the Ethernet interface bound to it.
To use one physical link to carry multiple VFC interfaces, you must bind these VFC interfaces to different
peer FCoE MAC addresses. However, you can bind them to one Ethernet interface. The FCoE MAC
address identifies the device that communicates with a VFC interface. For a point-to-multipoint network,
the FCoE MAC address is required. For a point-to-point network, the FCoE MAC address is optional.
You can use the display fcoe command to display the FCoE MAC address of a switch. You can display
the FCoE MAC address of an ENode through some software or the NMS.
A VFC interface can be bound to only one Ethernet interface and to only one FCoE MAC address.
An Ethernet interface can be bound to multiple VFC interfaces, but an FCoE MAC address can be bound
to only one VFC interface.
You must change the switch to the expert mode before binding a VFC interface to an S-channel interface
or S-channel aggregate interface. Otherwise, the binding will fail. The switch supports FCoE over
S-channel capabilities only when it is operating in expert mode. For information about system operating
modes, see Fundamentals Configuration Guide. For information about S-channel interfaces and
S-channel aggregate interfaces, see EVB Configuration Guide.
To successfully bind a VFC interface to a Layer 2 Ethernet interface, make sure the Layer 2 Ethernet
interface is FCoE capable. To successfully bind a VFC interface to a Layer 2 aggregate interface, make
sure all member ports of the Layer 2 aggregate interface are FCoE capable. New member ports of the
Layer 2 aggregate interface must also be FCoE capable. To successfully bind a VFC interface to an
S-channel interface, make sure the Layer 2 Ethernet interface associated with the S-channel interface has
FCoE over S-channel capabilities. To successfully bind a VFC interface to an S-channel aggregate
interface, make sure all member ports of the Layer 2 Ethernet aggregate interface associated with the
S-channel aggregate interface have FCoE over S-channel capabilities. New member ports of the Layer
2 Ethernet aggregate interface must also have FCoE over S-channel capabilities. Otherwise, FCoE traffic
might be blocked. For FCoE-capable cards and cards that have FCoE over S-channel capabilities, see
the specific product manual.
The binding to the Layer 2 aggregate interface does not take effect when you perform the following tasks:
• Bind one VFC interface to a Layer 2 aggregate interface.
Bind another VFC interface to a Layer 2 Ethernet interface that is a member port of the Layer 2
•
aggregate interface.
The binding to an S-channel aggregate interface does not take effect when you perform the following
tasks:
Bind one VFC interface to the S-channel aggregate interface.
•
Bind another VFC interface to a member port of the Layer 2 aggregate interface associated with the
•
S-channel aggregate interface.
Enabling EVB on a Layer 2 Ethernet interface or Layer 2 aggregate interface disables the interface from
forwarding FCoE traffic. To enable such an interface to forward FCoE traffic, you must create an
S-channel interface or S-channel aggregate interface and bind a VFC interface to the created interface.
FCoE over S-channel can be used only between an EVB-capable switch and a server.
Examples
# Bind interface VFC 4 to interface Ten-GigabitEthernet 1/0/1 and FCoE MAC address
000c-2999-eacd.
19