Sun Cluster 2.2 Software Installation Guide

Chapter 8 Installing and Configuring Sun Cluster HA for Netscape

This chapter provides instructions for setting up and configuring the Sun Cluster HA for Netscape data services.

This chapter includes the following sections:

Sun Cluster HA for Netscape Overview

The Sun Cluster HA for Netscape data services consist of a group of Netscape^(TM) applications that can be made highly available by running them in the Sun Cluster environment. Table 8-1 displays the data service application and its associated highly available data service.

Table 8-1 Sun Cluster HA for Netscape Data Services


Netscape Application	Highly Available Data Service Name	HA DS Package Name
Netscape News Server	Sun Cluster HA for Netscape News	`SUNWscnew`
Netscape Mail Server and Netscape Messaging Server	Sun Cluster HA for Netscape Mail	`SUNWscnsm`
Netscape HTTP/Web Server	Sun Cluster HA for Netscape HTTP	`SUNWschtt`
Netscape HTTP Secure	Sun Cluster HA for Netscape HTTP	`SUNWschtt`
Netscape LDAP Server	Sun Cluster HA for Netscape LDAP	`SUNWscnsl`

See the Sun Cluster 2.2 Release Notes for a list of the supported release levels for the data services.

The procedures described in this chapter assume that you are familiar with the Sun Cluster concepts of disksets, logical hosts, physical hosts, switchover, takeover, and data services. See Chapter 1, Understanding the Sun Cluster Environment for a description of these concepts.

You should install and test the Netscape application software (DNS, Netscape HTTP Server, Netscape News, Netscape Mail or Messaging Server, and Netscape LDAP) independently of Sun Cluster. Refer to the Netscape application software installation documentation for installation instructions.

Table 8-2 describes the high-level procedures to set up Netscape data service applications to run with Sun Cluster.

Table 8-2 High-Level Steps to Set Up Netscape Data Service Applications


Task	Go To ...
Installing the Solaris and Sun Cluster environments, installing the Netscape data service packages, and installing all required patches	Chapter 3, Installing and Configuring Sun Cluster Software
Starting the cluster with the `scadmin(1M)` command	Chapter 3, Installing and Configuring Sun Cluster Software, and the `scadmin(1M)` man page
(Optional) Installing and setting up DNS for the Netscape data services to use	Chapter 12, Installing and Configuring Sun Cluster HA for DNS
Installing and configuring Sun Cluster HA for Netscape data services	See the section on installing your particular data service, and "Configuring the Sun Cluster HA for Netscape Data Services"
Registering and starting the Sun Cluster HA for Netscape data services	"Configuring the Sun Cluster HA for Netscape Data Services"

Note -

If you are running multiple data services in your Sun Cluster configuration, you can set up the data services in any order, with one exception: if you use Sun Cluster HA for DNS, you must set it up before setting up Sun Cluster HA for NFS. DNS software is included in the Solaris environment. See Chapter 12, Installing and Configuring Sun Cluster HA for DNS, for details. If the cluster is to obtain the DNS service from another server, then configure the cluster to be a DNS client first.

Note -

After installation, do not manually start and stop the Netscape data services. Once started, they are controlled by Sun Cluster.

Note -

Before you install the Netscape application software, refer to the section in this chapter describing the configuration procedures for each Netscape application. These sections describe Sun Cluster-specific configuration information that you must supply when you install the Netscape applications.

Choosing an Install Location for Netscape Binaries

The Netscape binaries and data directories can be installed on either the shared disk or on the local disk of each cluster node.

Installing the binaries and data directories on the shared disk eases administration and consumes less disk space, but increases down time during application upgrades, because the application must be brought down for the duration of the binary upgrade.

Installing the data directories on the shared disk and the binaries locally on each node preserves high availability during failover, and also reduces downtime during future upgrades of the application. You can upgrade the binaries on a node that is not currently hosting the application, switch the application over to that node, then upgrade the binaries on the original node. The application remains available except for during the brief switchover period.

Netscape News

Sun Cluster HA for Netscape News is Netscape News running under the control of Sun Cluster. This section describes how to install Netscape News to enable it to run as the Sun Cluster HA for Netscape News data service. Refer to Netscape documentation for the standard Netscape installation instructions.

There are two prerequisites to installing Netscape News using the ns-setup command.

A user name and a group name must be configured for the news server. Create these names on all Sun Cluster servers that will be running Sun Cluster HA for Netscape News and verify that they have the same ID numbers on all systems.
DNS must be configured and enabled on all servers running Sun Cluster HA for Netscape News. All Sun Cluster servers must have the same /etc/resolv.conf file, and the hosts entry in the /etc/nsswitch.conf file must include dns.

Netscape News requires some variation from the default installation parameters, notably:

Specify the logical host name rather than the physical host name.
Do not use the default server root disk when prompted. Your files must reside on the multihost disk.
Make sure all start and stop scripts are located in the base install directory.

How to Install Netscape News

Before you begin this procedure, complete the appropriate pre-requisite steps listed in Table 8-2.

This procedure shows the user interaction with the ns-setup command. Only the sections that are specific to Sun Cluster HA for Netscape News are shown here. For the other sections, choose or change the default value as appropriate.

All of the steps in this procedure must be performed as root.

Make sure each logical host is served by its default master.

The Netscape application will be installed from the physical host that is the logical host's default master. If necessary, switch over the logical hosts to be served by their respective default masters.

Note -
The logical host names you use in your Sun Cluster configuration should be used as the server names when you install and configure the Netscape application in the following steps. This is necessary for failover of the Netscape server to work properly.

Run the ns-setup command from the Netscape News install directory on the CD.

Change directory to the Netscape News distribution location on the CD, and run the ns-setup command.

phys-hahost1# cd /cdrom/news_server/solaris/news/install
phys-hahost1# ./ns-setup

Note -

The Netscape directory on the CD might be different from that shown in the example. Check your Netscape documentation for the actual location.

After the licensing agreement you see:

Netscape Communications Corporation 
Netscape SuiteSpot Server Installation
---------------------------------------------------------------
This program will extract the server files from the distribution
media and install them into a directory you specify. This 
directory is called the server root and will contain the server 
programs, the Administration Server, and the server configuration 
files.

To accept the default shown in brackets, press return.

Server root [/usr/netscape/suitespot]:

Enter the logical host name for the Netscape News Server and the appropriate DNS domain name.

A full name is of type hostname.domainname, such as hahost1.sun.com. You should not accept the default, and you can enter any directory name you might have created for the data service here as well.

Note -
You must use the logical host name rather than the physical host name here and everywhere else you are asked, for Sun Cluster HA for Netscape News to fail over correctly.

For example:
Machine's name [phys-hahost1]: hahost1
Follow the screen instructions (in many cases you may want to accept the default choices) for the server installation.

Enter the Server Administrator ID and password when asked.

Follow the guidelines for your system.

Note -
The default administration port is not the port on which the data services will listen, so it is an acceptable default. Make note of the default administration port number for future use.

When you see the following, your installation is complete and ready for configuration:
Your parameters are now entered into the Administration Server configuration files, and the Administration Server will be started. Writing configuration files ...

Bring up the Netscape browser.
Web browser [netscape]:
You should see the Netscape browser.

