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. 



Labels:

Comments

Post a Comment

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.
1 comment
Read more

BGP Local Preference Controlling Outbound Traffic in BGP

In BGP, Local Preference is used to control the outbound traffic path. It helps you decide which egress point (exit point) should be used when you have multiple connections to external networks, such as ISPs. Local Preference is an attribute that is local to your AS and is shared with all iBGP peers but not with eBGP neighbors. Higher Local Preference = More preferred outbound path. Example Scenario : You have two external links: ISP1 (via CE1) and ISP2 (via CE2). You want traffic to prefer ISP1 for all outbound traffic. 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 CE1 (Higher Local Preference) : Create a route map to set the local preference to 200 for routes learned from CE1: route-map SET_LOCAL_PREF permit 10 set local-preference 200 In the BGP configuration for CE1, apply this route map to the neighbor: router bgp 65001 ne...
Post a Comment
Read more

BGP MED: Managing Inbound Traffic with Multi-Exit Discriminator

The Multi-Exit Discriminator (MED) is used in BGP to control inbound traffic into your AS. It tells a neighboring AS which entry point into your network it should prefer when there are multiple links between your AS and the neighboring AS. The lower the MED value , the more preferred the path. MED is only honored between the same neighboring AS . Example Scenario : You are connected to ISP1 via two routers, CE1 and CE2 , and want to control which router ISP1 uses to send traffic into your AS. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP1): 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 CE1 (Lower MED, More Preferred) : Create a route map to set the MED to 50 for CE1: route-map SET_MED permit 10 set metric 50 Apply this route map to the neighbor in the BGP configuration for CE1: router bgp 65001 neighbor 10.0.1.1 remote-as 65000 neighbor 10.0.1.1 route-map SET_MED out Configuratio...
Post a Comment
Read more