1000V port channel to N5K w/ FCOE

[jpazahanick]

Is it possible to port channel 2 10G ports on the Nexus 1000V (Emulex CNAs) with 2 10G ports on the Nexus 5000 if the ports on the Nexus 5000 ports are also doing FCOE?

I am getting the following error:

N5k(config-if-range)# int  e1/5-6
N5k(config-if-range)# channel-group 10 mode on
command failed: port not compatible [port mode]

Previously I was getting an error along the lines of "Port already assigned to virtual interface (VIF).

The configuration of the 5k is attached.

Thanks,

[Darren Ramsey]

We've been working with Qlogic and Cisco on a FCOE IOPS loss under certain conditions. When an upstream FEX PortChannel or San PortChannel membership changes (8152=>2232=>5020=>MDS) with the 5020 in NPV mode, IOPS as measured by IOMETER drop out for around 20 seconds. This is observed when the SPC either loses or adds a member, or when the FPC loses a member. This has been reproduced by both Q and Cisco under both ESX and Windows bare metal on the Q8150/2 series. You guys might want to watch out for this and push Cisco and Q for a fix. Not sure if this effects the 1000v as we use vswitch and dvswitch.

[odahlqvist]

We have an similar problem regarding LACP and portchannel  with channel mode Active-Active between an Nexus 1kV with Qlogic 8152 and VPC-HM to an upstream N5k in VPC mode, We can´t get the portchannel from the Nexus 1kV to get active/formed with with the Nexus 5kv, the LACP counters on the Nexus 1kv is telling us that we are sending LACP packet but there is no or very little response in the Nexus n5k, the Nexus n1kv sees all the LACP packet from the Nexus5k but the n5k do not se the Nexus 1kv lacp packet, so we assume those are lost between the Nexus 1kv-Qlogi 8152 card and the Nexus 5k.

We have the latest drivers frpn Qlogic .39

And the not so funny issue was that when we where investigation this issue, we ran into an VPC crash on the Nexus 5k so it went down ( made an automatic reload) the VPC crash started to bounce between the nexus5k´s, we had to remove the VPC config to stop the issue. we haven´t been able to simulate this again.