Network Driver Certification Test Suite

The ndtests package includes test suites used for UnixWare 7 and OpenServer 6 MDI network adapter cards. The tests are:

ndtests(1Mcert): verify the integrity of the MDI driver and associated hardware.
spm(1Mcert): analyze the performance of an MDI network adapter driver.

This version of the ndtest package can be installed and run on UnixWare 7, Open UNIX 8, and OpenServer 6 systems to test any MDI version 2 or 2.1 driver written to DDI version 7, 7mp, 7.1, 7.1mp, 8, or 8mp.

In addition to passing the ndcert test suites, all MDI drivers should be manually checked to ensure conformance to the guidelines given in Developing DDI kernel drivers and MDI style guidelines.

Version 8.0.2 of this package differs from previous versions in the following ways:

The ndcard unit test autodetects all configured drivers under test for testing (fixed in 7.0.0a).
Improvements for verification of DDI-8 based MDI drivers have been made (fixed in 7.1.0).
The spm test of the ndcert test suites no longer transmits packets in the receive interrupt context (fixed in 7.1.0).
The nd-dlpmdi unit test does not give a false failure in the bindmax test case on UnixWare 7.1 (fixed in 7.1.0).
Fixed assorted minor bugs (fixed in 8.0.2d).
Removed obsolete ISDN and SPX tests (fixed in 8.0.2d).
Installation is more portable for future OS releases (fixed in 8.0.2d).
Add support for OpenServer 6 (fixed in 8.0.2d and 8.0.2e).

For current information about the entire UnixWare/OpenServer Hardware Development Kit (HDK) release, see the HDK Release Notes.

Note: Documentation references on this page link to the Product Documentation. They are also available on your local system when the baseMAN, HDKdoc, and HDKman packages are installed.

System requirements

This package has no installation dependencies. It can be installed on UnixWare 7, Open UNIX 8, and OpenServer 6 systems. The O5ndtests package contains similar test suites for OpenServer MDI network card drivers.

Installation

To install the package from:

downloaded files

Log in as root.
Download the package to an installation directory; for example, /tmp.
Use the pkgadd(1M) command to install it by entering:
pkgadd -d /tmp/ndtests

media distribution

Log in as root.
Insert the CD-ROM in the drive
Use the pkgadd(1M) command to install it by entering:
pkgadd -d cdrom1 ndtests

You will be prompted for a directory name where the tests are to be installed.

Configuration

The test suites are configured by logging into the system as the ndcert user and editing configuration files. These files have the suffix ".cfg". For example, to configure the nd-mdi testsuite, edit ~ndcert/nd-mdi.cfg on both the master and slave machines, then execute "auto_mdi".

Known limitations

When running unit tests in single user mode on Open Server 6, you must first log in as root and then type su - ndcert before running the tests.

The ndtests package should only be installed on test machines and executed on test machines connected to a private testing subnet because it can burden a system's networking. Also, if the test machines are not running at the same speed, the slave machine should be the faster one to avoid test failures caused by timeouts.

When configuring the nd-util unit test, you must also set up the /etc/hosts.equiv file on both test machines. Add both the hostname AND the fully-qualified hostname of the other machine to the local /etc/hosts.equiv file.

When configuring nd-util, nd-nfs and nd-tcp unit tests, make sure that the hostnames do not have any blank spaces inserted at the end of the name and the spelling is correct.

The spm test should only be installed and run on Pentium or better systems. If you try to run spm on a 80486 processor, an error message is written to the console and errors will occur with all networking operations. If this occurs, edit the /etc/ap/spam.ap file, comment out all lines and reboot the system to correct the problem.

When testing different drivers on master and slave machines, use the same DDI versions of the drivers or you may experience problems. For example, using a DDI7 driver on the master machine against a DDI8 slave driver will fail (hang) in MD I Unit mdigetunit() test during the verification of DDI7 noncontiguous minor dev ice numbers. DDI8 does not need to test this and so the test hangs.