After you have installed the NFS Gateway, you need to configure it before using it. This section describes how to configure certain system settings for the NFS Gateway for the first time.
Change the bind order for the NetWare Server for NFS Gateway functionality.
Refer to TID10070570, available at the Novell Support Web site.
(Conditional) The default value for the Largest UDP Packet Size parameter of NetWare is 33792. This is sufficient to read/write 32 KB of data to/from NFS Server. If your requirement is different from this, then set the value for the Largest UDP Packet Size parameter of NetWare based on the following guidelines:
If you enter a value other than the valid values, but greater than 4609, then the nearest lower valid value is used.
For example, if you enter 7000, then 4608 is used.
IMPORTANT:Because the NFS Gateway uses the nearest 2x value less than the value obtained after subtracting 512 from the Largest UDP Packet Size parameter, this can significantly reduce the read/write transfer size, if 512 is not added to the required parameter value.
For example, if Largest UDP Packet size = 16384, then the actual read/write transfer value used is 8192. This value (8192) is the 2x value, nearest to 16384 - 512.
Verify the readSize and WriteSize values used for a volume by entering the following at the system console prompt:
gymount -d -volparams [volumename]
or
Enter the following command at the system console:
set largest UDP packet size = Required_read/write_size_value + 512>
The Btrieve* configuration file sys:\system\bti.cfg is updated with optimal values for Btrieve* settings during NFS Gateway installation. To modify the settings manually, follow the guidelines listed below.
Set the parameter BalancedTrees = No.
Increase the value of the BackgroundThread parameter.
This is to support large number of operations on a volume simultaneously.
For best performance, set this value based on the average number of mounted gateway volumes. A good standard to follow is to have four volumes for every I/O thread.
For example, if average number of mounted gateway volumes is 100, use 100/4 = 25 I/O threads.
Specifying a value greater than 64 might negatively impact performance, but that depends on the system capabilities.
Set the cacheSize parameter value (in KB) based on your requirements. This setting represents kilobytes (KB).
To determine your requirements:
Maximum Shadow File Size: The estimated size that the shadow file increases to, because of the directory operations.
For example, a volume with 50,000 entries will have a shadow file size of 94 MB. Use this benchmark to estimate the shadow file size.
Working Data Set Size: The sum of the maximum shadow file size of all gateway volumes active at any given time.
Refer to the following table for guidelines to set the cacheSize parameter based on your performance requirements.
|
Performance |
CacheSize Value |
|---|---|
|
Best |
100% of the working data set size or 32768 KB (32 MB), whichever is greater. |
|
Balanced |
For good performance without excessive memory usage, use 20% to 30% of the working data set size or 32768 KB (32 MB), whichever is greater. |
|
Minimum Requirement |
10% of the working data set size or 32768 KB (32 MB), whichever is greater. |
Make sure that system times of the NetWare server and the corresponding UNIX server are synchronized.
Restart the NetWare server for the btrieve configuration changes to take effect.