Thank you, I had already read this document before I posted the question.  They do not answer the question I am asking. In particular this line here makes me think that N5K vpc to a CNA equipped server is not possible since you need to use unique VLANs on each 5K to accomodate the VSAN.

"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"

I'm ok with using VPC-HM if the answer comes back as my scenario not being supported, however it makes me wonder why I even implemented vpc on the 5K's in the first place.

I'd love to hear if anyone has gotten this to work and how.

Thanks

Yes, my setup is exactly as you described, and my concerns are exactly the same as yours

I don't see how this will work with anything other than VPC-HM.

I'll post back if I find anything out.

This is the sample configuration for FCOE over VPC. This toplogy has two seperate path to MDS switches. So I used the seperate vsan and fcoe vlan for each switch. Fcoe vlan is local specific but it has to be defined both N5K same since VPC is doing consistency check.

Then N1K side is just port-channel auto mode on uplink port-profile. However, VPC-HM mac-pining is easy to configure and workes good. However, if you have multicast application then port-channel with N5K is better choice.

##Nexus 5k-01
vlan 25,100,200
vsan database
vsan 100
vsan 200

vlan 100
fcoe vsan 100
vlan 200
fcoe vsan 200

interface vfc4
  bind interface port-channel38
  no shutdown

vsan database
  vsan 200 interface vfc4

interface Ethernet1/4
  switchport mode trunk
  switchport trunk allowed vlan 1,25,100,200
  spanning-tree port type edge trunk
  channel-group 38

interface Ethernet1/19
  switchport mode trunk
  channel-group 1 mode active

interface Ethernet1/20
  switchport mode trunk
  channel-group 1 mode active

interface port-channel1
  switchport mode trunk
  vpc peer-link
  switchport trunk allowed vlan 1,25
  spanning-tree port type network
  speed 10000

interface port-channel38
  switchport mode trunk
switchport trunk allowed vlan 1,25,100,200
  vpc 38
  spanning-tree port type edge trunk
  speed 10000

##Nexus 5k-02

vlan 25,100,200
vsan database
vsan 100
vsan 200

vlan 100
fcoe vsan 100
vlan 200
fcoe vsan 200

interface vfc38
  bind interface port-channel38
  no shutdown

vsan database
  vsan 100 interface vfc38

interface Ethernet1/38
  switchport mode trunk
  switchport trunk allowed vlan 1,25,100,200
  spanning-tree port type edge trunk
  channel-group 38

interface port-channel38
switchport mode trunk
   switchport trunk allowed vlan 1,25,100,200
  spanning-tree port type edge trunk
  vpc 38
  speed 10000

  interface Ethernet1/19
  switchport mode trunk
  channel-group 1 mode active

interface Ethernet1/20
  switchport mode trunk
  channel-group 1 mode active

interface port-channel1
  switchport mode trunk
  vpc peer-link
  switchport trunk allowed vlan 1,25
  spanning-tree port type network
  speed 10000

what about your VLAN 25, is that your data/management VLAN traversing the peer link? If you are not specifying the FCoE VLANs on the peer link, the vpc consistency check should be ok, but I assume if you have any other regular VLANs configured in the N5K for any reason, you will always have to update the peer link with those additional VLANs along with 1, 25.

Vlan 25 is your data vlan and yes, you need to update if there is more data vlans defined.

Hello all,

I have a question regarding a similar set up.

I have a Server (Windows 2008 with Dual port QLogic CNAs) connected to 2 Nexus (Nexus-1 and Nexus2)

QLogic CNAs -> Model         : QLE8152

port 1 of the CAN connects to port eth1/1 on Nexus-1. Port 2 of the CNA connects to port eth1/1 of the Nexus-2

Ports eth19-20 on both Nexus are in portchannel 1 which also has the vpc peer-link.

I tried to use the above configuration to create a port-channel to the CNAs. What I did was the following:

Nexus-1

vpc domain 1
  role priority 100
  peer-keepalive destination 172.16.1.231

vlan 1
vlan 100
  fcoe vsan 1
  name SAN1_FCOE

interface port-channel1
  switchport mode trunk
  switchport trunk allowed vlan 1
  vpc peer-link
  spanning-tree port type network

interface port-channel10
  switchport mode trunk
  switchport trunk allowed vlan 1,100
  spanning-tree port type edge trunk

  vpc 10
  speed 10000

interface vfc101
  bind interface port-channel10
  no shutdown

interface Ethernet1/1
  switchport mode trunk
  switchport trunk allowed vlan 1,100
  spanning-tree port type edge trunk
  channel-group 10

Nexus-2

vpc domain 1
  role priority 200
  peer-keepalive destination 172.16.1.230

vlan 1
vlan 200
  fcoe vsan 1
  name FABRIC2_FCoE

interface port-channel1
  switchport mode trunk
  switchport trunk allowed vlan 1
  vpc peer-link
  spanning-tree port type network

interface port-channel10
  switchport mode trunk
  switchport trunk allowed vlan 1,200
  spanning-tree port type edge trunk

  vpc 10
  speed 10000

interface vfc201
  bind interface port-channel10
  no shutdown

interface Ethernet1/1
  switchport mode trunk
  switchport trunk allowed vlan 1,200
  spanning-tree port type edge trunk
  channel-group 10

Ok so the vPC comes up but I can't ping the host (The host is configured with NIC Teaming - fail over but I wanted Load Balance),

As soon as I just remove the vpc 10 statement from the Port-Channel10 (int po10 ... no vpc 10) it is OK

When I was configuring it it gave me a Warning to check some compatibility (I ignored and to be honest I couldn't reproduce again unfortunately ... and I dont know where that line log went)

Is the CNA not compatible ?I have updated everything to above the versions stated in this document

http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/white_paper_c11-569320_v1.pdf

Is this not supported on this CNA ?

Thanks

Nuno Ferreira