mstm Online Help

STM: Support Tools for HP Computers (logo)

mstm Online Help

On Tasks

Preparation
Running Tools
Getting Information
Troubleshooting STM)

On Item

Main Window
System Map

On Menus and Commands

File
System
Device
Tools
Options
Help

On Help
Shortcuts to Commonly Used Functions
Using the keyboard to navigate the screen

The Support Tools Manager (STM) allows you to run various support tools on one or more PA-RISC/IA64 machines. Support tools include information modules, verifiers, diagnostics, exercisers, firmware update tools, expert tools, and utilities.
When you run mstm, the program displays a system map (device map) showing the devices configured on the Unit Under Test or UUT (for more information, see User Interface (UI) and Unit Under Test (UUT)).
Select devices by moving the cursor with the up and down arrow keys to the line entry for the device(s) and hitting the "Return" key. Choose the desired operations to perform on the selected devices by using (see pulldown menus) and function keys. Typical operations are verifying devices and viewing Failure Logs.
The results of a running a tool are reflected by changes in the "Last Op Status" column of the device map:

"Success" means a tool successfully completed an operation on the device.
"FAILURE" means a tool detected a device failure; view the Failure Log to determine appropriate corrective action.
"INCOMPLETE" means a tool was not able to complete its operation; view the tool's Activity Log for more information.

You can run the mstm interface on one machine, and use it to run support tools on one or more remote machines (Units Under Test, or UUTs). Alternatively, you can run the mstm interface on one machine, and use it to run support tools on the same machine (i.e., the machine running mstm and the UUT are one and the same).
The mstm program is the menu interface for the STM. Two other STM interfaces are available:

xstm -- the X-Windows graphical interface
cstm -- the command line interface

On User Interface (UI) and Unit Under Test (UUT)
STM has been designed so that the support tools can be run on the local machine or on remote machines.
The computer running the user interface is the UI system, and the computer being tested is the Unit Under Test or UUT.
You can run the user interface and the support tools on the same machine. In this case, the UI machine and the UUT are one and the same.
You can also run the STM user interface on one machine, and from it, run support tools on one or more remote machines.

User Interface (UI): The computer system on which the user interface resides. On the UI machine, the user views a system map of the UUT and selects STM commands.
Unit Under Test (UUT): The computer system which is being tested by the tools running under the UI. The UUT may be the same machine which is running the UI, or a different machine.

Top

On Tasks

Preparing to Run a Tool

Select a Remote System(s) to Test
Install/Deinstall Support Tool Licenses
Select/Deselect Test Options
Select Device(s)

Running Tools

Get Information on a Device
To Run a Go/No Go Test on Selected Hardware (Verify)
Isolate Hardware Errors to the FRU Level (Diagnose)
Locate Intermittent Hardware Problems (Exercise)
Update the Firmware on a Specific Device
Run Non-Device-Specific Support Tools (Utilities)

Getting Information

View Device Status
View the Failure Log
View a Tool's Activity Log
View STM Logs (All Available)

Troubleshooting STM

Troubleshooting the Support Tools Manager

Top

Select a Remote System(s) to Test

By default, the test system (Unit Under Test) is the same as the computer system running the user interface.
To select a remote system for testing, do the following:

Select the "System" pulldown menu.

Select Sel Sys to Test.

Select Connect.
You will see a dialog displayed, containing a list of test systems to choose from, the operating system (OS) they are running with their revision levels, and one of six statuses:

Blank: The status is blank immediately after the test system is added, but before it is connected.

Connected: The test system is connected, but its state is not being displayed.

Current: The test system is connected, and the mstm displays reflect the state of this system.

Unavailable: The system could not be connected due to an error.

Not Responding: The system could not be connected due to a problem with the network.

Disconnected: The system has been disconnected.

To select a system, move the cursor to its entry in the list, and hit "Return".

If you wish to add a new system to the list, type the system network name (e.g., "system5.cup.hp.com") in the "Test System to Add" field and hit "Add" or "Return").
If you wish to delete a system from the list, move the cursor to its network name in the "System to Test" list and then hit "Delete".

Once you have selected, added, and/or deleted the test systems you wished to choose, hit "OK".

A dialog is displayed, which prompts you for the logon and password for the system specified at the top of the dialog. Enter the requested information, and hit "OK".
NOTE: When a system is made the current test system, it is automatically connected to the User Interface (UI), if it is not already connected.

To connect to multiple systems:

Select the "System" pulldown menu.

Select Sel Sys to Test.

Select Connect. A dialog similar to the one you saw for the Current System function will be displayed; it is edited in exactly the same manner, with one major exception: you can select multiple systems to be "current" at one time.

Selecting a test system, unselects all other test systems. To select additional test systems, without unselecting the test system you have just chosen, hold down the CTRL or SHIFT key when clicking on the names of additional test systems you wish to select.

To disconnect from one or more systems:

When you wish to disconnect a system(s) from the User Interface (UI), go back to the "system" function key screen and select "sel sys to test".

Select Disconnect.
You will see a dialog displayed, which is similar to those you have seen displayed for "current system" and "current system" functions. You may select one or more systems for disconnection, using the SHIFT or CNTRL keys. (Hold down the CTRL or SHIFT key when moving the cursor to the names of additional test systems you wish to select.)

Once you have selected the system(s) you wish to disconnect, hit "OK".

If a system you have chosen to disconnect has currently active interactive tools, you will be cautioned that disconnecting the system will cause those tools to abort. If you wish to disconnect the system anyway, hit "Continue".

Top

Install/Deinstall Support Tool Licenses

Most support tools do not require a support tool license. A few of the advanced tools (for example, expert tools) require a license from HP.
The following procedure tells you how to install and deinstall support tool licenses:

Select the System Menu.

Select Install.

Select Install or Install HP-Only, depending upon your licensing privileges (only HP personnel should select "install hp only").

Enter your password.

Hit "OK".
NOTE: If you selected "install", your permissions are only valid on the current test system.
If you selected "install hp only", your permissions are valid on all test systems accessible to the user interface, until the user interface is exited. Your permissions are only valid on the system running the user interface during the current test session.

To deinstall all licenses on the current test system (including any HP-Only licenses on the system), return to the Install cascade menu selection.

Click on Deinstall.
A popup dialog box is displayed, cautioning you of the consequences of continuing with the deinstall process, and asking you if you wish to continue or cancel.

Click on "Continue".

To deinstall all licenses on the current test system (including any HP-Only licenses on the system), return to the screen containing the "license" function key.

Select "license".

Select "Deinstall".
A popup dialog is displayed, cautioning you of the consequences of continuing with the deinstall process, and asking you if you wish to continue or cancel.

Hit "Continue".

Top

Select/Deselect Test Options

You can modify the behavior of tools by setting test options at the user interface. For example, you can set an option for all exercisers to loop continuously when they are run.
To select and set test options, do the following:

Select the Options Menu.

Select the Tool Options function key.

Select the function whose options you wish to change; for example, you might select "Verify", and the "Verify Options" dialog box will then be displayed.

Select the options you desire by placing an "x" in the appropriate checkbox(es).
WARNING: When you disable the "User Queries" function, some tools will perform DESTRUCTIVE tests. This means that ALL DATA on unmounted disks WILL BE DESTROYED. The ability to disable this function is intended for manufacturing purposes only. It is highly recommended that you use the "User Queries" function, and DO NOT DISABLE IT.

Click on "OK".

Top

Select Device(s)

Before you can run a tool, you select the device or devices on which the tool is to be run. You can select a device in several different ways:

To select a specific device for testing, move the cursor to its line entry in the device map and hit "Return".

To select multiple devices for testing, use the "Shift" or "Ctrl" key after making your first selection, and continue to do so until you have selected all the systems you wish to test; then hit "Return".

To select all devices in the hardware map for verification, select Select All.

More advanced methods for selecting devices:

To select only specific device types in the hardware map for verification, select Unselect All; then select Select Class.

To select specific device types in the hardware map for verification, in addition to devices previously selected, select "select class".

To unselect specific device types in the hardware map, while leaving other devices/device types selected for verification, select Unselect Class.

NOTE: If you choose Select Class" or Unselect Class, a dialog will be displayed, prompting you to enter the appropriate device class qualifiers; enter the information requested, and hit "OK" when you are done.

Top

Get Information on a Device

To get information about a hardware device(s), run an information tool:

Select Device(s).

If desired, Select/Deselect Test Options.

Select the "tools" pulldown menu.

Run Information and consult the Information Log.

Go back to the top level menu, and select the "device" pulldown menu.

