Port Requirements
VF Ports
For each host directly connected over Ethernet interfaces on the FCoE NPV bridge, a virtual Fibre Channel
(vFC) interface must be created and bound to the Ethernet interface. By default, the vFC interface is configured
in the F mode (VF port).
The VF port must be configured with the following parameters:
•
A VF port must be bound to a VLAN trunk Ethernet interface or a port-channel interface. The FCoE
VLAN must not be configured as the native VLAN on the Ethernet interface.
•
A port VSAN must be configured for the VF port.
•
The administrative state must be up.
VNP Ports
Connectivity from an FCoE NPV bridge to the FCF is only supported over point-to-point links. These links
can be individual Ethernet interfaces or members of an Ethernet port channel interface. For each FCF connected
Ethernet interfaces, a vFC interface must be created and bound to the Ethernet interface. These vFC interfaces
must be configured as VNP ports. On the VNP port, an FCoE NPV bridge emulates an FCoE-capable host
with multiple enodes, each with a unique enode MAC address. A VNP port interface binding to MAC address
is not supported. By default, the VNP port is enabled in trunk mode. Multiple VSANs can be configured on
the VNP port. The FCoE VLANs that correspond to the VNP port VSANs must be configured on the bound
Ethernet interface.
The spanning-tree protocol (STP) is automatically disabled in the FCoE VLAN on the interfaces that the
VNP port are bound to.
Note
NPV Features
The following NPV features apply for the FCoE NPV feature:
•
Automatic Traffic Mapping
•
Static Traffic Mapping
•
Disruptive Load Balancing
•
FCoE Forwarding in the FCoE NPV Bridge
•
FCoE frames received over VNP ports are forwarded only if the L2_DA matches one of the FCoE MAC
addresses assigned to hosts on the VF ports otherwise they
’
re discarded.
Cisco Nexus 5500 Series NX-OS SAN Switching Configuration Guide, Release 7.x
OL-30895-01
67
Configuring FCoE NPV
Port Requirements
