This appendix provides additional information on running the array diagnostics. Use this information with specified sections of Chapter 4 to test the configuration.
There are four major stages of array testing. As the array evolves through various stages of functionality; each can be independently tested. The stages are:
single isolated server with hardware tested (base node)
single server operating on local area network (LAN node)
single server operating on HIPPI network (HIPPI node)
fully operational array (array node)
The diagnostic tests are automatically loaded when you install the array CD software.
These diagnostics test the base nodes of an array (see Section 4.6.5, "Base Node Testing") by:
determining if IRIX 6.1 or greater is installed
determining if the HIPPI software installed
determining if /dev/hippi* devices exist
determining the /dev/hippi* permission level.
performing a HIPPI loopback test via hiptest
 | Note: These tests do not perform additional array node hardware tests. For a description of those tests, see the CHALLENGE/Onyx Diagnostics Road Map (p/n 108-7045-xxx). |
Invoke the test by becoming a superuser and typing:
/usr/array/diags/arraytest -stage base_node
You should get a display similar to the following
STARTUP: DiagsPath = '/usr/array/diags'
NOTICE: Running Array Diagnostics
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Running Diagnostics for Stage 'Base POWERnode' +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Beginning Stage 'Base POWERnode' %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
NOTICE: Testing OS Level
NOTICE: OS Version 6.2-jackj-root is Correct
NOTICE: Testing HiPPI Software Installation
NOTICE: HiPPI Software Installed
If the test was successful, you receive a message similar to the following:
SUCCESS: Diagnostics Succeed for 'Base POWERnode' Stage
If the test fails, because you did not install HIPPI boards (for example), you get the following message:
NOTICE: Testing HiPPI Device Inventory
FATAL ERROR: No HiPPI Devices Show Up In Inventory
These diagnostics provide local area network (LAN) tests (see Section 4.7.2, "LAN Node Testing") on each array node by:
determining if chkconfig network is on
determining if chkconfig nfs is on
determining if chkconfig automount/amd/autofs on
Note: For information on "amd" (array membership daemon), see the reference pages. checking if the array can get IP addresses for each host (with timeout)
checking if the array can ping self (with timeout)
checking if the array can ping other machines (with timeout)
checking if the array can run a guest rsh (remote shell) to other nodes (with timeout)
checking if the array can ttcp between nodes (with timeout)
checking if the array can NFS mount other filesystems (with timeout)
You can invoke the test by becoming superuser and typing:
/usr/array/diags/arraytest -stage lan_node |
| Note: If no hostnames are supplied, the diagnostics assume local node tests only. If you want to test some or all of the nodes, specify the hostname(s) in the command line. |
You should then get display similar to the following:
STARTUP: DiagsPath = '/usr/array/diags'
NOTICE: Running Array Diagnostics
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Running Diagnostics for Stage 'LAN Configured POWERnode' +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Beginning Stage 'Base POWERnode' %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
NOTICE: Testing OS Level
NOTICE: OS Version 6.2 is Correct
NOTICE: Testing HiPPI Software Installation
NOTICE: HiPPI Software Installed
NOTICE: Testing HiPPI Device Inventory
NOTICE: 1 HiPPI Interfaces Show Up In Inventory
.
.
.
NOTICE: Some HiPPI Devices Have Non-Recommended Permissions and Ownership
NOTICE: Calling Stage Is 'lan_node', Bypassing Base Node Loopback Test
SUCCESS: Diagnostics Succeed for 'Base POWERnode' Stage
If these tests are successful, the diagnostics progresses to the next level as shown below:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Beginning Stage 'LAN Configured POWERnode' %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
NOTICE: Ensuring That Local LAN Services Are Properly Configured
NOTICE: Ensured That Local LAN Services Are Properly Configured
NOTICE:
NOTICE: Verifying I Can Ping Myself (disarray.engr.sgi.com)
NOTICE: Successfully Pinged 'disarray.engr.sgi.com'
NOTICE:
NOTICE: Doing 'guest rsh' to Myself (disarray.engr.sgi.com)
NOTICE: Successful 'guest rsh' To 'disarray.engr.sgi.com'
NOTICE:
NOTICE: Testing Local NFS & Automounter
NOTICE: Checking nfs Version On 'disarray.engr.sgi.com'
NOTICE: NFS Installed On 'disarray.engr.sgi.com'
NOTICE: Verifying NFS Configuration Flags
NOTICE: Network/NFS Configuration Flags Are Correct For 'disarray.engr.sgi.com'
NOTICE: Ensuring 'automount' Operational On 'disarray.engr.sgi.com'
NOTICE: Automounter Running On 'disarray.engr.sgi.com'
NOTICE: Entries In 'disarray.engr.sgi.com:/etc/exports' Pass Verification
If the test passes, you should see a message similar to:
SUCCESS: Diagnostics Succeed for 'LAN Configured POWERnode' Stage
If the test fails, you receive a corresponding error message. Recheck the LAN connections and setup, and retry the test.
These diagnostics tests the HIPPI interface and network (see Section 4.8.4, "HIPPI Node Testing").
You can invoke the test by becoming superuser and typing:
/usr/array/diags/arraytest -stage hippi_node
| Note: If no hostnames are supplied, the diagnostics assume local node tests only. If you want to test some or all of the nodes, specify the hostname(s) in the command line. |
You should then get a display similar to the following
STARTUP: DiagsPath = '/usr/array/diags'
NOTICE: Running Array Diagnostics
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Running Diagnostics for Stage 'LAN and HIPPI Configured POWERnode' +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The diagnostics then runs each of the testing stages as follows:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Beginning Stage 'Base POWERnode' %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
If the test is successful, it brings up the next test set.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Running Diagnostics for Stage 'LAN Configured POWERnode' +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
These tests should be followed by the HIPPI test stage as follows:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Beginning Stage 'LAN and HIPPI Configured POWERnode' %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
NOTICE: 1 HIPPI Devices Registered With System
NOTICE: HIPPI Device 'hippi0' Appears in Slot 15
NOTICE: HIPPI Device '/dev/hippi0' Exists With Proper Permissions
NOTICE:
NOTICE: Verifying The 8 Entries In '/usr/etc/hippi.imap'
NOTICE: Ifield For 'gate2-disarray.engr.sgi.com' Is '0x01000000'
NOTICE: (0x01000000 = [L:0 VU:0 W:32 D:LSB PS:Source C:Camp RC:0x000000])
NOTICE: Ifield For 'gate3-disarray.engr.sgi.com' Is '0x01000001'
NOTICE: (0x01000001 = [L:0 VU:0 W:32 D:LSB PS:Source C:Camp RC:0x000001])
NOTICE: Ifield For 'gate2-datarray.engr.sgi.com' Is '0x01000002'
NOTICE: (0x01000002 = [L:0 VU:0 W:32 D:LSB PS:Source C:Camp RC:0x000002])
NOTICE: Loopback Testing HIPPI Interface /dev/hippi0 (Ifield '0x01000000')
NOTICE: Testing HIPPI Device '/dev/hippi0' Via Ifield '0x01000000'
NOTICE: Sending 50 HIPPI Packets: .....................................................
NOTICE: HIPPI Loopback Test Of '/dev/hippi0' Successful
If the test passes, you get a message similar to the following:
SUCCESS: Diagnostics Succeed for 'LAN and HIPPI Configured POWERnode' Stage
If the tests fails, you get a corresponding error message. Recheck the HIPPI interface (cabling and software installation) and then retry the test.
After the entire array has been configured, invoke the array-wide test by becoming superuser and typing:
/usr/array/diags/arraytest -stage array_node
You should get a display similar to the following:
STARTUP: DiagsPath = '/usr/array/diags'
NOTICE: Running Array Diagnostics
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Running Diagnostics for Stage 'Complete Array' +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
NOTICE: Array Is Comprised Of Following Nodes:
NOTICE: <disarray>
NOTICE: <datarray>
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Beginning Stage 'Base POWERnode' %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
NOTICE: Testing OS Level
NOTICE: OS Version 6.2 is Correct
NOTICE: Testing HiPPI Software Installation
NOTICE: HiPPI Software Installed
NOTICE: Testing HiPPI Device Inventory
.
.
.
If these tests are sucessful, it brings up the next stage of testing.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Beginning Stage 'LAN Configured POWERnode' %
% %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
NOTICE: Ensuring That Local LAN Services Are Properly Configured
NOTICE: Ensured That Local LAN Services Are Properly Configured
NOTICE: Ensuring Node Can Get IP Addresses For All Specified Hosts
NOTICE:
NOTICE: Verifying I Can Ping Myself (disarray.engr.sgi.com)
NOTICE: Successfully Pinged 'disarray.engr.sgi.com'
NOTICE: Verifying I Can Ping Other Nodes
.
.
.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Beginning Stage 'LAN and HIPPI Configured POWERnode' %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
NOTICE: 2 HIPPI Devices Registered With System
NOTICE: HIPPI Device 'hippi0' Appears in Slot 15
NOTICE: HIPPI Device 'hippi1' Appears in Slot 15
NOTICE: HIPPI Device '/dev/hippi0' Exists With Proper Permissions
.
.
.
The test continues to go through all the array evolution stages until completion. If errors are encountered during testing, the diagnostics stop immediately and display the corresponding error message.