Upgrade BIOS on Cisco UCS Server Blade

ntroduction

In order to upgrade the BIOS on a Server Blade or a Server Pool, you complete five major steps:

1. Verify/confirm that the correct BIOS is present in the fabric interconnect flash.
   
2. Create a Host Firmware Package policy.
   
3. Associate the Host Firmware Package policy with a Service Profile.
   
4. Associate the Service Profile with the server blade or server pool.
   
5. Verify the BIOS version of the blade matches the BIOS for the Host Firmware Package policy.
   

This tech note addresses how to upgrade the BIOS on a Server Blade or a Server Pool with one of these methods:

• Cisco UCS Manager GUI
  
• Cisco UCS Manager CLI
  

Note: You cannot update the BIOS firmware directly. You must perform the BIOS firmware update through a host firmware package in a service profile. If the BIOS fails, it can recover and boot from the ISO image that is shipped with the server.

Prerequisites

Requirements

Cisco recommends that you:

• Have a working knowledge of Cisco UCS Server Blade software and hardware.
  
• Be familiar with the UCS manager GUI.
  
• Understand the impact and implications of the different commands described in this document
  
• Be familiar with the UCS components and topology. Refer to the diagram for a typical solution
  

Components Used

The information in this document is based on Cisco UCS.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Network Diagram

A typical Cisco UCS topology looks something like this:

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Background Information

The Host Firmware Package enables you to specify firmware versions for different components and bundle them together under one policy. The host firmware includes these server and adapter components:

• BIOS
  
• SAS controller
  
• Emulex Option ROM
  
• Emulex firmware
  
• QLogic option ROM
  
• Adapter firmware
  

In order to upgrade the BIOS on a server blade or a server pool, you must create a Host Firmware that has these components, and then push it to all servers associated with Service Profiles that include this policy.
This Host Firmware Package policy ensures that the host firmware is identical on all servers associated with service profiles that use the same policy. Therefore, if you move the service profile from one server to another, the firmware versions are maintained.
You must include this Host Firmware Package policy in a service profile, and that service profile must be associated with a server for it to take effect.
If you associate a new Host Firmware Package policy to a Service Profile currently linked to blades, it causes those blades to reboot. You must decide if you want to disassociate the service profile before the new firmware package policy is applied.
If a server blade is currently associated with a Service Profile, you can choose to disassociate the blade before the BIOS upgrade is performed. Complete these steps:

1. In the Navigation pane, click the Servers tab.
   
2. In the Servers tab, expand Servers > Service Profiles.
   
3. Expand the node for the organization that contains the service profile that you want to disassociate from a server or server pool. If the system does not include multi-tenancy, expand the root node.
   
4. On the service profile that you want to disassociate with a server, and select Disassociate Service Profile.
   
5. In the Disassociate Service Profile dialog box, click Yes in order to confirm that you want to disassociate the service profile.
   
6. Click OK. If desired, monitor the status and FSM for the server to confirm that the disassociation completes.
   
   

Main Task

Task

These sections detail the processes used to upgrade BIOS on a server blade or a server pool through the GUI and CLI.

1. Upgrade BIOS on a UCS Server Blade with the GUI

Complete these steps:

1. Verify/confirm that the correct BIOS is present in the fabric interconnect flash.
   
2. Create the Host Firmware Package policy with the desired BIOS version:
   
   1. In the Navigation pane, select the Servers tab.
      
   2. On the Servers tab, expand Servers >Policies.
      
   3. Expand the node for the organization where you want to create the policy. If the system does not include multi-tenancy, expand the root node.
      
   4. Right-click Host Firmware Packages, and select Create Host Firmware Package.
      
      
   5. In the Create Host Firmware Package dialog box, enter a unique name and description for the package. This name can be between one and 16 alphanumeric characters. You cannot use spaces or any special characters, and you cannot change this name once the object is saved.
      
   6. Click the down arrows in order to expand one or more of these sections on the left of the dialog box, and select BIOS Firmware Packages.
      
      
   7. When you have added all of the desired firmware to the package, click OK.
      
   8. Double click to select the BIOS Firmware. Click OK in order to confirm that the host firmware package policy is created.
      
      
3. Associate the created Host Firmware Package policy to a Service Profile.
   This association automatically updates and activates the firmware in the server and adapter with the new versions and reboots the server. Complete these steps:
   
   1. In the Navigation pane, click the Servers tab.
      
   2. On the Servers tab, expand Service Profiles.
      
   3. Select the desired Service Profile.
      
   4. On the right pane, click the Policies tab of the selected Service Profile.
      
   5. Extend the Firmware Policies drop down container and select the previously created Host Firmware Package from the Host Firmware menu.
      
   6. Save the changes.
      Note: If your Service Profile is currently associated with a server, this change causes an immediate server reboot with the BIOS installation. If your Service Profile is not associated with a server, apply it to a blade in order for the BIOS upgrade to take effect.
      
      
