UCSM Server

[jibber.mark1]

My UCSM the server is having a critical error with the reason WILL_BOOT_FAULT:Sensor Failure Asserted;

Anyone have an idea on this error? Any help would be appreciate.

[Qiese Dides · Accepted solution]

Hi Mark,

By UCSM Server are you possibly referring to a B200 - M3 blade? Also what UCS-M version are you currently running along with the BIOS Version. This information will help us narrow down your issue.

However, based on the error code it looks like you are running into an issue regarding Discovery on the blade. I pasted a link with the excerpt pasted out regarding the issue you MAY be hitting. However, without further information we will not be able to fully assist you.

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/hw/CPU/IVB/install/IVB-B.html#wp45312

Upgrade Scenario 2: UCSM and BIOS at Version 2.1(3a) or Later, CPU Earlier Than Intel E5-2600 v2

This scenario assumes the following conditions:

The Cisco UCS Manager software is at version 2.1(3a) or later.
   The server is already using BIOS/CIMC version 2.1(3a) or later.
   The server is using CPUs earlier than Intel E5-2600 v2 Series CPUs.

In this case, the server already has the software and firmware prerequisites. Use the following procedure to upgrade the CPUs:

Step 1        Disassociate the server in Cisco UCS Manager.

Step 2        Power off the server.

Step 3        Replace the CPUs with the Intel E5-2600 v2 Series CPUs.

Use the procedures in the Blade Server Installation and Service Note for your server.

Step 4        Reinsert the server to the chassis.

Step 5        Wait for Cisco UCS Manager to automatically discover the server.

Note        At this point, the Health LED of the server shows a critical fault and Cisco UCS Manager reports a generic error message: WILL_BOOT_FAULT: Sensor failure asserted. This is because a board controller activation is required, as described in the next step.

Step 6        Perform a board controller activation by using the Cisco UCS Manager CLI interface. Use the following sequence of commands:

Note        The server automatically reboots after the commit-buffer command is executed.

Note        The show image command in the sequence below lists the board controller versions available for the server. Always activate the latest board controller image version when you use the
activate firmware command.

# scope server <chassis/server>
# scope boardcontroller
# show image
# activate firmware <boardcontroller version>.0 force
# commit-buffer

See also Sample Board Controller Activation Command Sequence.

Step 7        Do not continue with the next step until the board controller activation completes. Verify whether the activation is complete by using the show version command.

As shown in the example below, wait until the Activate-Status returns Ready. This process takes a few minutes before Activate-status is successfully completed and returns Ready.
# show version
BoardController:
Running-Vers: 8.0
Package-Vers:
Activate-Status: Ready

Step 8        Clear the WILL_BOOT_FAULT by using the Cisco UCS Manager GUI to reset the server CIMC:

1. In the Navigation pane, click the Equipment tab.

2. On the Equipment tab, expand Equipment > Chassis > Chassis number > Servers, then choose your server.

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

4. In the Actions area, click Recover Server.

5. In the Recover Server dialog, click Reset CIMC (Server Controller), then click OK.

Wait for CIMC to reboot and for Cisco UCS Manager to do a shallow discovery of the server. This takes two to three minutes. At the end of this process the WILL_BOOT_FAULT is cleared.