The following is added in Section 5.2.4, Other:
When OES2 SP1 AFP iManager plugin tries to manage a OES2 SP2 AFP server, configuration settings like CROSS_PROTOCOL_LOCKS, NO_UNLOAD_TIME_CHECK, NO_COUNT_ON_OFFSPRING cannot be managed as these options are removed from OES2 SP2 AFP Server. Similarly, the new settings GUEST_USER and EXPORT_ALL_VOLUMES added in OES2 SP2 AFP Server cannot be managed by OES2 SP1 AFP iManager plugin.
Specifying alias names for volumes in afpvols.conf file is mandatory in OES2 SP1. However, it is optional in OES2 SP2. Hence when an OES2 SP1 AFP iManager plugin tries to use the volume management feature of an OES2 SP2 AFP Server, it is mandatory to specify the alias name for the volumes.
Section 8.2.1, Volume Name Management in a Cluster is added to Section 8.0, Configuring AFP with Novell Cluster Services for an NSS File System.
Section 12.6, AFP Server Responds Slowly is added to Section 12.0, Troubleshooting AFP.
In Section 5.2.4, Other, Off Spring Count and Cross Protocol information is removed.
Frontfile updated with the release date as November, 2009.
The Load and Unload scripts are revised in Section 8.0, Configuring AFP with Novell Cluster Services for an NSS File System.
Section 12.5.3, zAFPCountByScanDir: scandir failed is added in Section 12.0, Troubleshooting AFP.
Section 3.3, Antivirus Support is added.
Section 5.2.5, Rights to a File or Folder is added in the Section 5.0, Administering the AFP Server.
The following content is included in the Section 4.0, Installing and Setting Up AFP:
The AFP Proxy user:
must be a member of the Universal Password policy.
must be added as a reader of passwords in that policy.
The following is included in the Section 5.0, Administering the AFP Server:
The AFP volume share name supports all ASCII characters except NULL, colon(:), and forward slash(/).
AFP now supports Bonjour. A new screenshot and a writeup is included in the Installing AFP during the OES 2 SP3 Installation in the Installing and Setting Up AFP chapter.
The following note is included in Administering the AFP Server:
NOTE: Admin equivalent/container admin users should be LUM enabled to manage the AFP server through AFP iManager plugin.
and are documented in the Section 5.2.4, Other in the Administering the AFP Server chapter.
An important note is included in the Section 5.3, Configuring Volume Details as follows:
IMPORTANT:Do not edit the afpvols.conf file for a volume that is already mounted and are already in use (mounted on AFP clients). However, if there is a need to modify the file, only restart of the server is recommended. This lets the volumes mounted on clients to have a clean unmount. Using the reload option for modification leads to irrecoverable issues and is recommended to avoid.
The following description is included in the Section 5.3, Configuring Volume Details:
Dynamic Detection of Volumes: AFP server now dynamically detects adding/mounting a new NSS volume and deleting/unmounting an existing NSS volume. The AFP server updates itself with the current set of volumes on the OES 2 SP2 server. An explicit reload of the server is not required.
NOTE:The dynamic detection is applicable to standalone servers as well as cluster nodes.
A note is included in Installing AFP during the OES 2 SP3 Installation section in Section 4.0, Installing and Setting Up AFP as follows:
NOTE:AFP configuration fails when the container admin tries to add the proxy user as reader of passwords to the password policy. Configuration fails as the container admin does not have the write rights to the password policies in the security container. Provide the container admin create rights on the password policy container and rerun the configuration.