UCS Firmware Upgrade 2.1 to 2.2 with Service Profile Templates

This post is part 2 of the UCS upgrade guide.  If you use Service Profile Templates in your UCS deployments, use this quick guide to safely upgrade your servers, which is step 4 of the UCS upgrade outlined in an earlier post from Chris Murray of TechShifter.

Current Environment

We currently have one Cisco UCS system with 1 chassis, soon to be 3, filled with B200M2 blades with VMware ESXi 5.1 and 5.5.  In order to safely complete the upgrade process, which is step4, you must do the following on all servers, 1 at a time.

 

Tasks

  1. Go to vCenter and place host in maintenance mode
  2. Perform upgrades in UCS
    1. Create a new Host Firmware Package
    2. Create a Clone of the Service Profile Template
    3. Associate the Host Firmware Package with the new Service Profile Template
    4. Bind the Service Profile to the new Template
  3. Go to vCenter and exit host from maintenance mode
  4. Repeat steps 1 – 3 for every server

Let us start

Place host in maintenance mode

maint

 

 

Perform server upgrade in UCS

 

  • Right click on Host Firmware Package and Create a new Host Firmware Package

pol0

 

 

  • You can give this any name you want.  Then choose the appropriate Blade Package from the drop down list.

policy

 

 

  • Go to Servers, Service Profile Templates, click the Service Profile Template you are currently using and Create a Clone

clonetemp

 

 

  • Again, choose any name you want

newtemplate

 

 

  • Here we see that the new Service Profile Template was created

temp-1

 

 

  • Click on the Service Profile Template, then Policies, then Firmware Policies.  From the drop down list, choose the Host Firmware Package that we created earlier.  Now, your Service Profile Template is ready to used and is a clone the current template with the exception of the Host Firmware Package.

temp-pol

 

 

  • Go to Servers, Service Profile and click the server that you put in maintenance mode.  Click Bind to a Template, which is at the bottom of the screen.  It will now ask you if you want to reboot the server.

bind

 

 

  • Choose the new Service Profile Template that you created earlier from the drop down list

bind2

 

 

  • As you see, it warns you before rebooting the server.  But, since this server is in maintenance mode, we really don’t care.  So, click Yes.

warning.

 

 

  • Go to Equipment, Firmware Management, Firmware Auto Install and get a concise list of components and versions

auto

 

 

Exit host from maintenance mode

nomaint

 

Do this for every Server/Host and you will safely upgrade all of you servers

 

Permanent link to this article: https://daherlabs.mywire.org/wordpress/?p=165

3 comments

    • Amir on April 18, 2015 at 8:08 am
    • Reply

    Hi,

    If I already have an existing updating service profile template that was used to create 4 service profiles that are tied to my 4 blades, can I just do the following:

    1. Place first blade into maintnence mode
    2. Create a new Host Firmware Package with new firmware versions
    3. associate new Host Firmware Package with the existing updating Service Profile Template
    4. Then from Pending Activities, acknowledge reboot of first blade

    My real concern is, although I’ve created a maintenance policy requiring user ack, what happens to the 3 blades that are not in maintnence mode. when I modify the Updating service profile template with the new host firmware package? Does the Pending Activity window get populated with 4 alerts requiring me to ack each blade reboot

    Thank you!

    Amir

    1. Hi Amir,

      If I remember correctly, I think you would get one alert popup window which will alert you for all blades that are going to reboot.

    • Jonathan Kim on January 27, 2016 at 10:05 am
    • Reply

    Thank you. Very nice note.

Leave a Reply

Your email address will not be published.