Installing the test suites

To install and set up the test suites:

1. Install the ndtests package from the HDK CD-ROM or from the HDK homepage. These test suites are updated and enhanced periodically; we recommend downloading the latest version from the web site whenever possible. Installation instructions are provided in the /info hierarchy on the HDK CDROM or in the ? icon on the webpage.

   Note that the ndcert account password must be set to <Enter> or the auto_util test will fail.

   The master and slave systems to be used for testing should be installed on an isolated network. Problems that are detected in the driver being tested could corrupt the network, and the stress tests may adversely affect the performance of other activities on the network.

2. Install the hardware and network driver to be tested on the master machine.

3. Install hardware and a network driver that has already been certified for SVR5 on the slave machine.

4. Log in as root and configure the network on both the master and slave machines:
   

   • Run netcfg and do the following:

     • Select ->Hardware->Add new LAN adapter... and select your adapter; select Continue.

     • Select TCP/IP, select Add, and configure the TCP/IP protocol.

     • Select OK.

     • Select Protocol-> Add protocol....

     • Select IPX/SPX. Do not select IPX/SPX as part of TCP/IP. Select Add.

     • Configure the IPX/SPX protocol by setting the 'External network number' to 0x1 on both machines. Use the defaults for the remaining parameters. Select "OK".

     • Exit netcfg.

   • Set up the /etc/hosts and /etc/hosts.equiv files on the master and slave machines so that rsh and rcp work correctly between the slave and master machines. To do this, edit the files on each machine appropriately:

     • Edit the /etc/hosts file to include the name and IP address of the other machine. The format of this file is:

          <IP_address>	<machine_name>
       

     • Edit the /etc/hosts.equiv file to include the name of the other machine. The format of this file is:

          <machine_name>
       

   • Reboot the system:

        shutdown -y