#
# CDDL HEADER START
#
# The contents of this file are subject to the terms of the
# Common Development and Distribution License (the "License").
# You may not use this file except in compliance with the License.
#
# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
# or http://www.opensolaris.org/os/licensing.
# See the License for the specific language governing permissions
# and limitations under the License.
#
# When distributing Covered Code, include this CDDL HEADER in each
# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
# If applicable, add the following below this CDDL HEADER, with the
# fields enclosed by brackets "[]" replaced with your own identifying
# information: Portions Copyright [yyyy] [name of copyright owner]
#
# CDDL HEADER END
#

#
# Copyright 2009 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#
# ident	"@(#)README	1.2	09/09/03 SMI"
#

DESCRIPTION:
============

This test suite tests the functionality and performance of WiFi drivers.


PREREQUISITES:
==============

The SUNWstc-tetlite test harness package is required to be installed,
or be accessible via nfs.

This test suite requres two test machines.  Both of them should have a
WiFi and a NIC interfaces.  The NIC interface is used to control the
execution of the test suite.  Rsh service should be enabled on remote
host for user root.  Here is the steps to enable rsh service:

# echo "+ +" > $HOME/.rhosts;
# svcadm enable svc:/network/shell:default;

If the system is OpenSolaris instead of Nevada, please disable nwam service
and enable physical:default service.

# svcadm disable svc:/network/physical:nwam
# svcadm enable svc:/network/physical:default

Finally, another command is needed to enable rsh service for OpenSolaris.

# rolemod -K type=normal root

Driver-wifi test suite uses uperf to do performance test.  User should provide
uperf binaries.  The test suite provides a default value for Sun internal
users in configure file config/test_config.
UPERF=/net/pae.sfbay/export/home/uperf/latest/uperf
Please note that this path is subjected to change without notification by PAE.
For external users, please install uperf manually on both machines at the same
location and set UPERF variable accordingly.

Uperf is a network performance tool that supports modelling and replay of
various networking patterns. Uperf was developed by the Performance Applications
Engineering group at Sun Microsystems and is released under the GNU General
Public License Version 3.
For more information, please visit the homepage http://www.uperf.org and the
following directories for Sun internal users.
/net/pae.sfbay/export/home/uperf
/net/pae.sfbay/export/home/ncs


CTI-TET PACKAGE INSTALLATION:
=============================

The CTI-TET package is called SUNWstc-tetlite and installs into "/opt"
by default.  Installation is via the standard Solaris package
installation tool pkgadd(1m).  To install SUNWstc-tetlite simply enter
the following command line as root (or having adopted the root role):

# pkgadd -d <package location>  SUNWstc-tetlite

Where <package location> refers to the path containing the SUNWstc-tetlite
package directory.

o It is recommended that you install the packages from scratch, rather
  than on top of an existing installation.  Thus, if an old version of
  the tests is installed, remove it:

# pkgrm SUNWstc-tetlite

It is also acceptable to use an nfs accessible version of SUNWstc-tetlite.


TEST SUITE INSTALLATION:
========================

In the majority of cases, the test suite can be installed from packages.
The package is called SUNWstc-driver-wifi and installs into "/opt" by
default.  Installation is via the standard Solaris package installation
tool pkgadd(1m).  To install SUNWstc-driver-wifi simply enter the following
command line as root (or having adopted the root role):

# pkgadd -d <package location>  SUNWstc-driver-wifi

Where <package location> refers to the path containing the SUNWstc-driver-wifi
package directory.

o It is recommended that you install the packages from scratch, rather
  than on top of an existing installation.  Thus, if an old version of
  the tests is installed:

# pkgrm SUNWstc-driver-wifi

It is also acceptable to use an nfs accessible version of SUNWstc-driver-wifi.

Optionally, the test suite source can be installed locally, built in the
source tree and run from that location.
As any user do the following after installing the test suite source :

1. export TET_ROOT=/opt/SUNWstc-tetlite
2. export CTI_ROOT=$TET_ROOT/contrib/ctitools
3. cd $WIFI_WS/usr/src/suites/net/driver-wifi (e.g location)
4. export PATH=/opt/SUNspro/bin:$PATH (or other Sun Studio path)
5. /usr/bin/make

