本ページの製品は2024年4月1日より、エフサステクノロジーズ株式会社に統合となり、順次、切り替えを実施してまいります。一部、富士通表記が混在することがありますので、ご了承ください。

MetroCluster マニュアル ( CA08871-401 )

to English version

Tiebreaker 1.6のインストール

MetroCluster構成を監視するには、ホストLinuxオペレーティングシステムでTiebreaker 1.6の新規インストールまたはアップグレードを実行します。

タスク概要

ストレージシステムでONTAP 9.12.1以降が実行されている必要があります。
MetroCluster Tiebreakerのインストールは、Tiebreakerのインストール、テーブルやユーザーの作成、ユーザーパスワードの設定を行える十分な管理者権限が付与されたroot以外のユーザーとして実行できます。

手順

ダウンロードサイトからMetroCluster Tiebreaker 1.6ソフトウェアをダウンロードします。
rootユーザーとしてホストにログインします。

アップグレードを実行する場合は、実行しているTiebreakerのバージョンを確認します。

次の例はTiebreaker 1.5を示しています。

[root@mcctb ~] # fujitsu-metrocluster-tiebreaker-software-cli
Fujitsu MetroCluster Tiebreaker :> version show
Fujitsu MetroCluster Tiebreaker 1.5: Sun Mar 13 09:59:02 IST 2022
Fujitsu MetroCluster Tiebreaker :> exit

Tiebreakerソフトウェアをインストールまたはアップグレードします。

Tiebreaker 1.6のインストール

Tiebreaker 1.6を新規にインストールする場合は、次の手順を実行します。

手順

[root@mcctb ~] #プロンプトで次のコマンドを実行して、インストールを開始します。

sh MetroClusterTiebreakerInstall-1.6

インストールが完了すると、次の出力が表示されます。

Extracting the MetroCluster Tiebreaker installation/upgrade archive
Install digest hash is Ok
Performing the MetroCluster Tiebreaker code signature check
Install code signature is Ok
Enter unix user account to use for the installation:
mcctbadminuser
Unix user account "mcctbadminuser" doesn't exist. Do you wish to create "mcctbadminuser" user account? [Y/N]: y
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.
Creating mailbox file: File exists
Unix account "mcctbadminuser" created.
Changing password for user mcctbadminuser.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.
MetroCluster Tiebreaker requires unix user account "mcctbadminuser" to be added to the group "mcctbgrp" for admin access.
Do you wish to add ? [Y/N]: y
Unix user account "mcctbadminuser" added to "mcctbgrp".
Do you wish to generate your own public-private key pair for encrypting audit log? [Y/N]: y
Generating public-private key pair...
Configuring Vault...
Starting vault server...
==> Vault server configuration:

             Api Address: <api_address>
                     Cgo: disabled
         Cluster Address: <cluster_address>
   Environment Variables: BASH_FUNC_which%%, DBUS_SESSION_BUS_ADDRESS, GODEBUG, HISTCONTROL, HISTSIZE, HOME, HOSTNAME, HOST_ACCOUNT, LANG, LESSOPEN, LOGNAME, LS_COLORS, MAIL, PATH, PWD, SHELL, SHLVL, SSH_CLIENT, SSH_CONNECTION, SSH_TTY, STAF_TEMP_DIR, TERM, USER, VAULT_ADDR, VAULT_TOKEN, XDG_RUNTIME_DIR, XDG_SESSION_ID, _, vault_Addr, which_declare
              Go Version: go1.20.5
              Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "0.0.0.0:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "enabled")
               Log Level:
                   Mlock: supported: true, enabled: true
           Recovery Mode: false
                 Storage: file
                 Version: Vault v1.14.0, built 2023-06-19T11:40:23Z
             Version Sha: 13a649f860186dffe3f3a4459814d87191efc321

==> Vault server started! Log data will stream in below:

2023-11-23T15:14:28.532+0530 [INFO]  proxy environment: http_proxy="" https_proxy="" no_proxy=""
2023-11-23T15:14:28.577+0530 [INFO]  core: Initializing version history cache for core
2023-11-23T15:14:38.552+0530 [INFO]  core: security barrier not initialized
2023-11-23T15:14:38.552+0530 [INFO]  core: seal configuration missing, not initialized
2023-11-23T15:14:38.554+0530 [INFO]  core: security barrier not initialized
2023-11-23T15:14:38.555+0530 [INFO]  core: security barrier initialized: stored=1 shares=5 threshold=3
2023-11-23T15:14:38.556+0530 [INFO]  core: post-unseal setup starting
2023-11-23T15:14:38.577+0530 [INFO]  core: loaded wrapping token key
2023-11-23T15:14:38.577+0530 [INFO]  core: successfully setup plugin catalog: plugin-directory=""
2023-11-23T15:14:38.577+0530 [INFO]  core: no mounts; adding default mount table
2023-11-23T15:14:38.578+0530 [INFO]  core: successfully mounted: type=cubbyhole version="v1.14.0+builtin.vault" path=cubbyhole/ namespace="ID: root. Path: "
2023-11-23T15:14:38.578+0530 [INFO]  core: successfully mounted: type=system version="v1.14.0+builtin.vault" path=sys/ namespace="ID: root. Path: "
2023-11-23T15:14:38.578+0530 [INFO]  core: successfully mounted: type=identity version="v1.14.0+builtin.vault" path=identity/ namespace="ID: root. Path: "
2023-11-23T15:14:38.581+0530 [INFO]  core: successfully mounted: type=token version="v1.14.0+builtin.vault" path=token/ namespace="ID: root. Path: "
2023-11-23T15:14:38.581+0530 [INFO]  rollback: starting rollback manager
2023-11-23T15:14:38.581+0530 [INFO]  core: restoring leases
2023-11-23T15:14:38.582+0530 [INFO]  expiration: lease restore complete
2023-11-23T15:14:38.582+0530 [INFO]  identity: entities restored
2023-11-23T15:14:38.582+0530 [INFO]  identity: groups restored
2023-11-23T15:14:38.583+0530 [INFO]  core: Recorded vault version: vault version=1.14.0 upgrade time="2023-11-23 09:44:38.582881162 +0000 UTC" build date=2023-06-19T11:40:23Z
2023-11-23T15:14:38.583+0530 [INFO]  core: usage gauge collection is disabled
2023-11-23T15:14:38.998+0530 [INFO]  core: post-unseal setup complete
2023-11-23T15:14:38.999+0530 [INFO]  core: root token generated
2023-11-23T15:14:38.999+0530 [INFO]  core: pre-seal teardown starting
2023-11-23T15:14:38.999+0530 [INFO]  rollback: stopping rollback manager
2023-11-23T15:14:38.999+0530 [INFO]  core: pre-seal teardown complete
2023-11-23T15:14:39.311+0530 [INFO]  core.cluster-listener.tcp: starting listener: listener_address=0.0.0.0:8201
2023-11-23T15:14:39.311+0530 [INFO]  core.cluster-listener: serving cluster requests: cluster_listen_address=[::]:8201
2023-11-23T15:14:39.312+0530 [INFO]  core: post-unseal setup starting
2023-11-23T15:14:39.312+0530 [INFO]  core: loaded wrapping token key
2023-11-23T15:14:39.312+0530 [INFO]  core: successfully setup plugin catalog: plugin-directory=""
2023-11-23T15:14:39.313+0530 [INFO]  core: successfully mounted: type=system version="v1.14.0+builtin.vault" path=sys/ namespace="ID: root. Path: "
2023-11-23T15:14:39.313+0530 [INFO]  core: successfully mounted: type=identity version="v1.14.0+builtin.vault" path=identity/ namespace="ID: root. Path: "
2023-11-23T15:14:39.313+0530 [INFO]  core: successfully mounted: type=cubbyhole version="v1.14.0+builtin.vault" path=cubbyhole/ namespace="ID: root. Path: "
2023-11-23T15:14:39.314+0530 [INFO]  core: successfully mounted: type=token version="v1.14.0+builtin.vault" path=token/ namespace="ID: root. Path: "
2023-11-23T15:14:39.314+0530 [INFO]  rollback: starting rollback manager
2023-11-23T15:14:39.314+0530 [INFO]  core: restoring leases
2023-11-23T15:14:39.314+0530 [INFO]  identity: entities restored
2023-11-23T15:14:39.314+0530 [INFO]  expiration: lease restore complete
2023-11-23T15:14:39.314+0530 [INFO]  identity: groups restored
2023-11-23T15:14:39.315+0530 [INFO]  core: usage gauge collection is disabled
2023-11-23T15:14:39.316+0530 [INFO]  core: post-unseal setup complete
2023-11-23T15:14:39.316+0530 [INFO]  core: vault is unsealed
Success! Uploaded policy: mcctb-policy
2023-11-23T15:14:39.795+0530 [INFO]  core: enabled credential backend: path=approle/ type=approle version=""
Success! Enabled approle auth method at: approle/
2023-11-23T15:14:39.885+0530 [INFO]  core: successful mount: namespace="" path=mcctb/ type=kv version=""
Success! Enabled the kv secrets engine at: mcctb/
Success! Data written to: auth/approle/role/mcctb-app
Installing the Fujitsu-MetroCluster-Tiebreaker-Software-1.6-1.x86_64.rpm
Preparing...                          # ############################### # [100%]

Updating / installing...