4. Associate the Service Profile with a server blade or server pool:
   After the Host Firmware Package policy is assigned and saved, associate this policy to the Service Profile used by the blade server and, monitor the KVM output to see the new BIOS get displayed. The BIOS upgrade should not extend the blade's boot time.
   
   1. Click the General tab.
      
   2. Click Change Service Profile Association.
      
      
   3. In the Associate Service Profile window, select the appropriate server or server pool, and click OK in order to push new BIOS to the server.
      
      
5. Verify the BIOS version of the blade matches the BIOS for the Host Firmware Package policy.
   
   

2. Upgrade BIOS on a UCS Server Blade with the CLI

!--- STEP 1. Verify/confirm that the correct BIOS is present in the !--- fabric interconnect flash F340-31-17-FI-A# F340-31-17-FI-A# scope firmware F340-31-17-FI-A /firmware # show image | include Bios Server Bios S5500.86B.01.00.0036-105.042920090209 Server Bios S5500.86B.01.00.0036-132.051320090429 Server Bios S5500.86B.01.00.0036-132.051320090429 Server Bios S5500.86B.01.00.0036-191.061320091126 F340-31-17-FI-A /firmware # !--- STEP 2. Create a Firmware Host Package policy F340-31-17-FI-A# scope org / F340-31-17-FI-A /org # create fw-host-pack bios-upgrade F340-31-17-FI-A /org/fw-host-pack* # create pack-image "Intel" S5500.86B.01.00.0036-191.061320091126 server-bios F340-31-17-FI-A /org/fw-host-pack/pack-image* # commit-buffer !--- STEP 3. Associate Host Firmware Package !--- policy with Service Profile !--- STEP 4. Associate Service Profile with a blade !--- to have BIOS updated. F340-31-17-FI-A* # scope org / F340-31-17-FI-A /org* # scope service-profile jdewberr-c2s1 F340-31-17-FI-A /org/service-profile* # associate server 2/1 F340-31-17-FI-A /org/service-profile* # commit-buffer F340-31-17-FI-A /org/service-profile* # show assoc Service Profile Name Association Server Server Pool -------------------- -------------- ------ ----------- jdewberr-c2s1 Associated 2/1 F340-31-17-FI-A /org/service-profile* # !--- STEP 5. When association is completed, !--- check current BIOS version F340-31-17-FI-A* # F340-31-17-FI-A* # F340-31-17-FI-A* # scope server 2/1 F340-31-17-FI-A /chassis/server* # F340-31-17-FI-A /chassis/server* # show bios Bios Firmware: Server Model Vendor Running-Vers ------- ---------- ----------------- ------------ 2/1 N20-B6620-1 Intel Corp. S5500.86B.01.00.0036-191.061320091126 F340-31-17-FI-A /chassis/server* #

Verify

There is currently no verification procedure available for this configuration.

Read More

Cisco UCS Firmware Versioning

Introduction

This document explains how to interpret UCS firmware version information and identify components of the UCS firmware.
The Cisco UCS firmware is delivered in these ways:

• The UCS images are shipped as a single bundle or as individual component images, which include the UCS Manager, UCS Fabric Interconnect, IO module, BMC, BIOS, adapter, etc.
  
• The UCS firmware is hosted on the Cisco Software Delivery System.
  
• UCS Manager unpacks the bundle and updates the image catalog stored on the switch.
  
• The UCS Manager maintains a catalog of all the component images stored on the switch.
  
• Only one version of each component is shipped in any bundle. Component images for multiple hardware platforms with UCS are included in the same bundle.
  
• Each component image is versioned and customer visible. You can upgrade each component image separately, provided that it is compatible.
  

The UCS firmware comes in two ways, either in a bundle or in individual images:

• Bundle:
  
  • The bundle includes a package for each component that requires firmware.
    
  • Currently there are three bundles to track:
    
    • .bin—normal bundle
      
    • .gbin—bundle with debug information; engineering instructed only
      
    • dplug—dplug file that allows root access to the NX-OS; engineering instructed only
      
• Individual images
  

Prerequisites

Requirements

Cisco recommends that you have a working knowledge of these:

• The Cisco UCS Server Blade software and hardware
  
• The UCS Manager
  
• The impact and implications of the different commands described in this document
  
• The UCS components and topology; refer to the network diagram for a typical solution.
  

Ensure that you meet these requirements before you attempt this configuration:

Components Used

The information in this document is based on Cisco UCS.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a default configuration. If your network is live, make sure that you understand the potential impact of any command.

Network Diagram

A typical Cisco UCS topology looks similar to this:

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Configure

1. UCS Firmware Version Information

This section describes the UCS firmware version format.

NX-OS

The NX-OS version numbers adhere to the standard Cisco format. For example, 4.0(0)N1.1.

Other UCS Components

Other UCS components adhere to the standard software format (X.Y.Z). For example, 1.0.0.

• X is a major version/release. It is used for major feature releases or architectural changes
  
• Y is a minor version/release.
  
• Z is a bug fix version/release.
  

