PDF(188.0 KB) View with Adobe Reader on a variety of devices
ePub(83.5 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Updated:June 28, 2018
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Release Notes for Cisco UCS Diagnostics for B-Series Blade Servers, Release 1.0
First Published: October 25, 2013 Last Updated: June 28, 2018 Part Number: OL-30793-01
This document describes system requirements, image download location, known caveats, and workarounds for Cisco UCS Diagnostics for B-Series Blade Servers, Release 1.0. This document also includes the following:
Current information that became available after the technical documentation was published
List of supported servers for the UCS Blade Server Diagnostics, Release 1.0
Make sure to review other available documentation on Cisco.com to obtain current information on Cisco UCS B-Series Blade Servers.
Updated release notes for Cisco UCS Blade Server Diagnostics, Release 1.0(4c).
1.0(4a)
April 18, 2017
Updated “Supported Servers” table for B420, B260, B460, and B200 M4 servers.
1.0(4a)
August 5, 2016
Updated release notes for Cisco UCS Blade Server Diagnostics, Release 1.0(4a).
1.0(3a)
April 11, 2016
Updated release notes for Cisco UCS Blade Server Diagnostics, Release 1.0(3a).
1.0(1d)
July 7, 2015
Updated release notes for Cisco UCS Blade Server Diagnostics, Release 1.0(1d).
1.0(1c)
June 26, 2015
Updated release notes for Cisco UCS Blade Server Diagnostics, Release 1.0(1c).
1.0(1b)
October 14, 2014
Updated release notes for Cisco UCS Blade Server Diagnostics, Release 1.0(1b); removed “(1 x)” designation from document title; added generic “Obtaining Documentation and Submitting a Service Request” section.
1.0(1a)
October 25, 2013
Created release notes for Cisco UCS Blade Server Diagnostics, Release 1.0(1a).
Introduction
Cisco UCS Blade Server Diagnostics tool for Cisco UCS Blade Servers enables you to verify the health of the hardware components on your servers. The diagnostics tool provides a variety of tests to exercise and stress the various hardware subsystems on the Cisco UCS Blade Servers, such as memory and CPU. You can use the tool to run a sanity check on the state of your Cisco UCS Blade Servers after you fix or replace a hardware component. You can also use this tool to run comprehensive burn-in tests before you deploy a new Cisco UCS Blade Server in your production environment.
Image Download Link
You can download the ISO image for the Cisco UCS Blade Server Diagnostics from the Cisco website at:
The following caveats were resolved in Release 1.0(4c):
Table 3 Resolved Caveats in Release 1.0(4c)
Defect ID
Symptom
First Release Affected
Resolved in Release
CSCvj73196
Diagnostics ISO appeared as an unsupported platform on blade servers that did not have PIDs beginning with UCSB.
This issue has been resolved.
1.0(1d)
1.0(4c)
The following caveats were resolved in Release 1.0(3a):
Table 4 Resolved Caveats in Release 1.0(3a)
Defect ID
Symptom
First Release Affected
Resolved in Release
CSCuw90119
The UCS Diagnostic Tool no longer marks DIMM tests as failed for correctable ECC errors.
1.0(1d)
1.0(3a)
The following caveats were resolved in Release 1.0(1b):
Table 5 Resolved Caveats in Release 1.0(1b)
Defect ID
Symptom
First Release Affected
Resolved in Release
CSCui83062
When running the show spd command in the CLI, the diagnostic tool no longer incorrectly displays Serial Presence Detect (SPD) errors.
1.0(1a)
1.0(1b)
CSCuo25152
The CLI now correctly displays the Fusion ioDrive2 Mezzanine Flash card.
1.0(1a)
1.0(1b)
CSCuq45525
The SEL log is now cleared before running diagnostic tests.
1.0(1a)
1.0(1b)
CSCuq45512
Memory tests no longer fail if the error is correctable using Error-Correcting Code (ECC) memory.
1.0(1a)
1.0(1b)
CSCuo25091
The IO tab in the GUI (Server Information > Inventory > IO) now displays the correct information for the Fusion ioDrive2 Mezzanine Flash card and LSI Warpdrive Mezzanine Flash card.
1.0(1a)
1.0(1b)
CSCuq25281
The IO tab in the GUI (Server Information > Inventory > IO) now displays the correct information for the Fusion ioMemory3 Flash card.
1.0(1a)
1.0(1b)
CSCuo24564
Server diagnostics no longer fail if there is a P2_TEMP_SENS error.
1.0(1a)
1.0(1b)
CSCuo61101
The SaveUSB test no longer passes in the CLI if the USB is not connected.
1.0(1a)
1.0(1b)
CSCuo88961
The CLI now correctly displays memory information for the Cisco UCS B230 M2 Blade server.
1.0(1a)
1.0(1b)
Open Caveats
Open caveats are provided in the following release-specific tables:
Open caveats may be listed in association with the release in which they were first noticed or in the release identified as the first affected. Users should review open caveats in all releases to avoid overlooking a defect that may impact their release.
The following caveats were open in Release 1.0(4a):
Table 6 Open Caveats in Release 1.0(4a)
Defect ID
Symptom
Workaround
First Release Affected
CSCva64192
The blade server diagnostics CLI for a Cisco UCS B200 or B420 M4 server displays an error message when the server memory command is run.
When this issue occurs, retrieve the server memory details from the blade server diagnostics GUI.
1.0(4a)
CSCva74940
When you run multiple tests from the test suite and view the log summary through the Blade Server Diagnostics GUI by using the scroll bar, the GUI becomes unresponsive. However, this issue does not impact the tests. The tests continue to run.
To avoid this issue, use the up and down arrows instead of the scroll bar.
1.0(4a)
The following caveats were open in Release 1.0(1c):
Table 7 Open Caveats in Release 1.0(1c)
Defect ID
Symptom
Workaround
First Release Affected
CSCuu40670
Server information does not display information about the Cisco UCSB-LSTOR-PT storage expander in the Cisco UCS B420 M4 diagnostic tool.
This issue has no known workaround.
1.0(1c)
CSCuu40612
The Universally Unique Identifier (UUID) in the Cisco UCS B420 M4 diagnostics tool is displayed incorrectly.
Use the UUID displayed in Cisco UCS Manager.
1.0(1c)
CSCuu40627
PCI inventory shows the "?" character instead of the "&" character for Cisco UCS B420 M4.
This issue has no known workaround.
1.0(1c)
The following caveats were open in Release 1.0(1b):
Table 8 Open Caveats in Release 1.0(1b)
Defect ID
Symptom
Workaround
First Release Affected
CSCuo39634
SEL logs from the slave blade are not accessible from the Cisco UCS B460 M4 diagnostics tool. SEL logs from the master blade are accessible and exposed.
Clear SEL logs in Cisco UCS Manager and run diagnostics normally. Then, using Cisco UCS Manager, check the blade SEL logs for any memory errors.
1.0(1b)
CSCuo46470
Sensor data from the slave blade is not accessible from the Cisco UCS B460 M4 diagnostics tool. Sensor data from the master blade is accessible and exposed.
Use Cisco UCS Manager to access the sensor data.
1.0(1b)
CSCuo52795
In some cases, the GUI Overview (“splash”) page does not load properly.
Navigate to another section of the GUI and then return to the Overview page.
1.0(1b)
CSCup16610
Running the SaveUSB command without having a USB memory device mounted appears to be successful but logs are saved to a /tmp directory instead of being saved to the user host.
This issue has no known workaround. User must mount USB flash drive before log can be saved to user host.
1.0(1b)
CSCuq18740
Blade server diagnostics GUI shows incorrect CPU thread count for B200 M4.
This issue has no known workaround. use the diagnostics CLI to get the CPU thread count.
1.0(1b)
CSCuq27645
PCI inventory shows the "?" character instead of the "&" character; other output is correct.
This issue has no known workaround.
1.0(1b)
CSCur01405
Unable to clear all SEL entries on Š B420M3, B260M4, and B460M4 servers.
Use Cisco UCS Manager to clear the SEL logs on these blade servers.
1.0(1b)
The following caveats were open in Release 1.0(1a):
Table 9 Open Caveats in Release 1.0(1a)
Defect ID
Symptom
Workaround
First Release Affected
CSCui00152
When displaying the CPU cache information (SMBIOS --> cache) for the B200-M2 UCS Blade Server, the diagnostics tool incorrectly calculates the L1 and L2 level cache size.
The B200-M2 UCS Blade Server running an older BIOS displays the L1 and L2 caches per core and therefore, the diagnostics tool incorrectly calculates the L1 and L2 level cache size.This is a known issue and it has no known workaround.
1.0(1a)
CSCui28615
If five or more loops are run for the Memory Random test on B200-M2 server, it can cause the Memory Random test to fail due to the high CPU temperature.
If the Memory Random test fails, check if the failure is due to the high CPU temperature. This is an expected behavior and it does not mean that the memory is bad.
1.0(1a)
CSCui77931
The CPU Register test fails on the B230-M2 and B440-M2 servers with the following errors:
[NON-FATAL ERROR][Node 0 QPI 1] QPI is not running full width
[NON-FATAL ERROR][Node 0 QPI 2] QPI is not running full width
[FATAL error][IOH 0] PCIe port 1 has detected an error
This issue has no known workaround.
1.0(1a)
CSCui83062
When running the show spd command in the CLI, the diagnostic tool does not correctly display the Serial Presence Detect (SPD) errors with the memory DIMM even though the DIMM has errors.
The UCS blade diagnostics have a SEL event titled as the System Firmware Error #0x06 without a decode to the DIMM. The UCSM can decode the blade SEL to the DIMM.
1.0(1a)
Resolved in 1.0(1b).
CSCuj98184
The show status output in the CLI does not match the number of loops if the test is started in the GUI.
This issue has no known workaround.
1.0(1a)
CSCuj45779
When viewing the logs in the Logs tab, the diagnostics tool generates a " This value is out of range " error when you try to manually select a page number, for example, "2 of [22]". The page navigation also stops responding when you reach the last page in the logs.
Refresh the GUI by navigating away from the logs or use the Refresh button on the screen.
1.0(1a)
CSCul00980
Some DIMMS display No Module Installed in the CLI output of the server memory command. The SMBIOS table is not populated with the correct size for each DIMM.
This issue happens with the 32GB DIMMs using BIOS 1.4 and it has no known workaround.
1.0(1a)
Related Documentation
For more information, you can access the following guides:
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.
This document is to be used in conjunction with the documents listed in the
“Related Documentation” section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.