C H A P T E R

C H A P T E R 38

Network Hardware Test (nettest)

nettest checks all the networking hardware on the system CPU board and separate networking controllers (for example, a second SBus Ethernet controller). For this test to be meaningful, the machine under test must be attached to a network with at least one other system on the network.

Note - This version of nettest is used for all networking devices, including Ethernet (ie and le), token ring (tr, trp), quad Ethernet (QED), fiber optic (fddi, nf, bf, pf), SPARCcluster trademark 1 system (em), ATM (sa, ba), HiPPI, 100-Mbits per second Ethernet (be,hme), and GigaSwift Ethernet (ce) devices.

The nettest mainly uses the Internet Control Message Protocol (ICMP), and requires at least two machines on a network--the machine under test and another machine reliable enough to be a test target. Both machines must support the Transmission Control Protocol/Internet Protocol (TCP/IP) (ICMP is part of TCP/IP). The target machine must either be configured to respond to ICMP broadcast or to RPC broadcast.

First nettest determines the target machine(s) to test against. If no targets are specified, it sends an ICMP broadcast to find them. If it fails to find all necessary targets, it tries RPC broadcast to the RPC port mapper daemon. If you specify the targets, nettest uses the specified target(s) instead.

After finding the necessary targets, nettest performs the following tests:

Random test--sends out 256 packets with random data length and random data.

Incremental test--sends out packets with length from minimum to maximum packet size using incremental data. (Minimum and maximum values differ for each device.)

Pattern test--sends 256 packets of maximum length, where each packet contains one test pattern, and all byte patterns (0 to 0xFF hex) are used. That is, the first packet contains pattern 0, the second packet contains pattern 1, and so on, until the last packet pattern of 0xFF.

Note - nettest is a scalable test. However, the maximum number of networked devices allowed on a system is 255, and the number of instances for each device is limited to 200. So, if you start the SunVTS exerciser using the -i option to specify a default number of instances for all tests, nettest cannot assign more than 200 instances per each networked device.

nettest Options

To reach the dialog box below, right-click on the test name in the System Map and select Test Parameter Options. If you do not see this test in the System Map, you might need to expand the collapsed groups, or your system may not include the device appropriate to this test. Refer to the SunVTS User's Guide for more details.

FIGURE 38-1 nettest Test Parameter Options Dialog Box

The Configuration section specifies the host name, host ID, host address, and domain name of the system being tested.

TABLE 38-1 `nettest` Options
`nettest` Options	Description
Target Host	Specifies one or more targets to be tested against. Target host entries can be either a host name or an Internet address. When no target host is specified, the test finds necessary targets through broadcasting. The default setting leaves this field empty.
Receive Timeout field	The default is 120 seconds, but can be changed. Use a range from 0 to 600 seconds.
Number of Retries field	The default number of retries before flagging an error is three, but can be changed. Use a range between 0 to 128 retries.
Print Warning	Disabled by default. Click Enable to see warning errors, such as retry on timeout.

nettest Test Modes

Both Connection and Functional test modes are supported by nettest . Different test schemes are performed on the network device based on the mode selected.

TABLE 38-2 `nettest` Test Modes
Test Mode	Supported?	Description
Connection	Yes	Checks whether the device is connected. It searches through all the network interfaces for a specified device name. If `nettest` does not find the device connected, the test fails; otherwise it returns: `device is connected.`
Functional (Offline)	Yes	Performs all three tests (Random test, Incremental test, and Pattern test) sequentially. It allows you to specify options that will perform heavy stress testing.

nettest Command-Line Syntax

/opt/SUNWvts/bin/nettest standard_arguments -o target= h1+h2+... , dev= interface ,test= type ,packets= n ,pattern= hex ,timeout= seconds , retry= n ,warn

TABLE 38-3 `nettest` Command-Line Syntax
Argument	Description
`target=` h1 `+` h2 `+...`	A list of test targets by host name or Internet address.
`dev=` interface	Network interface name. The default value is `le0` for Ethernet networks.
`test=` type	The test type. Type `Random` , `Increment` , or `Pattern` for the desired test. The default value is Random+Increment+Pattern where all tests run.
`packets=` n	Number of random/pattern packets. The default is 256.
`pattern=` hex	Specifies a data pattern, in hexadecimal form. The default is all patterns from `0` to `0xff` .
`timeout=` seconds	Indicates the number of seconds to wait before a timeout; the default is 120 seconds.
`retry=` n	Indicates the number of test timeout retries; the default is three retries.
`warn`	When enabled, prints warning messages.

Note Note - 64-bit tests are located in the sparcv9 subdirectory: /opt/SUNWvts/bin/sparcv9/testname. If a test is not present in this directory, then it may only be available as a 32-bit test. For more information refer to 32-Bit and 64-Bit Tests.