2. The UCS Firmware Package

The image represents a piece of firmware that is specific to an end point. For example, IOM image, BMC image, etc. Multiple Images are bundled together to form a package. A package is meant only for ease of distribution and download. Unlike the image, a package does not have a version. The UCS manager allows the download of both the package and individual images. If you download a package, it is unpacked, and the individual images are extracted from it. A package is a read-only object that is created when it is downloaded. A package does not occupy any disk space. It represents a list of images that were unpacked as part of the package download. A package cannot be deleted. It is deleted automatically when all the images that came with it are deleted. When an individual image is downloaded, the package name is same as the image name.
Images that are in a package:

• Fabric-Interconnect Kernel and System images
  
• UCS Manager image
  
• IOM firmware image
  
• BMC firmware image
  
• Adapter firmware - network facing (Cisco UCS CNA M71KR , Cisco UCS VIC M81KR )
  
• Adapter firmware - host facing (applicable for Cisco UCS CNA M71KR adapter only)
  
  • Qlogic option ROM
    
  • Emulex option ROM
    
  • Emulex firmware
    
• LSI option ROM
  
• LSI firmware
  
• BIOS
  

3. The UCS Firmware Bundle Overview

In order to see a UCS firmware bundle, complete these steps:

1. Log into the UCS Manager.
   
2. Click the Equipment tab on the Navigation pane.
   
3. Click the Firmware Management tab on the Work pane.
   
4. Click Package under the Firmware Management tab.
   
5. Click the specific firmware bundle.
   
   These illustrate the firmware components within each bundle:
   
   • ucs-2100.1.0.1e.bin—IO Module image
     
   • ucs-6100-k9-kickstart.4.0.1a.N2.1.1e.bin—UCS Fabric Interconnect Kickstart Image
     
   • ucs-6100-k9-system.4.0.1a.N2.1.1e.bin—UCS Fabric Interconnect System Image
     
   • ucs-b200-m1-bios.S5500.86B.01.00.0036-191.061320091126.bin—UCS-B200-M1 Blade BIOS
     
   • ucs-b200-m1-k9-bmc.1.0.1e.bin—Blade BMC Image
     
   • ucs-b200-m1-sasctlr.01.26.00.00_06.24.02.00_03.08.00.00.bin—LSI Logic SAS Controller Image
     
   • ucs-m71kr-e-cna.1.0.1e.bin—Cisco UCS CNA M71KR -Emulex CNA Image
     
   • ucs-m71kr-e-hba.2.80A4.bin—Cisco UCS CNA M71KR -Emulex HBA Image
     
   • ucs-m71kr-e-optionrom.5.03A8.bin—Cisco UCS CNA M71KR -Emulex Option ROM Image
     
   • ucs-m71kr-q-cna.1.0.1e.bin—Cisco UCS CNA M71KR -Qlogic CNA Image
     
   • ucs-m71kr-q-optionrom.2.02.bin—Cisco UCS CNA M71KR -Qlogic Option ROM Image
     
   • ucs-manager-k9.1.0.1e.bin—UCS GUI Image
     

4.1 The UCS 6100 Fabric Interconnect Firmware

This is an image of the UCS Fabric Interconnect firmware:

• Kickstart Image—ucs-6100-k9-kickstart.4.0.1a.N2.1.1e.bin
  
• System Image—ucs-6100-k9-system.4.0.1a.N2.1.1e.bin
  

4.2 The UCS 2100 Firmware – IO Module

This is a single firmware image—ucs-2100.1.0.1e.bin

4.3 The UCS B Series Blade Firmware

This is an image of the UCS B Series Blade firmware:

• BIOS—ucs-b200-m1-bios.S5500.86B.01.00.0036-191.061320091126.bin
  
• BMC—ucs-b200-m1-k9-bmc.1.0.1e.bin
  
• LSI SAS Controller—ucs-b200-m1-sasctlr.01.26.03.00_03.12.00.00.bin
  

4.4 The UCS Adapter Cards Firmware

• Cisco UCS 82598KR-CI Converged Network Adapter—No firmware
  
• Cisco UCS CNA M71KR—Emulex
  
  • Cisco UCS CNA M71KR Emulex—ucs-m71kr-e-cna.1.0.1e.bin
    
  • Cisco UCS CNA M71KR Emulex FC—ucs-m71kr-e-hba.2.80A4.bin
    
  • Cisco UCS CNA M71KR Emulex Option ROM—ucs-m71kr-e-optionrom.5.03A8.bin
    
• Cisco UCS CNA M71KR—Qlogic
  
  • Cisco UCS CNA M71KR Qlogic—ucs-m71kr-q-cna.1.0.1e.bin
    
  • Cisco UCS CNA M71KR Qlogic Option ROM—ucs-m71kr-q-optionrom.2.02.bin
    

4.5 The UCS Manager Firmware

This is an image of the UCS Manager firmware:

UCS Manager—ucs-manager-k9.4.0.1a.N2.1.1e.bin
The code resides and runs on the UCS 6100.

