04-11-2016 01:58 PM - edited 03-01-2019 12:41 PM
Hi,
It is my first UCs-B implementation
I'm now upgrading the firmware to 2.2.6e which is the latest suggested one from Cisco
I finished upgrading infrastructure firmware
Then when Trying to upgrade server firmware. I got no associated devices that the B servers was down.
Trying to boot up server not help to power the server
I think to associate the service profile is required to power up the server
But I got the attached error 1 that state configuration failure with reason is "issue for boot order, possibly vhba not found or boot target not found"
Although the service profile is having 2 vhba and boot order with 1.remote CD 2.SAN primary and secondry
After I press ok for the association error, I found the configuration boot order on the server is empty with the attached error 2 that appear in Faults tab
So please help to solve this problem and clear the above thoughts
Thanks
Solved! Go to Solution.
04-13-2016 11:00 AM
thanks Keny for your response
The issue was due to name mismatch between the vhba and boot policy
04-13-2016 08:15 AM
Try to pull KVM from UCSM and go to BIOS and set the BIOS settings to factory defaults and then try to associate the Service Profile.
Please post any errors you get if Service Profile association still fails...
-Kenny
04-13-2016 11:00 AM
thanks Keny for your response
The issue was due to name mismatch between the vhba and boot policy
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide