#
# 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.5	09/05/21 SMI"
#

1.   INTRODUCTION
2.   HOW TO CONFIGURE CIFS CLIENT
3.   HOW TO CONFIGURE SAMBA SERVER
4.   HOW TO CONFIGURE SUN CIFS SERVER
5.   HOW TO CONFIGURE WINDOWS 2003/2008 SERVER(MANUAL)
6.   HOW TO CONFIGURE NAS SERVER(MANUAL)
7.   HOW TO RUN THE TESTS 
8.   HOW TO CLEAN TEST ENVIRONMENT
9.   HOW TO GET TEST RESULT AND LOGS
10.  CONTACT US

1. INTRODUCTION

This test suite is designed for CIFS client testing. It needs
two machines (a test client and a CIFS server) and the test suite runs
on the client machine. 

Client machine must run snv_84 or later. Server machine can 
be one of the following five systems:

   1. Samba Server (snv_84 or later)
   2. Sun CIFS Server (snv_84 or later)
   3. Windows 2003
   4. Windows 2008
   5. Sun NAS system

User must run the test suite as root 

2. HOW TO CONFIGURE CIFS CLIENT

a. Select a client that runs on snv_84 or later

b. Install the SUNWstc-dtet package

  - Create a text file named /tmp/INET_TET which only contain one word 'root'.
  - Check this file content by using cat or more command. E.g.
     # cat /tmp/INET_TET
     root

   - Add the SUNWstc-dtet package
     # pkgadd -d <package-location> SUNWstc-dtet

c. Make sure the user has rsh access to server as root

   - Create .rhosts file. 
     # echo "+" > ~root/.rhosts

    CAUTION: THIS WILL MAKE THE SYSTEM TOTALLY INSECURE (any user
    on any system can remote-login to the CIFS server as root) 

   - Modify /etc/default/login file to allow remote root access
     # grep console /etc/default/login
     #CONSOLE=/dev/console

   - Enable rlogin service
     # svcadm enable svc:/network/login:rlogin
     # svcadm enable svc:/network/shell:default

d. Compile and install the test suite
   There are two ways to set up the test environment. 
   1. Install the pre-built package, 
   2. Compile the source code and execute it.

  1. Install test suite package 
   In majority of the cases, the test suite can be installed from
   packages.

     # pkgadd -d <package-location> SUNWstc-fs-cifs-client
E.g. # pkgadd -d  /ws/stcnv-gate/packages/`uname -p` SUNWstc-fs-cifs-client

   Always install a fresh copy of the test suite package.  If a version
   of the package is already installed on the system, first remove it:

     # pkgrm SUNWstc-fs-cifs-client
   
   ALTERNATIVELY, the test suite can be compiled from source.  To do
   this, perform the following steps.

   - obtain the test suite source as a non-root user

     Obtain the test suite source code from your source code repository 
     which will contain the following directory structure 
     <WS_ROOT>/usr/src/suites/fs/cifs-client

     where <WS_ROOT> is the root of the workspace under which the
     cifs-client test suite resides.

   - set up CTI-TET environment variables and PATH

     $ export CTI_ROOT=/opt/SUNWstc-dtet/contrib/ctitools
     $ export PATH=$CTI_ROOT/bin:$PATH

   - compile the test suite and create the test suite package

     $ cd <WS_ROOT>/usr/src/suites/fs/cifs-client
     $ /usr/ccs/bin/make package

     This will create the installable test suite package corresponding
     to the machine architecture of the build system.  The package will
     be placed in <WS_ROOT>/packages/<arch>

   - install the test suite package

     # pkgadd -d <WS_ROOT>/packages/<arch> SUNWstc-fs-cifs-client

  2. Compile test suite source code(need not install package)
   To do this, perform the following steps.

   - obtain the test suite source as a non-root user
   
   Obtain the test suite source code from your source code repository
   which will contain the following directory structure
   <WS_ROOT>/usr/src/suites/fs/cifs-client
   
   where <WS_ROOT> is the root of the workspace under which the
   cifs-client test suite resides.

   - set up CTI-TET environment variables and PATH

     $ export CTI_ROOT=/opt/SUNWstc-dtet/contrib/ctitools
     $ export PATH=<PATH-of-cc>:$CTI_ROOT/bin:$PATH

   - compile the test suite and create the test suite package

     $ cd <WS_ROOT>/usr/src/suites/fs/cifs-client
     $ /usr/ccs/bin/make 
  After compiling the source, any test case can be executed directly.

e. Setup the client for testing

   - Setup local test directory.  You need to have a free disk slice
     larger than 11G. If you want to test UFS, run the following 
     command to create a UFS directory:
     # run_test -v test_disk="c1t0d0s7" cifs-client ufs_create

     If you want to test ZFS, run the following command to create 
     zfs test directory:
     # run_test -v test_disk="c1t0d0s7" cifs-client zfs_create

   - Create test users
     # run_test cifs-client user_create

   - Edit /opt/SUNWstc-dtet/systems.equiv file and add server
     hostname int this file if it is Samba Server.

