PSD TESTS MENU
--------------
 	1.  Utilities/
 	2.  Node Tests/
 	3.  Message Network Tests/
 	4.  MIO Module Tests/
 	5.  SCSI Device Tests/
 	6.  HiPPI Module Tests/

NOTE:  The back slash (/) immediately following a test name indicates
       that the test is a directory and that there are a series of
       tests contained within that directory.  Any test without a
       back slash indicates an individual test.


MESSAGE NETWORK TESTS
---------------------

   The Message Network Tests check the router backplane and the node-to-node
   communications through the router backplane. They also include system RPM 
   tests. Following are the Message Network Tests along with a description
   of each test:

 	1.  RPM Global Clock Test
 	2.  Mesh Routing Chip Loopback Test
  	3.  CRC Error Test
   	4.  Transmit and Receive Test (Ignored)
    	5.  Concurrent Receive Test (Ignored)
     	6.  Router Test (Ignored)
      	7.  Channel Arbitration Test (Ignored)
       	8.  Concurrent Router Test (Ignored)
	9.  Multi-Hop Test (Ignored)
       10.  Neighbor Concurrent Comm Test
       11.  Node Concurrent Comm Test
       12.  Channel Mask Concurrent Comm Test (Ignored)
       13.  Generic Transmit and Receive Test (Ignored)
       14.  RPM Mesh Counters Test


RPM Global Clock Test 
   The RPM Global Clock Test verifies the diagnostic station's global
   clock and the RPM's global clock counter on the nodes. The test includes
   several steps. The global clock is stopped and the nodes verify that the 
   RPM's global counters are not incrementing. A local rpm global counter 
   reset is issued and the nodes verify that the counters are cleared.
   The global clock is then started and the nodes verify that the RPM's
   global counters are incrementing. Finally, the global clock is stopped 
   again and the host verifies that all nodes' global counters are within
   1 micro second from each others. The bootnode is used as a reference 
   for checking the global counters accuracy. If the bootnode is logically
   ignored, the next available node is selected. If all nodes counters are 
   not incrementing, it is assumed that the global clock on the diagnostic
   station's corelis card is not functioning.

Mesh Routing Chip Loopback Test 
   The Mesh Routing Chip Loopback Test transmits and receives a message
   using a null routing probe. This forces the MRC to loop the message
   back into the node. The message is then received and compared with
   what was written. An error message is generated if there is a difference.
   This test checks as much of the communication hardware as possible
   without requiring that two nodes communicate with each other. 

CRC Error Test 
   The CRC Error Test transmits and receives a message with a null
   routing probe and a corrupted CRC. The message is then received
   and a CRC error is expected. If a CRC error is not detected, an
   error message is generated. A message is then transmitted with a
   null routing probe and a normal CRC. If a CRC error is detected,
   an error message is generated. This checks the node CRC error
   detection circuits without requiring that two nodes communicate
   with each other. 

Transmit and Receive Test 
   The Transmit and Receive Test individually checks each of the node-to-node
   links. Each node transmits a message to its neighbors in a north,
   south, east, west sequence. The receiving nodes compare the message
   received with an expected pattern. An error is reported if a difference
   is detected.

Concurrent Receive Test 
   The Concurrent Receive Test checks the ability of the MRC to concurrently
   receive a message from its neighbors. Each node is tested individually.
   All neighbors are simultaneously commanded to transmit to the node
   under test. The node under test receives and checks all of the
   messages.

Router Test 
   The Router Test checks the ability of the MRC to route messages.
   Each MRC is tested individually. The test is performed as follows.
   The node north of the node under test transmits to the node south.
   South transmits north. East transmits south, west, then north.
   West transmits north, east, and south. The receiving nodes verify
   the messages. Each transmit and receive occurs individually.

Channel Arbitration Test 
   The Channel Arbitration Test checks the ability of the MRC to arbitrate
   simultaneous messages through a channel. Each MRC is tested individually.
   All input neighbors of the node under test and the node under test
   simultaneously transmit to the output neighbor. 

Concurrent Router Test 
   The Concurrent Router Test checks the ability of the MRC to simul-
   taneously route messages to different nodes. Each MRC is tested
   individually. The neighbor to the north of the node under test transmits
   to the neighbor south of the node under test. The node to the east
   transmits west and the node to the west transmits east. The node under
   test performs an MRC internal loopback. All transmits occur simul-
   taneously. The receiving node verifies the messages.

Multi-Hop Test 
   The Multi-Hop Test individually checks the capability of each node
   to transmit a message to all other nodes in the system one at a
   time. Each node transmits to all other nodes (one at a time) in
   the system. The receiving nodes verify the messages. 

Neighbor Concurrent Comm Test 
   The Neighbor Concurrent Comm Test simultaneously checks all of
   the MRC capabilities for communicating between each node and its
   neighbors. Each node transmits to its neighbors, receives, and
   checks messages. 

Node Concurrent Comm Test 
   The Node Concurrent Comm Test simultaneously checks all of the
   MRC capabilities for communicating between each and every node
   in the system. Each node transmits to all other nodes including
   itself, receives, and checks messages.   

Channel Mask Concurrent Comm Test 
   The Channel Mask Concurrent Comm Test assists in engineering and
   manufacturing debug of the routing backplane. The user is prompted
   for transmits on each of the MRC channels. MRC channels are north,
   south, east, west, and the internal loopback. Each node transmits,
   receives, and checks messages on channels which are not masked.

Generic Transmit and Receive Test 
   The Generic Transmit and Receive Test assists in engineering and
   manufacturing debug of the node boards and the routing backplane.
   The user is prompted to enter source and destination node numbers
   for messages. All messages are transmitted simultaneously. The
   destination nodes receive and check the messages. 

RPM Mesh Counters Test 
   The RPM Mesh Counters Test verifies that all four ports (North, South, 
   East and West) of the RPM Mesh counters are functional. Of course, the 
   Mesh network needs to be functional before you run this test. You can
   verify the Mesh by running other mesh tests. The test includes several
   steps.  A local reset to the four mesh counters is issued. Then, the
   nodes verify that the counters are cleared. "Neighbor Concurrent Comm" 
   test is invoked with 1k message length to generate some mesh traffic.
   If the mesh test pass, the nodes verify that the rpm mesh counters are
   incrementing.
