Cisco UCS B460 M4 Manuel utilisateur
Contents
Introduction
Prerequisites
Requirements
Components Used
Background
Discovery Problems
Discovery Fails at 3% - Firmware Mismatch
Solution
Discovery Fails at 7% - CPU Mismatch
Solution
Introduction
This document describes two possible discovery failures that can occur when a B460 M4 motherboard is replaced and their respective solutions.
Prerequisites
Requirements
This document assumes knowledge of UCS B460 M4 and UCS Manager (UCSM).
Components Used
B460 M4 Blade Server
●
UCS Manager
●
Firmware 2.2(3b)
●
Background
The B460 M4 server consists of two Scalable M4 Blade Modules (B260 M4) and a Scalability Connector that cross-connects the two Blade Modules and
allows them to function as a single server. The Blade Module on the bottom is the “Master” and the Blade Module on the top is the “Slave.”
Discovery Problems
Discovery Fails at 3% - Firmware Mismatch
In this failure scenario, the discovery fails at 3% with Remote Invocation Description Aggregate blade CIMC firmware version mismatch. Activate same
firmware version on both CIMC as shown in the figure below. This can occur due to the replacement motherboard or blade module having a different
firmware than the pre-existing B460 M4 server.
The Overall Status will be Discovery Failed as shown in the figure below.
The mismatched firmware can be checked from the command line (CLI) as shown below. In the
output below, the first CIMC is the master and the second is the slave.
UCS-A# show system firmware expand detail
Server 7:
CIMC:
Running-Vers: 2.2(3b)
Package-Vers:
Update-Status: Ready
Activate-Status:
Startup-Vers:
Backup-Vers: 2.2(3a)
Bootloader-Vers: 2.2(3b).33
CIMC:
Running-Vers: 2.2(3a)
Package-Vers:
Update-Status: Ready
Activate-Status:
Startup-Vers:
Backup-Vers: 2.2(3b)
Bootloader-Vers: 2.2(3a).33
CIMC:
Running-Vers: 2.2(3b)
Package-Vers: 2.2(3b)B
Update-Status: Ready
Activate-Status: Ready
Startup-Vers: 2.2(3b)
Backup-Vers: 2.2(3b)
Bootloader-Vers: 2.2(3b).33
Solution
In order to recover from this, follow the steps below.
1) Navigate to Equipment > Chassis > Chassis # > Servers > Server # > Installed Firmware tab.
2) Right-click on the component that needs to be updated (e.g. BIOS, CIMC Controller) and select Update Firmware. In this example, the CIMC Controller
will be updated to 2.2(3b).
3) Select the correct firmware, the Force checkbox and click Apply.
Tip: If it's not clear which version needs to be selected from the dropdown, the network
administrator can navigate to Equipment > Firmware Management > Packages, expand
ucs-k9-bundle-b-series.VERSION.B.bin and look for "ucs-EXM4." There will be three
components: bios (BIOS), brdprog (Board Controller), and cimc (CIMC Controller).
4) Monitor the Installed Firmware tab and wait until the Update Status and Activate Status columns change to Ready and the Backup Version column
changes to the correct firmware.
Tip: The server administrator can monitor the update status from Equipment > Chassis >
Chassis # > Servers > Server # > Inventory tab > CIMC tab > Update Status
5) Right-click on this same component and select Activate Firmware. Again, select the correct firmware, the Force checkbox and click Apply.
6) The Activate Status column in the Installed Firmware tab will change state and eventually return to Ready.
7) The Overall Status in the General tab will change to Inaccessible while the server is rebooting. It should then change to Discovery and go through the
discovery process.
Discovery Fails at 7% - CPU Mismatch
In this failure scenario, the discovery fails at 7% with Remote Invocation Description Pre-boot Hardware config failure - Look at POST/diagnostic results
as shown in the figure below.
The Overall Status in the General tab will be Compute Failed.
The POST Results can be verified by clicking the View Post Results under Actions in the General tab. The figure below shows that the problem is due to a
CPU Mismatch.
Solution
If the hardware matches between the two blade modules, this could be caused by cached information on the server. An enhancement request (CSCuv27099)
exists to clear the cached information from UCS Manager (UCSM). The server administrator can also contact the Cisco Technical Assistance Center (TAC)
for a workaround.
Autres manuels pour UCS B460 M4
3
Table des matières
Autres manuels Cisco Serveur
Cisco
Cisco UCS C480 M5 Instructions d'installation et d'entretien
Cisco
Cisco AS5300 - Universal Access Server Manuel utilisateur
Cisco
Cisco 700 series Manuel d'installation et d'exploitation
Cisco
Cisco UCS C480 M5 Instructions de montage
Cisco
Cisco UCS C22 Instructions d'installation et d'entretien
Cisco
Cisco UCS C220 M3 Manuel utilisateur
Cisco
Cisco TD 92322GB Manuel utilisateur
Cisco
Cisco ACE-4710-1F-K9 Manuel utilisateur
Cisco
Cisco Unity Manuel utilisateur
Cisco
Cisco SNS-3415 series Manuel de programmation
Cisco
Cisco NCS 1001 Manuel utilisateur
Cisco
Cisco Meraki MX65 Manuel utilisateur
Cisco
Cisco UCS B250 M1 Manuel
Cisco
Cisco UCS C240 M4 Instructions d'installation et d'entretien
Cisco
Cisco TelePresenceMCU 5300 Series Manuel utilisateur
Cisco
Cisco CRS-16 DC Mode d’emploi
Cisco
Cisco NAC-3300 Series Manuel utilisateur
Cisco
Cisco ONS 15454 Manuel
Cisco
Cisco UCS B420 M3 Manuel
Cisco
Cisco UCS C Series Manuel utilisateur