Run Curr Dev Status to display the list of tools installed for a device, in addition to obtaining information about the device.

To see the device information obtained by the information tool, see the Information Log.

Top

To Run a Go/No Go Test on Selected Hardware (Verify)

To quickly determine whether or not a selected hardware device(s) is usable (for example, on system bring-up or after adding a new device to your configuration), run a verifier on the device:

Select Device(s).

If desired, Select/Deselect Test Options.

Select the "Tools" pulldown menu.

Select the Verify key.

Select Run.
The status information in the rightmost column of the device map will change, depending upon the state of the device, and the result of the verification procedure. You should see the status change to SUCCESS if the verification procedure is successful.

For more detailed information on test results, go to the screen containing the Device Menu function key and select "device".

Select Curr Dev Status.
You will see a display, which will inform you of the results of the verification procedure (e.g., "Success" or "Failure"), and will recommend further action, as appropriate.

Top

Isolate Hardware Errors to the FRU Level (Diagnose)

To determine whether or not a selected Field Replaceable Unit (FRU) is failing, run a diagnostic tool on the device:

Select Device(s).

If desired, Select/Deselect Test Options.

Select the Tools Menu.

Select Diagnose.

Select Run.

Select the Device Menu.

Select Curr Dev Status.

The display will inform you of the results of the diagnosis procedure (e.g., "Success" or "Failure"), and will recommend further action, as appropriate.

Top

Locate Intermittent Hardware Problems (Exercise)

To locate intermittent problems in a hardware device(s), run an exerciser on the device(s) :

Select Device(s).

If desired, Select/Deselect Test Options.

Select the Tools Menu.

Select Exercise.

Select Run.

Select the Device Menu.

Select Curr Dev Status.

The display will inform you of the results of the exercising procedure (e.g., "Success" or "Failure"), and will recommend further action, as appropriate.

Top

Update the Firmware on a Specific Device

To update the firmware on a specific device, run a firmware update tool on the device:
NOTE: The firmware update process is device-specific. This means that while the user interface to the update process remains consistent, the specifics of the process for a given device may vary considerably. This procedure is an example only, using a SCSI disk.
CAUTION: Be sure that you put the firmware file on the UUT (for example, with FTP), before starting the update process.

Select Device(s).

If desired, Select/Deselect Test Options.

From Tools Menu, invoke the "Update" command.
A new screen will be displayed, with its own function keys.

Use the File Menu to select the file containing the device firmware.
CAUTION: Make sure that you select the correct firmware file for the device! Updating a device with incorrect firmware can make the device permanently unusable and data could be lost.

From the "Update" menu select "Start Update...".
CAUTION: If absolutely necessary, you can select "interrupt" or "abort" during the update process; however, it is not advisable.

Top

Run Non-Device-Specific Support Tools (Utilities)

To run non-device-specific support tools (utilities), do the following:

Select Device(s).

If desired, Select/Deselect Test Options.

From the Tools Menu invoke the utility options.
The "Run Utility" screen will be displayed, prompting you to select a utility from a list of all utilities for which you have licensing privileges.

Select one utility (only one utility may be selected at a time), and hit "OK".

Top

View Device Status

The fastest way to determine the status of a device is to examine the the rightmost column of the system map display. For more information, you can view the Current Device Status:

Select the Device Menu.

Select Curr Dev Status.
A display will inform you of the results (e.g., "Success" or "Failure") for the most recently executed tool, and will recommend further action, as appropriate.
Top

View the Failure Log

When a tool has detected a device failure, the column for the device in the system map displays the word "FAILURE". To get a description of the failure, the suspected cause and recommended action(s), look at the failure log for the device:

Select Device(s).

Select the tool that detected the failure (for example, "exercise") in the tools menu.

Select "exercise fail log".
The "Tool Failure Log" for the Exercise tool will be displayed.

If the information in the Failure Log is not sufficient, you can look View a Tool's Activity Log

Top

View a Tool's Activity Log

When a tool is run on a device, it creates a log of its activity. This log may contain technical and low-level information.
The tool's Activity Log is useful when there are problems running a tool on a device. If a tool reports a device failure, you should first View the Failure Log. Only if that information is not sufficient do you need to look at the Activity Log.
Note that you can view logs for multiple selected devices.
To view a Tool's Activity Log:

Select Device(s).

Select the desired tool (for example, "exercise") in the "Tools" pulldown menu.

Select "exercise act log".
The "Tool Activity Log" for the Exercise tool will be displayed.

Top

View the Information Log

After you have performed the procedure to Get Information on a Device, you can look at the information log created for the device:

Select Device(s).

Select the "tools" pulldown menu.

Select "information".

Select "info log".
The Information Log for the chosen device is displayed.
For more detailed information, View Device Status.
Top

View STM Logs (All Available)

mstm allows you to view the following logs:

UI Activity Log: Log of errors encountered by mstm
Map Log: Log of events during system map build
System Activity Log: Log of all mstm operations performed
Information Log: Log of device-specific ids/descriptions
Information Tool Activity Log: Log of most recent run of device info tool
Information Tool Failure Log: Error log for most recent run of device info tool
Verify Tool Activity Log: Log of most recent run of verifier
Verify Tool Failure Log: Error log for most recent run of verifier
Diagnose Tool Activity Log: Log of most recent run of diagnostic
Diagnose Tool Failure Log: Error log for most recent run of diagnostic
Exercise Tool Activity Log: Log of most recent run of exerciser
Exercise Tool Failure Log: Error log for most recent run of exerciser
Firmware Update Tool Activity Log: Log of most recent run of FW update tool
Firmware Update Tool Failure Log: Error log for most recent run of FW update tool
Expert Tool Activity Log: Log of most recent run of expert tool
Expert Tool Tool Failure Log: Error log for most recent run of expert tool
Utility Tool Activity Log: Log of most recent run of utility
Utility Tool Failure Log: Error log for most recent run of utility
Syslog: Log of system daemon info

For more information on a particular type of log (e.g., the UI Activity Log), select its hyperlink (e.g., UI Activity Log).
Log contents are unique, but all of the logs displayable under mstm employ a similar log viewing dialog. Using this dialog, you may:

View a log
Save a log to a file
Print a log
Clear a log (UI Activity and System Activity Logs only)

The title of the log viewing dialog will specify the log type, as well as the tool or utility (and device, if necessary) whose log you have selected.
Note that multiple logs can be viewed at once; "Prev" and "Next" keys are provided to simplify navigation through these logs when viewing them.
Top

UI Activity Log

The UI Activity Log contains a record of the errors encountered by the mstm user interface. The log dialog allows you to view, save, print, and clear the contents of the log, as desired.
There is only one copy of the log per machine, although multiple instances of the User Interface (UI) may be executed. Each log entry contains a label with a timestamp, user name, and the UI process id, in order to allow you to distinguish between these separate invocations of the UI. Here is an example of such a label:
Wed Dec 7 15:18:49 1994: User Name: joeuser, UI Process ID: 27697
To view the UI Activity Log, do the following:

Select the "file" pulldown menu on the first level screen.

Select UI Act Log.
The "UI Activity Log" screen is displayed.

Top

Map Log

The Map Log contains a record of what transpired while the system map was being built. The log dialog allows you to view, save, and print the contents of the log, as desired.
The log is created at boot time, and whenever the Remap System command is executed.
To view the Map Log, do the following:

Select the "System" pulldown menu.

Select Map Log.
The "Map Log" screen is displayed.

Top

System Activity Log

The System Activity Log contains a record of system startup and shutdown events, events that occurred during operations, and tool start and completion information. The log dialog allows you to view, save, print , and clear the contents of the log, as desired.
To view the System Activity Log, do the following:

Select the "System" pulldown menu.

Select Sys Act Log.
The "System Activity Log" screen is displayed.

Top

Information Log

The information provided by the Information Log is device-specific, but should at least include:

The hardware path to the device
A timestamp indicating when the log was created
NOTE: You should include the firmware revision, if it is available.
To view the Information Log, use the following procedure:

Select the "tools" pulldown menu.

Select "information".

Select "information log".
The Information Log for the chosen device is displayed.

Top

Information Tool Activity Log

The Information Tool Activity Log allows you to review details of the most recent execution of the Information support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Information Tool Activity Log for a particular device, do the following:

Select the "tools" pulldown menu.

Select "information".

Select "info act log".
The "Tool Activity Log" for the Information tool will be displayed.

Top

Information Tool Failure Log

The Information Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Information support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Information Tool Failure Log for a particular device, do the following:

Select the "tools" pulldown menu.

Select "information".

