HP (Hewlett-Packard) 2040D Network Router User Manual


 
Series 2040 Test System
Series 2040 Maintenance Manual V2.00 Diagnostics
21
Selection of the ‘Diagnostic’ option for file output will create a file with all the
information required by STEX to analyze the system. This information
includes the tester type being run, a listing of the Testhead resources as
recorded in the ‘resource.ini’ file or the Registry, and a listing of all tests run
along with any problems encountered during the tests. These results will be
written into a file in the ‘digalog\bin\’ directory. The filename is the date on
which the test was run with the file extension ‘.dxx’, where ‘xx’ is an
incrementing number starting at ‘01’ and going through ‘99’. For example, if
the diagnostic file was written on January 20, 1997, the file name would be
‘jan2097.d01’. If a second file were created on the same day, its name would
be ‘jan2097.d02’, and so on. The first SelfExec file written each day would
carry the extension ‘.d01’. If SelfExec’s file option is not set to ‘Diagnostic’, the
file extension would be ‘.001’, ‘.002’, and so on. These files do not contain
the configuration information required by STEX and will not be accepted as
proper files for analysis by STEX.
Analyzing Selftest Data
When starting the STEX program, the graphics show the Testhead as being
empty. Under the menu item ‘File’ are the selections: Open for EXam, View
Log File, Report Details, Close, and Exit.
Open for EXam - Selecting this menu item opens up a
file selection window showing the files available in the
‘digalog\bin\’ directory with the ‘.dxx’ file extension.
Highlight the desired filename and Click on the ‘Open’
button to select for analysis under STEX. STEX will then
open that file, and examine it to see if it is a valid file for
this program. If the file is not valid for STEX, a message
box will inform the user of this, and the graphics will
return to their default condition. If it is valid, the tester
resource information will be read in for analysis. The boards listed in the
Registry will be placed in the proper slots in the Testhead graphic and the file
will be inspected for any fail data from the tests listed. If fail data or system
errors are found, the program will analyze those results using information
about the tests located in the STEX database — ‘digalog\include\stex.mdb’.
The program will then use this information to calculate the three most likely
tester resources that could cause the problems found in this diagnostic file.