3.3 PRIMECLUSTER Installation

You can install PRIMECLUSTER using an installation script.

The installation script is also called the CLI Installer.

It is used to install PRIMECLUSTER on a system in which Linux(R) software and related Fujitsu software have been installed. It is also used for installation of the cluster management server.

See

For details on the installation procedures, see the Installation Guide for PRIMECLUSTER.

After PRIMECLUSTER was installed, perform the following settings so that the CF modules and the GDS modules are not incorporated to an initial RAM disk (initramfs) for kdump:

RHEL6 environment
1. Add CF modules (cf, symsrv) and GDS modules (sfdsk, sfdsk_lib, sfdsklog, sfdsksys) to the setting of blacklist for /etc/kdump.conf.
  Example
  - If the setting of blacklist has been described in /etc/kdump.conf
    Before change:
    blacklist kvm-intel
    After change (if GDS is not installed):
    blacklist kvm-intel cf symsrv
    After change (if GDS is installed):
    blacklist kvm-intel cf symsrv sfdsk sfdsk_lib sfdsklog sfdsksys
  - If the setting of blacklist has not been described in /etc/kdump.conf
    Add the following line.
    If GDS is not installed:
    blacklist cf symsrv
    If GDS is installed:
    blacklist cf symsrv sfdsk sfdsk_lib sfdsklog sfdsksys
2. Restart the system or the service of kdump.
Note
In physical environment of PRIMERGY, PRIMECLUSTER sets kdump_post in /etc/kdump.conf. Do not set kdump_post in any other environments than PRIMECLUSTER as only one kdump_post is active in /etc/kdump.conf.
PRIMECLUSTER adds the following settings to /etc/kdump.conf when OS is started.
```
### poffinhibit configuration(automatically inserted) ###
kdump_post /etc/poffinhibit/unlock.sh
extra_modules poffinhibit_ipdv poffinhibit
options poffinhibit_ipdv SmBiosAddrParam=0x0
### poffinhibit configuration end ###
```

RHEL7 environment

Add the following description to the line of KDUMP_COMMANDLINE_APPEND in /etc/sysconfig/kdump by the same line.

If GDS is not installed:

rd.driver.blacklist=cf,symsrv

If GDS is installed:

rd.driver.blacklist=cf,symsrv,sfdsk,sfdsksys,sfdsklog,sfdsk_lib

Example

Before change:

KDUMP_COMMANDLINE_APPEND="irqpoll ... acpi_no_memhotplug"

After change (if GDS is not installed):

KDUMP_COMMANDLINE_APPEND="irqpoll ... acpi_no_memhotplug rd.driver.blacklist=cf,symsrv"

After change (if GDS is installed):

KDUMP_COMMANDLINE_APPEND="irqpoll ... acpi_no_memhotplug rd.driver.blacklist=cf,symsrv,sfdsk,sfdsksys,sfdsklog,sfdsk_lib"

Restart the system or the service of kdump.

See

For details on kdump, see the Linux documentation.

Note

When using the ntpdate service to adjust the time at OS startup in RHEL7, rapid time adjustment may be performed by the ntpdate service after each PRIMECLUSTER service is started. Therefore, considering the startup order of systemd, set the time adjustment by the ntpdate service to be completed before each PRIMECLUSTER service below is started.

fjsvwvbs.service
smawcf.service
fjsvsdx.service (if using GDS)

The operation procedure is as follows.

You can skip these steps when not using the ntpdate service.

Operation Procedure:

Perform the following procedure on all the nodes.

Create the directories.

# mkdir /etc/systemd/system/fjsvwvbs.service.d
# chmod 755 /etc/systemd/system/fjsvwvbs.service.d
# mkdir /etc/systemd/system/smawcf.service.d
# chmod 755 /etc/systemd/system/smawcf.service.d

When using GDS, also create the following directory.

# mkdir /etc/systemd/system/fjsvsdx.service.d
# chmod 755 /etc/systemd/system/fjsvsdx.service.d

Create the configuration files (ntp.conf) in the created directories.

# touch /etc/systemd/system/fjsvwvbs.service.d/ntp.conf
# chmod 644 /etc/systemd/system/fjsvwvbs.service.d/ntp.conf
# touch /etc/systemd/system/smawcf.service.d/ntp.conf
# chmod 644 /etc/systemd/system/smawcf.service.d/ntp.conf

When using GDS, also create the following configuration file.

# touch /etc/systemd/system/fjsvsdx.service.d/ntp.conf
# chmod 644 /etc/systemd/system/fjsvsdx.service.d/ntp.conf

Add the following setting to each configuration file (ntp.conf) created in step 2.
```
[Unit]
After=time-sync.target
```
Reflect the setting of start/stop order of the PRIMECLUSTER services.
```
# systemctl daemon-reload
```
Check the setting of start/stop order of the PRIMECLUSTER services. Make sure that time-sync.target is included.
```
# systemctl show fjsvwvbs.service | grep "After="
# systemctl show smawcf.service | grep "After="
```
When using GDS, also check the following service.
```
# systemctl show fjsvsdx.service | grep "After="
```
If the time-sync.target is not included, make sure that settings step 1 to 4 are correctly done.