Select "info fail log".
The "Tool Failure Log" for the Information tool will be displayed.

Top

Verify Tool Activity Log

The Verify Tool Activity Log allows you to review details of the most recent execution of the Verify support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Verify Tool Activity Log for all selected devices, do the following:

Select the "tools" pulldown menu.

Select "verify".

Select "verify act log".
The "Tool Activity Log" for the Verify tool will be displayed.

Top

Verify Tool Failure Log

The Verify Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Verify support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Verify Tool Failure Log for all selected devices, do the following:

Select the "tools" function pulldown menu.

Select "verify".

Select "verify fail log".
The "Tool Failure Log" for the Verify tool will be displayed.

Top

Diagnose Tool Activity Log

The Diagnose Tool Activity Log allows you to review details of the most recent execution of the Diagnose support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Diagnose Tool Activity Log for all selected devices, do the following:

Select the "tools" function pulldown menu.

Select "diagnose".

Select "diagnose act log".
The "Tool Activity Log" for the Diagnose tool will be displayed.

Top

Diagnose Tool Failure Log

The Diagnose Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Diagnose support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Diagnose Tool Failure Log for all selected devices, do the following:

Select the "tools" function pulldown menu.

Select "diagnose".

Select "diagnose fail log".
The "Tool Failure Log" for the Diagnose tool will be displayed.

Top

Exercise Tool Activity Log

The Exercise Tool Activity Log allows you to review details of the most recent execution of the Exercise support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Exercise Tool Activity Log for all selected devices, do the following:

Select the "tools" function pulldown menu.

Select "exercise".

Select "exercise act log".
The "Tool Activity Log" for the Exercise tool will be displayed.

Top

Exercise Tool Failure Log

The Exercise Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Exercise support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Exercise Tool Failure Log for all selected devices, do the following:

Select the "tools" function pulldown menu.

Select "exercise".

Select "exercise fail log".
The "Tool Failure Log" for the Exercise tool will be displayed.

Top

Firmware Update Tool Activity Log

The Firmware Update Tool Activity Log allows you to review details of the most recent execution of the Firmware Update support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Firmware Update Tool Activity Log for all selected devices, do the following:

Select the "tools" function pulldown menu.

Select "firmware update".

Select "firmware update act log".
The "Tool Activity Log" for the Firmware Update tool will be displayed.

Top

Firmware Update Tool Failure Log

The Firmware Update Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Firmware Update support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Firmware Update Tool Failure Log for all selected devices, do the following:

Select the "tools" function pulldown menu.

Select "firmware update".

Select "firmware update fail log".
The "Tool Failure Log" for the Firmware Update tool will be displayed.

Top

Expert Tool Activity Log

The Expert Tool Activity Log allows you to review details of the most recent execution of the Expert Tool support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Expert Tool Tool Activity Log for all selected devices, do the following:

Select the "tools" function pulldown menu.

Select "expert tool".

Select "expert tool act log".
The "Tool Activity Log" for the Expert Tool will be displayed.

Top

Expert Tool Tool Failure Log

The Expert Tool Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Expert Tool support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Expert Tool Tool Failure Log for all selected devices, do the following:

Select the "tools" function pulldown menu.

Select "expert tool".

Select "expert tool fail log".
The "Tool Failure Log" for the Expert Tool will be displayed.

Top

Utility Tool Activity Log

The Utility Tool Activity Log allows you to review details of the most recent execution of the Utility support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Utility Tool Activity Log for all selected devices, do the following:

Select the "tools" function pulldown menu.

Select "utility".

Select "utility act log".
The "Tool Activity Log" for the Utility tool will be displayed.

Top

Utility Tool Failure Log

The Utility Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Utility support tool against all selected devices. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Utility Tool Failure Log for all selected devices, do the following:

Select the "tools" pulldown menu.

Select "utility".

Select "utility fail log".
The "Tool Failure Log" for the Utility tool will be displayed.

Top

Troubleshooting the Support Tools Manager

Occasionally, you may have problems running the Support Tools Manager. While such problems will occur infrequently, if at all, the following are the situations you are most likely to encounter, with their proposed fixes:

Device not displayed in the map
Device listed as "Unknown" in map
Tools disabled
UI cannot connect to a system
Tool goes into HUNG state
Cannot start tools
Top

Device not displayed in the map

If the kernel cannot bind in the appropriate drivers, or is unable to recognize the hardware, STM cannot communicate with the hardware in order to identify it.
For new hardware (if you have attached new hardware or powered up previously unpowered hardware):

Execute an ioscan command at the OS prompt.
Run the Remap System command from the System menu in STM.

For software problems, try the following:

Add the driver to the kernel.
Rebuild the kernel.

For hardware problems, try the following:

Reset the device.
Reseat the cables.
Reboot the system.
Replace the device.

Report STM defects through an HP representative. HP personnel should use the CHART defect-tracking program with the project name diag.stm.tools.hpux or diag.stm.ui.hpux.
NOTE: Be sure to include the information from the Map Log and ioscan -kf commands.
Top

Device listed as "Unknown" in map

The Map Log should indicate the cause of this problem, as well as what do about it.
You can determine if you have an old version of STM by checking the Release Notes at /usr/sbin/stm/Rel_NOTES.STM.
HP personnel can file an SR, use product number B4708AA and product name STM.
NOTE: Be sure to include the information from the Map Log and ioscan -kf commands.
Top

Tools disabled

Consult the following for the information needed to determine the cause for an unavailable tool:

Curr Dev Status
Sys Act Log
Current License Level

The message "Tool expected?" indicates that a particular tool should be available. Whether this is the case can be determined by checking the Release Notes (/usr/sbin/stm/Rel_NOTES.STM). It can also be ascertained during the process of installing a new tool.
Some tools (e.g., Expert Tools) require that you have a license to run them. If you do not have a license to run a particular tool, or if it is not installed, you will not see it listed as an available tool. In this instance, you should examine current device status (Curr Dev Status), where you will find a listing of all licensed and non-licensed tools for a specific device.
If necessary, install the license and try to run the tool again. HP personnel can file an SR, use product number B4708AA and product name STM.
NOTE: Be sure to include the information from the System Activity Log, prod_op_xref file, and Current License Level.
Top

UI cannot connect to a system

One indication that you have encountered this situation is that an invalid user name or password error will be displayed to you.
If "ping" works for the IP address, but not for the hostname, use the IP address.
When checking "uname -s" and "nslookup", ensure that the hostname portions match; for example,
"uname -s" returns "hprdstl6" "nslookup" returns "hprdstl6.rose.hp.com"

In the following instances, you must make the system independent of the network and the nameserver:

When the nameserver is down
When there are hostname or IP address conflicts
When the system is not connected to the network

To do this, move the "/etc/resolv.conf" nameserver file, and create a local "/etc/hosts" file, which contains the local hostname and IP address. This will allow you to override the nameserver, permitting the system to run locally.
Consult the following (on the UUT) for the information needed to determine the cause of a failure to connect to the UUT:

Syslog
Sys Act Log
Map Log

When running STM locally on a system which had a problem performing a remote connect, errors may be displayed when STM attempts to perform a local connect: you may safely ignore these error messages.
You may have to restart "diagmond": you must be root in order to do so (STM Startup).
Top

Tool goes into HUNG state

This is one of the more common problems you may encounter with the operation of the STM. Tools may move into and out of the "HUNG" state in the following instances:

When the system is very busy
When you attempt to start many tools simultaneously
When you already have multiple tools running (especially true if any of the tools is set to Maximum stress or Coverage level)
When the system has limited resources

If any of the above conditions is true, update the "diagmond" configuration so that it waits longer before marking a tool as "HUNG" (the default wait time is 4 minutes).
If a tool stays in the "HUNG" state, determine if there is an error by examining the activity log for the tool you are running (e.g., Verify Tool Activity Log) for errors, and/or to determine the last time the tool logged, compared to the current time. You may also want to examine the process, using the "ps -ef" command.
If the activity log for the tool you are running is actually hung, attempt to abort the tool. If the tool remains in the ABORT PENDING state indefinitely, kill the tool manually. To do so, logon to the UUT, find the tool that is executing, note its pid, and send it a KILL signal ("kill -9 tool_pid").
Top

Cannot start tools

You may not be able to start tools, or perform initiation tasks, in the following instances:

When the system is very busy
When you have multiple tools running (especially if any of the tools is set to Maximum stress or Coverage level)
When the system has limited resources

