We have discovered that sometimes UCS Server firmware doesn't always install properly. When you look at the server firmware, it displays sometimes like this;
Firmware Version 3.1(2f)C,3.2(3i)C
Now we have track some of this down to human error. When the operations team migrates service profiles within UCS Central to newer UCS Domains with Newer Firmware, they sometimes forget to update the firmware policy until after the profile has been migrated. In the example above, A service Profile that had firmware policy for 3.1(2f) was migrated to a server with 3.2(3j). This forced a downgrade of the server which did not downgrade completely. After updating the service profile the upgrade runs but doesn't upgrade completely.
The way to fix this is to upgrade the local components manually. from UCSM.
We have discovered the only role that is allowed to update server firmware locally is admin. We do not want to give the operations staff full admin rights so I was wondering if anyone else has seen this and what they have done to fix it.
Dear all,need your help to troubleshoot.when i am trying to configure up link port towards to nexus switches ( which is connect to Netapp), existing network get fluctuate and cant configure up link port. an attaching network diagram for ref. any...
Dear All,We are running an old version of the UCSM (verison 2.2(5a)) with 6248UP FIs and have a requirement to add two addtional 2xvNICs to existing blades. All blades are half size and B200 M3 with 1240 VIC. At present we have 2xvHBA and 4xvNIC (vnic 0,1...
Hi friends, We have many UCS domains, and in all of them we're using the "Grid" power policy, we take this decision why we have 2 PDUs in our datacenter (two power sources).We connect PSU1 and PSU3 in source A and PSU2 and PSU4 in source B.Recen...