The NFS example below demonstrates the actions, directory/file and forms database needed to create and write a unique file to a file server or DUT (device under test). Each user will create a unique file named "1" to "9999". If more files are needed, modify the arrange in the action ASSIGN VARIABLE <fileIndex SEQUENTIAL 1 9999>.
In Client > Actions, create an action profile with the following NFS actions. Note modify your server IP, server name, auth flavor and mount port according to your device.
ASSIGN VARIABLE <fileIndex SEQUENTIAL 1 9999>
ASSIGN VARIABLE <srcFile Form_0001.$1>
nfs://126.96.36.199:/nfs-test AUTH_FLAVOR=UNIX MACHINE_NAME=centos59-021213 READ_BLOCK_SIZE=32768 WRITE_BLOCK_SIZE=32768 MOUNT_PORT=635
NFS_SUB_CMD CREATE NEW_FILENAME_VAR=<APPLY fileIndex>
NFS_SUB_CMD WRITE FILENAME_VAR=<APPLY fileIndex> BYTE_SIZE=10240000 INPUT_SOURCE_VAR=<APPLY srcFile> STABLE_FLAG=FILE_SYNC
NFS_SUB_CMD READ FILENAME_VAR=<APPLY fileIndex>
NFS_SUB_CMD REMOVE_FILE FILENAME_VAR=<APPLY fileIndex>
The FSTREE specifies the directory of the source file (a directory on your PC) to support the action INPUT_SOURCE_VAR=<srcFile>. In your Client > Actions > Directories tab, create a directory called "nfs_dir" with a file called "nfs1.txt". Please refer to the picture below. Note this is a local directory and file; create them first on your local drive if needed.
In Client > Actions > Forms tab, create a forms database named "Form_0001" to support the action ASSIGN VARIABLE <srcFile Form_0001.$1>. Refer to picture below:
NOTE: The example does not go over the Subnet and Associations configuration. Please see Avalanche online documentation for details on how set up a basic test.