In the first instance, the UI Act Log will indicate a timeout when attempting to start the tool. In the second instance, the activity log for the tool you are trying to run will indicate a timeout when attempting to initialize.
In both of these instances, keep retrying, or wait for a time when the system is less busy and retry.
Also, some tools (e.g., Expert Tools) require that you have a license to run them. If you do not have a license to run a particular tool, or if it is not installed, you will not see it listed as an available tool. In this instance, you should examine Current Device Status (Curr Dev Status), where you will find a listing of all licensed and non-licensed tools for a specific device.
If necessary, install the license and try to run the tool again.
Top

On Item

Main Window
The main window displays the system map, which provides configuration information, test status, and forward progress indicators, as appropriate.
It is also the starting point for accessing all other system functions and commands.

System Map
The easiest way to determine the last state of a device is by checking the "Last Op Status" field on the system map, and noting any text displayed.
The following is a list of possible statuses with their meanings:

Status Description ------ ----------- (blank) The device has not been tested Testing Testing is in progress QUERY PENDING Query waiting; click icon to respond SUSPENDED Suspended by the user HUNG The operation has hung ABORTED The operation was aborted WARNING The operation completed, with warnings in the Tool Activity Log INCOMPLETE The operation could not be completed FAILURE The most recent operation failed Success The most recent operation succeeded

For information on selecting a device, see Select Device(s).
Top

On Menus and Commands

In mstm, commands are selected from the pulldown menus. Use the tab key or the "Menubar on/off" function key to move the cursor to the menu bar. The cursor arrow keys can then be used to select a specific menu, and the "Return" key can be used to pull down the highlighted menu or select the highlighted command from a menu.

File Menu System Menu Device Menu --------- ----------- ----------- Save Config... Sel System to Test-> Current Device Status Restore Config... Save Map... Clear Tool Status Record Command File-> Print Map... Select-> Run Command File... Remap System Unselect-> Record Output-> Map Log Filter-> UI Activity Log License-> Administration-> System Activity Log Escape To OS Daemons-> Exit
Tools Options Help ----- ------- ---- Information->* Tool Options-> On Tasks Verify->* Map... On Application Diagnose->* General... On Menus/Commands Exercise->* On HomeTopic Firmware Update->* On Shortcuts Expert Tool->* On Keyboard Utility->* On Help Latest Logs->* On Version Tool Management->

The entries above marked with "->" display one of the cascade menus shown below. Each tool (marked with "*") generates the cascade menu shown below labeled "*(Tools)->".

Record Command File-> Sel System to Test-> *(Tools)-> ------------------- ------------------ -------- Start Recording... Connect to Systems... Run Stop Recording Select Current System... [Information Log] Disconnect Systems... Activity Log Record Output-> Failure Log ------------- License-> Info Start Recording... ------- Stop Recording Display Latest Logs-> Record Map Install... ----------- Install HP-Only... Activity Log Administration-> Deinstall Failure Log -------------- Read UUT Config File Daemons-> Tool Management-> Update Tool Info ------- --------------- STM Startup Daemon Startup... Abort Tool STM Shutdown Daemon Shutdown... Suspend Tool Local UUT Logs-> Daemon Kill... Resume Tool Daemon Activity Log... Kill Tool Local UUT Logs-> Abort Utility... -------------- Kill Utility... Map Log Select-> Display "Query Pending" System Activity Log ------ Attach To Tool syslog All Class... Matching Devices Tool Options-> Matching Products ------------ Devices Above Information... Devices Below Verify... Diagnose... Unselect-> Exercise... -------- Firmware Update... All Expert Tool... Class... Utility... Tool Launch... Filter-> ------ Set Clear
The help, REFRESH, and EXIT keys occupy fixed positions in the function key display.

By choosing hyperlinks, you can get help on each of the top level menus:

Help Menu
File Menu
System Menu
Device Menu
Tools Menu
Options Menu
Exit

Top

File Menu

There are eight functions accessible via the File menu:

Save Config: Save current interface state as file functions
Restore Config: Read/execute saved config functions from file
Record Cmd File: Enable/disable recording of functions to file
Run Cmd File: Read/execute sequence of cstm functions from file
Record Output: Record functions/output to file in cstm format
UI Act Log: View log of errors encountered by mstm
Admin: Menu for managing mstm and its configuration
os: Suspend STM and invoke an OS command shell
Exit: To leave mstm

Top

Save Config

Use this function to save the state of the user interface in a specified file. The following items will be saved:

The description entered in the dialog (saved as a comment in the config file)
All items in the General Options and Map Options dialogs
All items selected via the tool options menu

Information Options
Verify Options
Diagnose Options
Exercise Options
FWupdate Options
Expert Tool Options
Utility Options

All shortcuts
See also Restore Config.

Description

The information you enter here will be saved as a comment in the configuration file.
For example, you might enter something like the following: "This config tests the workstations in building R5".

File

You enter the path (i.e., directory) and filename of the configuration file to which you wish to save the current configuration. You may specify wild cards (file filters), if you wish. For example, you might enter the following: "/users/username/*.stm". Once you hit "Return", you will see all the "/users/username" directories on the system displayed in the "Directories" screen display area; similarly, all files with a ".stm" extension will be displayed in the "Files" screen display area. Select the configuration file you want by moving the cursor to the appropriate directory and hitting "Return"; then move the cursor to the appropriate file and hit "Return".
Hit "OK" and the current configuration will be saved to that file.

Top

Restore Config

Use this function to repaint the display map, using the configuration stored by the Save Config function. Before reading the configuration file, the interface restores the factory default configuration; this means that the user interface disconnects from all test systems.

File

You enter the path (i.e., directory) and filename of the configuration file to which you wish to save the current configuration. You may specify wild cards (file filters), if you wish. For example, you might enter the following: "/users/username/*.stm". Once you hit "Return", you will see all the "/users/username" directories on the system displayed in the "Directories" screen display area; similarly, all files with a ".stm" extension will be displayed in the "Files" screen display area. Select the configuration file you want by moving the cursor to the appropriate directory and hitting "Return"; then move the cursor to the appropriate file and hit "Return".
Hit "OK" and the current configuration will be saved to that file.
Top

Record Cmd File

By using this function, you can record the functions executed by the interface in a file you specify, or you can toggle recording off. mstm operations are recorded as a series of cstm (command line interface of the Support Tools Manager) functions which can be read by:

the Run Cmd File function
the -f initiation option, or
automatically from the .stmrc file.
A wait function is automatically inserted after each identify, verify, exercise, or diagnose operation, so that operations executed sequentially at the time of recording, won't attempt simultaneous execution at playback time. You may wish to edit the output file and remove some of these wait functions.

Description

The information you enter here will be saved as a comment in the command file.
For example, you might enter something like the following: "This command file verifies the disks and tapes."

File

You enter the path (i.e., directory) and filename of the configuration file to which you wish to save the current configuration. You may specify wild cards (file filters), if you wish. For example, you might enter the following: "/users/username/*.stm". Once you hit "Return", you will see all the "/users/username" directories on the system displayed in the "Directories" screen display area; similarly, all files with a ".stm" extension will be displayed in the "Files" screen display area. Select the configuration file you want by moving the cursor to the appropriate directory and hitting "Return"; then move the cursor to the appropriate file and hit "Return".
Hit "OK" and the current configuration will be saved to that file.
Top

Run Cmd File

Use this function to have mstm read in and execute a sequence of cstm functions saved by the Record Cmd File function. Alternatively, any sequence of cstm (command line interface of the Support Tools Manager) functions can be read and executed by this function.

File

You enter the path (i.e., directory) and filename of the configuration file to which you wish to save the current configuration. You may specify wild cards (file filters), if you wish. For example, you might enter the following: "/users/username/*.stm". Once you hit "Return", you will see all the "/users/username" directories on the system displayed in the "Directories" screen display area; similarly, all files with a ".stm" extension will be displayed in the "Files" screen display area. Select the configuration file you want by moving the cursor to the appropriate directory and hitting "Return"; then move the cursor to the appropriate file and hit "Return".
Hit "OK" and the current configuration will be saved to that file.

Cancel

If you no longer wish to run the currently executing command file, select "Cancel".
Top

Record Output

During any mstm session, you can use this function to save the cstm (command line version of the Support Tools Manager) version of the terminal output functions generated by the session to a file of your choice. The output will show both the functions executed and the output they produced. Note that some output will not be the same as a cstm session, due to intrinsic differences in the three interfaces, especially functions which are automatic in mstm and xstm, such as displaying the system map.

Description

The information you enter here will be saved as a comment in the file in which you save your terminal output.
For example, you might enter something like the following: "This is the output of the disk verification."

File

