I recently deployed a new UCS blade, and I was greeted with the error:
"configuration failed due to compute-unavailable,insufficient resources"
Since it was just a copy of another service profile template with different vNIC settings - I knew there was no changes otherwise. I simply disassociated the profile, waited for the blade to become available again, and reapplied the service profile...and voila! The error cleared itself and the blade became available.
Subscribe to:
Post Comments (Atom)
Featured Post
Remove 3D Objects and other annoying folders on Windows 10
Microsoft just keeps adding more crap to clutter up the navigation in Windows 10. Seriously, who needs a 3D Objects folder? The tiny perc...
-
I recently deployed a new UCS blade, and I was greeted with the error: " configuration failed due to compute-unavailable,insufficient...
-
Sometimes a VM snapshot can get corrupted. You can check for consistency by running vmkfstools against the last snapshot in the chain for a...
-
I recently starting receiving NHT health warnings on one of my filers, concerning a disk. Disk 5a.14.20 received NHT health trigger (0x1...
Our issue was UCS is at 2.0(1q) and the blades have a 1280 vic adapter, the 1280 requires minimum of 2.0(2) code.
ReplyDeleteWe rolled back to 2.0(1q) and are planning an upgrade this weekend.