Configuring Virtual Interfaces; Mapping A Vsan To A Vlan - Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual

Mapping a VSAN to a VLAN

• Each virtual Fibre Channel interface is associated with only one VSAN.
• You must map any VSAN with associated virtual Fibre Channel interfaces to a dedicated FCOE-enabled
• FCoE is not supported on private VLANs.
• If the converged access switches (in the same SAN fabric or in another) need to be connected to each
• You must use separate FCoE VLANs for FCoE in SAN-A and SAN-B fabrics.
• FCoE connectivity to pre-FIP CNAs over virtual port channels (vPCs) is not supported.
Virtual interfaces are created with the administrative state set to down. You must explicitly configure the
Note
administrative state to bring the virtual interface into operation.

Configuring Virtual Interfaces

Mapping a VSAN to a VLAN
A unique, dedicated VLAN must be configured at every converged access switch to carry traffic for each
Virtual Fabric (VSAN) in the SAN (for example, VLAN 1002 for VSAN 1, VLAN 1003 for VSAN 2, and
so on). If MST is enabled, a separate MST instance must be used for FCoE VLANs.
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
412
◦ The Ethernet or EtherChannel interface must be a trunk port (use the switchport mode trunk
command).
◦ The FCoE VLAN that corresponds to a virtual Fibre Channel's VSAN must be in the allowed
VLAN list.
◦ You must not configure an FCoE VLAN as the native VLAN of the trunk port.
The native VLAN is the default VLAN on a trunk. Any untagged frames transit the
Note
trunk as native VLAN traffic.
◦ You should use an FCoE VLAN only for FCoE.
◦ Do not use the default VLAN, VLAN1, as an FCoE VLAN.
◦ You must configure the Ethernet interface as PortFast (use the spanning-tree port type edge
trunk command).
Note You are not required to configure trunking on the server interface even if the switch
interface is configured with trunking enabled. All non-FCoE traffic from the server will
be passed on the native VLAN.
VLAN.
other over Ethernet links for a LAN alternate path, then you must explicitly configure such links to
exclude all FCoE VLANs from membership.
Configuring Virtual Interfaces
OL-16597-01