Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
BladeSystem Server Blades
cancel
Showing results for 
Search instead for 
Did you mean: 

After OA upgrade to 4.50, some of my VC's can no longer communicate with the OA

Kevin_Tunge
Occasional Contributor

After OA upgrade to 4.50, some of my VC's can no longer communicate with the OA

Hey all,

Seeing if anyone else has had this problem and/or found the solution- after the latest upgrade of OA firmware 4.50(completed last week), it seems some(not all) of my VC's can no longer communicate with their enclosure's OA's. This results in the status on the VC's going Orange, and I am no longer able to assign server profiles to slots. So far this has not caused any interruption. The very maddening part of this is that there is a button to re-enter the OA credentials into the VC. It asks for the OA IP, user name and pw- pretty standard. I can see in the logs on the OA that the login takes place from the VC. However, the VC still remains clueless. Anyone else run across this?

So my OA's are running 4.50(successful upgrades to both OA's), and my VC's are running 4.31.