Enter the URL of the logical host where the server is installed.

F
logicalhostname:admin_port_#
or example:

Enter the proper user ID and password when prompted. You see the page with the logical host name you assigned and the Administration port number.

Click the Create selection for the Netscape product and version you want to install.

Click OK from the bottom of the following page.

You see the Success page with the name of the new server and associated port number.

If the service is not yet registered, use the hareg(1M) command to register it.

To register the service only on the logical host, include the -h option and logical host name:
# hareg -s -r nsnews [-h logicalhost]

Run the hadsconfig command from the physical host:
phys-hahost1: hadsconfig

Enter the number for the nsnews menu item at the prompt.

Your choices may vary depending on the services installed.

Enter the number for the Create a new instance item at the prompt.

You see something similar to the following:

Name of the instance [?] :
Logical host [?] :
Base directory of product installation [?] :
Server Port Number [?] :
Time between probes (sec) [60]  [?] :
Time out value for the probe (sec) [60]  [?] :
Take over flag [y]  [?] :

Enter the name for the instance.

Enter your logical hostname.

Enter the location to the logical host where the service is installed for the Base directory location.

This is the location of the start and stop scripts. For example, /netscape-1/vol01/nsnews/hahost1. Your path may differ.

Enter the server port number on which you want the server to listen.

For example, 119 for News.

Either accept the defaults or change them by entering the appropriate information.

You can change the defaults now if necessary. After you finish, a confirmation appears.

Add this instance.

You see instance added to workfile.

Enter the menu item number to go to the Main Menu.

You see Configuration has changed in workfile.

Update the configuration from the workfile.

Enter the appropriate information when you see the checking node status... message.

Enter the Quit menu item number.

You are returned to the root prompt of your physical host.

Activate the service by using the hareg(1M) command.

Run the hareg(1M) command on only one host.
# hareg -y nsnews

Confirm your News server operation by making a telnet connection to the logical host on which the service is listening.

For example:
# telnet logicalhost 119
After you have confirmed the server's operation, your installation is complete.

Netscape Web or HTTP Server

Sun Cluster HA for Netscape HTTP is a Netscape Web or HTTP Server running under the control of Sun Cluster. This section describes the steps to take when installing the Netscape Web or HTTP Server (by using the ns-setup command) to enable it to run as the Sun Cluster HA for Netscape HTTP data service.

You can install any of a number of Netscape web server products. Refer to Netscape documentation for standard installation instructions.

Note -

If you will be running the Sun Cluster HA for Netscape HTTP service and an HTTP server for Sun Cluster Manager (SCM), configure the HTTP servers to listen on different ports. Otherwise, there will be a port conflict between the two servers. Do not assign port numbers that are already reserved by Sun Cluster or Solaris. See "Default Port Numbers Reserved by Sun Cluster" for details.

Note -

You must follow certain conventions when you configure URL mappings for the web server. For example, when setting the CGI directory, to preserve availability you must locate the mapped directories on the multihost disks associated with the logical host serving HTTP requests for this mapping. In this example, you would map your CGI directory to /logicalhost/commerce/ns-home/cgi-bin. In situations where the CGI programs access "back-end" data, make sure the data also is located on the multihost disks associated with the logical host serving the HTTP requests. In situations where the CGI programs access "back-end" servers such as an RDBMS, make sure that the "back-end" server also is controlled by Sun Cluster. If the server is an RDBMS supported by Sun Cluster, use one of the highly available RDBMS packages. If not, you can put the server under Sun Cluster control using the APIs documented in the Sun Cluster 2.2 API Developer's Guide.

Netscape Web or HTTP server requires some variation from the default installation parameters, notably:

Specifying the logical host name rather than the physical host name
Do not use the default server root disk when prompted, your files must reside on the multihost disk
When supplying the base install directory pathname, this should be the location of the start and stop scripts

How to Install Netscape Web or HTTP Server

Before you begin this procedure, complete the appropriate pre-requisite steps listed in Table 8-2.

This procedure shows the user interaction with the ns-setup command. Only the sections that are specific to Sun Cluster HA for Netscape HTTP are shown here. For the other sections, choose or change the default value as appropriate.

All of the steps in this procedure must be performed as root.

Make sure each logical host is served by its default master.

The Netscape application will be installed from the physical host that is the logical host's default master. If necessary, switch over the logical hosts to be served by their respective default masters.

Note -
The logical host names you use in your Sun Cluster configuration should be used as the server names when you install and configure the Netscape application in the following steps. This is necessary for failover of the Netscape server to work properly.

On one node only, run the ns-setup command from the Netscape Commerce install directory on the CD.

phys-hahost1# cd /cdrom/commerce/solaris/us/https/install
phys-hahost1# ./ns-setup

Note -

The Netscape directory on the CD might be different from that shown in the example. Check your Netscape documentation for the actual location.

After the licensing agreement you see:

Netscape Communications Corporation 
Netscape SuiteSpot Server Installation
---------------------------------------------------------------
This program will extract the server files from the distribution
media and install them into a directory you specify. This 
directory is called the server root and will contain the server 
programs, the Administration Server, and the server configuration 
files.

Server root [/usr/netscape/suitespot]:
To accept the default in brackets, press return.

Enter the logical host name for the Netscape Web Server and the appropriate DNS domain name.

A full name is of type hostname.domainname, such as hahost1.sun.com. You can enter any directory name you might have created for the data service here as well.

Note -
You must use the logical host name rather than the physical host name here and everywhere else you are asked, for Sun Cluster HA for Netscape HTTP to fail over correctly.

For example:
Machine's name [phys-hahost1]: hahost1
Follow the screen instructions (in most cases you may want to accept the default choices) for the server installation.

Enter the Server Administrator ID and password when asked.

Follow the guidelines for your system.

Note -
The default administration port is not the port on which the data services will listen, so it is an acceptable default. You will however, want to make note of the port number for future use.

When the following message appears, your installation is ready for configuration:
Your parameters are now entered into the Administration Server configuration files, and the Administration Server will be started. Writing configuration files ...

Bring up the Netscape browser.
Web browser [netscape]:
The Netscape browser appears.

Enter the URL of the logical host where the server is installed. For example:
logicalhostname:admin_port_#

Enter the proper user ID and password when prompted.

You see the page with the logical host name you assigned and the Administration port number.

Click the Create selection for the Netscape product and version you want to install.

Click OK from the bottom of the following page.

You see the Success page with the name of the new server and associated port number.

This step creates a directory https-hostname in the server root you specified in Step 2. For example, if the server root you specified is /netscape-1/vol01/nshttps and the name of the server you created is hahost1, then the directory created is /netscape-1/vol01/nshttps/https-hahost1.

(For Netscape HTTP Secure 4.0 only) In the directory created in Step 9, create a file called keyPass.

This file should contain the Server Administrator password. This allows the HA data service to run the server with encryption turned on. For more details about how to configure the server to run with encryption on or off, refer to your Netscape Enterprise Server documentation.

Note -
(Netscape HTTP 4.0 only) The certificates necessary for the Enterprise Server to run in encrypted mode must be created for each of the physical hosts on which the server can potentially run. This is different from Netscape HTTP versions 3.6 and earlier, in which only one certificate (independent of the physical servers) had to be installed. This change is imposed by the Enterprise certificate management model for Enterprise OS version 4.

