Sun Cluster 2.2 Software Installation Guide

Chapter 8 Setting Up and Administering 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 procedures:

8.1 Sun Cluster HA for Netscape Overview

The Sun Cluster HA for Netscape data services consist of a group of NetscapeTM 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 

Package Name 

Netscape News Server 

Sun Cluster HA for Netscape News 

SUNWscnew

Netscape Mail Server 

Sun Cluster HA for Netscape Mail 

SUNWscnsm

Netscape HTTP/Web Server 

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.

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 ... 

  1. 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

  1. Starting the cluster with the scadmin(1M) command

Chapter 3, Installing and Configuring Sun Cluster Software, or the scadmin(1M) man page

  1. (Optional) Installing and setting up DNS for the Netscape data services to use

Chapter 12, Setting Up and Administering Sun Cluster HA for DNS

  1. Installing and configuring Sun Cluster HA for Netscape data services

"8.2 Installing Netscape Services"," and "8.7 Configuring the Sun Cluster HA for Netscape Data Services"

  1. Registering and starting the Sun Cluster HA for Netscape data services

"8.7 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, Setting Up and Administering 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.

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


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.

8.2 Installing Netscape Services

Before you begin the Netscape services installation, complete the appropriate pre-requisite steps listed in Table 8-2.

8.2.1 How to Install Netscape Services

Consult your Netscape application documentation before performing this procedure. All of the procedures in this chapter must be performed as root.

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

    Each 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 applications in the following steps. This is necessary for failover of the Netscape server to work properly.


  2. After cluster reconfiguration is complete, install the Netscape application software on the logical hosts by using the Netscape ns-setup command on the distribution CD.

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


    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.


    Proceed to "8.3 Installing Netscape News", to install the Sun Cluster HA for Netscape data services.

8.3 Installing 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 (by using the ns-setup command) 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.

  1. 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.

  2. 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:

8.3.1 How to Install Netscape News

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.

  1. 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]:
  2. 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.

  3. Enter Server Administrator ID and password when asked.

    Follow the guidelines for your system.


    Note -

    The default administration port is not the port that the data services will listen on, so it is an acceptable default. You will however, want to make note of the 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 ...
  4. Bring up the Netscape browser.

    Web browser [netscape]: 

    You should see the Netscape browser.

  5. 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.

  6. Click Create New Netscape Collabra Server 3.5.

    This should be the second link from the bottom of the page. You should see another page load.

  7. 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.

  8. Run the hadsconfig command from the physical host:

    [phys-hahost1]: hadsconfig
    
  9. Enter the number for the nsnews menu item at the prompt.

    Your choices may vary depending on the services installed.

  10. 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]  [?] :
  11. Enter the name for the instance.

  12. Enter your logical hostname.

  13. 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. You may have created other directories between the logical host and service directories.

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

    For example 119 for News.

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

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

  16. Add this instance.

    You see instance added to workfile.

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

    You see Configuration has changed in workfile.

  18. Update the configuration from the workfile.

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

  20. Enter the Quit menu item number.

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

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

    Run the hareg(1M) command on only one host.

    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]

    If the cluster is running already, use the hareg(1M) command to activate the service:

    # hareg -y nsnews
    
  22. Confirm your News server operation by making a telnet connection to your logical host where the service is listening.

    For example:

    # telnet logicalhost 119
    

    After you have confirmed the server's operation, your installation is complete.

8.4 Installing 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.



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:

8.4.1 How to Install Netscape Web or HTTP Server

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.

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

    From the Netscape Commerce distribution location on the CD, run the ns-setup command.

    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.
  2. 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.

  3. Enter the Server Administrator ID and password when asked.

    Follow the guidelines for your system.


    Note -

    The default administration port is not the port where the data services will listen on, 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 ...
  4. Bring up the Netscape browser.

    Web browser [netscape]: 

    The Netscape browser appears.

  5. 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.

  6. 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.

  7. Click Create New Netscape Enterprise Server 3.5.1.

    This should be the second link from the bottom of the page. You should see another page load.

  8. 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.

  9. Run the hadsconfig command from the physical host:

    [phys-hahost1]: hadsconfig
    
  10. Enter the number for the nshttp menu item at the prompt.

    Your choices may vary depending on the services installed.

  11. 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]  [?]
  12. Enter a name for the instance.

  13. Enter your logical hostname.

  14. 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/hahost1. You may have created other directories between the logical host and service directories.

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

  16. 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.

  17. Add this instance.

    You see instance added to workfile.

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

    You see Configuration has changed in workfile.

  19. Update the configuration from the workfile.

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

  21. Enter the Quit menu item number.

    Return to the root prompt of your physical host.

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

    Run the hareg(1M) command on only one host.

    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]

    If the cluster is running already, use the hareg(1M) command to activate the service:

    # hareg -y nshttp
    
  23. 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.

8.5 Installing Netscape Mail

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

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:

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

8.5.1 How to Install Netscape Mail

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.

  1. 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.
  2. 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
    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.

  3. Enter Server Administrator ID and password when asked.

    Follow the guidelines for your system.


    Note -

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


    You see information similar to the following:

    Attempting to start Netscape Admin Server...
  4. Continue with the installation when prompted.

  5. 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.

  6. 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.

  7. Specify a Server Identifier name.

  8. 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]:
  9. When you are ready, 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
  10. Start the Netscape Messaging Server when prompted.

  11. Run the hadsconfig command from the physical host:

    [phys-hahost1]: hadsconfig
    
  12. Enter the number for the nsmail menu item at the prompt.

    Your choices may vary depending on the services installed.

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

    You see something similar to the following:

    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
  14. Enter the name for the instance.

  15. Enter your logical hostname.

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

    You can change these defaults at this time if necessary.

  17. Add this instance.

    You see Instance added to workfile.

  18. Go to the -Main -Menu when prompted.

    You see Configuration has changed in workfile.

  19. Update the configuration from the workfile when prompted.

  20. Enter the -Quit menu item number.

    Return to the root prompt of your physical host.

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

    Run the hareg(1M) command on only one host.

    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]

    If the cluster is running already, use the hareg(1M) command to activate the service:

    # hareg -y nsmail
    

    This completes the installation of Netscape Mail.

8.6 Installing Netscape Directory Server

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 SUNWhadns package on each Sun Cluster server.

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

8.6.1 How to Install Netscape Directory Server

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.

  1. 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.

  2. 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
    
  3. Use the Netscape admin server to configure and test the Netscape Directory Server.

    See your Netscape documentation for details.

8.7 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.

8.7.1 How to Configure the Sun Cluster HA for Netscape Data Services

  1. 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 "8.7.2 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.


  2. Register the Sun Cluster HA for Netscape data services.

    Register the data services by running the hareg(1M) command.

    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 

    hareg -s -r nsmail [-h logicalhost]

    Sun Cluster HA for Netscape LDAP 

    hareg -s -r nsldap [-h logicalhost]

  3. Run the hareg -Y command to enable all services and perform a cluster reconfiguration.

    phys-hahost1# hareg -Y
    

    The configuration is complete.

8.7.2 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:

8.7.2.1 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-4.

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.


8.7.2.2 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 News

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.


8.7.2.3 Configuration Parameters for Sun Cluster HA 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

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).

8.7.2.4 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-7.

Table 8-7 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.