F    Configuring ASU in a Version 1.x Cluster

In a TruCluster Version 1.x cluster, the ASU server runs on only one cluster member at a time. If that cluster member fails, the ASU server automatically restarts on another cluster member on which the ASU software is installed, and user conections are reestablished. Users may experience a short delay while the ASU server restarts.

You must perform the following tasks to configure the ASU server in a TruCluster Version 1.x cluster:

F.1    ASU and TruCluster Software Prerequisites

You must identify at least two cluster members that will run the ASU server. One member on which the ASU server is active and one member on which the ASU server is inactive. The inactive member takes over the ASU server responsibility if the active member fails.

The cluster members must have compatible versions of software and firmware and use a SCSI-connected shared bus to access the shared disk that will contain ASU-related configuration and data files, such as the ASU share database and the user account database. The shared disk may be a single disk, multiple disks, mirrored disks, or a disk array that is accessible to systems in the environment.

If the cluster members and clients use TCP/IP, you need a TCP/IP address for the ASU disk service. Cluster members must have an entry in their /etc/hosts file for the ASU disk service that includes the TCP/IP address and name for the ASU disk service. The name associated with the TCP/IP address must be the ASU server name.

For example, if the the ASU server and disk service name is ASU and the IP address assigned to the service is 10.0.0.10, then a line similar to the following must be included in the /etc/hosts file on each cluster member:

10.0.0.10 ASU

Systems that reside in different subnets must have access to the name and address of the ASU disk service either by adding an entry in the local /usr/net/servers/lanman/datafiles/lmhosts file or through a DNS or a WINS server.

F.2    Creating a TruCluster Disk Service

Use the asemgr utility to create a disk service for the ASU server. Follow these steps to create a TruCluster disk service:

  1. Edit the /etc/hosts file and add the TCP/IP name and address assigned to the ASU disk service.

  2. Log in as root and start the TruCluster asemgr utility as follows:

    # asemgr

    The asemgr utility displays the ASE main menu.

  3. Choose the following options: Managing ASE Service, then Service Configuration, then Add a new service, then Disk Service.

    A status message is displayed. You are prompted to enter a name for the disk service.

  4. Enter a name for the disk service. Enter the same name that you will use for the ASU server when you configure the ASU software.

    You are prompted to assign a TCP/IP address to the disk service.

  5. Enter yes to assign a TCP/IP address.

    The TruCluster software locates the TCP/IP address for the service in the /etc/hosts file.

    You are prompted for the location of the shared disk.

  6. Enter the location of the shared disk for the service. For example, /dev/rz10c.

    You are prompted to enter the mount point for the shared disk.

  7. Enter a mount point. For example, /ASU.

    You are prompted for the type of access to the mount point.

  8. Enter 1, Read-write.

    You are prompted to optionally enable user and group quotas.

  9. Enable quotas by using the default files provided or supply a full path to a file that you choose. Enter none to disable quotas.

    You are prompted to optionally provide mount options.

  10. Enter the options you want or press the Enter key to choose the default options, which are listed in the mount reference page.

    You are prompted to enter information about another shared disk.

  11. Optionally, enter the location of another shared disk to be used by the service and repeat steps 5 through 9. Press the Enter key to continue.

    The Modifying user-defined scripts for the service menu is displayed.

  12. Choose the Start action script option.

    The Modifying the start script for the service menu is displayed.

  13. Choose the Add a start action script option.

    You are prompted for the full pathname for the start action script.

  14. Enter the following pathname:

    /usr/net/servers/lanman/scripts/asuase_start

    You are prompted to enter an argument list for the script.

  15. Press the Enter key.

    You are prompted to enter a timeout period (in seconds).

  16. Press the Enter key to choose the default value.

    The Modifying the start script for the service menu is displayed.

  17. Choose the Exit option.

    The Modifying user-defined scripts for the service menu is displayed.

  18. Repeat steps 12 through 16 replacing the word start with stop.

    The Modifying the stop script for the service menu is displayed.

  19. Choose the Exit option until the Selecting an Automatic Service Placement (ASP) Policy menu is displayed.

    Choose the Favor Members option.

    A list of system names is displayed. You are prompted to select the systems to which the service will fail over.

  20. Choose the systems in the order in which you want the service to fail over.

    You are prompted to relocate the server to a more highly favored member if one becomes available.

  21. Choose no if you want the service to remain on the system to which it failed over even after the system that it was originally running on returns to the cluster.

    You are prompted to add the service.

  22. Answer yes.

    The service is added.

For more information on creating a disk service, see the TruCluster Available Server Software Software Installation guide.

F.3    Configuring the ASU Software

