Cisco Unified Computing System Upgrade Best Practices with Payal Bhaduri

[Lisa Latour]

  Cisco subject matter expert Payal Bhaduri will focus on upgrade of Cisco UCS (Unified Computing System). With lots of companies adopting Cisco UCS, there is need to understand the UCS architecture and the complete firmware upgrade procedure which would help customers/partners to maintain and operate the UCS environment effectively.  

Ask questions from July 6, 2015 through July 17, 2015 

Payal Bhaduri is a Customer Support Engineer for Cisco's Data Center Server Virtualization TAC team based in San Jose, California. She has been working in the TAC for close to five years ,with a primary focus on Data Center Technologies such as Cisco UCS  Blade servers including the B series (UCSB), UCS Rack Mount Servers (UCSC), Cisco Nexus 1000v, and Virtualization.  She holds a Bachelors degree in Electronics and Telecommunication and has CCIE Certification (number 36570) in Collaboration and Data Center. She also holds a certification in Virtualization (VCP 5 VMware Certified Professional).

Find other  https://supportforums.cisco.com/expert-corner/events.

**Ratings Encourage Participation! **
Please be sure to rate the Answers to Questions

[Wilson Samuel]

Hi Payal,

My question is directly related to Cisco UC on UCS (C-Series Servers).

Just wondering whenever we do an in place upgrade of Cisco Unified Communications Servers (UCM, UCXN, UCCX, CER etc) from 8.0 or 8.5 or 8.6  to 9.x or 10.x what is the best process to upgrade the underlying VM?

Thanks

[Payal Bhaduri]

Hi Wilson,

For upgrading the Vmware host, you need to check with the application team to see which version is supported.

The Doc Wiki below can help you to understand the supported versions for UC with Vmware.

http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#VMware_vSphere_ESXi_Version_Support_for_Call_Processing_and_System_Management_Applications

The link below will help you with the Vmware upgrade process.

https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc_50%2FGUID-EB29D42E-7174-467C-AB40-DB37236FEAF5.html

To upgrade your UCS C series server, you can reference the following link.

http://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-c-series-rack-servers/products-installation-guides-list.html

http://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-c-series-rack-servers/products-user-guide-list.html

Thanks,

Payal

[tenaro.gusatu.novici]

Hi Payal,

can you please explain what do you mean by "adapter"? I always thought that after upgrading UCSM/IOM/FI we "only" need to apply firmware package to the blades and how you are introducing "adapter". I believe that proper screenshot could significantly improve understanding of this issue.

Thanks,

Tenaro

[Payal Bhaduri]

Hi Tenaro,

I think you are referring to Bijoy's question.

Based on the release  we are upgrading from the order of upgrade of blade can be different.

If you are upgrading from a release prior to 2.1(3a) or 2.2(1b), you may be impacted by CSCuh61202. This defect affects FC traffic on the Cisco 1240, Cisco 1280, and Cisco M81KR adapters. To avoid this situation and reduce the number of server reboots, you must first upgrade the adapter and server firmware using a host firmware package, and then proceed with the corresponding infrastructure upgrade. This is an exception to the normal upgrade procedure. For more details, refer to https:/​/​tools.cisco.com/​bugsearch/​bug/​CSCuh61202.

If you are upgrading from 1.4 to 2.2, the upgrade procedure mentions activating the adapter prior to UCS Manager as an option. I am pasting a link to that below.

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/upgrading/from1-4/to2-2/b_UpgradingCiscoUCSFrom1-4To2-2.html#concept_BDF9B17E39974D9C82637792224B76C6

If you are upgrading from release 2.1 to 2.2 and are not affected CSCuh61202, then the order that you mentioned is correct.

Let me know if you have any questions.

Regards,

Payal

[lomonaco]

Hi Payal,

My question is about the procedure to update the FI and the servers

I usually use the auto install upgrade method to upgrade first the FI (and the UCSM)

After I create a Host Firmware with the new firmware and I use it inside the service profile template.

When finally I apply the service profile to the server i update the server too.

I don't like to use the default host firmware.

I'm doing wrong ? right ? can you advise me please

thanks a lot

My Best Regards

Andre Gustavo Lomonaco

[ssumichrast]

I used to not update the default host firmware packages, until the option came out to auto update newly plugged in blades/racks to the firmware on the system. Ucs uses whatever firmware is in default for that. So since we have the auto update host firmware options on we now also update our default package. 

[Payal Bhaduri]

Hi Andre,

Using the  Auto Install procedure to upgrade the infrastructure part(UCS, FI, IOM) and using a Host firmware package with the new firmware and applying this to service profile template to upgrade the associated blades, this procedure is absolutely fine. You don't need to use the default firmware package for that.

I think you are also talking about the "Auto-Sync Server Policy" feature. With this policy, you can upgrade the firmware versions of recently discovered unassociated servers to match the firmware version defined in the default host firmware pack. For that feature to work, you need to make sure that the default Host firmware package is updated to the version you want your servers to be upgraded to.

Let me know if you still have any concerns.

Regards,

Payal

[lomonaco]

Hi Payal, thanks for your reply.

So just to clarify.

Do you recommend after update the infrastructure always update the default host firmware pack with this new version to use the Auto-Sung Server Policy ?