Verify

There is currently no verification procedure available for this configuration.

Read More

Upgrade BIOS on Cisco UCS Server Blade

Introduction

In order to upgrade the BIOS on a Server Blade or a Server Pool, you complete five major steps:

1. Verify/confirm that the correct BIOS is present in the fabric interconnect flash.
   
2. Create a Host Firmware Package policy.
   
3. Associate the Host Firmware Package policy with a Service Profile.
   
4. Associate the Service Profile with the server blade or server pool.
   
5. Verify the BIOS version of the blade matches the BIOS for the Host Firmware Package policy.
   

This tech note addresses how to upgrade the BIOS on a Server Blade or a Server Pool with one of these methods:

• Cisco UCS Manager GUI
  
• Cisco UCS Manager CLI
  

Note: You cannot update the BIOS firmware directly. You must perform the BIOS firmware update through a host firmware package in a service profile. If the BIOS fails, it can recover and boot from the ISO image that is shipped with the server.

Prerequisites

Requirements

Cisco recommends that you:

• Have a working knowledge of Cisco UCS Server Blade software and hardware.
  
• Be familiar with the UCS manager GUI.
  
• Understand the impact and implications of the different commands described in this document
  
• Be familiar with the UCS components and topology. Refer to the diagram for a typical solution
  

Components Used

The information in this document is based on Cisco UCS.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Network Diagram

A typical Cisco UCS topology looks something like this:

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Background Information

The Host Firmware Package enables you to specify firmware versions for different components and bundle them together under one policy. The host firmware includes these server and adapter components:

• BIOS
  
• SAS controller
  
• Emulex Option ROM
  
• Emulex firmware
  
• QLogic option ROM
  
• Adapter firmware
  

In order to upgrade the BIOS on a server blade or a server pool, you must create a Host Firmware that has these components, and then push it to all servers associated with Service Profiles that include this policy.
This Host Firmware Package policy ensures that the host firmware is identical on all servers associated with service profiles that use the same policy. Therefore, if you move the service profile from one server to another, the firmware versions are maintained.
You must include this Host Firmware Package policy in a service profile, and that service profile must be associated with a server for it to take effect.
If you associate a new Host Firmware Package policy to a Service Profile currently linked to blades, it causes those blades to reboot. You must decide if you want to disassociate the service profile before the new firmware package policy is applied.
If a server blade is currently associated with a Service Profile, you can choose to disassociate the blade before the BIOS upgrade is performed. Complete these steps:

1. In the Navigation pane, click the Servers tab.
   
2. In the Servers tab, expand Servers > Service Profiles.
   
3. Expand the node for the organization that contains the service profile that you want to disassociate from a server or server pool. If the system does not include multi-tenancy, expand the root node.
   
4. On the service profile that you want to disassociate with a server, and select Disassociate Service Profile.
   
5. In the Disassociate Service Profile dialog box, click Yes in order to confirm that you want to disassociate the service profile.
   
6. Click OK. If desired, monitor the status and FSM for the server to confirm that the disassociation completes.
   
   

Main Task

Task

These sections detail the processes used to upgrade BIOS on a server blade or a server pool through the GUI and CLI.

1. Upgrade BIOS on a UCS Server Blade with the GUI

Complete these steps:

1. Verify/confirm that the correct BIOS is present in the fabric interconnect flash.
   
2. Create the Host Firmware Package policy with the desired BIOS version:
   
   1. In the Navigation pane, select the Servers tab.
      
   2. On the Servers tab, expand Servers >Policies.
      
   3. Expand the node for the organization where you want to create the policy. If the system does not include multi-tenancy, expand the root node.
      
   4. Right-click Host Firmware Packages, and select Create Host Firmware Package.
      
      
   5. In the Create Host Firmware Package dialog box, enter a unique name and description for the package. This name can be between one and 16 alphanumeric characters. You cannot use spaces or any special characters, and you cannot change this name once the object is saved.
      
   6. Click the down arrows in order to expand one or more of these sections on the left of the dialog box, and select BIOS Firmware Packages.
      
      
   7. When you have added all of the desired firmware to the package, click OK.
      
   8. Double click to select the BIOS Firmware. Click OK in order to confirm that the host firmware package policy is created.
      
      
3. Associate the created Host Firmware Package policy to a Service Profile.
   This association automatically updates and activates the firmware in the server and adapter with the new versions and reboots the server. Complete these steps:
   
   1. In the Navigation pane, click the Servers tab.
      
   2. On the Servers tab, expand Service Profiles.
      
   3. Select the desired Service Profile.
      
   4. On the right pane, click the Policies tab of the selected Service Profile.
      
   5. Extend the Firmware Policies drop down container and select the previously created Host Firmware Package from the Host Firmware menu.
      
   6. Save the changes.
      Note: If your Service Profile is currently associated with a server, this change causes an immediate server reboot with the BIOS installation. If your Service Profile is not associated with a server, apply it to a blade in order for the BIOS upgrade to take effect.
      
      
