日本-日本語 |
|
|
|
OpenVMS マニュアル |
|
HP OpenVMS
|
目次 | 索引 |
8.4.1 準備 |
通常,既存のクラスタの構成を変更するために,クラスタ構成コマンド・プロシージャを使用する場合は,その前に多くの作業を行う必要があります。
表 8-9 では,複数の典型的な構成の変更を示し,その変更に必要な手順も示しています。
作業 | 手順 |
---|---|
サテライト・ノードを追加する。 | これらの操作は,クラスタ・ブート・サーバとして有効にするコンピュータで実行する。
|
サテライト・ノードを含むように,既存の CI または DSSI クラスタを変更する。 |
すべてのコンピュータで LAN (イーサネットまたは FDDI) を介したクラスタ通信を有効にし,1 台以上のコンピュータをブート・サーバとして有効にするには,以下の操作を実行する。
|
CI および DSSI インターコネクトを含むように,既存の LAN ベースのクラスタを変更する。 |
ここで説明する操作を実行する前に,新しい構成に含む予定のコンピュータおよび HSC サブシステムまたは RF ディスクが正しくインストールされ,正しく動作するかどうか確認しなければならない。
既存の LAN ベースのクラスタ構成に CI インターコネクトおよび DSSI インターコネクトを追加するために使用する方法は,現在のブート・サーバが CI または DSSI コンピュータとして構成可能であるかどうかに応じて異なる。 注意: 以下の手順では,サテライト・ルートを格納しているシステム・ディスクが HSC ディスク (CI 構成の場合) または RF ディスク (DSSI 構成の場合) に存在するものと仮定している。
|
スタンドアロン・コンピュータを OpenVMS Cluster コンピュータに変換する。 |
スタンドアロン・コンピュータで CLUSTER_CONFIG_LAN.COM または CLUSTER_CONFIG.COM を実行して,以下のいずれかの操作を実行する。
例 8-13 を参照。この例では,スタンドアロン・コンピュータ PLUTO で CLUSTER_CONFIG.COM を使用して,PLUTO をクラスタ・ブート・サーバに変換する方法を示している。 クラスタで DECdtm サービスを使用する場合は,コンピュータをクラスタに追加するときに,そのコンピュータのトランザクション・ログを作成しなければならない。この操作方法については,『OpenVMS システム管理者マニュアル』の DECdtm サービスに関する章を参照。 |
ディスク・サービス機能またはテープ・サービス機能を有効または無効に設定する。 | CLUSTER_CONFIG_LAN.COM または CLUSTER_CONFIG.COM を起動して,ディスク・サービス機能またはテープ・サービス機能を有効または無効に設定した後, REBOOT オプションを使用して AUTOGEN を実行することで,ローカル・コンピュータをリブートする ( 第 8.6.1 項 を参照)。 |
注意: クラスタ構成コマンド・プロシージャで MODPARAMS.DAT の値を設定または変更すると,新しい値は常にファイルの最後に追加されるため,以前の値は無効になります。場合によっては,ファイルを編集し,以前の値を指定している行を削除することもあります。
例 8-7 から 例 8-13 までは,CLUSTER_CONFIG_LAN.COM を使用して以下の操作を実行する方法を示しています。
8.4.2 例
例 8-7 ローカル・コンピュータをディスク・サーバとして有効にするための会話型 CLUSTER_CONFIG_LAN.COM セッションの例 |
---|
$ @CLUSTER_CONFIG_LAN.COM Cluster/IPCI Configuration Procedure CLUSTER_CONFIG_LAN Version V2.84 Executing on an IA64 System DECnet-Plus is installed on this node. IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. TCP/IP is installed and running on this node. Enter a "?" for help at any prompt. If you are familiar with the execution of this procedure, you may want to mute extra notes and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". BHAGAT is an IA64 system and currently a member of a cluster so the following functions can be performed: MAIN Menu 1. ADD an IA64 node to the cluster. 2. REMOVE a node from the cluster. 3. CHANGE a cluster member's characteristics. 4. CREATE a duplicate system disk for BHAGAT. 5. MAKE a directory structure for a new root on a system disk. 6. DELETE a root from a system disk. 7. EXIT from this procedure. Enter choice [7]: 3 CHANGE Menu 1. Enable BHAGAT as a boot server. 2. Disable BHAGAT as a boot server. 3. Enable a quorum disk for BHAGAT. 4. Disable a quorum disk for BHAGAT. 5. Enable BHAGAT as a disk server. 6. Disable BHAGAT as a disk server. 7. Change BHAGAT's ALLOCLASS value. 8. Enable BHAGAT as a tape server. 9. Disable BHAGAT as a tape server. 10. Change BHAGAT's TAPE_ALLOCLASS value. 11. Change an IA64 satellite node's LAN adapter hardware address. 12. Enable Cluster Communication using IP on BHAGAT. 13. Disable Cluster Communication using IP on BHAGAT. 14. Change BHAGAT's shared SCSI port allocation class value. 15. Reset an IA64 satellite node's boot environment file protections. 16. Return to MAIN menu. Enter choice [16]: 5 Enter a value for BHAGAT's ALLOCLASS parameter [1]: The configuration procedure has completed successfully. BHAGAT has been enabled as a disk server. In MODPARAMS.DAT: MSCP_LOAD has been set to 1 MSCP_SERVE_ALL has been set to 2 Please run AUTOGEN to reboot BHAGAT: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT If you have changed BHAGAT's ALLOCLASS value, you must reconfigure the cluster, using the procedure described in the OpenVMS Cluster Systems manual. |
例 8-8 ローカル・コンピュータの ALLOCLASS 値を変更するための会話型 CLUSTER_CONFIG_LAN.COM セッションの例 |
---|
$ @CLUSTER_CONFIG_LAN.COM Cluster/IPCI Configuration Procedure CLUSTER_CONFIG_LAN Version V2.84 Executing on an IA64 System DECnet-Plus is installed on this node. IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. TCP/IP is installed and running on this node. Enter a "?" for help at any prompt. If you are familiar with the execution of this procedure, you may want to mute extra notes and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". BHAGAT is an IA64 system and currently a member of a cluster so the following functions can be performed: MAIN Menu 1. ADD an IA64 node to the cluster. 2. REMOVE a node from the cluster. 3. CHANGE a cluster member's characteristics. 4. CREATE a duplicate system disk for BHAGAT. 5. MAKE a directory structure for a new root on a system disk. 6. DELETE a root from a system disk. 7. EXIT from this procedure. Enter choice [7]: 3 CHANGE Menu 1. Enable BHAGAT as a boot server. 2. Disable BHAGAT as a boot server. 3. Enable a quorum disk for BHAGAT. 4. Disable a quorum disk for BHAGAT. 5. Enable BHAGAT as a disk server. 6. Disable BHAGAT as a disk server. 7. Change BHAGAT's ALLOCLASS value. 8. Enable BHAGAT as a tape server. 9. Disable BHAGAT as a tape server. 10. Change BHAGAT's TAPE_ALLOCLASS value. 11. Change an IA64 satellite node's LAN adapter hardware address. 12. Enable Cluster Communication using IP on BHAGAT. 13. Disable Cluster Communication using IP on BHAGAT. 14. Change BHAGAT's shared SCSI port allocation class value. 15. Reset an IA64 satellite node's boot environment file protections. 16. Return to MAIN menu. Enter choice [16]: 7 Enter a value for BHAGAT's ALLOCLASS parameter [1]: 2 The configuration procedure has completed successfully. Since you have changed BHAGAT's ALLOCLASS value, you must reconfigure the cluster, using the procedure described in the "OpenVMS Cluster Systems" manual. This includes running AUTOGEN for BHAGAT as shown below, before rebooting the cluster: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT If you have changed BHAGAT's ALLOCLASS value, you must reconfigure the cluster, using the procedure described in the OpenVMS Cluster Systems manual. |
例 8-9 ローカル・コンピュータをブート・サーバとして有効にするための会話型 CLUSTER_CONFIG_LAN.COM セッションの例 |
---|
$ @CLUSTER_CONFIG_LAN.COM Cluster/IPCI Configuration Procedure CLUSTER_CONFIG_LAN Version V2.84 Executing on an IA64 System DECnet-Plus is installed on this node. IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. TCP/IP is installed and running on this node. Enter a "?" for help at any prompt. If you are familiar with the execution of this procedure, you may want to mute extra notes and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". BHAGAT is an IA64 system and currently a member of a cluster so the following functions can be performed: MAIN Menu 1. ADD an IA64 node to the cluster. 2. REMOVE a node from the cluster. 3. CHANGE a cluster member's characteristics. 4. CREATE a duplicate system disk for BHAGAT. 5. MAKE a directory structure for a new root on a system disk. 6. DELETE a root from a system disk. 7. EXIT from this procedure. Enter choice [7]: 3 CHANGE Menu 1. Enable BHAGAT as a boot server. 2. Disable BHAGAT as a boot server. 3. Enable a quorum disk for BHAGAT. 4. Disable a quorum disk for BHAGAT. 5. Enable BHAGAT as a disk server. 6. Disable BHAGAT as a disk server. 7. Change BHAGAT's ALLOCLASS value. 8. Enable BHAGAT as a tape server. 9. Disable BHAGAT as a tape server. 10. Change BHAGAT's TAPE_ALLOCLASS value. 11. Change an IA64 satellite node's LAN adapter hardware address. 12. Enable Cluster Communication using IP on BHAGAT. 13. Disable Cluster Communication using IP on BHAGAT. 14. Change BHAGAT's shared SCSI port allocation class value. 15. Reset an IA64 satellite node's boot environment file protections. 16. Return to MAIN menu. Enter choice [16]: 1 Enter a value for BHAGAT's ALLOCLASS parameter [1]: [Return] The configuration procedure has completed successfully. BHAGAT has been enabled as a boot server. Disk serving and LAN capabilities are enabled automatically. If BHAGAT was not previously set up as a disk server, please run AUTOGEN to reboot BHAGAT: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT If you have changed BHAGAT's ALLOCLASS value, you must reconfigure the cluster, using the procedure described in the OpenVMS Cluster Systems manual. |
例 8-10 サテライトのハードウェア・アドレスを変更するための会話型 CLUSTER_CONFIG_LAN.COM セッションの例 |
---|
$ @CLUSTER_CONFIG_LAN.COM Cluster/IPCI Configuration Procedure CLUSTER_CONFIG_LAN Version V2.84 Executing on an IA64 System DECnet-Plus is installed on this node. IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. TCP/IP is installed and running on this node. Enter a "?" for help at any prompt. If you are familiar with the execution of this procedure, you may want to mute extra notes and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". BHAGAT is an IA64 system and currently a member of a cluster so the following functions can be performed: MAIN Menu 1. ADD an IA64 node to the cluster. 2. REMOVE a node from the cluster. 3. CHANGE a cluster member's characteristics. 4. CREATE a duplicate system disk for BHAGAT. 5. MAKE a directory structure for a new root on a system disk. 6. DELETE a root from a system disk. 7. EXIT from this procedure. Enter choice [7]: 3 CHANGE Menu 1. Enable BHAGAT as a boot server. 2. Disable BHAGAT as a boot server. 3. Enable a quorum disk for BHAGAT. 4. Disable a quorum disk for BHAGAT. 5. Enable BHAGAT as a disk server. 6. Disable BHAGAT as a disk server. 7. Change BHAGAT's ALLOCLASS value. 8. Enable BHAGAT as a tape server. 9. Disable BHAGAT as a tape server. 10. Change BHAGAT's TAPE_ALLOCLASS value. 11. Change an IA64 satellite node's LAN adapter hardware address. 12. Enable Cluster Communication using IP on BHAGAT. 13. Disable Cluster Communication using IP on BHAGAT. 14. Change BHAGAT's shared SCSI port allocation class value. 15. Reset an IA64 satellite node's boot environment file protections. 16. Return to MAIN menu. Enter choice [16]: 11 What is the node's SCS node name? gomthi Note: The current hardware address entry for GOMTHI is 00-30-6E-4C-BB-1A. What is GOMTHI's new LAN adapter hardware address? 00-30-6E-4C-BA-2A The configuration procedure has completed successfully. |
例 8-11 ローカル・コンピュータをテープ・サーバとして有効にするための会話型 CLUSTER_CONFIG_LAN.COM セッションの例 |
---|
$ @CLUSTER_CONFIG_LAN.COM Cluster/IPCI Configuration Procedure CLUSTER_CONFIG_LAN Version V2.84 Executing on an IA64 System DECnet-Plus is installed on this node. IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. TCP/IP is installed and running on this node. Enter a "?" for help at any prompt. If you are familiar with the execution of this procedure, you may want to mute extra notes and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". BHAGAT is an IA64 system and currently a member of a cluster so the following functions can be performed: MAIN Menu 1. ADD an IA64 node to the cluster. 2. REMOVE a node from the cluster. 3. CHANGE a cluster member's characteristics. 4. CREATE a duplicate system disk for BHAGAT. 5. MAKE a directory structure for a new root on a system disk. 6. DELETE a root from a system disk. 7. EXIT from this procedure. Enter choice [7]: 3 CHANGE Menu 1. Enable BHAGAT as a boot server. 2. Disable BHAGAT as a boot server. 3. Enable a quorum disk for BHAGAT. 4. Disable a quorum disk for BHAGAT. 5. Enable BHAGAT as a disk server. 6. Disable BHAGAT as a disk server. 7. Change BHAGAT's ALLOCLASS value. 8. Enable BHAGAT as a tape server. 9. Disable BHAGAT as a tape server. 10. Change BHAGAT's TAPE_ALLOCLASS value. 11. Change an IA64 satellite node's LAN adapter hardware address. 12. Enable Cluster Communication using IP on BHAGAT. 13. Disable Cluster Communication using IP on BHAGAT. 14. Change BHAGAT's shared SCSI port allocation class value. 15. Reset an IA64 satellite node's boot environment file protections. 16. Return to MAIN menu. Enter choice [16]: 8 Enter a value for BHAGAT's TAPE_ALLOCLASS parameter [0]: [Return] Should BHAGAT serve any tapes it sees, local and remote [Y]? [Return] BHAGAT has been enabled as a tape server. In MODPARAMS.DAT, TMSCP_LOAD has been set to 1 TMSCP_SERVE_ALL has been set to 1 Please run AUTOGEN to reboot BHAGAT: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT If you have changed BHAGAT's TAPE_ALLOCLASS value, you must reconfigure the cluster, using the procedure described in the "OpenVMS Cluster Systems" manual. |
例 8-12 ローカル・コンピュータの TAPE_ALLOCLASS 値を変更するための会話型 CLUSTER_CONFIG_LAN.COM セッションの例 |
---|
$ @CLUSTER_CONFIG_LAN.COM Cluster/IPCI Configuration Procedure CLUSTER_CONFIG_LAN Version V2.84 Executing on an IA64 System DECnet-Plus is installed on this node. IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. TCP/IP is installed and running on this node. Enter a "?" for help at any prompt. If you are familiar with the execution of this procedure, you may want to mute extra notes and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". BHAGAT is an IA64 system and currently a member of a cluster so the following functions can be performed: MAIN Menu 1. ADD an IA64 node to the cluster. 2. REMOVE a node from the cluster. 3. CHANGE a cluster member's characteristics. 4. CREATE a duplicate system disk for BHAGAT. 5. MAKE a directory structure for a new root on a system disk. 6. DELETE a root from a system disk. 7. EXIT from this procedure. Enter choice [7]: 3 CHANGE Menu 1. Enable BHAGAT as a boot server. 2. Disable BHAGAT as a boot server. 3. Enable a quorum disk for BHAGAT. 4. Disable a quorum disk for BHAGAT. 5. Enable BHAGAT as a disk server. 6. Disable BHAGAT as a disk server. 7. Change BHAGAT's ALLOCLASS value. 8. Enable BHAGAT as a tape server. 9. Disable BHAGAT as a tape server. 10. Change BHAGAT's TAPE_ALLOCLASS value. 11. Change an IA64 satellite node's LAN adapter hardware address. 12. Enable Cluster Communication using IP on BHAGAT. 13. Disable Cluster Communication using IP on BHAGAT. 14. Change BHAGAT's shared SCSI port allocation class value. 15. Reset an IA64 satellite node's boot environment file protections. 16. Return to MAIN menu. Enter choice [16]: 10 Enter a value for BHAGAT's TAPE_ALLOCLASS parameter [0]: 1 If you have changed BHAGAT's TAPE_ALLOCLASS value, you must reconfigure the cluster, using the procedure described in the "OpenVMS Cluster Systems" Manual. This includes running AUTOGEN for BHAGAT as shown below, before rebooting the cluster: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT If you have changed BHAGAT's TAPE_ALLOCLASS value, you must reconfigure the cluster, using the procedure described in the OpenVMS Cluster Systems manual. |
例 8-13 スタンドアロン・コンピュータをクラスタ・ブート・サーバに変換するための会話型 CLUSTER_CONFIG_LAN.COM セッションの例 |
---|
$ @CLUSTER_CONFIG_LAN.COM IA64 platform support is in procedure CLUSTER_CONFIG_LAN.COM. The currently running procedure, CLUSTER_CONFIG.COM, will call it for you. Cluster/IPCI Configuration Procedure CLUSTER_CONFIG_LAN Version V2.84 Executing on an IA64 System DECnet-Plus is installed on this node. IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. TCP/IP is installed and running on this node. Enter a "?" for help at any prompt. If you are familiar with the execution of this procedure, you may want to mute extra notes and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". This IA64 node is not currently a cluster member. MAIN Menu 1. ADD MOON to existing cluster, or form a new cluster. 2. MAKE a directory structure for a new root on a system disk. 3. DELETE a root from a system disk. 4. EXIT from this procedure. Enter choice [4]: 1 Is the node to be a clustered node with a shared SCSI/FIBRE-CHANNEL bus (Y/N)? N What is the node's SCS node name? moon DECnet is running on this node. Even though you are configuring a LAN- based cluster, the DECnet database will provide some information and may be updated. Do you want to define a DECnet synonym [Y]? N IA64 node, using LAN for cluster communications. PEDRIVER will be loaded. No other cluster interconnects are supported for IA64 nodes. Enter this cluster's group number: 123 Enter this cluster's password: Re-enter this cluster's password for verification: Will MOON be a boot server [Y]? [Return] TCP/IP BOOTP and TFTP services must be enabled on IA64 boot nodes. Use SYS$MANAGER:TCPIP$CONFIG.COM on MOON to enable BOOTP and TFTP services after MOON has booted into the cluster. Enter a value for MOON's ALLOCLASS parameter [0]:[Return] Does this cluster contain a quorum disk [N]? [Return] The EXPECTED_VOTES system parameter of members of a cluster indicates the total number of votes present when all cluster members are booted, and is used to determine the minimum number of votes (QUORUM) needed for cluster operation. EXPECTED_VOTES value for this cluster: 1 Warning: Setting EXPECTED_VOTES to 1 allows this node to boot without being able to see any other nodes in the cluster. If there is another instance of the cluster in existence that is unreachable via SCS but shares common drives (such as a Fibrechannel fabric) this may result in severe disk corruption. Do you wish to re-enter the value of EXPECTED_VOTES [Y]? N The use of a quorum disk is recommended for small clusters to maintain cluster quorum if cluster availability with only a single cluster node is a requirement. For complete instructions, check the section on configuring a cluster in the "OpenVMS Cluster Systems" manual. WARNING: MOON will be a voting cluster member. EXPECTED_VOTES for this and every other cluster member should be adjusted at a convenient time before a reboot. For complete instructions, check the section on configuring a cluster in the "OpenVMS Cluster Systems" manual. Execute AUTOGEN to compute the SYSGEN parameters for your configuration and reboot MOON with the new parameters. This is necessary before MOON can become a cluster member. Do you want to run AUTOGEN now [Y]? [Return] Running AUTOGEN -- Please wait. %AUTOGEN-I-BEGIN, GETDATA phase is beginning. . . . |
目次 | 索引 |
|