Technical data

Chapter 3
Diagnostics
HP bc2100 ATCA Server Blade Diagnostics Syntax and Semantics of UI
156
t Summary File
The summary file (by default called summary.txt) is a text file that records the cumulative test results for
all invocations of the Test Executive. In the file, there is a line for each test that summarizes the number of
passes, failures, and errors that each test has reported. The format of the file is as follows:
---Module.Subtest--------------------Pass Fail Errors Last Updated::
Modulename.testname ##### ##### ##### MM-DD-YYYY HH:MM:SS
NOTE The summary file is cumulative across Test Executive invocations, so to reset the counters, the
file must be deleted.
Environment Variable Return Code
The environment variable MTA_RETURN_CODE is set to “0” if all the tests are successful, and a non-zero value
if any tests report a failure. The value is also available in the $? environment variable.
Tests and Subtest Descriptions
Descriptions and information on the available tests can be found in the module help (*_hlp.text) files in
the Service OS. A subdirectory “module help files” will be installed in the test directory
(/opt/intel/bdp/common/iMTA-1.5) with a help text file for each test module. Please refer to the
installed help files for the updated descriptions of the available tests.
XTC Graphical User Interface
The BDP interface is the recommended method to invoke MTA. There is also an iMTA utility that can be used
as a stand-alone utility (without the BDP interface) for advanced options. Bypassing the BDP interface may
limit the additional interface capabilities provided by the BDP interface.
The iMTA utility has two user interfaces. This chapter describes XTC, which is a Graphical User Interface
(GUI). The previous chapter, ““t” Command Line Interface” describes the “t” interface, which is a Command
Line Interface (CLI).
The XTC GUI requires a working X server on the client machine.
NOTE The autoconfigure feature of iMTA scans all the hardware present on the Server Blade.
Therefore, it is recommended to populate the board with all standard hardware configuration
before running the XTC program (or the “t” program) to create or modify configurations.
Prerequisite to Using the XTC Program
To use the XTC (X-windows Test Control) GUI program, it is necessary to have X server running on your
client machine. Any X server that supports the X11R6 protocol should be sufficient. Examples of X servers are
the standard X-server on Linux/UNIX desktops and workstations. Examples of X-servers running on
Windows clients are Hummingbird or Cygwin-X.
The following is an example of how to start XTC from an X-server desktop:
1. Boot the Server Blade into the Service OS. Write down the host name or IP address of the Server Blade.
Also write down the X-server’s IP address
2. Start a new “xterm” window on your X-server.