4. Associate the Service Profile with a server blade or server pool:
   After the Host Firmware Package policy is assigned and saved, associate this policy to the Service Profile used by the blade server and, monitor the KVM output to see the new BIOS get displayed. The BIOS upgrade should not extend the blade's boot time.
   
   1. Click the General tab.
      
   2. Click Change Service Profile Association.
      
      
   3. In the Associate Service Profile window, select the appropriate server or server pool, and click OK in order to push new BIOS to the server.
      
      
5. Verify the BIOS version of the blade matches the BIOS for the Host Firmware Package policy.
   
   

2. Upgrade BIOS on a UCS Server Blade with the CLI

!--- STEP 1. Verify/confirm that the correct BIOS is present in the !--- fabric interconnect flash F340-31-17-FI-A# F340-31-17-FI-A# scope firmware F340-31-17-FI-A /firmware # show image | include Bios Server Bios S5500.86B.01.00.0036-105.042920090209 Server Bios S5500.86B.01.00.0036-132.051320090429 Server Bios S5500.86B.01.00.0036-132.051320090429 Server Bios S5500.86B.01.00.0036-191.061320091126 F340-31-17-FI-A /firmware # !--- STEP 2. Create a Firmware Host Package policy F340-31-17-FI-A# scope org / F340-31-17-FI-A /org # create fw-host-pack bios-upgrade F340-31-17-FI-A /org/fw-host-pack* # create pack-image "Intel" S5500.86B.01.00.0036-191.061320091126 server-bios F340-31-17-FI-A /org/fw-host-pack/pack-image* # commit-buffer !--- STEP 3. Associate Host Firmware Package !--- policy with Service Profile !--- STEP 4. Associate Service Profile with a blade !--- to have BIOS updated. F340-31-17-FI-A* # scope org / F340-31-17-FI-A /org* # scope service-profile jdewberr-c2s1 F340-31-17-FI-A /org/service-profile* # associate server 2/1 F340-31-17-FI-A /org/service-profile* # commit-buffer F340-31-17-FI-A /org/service-profile* # show assoc Service Profile Name Association Server Server Pool -------------------- -------------- ------ ----------- jdewberr-c2s1 Associated 2/1 F340-31-17-FI-A /org/service-profile* # !--- STEP 5. When association is completed, !--- check current BIOS version F340-31-17-FI-A* # F340-31-17-FI-A* # F340-31-17-FI-A* # scope server 2/1 F340-31-17-FI-A /chassis/server* # F340-31-17-FI-A /chassis/server* # show bios Bios Firmware: Server Model Vendor Running-Vers ------- ---------- ----------------- ------------ 2/1 N20-B6620-1 Intel Corp. S5500.86B.01.00.0036-191.061320091126 F340-31-17-FI-A /chassis/server* #

Verify

Read More

Determining Which Devices Are Installed in Your Server

Viewing Installed Devices Using the UCS Manager GUI

To view the installed devices in the server by using the UCS Manager GUI, follow these steps:

1. In the UCS Manager main window, click the Equipment tab in the Navigation pane.

2. On the Equipment tab, expand Equipment > Chassis > Chassis_Number > Servers > Server_Number.

where Server_Number is the target server.

3. Select Interface Cards.

The interface cards installed in the target server are displayed. The product ID (PID) of each card is listed.

Viewing Installed Devices Using the UCS Manager CLI

To view the installed devices in the server by using the UCS Manager CLI, follow these steps. For more information about the UCS Manager CLI, see the Cisco UCS Manager CLI Configuration Guide and the Cisco UCS Manager CLI Command Reference.

1. Use Telnet or SSH to connect to the UCS system.

2. Use the scope command to change to chassis-server command mode:

# scope server chassis-id/blade-id

Where chassis-id/blade-id is the target server.

3. Use the show adapter command to display a list of installed interface cards in the target server. The interface cards are displayed by their PID numbers.

/chassis/server # show adapter

Viewing Installed Devices Using the KVM Console

To see the names and model numbers of the devices displayed on the console screen during server bootup, follow these steps:

1. In the UCS Manager main window, click the Equipment tab in the Navigation pane.

2. On the Equipment tab, expand Equipment > Chassis > Chassis_Number > Servers.

3. Select the target server that you want to access through the KVM console.

4. In the Work pane, click the General tab.

5. In the Actions area, click KVM Console. The KVM console opens in a separate window.

6. Reboot the server and observe the information about the installed devices on the console screen during bootup.

Read More

Common Tips in UCS Firmware Management

Introduction

This document presents some common tips to simplify your daily firmware management process.

Prerequisites

Requirements

Cisco recommends that you:

• Have a working knowledge of Cisco UCS Server Blade software and hardware.
  
• Be familiar with the UCS manager GUI.
  
• Understand the impact and implications of the different commands described in this document
  
• Be familiar with the UCS components and topology. Refer to the diagram for a typical solution
  

Components Used

