NFS Gateway for NetWare 6.5

1.0 Overview

The information in this Readme file pertains to the NFS* Gateway for NetWare^® 6.5.

The NFS Gateway provides connectivity between NetWare and UNIX* file systems.

The NFS Gateway enables NetWare servers to mount exported paths (typically from UNIX servers) over the NFS protocol and expose them as NetWare NSS volumes. Using the NFS Gateway, NetWare clients can transparently access files and directories on any NFS server system on the network.

1.1 What's New

This release of the NFS Gateway has the following new features:

• You can now use the iManager Web-based administration utility to administer NFS Gateway.

  For details, see iManager-Based Administration chapter of the NFS Gateway for NetWare 6.5 Administration Guide.

• Dynamic configuration is now supported for both NFS Gateway and mount parameters.
• For Gateway volumes, you can now specify whether or not to dynamically set RPC timeouts based on network behavior.
• Supports the upgrade of this product from NFS Gateway for NetWare 6 to NFS Gateway for NetWare 6.5.
• The showmount utility for NetWare lets you view the list of mounted volumes. Use this utility to view the following lists:
  • List of paths that have been exported
  • All remote mounts
  • Remotely mounted directories

• For Gateway volumes, you can now specify whether the NFS requests are enforced to go with anonUid and anonGid.
• It has a new install that provides several improvements:
  • It prompts to accept the product license.
  • File backup

• The uninstall provides for file restoration.
• It incorporates the changes in the LSS interface for NSS 3.x.
• It is now SMP enabled.
• It provides dynamic mounting and unmounting of gateway volumes over UDP protocol.
• Volumes can be accessed through CIFS clients.
• It provides interoperability with different flavors of NFS Servers that are widely used in the various user environments.
• NFS Gateway for NetWare 6.5 is cluster-enabled for high availability and load balancing.
• File I/O error handling is improved. All file I/O errors are now reported to the users connected through NCP^TM.
• Symbolic and hard links are now supported.
• Unicode* character support is enabled.
• The logging feature enables viewing errors, information on the current operation, and warning messages.

  The log messages specific to each volumes are saved as shadowVolume/gateway/volumename.log, where the shadowVolume is the volume used to store the shadow files for this volume and volumename is the volume specified in the gymount.

  The general log messages for NFS Gateway are saved as shadowVolume/gateway/system.log, where the shadowVolume is the volume specified in the -shadowVolume of nfsgy.

1.2 What's Not Supported

• NFS Gateway does not support NFS and mount protocols over TCP.
• NFS Gateway does not support the Network Lock Manager protocol and sparse files, so database files are also not supported.
• SUID is not supported.

  For example, if the SUID bit is set for the executable file, then the files/directories created using this executable will not have the UID of the executable; they will have the UID of the user who executes the executable file.

2.0 System Requirements

Meet the following requirements before installing NFS Gateway for NetWare 6.5:

• Change the bind order on the NetWare Server to support NFS Gateway functionality.

  To do this, follow the instructions from TID 10070570 available at Novell Support Web site.

• Install the support for Java sockets and TCP/IP patch for NetWare 6.5. The patches are available as jsocknfs.exe and tcp654j.exe from the Novell Support Web site.
• Install NetWare 6.5 Support Pack 1.
• Have a minimum of 32 MB RAM to load with default parameter values.
• Make sure that there is adequate free space on the volume where the shadow files are to be stored.

  To determine free space requirements, refer to Setting Up the NFS Gateway in NFS Gateway for NetWare 6.5 Administration Guide at the root directory of the product.

• For listing large directories, typically with more than 30,000 entries, increase the value of shadowCacheSize parameter.

  For more information, refer to Setting the NFS Gateway Parameters in Setting Up the NFS Gateway, Setting Up the NFS Gateway in NFS Gateway for NetWare 6.5 Administration Guide at the root directory of the product.

3.0 Documentation

