You can configure ASU disk shares, print shares, and services to be highly available by configuring two or more ASU servers in a TruCluster environment. A TruCluster environment is a grouping of AlphaServer systems running the TruCluster software. See Cluster Administration for more information on the TruCluster software.
This chapter describes how to configure the ASU server in a TruCluster Server Version 5.x or higher environment.
See
Appendix F
for information on how to configure
the ASU server in a TruCluster Version 1.x (Available Server Environment (ASE))
environment.
6.1 ASU Server Modes in a TruCluster Server Version 5.x Environment
You can configure the ASU server to operate in one of the following modes in a TruCluster Server Version 5.x environment:
Multi
Configuring 1 or more cluster members in multi mode provides the highest ASU server availability.
In multi mode, the ASU server runs on each cluster member and appears to clients as a single ASU server. For example, ASU servers configured in multi mode on six cluster members can access all ASU resources and have a single role of either primary domain controller (PDC), backup domain controller (BDC), or member server.
ASU servers configured in mutli mode use a cluster alias, which is a name known by each ASU server. Users should specify the cluster alias instead of an ASU server when connecting to shares. When users specify the cluster alias, one of the ASU servers responds. Client connections using TCP/IP are distributed among the ASU servers. Client connections using the NetBEUI transport protocol go to a single cluster member.
If an ASU server configured in multi mode stops, user connections to that ASU server are disconnected. Most clients that connected using the cluster alias will automatically reconnect to an active ASU server. If users must manually reconnect, they should again specify the cluster alias, which will connect them to an active ASU server.
Multi mode is the default mode. See Section 6.1.1 for more information on configuring the ASU server in multi mode.
Single, also called cluster application availability (CAA)
Configuring 2 or more cluster members in single mode provides high ASU server availability.
In single mode you configure the ASU server on 2 or more cluster members, but run the ASU server on only one cluster member.
If the ASU server configured in single mode stops, user connections are disconnected and the TruCluster software automatically restarts the ASU server on an alternate cluster member that is configured to run the ASU server in single mode. The alternate ASU server assumes the identity and responsibility of the stopped ASU server. Most clients will automatically reconnect to the alternate ASU server. If users must manually reconnect, they should again specify the same ASU server name, which will connect them to the alternate ASU server.
Configuring ASU servers in single mode provides similar functionality to that provided by the TruCluster Version 1.x (ASE) software.
See Section 6.1.2 for more information on configuring the ASU server in single mode.
None
Configuring ASU servers in none mode does not provide high ASU server availability. You configure the ASU server in none mode if you are running the TruCluster software on a system and do not want the ASU server to use the TruCluster software.
In none mode you configure the ASU server to run on only one cluster member. If that cluster member fails, the ASU server does not restart on another cluster member.
See Section 6.1.3 for more information on configuring the ASU server in none mode.
6.1.1 Configuring the ASU Server in Multi Mode
You must run the
asusetup
utility
on a cluster member.
The
asusetup
utility prompts you for
ASU server network and general information that is described in
Section 1.4
and for the following TruCluster information:
The mode (multi, single, or none) in which the ASU server will operate in the TruCluster environment
The cluster alias
To run the
asusetup
utility, enter:
#
/usr/sbin/asusetup
Example 6-1
displays sample
asusetup
output for an ASU server configured to operate in multi mode.
Example 6-1: Sample Multi Mode asusetup Output
Advanced Server for UNIX Configuration Utility Administrators can configure the Advanced Server software by using the default configuration values that are detected from a previous Advanced Server configuration. If no previous Advanced Server configuration is detected then the default values are determined by this utility. In either case, administrators can choose not to use the default values and customize the Advanced Server configuration by interactively supplying Advanced Server configuration values. The following default configuration can be used: Transports : NetBIOS over TCP/IP (controller 'ics0') NetBEUI (controller 'ics0') Cluster Alias: colors Cluster Type: multi Server Name: red Domain Name: red.dom Domain Role: Primary WAN Support: enabledns=yes, uselmhosts=yes Do you want to use this default information [y/n]? n The following network configuration is based on the previous network configuration, with default values for new items: Controllers: TCP/IP = ics0 NetBEUI = ics0 Use DNS: yes Sub Domains: company.com Use lmhosts: yes lmhosts file: /usr/net/servers/lanman/datafiles/lmhosts Use NBNS: no Primary NBNS address: Secondary NBNS address: Would you like to use this network information [y/n]? n You will now be prompted to enter configuration information for the Advanced Server for UNIX server including which network transports and controllers to use and how to resolve names in a wide area network. ********************************************************** NetBIOS over TCP/IP Setup ********************************************************** Select a controller for NetBIOS over TCP/IP. The "transports.ini" file will be modified accordingly. ics0 @ address: 10.0.0.2 tu0 @ address: 10.0.0.3 none Enter the controllers separated by a comma or type ? for help: [ ics0 ] tu0 You have entered: tu0 Are you satisfied with these controllers? [yes]? Modifying the "transports.ini" file with tu0. ********************************************************** WAN Name Services ********************************************************** By configuring Name Services, your server will be able to become a part of domains that span IP subnets. Do you want to (re)configure the Name Services [yes]? To enable WAN support you must select at least one of the following mechanisms: - Name Resolution via lmhosts file - Name Resolution via NetBIOS Name Service (NBNS) - e.g WINS Client - Name Resolution via Domain Name Service (DNS) Do you want to use lmhosts file? [no]? y lmhosts filename: [/usr/net/servers/lanman/datafiles/lmhosts] Do you want to edit the lmhosts file now [y/n]? n Do you want to enable NBNS name resolution [no]? y Enter IP address of Primary NBNS server: [no default] 10.0.0.4 Enter IP address of Secondary NBNS server or none: [none] 10.0.0.5 Do you want to enable DNS name resolution [no]? y Enter list of DNS subdomains separated by comma: [no default] company.com,company1.com You've selected the following options for Name Services: Use lmhosts file /usr/net/servers/lanman/datafiles/lmhosts Use Primary NBNS server, address 10.0.0.4 Use Secondary NBNS server, address 10.0.0.5 Use DNS server, subdomains company.com,company1.com Are you satisfied with these choices [yes]? y Modifying the "transports.ini" file with Name Service choices. ********************************************************** NetBEUI-Datalink Controller Selection ********************************************************** Select the controllers for the NetBEUI transport. ics0 tu0 Enter the controllers separated by a comma or type ? for help: [ ics0 ] tu0 You have entered: tu0 Are you satisfied with these controllers? [yes]? Modifying the "transports.ini" file with tu0. You will now be prompted to enter cluster configuration information for the Advanced Server for UNIX. The cluster environment can be configured as follows: none - not using the cluster, the server runs on one node, single - single instance server ( controlled by CAA ), multi - multi instance server, the server runs on all cluster members. Enter the cluster environment type (multi, single or none) [multi]: multi Enter the cluster alias [colors]: Starting the transports... Start: Datalink service controller_01 tu0 The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/netbeui 32 69 /dev/streams/netbeuid 32 70 /dev/streams/nbeadmin 32 71 Microsoft Datalink Driver : Starting dllink ... Datalink driver attached to tu0 at PPA1 dllink: done - Adapter set Start: NetBEUI controller_01 tu0 The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/netbeui 32 69 /dev/streams/netbeuid 32 70 /dev/streams/nbeadmin 32 71 Microsoft NetBEUI Driver : Starting nbelink ... done Start: TCP/IP NetBIOS controller_01 tu0 Starting the TCP/IP NetBIOS service... The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/knbtcp 32 72 /dev/streams/knbadm 32 73 /dev/streams/knbtcpd 32 74 TCP/IP NetBIOS: Starting knblink ... controller(s) configured as 'tu0' kernel dynamic cache will be enabled lmhosts file use enabled DNS support is enabled The following 2 DNS subdomains have been specified: company.com company1.com Cluster IP address = 10.0.0.6 NBNS Client support enabled, primary server at 10.0.0.4 NBNS Client support enabled, secondary server at 10.0.0.5 Successfully configured with controller(s) 'tu0' TCP/IP NetBIOS name resolver started, pid=1080614 TCP/IP NetBIOS service started Each ASU server must be assigned an ASU server name. ASU server names can be up to 15 alphanumeric characters and can contain the following symbols: ~ ! # $ % ^ & _ ( ) . - Server names cannot include any international characters. If this ASU server will participate in an ASE cluster environment, then the server name that you assign here must also be the name that you assign to the ASE cluster disk service for the ASU server. Enter the name of the server or press Enter to select 'red': Each server must be given a role in a domain. The possible roles are: Primary domain controller (PDC). There can be only one PDC per domain. The PDC is where the master user account database is stored, which is what the PDC uses to validate network logon requests. Backup domain controller (BDC). There can be many BDCs per domain. The BDC recieves a copy of the user account database from the PDC, which is what it uses to validate network logon requests. A BDC can be promoted to PDC if the PDC is not accessible. Member server is a member of a domain. Member servers do not store user account information and therefore do not validate network logon requests. These servers are dedicated to perform specific tasks such as being file and print servers. Enter role (primary, backup, or member): primary Enter the name of the domain or press Enter to select 'red.dom': colors.dom That domain name may already be in use. Do you want to select a different domain name [y/n]? n Confirm choices: server name : red role : primary domain : colors.dom Is this correct [y/n]? y Enter the password for Administrator: Re-enter password: Creating Advanced Server for UNIX accounts database. A clean copy of the SAM database has been written. Configuring registry... reg.ini created successfully reg.ini upgraded successfully Creating new registry file... processed 935 lines... Registry file created successfully loading /usr/net/servers/lanman/regfiles/perf009.regadm loading /usr/net/servers/lanman/regfiles/users.regadm loading /usr/net/servers/lanman/regfiles/machine.regadm load registry initialization scripts... registry load complete. Upgrading SAM database to support new format The ASU server currently listens for, and responds to, messages sent to these network names: clusteralias : colors ExtraListenNames: (none) You can define Extra Listen Names for the server to listen for via the Registry parameter ExtraListenNames. Do you want to modify the ExtraListenNames entry [y/n]? y Enter the Extra Listen Names to add to the list. Press RETURN to terminate the list. Enter an Extra Listen Name to add: red1 Enter an Extra Listen Name to add: red2 Enter an Extra Listen Name to add: ExtraListenNames: red1 red2 Enter the Extra Listen Names to remove from the list. Press RETURN to terminate the list. Enter an Extra Listen Name to remove: ExtraListenNames: red1 red2 Are you satisfied with this list of ExtraListenNames [y/n]? y These changes will take effect the next time the server is started. Cluster member blue.company.com is not configured to run Advanced Server. You can configure it without affecting any other cluster member. You will be asked to provide the names of controllers on blue.company.com to be used for the Advanced Server transports. We will provide default controller names based on the configuration of another member of the cluster. But we cannot see what devices are on blue.company.com, so we cannot validate these defaults. Also, we cannot validate any device names you specify. If you aren't sure what controllers to specify, you should answer "no" and re-run asusetup from blue.company.com. Would you like to configure Advanced Server for UNIX for cluster member blue.company.com [y/n]? y CAUTION: The following default configuration is based on the configuration of cluster member red.company.com. It may not be suitable for blue.company.com, so please respond appropriately. The following default configuration can be used: Transports : NetBIOS over TCP/IP (controller 'tu0') NetBEUI (controller 'tu0') Would you like to use this network information [y/n]? y The Advanced Server will be configured using this network information. Cluster member green.company.com is not configured to run Advanced Server. You can configure it without affecting any other cluster member. You will be asked to provide the names of controllers on green.company.com to be used for the Advanced Server transports. We will provide default controller names based on the configuration of another member of the cluster. But we cannot see what devices are on green.company.com, so we cannot validate these defaults. Also, we cannot validate any device names you specify. If you aren't sure what controllers to specify, you should answer "no" and re-run asusetup from green.company.com. Would you like to configure Advanced Server for UNIX for cluster member green.company.com [y/n]? y CAUTION: The following default configuration is based on the configuration of cluster member red.company.com. It may not be suitable for green.company.com, so please respond appropriately. The following default configuration can be used: Transports : NetBIOS over TCP/IP (controller 'tu0') NetBEUI (controller 'tu0') Would you like to use this network information [y/n]? y The Advanced Server will be configured using this network information. There are a number of registry parameters that affect how the Advanced Server creates UNIX user accounts, such as UseNIS, CreateUnixUser, and SpreadUnixHomeDirectory. If you want to change the values of these parameters, please use the regconfig utility to change the parameters now before starting the server. Please see the installation guide for further information. Start the Advanced Server for UNIX [y/n]? y The SERVER service is starting.................. The SERVER service was started successfully. Advanced Server for UNIX has the ability to test itself. Would you like to run this test now [y/n]? y (c) Compaq Computer Corp. 2001. All Rights Reserved. Verification #1 via network netbeui Create Share netbeui ...Succeeded Grant user access to share ...Succeeded Attempting connection to \\RED\netbeui ...Succeeded List File ...Succeeded Create File ...Succeeded Write data to file ...Succeeded Close data file ...Succeeded Open file for reading ...Succeeded Read data from file ...Succeeded Data Verification ...Succeeded Close data file ...Succeeded Tree Disconnect ...Succeeded Revoke user access to share ...Succeeded Remove share netbeui ...Succeeded Network netbeui complete. Verification #1 via network knbtcp Create Share knbtcp ...Succeeded Grant user access to share ...Succeeded Attempting connection to \\RED\knbtcp ...Succeeded List File ...Succeeded Create File ...Succeeded Write data to file ...Succeeded Close data file ...Succeeded Open file for reading ...Succeeded Read data from file ...Succeeded Data Verification ...Succeeded Close data file ...Succeeded Tree Disconnect ...Succeeded Revoke user access to share ...Succeeded Remove share knbtcp ...Succeeded Network knbtcp complete.
6.1.1.1 Configuring Additional ASU Servers in Multi Mode
If the ASU server is already running in the TruCluster cluster, and
you want to configure an additional ASU server on a cluster member, then you
must run the
asusetup
utility that cluster member.
The
asusetup
utility provides default values that
you should use.
If you must change some of the default values, do not change
the default values of the cluster environment type (multi), cluster alias,
and ASU role.
These values are the same for all the ASU servers configured
in multi mode in the TruCluster environment.
6.1.1.2 Multi lanman.ini File
ASU servers configured in multi mode determine their configuration by
using a shared
lanman.ini
file that the
asusetup
utility creates.
The
[ cluster ]
section in the
lanman.ini
file contains the
cluster
attribute that specifies
the ASU server mode and the
clusteralias
attribute that
specifies the name of the cluster alias.
Example 6-2
is a sample
lanman.ini
file for ASU servers configured to operate in multi mode in a TruCluster environment.
Example 6-2: Sample Multi Mode lanman.ini File
[ cluster ] cluster=multi clusteralias=colors [ workstation ] domain=colors.dom [ server ] srvservices=alerter,netlogon,browser [ lmxserver ] LMCompatibilityLevel=0 secsources=Spooler;Security Account Manager;SC Manager;LSA;Security syssources=workstation;UPS;Srv;Service Control Manager;server;SAM; Rdr;Print;NetLogon; eventlog;Browser;Alerter;System appsources=Replicator;Perfmon;Perflib;Application
6.1.1.3 Multi transports.ini File
ASU servers configured in multi mode determine their network-specific
configuration by using a shared
transports.ini
file that
the
asusetup
utility creates.
The
[ member ]
section in the
transports.ini
file contains
member_nn=ASU_server_name
attributes that uniquely identify each cluster member that is running
the ASU server in the TruCluster environment.
This identification is necessary
for the TruCluster software to rotate client connections and to redistribute
client connections from a failed cluster member, and so clients can connect
to ASU shares using the ASU server name instead of the cluster alias.
The [
tcpip
] section contains the
clusteraddr
attribute that specifies either the DNS name or TCP/IP address
of the cluster alias.
Example 6-3
is a sample
/usr/net/servers/lanman/transports.ini
file for ASU servers configured to operate in multi mode in a TruCluster
environment.
Example 6-3: Sample Multi Mode transports.ini File
[ tcpip ] clusteraddr=colors controller_01=tu0 uselmhosts=yes lmhostsfile=/usr/net/servers/lanman/datafiles/lmhosts enablenbns=yes nbnsservaddr=10.0.0.4 nbnsservaddr2=10.0.0.5 enabledns=yes dnssubdomains=company.com,company1.com controller_02=tu0 controller_03=tu0 [ member ] member_01=red.company.com,red member_02=blue.company.com,blue member_03=green.company.com,green [ netbeui ] controller_01=tu0 controller_02=tu0 controller_03=tu0
6.1.1.4 Managing ASU Servers Configured in Multi Mode
Rebooting or taking off-line a cluster member running the ASU server in multi mode does not effect the other ASU servers running in the TruCluster environment.
You use the ASU
net
commands to manage an ASU server
configured in multi mode in a TruCluster environment.
See
Appendix D
for more information about
net
commands.
Table 6-1
notes how some
net
commands work differently in a TruCluster
environment.
You use the commands and utilities described Cluster Administration to manage the cluster members and some aspects of the ASU servers, such as a load balancing policy. See Cluster Administration for more information.
Table 6-1: The net Commands that Work Differently in a Cluster
Command | Notes |
|
Displays all the open files in the TruCluster environment. |
|
Sends the message to users connected to the cluster member on which the command is entered. |
|
Displays all the client sessions in the TruCluster environment. |
|
Displays counters for the cluster member on which the command is entered. |
net start <service> |
Starts the specified service on all the ASU servers.
For example, entering
An exception is the
|
net stop <service> |
Stops the specified service on all the ASU servers.
For example, entering
An exception is the
You can enter
the
|
net pause <service> |
Pauses the specified service on all the ASU servers.
For example, entering
|
net continue <service> |
Continues the specified service on all the ASU
servers.
For example, entering
|
6.1.2 Configuring the ASU Server in Single Mode
You must run the
asusetup
utility on each cluster member on which you want to run the ASU server in
single mode.
The
asusetup
utility prompts you for the ASU
server network and general information that is described in
Section 1.4
and for the following TruCluster information:
The mode (multi, single, or none) in which the ASU server will operate in the TruCluster environment
The cluster alias
To run the
asusetup
utility, enter:
#
/usr/sbin/asusetup
Example 6-4
displays sample
asusetup
output for an ASU server configured to operate in single mode.
Example 6-4: Sample Single Mode asusetup Output
Advanced Server for UNIX Configuration Utility Administrators can configure the Advanced Server software by using the default configuration values that are detected from a previous Advanced Server configuration. If no previous Advanced Server configuration is detected then the default values are determined by this utility. In either case, administrators can choose not to use the default values and customize the Advanced Server configuration by interactively supplying Advanced Server configuration values. The following default configuration can be used: Transports : NetBIOS over TCP/IP (controller 'ics0') NetBEUI (controller 'ics0') Cluster Alias: cplors Cluster Type: multi Server Name: green Domain Name: green.dom Domain Role: Primary WAN Support: enabledns=yes, uselmhosts=yes Do you want to use this default information [y/n]? n The following network configuration is based on the previous network configuration, with default values for new items: Controllers: TCP/IP = ics0 NetBEUI = ics0 Use DNS: yes Sub Domains: asu.company.com Use lmhosts: yes lmhosts file: /usr/net/servers/lanman/datafiles/lmhosts Use NBNS: no Primary NBNS address: Secondary NBNS address: Would you like to use this network information [y/n]? n You will now be prompted to enter configuration information for the Advanced Server for UNIX server including which network transports and controllers to use and how to resolve names in a wide area network. Press return to continue... ********************************************************** NetBIOS over TCP/IP Setup ********************************************************** Select a controller for NetBIOS over TCP/IP. The "transports.ini" file will be modified accordingly. ics0 @ address: 10.0.0.3 tu0 @ address: 10.0.0.4 none Enter the controllers separated by a comma or type ? for help: [ ics0 ] tu0 You have entered: tu0 Are you satisfied with these controllers? [yes]? Modifying the "transports.ini" file with tu0. ********************************************************** WAN Name Services ********************************************************** By configuring Name Services, your server will be able to become a part of domains that span IP subnets. Do you want to (re)configure the Name Services [yes]? To enable WAN support you must select at least one of the following mechanisms: - Name Resolution via lmhosts file - Name Resolution via NetBIOS Name Service (NBNS) - e.g WINS Client - Name Resolution via Domain Name Service (DNS) Do you want to use lmhosts file? [no]? y lmhosts filename: [/usr/net/servers/lanman/datafiles/lmhosts] Do you want to edit the lmhosts file now [y/n]? n Do you want to enable NBNS name resolution [no]? y Enter IP address of Primary NBNS server: [no default] 10.0.0.4 Enter IP address of Secondary NBNS server or none: [none] 10.0.0.5 Do you want to enable DNS name resolution [no]? y Enter list of DNS subdomains separated by comma: [no default] company.com,company1.com You've selected the following options for Name Services: Use lmhosts file /usr/net/servers/lanman/datafiles/lmhosts Use Primary NBNS server, address 10.0.0.4 Use Secondary NBNS server, address 10.0.0.5 Use DNS server, subdomains company.com,company1.com Are you satisfied with these choices [yes]? y Modifying the "transports.ini" file with Name Service choices. ********************************************************** NetBEUI-Datalink Controller Selection ********************************************************** Select the controllers for the NetBEUI transport. ics0 tu0 none Enter the controllers separated by a comma or type ? for help: [ ics0 ] tu0 You have entered: tu0 Are you satisfied with these controllers? [yes]? Modifying the "transports.ini" file with tu0. You will now be prompted to enter cluster configuration information for the Advanced Server for UNIX. The cluster environment can be configured as follows: none - not using the cluster, the server runs on one node, single - single instance server ( controlled by CAA ), multi - multi instance server, the server runs on all cluster members. Enter the cluster environment type (multi, single or none) [multi]: single Enter the cluster alias [colors]: Starting the transports... Start: Datalink service controller_01 tu0 Microsoft Datalink Driver : Starting dllink ... Datalink driver attached to tu0 at PPA1 dllink: done - Adapter set Start: NetBEUI controller_01 tu0 The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/netbeui 32 72 /dev/streams/netbeuid 32 73 /dev/streams/nbeadmin 32 74 Microsoft NetBEUI Driver : Starting nbelink ... done Start: TCP/IP NetBIOS controller_01 tu0 Starting the TCP/IP NetBIOS service... The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/knbtcp 32 69 /dev/streams/knbadm 32 70 /dev/streams/knbtcpd 32 71 TCP/IP NetBIOS: Starting knblink ... controller(s) configured as 'tu0' kernel dynamic cache will be enabled lmhosts file use enabled DNS support is enabled The following 2 DNS subdomains have been specified: company.com company1.com Cluster IP address = 10.0.0.6 NBNS Client support enabled, primary server at 10.0.0.4 NBNS Client support enabled, secondary server at 10.0.0.5 Using alias as IP address on interface tu0 Successfully configured with controller(s) 'tu0' TCP/IP NetBIOS name resolver started, pid=1624682 TCP/IP NetBIOS service started Each ASU server must be assigned an ASU server name. ASU server names can be up to 15 alphanumeric characters and can contain the following symbols: ~ ! # $ % ^ & _ ( ) . - Server names cannot include any international characters. If this ASU server will participate in an ASE cluster environment, then the server name that you assign here must also be the name that you assign to the ASE cluster disk service for the ASU server. Enter the name of the server or press Enter to select 'green': Each server must be given a role in a domain. The possible roles are: Primary domain controller (PDC). There can be only one PDC per domain. The PDC is where the master user account database is stored, which is what the PDC uses to validate network logon requests. Backup domain controller (BDC). There can be many BDCs per domain. The BDC recieves a copy of the user account database from the PDC, which is what it uses to validate network logon requests. A BDC can be promoted to PDC if the PDC is not accessible. Member server is a member of a domain. Member servers do not store user account information and therefore do not validate network logon requests. These servers are dedicated to perform specific tasks such as being file and print servers. Enter role (primary, backup, or member): primary Enter the name of the domain or press Enter to select 'green.dom': colors.dom That domain name may already be in use. Do you want to select a different domain name [y/n]? n Confirm choices: server name : green role : primary domain : colors.dom Is this correct [y/n]? y Enter the password for Administrator: Re-enter password: Creating Advanced Server for UNIX accounts database. A clean copy of the SAM database has been written. Configuring registry... reg.ini created successfully Upgrading ... reg.ini upgraded successfully Creating new registry file... processed 935 lines... Registry file created successfully loading /usr/net/servers/lanman/regfiles/perf009.regadm loading /usr/net/servers/lanman/regfiles/users.regadm loading /usr/net/servers/lanman/regfiles/machine.regadm load registry initialization scripts... registry load complete. Upgrading SAM database to support new format The ASU server currently listens for, and responds to, messages sent to these network names: listenname : green ExtraListenNames: (none) You can define Extra Listen Names for the server to listen for via the Registry parameter ExtraListenNames. Do you want to modify the ExtraListenNames entry [y/n]? y Enter the Extra Listen Names to add to the list. Press RETURN to terminate the list. Enter an Extra Listen Name to add: green1 Enter an Extra Listen Name to add: green2 Enter an Extra Listen Name to add: ExtraListenNames: green1 green2 Enter the Extra Listen Names to remove from the list. Press RETURN to terminate the list. Enter an Extra Listen Name to remove: ExtraListenNames: green1 green2 Are you satisfied with this list of ExtraListenNames [y/n]? y These changes will take effect the next time the server is started. Cluster member blue.company.com is not configured to run Advanced Server. You can configure it without affecting any other cluster member. You will be asked to provide the names of controllers on blue.company.com to be used for the Advanced Server transports. We will provide default controller names based on the configuration of another member of the cluster. But we cannot see what devices are on blue.company.com, so we cannot validate these defaults. Also, we cannot validate any device names you specify. If you aren't sure what controllers to specify, you should answer "no" and re-run asusetup from blue.company.com. Would you like to configure Advanced Server for UNIX for cluster member blue.company.com [y/n]? y CAUTION: The following default configuration is based on the configuration of cluster member green.company.com. It may not be suitable for blue.company.com, so please respond appropriately. The following default configuration can be used: Transports : NetBIOS over TCP/IP (controller 'tu0') NetBEUI (controller 'tu0') Would you like to use this network information [y/n]? y The Advanced Server will be configured using this network information. Cluster member red.company.com is not configured to run Advanced Server. You can configure it without affecting any other cluster member. You will be asked to provide the names of controllers on red.company.com to be used for the Advanced Server transports. We will provide default controller names based on the configuration of another member of the cluster. But we cannot see what devices are on red.company.com, so we cannot validate these defaults. Also, we cannot validate any device names you specify. If you aren't sure what controllers to specify, you should answer "no" and re-run asusetup from red.company.com. Would you like to configure Advanced Server for UNIX for cluster member red.company.com [y/n]? y CAUTION: The following default configuration is based on the configuration of cluster member green.company.com. It may not be suitable for red.company.com, so please respond appropriately. The following default configuration can be used: Transports : NetBIOS over TCP/IP (controller 'tu0') NetBEUI (controller 'tu0') Would you like to use this network information [y/n]? y The Advanced Server will be configured using this network information. There are a number of registry parameters that affect how the Advanced Server creates UNIX user accounts, such as UseNIS, CreateUnixUser, and SpreadUnixHomeDirectory. If you want to change the values of these parameters, please use the regconfig utility to change the parameters now before starting the server. Please see the installation guide for further information. Start the Advanced Server for UNIX [y/n]? y The SERVER service is starting................... The SERVER service was started successfully. Advanced Server for UNIX has the ability to test itself. Would you like to run this test now [y/n]? y (c) Compaq Computer Corp. 2001. All Rights Reserved. Verification #1 via network netbeui Create Share netbeui ...Succeeded Grant user access to share ...Succeeded Attempting connection to \\GREEN\netbeui ...Succeeded List File ...Succeeded Create File ...Succeeded Write data to file ...Succeeded Close data file ...Succeeded Open file for reading ...Succeeded Read data from file ...Succeeded Data Verification ...Succeeded Close data file ...Succeeded Tree Disconnect ...Succeeded Revoke user access to share ...Succeeded Remove share netbeui ...Succeeded Network netbeui complete. Verification #1 via network knbtcp Create Share knbtcp ...Succeeded Grant user access to share ...Succeeded Attempting connection to \\GREEN\knbtcp ...Succeeded List File ...Succeeded Create File ...Succeeded Write data to file ...Succeeded Close data file ...Succeeded Open file for reading ...Succeeded Read data from file ...Succeeded Data Verification ...Succeeded Close data file ...Succeeded Tree Disconnect ...Succeeded Revoke user access to share ...Succeeded Remove share knbtcp ...Succeeded Network knbtcp complete.
6.1.2.1 Configuring Additional ASU Servers in Single Mode
If the ASU server is already running in the TruCluster cluster, and
you want to configure an additional ASU server on a cluster member, then you
must run the
asusetup
utility that cluster member.
The
asusetup
utility provides default values that
you should use.
If you must change some of the default values, do not change
the default values of the cluster environment type (single), cluster alias,
and ASU role.
These values are the same for all the ASU servers configured
in single mode in the TruCluster environment.
6.1.2.2 Single lanman.ini File
ASU servers configured in single mode determine their configuration
by using a shared
lanman.ini
file that the
asusetup
utility creates.
The
[ cluster ]
section in the
lanman.ini
file contains the
cluster
attribute that specifies
the ASU server mode and the
clusteralias
attribute that
specifies the name of the cluster alias.
Example 6-5
is a sample
lanman.ini
file for ASU servers configured to operate in single mode in a TruCluster
environment.
Example 6-5: Sample Single Mode lanman.ini File
[ cluster ] cluster=single clusteralias=colors [ workstation ] domain=colors.dom [ server ] listenname=green srvservices=alerter,netlogon,browser [ lmxserver ] LMCompatibilityLevel=0 secsources=Spooler;Security Account Manager;SC Manager;LSA;Security syssources=workstation;UPS;Srv;Service Control Manager;server;SAM;Rdr; Print;NetLogon;eventlog;Browser;Alerter;System appsources=Replicator;Perfmon;Perflib;Application
6.1.2.3 Single transports.ini File
ASU servers configured in single mode determine their network-specific
configuration by using a shared
transports.ini
file that
the
asusetup
utility creates.
The
[ member ]
section in the
transports.ini
file contains
member_nn=ASU_server_name
attributes that uniquely identify each member server that is running
the ASU server in the TruCluster environment.
This identification is necessary
for the TruCluster software to identify an alternate cluster member on which
to start the ASU server if necessary.
The [
tcpip
] section contains the
clusteraddr
attribute that specifies either the DNS name or TCP/IP address
of the cluster alias.
Example 6-6
is a sample
/usr/net/servers/lanman/transports.ini
file for ASU servers configured to operate in single mode in a
TruCluster environment.
Example 6-6: Sample Single Mode transports.ini File
[ tcpip ] clusteraddr=colors controller_01=tu0 uselmhosts=yes lmhostsfile=/usr/net/servers/lanman/datafiles/lmhosts enablenbns=yes nbnsservaddr=10.0.0.4 nbnsservaddr2=10.0.0.5 enabledns=yes dnssubdomains=company.com,company1.com controller_02=tu0 controller_03=tu0 [ member ] member_01=green.company.com,green member_02=blue.company.com,blue member_03=red.company.com,red [ netbeui ] controller_01=tu0 controller_02=tu0 controller_03=tu0
6.1.2.4 Managing ASU Servers Configured in Single Mode
You use the ASU
net
commands to manage an ASU server
configured in single mode in a TruCluster environment.
The
net
commands will only work on the system on which the ASU server is running.
See
Appendix D
for more information about
net
commands.
You use the commands and utilities described Cluster Administration to manage the cluster member and some aspects of the ASU server, such as specifying the alternate ASU server. See Cluster Administration for more information.
Note
If you configure ASU to run in single mode (CAA), then the ASU server is started by using the
caa_start asu
command and stopped by using thecaa_stop asu
command.If the ASU server is not running at the time of a system shutdown, it will not start during the boot process. You must issue the
caa_start asu
command to start the ASU server.See Cluster Administration for more information.
6.1.3 Configuring the ASU Server in None Mode
You must run the
asusetup
utility
on the cluster member on which you want to run the ASU server in none mode.
The
asusetup
utility prompts you for the ASU server network
and general information that is described in
Section 1.4
and
for the following TruCluster information:
The mode (multi, single, or none) in which the ASU server will operate in the TruCluster environment
The cluster alias
The cluster alias has no effect on an ASU server configured in none mode.
To run the
asusetup
utility, enter:
#
/usr/sbin/asusetup
Example 6-7
displays sample
asusetup
output for an ASU server configured to operate in none mode.
Example 6-7: Sample None Mode asusetup Output
Advanced Server for UNIX Configuration Utility Administrators can configure the Advanced Server software by using the default configuration values that are detected from a previous Advanced Server configuration. If no previous Advanced Server configuration is detected then the default values are determined by this utility. In either case, administrators can choose not to use the default values and customize the Advanced Server configuration by interactively supplying Advanced Server configuration values. The following default configuration can be used: Transports : NetBIOS over TCP/IP (controller 'ics0') NetBEUI (controller 'ics0') Cluster Alias: colors Cluster Type: multi Server Name: blue Domain Name: blue.dom Domain Role: Primary WAN Support: enabledns=yes, uselmhosts=yes ********************************************************** NetBIOS over TCP/IP Setup ********************************************************** Select a controller for NetBIOS over TCP/IP. The "transports.ini" file will be modified accordingly. ics0 @ address: 10.0.0.3 tu0 @ address: 16.20.20.96 Enter the controllers separated by a comma or type ? for help: [ ics0 ] tu0 You have entered: tu0 Are you satisfied with these controllers? [yes]? Modifying the "transports.ini" file with tu0. ********************************************************** WAN Name Services ********************************************************** By configuring Name Services, your server will be able to become a part of domains that span IP subnets. Do you want to (re)configure the Name Services [yes]? To enable WAN support you must select at least one of the following mechanisms: - Name Resolution via lmhosts file - Name Resolution via NetBIOS Name Service (NBNS) - e.g WINS Client - Name Resolution via Domain Name Service (DNS) Do you want to use lmhosts file? [no]? y lmhosts filename: [/usr/net/servers/lanman/datafiles/lmhosts] Do you want to edit the lmhosts file now [y/n]? n Do you want to enable NBNS name resolution [no]? y Enter IP address of Primary NBNS server: [no default] 10.0.0.4 Enter IP address of Secondary NBNS server or none: [none] 10.0.0.5 Do you want to enable DNS name resolution [no]? y Enter list of DNS subdomains separated by comma: [no default] company.co m,company1.com You've selected the following options for Name Services: Use lmhosts file /usr/net/servers/lanman/datafiles/lmhosts Use Primary NBNS server, address 10.0.0.4 Use Secondary NBNS server, address 10.0.0.5 Use DNS server, subdomains company.com,company1.com Are you satisfied with these choices [yes]? Modifying the "transports.ini" file with Name Service choices. ********************************************************** NetBEUI-Datalink Controller Selection ********************************************************** Select the controllers for the NetBEUI transport. ics0 tu0 Enter the controllers separated by a comma or type ? for help: [ ics0 ] tu0 You have entered: tu0 Are you satisfied with these controllers? [yes]? Modifying the "transports.ini" file with tu0. You will now be prompted to enter cluster configuration information for the Advanced Server for UNIX. The cluster environment can be configured as follows: none - not using the cluster, the server runs on one node, single - single instance server ( controlled by CAA ), multi - multi instance server, the server runs on all cluster members. Enter the cluster environment type (multi, single or none) [multi]: none Starting the transports... Start: Datalink service controller_01 tu0 The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/knbtcp 32 69 /dev/streams/knbadm 32 70 /dev/streams/knbtcpd 32 71 /dev/streams/netbeui 32 72 /dev/streams/netbeuid 32 73 /dev/streams/nbeadmin 32 74 Microsoft Datalink Driver : Starting dllink ... Datalink driver attached to tu0 at PPA1 dllink: done - Adapter set Start: NetBEUI controller_01 tu0 The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/netbeui 32 72 /dev/streams/netbeuid 32 73 /dev/streams/nbeadmin 32 74 Microsoft NetBEUI Driver : Starting nbelink ... done Start: TCP/IP NetBIOS controller_01 tu0 Starting the TCP/IP NetBIOS service... TCP/IP NetBIOS: Starting knblink ... controller(s) configured as 'tu0' kernel dynamic cache will be enabled lmhosts file use enabled DNS support is enabled The following 2 DNS subdomains have been specified: company.com company1.com Cluster IP address = 10.0.0.6 NBNS Client support enabled, primary server at 10.0.0.4 NBNS Client support enabled, secondary server at 10.0.0.5 Using alias as IP address on interface tu0 Successfully configured with controller(s) 'tu0' TCP/IP NetBIOS name resolver started, pid=1649549 TCP/IP NetBIOS service started Each ASU server must be assigned an ASU server name. ASU server names can be up to 15 alphanumeric characters and can contain the following symbols: ~ ! # $ % ^ & _ ( ) . - Server names cannot include any international characters. If this ASU server will participate in an ASE cluster environment, then the server name that you assign here must also be the name that you assign to the ASE cluster disk service for the ASU server. Enter the name of the server or press Enter to select 'blue': Each server must be given a role in a domain. The possible roles are: Primary domain controller (PDC). There can be only one PDC per domain. The PDC is where the master user account database is stored, which is what the PDC uses to validate network logon requests. Backup domain controller (BDC). There can be many BDCs per domain. The BDC recieves a copy of the user account database from the PDC, which is what it uses to validate network logon requests. A BDC can be promoted to PDC if the PDC is not accessible. Member server is a member of a domain. Member servers do not store user account information and therefore do not validate network logon requests. These servers are dedicated to perform specific tasks such as being file and print servers. Enter role (primary, backup, or member): primary Enter the name of the domain or press Enter to select 'blue.dom': colors.dom That domain name may already be in use. Do you want to select a different domain name [y/n]? n Confirm choices: server name : blue role : primary domain : colors.dom Is this correct [y/n]? y Enter the password for Administrator: Re-enter password: Creating Advanced Server for UNIX accounts database. A clean copy of the SAM database has been written. Configuring registry... reg.ini created successfully Upgrading ... reg.ini upgraded successfully Creating new registry file... processed 935 lines... Registry file created successfully loading /usr/net/servers/lanman/regfiles/perf009.regadm loading /usr/net/servers/lanman/regfiles/users.regadm loading /usr/net/servers/lanman/regfiles/machine.regadm load registry initialization scripts... registry load complete. Upgrading SAM database to support new format The ASU server currently listens for, and responds to, messages sent to these network names: listenname : blue ExtraListenNames: (none) You can define Extra Listen Names for the server to listen for via the Registry parameter ExtraListenNames. Do you want to modify the ExtraListenNames entry [y/n]? y Enter the Extra Listen Names to add to the list. Press RETURN to terminate the list. Enter an Extra Listen Name to add: blue1 Enter an Extra Listen Name to add: blue2 Are you satisfied with this list of ExtraListenNames [y/n]? y These changes will take effect the next time the server is started. There are a number of registry parameters that affect how the Advanced Server creates UNIX user accounts, such as UseNIS, CreateUnixUser, and SpreadUnixHomeDirectory. If you want to change the values of these parameters, please use the regconfig utility to change the parameters now before starting the server. Please see the installation guide for further information. Start the Advanced Server for UNIX [y/n]? y The SERVER service is starting................... The SERVER service was started successfully. Advanced Server for UNIX has the ability to test itself. Would you like to run this test now [y/n]? y (c) Compaq Computer Corp. 2001. All Rights Reserved. Verification #1 via network netbeui Create Share netbeui ...Succeeded Grant user access to share ...Succeeded Attempting connection to \\BLUE\netbeui ...Succeeded List File ...Succeeded Create File ...Succeeded Write data to file ...Succeeded Close data file ...Succeeded Open file for reading ...Succeeded Read data from file ...Succeeded Data Verification ...Succeeded Close data file ...Succeeded Tree Disconnect ...Succeeded Revoke user access to share ...Succeeded Remove share netbeui ...Succeeded Network netbeui complete. Verification #1 via network knbtcp Create Share knbtcp ...Succeeded Grant user access to share ...Succeeded Attempting connection to \\BLUE\knbtcp ...Succeeded List File ...Succeeded Create File ...Succeeded Write data to file ...Succeeded Close data file ...Succeeded Open file for reading ...Succeeded Read data from file ...Succeeded Data Verification ...Succeeded Close data file ...Succeeded Tree Disconnect ...Succeeded Revoke user access to share ...Succeeded Remove share knbtcp ...Succeeded Network knbtcp complete.
ASU servers configured in none mode determine their configuration by
using a shared
lanman.ini
file that the
asusetup
utility creates.
The
[ cluster ]
section in the
lanman.ini
file contains the
cluster
attribute that specifies
the ASU server mode and the
clusteralias
attribute that
specifies the name of the cluster alias.
Example 6-8
is a sample
lanman.ini
file for ASU servers configured to operate in none mode in a TruCluster environment.
Example 6-8: Sample None Mode lanman.ini File
[ cluster ] cluster=none [ server ] listenname=blue srvservices=alerter,netlogon,browser [ workstation ] domain=colors.dom [ lmxserver ] LMCompatibilityLevel=0 secsources=Spooler;Security Account Manager;SC Manager;LSA;Security syssources=workstation;UPS;Srv;Service Control Manager;server;SAM;Rdr; Print;NetLogon;eventlog;Browser;Alerter;System appsources=Replicator;Perfmon;Perflib;Application
6.1.3.2 None transports.ini File
ASU servers configured in none mode determine their network-specific
configuration by using a shared
transports.ini
file that
the
asusetup
utility creates.
The
[ member ]
section in the
transports.ini
file contains
member_nn=ASU_server_name
attributes that uniquely identify each ASU server in the TruCluster
environment.
This identification is necessary if clients connect to ASU shares
using the ASU server name instead of the cluster alias.
Example 6-9
is a sample
/usr/net/servers/lanman/transports.ini
file for ASU servers configured to operate in none mode in a TruCluster
environment.
Example 6-9: Sample None Mode transports.ini File
[ tcpip ] clusteraddr=sam controller_01=tu0 uselmhosts=yes lmhostsfile=/usr/net/servers/lanman/datafiles/lmhosts enablenbns=yes nbnsservaddr=10.0.0.4 nbnsservaddr2=10.0.0.5 enabledns=yes dnssubdomains=company.com,company1.com [ member ] member_01=blue.company.com,blue [ netbeui ] controller_01=tu0
6.1.3.3 Managing ASU Servers Configured in None Mode
You use the ASU
net
commands to manage an ASU server
configured in none mode in a TruCluster environment.
See
Appendix D
for more information about
net
commands.
6.2 ASU Licensing in a TruCluster Environment
You configure ASU licensing in a TruCluster environment as follows:
If the ASU server is configured in none mode, you must have a separate ASU license PAK installed on each cluster member that is running the ASU server.
If the ASU server is configured in single mode (CAA), you can install the same ASU license PAK on all cluster members to which the ASU server can failover because the ASU server will be running only on one cluster member at a time.
If the ASU server is configured in multi mode, you can configure the ASU server to use cluster-wide licensing. When using cluster-wide licensing, you install the ASU license PAKs on each cluster member; the ASU server will issue the licenses and keep track of the connections to the cluster. For example, if you purchase a 100 user client PAK and you have a three member cluster, install the PAK on all three members. The ASU server will ensure that only 100 clients (plus two free) can connect to the cluster.
Follow these steps to use cluster-wide licensing:
On a cluster member, enter the
asustop
command to stop all instances of the ASU server in the cluster.
The
asustop
command stops the ASU server on all cluster members.
On a cluster member, enter the following command to enable
the
UseClusterLicensing
registry entry.
The backslash (
\ ) at the end a line indicates continuation.
Enter the entire command, then
press the Enter key.
# regconfig SYSTEM/CurrentControlSet/Services/\ AdvancedServer/Parameters UseClusterLicensing REG_DWORD 1
On each cluster member on which the ASU server is installed, enter the following command to restart the ASU server:
#
net start server
Install the ASU license PAKs on each cluster member running the ASU server.