1:Fujitsu-MetroCluster-Tiebreaker-So# ############################### # [100%]
Performing file integrity check
etc/cron.weekly/metrocluster-tiebreaker-support is Ok
etc/cron.weekly/metrocluster-tiebreaker-support-cov is Ok
etc/init.d/fujitsu-metrocluster-tiebreaker-software is Ok
etc/init.d/fujitsu-metrocluster-tiebreaker-software-cov is Ok
etc/logrotate.d/mcctb is Ok
opt/fujitsu/mcctb/lib/common/activation-1.1.1.jar is Ok
opt/fujitsu/mcctb/lib/common/aopalliance.jar is Ok
opt/fujitsu/mcctb/lib/common/args4j.jar is Ok
opt/fujitsu/mcctb/lib/common/aspectjrt.jar is Ok
opt/fujitsu/mcctb/lib/common/aspectjweaver.jar is Ok
opt/fujitsu/mcctb/lib/common/asup.jar is Ok
opt/fujitsu/mcctb/lib/common/bcpkix-jdk15on.jar is Ok
opt/fujitsu/mcctb/lib/common/bcprov-jdk15on.jar is Ok
opt/fujitsu/mcctb/lib/common/bcprov-jdk18on.jar is Ok
opt/fujitsu/mcctb/lib/common/bctls-fips-1.0.13.jar is Ok
opt/fujitsu/mcctb/lib/common/bctls-jdk18on.jar is Ok
opt/fujitsu/mcctb/lib/common/bcutil-jdk18on.jar is Ok
opt/fujitsu/mcctb/lib/common/cglib.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-codec.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-collections4.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-compress.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-daemon.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-daemon.src.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-dbcp2.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-io.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-lang3.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-logging.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-pool2.jar is Ok
opt/fujitsu/mcctb/lib/common/guava.jar is Ok
opt/fujitsu/mcctb/lib/common/httpclient.jar is Ok
opt/fujitsu/mcctb/lib/common/httpcore.jar is Ok
opt/fujitsu/mcctb/lib/common/jakarta.activation.jar is Ok
opt/fujitsu/mcctb/lib/common/jakarta.xml.bind-api.jar is Ok
opt/fujitsu/mcctb/lib/common/java-xmlbuilder.jar is Ok
opt/fujitsu/mcctb/lib/common/javax.inject.jar is Ok
opt/fujitsu/mcctb/lib/common/jaxb-api-2.3.1.jar is Ok
opt/fujitsu/mcctb/lib/common/jaxb-core.jar is Ok
opt/fujitsu/mcctb/lib/common/jaxb-impl.jar is Ok
opt/fujitsu/mcctb/lib/common/jline.jar is Ok
opt/fujitsu/mcctb/lib/common/jna.jar is Ok
opt/fujitsu/mcctb/lib/common/joda-time.jar is Ok
opt/fujitsu/mcctb/lib/common/jsch.jar is Ok
opt/fujitsu/mcctb/lib/common/json.jar is Ok
opt/fujitsu/mcctb/lib/common/jsvc.zip is Ok
opt/fujitsu/mcctb/lib/common/junixsocket-common.jar is Ok
opt/fujitsu/mcctb/lib/common/junixsocket-native-common.jar is Ok
opt/fujitsu/mcctb/lib/common/logback-classic.jar is Ok
opt/fujitsu/mcctb/lib/common/logback-core.jar is Ok
opt/fujitsu/mcctb/lib/common/mail-1.6.2.jar is Ok
opt/fujitsu/mcctb/lib/common/mariadb-java-client.jar is Ok
opt/fujitsu/mcctb/lib/common/mcctb-mib.jar is Ok
opt/fujitsu/mcctb/lib/common/mcctb.jar is Ok
opt/fujitsu/mcctb/lib/common/mockito-core.jar is Ok
opt/fujitsu/mcctb/lib/common/slf4j-api.jar is Ok
opt/fujitsu/mcctb/lib/common/snmp4j.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-aop.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-beans.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-context-support.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-context.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-core.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-expression.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-web.jar is Ok
opt/fujitsu/mcctb/lib/common/vault-java-driver.jar is Ok
opt/fujitsu/mcctb/lib/common/xz.jar is Ok
opt/fujitsu/mcctb/lib/org.jacoco.agent-0.8.8-runtime.jar is Ok
opt/fujitsu/mcctb/bin/mcctb-asup-invoke is Ok
opt/fujitsu/mcctb/bin/mcctb_postrotate is Ok
opt/fujitsu/mcctb/bin/fujitsu-metrocluster-tiebreaker-software-cli is Ok
/

Synchronizing state of fujitsu-metrocluster-tiebreaker-software.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable fujitsu-metrocluster-tiebreaker-software
Created symlink /etc/systemd/system/multi-user.target.wants/fujitsu-metrocluster-tiebreaker-software.service → /etc/systemd/system/fujitsu-metrocluster-tiebreaker-software.service.

Attempting to start MetroCluster Tiebreaker software services
Started MetroCluster Tiebreaker software services
Successfully installed MetroCluster Tiebreaker software version 1.6.

Tiebreaker 1.5から1.6へのアップグレード

Tiebreaker 1.5ソフトウェアのバージョンをTiebreaker 1.6にアップグレードするには、次の手順を実行します。

手順

[root@mcctb ~] #プロンプトで次のコマンドを実行して、ソフトウェアをアップグレードします。

sh MetroClusterTiebreakerInstall-1.6

アップグレードが完了すると、次の出力が表示されます。

Extracting the MetroCluster Tiebreaker installation/upgrade archive
Install digest hash is Ok
Performing the MetroCluster Tiebreaker code signature check
Install code signature is Ok

Enter database user name : root

Please enter database password for root
Enter password:

Password updated successfully in the database.

