Running diagnostics on the DTTA

Ensure Blueworx Voice Response has been shut down before running hardware diagnostics (otherwise Blueworx Voice Response will experience unexpected failures).

To run DTTA hardware diagnostics, do the following:

Login as the root (or obtain superuser privileges) if you have not already done so.
To set up the diagnostic test environment, type the following command, then press Enter:
```
export RPQPATH=/usr/lpp/devices.iop_rpq
```
then type the following command, and press Enter:
```
export PATH=$PATH:/usr/lpp/devices.iop_rpq/bin
```
this may take a few minutes.
To test an adapter once, type the following command, then press Enter:
```
rpqtest adapter_number 99 -I
```
Where adapter_number is the card number corresponding to rpqioadapter_number. You will be asked to confirm the PCI Mezzanine Connector (PMC) ID (this should be 0xa1331). rpqtest will proceed through the testing. If the diagnostics do not find any problems with the adapter, they will end with the message Test completed.
To test a single adapter continuously until it has stopped, add the -C option to the previous command, as follows:
```
rpqtest adapter_number 99 -I -C
```
where adapter_number is the card number corresponding to rpqioadapter_number. This is a good reliability test.
Note: rpqtest does not require wrap plugs to be installed on the telephony (RJ45) interface.
You should repeat rpqtest for each adapter in the system to make sure that the hardware is working.
If any test fails, the most likely cause is a faulty adapter which should be replaced.

Note: For the DTTA, the Field Replaceable Unit (FRU) is the entire adapter.