You enter the path (i.e., directory) and filename of the configuration file to which you wish to save the current configuration. You may specify wild cards (file filters), if you wish. For example, you might enter the following: "/users/username/*.stm". Once you hit "Return", you will see all the "/users/username" directories on the system displayed in the "Directories" screen display area; similarly, all files with a ".stm" extension will be displayed in the "Files" screen display area. Select the configuration file you want by moving the cursor to the appropriate directory and hitting "Return"; then move the cursor to the appropriate file and hit "Return".
Hit "OK" and the current configuration will be saved to that file.
Top

UI Act Log

Consult the UI Activity Log when you want to view a display of errors recorded by the user interface. The dialog box for this log allows you to view and save the contents of the log to a file, print a hardcopy of the current log contents, or clear the current log contents.
There is only one copy of the log on a single machine, even though more than one mstm session may be executed. Each log entry contains a label containing a timestamp, the user name, and the UI process ID, in order to distinguish between separate mstm sessions on the same machine (for example, "Wed Dec 7 15:18:49 1994: User Name: bobcap, UI Process ID: 27697").
The UI Activity Log is not temporary; all other mstm session files are removed, once the session is terminated.
If the log file reaches the configurable size threshold, a warning will be displayed to inform you.

Clear the UI Activity Log

If you select this command, you will clear the current UI Activity Log of its present contents.
Top

Admin

Use the Administration menu to manage the diagnostic system and its configuration, including the following functions:

Causing the diagmond daemon on the current test system to reread its configuration file
Causing the list of available tools for the selected device to be reread
Causing the diagnostic system to be shut down locally, i.e., on the machine on which mstm is running. If the local Unit Under Test (UUT) is connected, it will be disconnected before the system is shut down. A warning/confirmation will be displayed, stating that the diagnostic system is being shut down and can only be restarted by the root user.
Allowing a root user to start the diagnostic system on the local machine, i.e., the machine on which mstm is running.

Top

Escape to OS

Use this function to suspend the Support Tools Manager user interface, and invoke an operating system command shell. You may then enter system commands at the shell prompt.
You type "exit" to return to mstm.
Top

Exit

Use this function to leave the user interface, and return to the prompt from which you launched mstm. The connection to the Unit Under Test is shut down, and all interactive tool execution is terminated. Non-interactive tools will continue execution.

Top

Record Cmd File

There are two Record Cmd File functions:

Start Rec Cmd: Enable recording of executed functions
Stop Rec Cmd: Disable recording of executed functions

Top

Start Rec Cmd

Use this function to record functions that you are executing. You must specify a file in which to save your recorded functions; alternatively, you can append the list of recorded functions to an existing file. Once recording is started, the function is unavailable until recording is turned off.
Top

Stop Rec Cmd

Use this function to disable recording of functions you are executing. The function is unavailable unless recording is in progress.
Top

Record Output

There are three Record Output functions:

Start Record Out: Enable recording of terminal output
Stop Record Out: Disable recording of terminal output
Record Map: Save the system device map

Top

Start Record Out

You use this function to enable terminal output recording. You must specify a file in which to save the record thus produced; alternatively, you can append the record to an existing file. Once recording begins, the function is unavailable until recording is disabled.
Top

Stop Record Out

You use this function to disable terminal output recording. The function is unavailable, unless recording is in progress.
Top

Record Map

You use this function to store a copy of the system device map. The function is unavailable unless recording is in progress.
Top

Administration

There are four Administration functions:

Reread UUT Cfg File: Reread config file on current test system
Update Toolinfo: Reread list of available tools for a device
STM Startup: Turn off diagnostics on local machine
STM Shutdown: Restart diagnostics on local machine (root only)

Top

Reread UUT Cfg File

Use this function to have the current test system diagmond daemon reread its configuration file.
Top

Update Toolinfo

Use this function to have the list of available tools for a selected device reread. This provides the basic functionality for incorporating a newly installed support tool into mstm.
Top

STM Startup

Use this function to start the diagnostic system on the local machine, i.e., the machine on which mstm is running, when you are logged on as root.
Top

STM Shutdown

Use this function to shut down the diagnostic system on the local machine, i.e., the machine on which mstm is running. You will see a warning/confirmation displayed, stating that the diagnostic system is being shut down and that it may only be restarted by the root user. If the local Unit Under Test (UUT) is connected, it will be disconnected before the diagnostic system is shut down.
Top

Local UUT Logs

Use this function to view the Map Log and Sys Act Log for the local Unit Under Test (UUT), when you cannot access the mstm interface. The logs may contain details concerning problems encountered when the system started, or concerning reasons that the system was caused to terminate. Additional details may be found in the "syslog" file.

Syslog

Syslog is a system log, which is administered outside the Support Tools Manager by the "syslogd" daemon. It provides you with information logged by "syslogd" on behalf of the daemons running on the system (e.g., inetd, ftpd, etc.). The Support Tools Manager daemon is called "diagmond", and you will find its starting and completion messages logged in "syslog" (1 line entry for startup and 1 line entry for shutdown).
Top

Local UUT Logs

There are two Local Log View functions:

Map Log: View the Map Log on local system
Sys Act Log: View the System Activity Log on local system

Top

Map Log

Use this function to view the Map Log on the local Unit Under Test (UUT), without having to be connected to the mstm machine.
See also Local UUT Logs and Sys Act Log.
Top

Sys Act Log

Use this function to view the System Activity Log on the local Unit Under Test (UUT), without having to be connected to the mstm machine.
See also Local UUT Logs and Map Log.

Top

System Menu

There are eight System functions:

Current System: Select current test system from a list
Save Map: Write ASCII copy of device map to file
Print Map: Print ASCII copy of device map to printer
Remap System: UUT re-examines configured hardware
Map Log: Record of all system devices in last map
Install: Obtain required license level to run tools
Sys Act Log: Record of all operations performed by mstm
Daemons: Access daemon commands and/or view log

Top

Sel Sys to Test

The Sel System to Test function permits access to a set of functions which allow you to maintain a list of test systems, and to select one of these to be the current test system.

Top

Sel System to Test

There are three Sel System to Test functions:

Connect: Connect to test system chosen from list
Current System: Display state of test system from list
Disconnect: Disconnect from test system on list

Top

Connect

Use this function to maintain a list of test systems, and to connect to those chosen.
The System information portion of the dialog contains the list of test systems available, and may be edited. When adding a test system, only the system name need be specified. The OS and OS Revision are automatically determined, to provide the necessary information prior to system connection.
To add a new test system, move from the "System to Test" section to the "Test System to Add" section by using the "Tab" key. Type the name of the test system you wish to add at the prompt, and then hit either the "Return" or "Add" key.
Multiple systems may be selected, by using the "Space" bar and the "Return" key: hitting "Return" while the cursor is over a system name causes that system to be selected, and all others to be deselected. You can then use the "Space" bar to toggle the selection state of individual systems, without automatically deselecting other systems when you do so.
Hitting the "Delete" key will cause the currently highlighted system to be deleted from the list of available systems; if that system is currently connected, it will be disconnected. If the current system is deleted, then there is no current system following deletion. You will be asked for confirmation prior to deleting a connected system, including the current system.
Once you hit "OK", another dialog is generated to prompt you for the logon name and password necessary to establish the connection. The same name and password are used to connect all the selected systems. An attempt to connect all the selected systems will be made; in case of an error, a list of systems not connected will be included in the error display.
The status of each test system is listed in its entry in the list of available test systems. The possible statuses and their meaning are as follows:

Blank: The status is blank immediately after it is added.

Connected: The test system is connected, but its state is not being displayed.

Current: The mstm displays reflect the state of this system.

Unavailable: The system could not be connected due to an error.

Not Responding: The system could not be connected due to a problem with the network.

Disconnected: The system has been disconnected.

System Information

This dialog allows you to add systems to, or delete them from, the list of test systems maintained by the interface.
To add a system to the list of systems to test, enter the network name of the system (e.g., "system5.cup.hp.com") in the "Test System to Add" field; then hit "Add" or "Return".
To delete a system from the list of systems to test, move the cursor to the system's entry in the "System to Test" field; then hit "Delete".
When "OK" is hit, a dialog will be displayed, prompting you for your login and password on the system you chose to be connected to.
Top

Current System