If the service is not yet registered, use the hareg(1M) command to register it.

To register the service only on the logical host, include the -h option and logical host name:
# hareg -s -r nshttp [-h logicalhost]

Run the hadsconfig command from the physical host:
phys-hahost1# hadsconfig

Enter the number for the nshttp menu item at the prompt.

Your choices vary depending on the services installed.

Enter the number for the Create a new instance item at the prompt.

Name of the instance [?]
Logical host [?]
Base directory of product installation [?] 
Server Port Number [?]
Time between probes (sec) [60]  [?]
Time out value for the probe (sec) [60]  [?]
Take over flag [y]  [?]

Enter a name for the instance.

Enter your logical hostname.

Enter the location to your logical host for the Base directory location.

This is the location of the start and stop scripts. For example, /netscape-1/vol01/nshttps/https-hahost1. You may have created other directories between the logical host and service directories.

Enter the server port number on which you want the server to listen.

Either accept or change the defaults here by entering the appropriate information.

You can change the defaults now, if necessary. After you finish, a confirmation appears.

Add this instance.

You see instance added to workfile.

Enter the menu item number to go to the Main Menu.

You see Configuration has changed in workfile.

Update the configuration from the workfile.

Enter the appropriate information when you see the checking node status... message.

Enter the Quit menu item number.

Return to the root prompt of your physical host.

Register and activate the service by using the hareg(1M) command.

Run the hareg(1M) command on only one host.
# hareg -y nshttp

Confirm your HTTP server operation by making a telnet connection to your logical host where the service is listening.

For example:
# telnet logicalhost port#
After you have confirmed the server's operation, your installation is complete.

Netscape Mail

Sun Cluster HA for Netscape Mail can be used with Netscape Mail or with Netscape Messaging Server. This section describes the steps to take when installing Netscape Mail to enable it to run as the Sun Cluster HA for Netscape Mail data service. If you are using Netscape Messaging Server, see "Netscape Messaging Server".

The Sun Cluster HA for Netscape Mail data service is an asymmetric data service. Only one logical host in the cluster provides the mail services.

Note -

The Sun Cluster HA for Netscape Mail service fault probing might cause /var/log/syslog to fill up quickly. To avoid this, disable logging of mail.debug messages in the /etc/syslog.conf file by commenting out the mail.debug entry and sending a HUP signal to the syslogd(1M) daemon.

The following are required on the Sun Cluster servers before configuring Sun Cluster HA for Netscape Mail:

Each server must have a unique user ID and unique group ID that contains only this unique user ID. These particular IDs will be used by the mail system. The names and numbers must be identical on all servers running Sun Cluster HA for Netscape Mail.
DNS must be configured and enabled on all servers running Sun Cluster HA for Netscape Mail. All Sun Cluster servers must have the same /etc/resolv.conf file, and the hosts entry in the /etc/nsswitch.conf file must include dns.

Because Netscape Mail is installed on one server, Sun Cluster HA for Netscape Mail requires some variation from the default installation parameters, notably:

Specifying the logical host name rather than the physical host name
Installing the Netscape Mail software and spool directories on the multihost disks
Do not use the default server root disk when prompted, your files must reside on the multihost disk
When supplying the base install directory pathname, this should be the location of the start and stop scripts

How to Install Netscape Mail

Before you begin this procedure, complete the appropriate pre-requisite steps listed in Table 8-2.

This procedure shows the user interaction with the ns-setup command and Sun Cluster commands. Only the sections that are specific to Sun Cluster HA for Netscape Mail are shown here. For the other sections, choose or change the default value as appropriate.

All of the steps in this procedure must be performed as root.

Make sure each logical host is served by its default master.

The Netscape application will be installed from the physical host that is the logical host's default master. If necessary, switch over the logical hosts to be served by their respective default masters.

Note -
The logical host names you use in your Sun Cluster configuration should be used as the server names when you install and configure the Netscape application in the following steps. This is necessary for failover of the Netscape server to work properly.

Run the ns-setup command from the Netscape Mail install directory on the CD.

Change directory to the Netscape Mail distribution location on the CD, and run the ns-setup command:

phys-hahost1# cd /cdrom/commerce/solaris/us/https/mail
phys-hahost1# ./ns-setup

Note -

The Netscape directory on the CD might be different from that shown in the example. Check your Netscape documentation for the actual location.

After the licensing agreement you should see something like the following:

Netscape Communications Corporation 
Netscape SuiteSpot Server Installation
---------------------------------------------------------------
This program will extract the server files from the distribution
media and install them into a directory you specify. This 
directory is called the server root and will contain the server 
programs, the Administration Server, and the server configuration 
files.

Server root [/usr/netscape/suitespot]:
To accept the default in brackets, press return.

Enter the logical host name for the Netscape Web Server and the appropriate DNS domain name.

A full name is of type hostname.domainname, such as hahost1.sun.com. You can enter any directory name you might have created for the data service here as well.

Note -
You must use the logical host name rather than the physical host name here and everywhere else you are asked, for Sun Cluster HA for Netscape Mail to fail over correctly.

For example:
Machine's name [phys-hahost1]: hahost1
Follow the screen instructions (in many cases you may want to accept the default choices) for the server installation.

Enter Server Administrator ID and password when asked.

Follow the guidelines for your system.

Note -
The default administration port is not the port on which the data services will listen, so it is an acceptable default.

You see information similar to the following:
Attempting to start Netscape Admin Server...
Continue with the installation when prompted.

Specify user, group, and domain names.

Enter the user name you configured for the mail server on all Sun Cluster servers running Sun Cluster HA for Netscape Mail.

Specify directories for system components.

You are asked the names of directories where the various components of the system will be installed. Enter a location on the logical host, for example, /hahost1/mail/mailbox, and /hahost1/mail/postoffice.

Specify a Server Identifier name.

Specify whether to use the NIS module and the Greeting Forms feature.

You see a confirmation of the information you specified as in the following example:

Mail user name: 
Domain name: 
Mailbox directory: 
Post Office directory: 
Server Identifier: 
NIS lookups: 
Greeting forms: 

You may accept these choices or quit the installation.

Install Netscape Messaging Server? [y]:

Install the Netscape Messaging Server and reply to queries when prompted.

Depending on how you set up your configuration, specify items appropriately. After all changes take effect, you see:
Netscape Messaging Server installation complete

Start the Netscape Messaging Server when prompted.

If the service is not yet registered, use the hareg(1M) command to register it.

To register the service only on the logical host, include the -h option and logical host name:
# hareg -s -r nsmail [-h logicalhost]

Run the hadsconfig command from the physical host:
[phys-hahost1]: hadsconfig

Enter the number for the nsmail menu item at the prompt.

Your choices may vary depending on the services installed.

Enter the number for the Create a new instance item at the prompt.

Name of the instance [nsmail]  [?]
Logical host [?] 
Take over flag [y]

Following are the specifications of this instance
Name of the instance : 
Logical host : 
Number of times to retry : 
Time between retries (sec) : 
Configuration File : 
Fault probe program : 
Time between probes (sec) : 
Time out value for the probe (sec) : 
Take over flag : 
Add this instance ?  (yes/no) [yes] 
Instance added to workfile
Press enter to return to main menu