The information in this document is based on Cisco UCS.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a default configuration. If your network is live, make sure that you understand the potential impact of any command.

Network Diagram

A typical Cisco UCS topology looks something like this:

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Main Task

1. Download Firmware from Cisco.com

Complete these steps:

1. Navigate to the SW Center Homepage and select a Product Category.
   
   
2. Choose a product from the hierarchical tree that appears.
   
   
3. Select a Software Type if multiple Software Types exist for the product you selected.
   
   
4. Click the Image Name, and the details for that image appear with an option to download.
   
   
5. Click Image.bin. You must accept the standard Cisco End User License Agreement (EULA).
   Once you accept the EULA, the download begins.
   
   

2.1 Firmware Management with GUI

Before you perform firmware management, refer to prerequisites for firmware upgrade or downgrade. It is recommended that all firmware management be handled through the GUI.

View Installed Firmware

Complete these steps in order to view installed firmware in UCS through the GUI:

1. Log into Cisco UCS Manager.
   
2. In the Navigation pane, click the Equipment tab.
   
3. Click the Firmware Management tab in the Work pane.
   
4. Click the Installed Firmware tab.
   

Packages

The Packages tab:

• Keeps track of all packages on the system
  
• Shows deleted Images
  
• When all Images are deleted, the package is removed from the tab
  

Images

The Images tab:

• Allows you to obtain information on individual Images in the package
  
• Allows you delete the Images
  
• Once all Images associated to a Package are deleted, the Package is removed from the Package tab
  

Download Tasks

When you download a firmware image bundle, a Fabric Interconnect needs at least twice as much available space as the size of the firmware image bundle. If the bootflash does not have sufficient space, delete the obsolete firmware, core files, and other unnecessary objects from the fabric interconnect. Before you download a new bundle, check the available free space on the Fabric Interconnects:

1. In the Navigation pane, select Equipment.
   
2. Expand Fabric Interconnects, and select Fabric Interconnect #.
   
3. Click the General tab in the Work pane to the right.
   
4. Expand Local Storage Information.
   
5. Check both fabric interconnects.
   
6. Delete Images and Packages if space is limited.
   
   

Use the Download Tasks tab in order to download firmware. The firmware image name can be between one and 16 alphanumeric characters. You cannot use spaces or any special characters, and you cannot change this name after the object has been saved. The system downloads and unpackages the bundle and distributes it to both fabric interconnects. You can watch the progress on the FSM tab.

From this screen, you can download, update, and activate firmware.

2.2 Firmware Management with CLI

Complete these steps in order to view installed firmware in UCS through the CLI:

1. Log into Cisco UCS through the CLI.
   
2. Issue the scope system command.
   
3. Enter the show firmware expand command.
   

View Installed Firmware
F340-31-17-FI-A# F340-31-17-FI-A# scope system F340-31-17-FI-A /system # show firmware expand UCSM: Running-Vers: 1.0(1e) Activate-Status: Ready Fabric Interconnect A: Running-Kern-Vers: 4.0(1a)N2(1.1e) Running-Sys-Vers: 4.0(1a)N2(1.1e) Startup-Kern-Vers: 4.0(1a)N2(1.1e) Startup-Sys-Vers: 4.0(1a)N2(1.1e) Act-Kern-Status: Ready Act-Sys-Status: Ready Bootloader-Vers: v1.2.0(06/19/08)

scope firmware is a useful CLI command that allows you to:

• Delete
  
• Download
  
• Scope—to download tasks
  
• Show—download tasks, event, fsm, image, and package
  

Image update and activation is done from the scope of individual components

scope firmware
F340-31-17-FI-A# F340-31-17-FI-A# scope firmware F340-31-17-FI-A /firmware # ? delete Delete managed objects download Download exit Exit from command interpreter scope Changes the current mode show Show system information F340-31-17-FI-A /firmware #

Verify

There is currently no specific verification information available for this configuration

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.

Read More

Virtual Interface Adapter in a Service Profile Scenario

Introduction

The new Cisco Unified Computing System (UCS) Cisco Blade Server B440 M1 allows for Virtual Interface Adapter placement in UCS Manager (UCSM) service profiles. This is known as Virtual Host Interface Placement Assignment.
Virtual Host Interface Placement Assignment specifies how vNICs and vHBAs are placed on physical network interface (mezzanine) cards in a server hardware configuration independent of one another. When a logical server is associated to a blade, a Virtual Interface Adapter is assigned to a physical adapter.
With the new B440 M1 blade server there are two Virtual Interface Adapters that can assign vNICs/vHBAs to a specific Virtual Interface Adapter (1 to 2). If a vNIC/vHBA is not assigned to a Virtual Interface Adapter, the Unified Computing Manager (UCM) applies a default policy based on pci bdf order. Further, UCSM gives you the ability to customize each individual Virtual Interface Adapter and to create Virtual Interface Adapter profiles that can be used after server blade implementation or recovery.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• Cisco UCS 5108 Chassis
  