Follow these steps to configure the ASU software:

  1. Choose a system on which the ASU server will be active and log in as root.

  2. Run the /usr/sbin/asusetup utility.

    The asusetup utility detects if the TruCluster software is installed on the system and, if so, asks if the ASU server will participate in a TruCluster Version 1.x cluster.

  3. Answer yes.

    The asusetup utility prompts you for the TruCluster disk service name and mount point.

  4. Enter the disk service name and mount point.

    The configuration proceeds. See Chapter 1 for more information on configuring the ASU software.

Follow these steps to configure the alternate system on which the ASU server is installed:

  1. Log in as root to the alternate server and run the /usr/sbin/asusetup utility.

    The asusetup utility detects if the TruCluster software is installed on the system and, if so, asks if the ASU server will participate in a TruCluster Version 1.x cluster.

  2. Answer yes.

    The asusetup utility prompts you for the TruCluster disk service name and mount point.

  3. Enter the disk service name and mount point.

    You are prompted for transport information for the ASU server.

  4. Enter the transport information for the ASU server.

    See Chapter 1 for more information on configuring the transport information for the ASU software.

Because the alternate ASU server assumes the identity and role of the active ASU server if that server becomes unavailable, no other configuration information is needed.

F.4    ASU Licensing in a TruCluster Cluster

Although the ASU server is cluster-aware, the license management facility (LMF) is not. ASU licenses are supplied in the form of a product authorization key (PAK) called ASDU-CONNECT that you load into LMF. You must load an ASDU-CONNECT PAK in LMF on each cluster member on which you will run the ASU server.

See Section 1.9 for ASU licensing information.

F.5    Managing ASU Resources in a TruCluster Cluster

The following sections describe how to create and manage ASU disk shares, domain user accounts, and ASU printer shares in a TruCluster cluster.

F.5.1    Creating Disk Shares

When you configure the ASU server in a TruCluster cluster, links are automatically established to the shared disk in the /usr/net/servers/lanman/shares directory.

Shares that you create in this directory, or in any other directory on the shared disk, are accessible by all cluster members. You must ensure that shares created prior to setting up the ASU server in a TruCluster cluster are located on the shared disk. Shares created on a nonshared or local disk are not accessible by other cluster members after a failover.

F.5.2    Maintaining User Accounts

In a TruCluster cluster, the ASU server requires that the /etc/passwd file contain identical entries on all cluster members.

By default, adding or deleting a domain user account adds or deletes the associated Tru64 UNIX user account only in the /etc/passwd file on the local system and other cluster members cannot access this information.

You can make Tru64 UNIX user account information available to all cluster members by using Network Information Service (NIS) in the cluster. To do so, you must create Tru64 UNIX user accounts on the NIS master server before you create domain user accounts. This way, when you create domain user accounts, ASU does not create the Tru64 UNIX accounts locally because they already exist in the NIS database.

If you do not include NIS in the cluster you must manually maintain the local /etc/passwd files on each member server.

F.5.3    Maintaining Print Services

In a TruCluster cluster, the shared disk stores information for each ASU printer share. If you modify information about print services in the /etc/printcap file on a member server, then you must modify the /etc/printcap file on all the member servers to include the same information.

F.6    Removing ASU from a TruCluster Cluster

To remove the ASU server you can:

F.6.1    Removing One ASU Server from the Cluster

Follow these steps to remove one ASU server from the cluster:

  1. If the system you want to remove from the cluster is currently running the ASU service, relocate the ASU service to an alternate system.

  2. Restrict the system you want to remove from running the ASU service.

  3. Either deinstall the ASU server from the system or run the asusetup utility and answer no when prompted if the ASU server will participate in a TruCluster Version 1.x cluster.

These steps are discussed in the following sections.

F.6.1.1    Relocating the ASU Service

Follow these steps to relocate an ASU service from the active server to an alternate server:

  1. Log in as root and start the asemgr utility as follows:

    # asemgr

    The ASE main menu is displayed.

  2. Choose the Managing ASE Services option, then the Relocate a service option.

    The Select the service that you want to relocate menu is displayed.

  3. Enter the number that represents the ASU service you want to relocate.

    The Select member to run 'service name' service menu is displayed.

  4. Enter the number that represents the ASU server to which you want to relocate the service.

    A status message indicates whether or not the relocation was successful.

F.6.1.2    Restricting a System from Running the ASU Service

Follow these steps to restrict a system in a the TruCluster Version 1.x cluster from running the ASU service:

  1. Log in as root and start the asemgr utility as follows:

    # asemgr

    The ASE main menu is displayed.

  2. Choose the Managing ASE Services option and then choose the Service Configuration option.

    The Service Configuration menu is displayed.

  3. Enter the number that represents the ASU service.

    A list of modification options is displayed.

  4. Choose the Restrict Membership option.

    A list of members displays.

  5. Choose to restrict the member you want to restrict from running the ASU disk service in the cluster.

F.6.1.3    Deinstall the ASU Server

