6    TruCluster 環境での ASU の構成

TruCluster 環境に 2 つ以上の ASU サーバを構成することにより,ASU ディスク共有,プリンタ共有,およびサービスを高可用に構成することができます。TruCluster 環境は,TruCluster ソフトウェアを実行する AlphaServer システムをグループ化したものです。TruCluster ソフトウェアについての詳細は,TruCluster Server の『クラスタ管理ガイド』を参照してください。

この章では,TruCluster Server バージョン 5.x 以降の環境で ASU サーバを構成する方法について説明します。

TruCluster バージョン 1.x (ASE (Available Server Environment)) 環境で ASU サーバを構成する方法については,付録 F を参照してください。

6.1    TruCluster Server バージョン 5.x 環境での ASU サーバのモード

ASU サーバは,TruCluster Server バージョン 5.x 環境において,次のいずれかのモードで動作するように構成することができます。

6.1.1    マルチ・モードでの ASU サーバの構成

クラスタ・メンバ上で asusetup ユーティリティを実行する必要があります。asusetup ユーティリティを実行すると,1.4 節で説明している ASU サーバのネットワーク情報や一般情報,および次の TruCluster 情報の入力が求められます。

asusetup ユーティリティを実行するには,次のように入力します。

# /usr/sbin/asusetup

例 6-1 は,マルチ・モードで動作するように構成された ASU サーバの場合の asusetup からの出力例を示しています。

例 6-1:  マルチ・モードの場合の asusetup からの出力例

       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    マルチ・モードでの追加の ASU サーバの構成

ASU サーバをマルチ・モードで実行する各クラスタ・メンバ上で asusetup ユーティリティを実行する必要があります。任意のクラスタ・メンバ上で asusetup ユーティリティを実行すると,TruCluster 環境内にある ASU サーバのすべてのインスタンスが停止します。

asusetup ユーティリティにより,ユーザが使用する省略時の値が提供されます。いくつかの省略時の値を変更する必要がある場合,クラスタ環境のタイプ (multi),クラスタ別名,および ASU の役割については,省略時の値を変更してはなりません。これらの値は,TruCluster 環境でマルチ・モードで構成されたすべての ASU サーバについて同じでなければなりません。

6.1.1.2    マルチの lanman.ini ファイル

マルチ・モードで構成された ASU サーバは,asusetup ユーティリティが作成する共有 lanman.ini ファイルを使用して,構成を決定します。

lanman.ini ファイルの [ cluster ] セクションには,ASU サーバ・モードを指定する cluster 属性と,クラスタ別名の名前を指定する clusteralias 属性が含まれています。

例 6-2 は,TruCluster 環境でマルチ・モードで動作するように構成された ASU サーバのための lanman.ini ファイルのサンプルです。

例 6-2:  マルチ・モードの lanman.ini ファイルのサンプル

