Share:

Replies

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?

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.

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.

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

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).