Do you wish to generate your own public-private key pair for encrypting audit log? [Y/N]: y
Generating public-private key pair...
Configuring Vault...
==> Vault shutdown triggered
2023-07-21T00:30:22.335+0530 [INFO]  core: marked as sealed
2023-07-21T00:30:22.335+0530 [INFO]  core: pre-seal teardown starting
2023-07-21T00:30:22.335+0530 [INFO]  rollback: stopping rollback manager
2023-07-21T00:30:22.335+0530 [INFO]  core: pre-seal teardown complete
2023-07-21T00:30:22.335+0530 [INFO]  core: stopping cluster listeners
2023-07-21T00:30:22.335+0530 [INFO]  core.cluster-listener: forwarding rpc listeners stopped
2023-07-21T00:30:22.375+0530 [INFO]  core.cluster-listener: rpc listeners successfully shut down
2023-07-21T00:30:22.375+0530 [INFO]  core: cluster listeners successfully shut down
2023-07-21T00:30:22.376+0530 [INFO]  core: vault is sealed
Starting vault server...
==> Vault server configuration:

             Api Address: <api_address>
                     Cgo: disabled
         Cluster Address: <cluster_address>
   Environment Variables: BASH_FUNC_which%%, DBUS_SESSION_BUS_ADDRESS, GODEBUG, HISTCONTROL, HISTSIZE, HOME, HOSTNAME, HOST_ACCOUNT, LANG, LESSOPEN, LOGNAME, LS_COLORS, MAIL, PATH, PWD, SHELL, SHLVL, SSH_CLIENT, SSH_CONNECTION, SSH_TTY, STAF_TEMP_DIR, TERM, USER, VAULT_ADDR, VAULT_TOKEN, XDG_RUNTIME_DIR, XDG_SESSION_ID, _, vault_Addr, which_declare
              Go Version: go1.20.5
              Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "0.0.0.0:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "enabled")
               Log Level:
                   Mlock: supported: true, enabled: true
           Recovery Mode: false
                 Storage: file
                 Version: Vault v1.14.0, built 2023-06-19T11:40:23Z
             Version Sha: 13a649f860186dffe3f3a4459814d87191efc321

==> Vault server started! Log data will stream in below:

2023-07-21T00:30:33.065+0530 [INFO]  proxy environment: http_proxy="" https_proxy="" no_proxy=""
2023-07-21T00:30:33.098+0530 [INFO]  core: Initializing version history cache for core
2023-07-21T00:30:43.092+0530 [INFO]  core: security barrier not initialized
2023-07-21T00:30:43.092+0530 [INFO]  core: seal configuration missing, not initialized
2023-07-21T00:30:43.094+0530 [INFO]  core: security barrier not initialized
2023-07-21T00:30:43.096+0530 [INFO]  core: security barrier initialized: stored=1 shares=5 threshold=3
2023-07-21T00:30:43.098+0530 [INFO]  core: post-unseal setup starting
2023-07-21T00:30:43.124+0530 [INFO]  core: loaded wrapping token key
2023-07-21T00:30:43.124+0530 [INFO]  core: successfully setup plugin catalog: plugin-directory=""
2023-07-21T00:30:43.124+0530 [INFO]  core: no mounts; adding default mount table
2023-07-21T00:30:43.125+0530 [INFO]  core: successfully mounted: type=cubbyhole version="v1.14.0+builtin.vault" path=cubbyhole/ namespace="ID: root. Path: "
2023-07-21T00:30:43.126+0530 [INFO]  core: successfully mounted: type=system version="v1.14.0+builtin.vault" path=sys/ namespace="ID: root. Path: "
2023-07-21T00:30:43.126+0530 [INFO]  core: successfully mounted: type=identity version="v1.14.0+builtin.vault" path=identity/ namespace="ID: root. Path: "
2023-07-21T00:30:43.129+0530 [INFO]  core: successfully mounted: type=token version="v1.14.0+builtin.vault" path=token/ namespace="ID: root. Path: "
2023-07-21T00:30:43.130+0530 [INFO]  rollback: starting rollback manager
2023-07-21T00:30:43.130+0530 [INFO]  core: restoring leases
2023-07-21T00:30:43.130+0530 [INFO]  identity: entities restored
2023-07-21T00:30:43.130+0530 [INFO]  identity: groups restored
2023-07-21T00:30:43.131+0530 [INFO]  core: usage gauge collection is disabled
2023-07-21T00:30:43.131+0530 [INFO]  expiration: lease restore complete
2023-07-21T00:30:43.131+0530 [INFO]  core: Recorded vault version: vault version=1.14.0 upgrade time="2023-07-20 19:00:43.131158543 +0000 UTC" build date=2023-06-19T11:40:23Z
2023-07-21T00:30:43.371+0530 [INFO]  core: post-unseal setup complete
2023-07-21T00:30:43.371+0530 [INFO]  core: root token generated
2023-07-21T00:30:43.371+0530 [INFO]  core: pre-seal teardown starting
2023-07-21T00:30:43.371+0530 [INFO]  rollback: stopping rollback manager
2023-07-21T00:30:43.372+0530 [INFO]  core: pre-seal teardown complete
2023-07-21T00:30:43.694+0530 [INFO]  core.cluster-listener.tcp: starting listener: listener_address=0.0.0.0:8201
2023-07-21T00:30:43.695+0530 [INFO]  core.cluster-listener: serving cluster requests: cluster_listen_address=[::]:8201
2023-07-21T00:30:43.695+0530 [INFO]  core: post-unseal setup starting
2023-07-21T00:30:43.696+0530 [INFO]  core: loaded wrapping token key
2023-07-21T00:30:43.696+0530 [INFO]  core: successfully setup plugin catalog: plugin-directory=""
2023-07-21T00:30:43.697+0530 [INFO]  core: successfully mounted: type=system version="v1.14.0+builtin.vault" path=sys/ namespace="ID: root. Path: "
2023-07-21T00:30:43.698+0530 [INFO]  core: successfully mounted: type=identity version="v1.14.0+builtin.vault" path=identity/ namespace="ID: root. Path: "
2023-07-21T00:30:43.698+0530 [INFO]  core: successfully mounted: type=cubbyhole version="v1.14.0+builtin.vault" path=cubbyhole/ namespace="ID: root. Path: "
2023-07-21T00:30:43.701+0530 [INFO]  core: successfully mounted: type=token version="v1.14.0+builtin.vault" path=token/ namespace="ID: root. Path: "
2023-07-21T00:30:43.701+0530 [INFO]  rollback: starting rollback manager
2023-07-21T00:30:43.702+0530 [INFO]  core: restoring leases
2023-07-21T00:30:43.702+0530 [INFO]  identity: entities restored
2023-07-21T00:30:43.702+0530 [INFO]  expiration: lease restore complete
2023-07-21T00:30:43.702+0530 [INFO]  identity: groups restored
2023-07-21T00:30:43.702+0530 [INFO]  core: usage gauge collection is disabled
2023-07-21T00:30:43.703+0530 [INFO]  core: post-unseal setup complete
2023-07-21T00:30:43.703+0530 [INFO]  core: vault is unsealed
Success! Uploaded policy: mcctb-policy
2023-07-21T00:30:44.226+0530 [INFO]  core: enabled credential backend: path=approle/ type=approle version=""
Success! Enabled approle auth method at: approle/
2023-07-21T00:30:44.315+0530 [INFO]  core: successful mount: namespace="" path=mcctb/ type=kv version=""
Success! Enabled the kv secrets engine at: mcctb/
Success! Data written to: auth/approle/role/mcctb-app
Upgrading to Fujitsu-MetroCluster-Tiebreaker-Software-1.6-1.x86_64.rpm
Preparing...                          ################################# [100%]
Updating / installing...
   1:Fujitsu-MetroCluster-Tiebreaker-So################################# [ 50%]