Thanks a lot for your help

My Best Regards

Andre Lomonaco

[Payal Bhaduri]

Hi Andre,

The "Auto-Sync Server Policy" is mainly for new blades that have been recently discovered.

You can use the Auto Install for upgrading the server. You need to be atleast on UCS version 2.1.1 to use the Auto Install method. You cannot cancel a server firmware upgrade process after you complete the configuration in the Install Server Firmware wizard. Cisco UCS Manager applies the changes immediately. However, when the actual reboot of servers occurs depends upon the maintenance policy in the service profile associated with the server.

Link for Auto Install for servers:

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/firmware-mgmt/gui/2-2/b_GUI_Firmware_Management_22/upgrading_firmware_through_auto_install.html#task_3C6EB9AEB84340D988D404245CAAA2D9

You can also do the upgrade by applying the host firmware package on the service profiles, as you are already doing.  Depending on your requirement, you can choose the method, you want to go with.

Regards,

Payal

[marktollett1]

Hi Payal,

We are getting ready to upgrade our UCS servers and CUCM from 8.6 to 10.5. Is there a single document anywhere that outlines the true steps to upgrade the EXSi and the CICM for the UCS servers? We have 3 UCS servers. It would be nice to have a high level overview of the steps involved in the correct order.There seems to be lot's of different places to go for information concerning bits and pieces. 

Thanks in advance for any info you can provide.

[Payal Bhaduri]

Hi Mark,

I am not aware of a single document that outlines the upgrade steps for ESXI and UCS firmware.

But before you do the upgrade , make sure that the ESXI version is supported with the UCS firmware.

The UCS software and hardware compatibility matrix will help you understand if the server firmware is compatible with the Vmware version.

http://www.cisco.com/c/en/us/support/servers-unified-computing/unified-computing-system/products-technical-reference-list.html

The install and upgrade guides will be helpful to upgrade the firmware on the UCS.

Link for servers integrated with UCS upgrade:

http://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-manager/products-installation-guides-list.html

Link for standalone Rack server upgrade:

http://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-c-series-rack-servers/products-installation-guides-list.html

The link below will help you with the Vmware upgrade process.

https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc_50%2FGUID-EB29D42E-7174-467C-AB40-DB37236FEAF5.html

Let me know if you have questions.

Regards,

Payal

[bantony10]

Hi Payal,

What is the best order we should follow while  activating  the endpoints (upgrading  to UCSM 2.2 (3b)) ?

Option-1

1.Activate adapters
2.Activate CIMC
3.Activate Cisco UCS Manager
4.Activate I/O modules
5.Activate subordinate fabric interconnect
6.Activate primary fabric interconnect

Option-2

1.Activating Adapter
2.Activating CIMC 
3.Activating IOM
4.Activating UCS Manager 
5.Activating Subordinate Fabric Interconnect
6. Activating Primary Fabric Interconnect

Thanks,

Bijoy

[bantony10]

Thank you Payal.

I always followed Option-I for the releases prior to 2.x but just want to make sure that order is the same with 2.1 to 2.2 release to (no changes right?)

Best Regards,

Bijoy

[Payal Bhaduri]

Hi Bijoy,

Thanks for clarifying the version.

If you are upgrading from a release prior to 2.1(3a) or 2.2(1b), you may be impacted by CSCuh61202. This defect affects FC traffic on the Cisco 1240, Cisco 1280, and Cisco M81KR adapters. To avoid this situation and reduce the number of server reboots, you must first upgrade the adapter and server firmware using a host firmware package, and then proceed with the corresponding infrastructure upgrade. This is an exception to the normal upgrade procedure. For more details, refer to https:/​/​tools.cisco.com/​bugsearch/​bug/​CSCuh61202.

Also make sure you go through the document below before you do the upgrade:

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/upgrading/from2-1/to2-2/b_UpgradingCiscoUCSFrom2-1To2-2.html#concept_964464BA5D4847B5897729A64F39F40C

Overview of the steps for upgrade from 2.1 to 2.2, if not affected by bug CSCuh61202

1. Activate Cisco UCS Manager
2. Update the I/O modules.
3.Activate the I/O modules
4. Activate the subordinate fabric interconnect. To avoid control plane disruption, manually failover the primary fabric interconnect to the fabric interconnect that has already been upgraded. Verify that the data path has been restored.
5. Activate primary fabric interconnect.

6. Update adapters and CIMC—If you prefer, you can upgrade the CIMC and the adapters in a host firmware package as part of the last upgrade step. Certain adapters must be upgraded in a host firmware package.
7.Activate adapters—Choose Ignore Compatibility Check and Set Startup Version Only when performing this step.
8. Activate CIMC—Choose Ignore Compatibility Check when performing this step.
9.Update host firmware package(s) for servers—Must be the last firmware upgraded. We recommend that you upgrade the board controller firmware during this step to avoid an additional reboot of servers with that firmware.  You can upgrade the following firmware in a host firmware package:
    •    BIOS
    •    Storage controller
    •    Adapters
    •    Cisco Integrated Management Controller (CIMC)

Cisco UCS no longer supports the creation of new management firmware packages. We recommend that you remove the management firmware packages from all service profiles and use host firmware packages to update the CIMC on the servers.

Regards,

Payal