B.1.1 Upgrading from PRIMECLUSTER Enterprise Edition 4.3A20

Check the configuration name of RMS by executing the following command on any one of the cluster nodes.
Put down the name as you can use it later.
```
# hvdisp -a | grep Configuration <Return>
Configuration: /opt/SMAW/SMAWRrms/build/<configuration_name>.us
```
Stop RMS if you are using it.
```
# hvshut -a <Return>
```
Boot each cluster node in single user mode.
```
# shutdown now <Return>
```
When update the basic software from existing environment, updating basic software, see the following document Operating Update manual.

Proceed the following steps on each cluster node.

Create a backup directory.
```
# mkdir /<mydir> <Return>
```

Back up the PRIMECLUSTER operating environment.

# cp -p /usr/opt/reliant/etc/hvipalias /<mydir> <Return>
# cp -p /var/opt/FJSVclapm/etc/Tuning_Param /<mydir> <Return>
# cp -p /opt/FJSVwvbs/etc/Plugin.html /<mydir> <Return>

In case of Red Hat Enterprise Linux 5 (for Intel64) or
Red Hat Enterprise Linux 6 (for Intel64) ,
back up the PRIMECLUSTER operating environment.

# cp -p /opt/FJSVwvbs/etc/webview.cnf /<mydir> <Return>
# cp -p /opt/FJSVwvbs/etc/.policy /<mydir> <Return>
# cp -p /opt/FJSVwvbs/etc/wvlocal.cnf /<mydir> <Return>

Back up the GLS operating environment.
```
# /opt/FJSVhanet/usr/sbin/hanetbackup -d /<mydir> <Return>
```
The backup file name is "hanetYYYYMMDD.bk". YYYYMMDD shows information of the command execution date. (YYYY: year, MM: month, DD: day)

Insert CD and mount the CD-ROM device.

# mount /media/cdrom <Return>

<CDROM_DIR> will be used as the mount point.

Execute the following script then delete a part of the PRIMECLUSTER package.

# cd <CDROM_DIR>/Tool <Return>
# ./upgrade_uninstall <Return>
Are you sure to remove a part of PRIMECLUSTER from your system (y or n) ? y <Return>
:
:
The uninstallation finished successfully.

Execute the following cluster_install script, and install the package or overwrite it.
```
PRIMERGY
```
```
# cd <CDROM_DIR>/Tool <Return>
# ./cluster_install -e EE-PG <Return>
:
:
The installation finished successfully.
```
```
PRIMEQUEST
```
```
# cd <CDROM_DIR>/Tool <Return>
# ./cluster_install -e EE-PQ <Return>
:
:
The installation finished successfully.
```
Note
- The following message might be output:
```
# ./cluster_install -x xx <Return>
INFO: no package to update
```
  This message indicates that the newer version of all the packages is installed, so it is not necessary to upgrade.
- While executing the cluster_install script, the following message might be output
```
# ./cluster_install -x xx <Return>
Installing package <XXXXXXXXXXX> ... skipped.
```
  This message indicates that the same version of all the packages is installed, so it is not necessary to upgrade.
Eject CD.
```
# cd / <Return>
# eject cdrom <Return>
```

Restore the PRIMECLUSTER operating environment that was backed up at step 2.

# sed s/"[ ]*WIDTH.*HEIGHT.*ALIGN.*"/"  WIDTH = \"810\" HEIGHT = \"430\" ALIGN = \"TOP\""/g 
   /<mydir>/Plugin.html > /opt/FJSVwvbs/etc/Plugin.html <Return>
# cp -p /<mydir>/Tuning_Param /var/opt/FJSVclapm/etc <Return>
# cp -p /<mydir>/hvipalias /usr/opt/reliant/etc <Return>

In case of Red Hat Enterprise Linux 5 (for Intel64) or
Red Hat Enterprise Linux 6 (for Intel64) ,
restore the PRIMECLUSTER operating environment that was backed up at step 2.

# cp -p /<mydir>/webview.cnf /opt/FJSVwvbs/etc/webview.cnf <Return>
# cp -p /<mydir>/.policy /opt/FJSVwvbs/etc/.policy <Return>
# cp -p /<mydir>/wvlocal.cnf /opt/FJSVwvbs/etc/wvlocal.cnf <Return>