Use this function to select which system will display the testing information for the current test system, which you choose from the list of connected test systems.
Only one test system can be selected by this function at a time; the list of test systems may be edited. When you choose a system to be the current test system, it is automatically connected to mstm, whenever possible, if it is not already connected.
When a new system becomes the current test system, all the displays are altered to reflect the status of this new system. However, the previous test system remains connected to mstm, and will continue to execute any currently active support tools.
If you exit mstm without making the previous system current again, then all interactive support tools running on that system are terminated, and the output from them is lost (non-interactive support tools will continue to execute). You will be warned that this is about to happen, and will be given the opportunity to cancel.
All connected systems are listed in the Status column of the list of systems available for testing.
If the connection to the current system fails, there will be no current system. You will be warned, the device map will be cleared, and any displays showing information on the formerly current system are closed.

System Information

This dialog allows you to add systems to, or delete them from, the list of test systems maintained by the interface, and to select one system at a time to be the current test system.
To add a system to the list of systems to test, enter the network name of the system (e.g., "system5.cup.hp.com") in the "Test System to Add" field; then hit "Add" or "Return".
To delete a system from the list of systems to test, move the cursor to the system's entry in the "System to Test" field; then hit "Delete".
When "OK" is hit, a dialog will be displayed, prompting you for your login and password on the system you chose to be the current test system.
Top

Disconnect

Use this function to disconnect from systems you have chosen to be connected with; the list of test systems is not editable in this dialog.
Multiple systems may be selected, and are disconnected when "OK" is used to finish the dialog.

System Information

This dialog allows you to disconnect from one or more systems at a time.
To disconnect from a system, move the cursor to the system's entry in the "System to Test" field; then hit "OK".
Top

Save Map

Use this function to write an ASCII copy of the device map to a specified file.

File

You enter the path (i.e., directory) and filename of the configuration file to which you wish to save the current configuration. You may specify wild cards (file filters), if you wish. For example, you might enter the following: "/users/username/*.stm". Once you hit "Return", you will see all the "/users/username" directories on the system displayed in the "Directories" screen display area; similarly, all files with a ".stm" extension will be displayed in the "Files" screen display area. Select the configuration file you want by moving the cursor to the appropriate directory and hitting "Return"; then move the cursor to the appropriate file and hit "Return".
Hit "OK" and the current configuration will be saved to that file.
Top

Print Map

Use this function to print an ASCII copy of the device map to a specified printer. The list of available printers includes all those configured on the system on which mstm is being run.

Printer

To print out a hardcopy of the device map to a particular printer, select a printer from the list displayed in the "Printer" screen display area; then hit "OK".
Top

Remap System

Use this function to determine what hardware is attached to the unit under test (UUT). This function is especially useful when you have attached new hardware to your system, or have powered up previously unpowered hardware. At the OS prompt, issue an ioscan command, so that the system will recognize the new hardware; then run the Remap System command in STM. Once the rescan is completed, the device map will be refreshed. All devices will be displayed and will be unselected.
Whenever this command is executed, the Map Log is created.
Top

Map Log

Use this function to view a record of all the devices identified when the system map was last built. You can view, save, or print the log. The log is created at boot time, and whenever the "RescanHW" function is executed.
The log displays the log creation time (e.g., "Fri Dec 9 13:27:31 1996"), followed by a list of log entries, describing events which occurred during the system map build. The individual log entries are preceded by the day, date, and time at which the logged event occurred. Log entries may contain information, error messages, tool status, etc.
See also Remap System.
Top

Install

This menu provides access to other functions which permit you to install licenses for running support tools, including an HP-Only license valid only for the current session. It also provides the functionality for deinstalling these licenses on the current test system.
Top

Sys Act Log

Consult the System Activity Log when you want to view a display of events which occurred during system startup and shutdown, as well as any events which occurred during operations; the log also contains tool start and completion information. The dialog for this log also allows you to save the current contents of the log to a file, print a hardcopy of the current log contents, or clear the current log contents.
The log displays host and user names, followed by log creation time (e.g., "Fri Dec 9 13:27:31 1996"). Each of the following log entries is preceded by a day, date, and timestamp of the same format. The log entries may include tool status messages, error messages, etc.

Clear the System Activity Log

If you hit "OK", the current contents of the System Activity Log will be deleted. If you don't wish to do delete the current contents of the System Activity Log, hit "Cancel".
Top

Daemons Menu

Select this menu to access the Daemon Startup, Daemon Shutdown, and Daemon Kill commands, or to view the Daemon Activity Log.
Top

License

There are three License functions:

Install: Install license needed to run support tools
Install HP-Only: Install HP-Only license for one session
Deinstall: Deinstall all licenses on current UUT

Top

Install

Use this function to install the level of licensing you need to run support tools. The password you enter will determine the level of access the system grants you. All permissions granted you apply to the current test system only.
The password you type is not displayed on the screen.
See also Install HP-Only and Deinstall.

Licensing Password

In order to determine the level of access granted you by the system on which you have installed your support tools license, you must enter a password at this time, and then select "OK" to proceed. If you do not want to continue with the password installation, select "Cancel" instead.
The password you type is not displayed on the screen.
Top

Install HP-Only

Use this function to install the HP-Only license. HP-Only privileges will be enabled on all test systems which are accessed by the user interface, until the Support Tools Manager UI is exited. On the UI system, the HP-Only password is only enabled for the duration of the current session.
Use this function to install the HP-Only license. HP-Only privileges will be enabled on all test systems accessed by mstm, until the user interface is exited. On the User Interface (UI) system, however, the HP-Only password is only enabled for the current session.
The password you type is not displayed.
See also Install and Deinstall.

HP-Only Licensing Password

In order to enable HP-Only run privileges on all systems accessed by the STM until you exit the current login session, or to enable HP-Only run privileges on the user interface for the current session, you must enter a password at this time, and then select "OK" to proceed. If you do not want to continue with this login session, select "Cancel" instead.
The password you type is not displayed on the screen.
Top

Deinstall

Use this function to deinstall licenses on the current test system. When executed, all licenses on the system will be deinstalled, including any active HP-Only licenses. Before the operation begins, however, a dialog will be displayed, which will ask you to confirm or cancel the operation.
See also Install and Install HP-Only.
Top

Daemons

There are four Daemons functions:

Daemon Startup: Initiate a daemon on the test machine
Daemon Shutdown: Abort a daemon on the test machine
Daemon Kill: Kill a daemon on the test machine
Daemon Activity Log: View a daemon activity log

Top

Daemon Startup

Use this command to initiate a daemon on the test machine. When invoked, a listing of all available STM daemons on the UUT (excluding diagmond) is displayed.
Top

Daemon Shutdown

Use this command to abort a daemon on the test machine. When invoked, a listing of all available STM daemons on the UUT (excluding diagmond) is displayed.
Top

Daemon Kill

Use this function to kill a daemon on the test machine. When invoked, a listing of all available STM daemons on the UUT (excluding diagmond) is displayed.
This command is allowed to complete only if the daemon has been issued an abort by the Daemon Shutdown command, and has not terminated. If this command is run, and no running daemons have been issued an abort, an informational dialog will be displayed, which will tell you to select the "Daemon Shutdown" function. Otherwise, this command sends a "kill -9" command to the daemon process.
Top

Daemon Activity Log

Select this function to view a daemon activity log.

Top

Device Menu

There are six Device functions:

Curr Dev Status: Display device info/suggest further action
Clr Tool Status: Reset map status for devices not under test
Select: Select devices in the hardware map
Unselect: Unselect devices in the hardware map
Filter: Filter the device map

Top

Curr Dev Status

Use this function to display all known information for the selected devices, including current status, and to receive suggestions on further actions which you might take at this point. The data displayed for each device includes the following:

A description of the device
The hardware path, specifying the address of the hardware components leading to the device
The device type (e.g, disk, tape)
The device qualifier (e.g., SCSI, CS80)
The most recent tool executed/executing on the device
Exit status of the most recent tool run
The current status of the device
Recommended user action

The "Current Device Status" may be run at any time, even if the device is currently busy, as it does not access the device to obtain its information.
When a utility is executing, the current status field also shows the process number for the utility.
The recommended action field is used to suggest what action you might want to take next. For example, in the event of a tool failure, you might see a message suggesting that you examine the Act Log and the Fail Log.
Top

Clr Tool Status

Use this function to reset the state of all selected devices which do not have a currently running support tool process to "Untested". This function also removes the Act Log and the Fail Log for all devices.

Top

Select

This menu allows the user to select devices in a number of different ways. These include:

Select All: Choose all devices in the hardware map
Select Class: Choose several devices at the same time
Select Matching Devices: Choose all devices of the same type
Select Matching Products: Choose all devices of the same product
Select Devices Above: Choose all devices above the selected devices
Select Devices Below: Choose all devices below the selected devices

Select All

Use this function to select all the devices displayed in the hardware map.

Select Class