Enter the name for the instance.

Enter your logical hostname.

Either accept or change the defaults for the remaining items depending on your configuration.

You can change these defaults now if necessary.

Add this instance.

You see Instance added to workfile.

Go to the Main Menu when prompted.

You see Configuration has changed in workfile.

Update the configuration from the workfile when prompted.

Enter the Quit menu item number.

Return to the root prompt of your physical host.

Register and activate the service by using the hareg(1M) command.

Run the hareg(1M) command on only one host.
# hareg -y nsmail

This completes the installation of Netscape Mail.

Netscape Messaging Server

Sun Cluster HA for Netscape Mail can be used with Netscape Messaging Server or with Netscape Mail. This section describes the steps to take when installing Netscape Messaging Server to enable it to run as the Sun Cluster HA for Netscape Mail data service. If you are using Netscape Mail, see "Netscape Mail".

The Sun Cluster HA for Netscape Mail data service is an asymmetric data service. Only one logical host in the cluster provides mail services.

Note -

Netscape Messaging Server Concepts and Features

Netscape Messaging Server introduces new concepts and features different from those included in Netscape Mail. The following sections describe these concepts and features, as well as the Netscape Messaging Server installation and configuration procedures.

Server Root Concept

Netscape Messaging Server introduces the concept of a server root, a directory which contains a complete installation of Netscape Messaging Server and configured instances for the installation, with one minor exception: the /etc/nsserver.cfg file resides outside of the server root and contains a list of all server roots on a node. Note, however, that Sun Cluster 2.2 allows only one Netscape Messaging Server instance per server root, and only one server root per logical host--hence, one instance per logical host.

Dependence on a Configuration Directory Server

At time of installation, Netscape Messaging Server requires that a configuration directory server be available to it, because during the installation, Netscape Messaging Server contacts the configuration directory server and populates it with configuration information. After initial installation, Netscape Messaging Server copies the configuration data back to its local cache, after which the external configuration directory server is no longer strictly relied upon. If the configuration directory server becomes unavailable, Netscape Messaging Server will emit warning messages stating that it is starting up with configuration data from its own local cache. These messages are expected and harmless.

If you choose to install the Netscape Directory Server to serve Netscape Messaging Server, you can make Netscape Directory Server highly available by also installing and configuring Sun Cluster HA for Netscape LDAP. For more information about Sun Cluster HA for Netscape LDAP, see "Netscape Directory Server (LDAP)".

Fault Monitoring Behavior

Netscape Messaging Server includes five separate daemons: smtpd, popd, imapd, mshttpd, and stored. These daemons can be stopped and started individually, and can fail individually.

Sun Cluster HA for Netscape fault monitoring checks that daemon processes exist and that protocol services are available. During process existing checking, the fault probe periodically verifies that a daemon exists. The fault probe interprets any daemon absence as an application failure, and takes action based on the current configuration parameters. During protocol probing, the fault probe periodically checks the daemon and takes action only in response to error codes indicating a timeout. The default timeout value set by Sun Cluster HA for Netscape is 660 seconds, to prevent inadvertent failovers in situations where a server is simply slow to respond.

Because this fault monitoring model relies on a fully active mail server, you must always turn off the Sun Cluster HA for Netscape data service (using hareg -n) before you perform any administrative tasks that require a daemon to stop. Otherwise the fault probe will take action. Turn on the data service (using hareg -y) only after completing the administrative task.

Sun Cluster HA for Netscape monitors the smtpd, popd, and imapd daemons with both process existence checking (using the local probe) and protocol probing (using both local and remote probes). Sun Cluster HA for Netscape monitors the mshttpd and stored daemons with only process existence checking (using the local probe). The mshttpd and stored daemons are never checked by a remote probe. Therefore, if an mshttpd process exists but is stalled, Sun Cluster HA for Netscape will take no action; once you notice that web mail clients are unable to connect, you must restart the mshttpd process manually.

Sun Cluster HA for Netscape does not monitor any SNMP subagents.

Use of User/Group Directory

Netscape Messaging Server requires use of a user/group directory, which was optional with Netscape Mail 3.5. The user/group directory is an LDAP directory used by the messaging server to process email. You can install and start the messaging server before configuring the user/group directory, but the messaging server depends upon access to the user/group directory after installation. Because of this dependency, the directory server that services the user/group directory should be installed on the multihost disk or on another clustered server, so as to be highly available.

The configuration directory and user/group directory can be serviced by the same directory server instance or by different instances.

Netscape Messaging Server Configuration Restrictions

The following dependencies and restrictions apply to Netscape Messaging Server on Sun Cluster 2.2.

When you install Netscape Messaging Server, the listener daemons popd, smtpd, imapd, mshttpd, and stored must be configured as active, and must be configured on their default ports. If not, the startup and fault monitoring programs will perceive the daemons as inactive, and will take action based on the current configuration parameters. Further, if these two conditions are not met, the Netscape Messaging Server instance will not start successfully. See "Fault Monitoring Behavior" for more information.
You can configure only one Netscape Messaging Server instance per server root, and only one server root per logical host--hence, one Netscape Messaging Server instance per logical host.
The Netscape Messaging Server Multiplexor feature is not supported with Sun Cluster 2.2. Because the Multiplexor requires services located outside the server root, the Multiplexor cannot be probed or failed over by Sun Cluster HA for Netscape.
Though Netscape Messaging Server supports SSL-enabled listening for some of its protocols, the separate ports using SSL are not fault probed by Sun Cluster HA for Netscape. Basic restart and failover is supported, however, for any Netscape Messaging Server instances listening on SSL-enabled ports.
Netscape Messaging Server supports SMTP plug-ins--shared libraries that you can install and configure to be used by Netscape Messaging Server for customized SMTP processing. If you configure Netscape Messaging Server to use SMTP plug-ins, then be sure to protect the shared libraries with Sun Cluster. Do this by placing the libraries on the shared disk, preferably within the Netscape Messaging Server server root tree, or by placing the libraries on local disks on each potential master node.
Netscape Messaging Server supports sophisticated access control on a service-by-service basis for its TCP-based services (IMAP, POP, HTTP, and SMTP). You can enable this feature by creating filters to screen access to servers. However, if you create filters, do so with care so that you do not prevent root on any potential master from connecting to any of the Netscape Messaging Server protocol servers. If root is prevented from connecting to any of the protocol servers, the data service probe that tests protocol service availability will fail, triggering Sun Cluster HA for Netscape to take action based on the current configuration parameters. This behavior will continue indefinitely until the filter in question is removed or the probe terminated. Make sure that root access is enabled from all nodes that are potential masters of the protocol servers.

Installing Netscape Messaging Server

Use the following procedure to install Netscape Messaging Server with Sun Cluster.

Install Netscape Messaging Server on only one cluster node. You will install all components into one server root residing on the shared disk (see "Server Root Concept"). This server root automatically becomes available to other nodes as necessary, in case of failover or switchover.

Cluster-specific guidelines are included where applicable. You must have root privileges to perform the installation.

How to Install Netscape Messaging Server

In the examples throughout this procedure, the logical host name is hahost1, the Netscape Messaging Server instance name is nms, and the LDAP instance name is ldap.

Configure a user account on the cluster.