Performing file integrity check
etc/cron.weekly/metrocluster-tiebreaker-support is Ok
etc/cron.weekly/metrocluster-tiebreaker-support-cov is Ok
etc/init.d/fujitsu-metrocluster-tiebreaker-software is Ok
etc/init.d/fujitsu-metrocluster-tiebreaker-software-cov is Ok
etc/logrotate.d/mcctb is Ok
opt/fujitsu/mcctb/lib/common/activation-1.1.1.jar is Ok
opt/fujitsu/mcctb/lib/common/aopalliance.jar is Ok
opt/fujitsu/mcctb/lib/common/args4j.jar is Ok
opt/fujitsu/mcctb/lib/common/aspectjrt.jar is Ok
opt/fujitsu/mcctb/lib/common/aspectjweaver.jar is Ok
opt/fujitsu/mcctb/lib/common/asup.jar is Ok
opt/fujitsu/mcctb/lib/common/bcpkix-jdk15on.jar is Ok
opt/fujitsu/mcctb/lib/common/bcprov-jdk15on.jar is Ok
opt/fujitsu/mcctb/lib/common/bcprov-jdk18on.jar is Ok
opt/fujitsu/mcctb/lib/common/bctls-fips-1.0.13.jar is Ok
opt/fujitsu/mcctb/lib/common/bctls-jdk18on.jar is Ok
opt/fujitsu/mcctb/lib/common/bcutil-jdk18on.jar is Ok
opt/fujitsu/mcctb/lib/common/cglib.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-codec.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-collections4.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-compress.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-daemon.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-daemon.src.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-dbcp2.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-io.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-lang3.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-logging.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-pool2.jar is Ok
opt/fujitsu/mcctb/lib/common/guava.jar is Ok
opt/fujitsu/mcctb/lib/common/httpclient.jar is Ok
opt/fujitsu/mcctb/lib/common/httpcore.jar is Ok
opt/fujitsu/mcctb/lib/common/jakarta.activation.jar is Ok
opt/fujitsu/mcctb/lib/common/jakarta.xml.bind-api.jar is Ok
opt/fujitsu/mcctb/lib/common/java-xmlbuilder.jar is Ok
opt/fujitsu/mcctb/lib/common/javax.inject.jar is Ok
opt/fujitsu/mcctb/lib/common/jaxb-api-2.3.1.jar is Ok
opt/fujitsu/mcctb/lib/common/jaxb-core.jar is Ok
opt/fujitsu/mcctb/lib/common/jaxb-impl.jar is Ok
opt/fujitsu/mcctb/lib/common/jline.jar is Ok
opt/fujitsu/mcctb/lib/common/jna.jar is Ok
opt/fujitsu/mcctb/lib/common/joda-time.jar is Ok
opt/fujitsu/mcctb/lib/common/jsch.jar is Ok
opt/fujitsu/mcctb/lib/common/json.jar is Ok
opt/fujitsu/mcctb/lib/common/jsvc.zip is Ok
opt/fujitsu/mcctb/lib/common/junixsocket-common.jar is Ok
opt/fujitsu/mcctb/lib/common/junixsocket-native-common.jar is Ok
opt/fujitsu/mcctb/lib/common/logback-classic.jar is Ok
opt/fujitsu/mcctb/lib/common/logback-core.jar is Ok
opt/fujitsu/mcctb/lib/common/mail-1.6.2.jar is Ok
opt/fujitsu/mcctb/lib/common/mariadb-java-client.jar is Ok
opt/fujitsu/mcctb/lib/common/mcctb-mib.jar is Ok
opt/fujitsu/mcctb/lib/common/mcctb.jar is Ok
opt/fujitsu/mcctb/lib/common/mockito-core.jar is Ok
opt/fujitsu/mcctb/lib/common/slf4j-api.jar is Ok
opt/fujitsu/mcctb/lib/common/snmp4j.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-aop.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-beans.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-context-support.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-context.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-core.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-expression.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-web.jar is Ok
opt/fujitsu/mcctb/lib/common/vault-java-driver.jar is Ok
opt/fujitsu/mcctb/lib/common/xz.jar is Ok
opt/fujitsu/mcctb/bin/mcctb_postrotate is Ok
opt/fujitsu/mcctb/bin/fujitsu-metrocluster-tiebreaker-software-cli is Ok
/