Restore the GLS operating environment that was backed up at step 3.

# /opt/FJSVhanet/usr/sbin/hanetrestore -f /<mydir>/hanetYYYYMMDD.bk <Return>

Edit the /opt/SMAW/SMAWRrms/bin/hvenv.local file, and set "0" to the HV_RCSTART variable. If the /opt/SMAW/SMAWRrms/bin/hvenv.local file does not exist, create a file as follows. This setting will prevent automatic RMS startup during node startup.
```
export HV_RCSTART=0
```

After completing step 5 on all the cluster nodes, reboot all the cluster nodes. Check if they are all active then go to the next step.
```
# shutdown -r now <Return>
```
Confirm the hardware model/configuration and change the setting of the shutdown facility. If the hardware model/configuration does not fall under the following cases, go to the next step.
1. PRIMERGY RX200/300/500/600 series , TX200/300 series, and BX620/920/960 series (used in combination with ServerView Resource Orchestrator Virtual Edition.)
2. PRIMEQUEST
3. When the Host OS failover function is used in KVM environment of PRIMEQUEST
a. PRIMERGY RX200/300/500/600 series , TX200/300 series, and BX620/920/960 series (used in combination with ServerView Resource Orchestrator Virtual Edition.)
1. Check the status of the shutdown facility on all the nodes.
  "InitFailed" may be displayed as the initial state of the shutdown facility, and "Unknown" or "TestFailed" may be displayed as the test status.
```
# sdtool -s <Return>
Cluster Host    Agent                SA State      Shut State  Test State  Init State
------------    -----                --------      ----------  ----------  ----------
node1           SA_lkcd              Idle          Unknown     TestFailed  InitWorked
node1           SA_ipmi              Idle          Unknown     TestFailed  InitWorked
node2           SA_lkcd              Idle          Unknown     TestFailed  InitWorked
node2           SA_ipmi              Idle          Unknown     TestFailed  InitWorked
```
2. Change the iRMC password by referring to "8.10.2 Changing the User Name and Password for iRMC" in the "PRIMECLUSTER Installation and Administration Guide".
b. PRIMEQUEST
1. Check the status of the shutdown facility on all the nodes.
  "InitFailed" may be displayed as the initial state of the shutdown facility, and "Unknown" or "TestFailed" may be displayed as the test status.
```
# sdtool -s <Return>
Cluster Host    Agent                SA State      Shut State  Test State  Init State
------------    -----                --------      ----------  ----------  ----------
node1           SA_mmbp.so           Idle          Unknown     Unknown     InitFailed
node1           SA_mmbr.so           Idle          Unknown     Unknown     InitFailed
node2           SA_mmbp.so           Idle          Unknown     Unknown     InitFailed
node2           SA_mmbr.so           Idle          Unknown     Unknown     InitFailed
```
2. Change the MMB password by referring to "8.8.2 Changing the User Name and Password for Controlling the MMB with RMCP" in the "PRIMECLUSTER Installation and Administration Guide".
c. When the Host OS failover function is used in KVM environment of PRIMEQUEST
1. Setup the Host OS failover function by referring to "5.1.2.5.4 Settings when using Host OS failover function in KVM environment of PRIMEQUEST" in the "PRIMECLUSTER Installation and Administration Guide".
Enable the RMS setting on any one of the cluster nodes.
1. Start RMS Wizard using the following command. The configuration name is the same as that of step 1.
```
# hvw -n <configuration name> <Return>
```
2. Select "Configuration-Activate" from "Main configuration menu" then execute Activate of the RMS setting.
3. Exit RMS Wizard.
Change HV_RCSTART variable from "0" to "1" on all the nodes as follows:
1. Edit the /opt/SMAW/SMAWRrms/bin/hvenv.local file, and change the HV_RCSTART variable to "1". The value was set to "0" at step 10 of the procedure 5. This change will enable automatic RMS startup during node startup.
```
export HV_RCSTART=1
```
2. Start RMS.
```
# hvcm <Return>
```