Upgrading VM Recovery Manager HA
If you are upgrading the VM Recovery Manager HA solution from the previous version to the latest version, you must install the packages that have updates to the existing software in your environment.
- You must have root authority to perform the installation tasks.
- When you install the new filesets, ensure that the existing version of the KSYS software is not running any active operations. The installation of the newer version of the KSYS software fails if the discovery, verification, or move operation is running in the existing version of the KSYS software.
- All KSYS-related operations such as discover, verification, move, and cleanup
must be complete before you attempt to upgrade the existing version of the VM Recovery Manager HA solution to the latest version. Run the
ksysmgr query system status monitor=yescommand to check the status of KSYS-related operations. - Before you install or upgrade VM monitor fileset, ensure that you set the virtual machine in the KSYS subsystem to unmanage, and run the discovery operation. Then, install or upgrade the VMM fileset at the VMM. You can set the unmanaged virtual machine to managed depending on your requirement. You must run the discovery operation after you have set the unmanaged virtual machine to managed.
- It is recommended to stop the IBM.VMR daemon by running the
stopsrc -s IBM.VMRcommand before starting the upgrade operation. You must restart the IBM.VMR daemon by running thestartsrc -s IBM.VMRcommand after the upgrade operation completes.
| Current version of KSYS subsystem | Upgrade version of KSYS subsystem |
|---|---|
| VM Recovery Manager HA 1.5.0.0 |
|
| VM Recovery Manager HA 1.5.0.1 |
|
| VM Recovery Manager HA 1.6.0.0 |
|
| VM Recovery Manager HA 1.7.0.0 |
|
|
|
| VM Recovery Manager HA 1.8.0.0 |
|
| VM Recovery Manager HA 1.8.0.1 |
|
| VM Recovery Manager HA 1.9.0.0 |
|
| VM Recovery Manager HA 1.9.0.1 | VM Recovery Manager HA 1.10.0.0 |
Upgrading the KSYS software
- Contact IBM sales team for information about download location of the VM Recovery Manager HA solution.
- Copy the filesets to the location where the existing filesets are installed.
- Decompress the filesets according to the guidelines that are provided with the package.
- To install the filesets by using SMIT panel, complete the following steps:
- To open the SMIT panel, enter the following command:
smit install - In the Install and Update Software screen, select Update
Installed Software to Latest Level (Update All), and press
Enter.Install and Update Software Move cursor to desired item and press Enter. Install Software Update Installed Software to Latest Level (Update All) Install Software Bundle Update Software by Fix (APAR) Install and Update from ALL Available Software - In the Update Installed Software to Latest Level (Update All) screen, change the values
according to your situation. You must also accept new license agreements. Press
Enterafter you make all other changes.
- To open the SMIT panel, enter the following command:
- Check the installation summary at the end of the installation output by scrolling to the end of
the output. The output indicates whether the installation of your fileset was successful.
If trace spooling is enabled and the trace file size is large, you must wait for a few minutes before you run the ksysmgr command. If the installation was not successful, check the reason of failure in the output.
- After upgrading of the KSYS software successfully, run the following script in the GUI server:
/opt/IBM/ksys/ui/server/dist/server/bin/vmruiinst.ksh. Then, restart the GUI
server by running the
stopsrc -s vmruiserverandstartsrc -s vmruiservercommands.
Upgrading VIOS to Version 4.1.2.10
- Ensure that the VIOS version 3.1.4.21 above and the Postgres version 13 are installed on the
VIOS. To check the Postgres version, run the following command:
To check the mount point of the Postgres database, run the following command:cat /var/vio/SSP/<cluster_name> /D_E_F_A_U_L_T_061310/VIOSCFG/DB/PG/PG_VERSIONmount - Ensure that the SSP cluster and database are in a healthy state. To verify the state of the
cluster, run the following command in the padmin command-line interface:
The padmin command-line interface must display OK state for all the VIOS that are part of the SSP cluster.cluster -status - Upgrade a VIOS, for example VIOS1, to version 4.1.1.0 then check the status of upgrade progress.
To check the progress of the upgrade process, run the following command:
An output that is similar to the following message must display: VIOS upgrade completed successfully.viosupgrade -q -lNote: After upgrading the VIOS to version 4.1.2.10, verify the status of theksys_hsmondaemon in VIOS. If the daemon is inoperative, a reboot of the respective VIOS is required.To verify daemon status, run the following command:lssrc -s ksys_hsmon - Wait for two minutes to get the cluster in the stable state. To check the state of the cluster,
run the following command:
The output must display OK state for the upgraded VIOS.cluster -status - Please verify the VIOS release notes and apply if any mandatory efix required.
- Restart the VIOS after you have applied the efix.
- After the VIOS1 is up and running, you must wait for two minutes to get the cluster in the stable state. You can observe that the Postgres version of the VIOS is still version 13.
- Run the discovery operation on the KSYS controller node. Ensure that the discovery operation completes successfully.
- Similarly, upgrade all other VIOSes by repeating Step-4 to Step-7 for each VIOS. After all the
VIOSes are upgraded, the Postgres version will be update to 15. To check the Postgres version, run
the following
command:
cat /var/vio/SSP/<cluster_name> /D_E_F_A_U_L_T_061310/VIOSCFG/DB/PG/PG_VERSION
Upgrading VM agents
- In Red Hat Enterprise Linux (RHEL) (little endian)
virtual machines.To verify existing vmagent version, run the following commands:
Upgrade vmagent from existing (1.9 SP1) to latest(1.10):rpm -q vmagent vmagent-1.10.0.1-1.0.el7.ppc64le
Verify the version after upgrading vmagent:rpm -Uvh vmagent-1.10.0.0-1.0.el7.ppc64le.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] ksys_vmmd service is running. Stopping ksys_vmm daemon. ksys_vmm has been requested to stop.Warning: pax rpm is not installed. Please install pax rpm to collect snap data. Updating / installing... 1:vmagent-1.10.0.0-1.0.el7 ################################# [ 50%] Starting ksys_vmm daemon.ksys_vmm has been started. DEBUG: Detected version in %preun (upgrade): 1.9.0.1 Backed up: /var/ksys/config/samples/SAPHANAconfig.xml -> /var/ksys/config/samples/SAPHANAconfig.xml_1.9.0.1_Backup Backed up: /var/ksys/config/samples/POSTGRESconfig.xml -> /var/ksys/config/samples/POSTGRESconfig.xml_1.9.0.1_Backup Backed up: /var/ksys/config/samples/S4HANAconfig.xml -> /var/ksys/config/samples/S4HANAconfig.xml_1.9.0.1_Backup NOTICE: Configuration Backup Created - Backup files have '_1.9.0.1_Backup' suffix. - New defaults may appear as '.rpmnew'. - Please merge changes as needed. Cleaning up / removing... 2:vmagent-1.9.0.1-1.0.el7 ################################# [100%]rpm -q vmagent vmagent-1.10.0.0-1.0.el7.ppc64le - In SUSE Linux Enterprise Server (SLES) (little endian)
virtual machines.To verify existing vmagent version, run the following commands:
Upgrade vmagent from existing (1.9 SP1) to latest(1.10):rpm -q vmagent vmagent-1.10.0.0-1.0.suse123.ppc64le.rpmrpm -Uvh vmagent-1.10.0.0-1.0.suse123.ppc64le.rpm Preparing... ################################# [100%] ksys_vmmd service is running. Stopping ksys_vmm daemon. ksys_vmm has been requested to stop. Updating / installing... 1:vmagent-1.10.0.0-1.0.suse123 ################################# [ 50%] Starting ksys_vmm daemon. ksys_vmm has been started. DEBUG: Detected version in %preun (upgrade): 1.9.0.1 Backed up: /var/ksys/config/samples/SAPHANAconfig.xml -> /var/ksys/config/samples/SAPHANAconfig.xml_1.9.0.1_BackupBacked up: /var/ksys/config/samples/POSTGRESconfig.xml -> /var/ksys/config/samples/POSTGRESconfig.xml_1.9.0.1_BackupBacked up: /var/ksys/config/samples/S4HANAconfig.xml -> /var/ksys/config/samples/S4HANAconfig.xml_1.9.0.1_Backup NOTICE: Configuration Backup Created - Backup files have '_1.9.0.1_Backup' suffix. - New defaults may appear as '.rpmnew'. - Please merge changes as needed.Cleaning up / removing... 2:vmagent-1.9.0.1-1.0.suse123 ################################# [100%]Verify the version after upgrading vmagent:rpm -q vmagent vmagent-1.10.0.0-1.0.suse123.ppc64le
Upgrading AIX VM agents
These commands upgrades the VM agent software without modifying the current configured file and
newly installed config file renames as
<configfile>.xml.rpmnew
To overwrite VM agent on AIX virtual machine follow the below steps:
- Download the required filesets.
- Before overwriting the VM agent, take a backup of your application configuration file from the /var/ksys/config/samples directory.
- Install the filesets by using the
installpcommand orsmitty installp
.installp -aFXYd. <ksys.vmmon.rte> - After installation, scroll to the end of the output and check the installation summary to confirm that the fileset installation was successful.
- If any application was previously configured, restore the backed-up application configuration
file to the
/var/ksys/config/samplesdirectory.
Upgrading AIX VM agents from version 1.10
/var/ksys/config/backup- Verify the currently installed
version:
lslpp -l ksys.vmmon.rte - Upgrade the
fileset:
Example:installp -acXYd fileset_location ksys.vmmon.rteinstallp -acXYd . ksys.vmmon.rte - Verify that the upgrade completed
successfully:
lslpp -l ksys.vmmon.rte - Verify that backup files are
available:
ls -l /var/ksys/config/backup
The backup directory contains copies of configuration files that existed before the upgrade.
If you uninstall the fileset, the system removes the active configuration files but retains the
backup files in the /var/ksys/config/backup directory.
- Upgrading KSYS filesets for KSYS high availability supported with PowerHA SystemMirror
- To upgrade the KSYS software in a KSYS LPAR on which PowerHA SystemMirror is configured,
complete the following steps:
- Stop PowerHA SystemMirror cluster service on all KSYS nodes by using the
smit clstopcommand. - Upgrade the KSYS fileset on all KSYS nodes.
- Start the PowerHA SystemMirror cluster services by using the
smit clstartcommand.
- Stop PowerHA SystemMirror cluster service on all KSYS nodes by using the