Synchronizing state of fujitsu-metrocluster-tiebreaker-software.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable Fujitsu-metrocluster-tiebreaker-software

Attempting to start Fujitsu MetroCluster Tiebreaker software services
Started Fujitsu MetroCluster Tiebreaker software services
Successfully upgraded Fujitsu MetroCluster Tiebreaker software to version 1.6.
Cleaning up / removing...
   2:Fujitsu-MetroCluster-Tiebreaker-So################################# [100%]

Tiebreaker 1.4から1.6へのアップグレード

Tiebreaker 1.4ソフトウェアのバージョンをTiebreaker 1.6にアップグレードするには、次の手順を実行します。

手順

[root@mcctb ~] #プロンプトで次のコマンドを実行して、ソフトウェアをアップグレードします。

sh MetroClusterTiebreakerInstall-1.6

アップグレードが完了すると、次の出力が表示されます。

Extracting the MetroCluster Tiebreaker installation/upgrade archive
Install digest hash is Ok
Performing the MetroCluster Tiebreaker code signature check
Install code signature is Ok
Enter unix user account to use for the installation:
mcctbuseradmin1
Unix user account "mcctbuseradmin1" doesn't exist. Do you wish to create "mcctbuseradmin1" user account? [Y/N]: y
Unix account "mcctbuseradmin1" created.
Changing password for user mcctbuseradmin1.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.

Enter database user name : root

Please enter database password for root
Enter password:

Password updated successfully in the database.

MetroCluster Tiebreaker requires unix user account "mcctbuseradmin1" to be added to the group "mcctbgrp" for admin access.
Do you wish to add ? [Y/N]: y
Unix user account "mcctbuseradmin1" added to "mcctbgrp".
Do you wish to generate your own public-private key pair for encrypting audit log? [Y/N]: y
Generating public-private key pair...
Configuring Vault...
Starting vault server...
==> Vault server configuration:

             Api Address: <api_addess>
                     Cgo: disabled
         Cluster Address: <cluster_address>
   Environment Variables: BASH_FUNC_which%%, DBUS_SESSION_BUS_ADDRESS, GODEBUG, HISTCONTROL, HISTSIZE, HOME, HOSTNAME, HOST_ACCOUNT, LANG, LESSOPEN, LOGNAME, LS_COLORS, MAIL, PATH, PWD, SHELL, SHLVL, SSH_CLIENT, SSH_CONNECTION, SSH_TTY, STAF_TEMP_DIR, TERM, USER, VAULT_ADDR, VAULT_TOKEN, XDG_RUNTIME_DIR, XDG_SESSION_ID, _, vault_Addr, which_declare
              Go Version: go1.20.5
              Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "0.0.0.0:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "enabled")
               Log Level:
                   Mlock: supported: true, enabled: true
           Recovery Mode: false
                 Storage: file
                 Version: Vault v1.14.0, built 2023-06-19T11:40:23Z
             Version Sha: 13a649f860186dffe3f3a4459814d87191efc321

==> Vault server started! Log data will stream in below:

