Changes to the FCoE Model and Related Configuration
S e n d d o c u m e n t a t i o n c o m m e n t s t o n e x u s 5 k d o c s @ c i s c o . c o m
Changes to the FCoE Model and Related Configuration
In the previous Cisco NX-OS 4.0(0)-based releases, the FCoE model allowed Ethernet and FCoE to
co-exist on the interface. The virtual interfaces, virtual Ethernet and virtual Fibre Channel (VFC), did
not affect each other. For example, if the virtual Ethernet interface was errdisabled, the VFC interface
could still be up.
With Cisco NX-OS Release 4.0(1a)N1(1), the CLI implementation was changed to provide forward
compatibility with the forthcoming T11 FCoE Initialization Protocol (FIP). In this new FCoE model, the
following is changed:
•
•
The changes to the virtual interfaces are described in the following topics:
•
•
•
•
Virtual Interface Groups
In previous Cisco NX-OS 4.0(0)-based releases, a virtual interface group allowed you to bind virtual
interfaces to a physical Ethernet interface, as shown in the following example:
switch# configure terminal
switch(config)# interface vig 1
switch(config-if)# bind interface ethernet 1/1
Virtual interface groups have been deprecated in release 4.0(1a)N1(1a).
Virtual Ethernet Interfaces
Cisco NX-OS Release 4.0(1a)N1(1a) does not support virtual Ethernet interfaces. All Ethernet features
previously configured at the virtual Ethernet interface now need to be configured at the bound Ethernet
interface.
The following configuration statements must be explicitly configured on the Ethernet interface to keep
behavior the same as virtual Ethernet interface:
spanning-tree bpduguard enable
spanning-tree port type edge trunk
All other features (for example, ACLs, SPAN etc.) that were previously configured at the virtual Ethernet
interface would need to be applied to the bound Ethernet interface.
Virtual Fibre Channel Interfaces
In previous Cisco NX-OS 4.0(0)-based releases, a virtual Fibre Channel interface was attached to a
virtual interface group, which then bound it to the physical Ethernet interface.
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
8
FCoE traffic is passed over Ethernet; the Ethernet STP controls port status.
FCoE traffic for a VSAN is transported over a single dedicated FCoE-enabled VLAN.
Although the CLI implementation requires a VLAN-to-VSAN mapping, the FCoE frames are
expected to be untagged or priority-tagged. The FCoE VLAN is not expected to be carried in the
FCoE frames. This will change in a future release once FIP-based FCoE is supported.
Virtual Interface Groups, page 8
Virtual Ethernet Interfaces, page 8
Virtual Fibre Channel Interfaces, page 8
VSAN-to-VLAN Mapping, page 9
OL-16601-01
Print Page