The following sources provide additional information about NFS Gateway for NetWare 6.5:

• For the NFS Gateway install FAQs, refer to install.txt in the product installation directory.
• To install iManager plug-in, the NFS Gateway web administration utility (nfsgyadmin.npm located at the root of the product), complete the steps given in Downloading and Installing iManager Plug-in section of Novell iManager 2.x Administration Guide (http://www.novell.com/documentation/lg/imanager20/imanager20/data/bnpta1r.html).
• For information on installing, and configuring NFS Gateway for NetWare 6.5, refer to the Setting Up the NFS Gateway in NFS Gateway for NetWare 6.5 Administration Guide at the root directory of the product.
• For NFS Gateway FAQs, refer to NFS Gateway FAQs in NFS Gateway for NetWare 6.5 Administration Guide at the root directory of the product.

4.0 Installing New Version of NFS Gateway iManager snap-in

To successfuly install a new version of NFSGYAdmin.npm (located at the root directory of the product), the NFS Gateway snap-in, over an existing NFS Gateway snap-in, and ensure that all new updates take effect, complete the following:

1. Delete the NFS Gateway snap-in entry from the iManager.

   You can do this by going to Configure > iManager Configuration > Modules, then select the NFSGYAdmin module and click Delete.

2. Install the new version of NFSGYAdmin.npm.

   You can do this by going to Configure > iManager Configuration > Modules, then click Install and select the new NFSGYAdmin.npm.

3. Delete the *.java and *.class files located at the sys:\tomcat\4\work\standalone\localhost\nps\portal\modules\nfsgy\skins\default\devices\default folder.

5.0 Known Issues

This section describes known issues that have not been resolved for this release of NFS Gateway for NetWare 6.5.

5.1 Install

• Install NetWare 6.5 Support Pack 1 before installing NFS Gateway, because the NFS Gateway install does not check for the existence of NetWare 6.5 Support Pack 1 on the server.

5.2 Loading / Mounting

• The NetWare Server hangs if the value for the Largest UDP Packet Size parameter value is less than 4608.
• Do not use the mounted Gateway volumes as the ShadowVolume when you mount another volume (using gymount).

  For example, if vol1 is a mounted NFS Gateway volume, do not execute the following:

  gymount vol2 -shadowvolume vol1 

5.3 Usage

• If the NFS server you are using is slow and is using NFS version 2, then the NFS server might take a while to respond to write requests.

  To improve the response time for NFS writes, use NFS version 3.

• If you move directory entries between symbolic links, where both symbolic links point to the same target directory, you cannot view the contents in both directories. This is because both directories point to the same target directory.

  For example:

  dira directory contains file1 and file2

  lndir1 and lndir2 are symbolic links to dira.

  If you move file1 from lndir1 to lndir2, then you cannot view the contents for file1 in lndir1, lndir2, or dira.

• When a directory is renamed, the symbolic link for that directory continues to display the initial target directory contents.
• Invalid and cyclic symbolic links, such as symbolic link pointing to itself or a symbolic link pointing to another symbolic link which in turn points to the first one, are not supported.
• When you make changes in the gystart.ncf file, the parameters are not taken into effect dynamically.

  They are taken into effect when you click the Refresh button from the iManager User Interface for NFS Gateway or when the next gymount operation is done.

• NFS Gateway uses only sys:\system\gystart.ncf.
• The gyumount -remove command does not remove Novell eDirectory volume object and shadow files.
• During dynamic configuration, if you give an invalid or out of range parameter, then the parameter value changes to its default value. It does not retain the last known valid value.
• Copying files to NFS Gateway volume from Windows* or any other application on NetWare does not preserve the modified time stamp value.

6.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.

Copyright ^© 2004 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, and NetWare are registered trademarks of Novell, Inc. in the United States and other countries.

eDirectory and NCP are trademarks of Novell, Inc.

All third-party products are the property of their respective owners.