STM Tutorial: Summary This Tutorial will get you started with the Support Tools Manager (STM). It covers the following topics: Start STM. See if STM is installed, then call up STM with the desired interface (xstm, mstm or cstm). Run tools. Select a device(s) from the system map, run the desired tool, and examine results on the system map and/or logs. System map The system map shows the hardware in the system, allowing you to select device(s) for testing and to examine test results.
(Be sure the DISPLAY variable for XWindows is set. For example: export DISPLAY=my_workstation.cup.hp.com Menu User Interface (mstm) - runs on non-graphics HP terminals and provides menu-driven access to your system devices and STM's tools. To start mstm, enter: /usr/sbin/mstm or /usr/sbin/stm/ui/bin/stm -m Command Line User Interface (cstm) - runs on non-graphics terminals and allows the user to create and run scripts to simplify the system management process.
into problems, press the "Break" key, then enter "ABORT" at the MPE/iX prompt. All STM functionality is currently available from the cstm (command-line) interface. STM Dependencies on MPE/iX The Support Tools Manager (STM) is loaded onto the MPE/iX 6.5 system via the Fundamental Operating System (FOS) tape and relies on certain MPE/iX features for its operation.
STM relies on the "Maximum number of connections" networking parameter to be set to an adequate level for it to perform all of its functions. A value of 1400 or higher is recommended for all of STM to work correctly. If less than 1400, (for example, the default 1024), some of the tools under STM, specifically the FW SCSI firmware download tool, will hang and STM will have to be aborted to clear. STM user interfaces (cstm and mstm) uses the /dev/tty device file.
Selecting a device Looking on the system map, we find the disk we want to test, the SCSI disk at path 32.6.0. Select it by clicking on it. The icon appears depressed to show that the device has been selected. Running a Tool With a device selected, the next step is to select a tool (test) to run on it.
As you can see, STM offers several tool types. (Not all tool types are supported on all devices on all operating systems.) In this case, we choose "Verify" to make sure that the new disk has been properly installed and is functional. Select "Verify" from the pull-down menu, then "Run". Protecting Against Harmful Operations Before the verify test begins on some devices, STM prompts you whether to run a Read-Only Test, or a Read/Write Test.
Examining Results A glance at the system map shows the results of the test. If the icon turns GREEN ("Successful"), the device successfully completed the verify test. If the icon turns YELLOW ("Incomplete"), the test was not able to complete for some reason; the device may or may not have problems. If the icon turns RED ("FAILURE"), the test was completed but the device failed. Failure Log When a failure occurs, you can get more information by looking at the Failure Log.
STM Tutorial: Run tools with mstm In this example, we are verifying a new SCSI disk using the menu-driven user interface (mstm). After entering the command to start mstm, you see a system map which shows the devices in the computer system (peripherals, I/O, cards, memory, CPU, etc.
Selecting a device Looking on the system map, we find the disk we want to test, the SCSI disk at path 32.11.0. Select it by moving the up and down arrow keys to the desired device, then pressing the Enter key or the "Select/Deselect" function key. The device entry is highlighted to show that the device has been selected.
Running a Tool With a device selected, the next step is to select a tool (test) to run on it: 1. Move the cursor to the menu bar by pressing the tab key or the "Menubar on/off" function key. 2. Press the left or right arrow keys to move to the "Tools" menu. 3. When the cursor is on the "Tools" menu, press Enter key to see the menu items. 4. Use the up or down arrow keys to select a menu item.
As you can see, STM offers several tool types. (Not all tool types are supported on all devices on all operating systems.) In this case, we choose "verify" to make sure that the new disk has been properly installed and is functional. To start the verify tool, choose "Verify" in the Tools menu, then choose "Run". Protecting Against Harmful Operations Before the verify test begins on some devices, STM prompts you whether to run a Read-Only Test, or a Read/Write Test.
As the test runs, you can follow its progress by watching the device entry on the system map. In the "Last Op Status" for the device, you will see messages like "Starting", "Loop 0/1", etc.
Several possible results are shown in this example: "Successful" means the test completed and the device did not indicate any problems. "Incomplete" means that for some reason the test was not able to complete; the device may or may not have problems. "FAILED" means that the test was completed, but the device failed. Failure Log When a failure occurs, you can get more information by looking at the Failure Log.
The Tool Activity log may also have helpful information. STM Tutorial: Run tools with cstm In this example, we are verifying a new SCSI disk using the command line user interface (mstm). After entering the command to start cstm, you see introductory messages and the cstm> prompt. Enter map at the prompt to display a system map which shows the devices in the computer system (peripherals, I/O, cards, memory, CPU, etc.
Selecting a device Looking on the system map, we find the disk we want to test, the SCSI disk at path 32.11.0. In cstm, this is device number 5. Select the device with the "select (sel)" command. You can specify the disk by the device number ( select device 5 or sel dev 5) or by the path ( sel path 32.11.0 ). Note that an asterisk (*) appears to the left of the selected device(s).
Running a Tool With a device selected, the next step is to select a tool (test) to run on it. To see a list of commands, including the commands to run tools, enter help . For a description of the commands, enter: cstm>help more As you can see, STM offers several tool types. (Not all tool types are supported on all devices on all operating systems.) In this case, we choose "verify" to make sure that the new disk has been properly installed and is functional.
As the test runs, you can follow its progress by entering: cstm>map In the "Last Op Status" for the device, you will see messages like "Starting", "Loop 0/1", etc. Examining Results When the test for device 5 is complete, you will see a completion message such as "Successful" for the device: Several possible results are shown in this example: "Successful" means the test completed and the device did not indicate any problems.
"FAILED" means that the test was completed, but the device failed. Failure Log When a failure occurs, you can get more information by looking at the Failure Log. Select the device that generated the failure, then enter the command to display the Failure Log for the tool that reported the failure. In this example, we will view the failure log that resulted from running the Information Tool on device 3, a SCSI Disk at path 32.9.0.
The log contains a variety of troubleshooting information, including a list of "Possible Causes/Recommended Actions", in order of probability. The first recommended action in this case is to look at the test activity log.
STM Tutorial: System Map Upon startup the HP Support Tool Manager provides you with a system map displaying all of the hardware within the designated system (CPU, memory, device adapters and I/O devices). The system map is used to select the specific devices to test and to display a summary of the test results (device type, device path, last test executed, test status: Successful, Failed, etc.).
device and leave all other selected devices in their current state, Control-left-click on the associated icon.) A pull-down menu (available from the right mouse button) allows you to select a tool to run on the selected device(s) and to view logs containing information gathered by the tools. Example of the xstm system map: STM Tutorial: mstm System Map The menu user interface (mstm) system map displays a character-based view of the system.
To select a specific device for testing, place the cursor on the specific device and press Return; all other devices are unselected. (To select a device and leave all other selected devices in their current state, place the cursor on the specific device and press the space bar.) You can use the TAB key to activate a pull down menu which allows you to select the specific tool that you want to run on the selected device(s).
number or path identifier) specifying the device at the user prompt. Example of the cstm system map: STM Tutorial: Commands The xstm, mstm, and cstm interfaces all have different ways to display menus and accept commands from the user. Both xstm and mstm select commands via pull-down menus; cstm has commands entered on the command line.
Exercise->* Firmware Update->* Expert Tool->* Utility->* Latest Logs-> Tool Management-> On Menus/ Commands... On Home Topic... On Help... On Version... Cascade Menus 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-> ------------------Start Recording... Stop Recording Record Output-> ------------Start Recording...
Run Command File... Record Output-> UI Activity Log... Administration-> Escape to OS Exit Remap System Map Log... License-> System Activity Log... Daemons-> Select Class... Unselect All Unselect Class... Tools ----Information->* Verify->* Diagnose->* Exercise->* Firmware Update->* Expert Tool->* Utility->* Latest Logs-> Tool Management-> Options ------Tool Options-> Map... General... Help ---On Item... On Tasks... On Application... On Menus/ Commands... On Home Topic... On Help... On Version...
"l&" Run logtool. "dte&" Select only disk and tapes and run exerciser. STM Tutorial: cstm Commands In cstm, you simply enter the command name (or its abbreviated form) at the prompt. There are no menus and you can enter any command at any time. The following lists the cstm commands by category. The format is command (abbreviation). See also the Complete Syntax of cstm Commands.
NOTE: Only the least number of characters that make each cstm command and keyword unique need to be entered. Keywords are grouped by category (File, System, Device, etc.), corresponding the xstm menus or mstm function keys.
rescanhw | rhw UUT re-examines configured hardware scanhwlog | shl Record of all system devices in last map license | lic [password {}] Obtain required license level to run tools hplicense | hlic [password {}] Obtain required license level to run HP-only tools deinstalllic | dlic Deinstall licenses on the current test system sysactlog | sal Record of all operations performed by cstm map To explicitly request a map display Device: currdevstatus | cds Display device
diaginfo | dinf View tool-specific help for a device exercise | exc Stress test of target hardware for intermittents exeractlog | eal View log of actions performed on a device exerfaillog | efl View log of test failures on a device exerinfo | einf View tool-specific help for a device firmwareupdate | fwu Update firmware on a selected device fwupdateactlog | fal View log of actions performed on a device fwupdatefaillog | ffl View log of test failures on a device fwupdateinfo | finf View tool-specific help fo
veroptions | vop [execctrl] [iterations {}|time {}|continuously] [behavior] [errorexit|errorcount {}] [testcoverage] [maxcoverage|medcoverage|mincoverage] [gentactlog {yes|no}] [reporterrors|reportwarnings|reportinfo] [queries {yes|no}] Configure verification tool options diagoptions | dop [execctrl] [iterations {}|time {}|continuously] [isolation] [fru|component] [testcoverage] [maxcoverage|medcoverage|mincoverage] [gentactlo
[launchoptions {yes|no}] Configure general interface options Help: help [all|more|syntax||] Access online help version | vers Display current interface version banner STM Tutorial: Logs Most of the time you will get the information you need by looking at the status of device icons on the system map. In xstm, a device icon is green for Successful and red for Failure. In mstm and cstm, device status is reported with a text label, such as "Successful" or "Failed".
In mstm and cstm, the failure log appears as follows: In xstm, the failure log is similarly displayed:
Tool Activity Log If a test result is anything other than Successful or Failure, look at the Tool Activity Log. This log contains testing details and errors for a specific tool on a specific device. For example, if a test results in an "Incomplete" status, the Tool Activity Log may explain that the problem is due to missing device files.
The Tool Activity Log is displayed similarly in mstm and xstm. Other Logs Other logs are less frequently used. NOTE: UUT = Unit Under Test: the computer being tested UI = User Interface: the computer running the STM user interface used by the tester If problems occur while initiating tools, viewing log files, connecting to a UUT, etc.
When errors occur that prevent the UI from functioning correctly, look in the UI Activity Log: File --> UI Activity Log The UI Activity Log contains errors logged by the UI. If diagmond does not start up, look in the Syslog: File --> Administration --> Local UUT Logs --> syslog The Syslog contains information and errors logged by a variety of HP-UX programs.
To run the exercisers long enough to get results , you'll want to set the time to a large value like 20 hours. First, get into the options for Exercisers: xstm: Options | Tool Options | Exercise mstm: Options | Tool Options | Exercise cstm: exeroptions Set the desired time (1200 minutes = 20 hours) by changing from the default time of 10 minutes to 1200 minutes: Both xstm and mstm display a form in which you can change the options. In cstm, you answer a series of prompts to change options.
The rest of the process -- running the tool and examining results -- is just the same as the basic STM process . For details on other commands, options, and tools, see the STM online help system. Summary Start STM Run tools Commands System map Logs Variations http://www.hp.