• Cisco UCS 6100XP Fabric Interconnet with release 4.1(3)N2
  
• Cisco UCS B440-M1 Blade Server
  
• Cisco UCSM version 1.3
  

Components Used

The information in this document is based on these software and hardware versions:

• Cisco UCS B440-M1 Blade Server
  

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Background Information

Cisco UCSM allows you to define the B440-M1 10Gb mezzanine adapters, of which there are now four:

• QLogic Schultz based CNA (M72KR-Q)
  
• Emulex Tigershark based CNA (M72KR-E)
  
• Intel Niantic based NIC (M61KR-I)
  
• Broadcom Everest based NIC (M51KR-I)
  

The B440-M1 10Gb mezzanine adapters used for this document are Emulex-based CNA M72KR-E that supports two vHBAs/vNICs.
This is an example of a 2-slot (1 and 2) Interface Adapter with 2 HBAs and 2 NICs per Virtual Interface Adapter:

Note: Pictured above is a Cisco UCSM equipment view of the Emulex installed adapters.
The service profile also supports vNIC/vHBA placement in UCSM GUI, which allows for Virtual Interface Adapter properties configuration of selection preference:

• All: Any vNIC/vHBA can be assigned to this Virtual Interface Adapter.
  
• Assigned-Only: Only the explicitly assigned vNIC/vHBA can belong to this Virtual Interface Adapter.
  
• Exclude-Dynamic: UCSM cannot assign dynamic vNICs to this Virtual Interface Adapter.
  
• Exclude-Unassigned: UCSM cannot assign static (non dynamic) vNICs to this Virtual Interface Adapter.
  

The above selection preference options indicate how UCSM can use this Virtual Interface Adapter when it assigns a vNIC/vHBA.
Note: Numerical order means vNIC/vHBA can be ordered inside a Virtual Interface Adapter.
This shows selection preference where vCon1 is assigned all and vCon2 is assigned assigned-only:

Virtual Interface Adapter in Service Profile

Configuring the service profile for the Virtual Interface Adapter requires an understanding of how the software assigns the adapters for the B440-M1:

• vNICs and vHBAs are assigned to the Virtual Interface Adapter implicitly by the user or automatically by UCSM during LS association.
  
• During the LS association, the Virtual Interface Adapter is mapped to physical mezzanine cards.
  

vNIC/vHBA Placement

Default placement of vNICs/vHBAs:

• If the 2 adapters are present, by default, the B440-M1 adapter assigns vNICs/vHBAs starting from the slot on the right (slot 1) and equally distributes the total number between the 2 adapters. For example: If you have 4 vNICs (i.e., 1, 2, 3, and 4), it will assign 1 and 2 on the slot 1 adapter and 3 and 4 on the slot 0 adapter.
  

Specific placement of vNICs/vHBAs:

• If more control is needed on how to place a vNIC/vHBA to a specific adapter, you can use the concept of Virtual Interface Adapter .
  

Service Profile

Perform these steps:

1. Creation of the service profile is not new to Cisco UCS and can be referenced in Configuring Service Profiles for details on creation.
   
2. With Cisco UCSM during service profile creation, you can perform your desired Virtual Interface Adapter placement or use the Modify vNIC/vHBA Placement under Actions for both Network (vNICs) or Storage (vHBAs). Refer to Setting the vNIC/vHBA Placement for more details on service profile configuration of Virtual Interface Adapters.
   

This is an illustration of Virtual Interface Adapter placement for vNICs/vHBAs after service profile creation of CE-B440-M1-SP:
Network Modify vNIC Virtual Interface Adapter Placement

Storage Modify vHBA Virtual Interface Adapter Placement

Hardware Adapter Verification

This section describes how to verify Physical Adapters installed in a Cisco UCS 5108 chassis:
From the Equipment tab of UCSM, choose the appropriate interface card under the Interface Cards of the server. Refer to Managing Firmware for further UCSM GUI Equipment tab pane functions.
Adapter Hardware Identification

Service Profile Default and Selection of Virtual Interface Placement Interface Adapter Card 2

The Default Virtual Interface Placement section describes how to use the default and selection Virtual Interface Placement using the Cisco B440-M1 Emulex Adapter Interface Card 2 with UCSM.

Default Virtual Interface Placement

Perform these steps:

1. Verify hardware for the B440-M1 Emulex Adapter Interface Card 2:
   
   1. Verify hardware for the B440-M1 Emulex Adapter.
      Identify Adapter Type for B440-M1 Interface Cards (slot1 and slot2)
      
      
   2. Verify hardware for the B440-M1 Emulex Adapter details for Interface Card 2.
      Verifying Interface Adapter details for slot 2 Interface Card 2
      
      
2. Configure the service profile for the B440-M1 Emulex Adapter Interface Card 2:
   
3. Verify the default virtual interface placement.
   

Create a Service Profile

Refer to Configuring Service Profiles for further details on service profile creation.

1. Create a service profile for Interface Card 2.
   