Perform the following command from the cluster console. Choose any name for the user account. The default is mailsrv.
# useradd -c nms_userid -d /export/mailsrv -g nobody -m mailsrv

Install Netscape Messaging Server using the scinstall(1M) command.

See Chapter 3, Installing and Configuring Sun Cluster Software for details about using scinstall(1M).
# scinstall

From only one cluster node, start the Netscape Messaging Server setup script from the install directory.

# ./setup
...
Welcome to the Netscape Server Family installation program
This program will install Netscape Server products and the
Netscape Console on your computer.
It is recommended that you have "root" privilege to install the
software.
 
During the installation:
 - Press "Return" to choose the default and go to the next screen
 - Type "Control-B" to go back to the previous screen
 - Type "Control-C" to cancel the installation program
 - Enter comma-separated list of numbers, e.g. 1, 2, 3, for selection of multiple items.
 
Would you like to continue with setup? [Yes]: Y
BY INSTALLING THIS SOFTWARE YOU ARE CONSENTING TO BE BOUND BY 
AND ARE BECOMING A PARTY TO THE AGREEMENT FOUND IN THE LICENCE.TXT
FILE. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS AGREEMENT,
PLEASE DO NOT INSTALL OR USE THIS SOFTWARE
Do you agree to the license terms? [No]: Y

Choose to install the Netscape Servers.

The Netscape Servers are required. The Netscape Console is optional.

Please select what you would like to install:
 1. Netscape Servers
	Install Netscape Servers and the integrated Netscape 	

	Console onto your computer.
 2. Netscape Console
	This will install the Netscape Console as a stand-alone

	Java application on your desktop or laptop.
To accept the default shown in brackets, press the Return key.
 Please select the component you want to install [1]: 1

Select Custom installation.

Please select the installation type for this installation:
 1. Express installation
		Allow you to quickly install the servers using the most.
 	common options and pre-defined defaults. Useful for quick
	evaluation of the products.
 
 2. Typical installation
	Allow you to specify common defaults and options.
 3. Custom installation
	Allow you to specify more advanced options. This is only
	recommended for experienced server administrators.
 
To accept the default shown in brackets, press the Return key.
Choose your installation type [2]: 3

Specify an install directory on the logical host.

Do not accept the default. Specify a location on the logical host.

This program will extract the server files from the distribution
media and install them into a directory you specify. This directory
is called the server root and will contain the server programs, the
Administration Server, and the server configuration files.
To accept the default shown in brackets, press the Return key.


Server root [/usr/netscape/server4]: /hahost1/nsm

Select the Netscape Server Family components.

The Netscape Server Family Core Components, Netscape Administration Services, and Netscape Messaging Suite are required. See your Netscape documentation for more information about these features.

Caution -

The Netscape Directory Suite components are optional, but you must have a directory server available for the configuration directory if you do not plan to install Netscape Directory Suite now. Step 14 requires specification of a directory server instance for the configuration directory. See "Dependence on a Configuration Directory Server" for more information.

Netscape Server Family components:
Components with a number in () contain additional subcomponents
which you can select using subsequent screens.
 
	1. Netscape Server Family Core Components (3)
	2. Netscape Directory Suite (2)
	3. Administration Services (2)
	4. Netscape Messaging Suite (3)
 
Specify the components you wish to install [All]: 1, 3, 4

Select the Netscape Server Family Core Components you want to install.

See your Netscape documentation for more information about these features.

Netscape Server 	Family Core Components components:
 
Components with 	a number in () contain additional subcomponents
which you can select using subsequent screens.
 
	1. Netscape	 Server Family Core Components
	2. Netscape	 Core Java classes
	3. Java Runtime Environment
Specify 	the components you wish 	to install [1, 2, 3]: 1

Select the Directory Suite components you want to install.

See your Netscape documentation for more information about these features.

Netscape Directory Suite components:
Components with a number in () contain additional subcomponents
which you can select using subsequent screens.
 
	1. Netscape Directory Server
	2. Netscape Directory Server Console
 
Specify the components you wish to install [1, 2]:

Select the Administration Services components you want to install.

See your Netscape documentation for more information about these features.

Administration Services components:
Components with a number in () contain additional subcomponents
which you can select using subsequent screens.
 
	1. Netscape       Administration Server
	2. Netscape       Console
 
Specify the components you wish to install [1, 2]:

Select the Netscape Messaging Suite components you want to install.

Netscape Messaging Server is required. Multiplexor and Mailstone Tools are optional. See your Netscape documentation for more information about these features.

Netscape Messaging Suite components:


Components with	 a number in () contain additional subcomponents
which you can select using subsequent screens.
 
	1. Netscape	 Messaging Server
	2. Netscape	 Messaging Multiplexor
	3. Netscape	 Messaging Server Mailstone Tools
 
Specify	 the components you wish	 to install [1]: 1

Specify the logical host name and domain name of the node.

Specify the fully qualified name of the logical host.

Enter the fully qualified domain name of your machine. A fully 
qualified domain name is of the type <hostname>.<domainname>
(e.g. foobar.widget.com).
 
To accept the default shown in brackets, press the Return key.
 
Machine's name [ ]: hahost1.eng.sun.com

Create UNIX users and groups.

Specify your preferences. No cluster-specific requirements exist for this step.

Choose a UNIX user and group to run individual Netscape
server as. It is recommended that this user should have no
privileges in the rest of the system. The Administration
Server will give this group some permissions in the server root
to perform server-specific operations.
You should create this user and group using your native UNIX
system utilities if they do not already exist.
 
Example for this user:   nobody or nsuser or your choice...
Example for this group: nobody or nsgroup or your choice...
 
To accept the default shown in brackets, press the Return key.
 
System User [nobody]:
System Group [nobody]:

If you did not specify a configuration directory server in Step 2, install the Netscape Configuration Directory Server now.

See "Dependence on a Configuration Directory Server" for more information.

Netscape server information is stored in the Netscape 
configuration directory server, which you may have already set up. 
If so, you should configure this server to be managed by the 
configuration server. To do so, the following information about 
the configuration server is required: the fully qualified host name 
of the form <hostname>.<domainname>(e.g. hostname.domain.com), the 
port number, the suffix, and the DN and password of a user having 
permission to write the configuration information, usually the 
Netscape configuration directory administrator.
 
If you want to install this software as a standalone server, or if 
you want this instance to serve as your Netscape configuration 
directory server, press Enter.
 
Do you want to register this software with an existing
Netscape configuration directory server? [No]:

Specify the directory server you will use to store data.

This screen appears only if you are installing Netscape Directory Server (that is, if your selection includes item 2, Netscape Directory Suite, in Step 7). If you answer no, the user/group directory is placed on the directory server you are installing now. If you answer yes, a series of screens will prompt you for more information about an alternate directory.

If you already have a directory server you want to use to store 
your data, such as user and group information, answer Yes to the 
following question. You will be prompted for the host, port, 
suffix, and bind DN to use for that directory server.
 
If you want this directory server to store your data, answer No.
 
Do you want to use another directory to store your data? [No]:

Specify the listener port.

Specify the same port used as the LDAP listener port.

The directory server usually listens to network port 389. You may
accept this as the default by pressing Enter. If you want the
directory server to listen to a different port, enter the port 
number and press Enter. Only the superuser may use port numbers 
less than 1024.
 