The build can also install into a proto directory below the workspace
root directory.  The workspace root is the directory under which the
usr/src or usr/closed directory is located (so, in the example location
used in step 3 above, the workspace root is "$WIFI_WS").
In addition, test suite packages can be built using the proto directory
and stored in the packages directory below the defined workspace root
directory.  To install the binaries into the proto area, do:

9. /usr/ccs/bin/make install

To create the test suite package, do

10. /usr/ccs/bin/make package


TEST SUITE CONFIGURATION:
=========================

The configure file is config/test_config.

     __________       _________      _________
    |          |     |         |    |         |
    |          |     |         |    |         |
    |       NIC|-----|         |----|NIC      |
    |          |     |         |    |         |
    |      iwk0|     |         |    |iwk1     |
    |          |     |         |    |         |
    |__________|     |_________|    |_________|
     local host        switch       remote host
                      (optional)  (hostname: leape)

Except UPERF, another five variables must be defined to run this test suite.
Two of them have default values.  They are TEST_IP and RMT_TEST_IP.
So for the above picture, please define the configure variables like this:
TEST_IF=iwk0
RMT_HOST=leape
RMT_TEST_IF=iwk1

Some other variables are configurable also. Here is some examples that
could be used:
1. IBSS test scenario will run in three supported modes, none security,
64-bit WEP and 128-bit WEP by default. To run none security mode only,
do like this,

IBSS_SEC_MODES=none

or to run in both none security and 64-bit WEP modes, do like this,

IBSS_SEC_MODES=none:64wep

2. To run uperf/NFS Corrupt test for 20 minutes, do like this,

IBSS_TP{5,6}_DURATION=1200

3. To run uperf/NFS Corrupt test for udp protocol only, do like this,

IBSS_TP{5,6}_PROTOCOLS=udp

or to run for both protocols, do like this,

IBSS_TP{5,6}_PROTOCOLS=tcp:udp

The similar configuration apples to IBSS_TP{5,6}_TRAFFICS and
IBSS_TP{5,6}_SESSIONS also.

To verify the correctness of configuration, do like this,

# run_test driver-wifi configure


TEST SUITE EXECUTION:
=====================

The test suite execution is required to be done as root.

Set up the environment variables:

export TET_ROOT=/opt/SUNWstc-tetlite
export TET_SUITE_ROOT=/opt/SUNWstc-driver-wifi
export PATH=$PATH:$CTI_ROOT/bin

To run the entire test suite, do the following:

# run_test driver-wifi

To run test purpose 4 of IBSS test scenario, do the following:

# run_test driver-wifi ibss:4

To run all test purposes of IBSS test scenario, do the following:

# run_test driver-wifi ibss


EVALUATING TEST SUITE RESULTS:
==============================

At the completion of a test run, a summary of test results will be
displayed on the terminal where the test suite was invoked.  If only
the configure scenario were run, this typically indicates a problem
was encountered.  Details on any issues can be found by viewing the
journal file, the location of which will be reported by TET at the
end of the test run.

The following test status values can be reported:

	PASS - Test ran to completion with no issues
	FAIL - Test ran to completion, but failed to prove the assertion
	UNRESOLVED - Unable to execute test assertion because of an issue
	    in prerequisite steps.
	UNTESTED - Test skipped, either because support for feature missing
	    on test system.


TEST SUITE UNCONFIGURE:
=======================

No test suite unconfiguration step is necessary.  So long as none of
the tests terminated abnormally, the suite will leave the test system
in the same shape that it found it.

Should the test suite exit abnormally (system goes down during testing,
etc.) then the tests may leave behind connected ad hoc network or secure
object. So to clean up the test environment, do the following:

# run_test driver-wifi unconfigure

Indexes created Sun Nov 08 07:40:19 UTC 2009

Terms of Use | Privacy | Trademarks | Copyright Policy | Site Guidelines | Help
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
Copyright © 1995-2008 Sun Microsystems, Inc.