2023-11-23T15:58:10.400+0530 [INFO]  proxy environment: http_proxy="" https_proxy="" no_proxy=""
2023-11-23T15:58:10.432+0530 [INFO]  core: Initializing version history cache for core
2023-11-23T15:58:20.422+0530 [INFO]  core: security barrier not initialized
2023-11-23T15:58:20.422+0530 [INFO]  core: seal configuration missing, not initialized
2023-11-23T15:58:20.424+0530 [INFO]  core: security barrier not initialized
2023-11-23T15:58:20.425+0530 [INFO]  core: security barrier initialized: stored=1 shares=5 threshold=3
2023-11-23T15:58:20.427+0530 [INFO]  core: post-unseal setup starting
2023-11-23T15:58:20.448+0530 [INFO]  core: loaded wrapping token key
2023-11-23T15:58:20.448+0530 [INFO]  core: successfully setup plugin catalog: plugin-directory=""
2023-11-23T15:58:20.448+0530 [INFO]  core: no mounts; adding default mount table
2023-11-23T15:58:20.449+0530 [INFO]  core: successfully mounted: type=cubbyhole version="v1.14.0+builtin.vault" path=cubbyhole/ namespace="ID: root. Path: "
2023-11-23T15:58:20.449+0530 [INFO]  core: successfully mounted: type=system version="v1.14.0+builtin.vault" path=sys/ namespace="ID: root. Path: "
2023-11-23T15:58:20.449+0530 [INFO]  core: successfully mounted: type=identity version="v1.14.0+builtin.vault" path=identity/ namespace="ID: root. Path: "
2023-11-23T15:58:20.451+0530 [INFO]  core: successfully mounted: type=token version="v1.14.0+builtin.vault" path=token/ namespace="ID: root. Path: "
2023-11-23T15:58:20.452+0530 [INFO]  rollback: starting rollback manager
2023-11-23T15:58:20.452+0530 [INFO]  core: restoring leases
2023-11-23T15:58:20.453+0530 [INFO]  identity: entities restored
2023-11-23T15:58:20.453+0530 [INFO]  identity: groups restored
2023-11-23T15:58:20.453+0530 [INFO]  expiration: lease restore complete
2023-11-23T15:58:20.453+0530 [INFO]  core: usage gauge collection is disabled
2023-11-23T15:58:20.453+0530 [INFO]  core: Recorded vault version: vault version=1.14.0 upgrade time="2023-11-23 10:28:20.453481904 +0000 UTC" build date=2023-06-19T11:40:23Z
2023-11-23T15:58:20.818+0530 [INFO]  core: post-unseal setup complete
2023-11-23T15:58:20.819+0530 [INFO]  core: root token generated
2023-11-23T15:58:20.819+0530 [INFO]  core: pre-seal teardown starting
2023-11-23T15:58:20.819+0530 [INFO]  rollback: stopping rollback manager
2023-11-23T15:58:20.819+0530 [INFO]  core: pre-seal teardown complete
2023-11-23T15:58:21.116+0530 [INFO]  core.cluster-listener.tcp: starting listener: listener_address=0.0.0.0:8201
2023-11-23T15:58:21.116+0530 [INFO]  core.cluster-listener: serving cluster requests: cluster_listen_address=[::]:8201
2023-11-23T15:58:21.117+0530 [INFO]  core: post-unseal setup starting
2023-11-23T15:58:21.117+0530 [INFO]  core: loaded wrapping token key
2023-11-23T15:58:21.117+0530 [INFO]  core: successfully setup plugin catalog: plugin-directory=""
2023-11-23T15:58:21.119+0530 [INFO]  core: successfully mounted: type=system version="v1.14.0+builtin.vault" path=sys/ namespace="ID: root. Path: "
2023-11-23T15:58:21.120+0530 [INFO]  core: successfully mounted: type=identity version="v1.14.0+builtin.vault" path=identity/ namespace="ID: root. Path: "
2023-11-23T15:58:21.120+0530 [INFO]  core: successfully mounted: type=cubbyhole version="v1.14.0+builtin.vault" path=cubbyhole/ namespace="ID: root. Path: "
2023-11-23T15:58:21.123+0530 [INFO]  core: successfully mounted: type=token version="v1.14.0+builtin.vault" path=token/ namespace="ID: root. Path: "
2023-11-23T15:58:21.123+0530 [INFO]  rollback: starting rollback manager
2023-11-23T15:58:21.124+0530 [INFO]  core: restoring leases
2023-11-23T15:58:21.124+0530 [INFO]  identity: entities restored
2023-11-23T15:58:21.124+0530 [INFO]  identity: groups restored
2023-11-23T15:58:21.124+0530 [INFO]  expiration: lease restore complete
2023-11-23T15:58:21.125+0530 [INFO]  core: usage gauge collection is disabled
2023-11-23T15:58:21.125+0530 [INFO]  core: post-unseal setup complete
2023-11-23T15:58:21.125+0530 [INFO]  core: vault is unsealed
Success! Uploaded policy: mcctb-policy
2023-11-23T15:58:21.600+0530 [INFO]  core: enabled credential backend: path=approle/ type=approle version=""
Success! Enabled approle auth method at: approle/
2023-11-23T15:58:21.690+0530 [INFO]  core: successful mount: namespace="" path=mcctb/ type=kv version=""
Success! Enabled the kv secrets engine at: mcctb/
Success! Data written to: auth/approle/role/mcctb-app
Upgrading to Fujitsu-MetroCluster-Tiebreaker-Software-1.6-1.x86_64.rpm
Preparing...                          ################################# [100%]
Updating / installing...
   1:Fujitsu-MetroCluster-Tiebreaker-So################################# [ 50%]