You can deinstall the ASU server from a system by removing the ASU subsets. Follow these steps to remove ASU subsets:

  1. Log in to the Tru64 UNIX system as the root user and notify users that the ASU server will be unavailable.

  2. Display the installed ASU subsets by entering the following command:

    # setld -i |grep ASU |grep -v not |grep installed

  3. Enter the /usr/sbin/setld -d command followed by the name of the subset(s) that you want to remove. For example:

    # setld -d ASUADMnnn ASUBASEnnn ASUMANPAGEnnn ASUTRANnnn

    The nnn represents the version number of the ASU software. See the ASU Release Notes for the current version number.

    During the deinstallation you are prompted to reconfigure the ASU software, resulting in its removal from the cluster.

  4. Answer yes at the prompt.

While the ASU subsets are being removed you might be prompted to save data files. You can answer no because the data files are saved on the shared disk.

Deinstalling the ASU subsets does not remove files and directories that were created in the ASU directory structure by users. You might want to delete any directories and files still remaining in the /usr/net/server/lanman directory.

F.6.2    Removing ASU from All Systems in a TruCluster Version 1.x Cluster

Follow these steps to remove the ASU server from all the systems in a cluster:

  1. Decide which system will receive the ASU data files from the shared disk and, if necessary, relocate the ASU service to that system.

  2. Restrict the ASU server to run on only the system that will receive the data files in step 1.

  3. Remove the ASU server from the alternate system.

  4. Remove the ASU server from the active system.

  5. Remove the ASU disk service from the TruCluster cluster.

These steps are discussed in more detail in the following sections.

F.6.2.1    Relocating the ASU Service

If the system to which you want to transfer the ASU data files is not the active server, then use the following steps:

  1. Log in as root and start the asemgr utility as follows:

    # asemgr

    The ASE main menu is displayed.

  2. Choose the Managing ASE Services option, then the Relocate a service option.

    The Select the service that you want to relocate menu is displayed.

  3. Enter the number that represents the ASU service you want to relocate.

    The Select member to run 'service name' service menu is displayed.

  4. Enter the number that represents the system to which you want to relocate the ASU service.

    A status message indicates whether or not the relocation was successful.

F.6.2.2    Restrict the ASU Server to Run on a Single System

Follow these steps to restrict the ASU server to run on a single system:

  1. Log in as root and start the asemgr utility as follows:

    # asemgr

    The ASE main menu is displayed.

  2. Choose the Managing ASE Services option and then choose the Service Configuration option.

    The Service Configuration menu is displayed.

  3. Enter the number that represents the ASU service.

    A list of modification options is displayed.

  4. Choose the Restrict Membership option.

    A list of member names is displayed.

  5. Choose to restrict all the members from running the ASU service, leaving as a member only the system to which you want to transfer the data files.

F.6.2.3    Removing the ASU Server from the Alternate System

Follow these steps to remove the ASU server from the alternate system:

  1. Log in as root and start the asusetup utility as follows:

    # asusetup

    The asusetup utility detects if the ASU server was configured to run as a TruCluster service and prompts you to respond whether or not you want it to continue to run as part of the TruCluster disk service.

  2. Answer no at the prompt.

    The asusetup utility prompts you to reconfigure the ASU server.

  3. Answer yes to configure the ASU server. The asusetup utility continues with normal configuration questions and procedures.

    Answer no to exit the asusetup utility and, if desired, use the setld command to delete the ASU subsets from the system.

    See Chapter 1 for more information on configuring the ASU software.

F.6.2.4    Removing the ASU Server from the Active System

Follow these steps to remove the ASU server from the active system:

  1. Log in as root and start the asusetup utility as follows:

    # asusetup

    The asusetup utility detects if the ASU server was configured to run as a TruCluster service, and prompts you to respond whether or not you want it to continue to run as part of the TruCluster disk service.

  2. Answer no at the prompt.

    The asusetup prompts you to transfer the data files located on the shared disk to the local disk.

  3. Answer yes at the prompt.

    The asusetup utility prompts you to reconfigure the ASU software.

  4. Answer yes at the prompt.

    The asusetup utility continues with normal configuration prompts and procedures.

    See Chapter 1 for more information on configuring the ASU software.

    If you configure the ASU server as back up domain controller, then the user account database that was transferred from the shared disk to the local disk is overwritten by the user account database maintained by the primary domain controller.

F.6.2.5    Removing the ASU Disk Service

Follow these steps to remove the ASU disk service:

  1. Log in as root and start the asemgr utility as follows:

    # asemgr

    The ASE main menu is displayed.

  2. Choose the following options: Managing ASE Service, then Service Configuration, then Delete a service option.

    The Deleting a Service menu is displayed.

  3. Enter the number that represents the ASU disk service that you want to remove.

    A confirmation message is displayed.

  4. Answer yes at the prompt.

    The service is removed.