[ 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    マルチの transports.ini ファイル

マルチ・モードで構成された ASU サーバは,asusetup ユーティリティが作成する共有 transports.ini ファイルを使用して,ネットワーク固有の構成を決定します。

transports.ini ファイルの [ member ] セクションには,TruCluster 環境で ASU サーバを実行している各クラスタ・メンバを一意に識別する member_nn=ASU_server_name 属性が含まれています。この識別は,TruCluster ソフトウェアがクライアント接続のローテーションを行ったり,障害の発生したクラスタ・メンバからクライアント接続を再分散するために必要です。そのため,クライアントは,クラスタ別名の代わりに ASU サーバ名を使用して ASU 共有に接続することができます。

[ tcpip ] セクションには,クラスタ別名の DNS 名または TCP/IP アドレスのいずれかを指定する clusteraddr 属性が含まれています。

例 6-3 は,TruCluster 環境でマルチ・モードで動作するように構成された ASU サーバのための /usr/net/servers/lanman/transports.ini ファイルのサンプルです。

例 6-3:  マルチ・モードの transports.ini ファイルのサンプル

[ 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    マルチ・モードで構成された ASU サーバの管理

ASU サーバをマルチ・モードで実行しているクラスタ・メンバをリブートしたりオフラインにしても,TruCluster 環境で実行されている他の ASU サーバには影響を及ぼしません。

TruCluster 環境でマルチ・モードで構成されている ASU サーバを管理するには,ASU net コマンドを使用します。net コマンドについての詳細は,付録 D を参照してください。表 6-1 に,TruCluster 環境で異なった動作をする net コマンドを示しています。

TruCluster Server の『クラスタ管理ガイド』に記載されているコマンドやユーティリティを使用して,クラスタ・メンバ,および,負荷分散ポリシなど ASU サーバのいくつかの構成を管理します。詳細については TruCluster Server の『クラスタ管理ガイド』を参照してください。

表 6-1:  クラスタ内で異なる動作をする net コマンド

コマンド 説明

net file

TruCluster 環境内のすべてのオープン・ファイルを表示する。

net send

コマンドを実行したクラスタ・メンバに接続されているユーザにメッセージを送信する。

net session

TruCluster 環境内のすべてのクライアント・セッションを表示する。

net statistics server, net status, および net config

コマンドを実行したクラスタ・メンバについてカウンタを表示する。

net start <service>

指定されたサービスをすべての ASU サーバ上で開始する。たとえば,1 つのクラスタ・メンバ上で net start browser を入力すると,すべての ASU サーバ上でブラウザ・サービスが開始される。ASU サービスの一覧については,1.6 節を参照。

net start server コマンドは例外。このコマンドでは,コマンドを入力したクラスタ・メンバ上でのみ ASU サーバ・サービスが開始される。

net stop <service>

指定されたサービスをすべての ASU サーバ上で停止する。たとえば,1 つのクラスタ・メンバ上で net stop browser を入力すると,すべての ASU サーバ上でブラウザ・サービスが停止する。ASU サービスの一覧については,1.6 節を参照。

net stop server コマンドは例外。このコマンドは,コマンドを入力したクラスタ・メンバ上でのみ ASU サーバ・サービスを停止する。

すべてのクラスタ・メンバ上の ASU サーバを停止するには,各クラスタ・メンバ上で asustop コマンドを入力する。

net pause <service>

指定されたサービスをすべての ASU サーバ上で一時停止する。たとえば,1 つのクラスタ・メンバ上で net pause browser を入力すると,すべての ASU サーバ上のブラウザ・サービスが一時停止される。ASU サービスの一覧については,1.6 節を参照。

net continue <service>

指定されたサービスをすべての ASU サーバ上で継続する。たとえば,1 つのクラスタ・メンバ上で net continue browser を入力すると,すべての ASU サーバ上のブラウザ・サービスが継続される。ASU サービスの一覧については,1.6 節を参照。

6.1.2    シングル・モードでの ASU サーバの構成

ASU サーバをシングル・モードで実行する各クラスタ・メンバ上で asusetup ユーティリティを実行する必要があります。asusetup ユーティリティを実行すると,1.4 節で説明している ASU サーバのネットワーク情報や一般情報,および次の TruCluster 情報の入力が求められます。

asusetup ユーティリティを実行するには,次のように入力します。

# /usr/sbin/asusetup

例 6-4 は,シングル・モードで動作するように構成された ASU サーバの場合の asusetup からの出力例を示しています。

例 6-4:  シングル・モードの場合の asusetup からの出力例

       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    シングル・モードでの追加の ASU サーバの構成

ASU サーバがすでに TruCluster クラスタ内で実行されているときに,クラスタ・メンバで追加の ASU サーバを構成したい場合は,そのクラスタ・メンバで asusetup ユーティリティを実行する必要があります。

asusetup ユーティリティにより,ユーザが使用する省略時の値が提供されます。いくつかの省略時の値を変更する必要がある場合,クラスタ環境のタイプ (single),クラスタ別名,および ASU の役割については,省略時の値を変更してはなりません。これらの値は,TruCluster 環境でシングル・モードで構成されたすべての ASU サーバについて同じでなければなりません。

6.1.2.2    シングルの lanman.ini ファイル

シングル・モードで構成された ASU サーバは,asusetup ユーティリティが作成する共有 lanman.ini ファイルを使用して,構成を決定します。

lanman.ini ファイルの [ cluster ] セクションには,ASU サーバ・モードを指定する cluster 属性と,クラスタ別名の名前を指定する clusteralias 属性が含まれています。

例 6-5 は,TruCluster 環境でシングル・モードで動作するように構成された ASU サーバのための lanman.ini ファイルのサンプルです。

例 6-5:  シングル・モードの lanman.ini ファイルのサンプル

[ 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    シングルの transports.ini ファイル

シングル・モードで構成された ASU サーバは,asusetup ユーティリティが作成する共有 transports.ini ファイルを使用して,ネットワーク固有の構成を決定します。

transports.ini ファイルの [ member ] セクションには,TruCluster 環境で ASU サーバを実行している各メンバ・サーバを一意に識別する member_nn=ASU_server_name 属性が含まれています。この識別は,TruCluster ソフトウェアが (必要な場合に) ASU サーバを起動する代替クラスタ・メンバを識別するために必要です。

[ tcpip ] セクションには,クラスタ別名の DNS 名または TCP/IP アドレスのいずれかを指定する clusteraddr 属性が含まれています。

例 6-6 は,TruCluster 環境でシングル・モードで動作するように構成された ASU サーバのための /usr/net/servers/lanman/transports.ini ファイルのサンプルです。

例 6-6:  シングル・モードの transports.ini ファイルのサンプル

[ 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    シングル・モードで構成された ASU サーバの管理

TruCluster 環境でシングル・モードで構成されている ASU サーバを管理するには,ASU net コマンドを使用します。net コマンドは,ASU サーバを実行しているシステム上でのみ動作します。net コマンドについての詳細は,付録 D を参照してください。

TruCluster Server の『クラスタ管理ガイド』に記載されているコマンドやユーティリティを使用して,クラスタ・メンバ,および代替 ASU サーバの指定など ASU サーバのいくつかのアスペクトを管理します。詳細については TruCluster Server の『クラスタ管理ガイド』を参照してください。

注意

ASU をシングル・モード (CAA) で稼働するように構成すると,ASU サーバは,caa_start asu コマンドで起動され,caa_stop asuコマンドで停止します。

システムのシャットダウン時に ASU サーバが実行されていなければ,ブート・プロセス中に起動されません。caa_start asu コマンドを発行して,ASU サーバを起動する必要があります。

詳細については,『クラスタ管理ガイド』を参照してください。

6.1.3    none (クラスタに参加しない) モードでの ASU サーバの構成

ASU サーバを none (クラスタに参加しない) モードで実行する各クラスタ・メンバ上で asusetup ユーティリティを実行する必要があります。asusetup ユーティリティを実行すると,1.4 節で説明している ASU サーバのネットワーク情報や一般情報,および次の TruCluster 情報の入力が求められます。

asusetup ユーティリティを実行するには,次のように入力します。

# /usr/sbin/asusetup

例 6-7 は,none モードで動作するように構成された ASU サーバの場合の asusetup からの出力例を示しています。

例 6-7:  none モードの場合の asusetup からの出力例

       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.
 
 

6.1.3.1    none モードの lanman.ini ファイル

none モードで構成された ASU サーバは,asusetup ユーティリティが作成する共有 lanman.ini ファイルを使用して,構成を決定します。

lanman.ini ファイルの [ cluster ] セクションには,ASU サーバ・モードを指定する cluster 属性と,クラスタ別名の名前を指定する clusteralias 属性が含まれています。

例 6-8 は,TruCluster 環境で none モードで動作するように構成された ASU サーバのための lanman.ini ファイルのサンプルです。

例 6-8:  none モードの lanman.ini ファイルのサンプル

[ 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 ファイル

none モードで構成された ASU サーバは,asusetup ユーティリティが作成する共有 transports.ini ファイルを使用して,ネットワーク固有の構成を決定します。

transports.ini ファイルの [ member ] セクションには,TruCluster 環境で各 ASU サーバを一意に識別する member_nn=ASU_server_name 属性が含まれています。この識別は,クライアントが,クラスタ別名ではなく ASU サーバ名を使用して,ASU 共有に接続する場合に必要です。

例 6-9 は,TruCluster 環境で none モードで動作するように構成された ASU サーバのための /usr/net/servers/lanman/transports.ini ファイルのサンプルです。

例 6-9:  none モードの transports.ini ファイルのサンプル

[ 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    none モードで構成された ASU サーバの管理

TruCluster 環境で none モードで構成されている ASU サーバを管理するには,ASU net コマンドを使用します。net コマンドについての詳細は,付録 D を参照してください。

6.2    TruCluster 環境での ASU のライセンス

TruCluster 環境での ASU のライセンスは,次のように構成します。