Performing file integrity check
etc/cron.weekly/metrocluster-tiebreaker-support is Ok
etc/cron.weekly/metrocluster-tiebreaker-support-cov is Ok
etc/init.d/fujitsu-metrocluster-tiebreaker-software is Ok
etc/init.d/fujitsu-metrocluster-tiebreaker-software-cov is Ok
etc/logrotate.d/mcctb is Ok
opt/fujitsu/mcctb/lib/common/activation-1.1.1.jar is Ok
opt/fujitsu/mcctb/lib/common/aopalliance.jar is Ok
opt/fujitsu/mcctb/lib/common/args4j.jar is Ok
opt/fujitsu/mcctb/lib/common/aspectjrt.jar is Ok
opt/fujitsu/mcctb/lib/common/aspectjweaver.jar is Ok
opt/fujitsu/mcctb/lib/common/asup.jar is Ok
opt/fujitsu/mcctb/lib/common/bcpkix-jdk15on.jar is Ok
opt/fujitsu/mcctb/lib/common/bcprov-jdk15on.jar is Ok
opt/fujitsu/mcctb/lib/common/bcprov-jdk18on.jar is Ok
opt/fujitsu/mcctb/lib/common/bctls-fips-1.0.13.jar is Ok
opt/fujitsu/mcctb/lib/common/bctls-jdk18on.jar is Ok
opt/fujitsu/mcctb/lib/common/bcutil-jdk18on.jar is Ok
opt/fujitsu/mcctb/lib/common/cglib.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-codec.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-collections4.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-compress.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-daemon.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-daemon.src.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-dbcp2.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-io.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-lang3.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-logging.jar is Ok
opt/fujitsu/mcctb/lib/common/commons-pool2.jar is Ok
opt/fujitsu/mcctb/lib/common/guava.jar is Ok
opt/fujitsu/mcctb/lib/common/httpclient.jar is Ok
opt/fujitsu/mcctb/lib/common/httpcore.jar is Ok
opt/fujitsu/mcctb/lib/common/jakarta.activation.jar is Ok
opt/fujitsu/mcctb/lib/common/jakarta.xml.bind-api.jar is Ok
opt/fujitsu/mcctb/lib/common/java-xmlbuilder.jar is Ok
opt/fujitsu/mcctb/lib/common/javax.inject.jar is Ok
opt/fujitsu/mcctb/lib/common/jaxb-api-2.3.1.jar is Ok
opt/fujitsu/mcctb/lib/common/jaxb-core.jar is Ok
opt/fujitsu/mcctb/lib/common/jaxb-impl.jar is Ok
opt/fujitsu/mcctb/lib/common/jline.jar is Ok
opt/fujitsu/mcctb/lib/common/jna.jar is Ok
opt/fujitsu/mcctb/lib/common/joda-time.jar is Ok
opt/fujitsu/mcctb/lib/common/jsch.jar is Ok
opt/fujitsu/mcctb/lib/common/json.jar is Ok
opt/fujitsu/mcctb/lib/common/jsvc.zip is Ok
opt/fujitsu/mcctb/lib/common/junixsocket-common.jar is Ok
opt/fujitsu/mcctb/lib/common/junixsocket-native-common.jar is Ok
opt/fujitsu/mcctb/lib/common/logback-classic.jar is Ok
opt/fujitsu/mcctb/lib/common/logback-core.jar is Ok
opt/fujitsu/mcctb/lib/common/mail-1.6.2.jar is Ok
opt/fujitsu/mcctb/lib/common/mariadb-java-client.jar is Ok
opt/fujitsu/mcctb/lib/common/mcctb-mib.jar is Ok
opt/fujitsu/mcctb/lib/common/mcctb.jar is Ok
opt/fujitsu/mcctb/lib/common/mockito-core.jar is Ok
opt/fujitsu/mcctb/lib/common/slf4j-api.jar is Ok
opt/fujitsu/mcctb/lib/common/snmp4j.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-aop.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-beans.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-context-support.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-context.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-core.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-expression.jar is Ok
opt/fujitsu/mcctb/lib/common/spring-web.jar is Ok
opt/fujitsu/mcctb/lib/common/vault-java-driver.jar is Ok
opt/fujitsu/mcctb/lib/common/xz.jar is Ok
opt/fujitsu/mcctb/lib/org.jacoco.agent-0.8.8-runtime.jar is Ok
opt/fujitsu/mcctb/bin/mcctb-asup-invoke is Ok
opt/fujitsu/mcctb/bin/mcctb_postrotate is Ok
opt/fujitsu/mcctb/bin/fujitsu-metrocluster-tiebreaker-software-cli is Ok
/

Synchronizing state of fujitsu-metrocluster-tiebreaker-software.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable fujitsu-metrocluster-tiebreaker-software

Attempting to start Fujitsu MetroCluster Tiebreaker software services
Started Fujitsu MetroCluster Tiebreaker software services
Successfully upgraded Fujitsu MetroCluster Tiebreaker software to version 1.6.
Cleaning up / removing...
   2:Fujitsu-MetroCluster-Tiebreaker-So################################# [100%]