Directory server network port [389]:

Specify the unique identifier for this directory server instance.

Each instance of a directory server requires a unique identifier.
Press Enter to accept the default, or type in another name and 
press Enter.
 
Directory server identifier [phys-hahost1]: ldap-hahost1

Specify an administrator ID.

Please enter the administrator ID for the Netscape configuration
directory server. This is the ID typically used to log in to the
console. You will also be prompted for the password.
Netscape configuration directory server admin ID [admin]: 
root Password:
Password (again):

Specify the suffix (the root of your directory tree).

The suffix is the root of your directory tree. You may have more 
than one suffix.
 
Suffix [o=sun.com]:

Specify the administrative user.

Certain directory server operations require an administrative 
user. This user is referred to as the Directory Manager and 
typically has a bind Distinguished Name (DN) of cn=Directory 
Manager. Press Enter to accept the default value, or enter another 
DN. In either case, you will be prompted for the password for this 
user. The password must be at least 8 characters long.
 
Directory Manager DN [cn=Directory Manager]:
 
Password:
Password (again):

Specify the Administrative Domain name, if you are using this feature.

The Administration Domain is a part of the configuration directory
server used to store information about Netscape software. If you 
are managing multiple software releases at the same time, or 
managing information about multiple domains, you may use the 
Administration Domain to keep them separate.
 
If you are not using administrative domains, press Enter to select 
the default. Otherwise, enter some descriptive, unique name for 
the administration domain, such as the name of the organization 
responsible for managing the domain.
 
Administration Domain [sun.com]:

Configure replication on this directory server.

Replication is used to duplicate all or part of a directory server 
to another directory server. This can be used for failsafe 
purposes, to ensure that the directory data is always online and 
up-to-date in case one server goes down. It is also useful for 
distributing directory data from a central main repository to 
remote directory servers.
 
Do you want to configure this directory server to use replication? [No]:

Install sample entries.

You may install some sample entries in this directory instance. 
These entries will be installed in a separate suffix and will not 
interfere with the normal operation of the directory server.
 
Do you want to install the sample entries? [No]:

Populate the directory instance with data.

You may wish to populate your new directory instance with some 
data. You may already have a file in LDIF format to use or some 
suggested entries can be added. If you want to import entries from 
an LDIF file, you may type in the full path and filename at the 
prompt. If you want the install program to add the suggested 
entries, type the word suggest at the prompt. The suggested entries 
are common container entries under your specified suffix, such as 
ou=People and ou=Groups, which are commonly used to hold the 
entries for the persons and groups in your organization. If you do 
not want to add any of these entries, type the word none at the 
prompt.
 
Type the full path and filename, the word suggest, or the word none [suggest]:

Enable or disable schema checking.

If you are going to import an old database immediately after or 
during installation, and you think you may have problems with your 
old schema, you may want to turn off schema checking until after 
the import. If you choose to do this, schema checking will remain 
off until you manually turn it back on. Netscape recommends that 
you turn it back on as soon as possible.
 
Do you want to disable schema checking? [No]:

Specify a port number for the Administration Server.

Choose any free port.

The Administration Server is separate from any of your application
servers since it listens to a different port and access to it is 
restricted.
 
Pick a port number between 1024 and 65535 to run your 
Administration Server on. You should NOT use a port number which 
you plan to run an application server on, rather, select a number 
which you will remember and which will not be used for anything 
else.
 
The default in brackets was randomly selected from the available
ports on your system. To accept the default, press return.
 
Administration port [15956]:

Configure an IP address for the Administration Server.

If you want to configure the Administration Server to bind to a 
specific IP address rather than the default IP address of the 
current host, enter the address below.
To accept the default shown in brackets, press the Return key.
 
IP address:

Specify root as the Server Administrator ID.

Server administration is restricted to people who know the Server
Administrator user ID and password, and to people who access the
server from a host you specify.
 
When you access the Administration Server, it will prompt you for 
the Server Administrator user ID and password. Please select a user 
ID and password.
 
Server Administrator ID [admin]: root

Specify a user for the Administration Server.

The Administration Server program runs as a certain user on your 
system. This user should be different than the one which your 
application servers run as. Only the user you select will be able 
to write to your configuration files. If you run the Administration 
Server as "root", you will be able to use the Server Administration 
screen to start and stop your application servers.
 
Run Administration Server as [root]:

Create a new server instance.

This installer allows you to create a new server instance now. You
will need to have the following information handy, in order to 
create a server instance.
 
			1. Unix user account for the server to run as
			2. User account to be notified of messages sent to 

				'postmaster'
 
Do you wish to create a new server instance at this time? [yes]: yes

Specify a default domain for the Messaging Server.

The Messaging Server needs a default domain. This information is 
used by the server when performing functions like routing and 
serving messaging clients.
 
Enter the default domain you wish Messaging Server to use 
[sunsoft.eng.sun.com]: sun.com

Specify the fully qualified logical host name as the default host.

The Messaging Server needs a default host name. This information 
is used by the server when performing functions like routing and 
serving messaging clients.
 
Enter the host name you wish Messaging Server to 

use [hahost1.eng.sun.com]: <return>

Specify a name for this instance of the Messaging Server.

The Messaging Server needs a server ID in the current server root. 
You will refer to the server instance you are creating using this 
server ID. The server administration utilities and configuration 
information depend on this information.
 
Enter the server ID you wish Messaging Server to 

use [msg-phys-hahost1]: nms-hahost1

Specify the Messaging Server user that you created in Step 2.

The Messaging Server runs as a non-privileged user. This account 
must exist on this system. It is recommended that this user be a 
member of the Netscape server group you defined earlier in this 
installation (i.e. nobody).
 
Enter the user you wish Messaging Server to run as [mailsrv]:

Specify the postmaster account, LDAP distinguished name, and email address.

See your Netscape Messaging Server documentation for guidelines about the postmaster account.

The Messaging Server needs a postmaster account for the Users/
Groups Directory Server that you are using.
 
 ldap://hahost1.domain.sun.com:389/o=sun.com
 
The installer will create a postmaster account now. Error and 
informational messages will be sent by the Messaging Server to this 
account.
 
Press any key to continue: <return>
...
Enter the postmaster's DN [cn=postmaster, o=sun.com]: <return>
...
Enter the postmaster's e-mail address: 
postmaster@hahost1.domain.sun.com

Accept the default ports for SMTP, IMAP, POP3, and Webmail.

The Messaging Server needs a port number for the SMTP daemon to 
listen to. The standard network port is 25. However, you can choose 
other ports.
Enter the SMTP port you wish Messaging Server to use [25]:<return>

...
Enter the IMAP port you wish Messaging Server to use [143]:<return>
...
Enter the POP3 port you wish Messaging Server to use [110]:<return>
...


Enter the Webmail port you wish Messaging Server to use [80]: <return>

Specify a directory for mail queuing.

The Messaging Server needs a directory where mail is queued before 
it is delivered to individual mailboxes or other servers. This 
directory should be secure enough to prevent undesirable 
eavesdropping or tampering.
Enter the queue directory you wish the Messaging Server to 

use [/hahost1/nms/msg-nms/queue]:

Specify a directory for creation of mailboxes.

