Cisco UCS Server Configuration Utility, Release 3.0 User Guide
Using Diagnostic Tools
Downloads: This chapterpdf (PDF - 63.0KB) The complete bookPDF (PDF - 1.35MB) | Feedback

Using Diagnostic Tools

Table Of Contents

Using Diagnostic Tools

Quick Test

Comprehensive Test

Quick Tasks

Tests Suite

Tests Log Summary

Tests Summary


Using Diagnostic Tools


You can use diagnostics tools to diagnose hardware problems with your Cisco servers. The user interface displays the status of the test run and examines log files for troubleshooting hardware issues.

Diagnostic tools allows you to:

Run tests on various server components to find out hardware issues along with analysis of the test results in a tabular format.

Run all the tests using the Quick Tasks functionality without browsing through available tests.

Run tests serially, as running some tests in parallel may interfere with other tests.

Configure the test by entering different argument values other than the default ones.

Select tests you want to run using the Test Suite functionality.

Save all the tests logs such SEL logs to an external USB flash drive.

Probe the current state of the server and view hardware issues.

The table below details when you should use a specific diagnostic functionality:

Table 7-1 Using Diagnostics

Diagnostic Component
Usage

Quick Test

Use this test when you want to quickly check the status of a sub-system within a stipulated period. The components that can be tested under the quick test are - processor, cache, memory, disk, video, network, QPI, CIMC, RAID and chipset.

Comprehensive Test

Use this test when you want to test a sub-system elaborately. These tests are designed to stress the sub-systems and report the error. The tests that can be run are - processor, memory, QPI, disk, and NUMA.

Quick Tasks

Allows for consolidated testing of both comprehensive and quick tests. You can run both types of tests using quick tasks.

Test Suite

All the tests available under the quick and comprehensive test are available here. The test suite gives you an option to pick as many tests as you like (using a check box) and running them together.

Tests Log Summary

Use the test log summary to view the log, error log and analysis of all the tests you have run. There are four filters you can use to sort the logs.

Tests Summary

This table on the left hand navigation gives you the results of the tests you have run in the form of either passed tests, tests in queue and failed tests.


This chapter contains the following sections:

Quick Test

Comprehensive Test

Quick Tasks

Tests Suite

Tests Log Summary

Quick Test

You can run these tests quickly to determine any hardware issue. These tests usually take 20-30 minutes to run and test limited functionality for a few subsystems. The comprehensive test provides more exhaustive diagnostics.

To run the quick test follow these steps:


Step 1 Click Diagnostic Tools from the left navigation pane.

Step 2 Click Tests.

Step 3 Click the Quick Test collapsible button to view the types of quick tests available for you to run.

Step 4 Click a subsystem (like memory, video, or network).

Step 5 On the content pane, click Run Test.

Step 6 If you click Run Test, the test is run and the status displays in the Tests Status area.

The table below describes the sub-systems covered under quick tests:

Table 7-2 Quick Tests

Test
Description

Processor Test

Runs processor specific tests. This test performs arithmetic and floating point operations on all available cores. You can also specify the duration of the tests

Cache Test

Runs test to exercise the CPU caches and checks for correctable/uncorrectable cache errors.

Memory Test

Tests DIMMs and memory controllers.

Disk Test

Tests the available disks in the system by reading each disk block-by-block.

Video Test

Test to stress the Video Memory.

Network Test

Tests the available network interfaces by running internal loopback test, register test, eeprom test and interrupt test.

QPI Test

Tests the Quick path interconnect fabric.

CIMC Test

Runs CIMC self test through the IPMI interface and also checks for SEL fullness.

Chipset Test

Runs a test to check the chipset for any errors logged in the chipset RAS registers.

RAID Adapter Test

Runs test to check the LSI MegaRAID 9260-8i and 8708 controller and battery backup unit diagnostics.


Comprehensive Test

The Comprehensive test can run for hours and usually runs when quick tests cannot diagnose the issue with your server. They are designed to test multiple hardware components and find issues that may be caused due to multiple components on your server.

The individual tests run can be customized to test some user-defined conditions. You can also select a group of tests to be run.

To run the comprehensive test, follow these steps:


Step 1 Click Diagnostic Tools from the left navigation pane.

Step 2 Click Tests.

Step 3 Click the Comprehensive Test collapsible button to view the types of comprehensive tests available for you to run.

Step 4 Click a subsystem (like processor, memory, or network).

Step 5 On the content pane, click Run Tests.

Step 6 If you click Run Tests, the test is run and the status displays in the Tests Status area.

The table below describes the sub-systems covered under comprehensive tests:

 

Table 7-3 Comprehensive Tests

Test
Description

Processor Stress Test

Imposes maximum stress on CPU and memory on the system. You can set the time (in minutes) you want this test to run for.

Memory Pattern Test

Tests the available free memory by writing and reading various patterns to the memory.

QPI Stress Test

Runs test to stress the QPI interconnect by generating traffic between the NUMA nodes.

Smart Disk Test

Tests the available disks in the system by reading each disk block by block

NUMA Test

Runs test to stress the NUMA memory access patterns and check for errors.

VDisk Stress Test

Runs test to stress the virtual disks in the system. This test runs for a longer time, depending on the size of the virtual disk.


Quick Tasks

Quick Tasks allow you to get started with diagnostic tools immediately. You can run all the tests (Quick/Comprehensive) from here and report the details to Cisco to troubleshoot the logs and provide information about problems with your system. To use this feature, follow these steps:


Step 1 Click Diagnostic Tools from the left navigation pane.

Step 2 Click Quick Tasks.

Step 3 Click either Run Quick Tests or Run Comprehensive Test from the toolbar. The status appears in the Test Status pane. You can also view detailed test results under Tests log summary.

Tests Suite

The Test Suite allows you to run the quick test and comprehensive test in a batch. It lists the various tests available, along with the test type and description of the test. You can select any number of tests you want to run from the list and view the result in the Tests Status column.

To run the test suite, follow these steps:


Step 1 Click Tests Suite from the left navigation pane.

Step 2 Select the tests you want to run by clicking the required checkboxes.

Step 3 Click Run Tests Suite to run the tests you added to the test suite. The status appears in the Tests Status pane along with the name, suite ID, Result, start time and end time. You can also view the Tests Log Summary to view the execution status of the tests in the test suite.


Tests Log Summary

Use the Tests Log Summary functionality to examine the test logs for troubleshooting. To view the Tests Log summary, follow these steps:


Step 1 Click Diagnostic Tools on the left navigation pane.

Step 2 Click Tests Log Summary on the left navigation pane.

Step 3 Select a filter from the filter drop-down and click Go. The status, result, start time, and end time of the test displays.

Step 4 For more details, click a specific log entry (for example, click memory test). The Log, Error Log (if the test failed) and the analysis of the specific test displays in the content pane.


Tests Summary

The Test Summary table in the left navigation area provides you with a quick view of the tests that have passed, tests in queue and tests that have failed.