Manage Gateway volumes using the following screens:
The NFS Gateway Volumes List gives a list of volumes that are configured as Gateways.
The ConsoleOne main menu is divided into two panels. The left panel displays the NFSADMIN snap-in and the server that you are logged onto. To see the list of Gateway Volumes, do the following:
Start at the NFSADMIN Main Menu and click on the server name displayed on the left panel.
Click NFS Gateway > Show Volumes.
A list of gateway volumes is displayed on the right panel of the main menu. You can perform the following operations on each of these volumes:
IDXforms:Gateway volume information/IDXIDXvolumes:using the management screens:Gateway volume information form/IDXThe NFS Gateway Volume Information form displays configuration information for a specific Gateway volume. You can also use this form to display the resources used by a remote file system.
Start at the NFSADMIN Main Menu and select a volume from the list of volumes displayed on the right panel of the screen. See "NFS Gateway Volumes List in NFSADMIN" for details on displaying the gateway volumes list.
Right-click a volume.
A pop menu is displayed.
Select Properties from the pop-up menu.
The configuration information for the selected volume is displayed.
You can edit the information if required. After making the changes, click OK to return to the main menu.
This form contains the following fields:
Remote Hostname---the hostname or the IP address of the remote host for the NFS server that contains the exported directory.
Remote Path---the exported directory on the NFS server.
Gateway Volume Name---the name of the NetWare® volume that accesses the NFS file system. The Gateway creates this volume from the information entered on this form. The volume name can contain up to 40 characters.IDXparameters:NetWare volume name/IDXIDXNetWare volume-name parameter/IDXIDXvolume parameters:NetWare volume name/IDX
UNIX* UID Used for Mounting---the UID the Gateway uses when sending a mount request. Depending upon the type of NFS implementation, the NFS server might use this identification to authenticate the mount request. The default is 0, which equates to the root account if the file system is exported with the root access option (--root=hostname where hostname is the name of the NetWare server). Otherwise, 0 equates to the user account named NOBODY (UID is -2). If the file system is not exported with the root access option, change the UID to match that of the owner of the exported directory.
UNIX GID Used for Mounting---the GID the Gateway uses when sending a mount request. Currently, only VMS systems require a valid Group identification to authenticate mount requests. Change the GID to match that of the owner group of the exported directory; the default is 0, which can cause problems with some VMS installations.
RPC Retry Count---how many times the same NFS RPC is sent to an unresponsive remote server. Valid values are integers from 0 to 10. The default is 5. The NFS server might not be able to respond to the NFS request if it is too busy or if the network traffic is heavy. If the NFS server is operating but does not respond to an RPC, use a higher number for this parameter.
RPC Inter-Packet Timeout---how many seconds the Gateway waits for a response from the remote server before resending an RPC. Valid values are integers from 1 to 20. The default is 2. Increase the value of this parameter if the RPC does not get a response or if input/output failure occurs as a result of a slow network or busy NFS server.
NFS Packet Transfer Size---the NFS packet transfer size (in bytes) used when making read and write calls to the remote NFS server. Valid parameter values are integers from 512 to 8192. The default is 8192.IDXparameters:NFS Packet Transfer Size/IDXIDXNFS Packet Transfer Size parameter/IDXIDXvolume parameters:NFS Packet Transfer Size/IDX
Enable Remote NFS Server File Locking---indicates the state of the remote NFS server file locking. When this check box is checked, the Gateway sends a request to the remote NFS server's lock manager to manage lock control from the server. This lock control is in addition to the file locking the Gateway imposes on NetWare clients. File and record locking are then controlled on both the NetWare server and the remote NFS server.
If this check box is not checked, files and records are only locked from the NetWare side. Therefore, data integrity is guaranteed if two or more NetWare users access the file from the same NetWare server. However, another non-Gateway client can still access the same file through the remote server. For more information on file locking, "Managing the Gateway Lock Manager Service Using NFSADMIN."
Access Control Mode---the access control mode that applies to this Gateway. Select this field to display a list of access control modes (described below). The default mode is Gateway Mode #2. For additional information on access controls and converting file characteristics, see "NFS Gateway Access Control" under "Understanding."
Trustee Rights---the rights granted to all NetWare users who are members of the NetWare NDSTM group object mapped to the UNIX group named WORLD. By default, these rights are RWCEMF. If you accept the default rights, NetWare users have all rights except Supervisory and Access Control. All the rights are displayed in the box. Check the check box to select a right and uncheck the check box to deselect a right.
NetWare Volume on Which Shadow Files are Created---the volume where the shadow files are stored. Select this field to display a list of available volumes from which you can choose. The default volume is SYS:.
Mount Volume on StartupIDXparameters:mount volume on startup/IDXIDXmount volume on startup parameter/IDXIDXvolume parameters:mount volume on startup/IDX---indicates whether the Gateway volume is mounted at startup. If you check this check box, the Gaetway volume is automatically mounted each time you start the Gateway service.IDXmounting:automatically/IDX
Make Volume Read-Only---indicates whether users have read and write privileges. If this check box is checked, read-only access will be provided to the users. If this check box is not checked, users will have read and write privileges.
Enable Write Through---indicates whether the NFS Gateway stores modified file data in cache memory for a period of time or writes modified data to the NFS server immediately. This field appears only when the Make Volume Read-Only field is not checked.
If this check box is checked, the application receives an acknowledgment from the Gateway only after the Gateway has passed the request on to the NFS server and has been notified that the data has been successfully written to disk. You should keep this check box checked when you anticipate problems in saving recent changes (for example, if the disk is nearly full or the network is unreliable).
If this check box is not checked, the application that is trying to perform a write operation receives an acknowledgment from the Gateway when the request reaches the Gateway. This improves performance. However, when data is stored in cache memory, there is a possibility that it could be damaged or lost if the NFS server fails before the information is written to disk.
Enable Write Through when Remote Space Falls Below---ensures that data does not get lost if the remote server's disk fills up. This field appears only if the Make Volume Read-Only field and the Write Through field are both set to No.
Valid parameter values are integers from 0 to 1024. The default value is 500. If the disk space on the NFS server falls below the number of kilobytes specified, the data normally stored in cache memory is instead written directly to the remote NFS server. If the NFS server disk fills up and this parameter is not set high enough, the data left in cache memory might be lost.
When enough remote disk space is recovered, the NFS Gateway reverts to storing the data in cache memory.
Number of Blocks Initially Allocated for Volume---ensures that there is enough memory allocated for NFS directory information. A larger value causes the NFS Gateway to reserve more RAM at startup for directory table expansion. The default value is 1 block of 256 kbytes.
If a large NFS Gateway volume is to be mounted, a large block of memory should be allocated. If this memory can be allocated before the gateway volume is initially mounted, it improves the performance of the system. If you are aware of the large size of the NFS Gateway volumes and if memory required for each volume can be preallocated, performance will be highly improved.
The size of the initial block of memory is selected through the NUMBER OF BLOCKS INITIALLY ALLOCATED FOR VOLUME parameter in the "NFS Gateway Volume Information Form in NFSADMIN." Select the volume that needs a larger block of memory and enter the block allocation number. (You can enter a number between 1 and 256.)
The initial number of blocks can be calculated as follows:
NOTE: You can determine the No of Initial Blocks for a particular volume by using the above calculation. For the entire gateway, the Total Memory Required for this Volume should be added and this value should be assigned to the MAX_MEMORY parameter in the NWPARAMS file. You can specify the value for this parameter in the Maximum Size of Cache field in the NFS Gateway Parameters form. For more details, see "NFS Gateway Parameters Form (NFSADMIN)." You can also modify this parameter directly in the NWPARAMS file. For more details, see the description of this parameter in the "Parameters" section.
Example: For a directory containing 140,000 files in a volume, the initial number of blocks should be calculated as follows:
The Default Volume Configuration form displays default configuration information for Gateway volumes. NFSADMIN uses this information when creating new Gateway volumes.
Start at the NFSADMIN Main Menu and click NFS Gateway > Default Config.
The default information is displayed. You can change this if required. After viewing/modifying the details, click OK to return to the main menu.
This form contains the following fields:
UNIX UID Used for Mounting---the UID the Gateway uses when sending a mount request. Depending upon the type of NFS implementation, the NFS server might use this identification to authenticate the mount request. The default is 0, which equates to the root account if the file system is exported with the root access option (--root=hostname where hostname is the name of the NetWare server). Otherwise, 0 equates to the user account named NOBODY (UID is -2). If the file system is not exported with the root access option, change the UID to match that of the owner of the exported directory.
UNIX GID Used for Mounting---the GID the Gateway uses when sending a mount request. Currently, only VMS systems require a valid Group identification to authenticate mount requests. Change the GID to match that of the owner group of the exported directory; the default is 0, which can cause problems with some VMS installations.
RPC Retry Count---how many times the same NFS RPC is sent to an unresponsive remote server. Valid values are integers from 0 to 10. The default is 5. The NFS server might not be able to respond to the NFS request if it is too busy or if the network traffic is heavy. If the NFS server is operating but does not respond to an RPC, use a higher number for this parameter.
RPC Inter-Packet Timeout---how many seconds the Gateway waits for a response from the remote server before resending an RPC. Valid values are integers from 1 to 20. The default is 2. Increase the value of this parameter if the RPC does not get a response or if input/output failure occurs as a result of a slow network or busy NFS server.
NFS Packet Transfer Size---the NFS packet transfer size (in bytes) used when making read and write calls to the remote NFS server. Valid parameter values are integers from 512 to 8192. The default is 8192.IDXparameters:NFS Packet Transfer Size/IDXIDXNFS Packet Transfer Size parameter/IDXIDXvolume parameters:NFS Packet Transfer Size/IDX
Enable Remote NFS Server File Locking---the state of the remote NFS server file locking. When this option is set to Yes (the default), the Gateway sends a request to the remote NFS server's lock manager to manage lock control from the server. This lock control is in addition to the file locking the Gateway imposes on NetWare clients. File and record locking are then controlled on both the NetWare server and the remote NFS server.
If this option is set to No, files and records are only locked from the NetWare side. Therefore, data integrity is guaranteed if two or more NetWare users access the file from the same NetWare server. However, another non-Gateway client can still access the same file through the remote server. For more information on file locking, see "Managing the Gateway Lock Manager Service Using NFSADMIN."
Access Control Mode---the access control mode that applies to this Gateway. Select this field to display a list of access control modes (described below). The default mode is Gateway Mode #2. For additional information on access controls and converting file characteristics, see "NFS Gateway Access Control" under "Understanding."
Trustee Rights---the rights granted to all NetWare users who are members of the NetWare NDSTM group object mapped to the UNIX group named WORLD. By default, these rights are RWCEMF. If you accept the default rights, NetWare users have all rights except Supervisory and Access Control. You can grant a right by selecting it and clicking OK.
NetWare Volume on Which Shadow Files are Created---the volume where the shadow files are stored. Select this field to display a list of available volumes from which you can choose. The default volume is SYS:.
Mount Volume on Startup---whether the Gateway volume is mounted at startup. Setting this option to Yes (the default) automatically mounts the Gateway volume each time you start the Gateway service.
Make Volume Read-Only---whether users have read and write privileges. If this parameter is set to No (the default), users have read and write privileges. If this parameter is set to Yes, file access is restricted to read-only.
Enable Write Through---whether the NFS Gateway stores modified file data in cache memory for a period of time or writes modified data to the NFS server immediately. This field appears only when the Make Volume Read-Only field is set to No.
If this parameter is set to No (the default), the application that is trying to perform a write operation receives an acknowledgment from the Gateway when the request reaches the Gateway. If this parameter is set to Yes, the application receives an acknowledgment from the Gateway only after the Gateway has passed the request on to the NFS server and has been notified that the data has been successfully written to disk.
Setting this parameter to No improves performance. However, when data is stored in cache memory, there is a possibility that it could be damaged or lost if the NFS server fails before the information is written to disk.
You should set this option to Yes when you anticipate problems in saving recent changes (for example, if the disk is nearly full or the network is unreliable).
Enable Write Through when Remote Space Falls Below---ensures that data does not get lost if the remote server's disk fills up. This field appears only if the Make Volume Read-Only field and the Write Through field are both set to No.
Valid parameter values are integers from 0 to 1024. The default value is 500. If the disk space on the NFS server falls below the number of kilobytes specified, the data normally stored in cache memory is instead written directly to the remote NFS server. If the NFS server disk fills up and this parameter is not set high enough, the data left in cache memory might be lost.
When enough remote disk space is recovered, the NFS Gateway reverts to storing the data in cache memory.
Number of Blocks Initially Allocated for Volume---ensures that there is enough memory allocated for NFS directory information. A larger value causes the NFS Gateway to reserve more RAM at startup for directory table expansion. The default value is 1 block of 256 kbytes.
The Detailed Volume Status form displays detailed status information for a Gateway volume.
Start at the NFSADMIN Main Menu and select a volume from the list of volumes displayed on the right panel of the screen.
See "NFS Gateway Volumes List in NFSADMIN" for details on displaying the gateway volumes list.
Right-click a Gateway volume on the list and select the Detailed Status option.
The following screen is displayed.
This form contains the following fields:
Volume Name---the name of the NetWare Gateway volume.
Remote Path---the name of the remote NFS server, a colon, and the full path of the remote file system.
Volume Status---whether the volume is currently mounted.
Remote NFS Server Status---the status of the remote NFS server.
Remote Lock Manager Status---the status of the Lock Manager on the remote NFS server.
Total Disk Space---the disk space used by the Gateway volume, in kilobytes.
Available Disk Space---the amount of disk space available for the Gateway volume, in kilobytes. Available disk space also displays as a percentage of the total disk space.
Total Directory Entries---the number of directory entries for the volume.
Available Directory Entries---the number of directory entries available. This information also displays as a percentage of the total directory entries.