Adding VLAN to vNIC template gives non-fatal warning about no uplink with all VLANs

[jkeglovitz]

We are trying to add a new VLAN to an existing vNIC template. When I select the checkbox for the VLAN under Modify VLANS I get:

Your changes:

Create: [new VLAN]

Will cause a non fatal configuration warning for:

Service Profile [profile name]

Reason: Failed to find any operational uplink port that carries all vlans of the vNIC(s). The vNIC(s) will be shut down which we lead to traffic disruption on all existing VLANs on the vNIC(s).

We currently have VLANs assigned to the template, some of which are carried by a port channel to our production switch, the rest are carried by an Ethernet interface to our perimeter switch.

Does this error occur because neither interface/PC carries all the assigned VLANs on its own?

Am I missing something?

Thank you for any assistance.

Joe

[Saurabh Kothari]

Hey Joe,

Is this a disjoint L2 setup?

Probably you will have to bind those vlans to the uplink.

[Manuel Velasco · Accepted solution]

Hi

Even thought you have a port channel and a separate Ethernet uplink carrying all the vlans that servers required, your vnic will only be pinned to either the port-channel or the Ethernet uplink never to both, so if your vnic is currently pinned to the port-channel and the new vlan is assigned to the Ethernet interface you will be see this error message. To fix this problem you need to make sure the uplink that your vnic is pinned is carrying all the vlans you want.  See doc below

Disjoin layer 2

http://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/unified-computing/white_paper_c11-692008.html

[jkeglovitz]

We actually opened a TAC and Cisco support had us send in our vNIC template, VLANs list, etc. Somehow we have a working (unsupported) configuration with two different sets of VLANs working on our existing vNICs over two uplinks. Cisco has no idea how that's working but that's why we can't add new VLANs to the templates. We're currently in the process of creating new templates to separate the vNICs.

Thank you for your help.