N5K running 5.0(2)N2(1) support for FCOE VSAN-trunking

Question

Hi, from 5.0(2)N2(1) on , on the N5K on a FCoE Port VSAN-trunking should be supported on VE-Port and VF-Port.
But I could not find a doc how to configure
classical configuration where I assign one VSAN to every FCoE-Port
vlan 111
name ETH_111
vlan 112
name ETH_112
vlan 113
name ETH_113
vlan 1011
name VSAN_1
fcoe vsan 1
vlan 1012
name VSAN_2
fcoe vsan 2
vlan 1013
name VSAN_3
fcoe vsan 3
vsan database
vsan 1 interface vfc 1
vsan 2 interface vfc 2
vsan 3 interface vfc 3
int vfc 1
bind interface eth 1/1
int vfc 2
bind interface eth 1/2
int vfc 3
bind interface eth 1/3
interface eth 1/1
  switchport mode trunk
  switchport trunk allowed vlan 111,1011
  spanning-tree port type edge trunk
  spanning-tree bpduguard enable
interface eth 1/2
  switchport mode trunk
  switchport trunk allowed vlan 112,1012
  spanning-tree port type edge trunk
  spanning-tree bpduguard enable
interface eth 1/3
  switchport mode trunk
  switchport trunk allowed vlan 113,1013
  spanning-tree port type edge trunk
  spanning-tree bpduguard enable
no I want to configure FCoE trunk transporting all 3 VSANs on Eth 1/4
interface vfc 4
description FCoE Uplink
bind interface eth 1/4
switchport trunk allowed vsan 1-3
interface eth 1/4
  description FCoE Uplink
  switchport mode trunk
  switchport trunk allowed vlan 1011,1012,1013
  spanning-tree port type edge trunk
  spanning-tree bpduguard enable
so I assume I do not have to configure anything additional in the VSAN-database, I saw it s only possible to assign a VFC-Interface to only one VSAN.
Does anybody have more infos about configuring VSAN-trunking on FCoE Ports ?
Thx in Advance
Hubert

Answer 1

Unless you need to keep the data separate, there is not a requirement to place each VFC interface in a different VSAN.  They can all exist in the same VSAN, and you can isolate them from each other using zoning with in the VSAN.
What are you looking to trunk the FCoE connections to?  At this point the only option is another N5K.  Eventually, there will be FCoE trunk support between the N5K, the Cisco N7K, and the MDS.
You are correct that for the trunk port, you do not need to ad any VSAN database entry.  It will reside in the default VSAN which is normally VSAN 1.
It this not working for you, or is this a planned configuration that you want to verify.
You do need to make the VFC 4 interface in your post an E port.  'switchport mode e' is the command.
Here is a snip from a working FCoE trunk port on a 5K.  It happens to use an Ethernet port channel bound to the VFC.
pod2-N5010-82# sh run interface port-channel 402
version 5.0(2)N1(1)
interface port-channel402
  switchport mode trunk
  switchport trunk allowed vlan 122,222
  speed 10000
pod2-N5010-82# sh run interface vfc 402
version 5.0(2)N1(1)
interface vfc402
  bind interface port-channel402
  switchport mode E
  switchport trunk allowed vsan 122
  switchport trunk allowed vsan add 222
  no shutdown
pod2-N5010-82# sh int vfc 402
vfc402 is trunking
    Bound interface is port-channel402
    Hardware is Virtual Fibre Channel
    Port WWN is 21:91:00:05:9b:20:a9:7f
    Peer port WWN is 00:00:00:00:00:00:00:00
    Admin port mode is E, trunk mode is on
    snmp link state traps are enabled
    Port mode is TE
    Port vsan is 1  <====
    Trunk vsans (admin allowed and active) (122,222)
    Trunk vsans (up)                       (122,222)
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             ()
HTH,
Mike