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

VSAN-to-VLAN Mapping, Example of Virtual Interface Configuration Changes

Page 9 highlights

Changes to the FCoE Model and Related Configuration Send documentation comments to [email protected] Each virtual Fibre Channel interface is bound directly to an FCoE-enabled physical Ethernet interface in Release 4.0(1a)N1(1a). This change simplifies the interface vfc command as shown in the following example: switch# configure terminal switch(config)# interface vfc 1 switch(config-if)# bind interface ethernet 1/1 The Ethernet interface that you bind the virtual Fibre Channel interface to must be configured as follows: • It must be a trunk port (use the switchport mode trunk command). • The FCoE VLAN that corresponds to virtual Fibre Channel's VSAN must be in the allowed VLAN list. • FCoE VLAN must not be configured as the native VLAN of the trunk port. • The Ethernet interface must be configured as PortFast (use the spanning-tree port type edge trunk command). 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(1a), 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 OL-16601-01 Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a) 9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26

Send documentation comments to [email protected]
9
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
OL-16601-01
Changes to the FCoE Model and Related Configuration
Each virtual Fibre Channel interface is bound directly to an FCoE-enabled physical Ethernet interface
in Release 4.0(1a)N1(1a). This change simplifies the
interface vfc
command as shown in the following
example:
switch#
configure terminal
switch(config)#
interface vfc 1
switch(config-if)#
bind interface ethernet 1/1
The Ethernet interface that you bind the virtual Fibre Channel interface to must be configured as follows:
It must be a trunk port (use the
switchport mode trunk
command).
The FCoE VLAN that corresponds to virtual Fibre Channel’s VSAN must be in the allowed VLAN
list.
FCoE VLAN must not be configured as the native VLAN of the trunk port.
The Ethernet interface must be configured as PortFast (use the
spanning-tree port type edge trunk
command).
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(1a), 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