The Messaging Server needs a directory where mailboxes are created 
for user accounts and e-mail messages are stored. This directory 
should be secure enough to prevent undesirable eavesdropping or 
tampering and large enough to hold the e-mail messages of all the 
user accounts you intend to create on this server.
 
Enter the store directory you wish the Messaging Server to 

use [/hahost1/nms/msg-nms-hahost1/store/partition/primary]:

Create a Webmail end user administration account.

The Messaging Server requires a Webmail end user administration 
account. This account will exist in the Users/Groups Directory 
Server and must have privileges to manage the Webmail preferences 
of any user. Enter the name and password of the end user 
administrator.
 
NOTE: If this account doesn't exist, it will be created and the 
required privileges will be given to the account.
 
Webmail end user admin's uid: [webmail]:
 
Password:
Password (again):

Specify which server instances should start after installation.

The server instances the installer will create are listed below. 
Choose the server instances you wish to start after the 
installation. Enter 'none' if you want none of the servers to be 
started.

        1. msg-nms-hahost1Which server instances do you wish to start up? [All]:

Verify the Messaging Server parameters.

Listed below are all the parameters you specified that create a 
Messaging Server instance. Please check to make sure they are 
correct.Press '^B' to go back to the dialogs you visited and correct them
if necessary
 
When you are done, press enter to continue.


	Domain             : sun.com
	Hostname           : hahost1.domain.sun.com
	Server ID          : msg-nms-hahost1
	Server User        : mailsrv
	SMTP Port          : 25
	IMAP Port          : 143
	POP3 Port          : 110
	Webmail Port       : 80
	Queue Directory    : /hahost1/nms/msg-nms-hahost1/queue
	Store Directory 	 	 	 : /hahost1/nms/msg-nms-hahost1/store/part



<enter>

...

The setup program now uses the parameters you specified to set up and start the Netscape Messaging Server components you configured.

Decide whether to retain the installation cache, install.inf.

...

The installation cache "install.inf" generated by the setup 
program is located in the server root's setup directory. This file 
can be used as a silent installation script for installation of 
similar servers on other machines. It, however, may contain 
sensitive information such as user IDs and passwords you have 
entered.Would you like to remove it? [Yes]: No

Stop the Messaging Server manually.

Run this command from the node currently mastering the server root on the shared disk.
# cd /hahost1/nms/nms_instancename # ./stop-msg
Proceed to "Configuring the Sun Cluster HA for Netscape Data Services".

Netscape Directory Server (LDAP)

Sun Cluster HA for Netscape LDAP is the Netscape Directory Server using the Lightweight Directory Assistance Protocol (LDAP) and running under the control of Sun Cluster. This section describes the steps to take when installing Netscape Directory Server (by using the ns-setup command) to enable it to run as the Sun Cluster HA for Netscape LDAP data service.

If not already installed, use pkgadd to install the SUNWscnsl package on each Sun Cluster server.

Netscape Directory server requires some variation from the default installation parameters, notably:

Specifying the logical host name rather than the physical host name
Do not use the default server root disk when prompted, your files must reside on the multihost disk
When supplying the base install directory pathname, this should be the location of the start and stop scripts

How to Install Netscape Directory Server (LDAP)

Before you begin this procedure, complete the appropriate pre-requisite steps listed in Table 8-2.

This procedure shows the user interaction with the ns-setup command. Only the sections that are specific to Sun Cluster HA for Netscape LDAP are shown here. For the other sections, choose or change the default values as appropriate. These are the basic steps; consult your Netscape Directory Server documentation for details.

All of the steps in this procedure must be performed as root.

Make sure each logical host is served by its default master.

The Netscape application will be installed from the physical host that is the logical host's default master. If necessary, switch over the logical hosts to be served by their respective default masters.

Note -
The logical host names you use in your Sun Cluster configuration should be used as the server names when you install and configure the Netscape application in the following steps. This is necessary for failover of the Netscape server to work properly.

Install Netscape Directory Server.

Choose the logical host that will provide directory services for the cluster. Install the Netscape Directory Server product on that logical host's shared disk.

Run the ns-setup command from the install directory on the CD.

Run the ns-setup command from the Netscape Directory Server install directory. You must supply the logical host name when ns-setup prompts you for the full server name. In this example, the logical host is hahost1:
phys-hahost1# ./ns-setup Server root [/usr/netscape/suitespot]: /hahost1/d1/ns-home Full name [phys-hahost1]: hahost1

Use the Netscape admin server to configure and test the Netscape Directory Server.

See your Netscape documentation for details.

Configuring the Sun Cluster HA for Netscape Data Services

After you have installed the Sun Cluster HA for Netscape packages and the Netscape applications, you are ready to configure the individual data services.

Sun Cluster currently supports these Netscape data services: Sun Cluster HA for Netscape News, Sun Cluster HA for Netscape HTTP, Sun Cluster HA for Netscape Mail, and Sun Cluster HA for Netscape LDAP.

Sun Cluster HA for Netscape allows configurable instances, which are independent of each other. For example, you can install and configure any number of web servers; each such server is considered an instance.

All Sun Cluster HA for Netscape data services are configured by using the hadsconfig(1M) command.

How to Configure the Sun Cluster HA for Netscape Data Services

If you installed the data service packages on all potential masters of a logical host but not on all hosts in the cluster, use the -h option and specify the logical host name.

Table 8-3 Data Service Registration Names and Syntax


Data Service	Registration Syntax
Sun Cluster HA for Netscape HTTP	`hareg` `-s` `-r` `nshttp` `[-h` `logicalhost`]
Sun Cluster HA for Netscape News	`hareg` `-s` `-r` `nsnews` `[-h` `logicalhost`]
Sun Cluster HA for Netscape Mail (for both Mail and Messaging Server)	`hareg` `-s` `-r` `nsmail` `[-h` `logicalhost`]
Sun Cluster HA for Netscape LDAP	`hareg` `-s` `-r` `nsldap` `[-h` `logicalhost`]

Run the hadsconfig(1M) command to configure your Sun Cluster data service(s).

The hadsconfig(1M) command is used to create, edit, and delete instances of a Sun Cluster HA for Netscape data service. See the hadsconfig(1M) man page for details. Refer to "Configuration Parameters for the Sun Cluster HA for Netscape Data Services", for information on the input to supply to hadsconfig(1M).
phys-hahost1# hadsconfig
Note -
Sun Cluster HA for Netscape News and Sun Cluster HA for Netscape HTTP support installation of multiple instances of news and http servers, which can be located anywhere in the cluster. Because the mail protocol listens to a well-known port, only one instance of Sun Cluster HA for Netscape Mail can exist in a cluster.

Run the hareg -y command to enable all services and perform a cluster reconfiguration.
phys-hahost1# hareg -y
The configuration is complete.

Configuration Parameters for the Sun Cluster HA for Netscape Data Services

This section describes the information you supply to the hadsconfig(1M) command to create configuration files for each Sun Cluster HA for Netscape data service. The hadsconfig(1M) command uses templates to create these configuration files. The templates contain some default, some hard coded, and some unspecified parameters. You must provide values for those parameters that are unspecified.

The fault probe parameters, in particular, can affect the performance of Sun Cluster HA for Netscape data services. Tuning the probe interval value too low (increasing the frequency of fault probes) might encumber system performance, and also might result in false takeovers or attempted restarts when the system is simply slow.