Use this function to select several devices at once, adding these to devices already selected. All devices to be selected must satisfy one of the items specified in the dialog: "Devices" or "Products". Currently selected devices are not unselected by this function. If you wish to select only the devices which meet these criteria, use the Unselect All function prior to choosing the "Select Class" function.
"Devices" is defined as "Device Type/Device Qualifier". "Device Type" and "Device Qualifier" are displayed by the Curr Dev Status command.
Examples of "Devices" include:

Adapter/Bus
Disk/CDROM
Disk/Hard
Interface/Centronics
Interface/Keyboard
Interface/LAN
Interface/RS-232
Interface/SCSI
Memory/Memory
Processor/CPU
Tape/DDS
Don't select anything if you do not want to use the device type and qualifier to select devices.
"Products" is defined as "Product (Qualifier)." "Product" and "Qualifier" are displayed in the device map and by the Curr Dev Status command.
Examples of "Products" include:

Built-in Keyboard/Mouse (2e)
Bus Adapter (580)
CPU (5a1)
SCSI Disk (SEAGATE31200N)
SCSI Tape (HPHP35480A)
Don't select anything if you do not want to use the product to select devices.

Select Devices [Device Type/Device Qualifier]

Scroll through the "Device Type and Qualifier" window to the device type and qualifier you wish to select (e.g., "Disk/Hard") and select it with the space bar or Return. Multiple selections can be made, using the space bar. Next, move to the "Product" window , or click on "OK", as desired. "Device Type" and "Device Qualifier" are displayed by the Curr Dev Status command.

Select Products [Product (Qualifier)]

