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 xstm, 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 clicking on one or more icons representing the device(s). Using pulldown and popup menus, choose the desired operations to perform on the selected devices. Typical operations are verifying devices and viewing Failure Logs.
The results of a running a tool are reflected by color changes to the icons in the device map.
You can run the xstm 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 xstm interface on one machine, and use it to run support tools on the same machine (i.e., the machine running xstm and the UUT are one and the same).
The xstm program is the X-Windows interface for STM. Two other STM interfaces are available:
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.
Troubleshooting STM
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:
You will see a dialog box 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:
If you wish to delete a system from the list, click on its network name in the "System to Test" list and then click on "Delete".
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:
To disconnect from one or more systems:
You will see a dialog box displayed, which is similar to those you have seen displayed for the Select Current System function. You may select one or more systems for disconnection, using the mouse and SHIFT or CTRL keys. (Hold down the CTRL or SHIFT key when clicking on the names of additional test systems you wish to select.)
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:
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.
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.
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:
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:
More advanced methods for selecting devices:
NOTE: If you chose Select Class... or Unselect Class..., a dialog box will be displayed, prompting you to enter the appropriate device class qualifiers, such as "Disk/Hard"; enter the information requested, and click "OK" when you are done.
To get information about a hardware device(s), run an information tool:
The device icon will change color, depending upon the state of the device, and the result of the tool's operation:
For more detailed information, View Device Status.
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:
The device icon will change color, depending upon the state of the device, and the result of the tool's operation:
For more detailed information, View Device Status.
To determine whether or not a selected Field Replaceable Unit (FRU) is failing, run a diagnostic tool on the device:
The device icon will change color, depending upon the state of the device, and the result of the tool's operation:
For more detailed information, View Device Status.
To locate intermittent problems in a hardware device(s), run an exerciser on the device(s):
The device icon will change color, depending upon the state of the device, and the result of the tool's operation:
For more detailed information, View Device Status.
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.
A new window will be displayed, with its own Main Menu Bar.
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.
NOTE: If absolutely necessary, you can click on the "Interrupt" or "Abort" buttons during the update process; however, it is not advisable.
Click on the "Interrupt" button when you want to interrupt the update tool; typically, you will do this when you want the tool to stop sending output to the screen display, and to return to its main prompt.
Click on the "Abort" button, when you want to halt the tool, ending execution of the firmware update.
To run non-device-specific support tools (utilities), do the following:
The "Run Utility" window will be displayed, prompting you to select a utility from a list of all utilities for which you have licensing privileges.
When a tool has detected a device failure, the icon for the device in the system map turns red and 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:
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 (icon turned yellow). If a tool reports a device failure (icon turned red), 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:
After you have performed the procedure to Get Information on a Device, you can look at the information log created for the device:
The Information Log for the chosen device is displayed.
The easiest way to determine the status of a device is by observing its icon on the system map, and noting its color, as well as any text displayed with the icon. The following is a list of icon colors with their meanings:
Status Icon Color Description ------ ---------- ----------- (blank) Blue The device has not been tested Testing Light Blue Testing is in progress QUERY PENDING Orange Query waiting; click icon to respond SUSPENDED Yellow Suspended by the user HUNG Yellow The operation has hung ABORTED Yellow The operation was aborted WARNING Yellow The operation completed, with warnings in the Tool Activity Log INCOMPLETE Yellow The operation could not be completed FAILURE Red The most recent operation failed Success Green The most recent operation succeeded
The fastest way to determine the status of a device is to Interpret the Icons on the System Map. For more information, you can view the Current Device Status:
A window will be displayed, which will inform you of the results (e.g., "Success" or "Failure") for the most recently executed tool, and will recommend further action, as appropriate.
The window also lists all the tools available for the device.
xstm allows you to view the following logs:
For more information on a particular type of log (e.g., the UI Activity Log), click on its underlined hyperlink (e.g., UI Activity Log).
Log contents are unique, but all of the logs displayable under xstm employ a similar log viewing dialog. Using this dialog box you may:
The title of the log viewing dialog box 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" buttons are provided to simplify navigation through these logs when viewing them.
The UI Activity Log contains a record of the errors encountered by the xstm user interface. The log dialog box 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:
The "UI Activity Log" window is displayed.
The Map Log contains a record of what transpired while the system map was being built. The log dialog box 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:
The "Map Log" window is displayed.
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 box allows you to view, save, print , and clear the contents of the log, as desired.
To view the System Activity Log, do the following:
The "System Activity Log" window is displayed.
The information provided by the Information Log is device-specific, but should at least include:
To view the Information Log, use the following procedure:
The Information Log for the chosen device is displayed.
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:
The "Tool Activity Log" for the Information tool will be displayed.
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:
The "Tool Failure Log" for the Information tool will be displayed.
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:
The "Tool Activity Log" for the Verify tool will be displayed.
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:
The "Tool Failure Log" for the Verify tool will be displayed.
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:
The "Tool Activity Log" for the Diagnose tool will be displayed.
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:
The "Tool Failure Log" for the Diagnose tool will be displayed.
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:
The "Tool Activity Log" for the Exercise tool will be displayed.
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:
The "Tool Failure Log" for the Exercise tool will be displayed.
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:
The "Tool Activity Log" for the Firmware Update tool will be displayed.
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:
The "Tool Failure Log" for the Firmware Update tool will be displayed.
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:
The "Tool Activity Log" for the Expert Tool will be displayed.
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:
The "Tool Failure Log" for the Expert Tool will be displayed.
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:
The "Tool Activity Log" for the Utility tool will be displayed.
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:
The "Tool Failure Log" for the Utility tool will be displayed.
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:
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):
For software problems, try the following:
For hardware problems, try the following:
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.
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.
Consult the following for the information needed to determine the cause for a blank or missing icon:
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, Current Device Status, prod_op_xref file, and XStm resource file.
Consult the following for the information needed to determine the cause for an unavailable tool:
The message "Tool expected?" indicates that a particular tool should be available. Whether this is the case can 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 (Current Device 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, Current Device Status, and Current License Level.
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:
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:
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).
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:
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").
You may not be able to start tools, or perform initiation tasks, in the following instances:
In the first instance, the UI Activity 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 (Current Device 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.
You can get context-sensitive help on parts of the xstm interface in two different ways:
Context-sensitive help is only available for HP-UX 10.20 and 11.00.
Parts of STM on which help is available:
Main WindowThe 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.
The easiest way to determine the state of a device is by observing its icon on the system map, and noting its color, as well as any text displayed with the icon. The following is a list of icon colors with their meanings:
Status Icon Color Description ------ ---------- ----------- (blank) Blue The device has not been tested Testing Light Blue Testing is in progress QUERY PENDING Orange Query waiting; click icon to respond SUSPENDED Yellow Suspended by the user HUNG Yellow The operation has hung ABORTED Yellow The operation was aborted WARNING Yellow The operation completed, with warnings in the Tool Activity Log INCOMPLETE Yellow The operation could not be completed FAILURE Red The most recent operation failed Success Green The most recent operation succeeded
For information on how to select a device, see Select Device(s).
In xstm, commands are accessed by means of the pulldown menus listed below. For help on individual menus and commands, select xstm Menus.
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 Exit Daemons->
Tools Options Help ----- ------- ---- Information->* Tool Options-> On Item Verify->* Map... On Tasks Diagnose->* General... On Application Exercise->* On Menus/Commands Firmware Update->* On HomeTopic Expert Tool->* On Help Utility->* On Version Latest Logs-> 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 ------
syslog All
Class... Tool Options->
Matching Devices ------------
Matching Products Information...
Devices Above Verify...
Devices Below Diagnose...
Exercise...
Unselect-> Firmware Update...
-------- Expert Tool...
All Utility...
Class... Tool Launch...
Filter->
------
Set
Clear
The Menubar for xstm offers six menus:
The File Menu has eight selections:
Use this function to save the state of the user interface in a specified file. The following items will be saved:
See also Restore Config....
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".
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 click on "Apply Filter", you will see all the "/users/username" directories on the system displayed in the "Directories" window; similarly, all files with a ".stm" extension will be displayed in the "Files" window. Select the configuration file you want by typing its full path and filename into the "Selection" window; e.g., "/users/username/config.stm". Click on "OK" and the current configuration will be saved to that file.
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.
You enter the path (i.e., directory) and filename of the configuration file from which you wish to restore a saved configuration. You may specify wild cards (file filters), if you wish. For example, you might enter the following: "/users/username/*.stm". Once you click on "Apply Filter", you will see all the "/users/username" directories on the system displayed in the "Directories" window; similarly, all files with a ".stm" extension will be displayed in the "Files" window. Select the configuration file you want by typing its full path and filename into the "Selection" window; e.g., "/users/username/config.stm". Click on "OK" and the configuration will be restored from that 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. xstm operations are recorded as a series of cstm (command line interface of the Support Tools Manager) functions which can be read by:
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.
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."
You enter the path (i.e., directory) and filename of the command file to which you wish to save the commands you are recording. You may specify wild cards (file filters), if you wish. For example, you might enter the following: "/users/username/*.stm". Once you click on "Apply Filter", you will see all the "/users/username" directories on the system displayed in the "Directories" window; similarly, all files with a ".stm" extension will be displayed in the "Files" window. Select the command file you want by typing its full path and filename into the "Selection" window; e.g., "/users/username/config.stm". Click on "OK" and the commands being recorded will be saved to that file.
Use this function to have the xstm read in and execute a sequence of cstm functions saved by the Record Command File... function. Alternatively, any sequence of cstm (command line interface of the Support Tools Manager) functions can be read and executed by this function.
You enter the path (i.e., directory) and filename of the command file from which you wish to read in and execute commands. You may specify wild cards (file filters), if you wish. For example, you might enter the following: "/users/username/*.stm". Once you click on "Apply Filter", you will see all the "/users/username" directories on the system displayed in the "Directories" window; similarly, all files with a ".stm" extension will be displayed in the "Files" window. Select the command file you want by typing its full path and filename into the "Selection" window; e.g., "/users/username/config.stm". Click on "OK" and the commands in the command file you have selected will be read in and executed.
If you no longer wish to run the currently executing command file, select "Cancel".
During any xstm 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 xstm and mstm, such as displaying the system map.
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."
You enter the path (i.e., directory) and filename of the file to which you wish to save your terminal output. You may specify wild cards (file filters), if you wish. For example, you might enter the following: "/users/username/*.txt". Once you click on "Apply Filter", you will see all the "/users/username" directories on the system displayed in the "Directories" window; similarly, all files with a ".txt" extension will be displayed in the "Files" window. Select the file you want by typing its full path and filename into the "Selection" window; e.g., "/users/username/config.txt". Click on "OK" and the terminal output will be saved to that file.
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 xstm session may be executed. Each log entry contains a label containing a timestamp, the user name, and the xstm process ID, in order to distinguish between separate xstm sessions on the same machine (for example, "Wed Dec 7 15:18:49 1994: User Name: bobcap, xstm Process ID: 27697").
The UI Activity Log is not temporary; all other xstm 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.
If you select this command, you will clear the current UI Activity Log of its present contents.
Use the Administration cascade menu to manage the diagnostic system and its configuration, including the following functions:
Use this function to leave the user interface, and return to the prompt from which you launched xstm. The connection to the Unit Under Test is shut down, and all interactive tool execution is terminated. Non-interactive tools will continue execution.
The Record Command File Menu has two selections:
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.
Use this function to disable recording of functions you are executing. The function is unavailable unless recording is in progress.
The Record Output Menu has three selections:
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.
You use this function to disable terminal output recording. The function is unavailable, unless recording is in progress.
You use this function to store a copy of the system device map. The function is unavailable unless recording is in progress.
The Administration Menu has four selections:
Use this function to have the current test system diagmond daemon reread its configuration file.
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 the xstm.
Use this function to start the diagnostic system on the local machine, i.e., the machine on which the xstm is running, when you are logged on as root.
Use this function to shut down the diagnostic system on the local machine, i.e., the machine on which the xstm 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.
Use this cascade to view the Map Log and System Activity Log for the local Unit Under Test (UUT), when you cannot access the xstm 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 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).
The Local UUT Logs Menu has two selections:
Use this function to view the Map Log on the local Unit Under Test (UUT), without having to be connected to the xstm machine.
See also Local UUT Logs and System Activity Log.
Use this function to view the System Activity Log on the local Unit Under Test (UUT), without having to be connected to the xstm machine.
See also Local UUT Logs and Map Log.
The System Menu has seven selections:
The Sel System to Test cascade contains functions which allow you to maintain a list of test systems, and to select one of these to be the current test system.
The Sel System to Test Menu has three selections:
Use this function to maintain a list of test systems, and to connect to those chosen.
The Host 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.
Multiple systems may be selected, and are connected when the dialog is finished using "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:
A system is selected by clicking its entry in the list. Multiple systems may be selected by using the Shift or Control keys while clicking entries. Test systems are added by typing the system name into the "Test System to Add:" field, and pressing the "Add" button. Hitting the RETURN key after typing in the new system name will also add the system. Selected entries are removed from the list by pressing the "Delete" button.
When "OK" is hit, a dialog box will be displayed, prompting you for the login name and password to be used for the connection(s).
This dialog box 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 click on the "Add" button or hit Return.
To delete a system from the list of systems to test, click on the system's entry in the "System to Test" field; then click on "Delete".
When "OK" is selected, a dialog box will be displayed, prompting you for your login and password on the system you chose to be connected to.
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 the xstm, 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 the xstm, and will continue to execute any currently active support tools.
If you exit the xstm 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 display windows showing information on the formerly current system are closed.
This dialog box 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 click on the "Add" button or hit Return.
To delete a system from the list of systems to test, click on the system's entry in the "System to Test" field; then click on "Delete".
When "OK" is selected, a dialog box will be displayed, prompting you for your login and password on the system you chose to be the current test system.
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.
This dialog box allows you to disconnect from one or more systems at a time.
To disconnect from a system, click on the system's entry in the "System to Test" field; then click on "OK".
Use this function to write an ASCII copy of the device map to a specified file.
You enter the path (i.e., directory) and filename of the file to which you wish to save the current device map. You may specify wild cards (file filters), if you wish. For example, you might enter the following: "/users/username/*.map". Once you click on "Apply Filter", you will see all the "/users/username" directories on the system displayed in the "Directories" window; similarly, all files with a ".map" extension will be displayed in the "Files" window. Select the configuration file you want by typing its full path and filename into the "Selection" window; e.g., "/users/username/system1.map". Click on "OK" and the current device map will be saved to that file.
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 the xstm is being run.
To print out a hardcopy of the device map to a particular printer, select a printer from the list displayed in the "Printer" window; then click on "OK".
Use this function to determine what hardware is attached to the unit under test. 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 redrawn. All devices are displayed and are unselected.
Whenever this command is executed, the Map Log is created.
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 Remap System 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.
This cascade provides the ability 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.
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 box 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.
If you click on "OK", the current contents of the System Activity Log will be deleted. If you don't wish to delete the current contents of the System Activity Log, click on "Cancel".
The License Menu has three selections:
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.
Any support tools which you cannot run due to insufficient licensing privilege are shown grayed out in the function menus.
The password you type is not displayed on the screen.
See also Install HP-Only and Deinstall.
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.
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.
The password you type is not displayed.
See also Install and Deinstall.
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.
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 popup dialog box will be displayed, which will ask you to confirm or cancel the operation.
See also Install and Install HP-Only.
There are four Daemons menu selections:
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.
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.
Use this key 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" menu selection. Otherwise, this command sends a "kill -9" command to the daemon process.
Choose this menu selection to view a daemon activity log.
This dialog has a clear button.
The Device Menu has six selections:
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:
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 Activity Log... and the Failure Log....
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 Activity Log... and the Failure Log... for all devices.
This menu allows the user to select devices in a number of different ways. These include:
Use this function to select all the devices displayed in the hardware map.
Use this function to select several devices at once, adding these to devices already selected. All devices to be chosen 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 Current Device Status command.
Examples of "Devices" include:
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 Current Device Status command.
Examples of "Products" include:
Don't select anything if you do not want to use the product to select devices.
Scroll through the "Devices [Device Type/DeviceQualifier]" window to the devices you wish to select (e.g., "Disk/Hard") and click on it with the mouse. Multiple selections can be made, using the control key. Next, move to the "Products [Product (Qualifier)]" window, or click on "OK", as desired. "Device Type" and "Device Qualifier" are displayed by the Current Device Status command.
Scroll through the "Products" window to the product you wish to select, (e.g., "SCSI Disk (SEAGATE31200N)", and click on it with the mouse. Multiple selections can be made, using the control key. "Product" and "Qualifier" are displayed in the device map and by the Current Device Status command.
When satisfied with your selections, click on "OK".
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 Current Device Status command.
This command will select all devices which are the same product as those devices which are already selected.
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.
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.
This menu allows the user to deselect devices in a couple of different ways. These include:
Use this function to deselect all devices on the hardware map.
Use this function to deselect several devices at once, removing these devices from the number of already selected devices. All devices to be deselected must satisfy one of the items specified in the dialog: "Devices" or "Products". Currently selected devices which do not meet this criteria are not deselected by this function.
"Devices" is defined as "Device Type/Device Qualifier." "Device Type" and "Device Qualifier" are displayed by the Current Device Status command.
Examples of "Devices" include:
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 Current Device Status command.
Examples of "Products" include:
Don't select anything if you do not want to use the product to deselect devices.
Scroll through the "Device Type and Qualifier" window to the device type and qualifier you wish to deselect (e.g., "Disk/Hard"), and click on it with the mouse. Next, move to the "Product" window , or click on "OK", as desired. Multiple selections can be made, using the control key.
Scroll through the "Product" window to the product you wish to deselect (e.g., "SCSI Disk (SEAGATE31200N)", and click on it with the mouse. Multiple selections can be made, using the control key.
When satisfied with your selections, click on "OK".
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.
The Tools Menu has eight selections:
See Tools Submenu for help on running these tools, for logging help, and for additional information.
Use this function to create a log of information specific to each selected device, which has an information function, including:
Typically, the firmware revision code, if firmware is present in the selected devices, 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..., Failure Log..., and/or Activity Log... for information retrieved by the tool about the hardware.
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 click on the device, or select Display "Query Pending" from the "Tools --> Tools Management" menu, 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 Failure Log... for information on tool failures, and the Activity Log... for all other tool activity information.
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, you must click on the device, or select Display "Query Pending" from the "Tools --> Tools Management" menu, 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 Failure Log... for information on tool failures, and the Activity Log... for all other tool activity information.
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 click on the device, or select Display "Query Pending" from the "Tools --> Tools Management" menu, 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 Failure Log... for information on tool failures, and the Activity Log... for all other tool activity information.
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.
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.
A new window is automatically created so that you can communicate directly with the expert tool or interactive utility.
Use this function to access the cascade menu for running support tools which are not device-specific. Current tools include logging and disk backup tools.
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.
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.
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 Select this radio button 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" window and click on it; then click on "OK".
Most Recent Utility Executed on Device Select this radio button 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" window and click on it; then click on "OK".
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.
This dialog allows you to select a utility from a list, and get more information about it.
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.
Use this function to access the cascade 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 Pending".
The Tools Submenu has five selections:
Use this function to start executing the tool you have selected from the main menu, on all the selected devices which have that tool available.
Use this function to view the log(s) generated by an Information request on all selected devices for which an information log exists. This function only exists on the cascade menu for the Information tool.
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).
Use this function to review the log which contains details concerning failures encountered during the most recent execution of a tool on all selected devices. The function is valid only when a Tool Failure Log for the tool exists for the selected device(s).
Use this function to display help information unique to the tool for all selected devices. It may always be run, because it does not access the device(s) to obtain its information.
Use this function to stop execution of the currently running tool on all selected devices.
Use this function to momentarily halt execution of a support tool running on all selected devices. Suspending an interactive tool causes the tool's window to freeze.
See also Resume Tool.
Use this function to restart execution of a suspended tool running on all selected devices.
See also Suspend Tool.
Use this function to halt execution of a utility running under the xstm. 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).
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.
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".
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.
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.