Table of Contents
Advertisement
Cisco UCS Blade Server
Upgrade Scenario 1: UCSM and BIOS Earlier Than Version 2.1(3a), CPU Earlier Than Intel E5-2600 v2
This scenario assumes the following conditions:
•
•
•
In this case, use the following procedure to upgrade the server and CPUs.
Upgrade the Cisco UCS Manager software to version 2.1(3a) or later. The required server CIMC and
Step 1
BIOS are also included with the 2.1(3a) download bundle.
Use the procedures in the appropriate upgrade guide for Release 2.1 (depending on your current software
version):
Use Cisco UCS Manager 2.1(3a) to upgrade and activate the server CIMC to version 2.1(3a) or later.
Step 2
Use the procedures in the GUI or CLI
Use Cisco UCS Manager 2.1(3a) to upgrade and activate the server BIOS to version 2.1(3a) or later.
Step 3
Use the procedures in the GUI or CLI
Disassociate the server in Cisco UCS Manager.
Step 4
Power off the server.
Step 5
Replace the CPUs with the Intel E5-2600 v2 Series CPUs.
Step 6
Use the procedures in the
Reinsert the server to the chassis.
Step 7
Wait for Cisco UCS Manager to automatically discover the server.
Step 8
Note
Perform a board controller activation by using the Cisco UCS Manager CLI interface. Use the following
Step 9
sequence of commands:
Note
Note
# scope server <chassis/server>
# scope boardcontroller
# show image
# activate firmware <boardcontroller version>.0 force
# commit-buffer
See also
Cisco UCS B-Series Servers Upgrade Guide for Intel E5-2600/E5 2400 v2 Series CPUs
4
The Cisco UCS Manager software is at a version earlier than 2.1(3a).
The server is at a BIOS/CIMC version earlier than 2.1(3a).
The server is using CPUs earlier than Intel E5-2600 v2 Series.
Release 2.1 Upgrade
Blade Server Installation and Service Note
At this point, the Health LED of the server shows a critical fault and Cisco UCS Manager reports
a generic error message:
controller activation is required, as described in the next step.
The
command in the sequence below lists the board controller versions available for
show image
the server. Always activate the latest board controller image version when you use the
command.
activate firmware
The server automatically reboots after the
Sample Board Controller Activation Command Sequence, page
Guides.
Firmware Management Guide, Release
Firmware Management Guide, Release
WILL_BOOT_FAULT: Sensor failure asserted
commit-buffer
2.1.
2.1.
for your server.
. This is because a board
command is executed.
15.
OL-28629-02
Advertisement
Table of Contents