Scroll through the "Product" window to the product you wish to select, (e.g., "SCSI Disk (SEAGATE31200N)", and select it using the space bar. "Product" and "Qualifier" are displayed in the device map and by the Curr Dev Status command.
When satisfied with your selections, hit "OK".

Select Matching Devices

This command will select all devices with the same device type and device qualifier as those devices which are already selected. Device type and device qualifier can be viewed using the Curr Dev Status command.

Select Matching Products

This command will select all devices which are the same product as those devices which are already selected.

Select Devices Above

This command will select all devices which are in the hardware path between the system processing unit and the selected devices. If, for example, a SCSI disk is selected, then using this command will also cause the SCSI interface card and any I/O or bus adapters to which this card is connected to also be selected.

Select Devices Below

This command will select all devices which are connected below the selected devices. If, for example, a SCSI interface card is selected, then using this command will also cause any SCSI devices connected to this card to be selected.

Top

Unselect

This menu allows the user to deselect devices in a couple of different ways. These include:

Unselect All: Deselect all devices in the hardware map
Unselect Class: Deselect several devices at the same time

Unselect All

Use this function to deselect all devices on the hardware map.

Unselect Class

Use this function to deselect several devices at once, removing these from the set of devices which are already selected. All devices to be deselected must satisfy one of the items specified in the dialog: "Devices" or "Products". Currently selected devices which do not match the criteria in the dialog are not deselected by this function.
"Devices" is defined as "Device Type/Device Qualifier." "Device Type" and "Device Qualifier" are displayed by the Curr Dev Status command. Examples of "Devices" include:

Adapter/Bus
Disk/CDROM
Disk/Hard
Interface/Centronics
Interface/Keyboard
Interface/LAN
Interface/RS-232
Interface/SCSI
Memory/Memory
Processor/CPU
Tape/DDS
Don't select anything if you do not want to use the device type and qualifier to deselect devices.
"Products" is defined as "Product (Qualifier)." "Product" and "Qualifier" are displayed in the device map and by the Curr Dev Status command.
Examples of "Products" include:

Built-in Keyboard/Mouse (2e)
Bus Adapter (580)
CPU (5a1)
SCSI Disk (SEAGATE31200N)
SCSI Tape (HPHP35480A)
Don't select anything if you do not want to use the product to deselect devices.
When satisfied with your selections, hit "OK".

Top

Filter

The Filter commands let you limit the number of items which are displayed in the device map at a given time. To do so, first use the selection commands in the Device Menu to select only the items that you wish to include in the device map. Then use the Filter -> Set command. To include all devices in the device map, use the Filter -> Clear command.
Top

Tools Menu

There are eight Tools functions:

Information: Generate an info log for a selected device
Verify: Pass/fail test of hardware's usability
Diagnose: Error isolation test to the FRU level
Exercise: Stress test of target hardware for intermittents
Firmware Update: Update firmware on a selected device
Expert Tool: Run device-specific interactive tool
Utility: Run non-device-specific mstm tools
Latest Logs: Display the latest tool logs
Tool Mgmt: Menu to abort/suspend/resume tools and utilities

See Tools Menu for help on running these tools, for logging help, and for additional information.
Top

Information

Use this function to create a log of information specific to each selected device, which has an information function, including:

The product identifier
A description of the device
The hardware path to the device
The vendor

Typically, the firmware revision code, if firmware is present in the device(s) selected, will also be displayed.
The information tool runs on all selected devices that are not currently busy.
When the tool exits, returning a "SUCCESSFUL" or "WARNING" status, you should consult the Information Log, Fail Log, and/or Act Log for information retrieved by the tool about the hardware.
Top

Verify

Use this function to verify all selected devices for which a verifier function exists. The purpose of the verification procedure is to ensure as quickly as possible that the target hardware is usable, and that you will be successful in using the device. Verifiers don't tend to isolate down to the FRU level, nor are they generally interactive.
To verify a selected device or devices, the target device(s) must not only support verification, it must also currently be idle.
When you first start to verify a device(s), the device(s) state on the device map will be changed to "RUNNING".
If the operation requires you to interact with the interface, the device state will change to "Query Pending". If the UI started the tool, the query will display automatically. If the UI did not start the tool, you must select the Display Query function to display the query.
Once the verify operation has completed, this state will change to "Success", "WARNING", or "FAILURE", as appropriate.
You should then consult the Fail Log for information on tool failures, and the Act Log for all other tool activity information.
Top

Diagnose

Use this function to diagnose all selected devices for which a diagnostic exists. The purpose of the diagnostic procedure is to test the target hardware as completely as possible, and if any errors are found, to isolate to the FRU level. Isolation to the component level is also provided, when possible. Diagnostic modules are not generally interactive.
To diagnose a selected device or devices, the target device(s) must not only support diagnostics, it must also currently be idle.
When you first start to diagnose a device(s), the device(s) state on the device map will be changed to "RUNNING".
If the operation requires you to interact with the interface, the device state will change to "Query Pending". If the UI started the tool, the query will display automatically. If the UI did not start the tool, select the Display Query function to display the query.
Once the diagnose operation has completed, this state will change to "Success", "WARNING", or "FAILURE", as appropriate.
You should then consult the Fail Log for information on tool failures, and the Act Log for all other tool activity information.
Top

Exercise

Use this function to exercise all selected devices for which an exerciser exists. The purpose of the exerciser procedure is to stress the target hardware in a way that meets or exceeds the stress typically placed on that hardware in the customer environment. Exercisers are not generally interactive.
To exercise a selected device or devices, the target device(s) must not only support exercise operations, it must also currently be idle.
When you first start to exercise a device(s), the device(s) state on the device map will be changed to "RUNNING".
If the operation requires you to interact with the interface, the device state will change to "Query Pending". If the UI started the tool, the query will display automatically. If the UI did not start the tool, you must select the Display Query function to display the query.
Once the exercise operation has completed, this state will change to "Success", "WARNING", or "FAILURE", as appropriate.
You should then consult the Fail Log for information on tool failures, and the Act Log for all other tool activity information.
Top

Firmware Update

Use this function to initiate the firmware update process for a selected device. While the user interface to the firmware update tools is generic, the tools themselves are device-specific.
This function is only valid when exactly one device is selected, that device is not currently busy, and the device supports the firmware update process.
A new window is automatically created so that you can communicate directly with the firmware update tool(s).
NOTE: Be sure that you put the firmware file on the UUT before starting the update process.
CAUTION: Make sure you select the correct firmware file for the device! Updating a device with incorrect firmware can make the device permanently unusable and data could be lost.
CAUTION: It is not advisable to interrupt or abort the firmware update functions.
Top

Expert Tool

Use this function to invoke the expert tool for the selected device. Expert tools are device-specific troubleshooting utilities for use by sophisticated users. Their functionality varies from tool to tool, but they are intended to be interactive, and rely on you to provide information necessary to perform a particular task.
This function is only valid when you select exactly one device, that device is not currently busy, and the selected device has an associated expert tool.
Top

Utility

Use this menu to access the set of functions for running support tools which are not device-specific. Current tools include logging and disk backup tools.
Top

Latest Logs

The commands below this menu allow the Activity and Failure logs associated with the most recently run tool on the currently selected devices to be displayed.

Utility Tool Log

This dialog allows you to specify which utility log information you wish to access, based on time of execution, or the device on which the utility was run.

Utility Execution

This dialog allows you to specify which utility's log you wish to access, either the last utility executed by the UI, or the last utility executed by the UI on a particular device.

Most Recent Utility Executed

Place an "x" in this box if you want to view the Tool Activity Log for the most recently executed utility on the Unit Under Test (UUT), without specifying a particular device.
To select the utility, move the cursor to the appropriate utility name in the "Select Utility" field and hit "Return"; then hit "OK".

Most Recent Utility Executed on Device

Place an "x" in this box if you want to view the Tool Activity Log for the most recently executed utility on a particular device.
To select the device, move the cursor to the appropriate device address in the "Select Device" field and hit "Return"; then hit "OK".

Select Utility

Select a utility to run from the list displayed, then select "OK" to proceed.
If you choose not to continue with utility selection and execution, select "Cancel" instead.

Utility Information

This dialog allows you to select a utility from a list, and get more information about it.

Select Utility Info

Select the name of a utility from the list displayed to access more information about the selected utility. Select "OK" to proceed. If you decide you do not wish to access the utility's information screen at this time, select "Cancel" instead.
Top

Tool Mgmt

Use this menu to access the set of functions which allows you to manage tools and utilities on the Unit Under Test (UUT). You may abort, suspend, or resume non-interactive tools, as well as respond to any "Query Pending" the tools may generate. A particular utility, once chosen from the list of available utilities, may also be aborted, suspended, or resumed.
See also Display Query.

Top

Tools Menu

There are five Tools functions:

Run: Start execution of a selected support tool
Information Log: View log describing/identifying selected device(s)
Act Log: View log of actions performed on selected device(s)
Fail Log: View log of test failures on selected device(s)
Info: View tool-specific help for selected device(s)

Top

Run

Use this function to start executing the tool you have selected from the main menu, on all of the selected devices which have that tool available.
Top

Information Log

Use this function to view the log(s) generated by an Information request on all selected devices for which an information log exists.
Top

Act Log

Use this function to review the log which contains details concerning the most recent invocation of a tool on all selected devices. The function is valid only when a Tool Activity Log for the tool exists for the selected device(s).
Top

Fail Log

Use this function to review the log which contains details concerning failures encountered during the most recent execution of the tool on all selected devices. The function is valid only when a Tool Failure Log for the tool exists for the selected device(s).
Top

Info

Use this function to display help information unique to the tools for all selected devices. It may always be run, because it does not access the device(s) to obtain its information.

Top

Tool Management

There are five Tool Management functions:

Abort Tool: Prematurely halt tool execution on selected device(s)
Suspend Tool: Pause execution of a tool on selected device(s)
Resume Tool: Start running a suspended tool on selected device(s)
Abort Utility: Prematurely halt utility executing on a device
Display Query: Display tool request for input/action

Top

Abort Tool

Use this function to stop execution of the currently running tool on all selected device(s).

Top

Suspend Tool

Use this function to momentarily halt execution of a support tool running on all selected device(s).
See also Resume Tool.
Top

Resume Tool

Use this function to restart execution of a suspended tool running on all selected device(s).
See also Suspend Tool.
Top

Abort Utility

Use this function to halt execution of a utility running under the mstm. Only one utility from the list of utilities can be selected at a time. Only currently executing or suspended utilities are listed. On HP-UX systems, the id number displayed is the utility's process id on the Unit Under Test (UUT).

Select Utility

From the list of currently executing or suspended utilities displayed to you, select one to abort, then select "OK" to proceed. If you decided you do not wish to abort the selected utility, select "Cancel" instead.

No Utility to Abort

You selected the Abort Utility function, but there are no currently executing or suspended utilities to abort. To repeat your selection, select "OK". To proceed without attempting to abort a utility, select "Cancel".
Top

Display Query

Use this function when a non-interactive tool requires your input in order to continue processing. Selecting "Display 'Query Pending'" will cause the support tool's request for information to be displayed, so that you can respond to it.
Top

Kill Tool

Use this function to kill a tool which is in the "abort pending" state, but which doesn't manage to abort properly (see also Kill Utility).
For tools which are not in the "abort pending" state, you should first try Abort Tool.
Top

Kill Utility

Use this function to kill a utility which is in the "abort pending" state, but which doesn't manage to abort properly (see also Kill Tool).
For utilities which are not in the "abort pending" state, you should first try Abort Utility.
Top

Attach

Use this command to connect the display to a specified interactive support tool, after an "escape to UI" has been executed. You will be shown a list of non-suspended interactive support tools, and then you choose the one you want connected to your display. This command is invalid if there are no currently non-escaped interactive support tools.

Support Tool to Attach

Use this command to select an interactive support tool after the "Attach" command has been selected. You will be shown a list of non-suspended interactive support tools, and then you choose the one you want connected to your display. This command is invalid if there are no currently non-escaped interactive support tools.

Select "OK" to proceed, and "Cancel" if you decide not to continue with execution of the "Attach" command.

No Support Tool Available

There are no currently non-suspended interactive tools available. You cannot attach the UI to an interactive tool at this time.
Select "OK" to proceed.

Top

Options Menu

There are three Options functions:

Tool Options: Menu for launching tools and utilities
Map Options: Configure device map options
General Options: Configure general interface options

Top

Tool Options

Use this menu to access the set of functions which allows you to define options for tools and utilities and how to launch them.

Top

Map Options

Use this function to configure mstm options pertaining to the device map.
The "Map Refresh Rate" field allows you to specify how often (in seconds) the device map is to be updated; the default is every 2 seconds. When the user interface is being run on a system other than the system under test, the device map information is sent between the systems at this rate.
The "Display xstm Device Map in Text Format" field allows you to display the device map in a format similar to that used in the menu interface, while running mstm.
The "Include in Device Map" checkboxes allow you to specify which items are to be displayed in the device map.
The "Width of Fields Map" allows you to specify how many characters are to be used to display certain fields in the line oriented maps. An additional space, not counted in the field width, is used to separate fields. In all line oriented maps, you can leave more room on the line for other items by eliminating an item from the map, or by restricting its width.

Map Refresh Rate (in seconds)

The "Map Refresh Rate" field allows you to specify how often (in seconds) the device map is to be updated; the default is every 2 seconds. When the user interface is being run on a system other than the system under test, the device map information is sent between the systems at this rate.

Display xstm Device Map in Text Format

The "Display xstm Device Map in Text Format" field allows you to display the device map in a format similar to that used in the menu interface.

Path

Select this checkbox to include path information in the device map; that is, the hardware address of a device, like "2.4.3".

Path Field Width

The "Path Field Width" field allows you to specify how many characters are to be used to display the hardware path information in the line oriented maps. An additional space, not counted in the field width, is used to separate fields. In all line oriented maps, you can leave more room on the line for other items by eliminating an item from the map, or by restricting its width.

Product

Select this checkbox to include product name information in the device map; for example, "HP 19744R".

Product Field Width

The "Product Field Width" field allows you to specify how many characters are to be used to display the product name in the line oriented maps. An additional space, not counted in the field width, is used to separate fields. In all line oriented maps, you can leave more room on the line for other items by eliminating an item from the map, or by restricting its width.

Active Tool

Select this checkbox to ensure that the device map indicates which tool(s) is currently active.

Time Used

Select this checkbox when you want to show elapsed time during non-interactive tool execution.

Time to Go

Select this checkbox when you want to show time remaining during non-interactive tool execution.

Loops Done

Select this checkbox when you want to show how many complete repetitions of a non-interactive tool test have been completed.

Loops to Go

Select this checkbox when you want to show how many complete repetitions of a non-interactive tool test are left to complete.

Last Operation Status/Percent Complete

This field indicates the progress of the currently running tool, as a measure of percentage of execution completed. If no tools are running, it indicates the status of the last tool that was run.

Last Operation Status Field Width

The "Last Operation Status Field Width" field allows you to specify how many characters are to be used to display operation status/percentage of test completed in the line oriented maps. An additional space, not counted in the field width, is used to separate fields. In all line oriented maps, you can leave more room on the line for other items by eliminating an item from the map, or by restricting its width.

Percent Complete Scale (mstm only)

Select this checkbox to display a graphic (scale) representation of forward test progress; i.e., to display the percentage of the test which has already completed.
Top

General Options