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.

Authoritative DNS Servers Delegation and Internal DNS Explained

DNS (Domain Name System) plays a critical role in how users and systems find resources on the internet or within internal networks. Whether it's managing an internal domain in an enterprise or delegating parts of a domain for traffic distribution, DNS setups vary widely depending on needs. In this blog post, we’ll break down the different types of DNS setups, including authoritative DNS servers, DNS delegation, and how internal DNS functions within organizations. 1. Authoritative DNS Server An Authoritative DNS server is the final source of truth for a specific domain. When someone queries a domain (e.g., example.com ), the authoritative DNS server for that domain holds the DNS records (A records, CNAME, MX, etc.) and responds with the corresponding IP address. Key Points: Who can host it? Authoritative DNS servers are often hosted by domain registrars (e.g., GoDaddy, Namecheap) or cloud DNS providers (e.g., AWS Route 53, Cloudflare). However, organizations can also host their ...

AS Path Prepending: Controlling Inbound Traffic in BGP

AS Path Prepending is a BGP feature used to make a specific path appear less preferred by artificially lengthening the AS path. This is done by adding your AS number multiple times to the AS path. It is a common method to influence inbound traffic from external networks. Longer AS Path = Less preferred route . Example Scenario : You have two ISPs: ISP1 (through CE1) and ISP2 (through CE2). You want inbound traffic from the internet to prefer ISP1 over ISP2. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP2): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE2 (AS Path Prepending to Make ISP2 Less Preferred) : Create a route map to prepend your AS path multiple times for CE2: route-map PREPEND_AS permit 10 set as-path prepend 65001 65001 65001 Apply this route map to the neighbor in the BGP configuration for CE2: router bgp 65001 neighbor 10.0.2.1 remote-as 65002 neighbor 10.0.2.1 ro...