Skip to main content

Unable to Perform Image Update on the Adapter 2 Intel Corp UCSC-PCIE-ID10GF

While applying Service Profile to newly discovered UCS Rack Servers (UCSC-220M5L)  getting this error "Unable to Perform Image Update on the Adapter 2 Intel Corp UCSC-PCIE-ID10GF". Though the servers are fully discovered without any error but when the service profile is applied it fails, as the Service profile has new firmware policy "UCS firmware Version 4.0 4h) and there is new firmware for Intel adapter cards in it. So when Service profile FSM reaches (77%) to upgrade the firmware of Intel Adapter Cards it fails every time. I have ten new rack servers and all are failing on this error.

I don't want upgrade the UCS firmware as I recently upgraded firmware from 3.1x to 4.0 4x. To avoid second UCS firmware upgrade, I tried a work around and it worked, so worth to share here:
  • Download HUU (Host Upgrade Utility) ISO from Cisco Website (HUU ISO is to upgrade firmware when you have standalone Rack Servers i.e. not integrated with UCSM. But it is completely Ok if you upgrade the Intel adapter card by using HUU)
  • Take KVM console of the UCSC Server, by directly assigning CIMC IP
  • Mount the HUU ISO "I used 4.1x HUU ISO as this ISO had the required firmware Version"
  • Upgrade only the network adapters firmware, UCSC-PCIE-ID10GF in this case.
  • Exit the HUU Utility
  • Un-mount the HUU ISO
  • Re-acknowledge the Server where you updated the firmware with HUU ISO
  • Verify the server has been discovered with new firmware Version for intel adapater cards. 
  • Apply the service profile – Applying service profile now skips the firmware update for Intel adapater cards as these cards have already the same firmware version which Service Profile will apply. 

By following above steps I have successfully applied Service Profile on all of my ten new C220M5L servers. 


Popular posts from this blog

How to check Gray-log current running version

If you planning to upgrade your graylog and want to see what your graylog current version is, here is how you can check it. Go to the Graylog Web Interface Click on System/Nodes Under System/Nodes --- Click on the N odes  Scroll down to the ' System ' Here you can see the current version of your graylog server

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.

Connection control operation failed for disk 'ide1:0'

I was getting this error while removing Operating System ISO image mounted on the Virtual Machine. What worked for me, is 1. Uncheck the "Connected and Connect at power on" from Device Status. 2. Then Change the Device type from " Datastore ISO File to Client Device " Radio Button 3. and press OK to save the changes. Note:- I was able to remove the mounted ISO only by directly logging to the ESXi at https://esxi-ip-address/ui where it asks "The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes. If possible, eject the CD-ROM from inside the guest before disconnecting. Disconnect anyway and override the lock?" You need to select yes to eject the CD-ROM and then remove the ISO file successfully.