NetWare NFS Services 3.0 Objects
NetWare NFS Services 3.0 can be configured using ConsoleOne and also by setting the file-based configuration parameters of the various components.
To start ConsoleOne from the client, complete the following steps.
IMPORTANT: Before starting ConsoleOne, ensure that you run NFSSTART on the server that you want to administer.
Start ConsoleOne from the server where NetWare NFS Services 3.0 is installed.
Click NFSAdmin and then the login icon in the toolbar.
Enter the tree name, context name, authorized username, and authorized password.
Click OK.
Enter the hostname or IP address and then click OK.
IMPORTANT: To log in successfully, make sure that the file server name and hostname are the same and that you have logged in to the tree of the server you want to administer. It is not possible to administer a NetWare NFS Services 3.0 on NetWare 5.1 from ConsoleOne on NetWare 6.
Figure 3
NetWare NFS Services 3.0 Objects
WARNING: After the NetWare NFS Services 3.0 installation, two objects are created in the tree: NFAUUser and NISSERV_Servername. Do not delete these objects.
Map the volume SYS: from your client by entering
map n ServerName\sys:
To change the directory to ConsoleOne, go to PUBLIC\MGMT\CONSOLEONE\1.2\BIN and enter
consoleone.exe
On the left panel tree view, click NFSAdmin.
On the toolbar items, click Login.
Expand the NFSAdmin folder and select the server you are logged in to.
HINT: You will now see the NFS Server and NFS Gateway menus. If you expand the Server folder, you can find the subfolders Imports and Exports.
Right-click the server and then click Properties > Directory.
To set access to NDS®, click the NDS radio button.
Enter the fully distinguished name (FDN) of the NDS context where NFS should search for its users.
You can have a maximum of five entries, separated by commas, in this field.
To set the access to Remote NIS, click the Remote NIS radio button and check the Enable Client Access box.
Enter the Remote NIS server name and the name of the domain it serves.
Start ConsoleOne and click The Network > Directory Services.
The list of trees in the network displays.
To log in to the tree where your server is running, double-click Tree Name.
To migrate maps, click the M icon on the toolbar.
After migration, browse the tree to see the NIS Domain objects.
To see the domains served by NIS Server, right-click Properties > Membership.
To see lists of maps, click Domain. To see properties of maps, right-click Maps. To see records, double-click Maps.
To edit the context whose users are served by NIS Server, right-click Domain and then click Properties > Other.
For detailed steps on how to migrate maps, see ConsoleOne-Based Migration.
Start ConsoleOne and log in to the server.
Click NFS Server.
To view exported paths, click Exports on the left panel tree view.
To view and edit exported path information, right-click Path.
To edit information, click Properties.
To remove an exported path, right-click Path and then click Remove.
To export a new path, click NFS Server > Export New Path, fill in the configuration information, and click OK.
To view and edit NFS Server configuration parameters, click NFS Server > Options.
For further details, see ConsoleOne-Based Management for NFS Server.
To install with Novell Cluster Services, see Cluster Services.
The configuration (.CFG) files are used to configure the services. All of these files have the following format:
PARAMETER_NAME = VALUE
Within the .CFG files, a pound sign (#) indicates a comment.
In addition to these configuration files, there are specific files for exported volumes for the NFS Server and for the migration utility. All the configuration files are usually located in the SYS:\ETC directory. To configure the modules, you need to change the desired parameter value in the corresponding .CFG file and restart the module.
NOTE: In a cluster environment, the configuration files will be located in the ETC directory of the shared volume.