HP Cisco Nexus 5000 Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1 - Page 8

Changes to the FCoE Model and Related Configuration Send documentation comments to [email protected] VSAN-to-VLAN Mapping In previous Cisco NX-OS 4.0(0)-based releases, FCoE had no dependence on the VLANs defined on the switch. In Release 4.0(1a)N1(1), each virtual Fibre Channel interface is associated with only one VSAN. Any VSAN with associated virtual Fibre Channel interfaces must be mapped to a dedicated FCOE-enabled VLAN as shown in the following example: switch# configure terminal switch(config)# vlan 200 switch(config-vlan)# fcoe vsan 2 switch(config-vlan)# exit switch(config)# interface ethernet 1/1 switch(config-if)# switchport mode trunk switch(config-if)# switchport trunk native vlan 1 switch(config-if)# switchport trunk allowed vlan 1,200 switch(config-if)# exit switch(config)# interface vfc 1 switch(config-if)# bind interface ethernet 1/1 switch(config-if)# exit switch(config)# vsan database switch(config-vsan)# vsan 2 interface vfc 1 Note The FCoE VLAN must be exclusively reserved for FCoE traffic; it must not be used for non-FCoE Ethernet forwarding. Example of Virtual Interface Configuration Changes Cisco NX-OS 4.0(0)-based Release Configuration interface vig 1 bind interface Ethernet 1/1 interface vethernet 1/1 switchport access vlan 2 interface vfc 1/1 no shutdown vsan database vsan 1 interface vfc 1/1 Release 4.0(1a)N1(1) Converted Configuration vlan 101 fcoe vsan 1 interface Ethernet 1/1 switchport mode trunk switchport trunk native vlan 2 switchport trunk allowed vlan 2,101 spanning-tree bpduguard enable spanning-tree port type edge trunk Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1) 8 OL-16601-01