2. Create two vNICs for the service profile created.
   
   1. Server Profile created with default 2 vNICs
      
      
      
   2. The below snapshot shows the order placement vCon 1 that has been assigned placement default Interface Card 1 slot 1 for the vNICs defined in the service profile.
      vNICs assigned to Interface Card 1
      
      

      Pubs-B /org # scope service-profile server 1/7
      Pubs-B /org/service-profile # show vnic detail
      
      
      Name: vnic-emulex-a
          Fabric ID: A
          Dynamic MAC Addr: 00:25:B5:03:03:0B
          Desired Order: 1
          Actual Order: 1
          Desired VCon Placement: 1
          Actual VCon Placement: 1
          Equipment: sys/chassis-1/blade-7/adaptor-1/host-eth-1
      
      Name: vnic-emulex-b
          Fabric ID: B
          Dynamic MAC Addr: 00:25:B5:04:B2:07
          Desired Order: 2
          Actual Order: 2
          Desired VCon Placement: 1
          Actual VCon Placement: 1
          Equipment: sys/chassis-1/blade-7/adaptor-1/host-eth-2
      

3. Verify vNIC default Virtual Interface Adapter placement.
   Default Virtual Interface Placement
   
   

   Pubs-B /org # scope service-profile server 1/7
   
   Pubs-B /org/service-profile # show vnic detail
   
    Name: vnic-emulex-c
       Fabric ID: A
       Dynamic MAC Addr: 00:25:B5:00:A5:00
       Desired Order: 3
       Actual Order: 1
       Desired VCon Placement: Any
       Actual VCon Placement: 2
       Equipment: sys/chassis-1/blade-7/adaptor-2/host-eth-1
       
    Name: vnic-emulex-d
       Fabric ID: B
       Dynamic MAC Addr: 00:25:B5:00:00:00
       Desired Order: 4
       Actual Order: 2
       Desired VCon Placement: Any
       Actual VCon Placement: 2
       Equipment: sys/chassis-1/blade-7/adaptor-2/host-eth-2
   

Manual Virtual Interface Adapter Placement

1. In order to use Cisco UCSM Modify vNICs/vHBAs Placement, refer to Setting the vNIC/vHBA Placement.
   
2. Assign the new vNICs (vnic-emulex-c and vnic-emulex-d) to Interface Card 1 (Slot 1) from Slot 2 and assign vnic-emulex-a/b vNICs.
   
   1. This step verifies that vnic-emulex-c/d can be specified manually.
      
      
   2. Reassign the vNICs placements.
      
      

      vNIC:
      
          Name: vnic-emulex-a
          Fabric ID: A
          Dynamic MAC Addr: 00:25:B5:03:03:0B
          Desired Order: 1
          Actual Order: 1
          Desired VCon Placement: 2
          Actual VCon Placement: 2
          Equipment: sys/chassis-1/blade-7/adaptor-2/host-eth-1
      
          Name: vnic-emulex-b
          Fabric ID: B
          Dynamic MAC Addr: 00:25:B5:04:B2:07
          Desired Order: 2
          Actual Order: 2
          Desired VCon Placement: 2
          Actual VCon Placement: 2
          Equipment: sys/chassis-1/blade-7/adaptor-2/host-eth-2
      
          Name: vnic-emulex-c
          Fabric ID: A
          Dynamic MAC Addr: 00:25:B5:00:A5:00
          Desired Order: 1
          Actual Order: 1
          Desired VCon Placement: 1
          Actual VCon Placement: 1
          Equipment: sys/chassis-1/blade-7/adaptor-1/host-eth-1
      
        Name: vnic-emulex-d
          Fabric ID: B
          Dynamic MAC Addr: 00:25:B5:00:00:00
          Desired Order: 2
          Actual Order: 2
          Desired VCon Placement: 1
          Actual VCon Placement: 1
          Equipment: sys/chassis-1/blade-7/adaptor-1/host-eth-2
      
      Pubs-B /org/service-profile # show vcon expand detail
      
      Virtual Network Interface:
          Virtual Network Interface ID: 1 This is Adapter ID:1 Slot1
          Selection Preference: All
      
           Virtual Network Interface ID: 2 This is Adapter ID:2 Slot2
          Selection Preference: All
      
      Pubs-B /chassis/server # show server adapter vnics
      
      Eth Interface:
      
      Adapter Interface Vnic Dn    Dynamic MAC Addr Type
      ------- --------- ---------- ---------------- ----
      
      1    1 org-root/ls-CE-B440-M1-SP/ether-vnic-emulex-c 00:25:B5:00:A5:00 Ether
      1    2 org-root/ls-CE-B440-M1-SP/ether-vnic-emulex-d 00:25:B5:00:00:00 Ether
      
      2    1 org-root/ls-CE-B440-M1-SP/ether-vnic-emulex-a 00:25:B5:03:03:0B Ether
      2    2 org-root/ls-CE-B440-M1-SP/ether-vnic-emulex-b 00:25:B5:04:B2:07 Ether
      
      

Read More