UCS Service profile error "Not enough vNICs available"

[RomainJean]

Hi everybody,

when i finished to setup service profile i always get the same error:

Config failure

Associate state: unassociated

Assigne state: failed

Configuration error: Connection-placement
                            There are not enough resources overall
                            Not enough vNICs available

I got that error whith and without dynamique VNIC.

Is someone got an idea??

thanks

[Jeremy Waldrop]

If the profile has more than 2 vNICs and you are trying to associate the profile to a blade that doens't have Palo (UCS VIC M81KR) adapter it will fail. What adapter is in the blade and how many vNICs are defined in the service profile?

[RomainJean]

Hi Jeremy,

the profile got 2 vNICs (see attached picture) and the blade got one Cisco CNA M71KR-Q interface card.

[Jeremy Waldrop]

Maybe a hardware issue with blade you are trying to associate the profile with? Do you have another blade you can try? Go to the Equipment tab and make sure that blade has an adapter. I have seen cases where the adapter had to be reset before it was recognized.

[RomainJean]

Actually i've got an issue with the DCE

Interface 1 of that blade, it is not connected to any FabricExtender (i/o mudule) and doesn't want to, even when i reset connectivity.

Maybe a hardware failure.

Thanks

[cpaggen]

If you have a M71 adapter ("Menlo") then make sure one vnic is "routed" to Fabric A and the other to Fabric B. This is a must for Menlo. Also by looking at the picture you attached make sure you default MAC address pool contains addresses.

[RomainJean]

Hi Christopher,

• The Blade was only connected to one I/O module. I couldn't change this connection.

Regarding this arcticle, this is the reason why the SP doesn't go active: "Unified Communications Virtualization Deployment Guide On UCS B-Series Blade Servers" (https://supportforums.cisco.com/docs/DOC-6158)

"This is important to note that a service profile that has two vNICs assigned would require a blade in a chassis with two IOMs connected to two fabric interconnects, and that service profile would fail to associate to a blade in a chassis with only a single IOM"

=> I resolved it by "Acknowledge chassis" in the chassis>genérale configuration. After it, the blade was connected with 2 I/O module.

• About ServiceProfile Network Configuration.

=> I choose an expert configuration mode to add manually 2vNICS. MAC address is mapped with hardware default.

All works fine now !!

Thank you for your help.

I hope this discussion will help someone.

[vincehale]

Acknowledge chassis solved my problem, i added memory to a blade and when it came back up it had this problem.

[Samuel Glenn Kevin]

I've got Not enough vNIC & vHBA available.

but i've tried to reset IOM/FEX that some DCE are down.

and it solved my problem. now, the service profile successfully associated with server..

thanks for your suggestion.

[pauguo]

if you have Palo card with lots VNICs and still have the same issue, you might not have the enough links between IOM and FabricInterconnect, try this:

First of all you need 4 physical links between IOM and FabricIntercon.

then go to left pane -> Equipment tab -> equipment -> right pane -> policy

select "4-link"

right click on your Chassis on left pane (e.g. "chassis 1") and re-knowlege it.

error msg should go away.

[#11]

hi ALL,

new to UCS central, while configuring the service profile I am receiving following error, can one help me to understand what mistake I am doing and how to get out of this.

config Errors

- there are not enough resources overall

- the server does not permission to access the named VLAN 

-the named VLAN cannot be resolved

I have already checked pool have sufficient resource, VLAN name also looks fine,

[Suresh Ramappachari]

Hi Romain JEAN,

UCS Service profile error "Not enough vNICs available"  Please check the Network settings of the Service profile, in that check the default path for vNIC1 & vNIC2. For each of the vNIC (in this case) Fabric Interconnect path should be different (check the attachment).

Edit the settings as above and associate it later....

Thanks,

Suresh H R

[brian.ladley67]

I had this error show up for one of our servers and it turned out to be the cable which connect the VIC to the FI was not completely inserted into the VIC.  Once the cable was properly seated, the LED started blinking and I was able to associate the server with the service profile.