NAME

m385diag − MVME385 FDDI interface diagnostic test utility

SYNOPSIS

m385diag [-?bv] [-c count] [-d device] [-m minor_test] [-t test]

DESCRIPTION

The m385diag command is a diagnostic test utility for the MVME385 Fiber Distributed Data Interface (FDDI) board.  The user level command interacts with the m385 STREAMS driver via defined ioctl(2) commands (I/O controls).  The device driver then performs the requested diagnostic test on the hardware that it controls, returning the result to the utility.  The command then gives an indication of the individual test result, which is ultimately either "PASSED" or "FAILED".  It should be noted that the diagnostic tests run by this utility are of a non-destructive nature.  That is to say they can be run on a loaded system, with the interface up, and leave the system operational when the tests are completed.  However, the services that the interface provide are temporarily taken off-line for the duration of the tests.  This can impact the system, possibly introducing side affects at higher levels, if the interval of the test is suffuciently long. A knowledgable system administrator is the intended user of this utility. A practical usage is for on-line system analysis.

OPTIONS

The user may issue the following options on the m385diag command line:

-? Help flag. 
This flag will display a brief usage message to the user, yet offering enough information for the advanced user to run the command properly.

-b Board type flag. 
The -b flag will query the m385 driver as to the model number of the hardware used for the given controller.  The utility will then display the result on stdout and exit.  The possible values are: MVME385-100 or MVME385-120. 

-v Verbose mode flag. 
The -v flag will cause the utility to display further detail of its operation to stdout. 

-c count
Specify the number of iterations for the specified set of tests.
(default: 1)

-d device
Specify the device name (path) of the m385 device on which the diagnostic tests are to be run. 
(default: /dev/m385_c0)

-m minor_test
Specify the minor test number to be executed. A value of zero implies that all minor tests be run in sequence.
(default: 0)

-t test Specify a test number to execute.  A value of zero implies that all major tests be run in sequence. 
(default: 0)

Test Descriptions

The test descriptions will be broken into sections.  Each section below will enumerate and explain briefly each test available for the particular model of hardware.  The detailed documentation of the individual tests is contained in the hardware manual for the controller.  The test numbers will be shown in brackets and the minor_test numbers will be shown in parentheses.  The additional level of indentation is also provided to help separate the (major) tests from the minor tests. 

MVME385-100 Tests

[0] All Tests

(0) All Minor Tests

[1] Memory Tests

(0) All Minor Tests
(1) Static RAM
(2) Buffer RAM
(3) Short I/O RAM

[2] FDDI Loopback Tests

(0) All Minor Tests
(1) FORMAC Loopback
(2) ENDEC Short Loopback (Port A)
(3) ENDEC Long Loopback (Port A)
(4) External Loopback (Port A)
(5) ENDEC Short Loopback (Port B)
(6) ENDEC Long Loopback (Port B)
(7) External Loopback (Port B)

[3] VME DMA Tests

(0) All Minor Tests
(1) Short I/O DMA
(2) Standard DMA

[4] NOVRAM Test

(n/a) No Minor Tests

[5] 9513 Counter Tests

(0) All Minor Tests
(1) Counter Chip 1
(2) Counter Chip 2

[6] CMT PAL Tests

(0) All Minor Tests
(1) CMT PAL (Port A)
(2) CMT PAL (Port B)

[7] CAM Test

(n/a) No Minor Tests

MVME385-120 Tests

[0] All Tests

(0) All Minor Tests

[1] Memory Tests

(0) All Minor Tests
(1) Excecution RAM
(2) Static RAM
(3) Buffer RAM

[2] FDDI Front End Tests

(0) All Minor Tests
(2) Port A ELM Short Loopback
(3) Port A ELM Long Loopback
(4) Port A External Loopback
(5) Port B ELM Short Loopback
(6) Port B ELM Long Loopback
(7) Port B External Loopback
(8) Port A ELM Path
(9) Port B ELM Path
(10) Port A FCG Path
(11) Port B FCG Path
(12) Report BIST
(13) Report FSI
(14) Report MAC
(15) Report ELM

[3] VME DMA Tests

(0) All Minor Tests
(2) Standard DMA
(4) Raw Data
(5) Read Buffer
(6) Write Buffer
(7) VIRQ

[7] CAM Test

(n/a) No Minor Tests

EXAMPLES

The m385diag utility is simple and straight forward to use.  To illustrate this fact, the following few examples are provided:

m385diag -d /dev/m385_c0 -t 0 -m 0

The above command invokes the m385diag utility using the provided device on which to run the tests and it requests that all tests be executed.  The result of this command is seeing each test being run in a sequential order.  This command is equivilent to running the m385diag command with no options, as all values provided in this case are the default values. 

m385diag -t 1 -m 3

The above command invokes the m385diag utility to run a specific test on the default controller (as no -d option was provided).  In this case, we request that test one be run and that we only wish for the third minor test to be executed. 

FILES

/etc/init.d/m385btd,
/etc/rc2.d/S68m385btd

SEE ALSO

drv_getparm(1M), frustat(1M), gold(1M), fddistat(1M),
m385(7)

DIAGNOSTICS

If m385diag terminates normally, it displays a message that indicates whether the requested test(s) passed or failed, and then exits with a 0 status.  If m385diag does not terminate normally, it displays an error message to stderr and returns a non-zero exit status indicating the error number. 
 

  —  MVME385 Diagnostic Utility