f. This testsuite also uses filebench, which is a framework of 
   file system workloads for measuring and comparing file system performance.
   You can find more information about filebench and configuration on
   opensolaris.org at 
   http://opensolaris.org/os/community/performance/filebench/

   This testsuite uses the default configuration of filebench.


3. How TO CONFIGURE SAMBA SERVER

Do all the steps in section 2, except adding client's hostname
in /opt/SUNWstc-dtet/systems.equiv in last step. 

Then run the following command:
     # run_test cifs-client smbs_setup

4. HOW TO CONFIGURE THE SUN CIFS SERVER

Do all the steps in section 2, except adding client's hostname
in /opt/SUNWstc-dtet/systems.equiv in last step. 

Then run the following command:
     # run_test cifs-client cifss_setup

5. HOW TO CONFIGURE WINDOWS 2003/2008 SERVER(MANUAL)

a. Create test users
   - Create user cifs_user and use "C_sun_123" as its password
   - Create user cifs_user1 and use "C_sun_123" as its password
   - Create user a_share and use "A_sun_123" as its password
   - Create user b_share and use "B_sun_123" as its password

b. Create test directories
   - Create three windows share directories in a partition which has
    more than 4G free space. The directory names are public,
    a_share and b_share.

c. Set permissions
   - Assign read/write permission for the "public" share directory
    to the following users: cifs_user, cifs_user1, a_share and 
    b_share.
   - Assign read/write permission for the "a_share" share directory
    to the following user: a_share.
   - Assign read/write permission for the "b_share" share directory
    to the following user: b_share. 

d. Disable firewall

6. HOW TO CONFIGURE NAS SERVER(MANUAL)

On the browser, use "https://[NAS_Server]" url to login "Sun 
StorageTek NAS OS Web Admin". Or on the Solaris terminal, telnet
the NAS Server and use menu command to open the "StorageTek 
[NAS_model_No] NAS Menu" to do the following operations:

a. Create test users
   -  Create user cifs_user and use "C_sun_123" as its password
   -  Create user cifs_user1 and use "C_sun_123" as its password
   -  Create user a_share and use "A_sun_123" as its password
   -  Create user b_share and use "B_sun_123" as its password
b. Create test directories
   -  Create three share directories: public, a_share and b_share.
c. Configure the Domain
   -  Select "Domain Configuration" (CIFS/SMB Configuration on telnet)
      or "Configure Domains and Workgroups" (on Web Admin) 
d. Reboot the system
   -  Reboot the NAS Server to make the configuration effective.

7. HOW TO RUN THE TESTS

a. Export the environment variables
   - same as step 2.c

b. Run tests

   - To run the tests against a Samba server
     # run_test -R <Server's host name> cifs-client all

   - To run the tests against a CIFS server
     # run_test -v SRV=<Server's host name> cifs-client all

   - To run the tests against a  Windows server
     # run_test -v SRV=<Server's host name> cifs-client all

   - To run the tests against Sun NAS server (We just run smbfs
     tests for NAS Server)
     # run_test -v SRV=<Server's host name> cifs-client smbfs
     # run_test -v SRV=<Server's host name> cifs-client performance/filebench

   - To run a single test case 
     # run_test -v SRV=<Server's host name> cifs-client \
         <test_case_name>:<testcase_id>
     For example:
     # run_test -v SRV=<Server's host name> cifs-client smbfs/mvtest:1

8. HOW TO CLEAN UP TEST ENVIRONMENT

Here is the procedure to clean up test setup on client and server:

a. Client

   - delete the users
     # run_test cifs-client user_delete

   - delete test directories
     To delete UFS test directories:
     # run_test cifs-client ufs_delete
     To delete ZFS test directories:
     # run_test cifs-client zfs_delete

b. Samba server

   - clean up server setup
     # run_test cifs-client smbs_clean

   - delete test directories
     To delete UFS test directories:
     # run_test cifs-client ufs_delete
     To delete ZFS test directories:
     # run_test cifs-client zfs_delete

   - delete test users
     # run_test cifs-client user_delete

c. CIFS server

   - clean up server setup
     # run_test cifs-client cifss_clean
   - delete the test directory
     To delete UFS test directories:
     # run_test cifs-client ufs_delete
     To delete ZFS test directories:
     # run_test cifs-client zfs_delete

   - delete the users
     # run_test cifs-client user_delete

9. HOW TO GET THE TEST RESULT AND LOGS

Test results are saved in a directory under /var/tmp, e.g. 
/var/tmp/results.195672. 

10.   CONTACT US

If you have questions or comments on the test suite, please 
send email to the STC_CONTACT alias mentioned in the STC.INFO
file of this test suite. Details on filing bugs against the test
suite are also included in the STC.INFO file.

Indexes created Wed Nov 25 19:14:01 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.