Nexus 5548 Config - HP VirtualConnect to NPV to NPIV

[Brandon Rumer]

Hello,

I have a new HP C7000 Blade Chassis with the Virtual Connect modules installed, and have that connected to a new Nexus 5548. For this discussion, lets just focus on one side of the Fabric. The NExus 5548 is in NPV mode, and has the FCOE links (VSAN) connected to an upstream Nexus 5548 which is running NPIV mode. That upstream 5548 in NPIV mode is currently doing all the other zoning for my SANs and other C7000 chassis. I would like the 5548 in NPIV mode to do all the zoning because I did not feel a need in having both operate in NPIV mode since the SAN is only connected to one of the 5548s. I want everything to operate in the same VSAN. Picture should be attached to this post.

The VFC is up between the two 5548s, and the VSAN is showing as trunked and up on the vfc. The problem I am having is that the VFC going down to the VirtualConnect is stuck in initializing state. First thoughts would be to check to make sure that VFC is in the vsan database (it is) and to double-check the QoS (I did, and it is obviously working because the VFC to the upstream 5k works).

I have found the page below, and believe that I am trying one of the supported configs (I think).
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/san_switching/503_n2_1/Cisco_n5k_nxos_sanswitching_config_guide_rel503_n2_1_chapter6.html

Any ideas what I need to do or if I am way off on this implementation?

Thanks!!
Brandon

[Walter Dey]

Do you see the flogi of the server hba's on the NPIV node ?

[Brandon Rumer]

No.

On the NPIV switch I only see the single flogi for the physical hba on the NPV switch.

Also, 'sh fcns database' on the NPIV switch shows the device npv, which is correct.

[Walter Dey]

Is the same vsan defined on  npv and npiv, and the port connecting the virtual connect ?
 

[Brandon Rumer]

yes. The same vsan and vlan are defined on both 5548s.

[Walter Dey · Accepted solution]

Hi Brandon

While searching for a interop statement, I found this:

http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c03808925-4.pdf

FCoE Cookbook for HP Virtual Connect

Version 4.45

Firmware Enhancements

August 2015

[Brandon Rumer]

Hi Walter,

Thank you for this document. I found the 4.41 version but the 4.45 is a bit different and helps. After reading through things about a dozen times and performing outside research I think I have found the answer to my problem. The document you provided says that the VirtualConnect is only supported by Cisco when it is conected to a Nexus running FCF (NPIV, right?). I've found that nested NPV isnt supported by Cisco, even though I feel it would technically be possible. Since the Nexus running NPV isnt really the edge switch (the VirtualConnect is the edge switch) my implementation isnt supported. Any Nexus switch that is connected to a Blade Chassis (C7000 or UCS) will need to be NPIV.

Thank you for your help,

Brandon

Thank you for your help.

[Walter Dey]

Is the HP Virtual connect using classical FC to connect to NPV ? or is it FCoE ?

[Brandon Rumer]

Hi Walter,

The Virtual Connect is running 4.41 and is using FCoE as a dedicated link. I have defined the same VLAN on the VC uplink, and defined it as an FCOE link. I am assuming that since we have gotten this far into the conversation that my Nexus architecture should work... It is very possible that the problem lies with HP, but I am just not sure where to look.

Thank you for your help,

Brandon