Intel® Direct Platform Control Console
and Platform Diagnostics
User’s Guide
Version 4.0
Printed in June 2001
Notice
The information contained in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not
limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-
Packard shall not be liable for errors contained herein or for incidental or consequential damages in
connection with the furnishing, performance, or use of this material.
This guide has been reprinted with the permission of Intel Corporation. Hewlett-Packard assumes no
responsibility for the use or reliability of this software on equipment that is not furnished by Hewlett-Packard.
Information in this document is provided in connection with Intel® products. No license, express or implied,
by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided
in Intel's Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel
disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or
warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent,
copyright or other intellectual property right. Intel products are not designed, intended or authorized for use
in any medical, life saving, or life sustaining applications or for any other application in which the failure of
the Intel product could create a situation where personal injury or death may occur. Intel may make changes
to specifications and product descriptions at any time, without notice. No part of this document may be
copied or reproduced in any form or by any means without prior consent of Intel.
This document contains proprietary information that is protected by copyright. All rights are reserved. No
part of this document may be photocopied, reproduced, or translated to another language without the prior
written consent of Hewlett-Packard Company.
Intel, Pentium, and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in
the United States and other countries.
†
All other brand and product names are trademarks of, and are used to identify products of, their respective
owners.
Hewlett-Packard Company
Network Server Division
Technical Communications/ MS 45SLE
10955 Tantau Avenue
Cupertino, California 95014 USA
© Copyright 2001, Hewlett-Packard Company.
Audience Assumptions
This guide is for the person who installs, administers, and troubleshoots LAN servers. Hewlett-Packard
Company assumes you are qualified in the servicing of computer equipment and trained in recognizing
hazards in products with hazardous energy levels.
ii
Contents
1 What’s Direct Platform Control Console?............................................................................................1
2 Client Workstation Requirements.........................................................................................................3
3 Server Requirements .............................................................................................................................5
Serial Connections ....................................................................................................................................5
LAN Connections ......................................................................................................................................5
Configuring the Connection....................................................................................................................... 5
System Setup Utility (SSU)...................................................................................................................5
BIOS Setup and Console Redirection ..................................................................................................5
Server Management Configuration (SMConfig) Utility..........................................................................6
4 Starting the DPC Console......................................................................................................................9
5 Connecting to a Managed Server .......................................................................................................11
6 Accessing DPC Console Features......................................................................................................13
7 Phonebook ............................................................................................................................................15
Adding a Server ......................................................................................................................................15
Deleting a Server ....................................................................................................................................15
8 SEL Manager ......................................................................................................................................... 17
9 SDR Manager ........................................................................................................................................19
10 FRU Manager.........................................................................................................................................21
11 RSA Manager ........................................................................................................................................23
12 Rebooting to the Service Partition .....................................................................................................25
Requirements .......................................................................................................................................... 25
Booting ....................................................................................................................................................25
Accessing Service Partition Features .....................................................................................................25
13 Displaying Configuration Status.........................................................................................................27
14 Disconnecting from a Managed Server..............................................................................................29
15 Platform Compatibility Matrix..............................................................................................................31
16 Using SR460AC4 Platform Diagnostics .............................................................................................35
1. QUICK START ....................................................................................................................................35
2. INVOKING THE APPLICATION .........................................................................................................35
3. UNDERSTANDING THE GENERAL USER INTERFACE..................................................................36
4. UNDERSTANDING APPLICATION OPTIONS .................................................................................. 36
5. ENABLING TESTS FOR EXECUTION............................................................................................... 36
6. SETTING TEST PARAMETERS ........................................................................................................37
7. INTERPRETTING RESULTS .............................................................................................................37
8. GETTING HELP ON INDIVIDUAL TESTS .........................................................................................37
9. VIEWING SYSTEM CONFIGURATION .............................................................................................37
10. VIEWING THE TEST LOG ...............................................................................................................37
iii
1 What’s Direct Platform Control Console?
Direct Platform Control (DPC) console is an application that allows remote server management. Depending
on the platform on which you are installing and running DPC, the features can vary. For information on DPC
feature availability, refer to Table 2 on page 31.
DPC contains a security feature that requires a password entry before initiating a connection to a managed
server. DPC runs on a client workstation and communicates with managed servers through any of the
following:
• A Windows NT
• A direct RS-232 connection to the server COM2 port
• A LAN connection
DPC console operation is independent of the state of the managed server’s operating system. As long as the
managed server is plugged into power receptacles, you can use DPC Console to:
• Establish or end a connection to a remote server.
• Power on a remote server.
†
, Windows† 2000 compatible modem
• Power off a remote server.
• Perform a reset operation on a remote server.
• Retrieve and display:
o System Event Log (SEL) entries for information about recent server activities, such as from
processors or fans.
o Sensor Data Records (SDR) entries for information about sensor characteristics.
o Field Replaceable Unit (FRU) inventories of the hardware components on the server.
o Remote Sensor Access (RSA) information such as current and voltage readings.
• Reboot the managed server to the service partition. When you boot a managed server to the service
partition you can do the following:
NOTE This feature is not supported on this release of the software. Please refer to the HP web
site at http://www.hp.com/ for the latest release.
o Run diagnostics on the managed server.
o Transfer files to and from the managed server.
o Run the managed server’s shell program.
o Run service partition based utilities located on the managed server.
• Maintain a Phonebook for remote server connection management.
1
2 Client Workstation Requirements
The following lists the minimum internal memory and hard drive space requirement for the client workstation
to run DPC:
• Windows NT 4.0 with Service Pack 6 or later
o 24 MB of RAM, 32 MB recommended
o 150 MB disk space
o Remote Access Service (RAS) must be installed
• Windows 2000
o 24 MB of RAM, 32 MB recommended
o 150 MB disk space
• Windows 2002
o 24 MB of RAM, 32 MB recommended
o 150 MB disk space
If the client workstation uses a modem for communications, the maximum modem speed must be set to
19.2K. The DPC Console uses the Windows Application Programming Interface (API) to determine if a
modem is connected and available. However, the console will not configure the modem. Any COM port on
the remote workstations can be used.
3
3 Server Requirements
The DPC console connects to servers with server management capabilities (managed servers). Any operating
system can be running on the server. If DPC connects to the server using a serial (modem or direct)
connection, the server’s Emergency Management Port (EMP) features are used. If DPC connects to the
server using a LAN connection, the server’s BMC LAN-Alert (BLA) features are used. Both server feature
sets require setup using these utilities, depending on your server features:
• BIOS Setup for IA-32 managed servers
• System Setup Utility (SSU) for IA-32 managed servers
• Server Management (SM) Configuration Utility for Itanium™-based servers
Serial Connections
If the server connection is by external modem or null-modem RS-232 serial cable, you must use the managed
server’s COM2 port. If the connection is by modem, you must use a Hayes-compatible modem listed on the
NT Hardware Compatibility list provided by Microsoft. Servers that are Intelligent Platform Management
Bus (IPMI) 0.9 servers require a modem speed of 19200 BPS.
LAN Connections
No external hardware requirements exist for LAN connections between the managed server and the client
workstation running DPC. The on-board Network Interface Card (NIC) is used for communication.
Configuring the Connection
Depending on the managed server and the connection type, you use different methods to configure the
connection between the workstation running DPC and the managed server. Table 1 shows these methods:
Table 1 Methods for Configuring a Connection
Managed Server Serial Connection LAN Connection
IA-32 Platforms System Setup Utility (SSU)
BIOS Setup for Console Redirection
Itanium-based Platforms Server Management Configuration
(SMConfig)
System Setup Utility (SSU)
SSU is used to configure all Emergency Management Port (EMP) settings for serial connections and all
Baseboard Management Controller (BMC) LAN settings for LAN connections. For details on how to use
SSU and for the settings you need to configure serial connections, see the server product guide for the
particular managed server.
BIOS Setup and Console Redirection
System Setup Utility (SSU)
Server Management
Configuration (SMConfig)
BIOS setup is used to enable or disable console redirection on the managed server. Using this method to
enable or disable console redirection applies only to IA-32 managed servers that have a serial connection to
the workstation running DPC. Furthermore, console redirection configuration using this method is only
effective when you
• Reboot the managed server from DPC.
• Power on the managed server from DPC.
For the case when you use DPC to boot the managed server to its service partition, console redirection is
always enabled regardless of how you have configured it in BIOS setup.
5
Chapter 3 Server Requirements
Do the following steps on the managed server to configure console redirection in BIOS Setup:
1. Press the <F2> key while the managed server is booting.
2. Select the System Management menu.
3. Select the Console Redirection menu.
4. For Com Port Address, select COM2 2F8 IRQ3. This is the COM2 port that the Emergency
Management Port (EMP) must use.
5. For Baud Rate, select 19.2K.
6. For Flow Control, select CTS/RTS + CD.
7. Save your changes and exit BIOS Setup.
Server Management Configuration (SMConfig) Utility
The SMConfig utility configures all EMP settings for serial connections and all BMC LAN settings for LAN
connections for Itanium-based managed servers. Depending on the type of connection (serial or LAN), you
need to perform different steps to configure the connections. However, it is convenient to configure the
settings for both types of connections during the same SMConfig session.
To run SMConfig from the Resource CD, copy the folder containing the SMConfig files to a 3.5-inch
diskette.
Configuring LAN Connections
Follow these steps to configure the LAN connection.
1. Boot the managed server to the Extensible Firmware Interface (EFI) shell.
2. Insert the diskette that contains the SMConfig software into the server’s LS120 drive.
3. Enter smconfig to invoke the SMConfig Utility.
4. Use the arrow keys to highlight the Config menu and press <Enter> to reveal the menu’s items.
5. Use the down arrow to highlight the DPC/LAN item and press <Enter>.
6. Use the arrow keys to do the following:
o Set LAN Access Mode to Enable
o Set the Host IP Address, Subnet Mask and Gateway IP Address to appropriate values
o Set the Alert IP Address to the IP Address of the workstation running Intel® Server Control
software to which the server will send alert notifications
o Set the SNMP Community String to Public
7. Set a password for the managed server. Whenever a user tries to connect to the server using a LAN
connection, they must supply this password to gain access to the server. To set the password, click Set
Password and follow the screen directions.
8. Click Save to save your changes.
9. Click OK to get back to the SMConfig Utility main screen.
Configuring Serial Connections
Serial connections consist of connections through a modem or a direct connection through a null-modem
cable. Follow these steps to configure serial connections.
1. Boot the managed server to the Extensible Firmware Interface (EFI) shell.
2. Insert the diskette that contains the SMConfig software into the server’s LS120 drive.
3. Enter
smconfig to invoke the SMConfig Utility.
4. Use the arrow keys to highlight the Config menu and press <Enter> to reveal the menu’s items.
6
Chapter 3 Server Requirements
5. Use the down arrow to highlight the EMP item and press <Enter>.
6. Use the arrow keys to do the following:
o Set Access Mode to Active
o Set Restricted Access Mode to Disable
o Set Connection Mode to Modem Connect
o Set DCD Mode to Enabled
o Set the Baud Rate to 19200
o Set Flow Control to Disabled
7. Set a password for the managed server. Whenever a user tries to connect to the server using a serial
connection, they must supply this password to gain access to the server. To set the password, click Set
Password and follow the screen directions.
8. Click Save to save your changes.
9. Click OK to get back to the SMConfig Utility main screen.
7
4 Starting the DPC Console
You can start the DPC Console on the client workstation several different ways.
• From a Windows-based operating system you can use Programs Intel Server Control DPC
Console selection from the Start menu.
• From a running ISC Console you can double-click the icon that represents the DPC Console.
• From a shell environment you can use the following command lines:
• DPCConsole /modem=[phonenumber], where [phonenumber] is the phone number of the server.
• DPCConsole /direct= [comX], where [comX] is the COM port of the client workstation direct
connection.
• DPCConsole /lan=[ipaddress or dnsname], where [ipaddress or dnsname] is the IP Address DNS Name
of the server.
• From a supported Enterprise System Management Console (ESMC) you can click the DPC Console
icon in the manager’s tool.
9
5 Connecting to a Managed Server
To connect the workstation running DPC to a managed server, you must first have configured the appropriate
connection on the server. For information on how to configure both LAN and serial connections, refer to
“Configuring the Connection” on page 5.
Follow these steps to connect to a managed server:
1. Start the DPC Console. For information on how to start the DPC Console, refer to “4 Starting the DPC
Console” on page 9.
2. Either click the telephone icon in the upper left-hand corner of the tool bar or select the File
Connection New menu item. Either action displays the Connect dialog box.
3. Click Phonebook and check if the server is listed. If the server is listed, select it and close the
phonebook dialog box. If the server is not listed, you need to add it to the Phonebook. For information
on how to add a server to the Phonebook, refer to “7 Phonebook” on page 15.
4. Select the type of connection: Modem, LAN, or Direct Port. For Direct Port make sure that you
choose the correct COM port.
5. Enter the server password. If you do not enter a password and the server is configured with one, DPC
will prompt you for the password during the connection process.
6. Click Connect. If the connection is successful, the status bar at the bottom of the console will display
the word “connected.” Also, the toolbar at the top of the console will contain enabled icons that let you
access DPC Console features.
11
6 Accessing DPC Console Features
Use the DPC Console menus or click a toolbar button to access DPC Console features. Menu items and the
toolbar change according to the available server features.
The user actions in this manual access DPC Console feature by menu item. Some of these actions can also be
accessed using the toolbar.
The DPC Console help system contains detailed information about user interface features. See the help
system for more information.
13
7 Phonebook
The DPC Console provides a phonebook that stores server names, their server phone numbers, their IP
addresses for the network card, and their server LAN addresses. The phonebook also allows you to add,
modify, or delete phonebook entries.
Adding a Server
Follow these steps to add a server to the phonebook:
1. Access the Phonebook feature.
2. Enter any string for the server name.
3. Supply a phone number, IP Address, or DNS name (any one will do).
4. Click OK.
Deleting a Server
Follow these steps to delete a server from the phonebook:
1. Access the Phonebook feature.
2. Highlight the server name.
3. Click Delete.
15
8 SEL Manager
The System Event Log (SEL) manager allows you to:
• View SEL events.
• View the properties of the non-volatile storage area for SEL.
• Save SEL events to a file.
• Print the SEL events to a local printer.
• Clear SEL records from the non-volatile storage area on a password protected server.
SEL events display as a sequential record of managed server events, one event per row. Those records
contain the following information:
• Number of Event
• Timestamp
• Sensor Type and Number
• Event description
• Generator ID
Each of the columns can be sorted by clicking on the column heading. Clicking the column heading again
sorts the column in descending order. You can also adjust the column heading width.
When the SEL manager is active, the SEL menu is added to the DPC Console menu bar between the Action
and Window menus.
17
9 SDR Manager
The Sensor Data Records (SDR) manager allows you to:
• View Sensor Data Records.
• View the properties of the non-volatile storage area for SDR.
• View SDR information in a previously stored file.
• Save SDR information to a file.
The SDR Manager displays with a navigation (tree view) pane, a presentation (grid) pane and a description
pane. Selecting a SDR from the tree view displays the corresponding SDR information in the grid. You can
resize both the tree view and the grid by using a splitter bar. You can also resize the individual data columns
within the grid.
When the SDR manager is active, the SDR menu is added to the DPC Console menu bar between the Action
and Window menus.
19
10 FRU Manager
The Field Replaceable Unit (FRU) manager allows you to:
• View some FRU inventory.
• View the properties for a FRU.
• Save FRU inventory information to a file.
The FRU manager displays a hierarchical tree of FRU areas (chassis, product, and board), and detailed
inventory information about a selected area. Select an area in the tree to see its associated inventory
information in the grid on the right. You can adjust the width of each column in the grid. A description of
each field selected in the grid displays in the right bottom pane.
When the FRU manager is active, the FRU menu is added to the DPC Console menu bar between the Action
and Window menus.
21
11 RSA Manager
The Remote Sensor Access (RSA) manager allows you to view server baseboard FRU and SDR information.
The RSA manager consists of a navigation pane (tree view) on the left and a property view on the right. The
tree view displays all detected sensors. The property view displays sensor status or sensor information for the
sensor that is selected in the tree view. Select the appropriate tab to display either sensor status and sensor
information. The displayed information depends on the selected sensor.
If the connected server is powered down, some sensors cannot be read and their current status displays as
Unknown.
When the RSA manager is active, the RSA menu is added to the DPC Console menu bar between the Action
and Window menus.
23
12 Rebooting to the Service Partition
NOTE This feature is not supported on this release of the software. Please refer to the HP web
site at http://www.hp.com/ for the latest release.
Itanium-based servers: The service partition on this type of server is not a separate partition. It is the
presence of service partition files on the existing system partition. This service partition is also sometimes
referred to as the Extensible Firmware Interface (EFI) System Partition. This service partition is established
by running the service partition installation software that copies the service partition files into the system
partition.
NOTE Please refer to the HP web site at http://www.hp.com/
installation software.
Requirements
Before you can boot to the service partition, the following conditions must be met:
• You must have established an authenticated connection between the workstation running DPC and the
managed server. EMP Restricted Access mode is not enabled on the managed server for these types of
connections.
• The managed server must contain BIOS support for booting to the service partition.
• A service partition must be installed on the managed server’s hard drive.
Booting
Follow these steps to reboot the managed server to the service partition from DPC:
1. Click the service partition icon in the toolbar or select the Action Reboot to Service Partition
menu item.
2. Click OK.
3. Click OK if you are queried to force a reset.
4. Monitor the action in the Redirection window that appears.
to download the service partition
Accessing Service Partition Features
When the reboot completes, the Service Partition menu is added to the DPC Console menu bar between
the Action and Window menus. New icons also appear in the DPC Console toolbar. Using the Service
Partition menu or the icons, you can access the following features on the service partition:
• Run the server’s shell program (DOS for IA-32 servers or EFI for Itanium-based servers).
• Run a program from the server’s hard drive.
• Run diagnostics specific to the server.
• Upload files by transferring them from the workstation running DPC to the managed server.
• Download files by transferring them from the managed server to the workstation running DPC.
25
13 Displaying Configuration Status
The Configuration dialog box displays the managed server’s configuration status. You can view this status
information whenever the DPC Console is successfully connected to a managed server through the
Emergency Management Port (EMP) or through a LAN-based form of the EMP (TCO mode).
To display the configuration status, select the Action Configuration Status menu item. Doing so
causes the Configuration information box to appear. This box displays information in several areas:
Supported Viewers: Status on the FRU, SEL, SDR, and RSA viewers.
Security: Displays the Authentication Level, Activation Mode and Chassis Intrusion setting.
• Authentication level: Indicates User or Administrator level. User level exists if you have a serial
connection through the EMP and EMP mode is set to restricted. User level also exists for LAN (TCO)
connections where a secure session is not available (e.g. someone else is already connected), or if there
is a restricted LAN access mode. Administrator level exists if you are logged in with administrative
rights.
• Activation Mode: Indicates whether the server is always active or just active during pre-boot.
• Chassis Intrusion: Indicates whether intrusion protection is set or not set.
Firmware: Displays the Intelligent Platform Management Interface (IMPI) and Baseboard Management
Controller (BMC) revisions on the server.
Aside from these designated areas, the Configuration dialog box also indicates the server’s power state, the
operating system (if detected), and the presence of a service partition.
NOTE In order for DPC Console to detect a connected server’s operating system, the server must
have Platform Instrumentation (PI) installed.
27
14 Disconnecting from a Managed Server
To disconnect the workstation running DPC from a managed server, follow these steps:
1. Either click the telephone icon (the one whose receiver is out of the cradle) in the toolbar or select the
File Connection Disconnect menu item.
2. Click Yes at the prompt to close the connection.
29
15 Platform Compatibility Matrix
Table 2 lists ISC and DPC features specific to hardware platforms. In the table, columns present grouped
platforms while rows describe specific features. More general features, which can consist of multiple specific
features, appear in bold type and span an entire row.
Table 2 Platform Compatibility Matrix
Features
HP Server rx4610
Summary
• Complete In-Band management
• Limited operating system support
Platform
31
Chapter 15 Platform Compatibility Matrix
Table 2 Platform Compatibility Matrix (cont.)
Features
Platform
HP Server rx4610
In-band Remote Management (OS based)
Desktop
Management
Interface (DMI)
Itanium™ - based
• No support
Instrumentation
Win32*
Console
Platform
Yes
• Windows 2000 with Service Pack 2
Instrumentation
Control (PIC)
32
Chapter 15 Platform Compatibility Matrix
Table 2 Platform Compatibility Matrix (cont.)
Features
Platform
HP Server rx4610
In-Band (Instrumentation based) Alerts
Network Alerts
Yes
(Popup
Messages)
DMI Indication No
SNMP Traps
No
(via DMI-SNMP
Translator)
ISC Paging Yes
BIOS Console Redirection
Over
Yes
Modem/Serial
Over LAN Yes
33
Chapter 15 Platform Compatibility Matrix
Table 2 Platform Compatibility Matrix (cont.)
Features
Platform
HP Server rx4610
Enterprise Server Management Console (ESMC) Integration’s
LANDesk®
Yes
Server Manager
(LDSM) 6.1
(Linux/UnixWar
e servers are not
discovered /
managed by
LDSM
HP OpenView
No
Network Node
Manager 6.1
CA Unicenter
No
Framework TNG
2.2
Web Browser
Yes
(Microsoft IE
5.X, Netscape
4.71)
Microsoft MMC Yes
ISC Standalone Yes
34
16 Using SR460AC4 Platform Diagnostics
The information in this chapter describes how to run and use the Platform Diagnostics application.
1. QUICK START
Use the following steps to quickly setup and run tests. For more detailed information on any of the steps,
please refer to the remainder of this guide.
1. Boot to the EFI shell.
2. Create a directory "efi\intel\service\diagnostics" on the target such as a hard drive.
3. Copy the distributed FieldDiags binary file (fielddiags.efi) to the root directory of the target.
4. Run the following command using the distributed FieldDiags binary file (fielddiags.efi):
fielddiags -d \efi\Intel\service\diagnostics
(it will unpack and install the FieldDiags software).
5. Be sure your working directory is on the same hard drive that contains the test software, type in the
following command and press the <Enter> key to load and run the tests:
\efi\intel\service\diagnostics\fielddiags
Entering this command causes the tests to run regardless of your current working directory. You can
also type a relative pathname that is based on your current working directory to execute the tests.
6. Enable the set of tests you want to run by using the arrow keys to highlight a test, and then press the
<Space> key to enable it.
7. Use the arrow keys to highlight "Run Quick Test" and then press the <Enter> key. As asterisk character
(*) appears to the left of the test that is running.
8. Refer to the "Pass" and "Fail" columns to interpret the test results.
In addition to running tests, you can display system configuration information or the current test log. To do
either, highlight the appropriate option and then press the <Enter> key.
2. INVOKING THE APPLICATION
The field diagnostics test Command-line syntax is as follows:
[path\]FIELDDIAGS [LOG [path]logfile[.log]] [CFG
[path]configfile[.cfg]]
In the above syntax, items enclosed within square brackets are optional, and items that appear in upper-case
characters must be typed exactly as shown. You must supply values for items shown in lower-case characters
as follows:
path Any valid absolute or relative pathname.
logfile The name of the log file generated during this diagnostic test session. By default, the software
creates a log file named "FIELDDIAGS.LOG" and keeps it in
"\EFI\INTEL\SERVICE\DIAGNOSTICS." If you use the LOG command-line option, you can
name and place the log file. If you do not supply a filename extension, ".LOG" is used.
configfile The name of the configuration file used to populate the interface with tests. By default, the
software uses the file named
"\EFI\INTEL\SERVICE\DIAGNOSTICS\FIELDDIAGS\FIELDDIAGS.CFG."
If you use the CFG command-line option, you can use a custom configuration file to populate
the diagnostic test interface with tests. If you do not use a filename extension, ".CFG" is used.
35
Chapter 16 Using SR460AC4 Platform Diagnostics
Following are some examples that show how to start a field diagnostics test session.
This first example works regardless of your current working directory. The software uses the default
configuration file and creates a default log file.
\EFI\INTEL\SERVICE\DIAGNOSTICS\FIELDDIAGS
This next example assumes your working directory is "\EFI\INTEL" and specifies a custom configuration file
named "MYCONFIG.CFG" located in a directory named "MYDIR":
SERVICE\DIAGNOSTICS\FIELDDIAGS CFG DIAGNOSTICS\MYDIR\MYCONFIG
This last example assumes your working directory is in the same directory as the test software and you are
using the custom configuration file used in the previous example. This example also creates a log file named
"MYLOGFILE.LG1" in a directory named "MYDIR":
FIELDDIAGS LOG ..\MYDIR\MYLOGFILE.LG1 CFG ..\MYDIR\MYCONFIG
3. UNDERSTANDING THE GENERAL USER INTERFACE
The platform diagnostics application uses a single screen from which you can choose execution options,
enable or disable tests for execution, and define test parameters. The screen consists of four areas from top to
bottom:
1. Execution Options
2. Test Selection and Results
3. Test Parameters
4. User Interface Help
Up and down arrows navigate vertically through all areas of the screen except for the User Interface Help
area. During navigation, items that you can modify become highlighted. Additionally, in the test selection
area, the greater-than character (<) also appears to the left of any highlighted test. Left and right arrow keys
navigate horizontally through the Execution Options and the Test Parameters areas.
Pressing the <Enter> key with an execution option highlighted causes the action to occur.
Pressing the <Enter> key from within a dialog box causes data to be entered.
Pressing the <F1> key while a test is highlighted or has the greater-than character (>) to the left of it causes
on-line help for that test to appear.
Pressing the <ESC> key with on-line help displayed or with a dialog box displayed dismisses the information
or dialog box.
4. UNDERSTANDING APPLICATION OPTIONS
There are four application options currently:
1. Run Quick Test - This option runs a partial set of a test's sub-test list, or the complete sub-test list but
using fewer built-in test parameters.
2. Run Comprehensive Test - This option runs a test's complete sub-test list and uses a comprehensive set
of built-in test parameters.
3. View System Configuration - Displays information about the server's configuration.
4. View Complete Test Log - Displays the current test log.
5. ENABLING TESTS FOR EXECUTION
To enable one or more tests for execution, use the up and down arrows to first select a test, and then press the
<Space> key to enable the test. Pressing the <Space> key multiple times toggles the test between enabled and
disabled. When a test is enabled, the word "Yes" appears next to the test under the "Enabled" column. If a
test is disabled, the word "No" appears under that column.
36
Chapter 16 Using SR460AC4 Platform Diagnostics
Because of space limitations, the test area of the screen displays only eight of the ten tests at a time. Using
the arrow keys will cause the test display to scroll completely through the list.
NOTE You must select all the tests you want to run before you run the tests (highlighting and
executing the application option).
6. SETTING TEST PARAMETERS
You can define two parameters for test execution: loops and test time. A loop completes when all enabled
tests execute once. Test time starts with execution of the first loop and runs continuously as long as tests are
being executed.
To set the loop count or execution time, use the arrow keys to highlight the appropriate parameter and then
press the <Enter> key. The application presents a dialog box in which you can enter the data (number loops
or time in minutes). Entering a zero for either parameter causes the application to ignore the parameter.
Running a set of selected tests always causes the application to complete at least one loop. Upon completion
of each loop, the application checks to see if more loops are required and also checks to see if execution time
has exceeded the test time parameter. If all of loops have been executed or if execution time has exceeded the
test time parameter, test execution halts.
7. INTERPRETTING RESULTS
Test results appear next to the enabled tests in the test area of the screen. Each time a test passes or fails
during a loop, the appropriate pass or fail count increments. For failed tests, Field Replaceable Unit (FRU)
information also appears under the "Details" column.
If you want greater detail for the test run, view the test log file. For information on how to view the test log
file, refer to Section 10.
To clear test results, you must exit the Platform Diagnostics application.
8. GETTING HELP ON INDIVIDUAL TESTS
To display on-line help text files for a particular test, use the arrow keys to highlight the desired test and then
press the <F1> key. The application presents a scrollable text file that describes the sub-tests for the
highlighted test.
9. VIEWING SYSTEM CONFIGURATION
To view system configuration, use the arrow keys to highlight the appropriate option and press the <Enter>
key. It does not matter if you have tests enabled when you view system configuration.
After pressing the <Enter> key, the application displays a scrollable information box that contains system
information.
10. VIEWING THE TEST LOG
By default, the diagnostic software keeps the log file in "EFI\INTEL\SERVICE\DIAGNOSTICS" in a file
named "FIELDDIAGS.LOG." To view this file, use the arrow keys to highlight the appropriate option and
press the <Enter> key. It does not matter if you have tests enabled when you view the test log.
After pressing the <Enter> key, the application displays a scrollable information box that contains the
sessions test log. Because the log file is a Unicode file, you can also view it in the EFI shell by using the
"type -u" command, and in the Windows operating system using the Notepad application.
When you start a new diagnostics session, the software deletes the existing default log file
(FIELDDIAGS.LOG) in the directory "EFI\INTEL\SERVICE\DIAGNOSTICS." Consequently, if you want
37
Chapter 16 Using SR460AC4 Platform Diagnostics
to keep an existing default log file you must rename or copy the file before invoking the diagnostic tests a
subsequent time.
When you run subsequent tests within the same diagnostic test session the software appends information to
the existing log file.
As an alternative to renaming or moving a default log file, you can use the LOG command-line option when
you invoke the diagnostic test software to create and place the generated log file. See section 2, "INVOKING
THE APPLICATION" for more information.
38
Loading...