Fault probe parameters are configurable for Sun Cluster HA for Netscape HTTP, Sun Cluster HA for Netscape News, and Sun Cluster HA for Netscape LDAP. Fault probe parameters are not configurable for Sun Cluster HA for Netscape Mail.

All Sun Cluster HA for Netscape data services require you to set the takeover flag. This flag specifies how Sun Cluster will handle partial failover. There are two options:

y (yes) - Sun Cluster will attempt to switch over the logical host to another master, but if the attempt fails the logical host will remain on the original master.
n (no) - Sun Cluster will not move the logical host to another master, even if it detects problems with the data server, nor will it take any action against the faulty data server or database on the logical host.

Configuration Parameters for Sun Cluster HA for Netscape News

Configure the Sun Cluster HA for Netscape News parameters listed in the hadsconfig(1M) input form by supplying options described in Table 8-2.

Table 8-4 Configuration Parameters for Sun Cluster HA for Netscape News


Parameter	Description
Name of the instance	Nametag used as an identifier for the instance. The log messages generated by Sun Cluster HA for Netscape News refer to this nametag. The `hadsconfig(1M)` command prefixes the package name to the value you supply here. For example, if you specify "`nsnews_119`," the `hadsconfig(1M)` command produces "`SUNWscnew_nsnews_119`."
Logical host	Name of the logical host that provides service for this instance of Sun Cluster HA for Netscape News.
Base directory of product installation	Rooted path name specifying the location on the multihost disk of the Netscape News installation. This is the "instance path," for example, `/hahost1/news-hahost1`.
Probe interval	The time, in seconds, between fault probes. The default interval is 60 seconds.
Probe timeout	The time, in seconds, after which a fault probe will time out. The default timeout value is 20 seconds.
Server port number	Unique port for this instance of Sun Cluster HA for Netscape News. This is the "Server Port" value you supplied to the `ns-setup` command.
Takeover flag	Specifies whether a failure of this instance will cause a takeover or failover of the logical host associated with the data service instance. Possible values are `y` (yes), or `n` (no).

Note -

Do not use an HA administrative file system for the Sun Cluster HA for Netscape News installation base directory. Check the vfstab.logicalhost file to verify that the base directory you have chosen is not an HA administrative file system.

Configuration Parameters for Sun Cluster HA for Netscape HTTP

Configure the Sun Cluster HA for Netscape HTTP parameters listed in the hadsconfig(1M) input form by supplying options described in Table 8-5.

Table 8-5 Configuration Parameters for Sun Cluster HA for Netscape HTTP


Parameter	Description
Name of the instance	Nametag used as an identifier for the instance. The log messages generated by Sun Cluster refer to this nametag. The `hadsconfig(1M)` command prefixes the package name to the value you supply here. For example, if you specify "nshttp_80," the `hadsconfig(1M`) command produces "SUNWschtt_nshttp_80."
Logical host	Name of logical host that provides service for this instance of Sun Cluster HA for Netscape HTTP.
Base directory of product installation	This is the base directory of the product installation, plus the server type and server port number. For example, `/hahost1/https-hahost`.
Probe interval	The time, in seconds, between fault probes. The default interval is 60 seconds.
Probe timeout	The time, in seconds, after which a fault probe will time out. The default timeout value is 20 seconds.
Server port number	Unique port for this instance of Sun Cluster HA for Netscape HTTP. This is the "Server Port" value you supplied to the `ns-setup` command.
Takeover flag	Specifies whether a failure of this instance will cause a takeover or failover of the logical host associated with the data service instance. Possible values are `y` (yes), or `n` (no).

Note -

Do not use an administrative file system for the Sun Cluster HA for Netscape HTTP installation base directory. Check the vfstab .logicalhost file to verify that the base directory you have chosen is not an administrative file system.

Configuration Parameters for Sun Cluster HA for Netscape Mail (for Netscape Mail)

Configure the Sun Cluster HA for Netscape Mail parameters listed in the hadsconfig(1M) input form by supplying options described in Table 8-6.

Table 8-6 Configuration Parameters for Sun Cluster HA for Netscape Mail (for Netscape Mail)


Parameter	Description
Name of the instance	Nametag used as an identifier for the instance. The log messages generated by Sun Cluster refer to this nametag. The `hadsconfig(1M)` command prefixes the package name to the value you supply here. For example, if you specify "nsmail," the `hadsconfig(1M`) command produces "SUNWscnsm_nsmail."
Logical host	Name of logical host that provides service for this instance of Sun Cluster HA for Netscape Mail.
Takeover flag	Specifies whether a failure of this instance will cause a takeover or failover of the logical host associated with the data service instance. Possible values are `y` (yes), `n` (no).

Configuration Parameters for Sun Cluster HA for Netscape Mail (for Netscape Messaging Server)

Configure Sun Cluster HA for Netscape with Netscape Messaging Server using the parameters described in Table 8-7.

Table 8-7 Configuration Parameters for Sun Cluster HA for Netscape Mail (for Netscape Messaging Server)


Parameter	Description
Name of the instance	Nametag used as an identifier for the instance. The log messages generated by Sun Cluster refer to this nametag. The `hadsconfig(1M)` command prefixes the package name to the value you supply here. For example, if you specify `nsmsg`, the `hadsconfig(1M)` command produces SUNWscnsm_nsmsg.
Logical host	Name of logical host that provides service for this instance of Sun Cluster HA for Netscape Mail.
Base directory of product installation	Rooted path name specifying the location on the multihost disk of the Netscape Messaging Server installation. This is the "instance path," for example, `/hahost1/nms-hahost1`.
Takeover flag	Specifies whether a failure of this instance will cause a takeover or failover of the logical host associated with the data service instance. Possible values are `y` (yes), `n` (no).

Configuration Parameters for Sun Cluster HA for Netscape LDAP

Configure the Sun Cluster HA for Netscape LDAP parameters listed in the hadsconfig(1M) input form by supplying options described in Table 8-8.

Table 8-8 Configuration Parameters for Sun Cluster HA for Netscape LDAP


Parameter	Description
Name of the instance	Nametag used as an identifier for the instance. The log messages generated by Sun Cluster refer to this nametag. The `hadsconfig(1M)` command prefixes the package name to the value you supply here. For example, if you specify "nsldap," the `hadsconfig(1M`) command produces "SUNWhansm_nsldap."
Logical host	Name of logical host on which the Netscape Directory Server resides.
Base directory of product installation	This is the base directory of the product installation. Include the logical host name prefixed with `ns-slapd_`. For example, `/hahost1/d1/ns-home/ns-slapd_hahost1/`. Make sure the directory you specify includes the `start` script.
Server port number	Unique port for this instance of Sun Cluster HA for Netscape LDAP. This is the "Server Port" value you supplied to the `ns-setup` command. The default value is 389.
Takeover flag	Specifies whether a failure of this instance will cause a takeover or failover of the logical host associated with the data service instance. Possible values are `y` (yes), or `n` (no).
Probe interval	The time, in seconds, between fault probes. The default interval is 60 seconds.
Probe timeout	The time, in seconds, after which a fault probe will time out. The default timeout value is 30 seconds.