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. 



Comments

Popular posts from this blog

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.

SSL VPN vs IPSec VPN: Understanding the Key Differences

When it comes to securing communication over the internet, Virtual Private Networks (VPNs) are a cornerstone of modern networking. Two popular types of VPNs are SSL VPN and IPSec VPN . While both serve to encrypt and secure data, they differ significantly in terms of technology, use cases, and implementation. This blog post will help you understand these differences and choose the right solution for your needs. What is SSL VPN? An SSL VPN uses the Secure Sockets Layer (SSL) or its successor, Transport Layer Security (TLS) , to create a secure connection. It operates at the Application Layer (Layer 7) of the OSI model and is designed to provide secure access to specific resources over the internet. Key Features of SSL VPN: Ease of Use: Accessible via a standard web browser without the need for dedicated client software. Granular Access Control: Allows users to access specific applications or resources rather than the entire network. Port Usage: Uses TCP port 443, which is rarely...

BGP Soft Reconfiguration vs. Route Refresh: Key Differences and Best Practices

In BGP (Border Gateway Protocol), managing route updates and reapplying new policies can sometimes be challenging, especially if you want to avoid resetting the BGP session. Two methods allow you to update routing policies without tearing down the session: BGP Soft Reconfiguration and BGP Route Refresh . While both methods serve the same purpose, they work differently and have distinct impacts on your router's resources. This post explains the key differences between Soft Reconfiguration and Route Refresh , when to use each, and why Route Refresh is preferred in most modern networks. 1. What is BGP Soft Reconfiguration? BGP Soft Reconfiguration is an older method of applying new policies (like route maps, filters, or prefix lists) without resetting the BGP session. It works by storing a local copy of all the routes received from a BGP neighbor before applying inbound policies. This local route copy allows the router to reprocess the routes when a policy change occurs. How So...