<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>Cisco UCS Firmware Update &#8211; AgileOps</title>
	<atom:link href="https://agileops.co.uk/tag/cisco-ucs-firmware-update/feed/" rel="self" type="application/rss+xml" />
	<link>https://agileops.co.uk</link>
	<description>Virtualization made simple for Everyone.</description>
	<lastBuildDate>Wed, 03 Sep 2014 20:50:01 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.5.8</generator>

<image>
	<url>https://agileops.co.uk/wp-content/uploads/2017/10/favicon-01-50x50.png</url>
	<title>Cisco UCS Firmware Update &#8211; AgileOps</title>
	<link>https://agileops.co.uk</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">194680508</site>	<item>
		<title>Cisco UCS Firmware Overview</title>
		<link>https://agileops.co.uk/cisco-ucs-firmware-overview/</link>
					<comments>https://agileops.co.uk/cisco-ucs-firmware-overview/#respond</comments>
		
		<dc:creator><![CDATA[Ibrahim Quraishi]]></dc:creator>
		<pubDate>Wed, 03 Sep 2014 20:50:01 +0000</pubDate>
				<category><![CDATA[CISCO UCS]]></category>
		<category><![CDATA[CISCO UCS Firmware Upgrade]]></category>
		<category><![CDATA[Cisco UCS FlexFlash]]></category>
		<category><![CDATA[Cisco UCS M3 Blades]]></category>
		<category><![CDATA[cisco ucs sd card]]></category>
		<category><![CDATA[CISCO UCS Unified Computing System]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[CISCO]]></category>
		<category><![CDATA[Cisco UCS Firmware Process]]></category>
		<category><![CDATA[Cisco UCS Firmware Update]]></category>
		<category><![CDATA[Firmware]]></category>
		<guid isPermaLink="false">https://quraishi.wordpress.com/?p=819</guid>

					<description><![CDATA[
				<![CDATA[]]>		]]></description>
										<content:encoded><![CDATA[<div class="vgblk-rw-wrapper limit-wrapper">
				<![CDATA[Hello Everyone,

Cisco has recently launched a lot of  Firmware for CISCO UCS, it is becoming rather hard to keep up with the new release. We had 5 New Release in Version 2.2 starting from 2.2.(1b),  2.2.(1c), 2.2.(1d),  2.2.(1e), 2.2.(2c).

The good thing is, in every release CISCO  is adding some good features. In one of  the release 2.2.(1d) they have introduced boot from SD, FlexFlash, this option was not available on the older versions of  UCS Manager.

If you are intreasted in this, and want to find how you can boot the ESXi or any other OS off the Secure Digital (SD)  FlexFlash  and how this can be implemented do check  my post  here: <a href="https://quraishi.wordpress.com/2014/08/21/cisco-ucs-flexflash-configuration-of-secure-digital-sd-card/" rel="bookmark">Cisco UCS FlexFlash Configuration of Secure Digital (SD) Card</a>

So, for the newbee  to Cisco UCS,  its confusing about the firmware. In this post I am trying to clarify few aspects of this, feel free to post comment below if you have any questions and I will get back to you.

The CISCO UCS firmware is bundled into two packages as given below:

<a href="httpss://ibrahimquraishi.com/wp-content/uploads/2014/09/ucs_firmware-1.png"><img fetchpriority="high" decoding="async" class="alignright size-full wp-image-820" src="httpss://ibrahimquraishi.com/wp-content/uploads/2014/09/ucs_firmware-1.png" alt="ucs_firmware" width="604" height="284" /></a>

&nbsp;

<strong>1. Infrastructure Firmware</strong>

In Infrastructure Software firmware we update the firmware of the following


<ul>
	

<li>Cisco UCS Manager software</li>


	

<li> Kernel and system firmware for the fabric interconnects</li>


	

<li> I/O module firmware</li>


</ul>


<strong>2. Server Firmware</strong>

Cisco UCS <strong>B-Series Blade Server</strong> Software Bundle


<ul>
	

<li>CIMC firmware</li>


	

<li>BIOS firmware</li>


	

<li>Adapter firmware</li>


	

<li>Board controller firmware</li>


	

<li>Third-party firmware images required by the new server</li>


</ul>


<em><span class="uicontrol">This also includes the firmware of Adapter, </span>BIOS<span class="uicontrol">, </span>FC Adapters,  <span class="uicontrol">HBA Option ROM, </span>Storage, Controller, Local Disk</em>

Cisco UCS <strong>C-Series Rack-Mount UCS-Managed Server</strong> Software


<ul>
	

<li>CIMC firmware</li>


	

<li>BIOS firmware</li>


	

<li>Adapter firmware</li>


	

<li>Board controller firmware</li>


	

<li>Third-party firmware images required by the new server</li>


</ul>


As most of you might be aware the UCS manager is the GUI Java based which allows you to fully manage the CISCO Unified Computing System.

<em>Note I have noticed that the Java version  7 update 40 is only compatible with the UCS Manager. </em>

So, where does the UCS Manager run ?

This was one of my first questions, Well the Software of the UCS Manager runs on the FI ( Fabric Interconnect 62xx) as we have a pair of Fabric Interconnect it has got resilience.

The UCS System is designed to be highly scalable and available, so upgrading the firmware should not bring any outage to the environment. However Cisco still suggests to arrange a Change windows and get this done out of hours or the quite period of your business.

This UCS Manager is bundled in the Infrastructure Firmware Software along with the Kernal update of the FI which is the NXOS, Finally we have the I/O Module firmware which is a part of the Infrastructure firmware software too.

The Other Bundle is the Server Firmware which has the firmware for BIOS, the Blades, Adapter, Board controller etc.

If you want to learn more about the process of doing a Firmware update please checkout my link <a href="https://quraishi.wordpress.com/2014/09/02/cisco-ucs-firmware-update-process/" rel="bookmark">CISCO UCS Firmware Update Process</a>

Hope this information is useful, feel free to comment.]]&gt;		</div>
<p><!-- .vgblk-rw-wrapper --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://agileops.co.uk/cisco-ucs-firmware-overview/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">819</post-id>	</item>
		<item>
		<title>CISCO UCS Firmware Update Process</title>
		<link>https://agileops.co.uk/cisco-ucs-firmware-update-process/</link>
					<comments>https://agileops.co.uk/cisco-ucs-firmware-update-process/#comments</comments>
		
		<dc:creator><![CDATA[Ibrahim Quraishi]]></dc:creator>
		<pubDate>Tue, 02 Sep 2014 15:56:25 +0000</pubDate>
				<category><![CDATA[CISCO UCS Firmware Upgrade]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[B200 M3 Server]]></category>
		<category><![CDATA[CISCO UCS B200 Blade]]></category>
		<category><![CDATA[Cisco UCS Firmware Update]]></category>
		<category><![CDATA[Firmware update]]></category>
		<guid isPermaLink="false">https://quraishi.wordpress.com/?p=807</guid>

					<description><![CDATA[
				<![CDATA[]]>		]]></description>
										<content:encoded><![CDATA[<div class="vgblk-rw-wrapper limit-wrapper">
				<![CDATA[Hi All,

Recently Cisco has released yet another release of the Cisco UCS firmware version 3.0.

This version of firmware is for 6324 Fabric Interconnect and  B200 M3, C220 M3, and C240 M3 servers.<a href="httpss://ibrahimquraishi.com/wp-content/uploads/2014/09/updatestarted-1.png"><img decoding="async" class="size-full wp-image-817 alignleft" src="httpss://ibrahimquraishi.com/wp-content/uploads/2014/09/updatestarted-1.png" alt="updatestarted" width="314" height="164" /></a>

This is released on 24-JUL-2014, you can find more details on the release notes for this firmware version:

https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/ucs_3_0_rn.html#pgfId-225587

Just to give everyone an idea there are two from of Firmware that needs to be updated on UCS system

<span style="text-decoration:underline;"><strong>1. Infrastructure Firmware</strong></span>

In Infrastructure Software firmware we update the firmware of the following


<ul>
	

<li>Cisco UCS Manager software</li>


	

<li> Kernel and system firmware for the fabric interconnects</li>


	

<li> I/O module firmware</li>


</ul>


<span style="text-decoration:underline;"><strong>2. Server Firmware</strong></span>

Cisco UCS <strong>B-Series Blade Server</strong> Software Bundle


<ul>
	

<li>CIMC firmware</li>


	

<li>BIOS firmware</li>


	

<li>Adapter firmware</li>


	

<li>Board controller firmware</li>


	

<li>Third-party firmware images required by the new server</li>


</ul>


<em><span class="uicontrol">This also includes the firmware of Adapter, </span>BIOS<span class="uicontrol">, </span>FC Adapters,  <span class="uicontrol">HBA Option ROM, </span>Storage, Controller, Local Disk</em>

Cisco UCS <strong>C-Series Rack-Mount UCS-Managed Server</strong> Software BundleCIMC firmware


<ul>
	

<li>BIOS firmware</li>


	

<li>Adapter firmware</li>


	

<li>Board controller firmware</li>


	

<li>Third-party firmware images required by the new server</li>


</ul>


So,  without wasting any time these are the steps to follow:

Step One


<ol>
	

<li>Create an all Configuration Backup</li>


	

<li>Verifying HA status of Fabric Interconnects ( as we do not have any compute it should not affect us in anyway)</li>


	

<li>Verifying the status of I/O Modules</li>


	

<li>Verifying the Status of the Servers and Adaptors</li>


	

<li>Download Firmware Images to the Fabric Interconnect.</li>


</ol>


&nbsp;

Step Two


<ol>
	

<li>Disable the Call Home ( Email alerts for reboot)</li>


	

<li>Updating the Firmware on the Adapters, CIMCs and IOMs</li>


</ol>


<em> </em>

<em>If the Service profiles are configured using host/management firmware policy this will create an error and we might need to think of Plan B (If we do not get any error message we can progress with upgrade)</em>

&nbsp;


<ol start="3">
	

<li>Activating the Firmware on the Adapters</li>


	

<li>Activating the Firmware on the CIMCs</li>


	

<li>Activating the Board Controller Firmware</li>


	

<li>Activating the I/O Modules</li>


	

<li>Activating the Subordinate Fabric Interconnect Firmware</li>


	

<li>Making the primary FI the Subordinate by login to FI ssh to the primary and to make it subordinate first check</li>


</ol>


<strong><span style="color:#ff0000;"># connect local-mgmt</span></strong>

&nbsp;

<span style="color:#ff0000;"><strong>FI-01-A(local-mgmt)# show cluster extended-state</strong></span>

<em>Cluster Id: xxxxxxxxxxxxxxxxxxxxxxxx</em>

<em> </em>

<em>Start time: Mon Jun 23 14:41:56 2014</em>

<em>Last election time: Tue Oct  7 11:54:01 2014</em>

<em> </em>

<em><span style="color:#ff0000;">A: UP, SUBORDINATE</span></em>

<em><span style="color:#ff0000;">B: UP, PRIMARY</span></em>

<em> </em>

<em>A: memb state UP, lead state SUBORDINATE, mgmt services state: UP</em>

<em>B: memb state UP, lead state PRIMARY, mgmt services state: UP</em>

<em>   heartbeat state PRIMARY_OK</em>

<em> </em>

<em>INTERNAL NETWORK INTERFACES:</em>

<em>eth1, UP</em>

<em>eth2, UP</em>

<em> </em>

<em>HA READY</em>

<em>Detailed state of the device selected for HA storage:</em>

<em>Chassis 1, serial: xxxxx, state: active</em>

<em>Chassis 2, serial: xxxxx, state: active</em>

<em>Chassis 3, serial: xxxxx, state: active</em>

&nbsp;

In my case as shown above FI B is the Primary so I can connect t0 FI B with hte below command .

&nbsp;

<span style="color:#ff0000;"><strong>FI-01-A(local-mgmt)# connect local-mgmt B</strong></span>

<strong><span style="color:#ff0000;"># cluster lead A</span></strong>


<ol start="9">
	

<li>Activating the Primary Fabric Interconnect Firmware</li>


</ol>


&nbsp;

Step Three


<ol>
	

<li>Listing the BIOS Upgrade Versions</li>


	

<li>Create a Host Firmware Package</li>


	

<li>Applying the Host Firmware Package</li>


	

<li>Enabling Call Home.</li>


</ol>


&nbsp;

Additional Notes

&nbsp;

<strong>Prerequisite for Firmware update</strong>

<strong> </strong>https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/upgrading/from2-0/to2-0MR/b_UpgradingCiscoUCSFrom2-0To2-0MR/b_UpgradingCiscoUCSFrom1-4To2-0_chapter_010.html#concept_DD68485034FB4E258D5827880D37225C


<div>

<strong>Process of Upgrading and Activating the Firmware</strong>

https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/upgrading/from2-0/to2-0MR/b_UpgradingCiscoUCSFrom2-0To2-0MR/b_UpgradingCiscoUCSFrom1-4To2-0_chapter_0100.html#task_F1119EB4EDBA42578ADE662462B5C4CE

<strong>UCS Firmware deep dive</strong>

https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/firmware-mgmt/gui/2-1/b_GUI_Firmware_Management_21/b_GUI_Firmware_Management_21_chapter_0100.html#concept_2474DE9D2048450CA1A37A8A3D3EE597

&nbsp;


<div>

You can also find the process of upgrading on this youtube video  httpss://www.youtube.com/watch?v=b6LQt2DYVWA

its broken down into 3 steps.

</div>


</div>

]]&gt;		</div>
<p><!-- .vgblk-rw-wrapper --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://agileops.co.uk/cisco-ucs-firmware-update-process/feed/</wfw:commentRss>
			<slash:comments>7</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">807</post-id>	</item>
	</channel>
</rss>
