You can culster-enable the FTP server in one of the following modes:
In the active/passive cluster mode, NetWare FTP Server runs on only one node in the cluster at a time. For example, if the node where FTP Server is installed fails, NetWare FTP Server starts on other specified nodes in the cluster and the FTP sites on the failed server fail over to other nodes in the cluster.
Cluster-enabling in this mode has the following advantages:
A common user restriction can be maintained across the cluster setup because only a single configuration and restriction file exists in the cluster. The restriction for any eDirectory 8.7.3 user on a particular FTP Server continues even when the FTP service fails over to another node in the cluster.
The FTP system log files for the cluster can be saved at a common location.
A User home directory can be saved in the shared volume path.
FTP Server status can be monitored by using the ftpstat command. This command lets you view session-based details such as bytes sent, bytes received, session duration, files sent, files received, and current Novell eDirectory context.
To configure an active/passive mode:
Stop FTP Services by executing unload nwftpd on every node in the cluster.
Edit autoexec.ncf and comment/remove the ftpstart.ncf entry from every FTP Server in each of the nodes in the cluster. This lets FTP Server to be started by NetWare Cluster Services.
Create an etc directory in the shared volume directory and copy FTP Server configuration file (ftpserv.cfg) and restrictions file (ftprest.txt) to shared_vol_name:/etc.
Edit shared_vol_name:/etc/ftpserv.cfg and make the following changes:
In the RESTRICT_FILE parameter, change the FTP user restrictions file path to shared_vol_name:/etc/ftprest.txt
In the FTPD_LOG parameter, change the FTP daemon log file path to shared_vol_name:/etc.
Bring the resource status to offline and then modify the load and unload scripts:
Using ConsoleOne®, select and right-click the Cluster resource object, then click
and .Add the following at the end of the existing load script:
load nwftpd -c shared_vol_name:\etc\ftpserv.cfg
load ftpstat
The load script specifies the commands to start the resource or service on a server or to mount the volume on a server.
Add the following at the beginning of the unload script:
unload ftpstat
unload nwftpd
The unload script specifies how the application or resource should terminate.
Bring the cluster resource online.
FTP Server is now configured to work in the active/passive clustering mode.
In active/active cluster mode, services of the NetWare FTP Server (nwftpd and ftpstat) run on all nodes in cluster.
For example, when a server fails, the FTP sites on that server have transparent failover to other FTP servers in the cluster. Only FTP sites move.
Cluster-enabling in this mode has the following advantages:
Faster recovery after a failure
Effective load balancing
Ensure that every node in the cluster has the same configuration and restrictions file
Make sure to use the default load/unload scripts
To configure an active/passive mode:
Edit the autoexec.ncf file and uncomment the ftpstart.ncf entry in individual nodes/servers of the cluster that will run NetWare FTP Server.
Bring the resource status to offline and then modify the load/unload scripts.
Using ConsoleOne®, select and right-click the Cluster resource object, then click
and .Add the following at the end of the existing load script:
nwftpd -c shared_vol_name:\etc\ftpserv.cfg
The load script specifies the commands to start the resource or service on a server or to mount the volume on a server.
For every FTP Server instance running, add the following at the beginning of the unload script:
nwftpd -u shared_vol_name:\etc\ftpserv.cfg
Unload script specifies how the application or resource should terminate.
Bring the cluster resource online.
FTP Server is now configured to work in the active/active clustering mode.