PowerHA SystemMirror Version 7.2.3 for Linux Release Notes

New functions and features

PowerHA® SystemMirror® Version 7.2.3 for Linux with Service Pack 1
The following features and enhancements are offered in PowerHA SystemMirror Version 7.2.3 for Linux with Service Pack 1:
PowerHA SystemMirror support on RHEL 7.7 and RHEL 8.0
PowerHA SystemMirror Version 7.2.3 for Linux with Service Pack 1 is supported on Red Hat Enterprise Linux (RHEL) 7.7 and RHEL 8.0
PowerHA SystemMirror support on SLES 15 Service Pack 1
PowerHA SystemMirror Version 7.2.3 for Linux with Service Pack 1 is supported on SUSE Linux Enterprise Server (SLES) 15 Service Pack 1.
Support for Cost Optimized configuration of SAP HANA
The Cost Optimized configuration mode uses the secondary node for running a non-productive SAP HANA instance. The maximum amount of memory that is used by the productive SAP HANA instance on the secondary node is limited by configuring a value for the Global Allocation Limit parameter and by disabling the table preload. Whenever takeover must occur, PowerHA SystemMirror stops the non-productive SAP HANA instance first and then takeover occurs. For more information, see PowerHA SystemMirror for SAP HANA.
Multinode disk heartbeat
PowerHA SystemMirror Version 7.2.3 for Linux with Service Pack 1, or later supports up to four nodes for disk heartbeat. For more information, see Heartbeating over disk.
Enable cluster services to start or stop automatically on a node after system restart
You can bring the cluster services online or offline on a node after the system restarts by configuring the START_ON_BOOT parameter. For more infraction see, Adding a node to a cluster.
Enhancements in Smart Assist
  • If you specify the value for the DEL_POLICY parameter as YES in the Delete Smart Assist operation, the configured srHook files and configuration that is related to PowerHA SystemMirror are deleted. For more information, see SAP HANA operations.
  • Enhanced the Setup Smart Assist operation for a Smart Assist policy by adding the PREFER_TAKEOVER parameter. The PREFER_TAKEOVER parameter defines whether PowerHA SystemMirror must switch over the SAP HANA database to the secondary node when the primary SAP HANA instance fails instead of restarting the SAP HANA instance locally on the primary node. For more information, see PowerHA SystemMirror for SAP HANA.
Enhancements in PowerHA SystemMirror graphical user interface (GUI)
The following updates are new in PowerHA SystemMirror GUI:
  • Support for Cost Optimized configuration of SAP HANA.
  • Create and manage resource group dependencies.
  • Non-root support for creating clusters and cloning clusters from snapshots.
  • Configure PowerHA SystemMirror GUI server to be highly available by using the High Availability wizard option in the PowerHA SystemMirror GUI.
  • Import multiple clusters by using the Add Multiple Clusters wizard.
  • Enhanced activity log to display the activity ID, start time and end time of the activity, and the duration of the activity. You can also view details such as the number of successful login attempts and failed login attempts, the number of new activities, and the number activities that are not viewed.
  • Enhanced security features with options to disable anonymous login and global access.
  • Automatic download and installation of the remaining files that are required to complete the PowerHA SystemMirror GUI installation process from the IBM® website by using the smuiinst.ksh command.
For more information, see PowerHA SystemMirror graphical user interface (GUI).
PowerHA SystemMirror Version 7.2.3 for Linux
The following features and enhancements are offered in PowerHA SystemMirror Version 7.2.3 for Linux:
PowerHA SystemMirror support on RHEL 7.6
PowerHA SystemMirror Version 7.2.3 for Linux is supported on Red Hat Enterprise Linux (RHEL) 7.6.
PowerHA SystemMirror support on SLES 12 SP4 and SLES 15
PowerHA SystemMirror Version 7.2.3 for Linux is supported on SUSE Linux Enterprise Server (SLES) 12 Service Pack 4 and SLES 15.
Support for PowerHA SystemMirror upgrade
You can upgrade PowerHA SystemMirror to a higher version and retain the cluster configuration. PowerHA SystemMirror Version 7.2.3 for Linux, or later, supports the rolling upgrade operation in addition to the offline cluster upgrade operation that is already available. During an offline upgrade operation, the cluster is not available and all resource groups must be stopped. During a rolling upgrade operation, the cluster remains online even though the nodes in the cluster run on different versions of PowerHA SystemMirror for Linux.
Support for Active/Active (read enabled) secondary configuration of SAP HANA
The Active/Active (read enabled) secondary configuration mode enables the secondary system for read-only queries. PowerHA SystemMirror Version 7.2.3 for Linux configures a secondary virtual IPv4 address to establish a direct connection to the secondary system. When the secondary system is not available, PowerHA SystemMirror activates the secondary virtual IPv4 address along with the first virtual IPv4 address on the primary system.
Enhancements in Smart Assist
PowerHA SystemMirror Version 7.2.3 for Linux, or later, supports the following enhancements:
  • Enhanced the Query Smart Assist operation for a Smart Assist policy by adding the RG_STATE and POLICY_TYPE parameters. The RG_STATE parameter indicates whether the SAP HANA resource groups are online or offline. The POLICY_TYPE parameter indicates whether the SAP HANA policy is only saved, or both saved and activated.
  • Enhanced the Delete Smart Assist operation by adding the DEL_POLICY={YES|NO} parameter to delete the SAP HANA saved policy when the SAP HANA resources are deactivated.
Support for standalone Enqueue Server 2
The standalone Enqueue Server 2 (ENSA2) in SAP NetWeaver Application Server for an SAP Advanced Business Application Programming (ABAP) system provides improved scalability and advanced SMENQ transaction. The ENSA2 can be configured either in a two-node cluster configuration or a multi-node cluster configuration. Smart Assist for SAP NetWeaver in PowerHA SystemMirror Version 7.2.3 for Linux supports both the Enqueue Server (ENSA) mode and the ENSA2 mode. Smart Assist for SAP NetWeaver automatically discovers the current mode that is configured and creates resources for SAP NetWeaver high availability based on the configured mode.
Support for four-node cluster deployment
Smart Assist in PowerHA SystemMirror Version 7.2.3 for Linux supports high availability of SAP NetWeaver on up to four-nodes running on SLES or RHEL.
Enhancements in PowerHA SystemMirror GUI
The following updates are new in the PowerHA SystemMirror graphical user interface (GUI):
  • Create, modify, and delete policies for SAP HANA through the Smart Assist wizard
  • Activate and deactivate SAP HANA policies
  • View and manage the saved and activated SAP HANA policies
  • Support for Active/Active (read enabled) secondary mode and Performance Optimized SAP HANA configuration mode through the Smart Assist wizard
  • View real-time replication status
  • View the Smart Assist-specific log file
  • View events related to Smart Assist operations
  • View Smart Assist configuration details
  • Add tags to distinguish Smart Assist policies.

Software requirements

You can download and install the PowerHA SystemMirror Version 7.2.3 for Linux from the IBM My Entitled Systems Support website.

The cluster node on which you want to install the PowerHA SystemMirror Version 7.2.3 for Linux must be running one of the following versions of the Linux operating system:
  • SUSE Linux Enterprise Server (SLES) for SAP 12 SP1 (64-bit)
  • SUSE Linux Enterprise Server (SLES) for SAP 12 SP2 (64-bit)
  • SUSE Linux Enterprise Server (SLES) for SAP 12 SP3 (64-bit)
  • SUSE Linux Enterprise Server (SLES) for SAP 12 SP4 (64-bit)
  • SUSE Linux Enterprise Server (SLES) for SAP 15 (GA) (64-bit)
  • start of changeSUSE Linux Enterprise Server (SLES) for SAP 15 Service Pack 1 (64-bit)end of change
  • Red Hat Enterprise Linux (RHEL) 7.2 (64-bit) (Little Endian)
  • Red Hat Enterprise Linux (RHEL) 7.3 (64-bit) (Little Endian)
  • Red Hat Enterprise Linux (RHEL) 7.4 (64-bit) (Little Endian)
  • Red Hat Enterprise Linux (RHEL) 7.5 (64-bit) (Little Endian)
  • Red Hat Enterprise Linux (RHEL) 7.6 (64-bit) (Little Endian)
  • start of changeRed Hat Enterprise Linux (RHEL) 7.7 (64-bit) (Little Endian)end of change
  • start of changeRed Hat Enterprise Linux (RHEL) 8.0 (64-bit) (Little Endian)end of change
PowerHA SystemMirror GUI

The PowerHA SystemMirror GUI requires OpenSSL installed on the GUI server to generate a unique set of security files (keys and certificate). You must have an installation of Secure Shell (SSH) on the GUI server and on all nodes in the cluster. SSH is used to add clusters to the GUI server to restore snapshots, and to create new clusters.

The PowerHA SystemMirror GUI is supported only on the following web browsers:
  • Google Chrome Version 57, or later
  • Mozilla Firefox Version 54, or later

Installation and migration

For information about installing PowerHA SystemMirror, see Installing PowerHA SystemMirror for Linux topic.
Note: Starting with PowerHA SystemMirror Version 7.2.2 for Linux Service Pack 1, you can migrate PowerHA SystemMirror for Linux to a later release. If you are using an earlier version, for example, PowerHA SystemMirror Version 7.2.2 for Linux, you must uninstall the existing version to install PowerHA SystemMirror Version 7.2.3 for Linux, or later.
For information about installing PowerHA SystemMirror GUI, see the Installing PowerHA SystemMirror GUI topic.
The PowerHA SystemMirror GUI has the following limitations in the PowerHA SystemMirror Version 7.2.3 for Linux, or later:
  • If you cannot add or create a cluster, verify that the SSH connection from the PowerHA SystemMirror GUI server system to the remote system is working. For example: 
    # ssh 172.19.67.49 /bin/hostname 
The authenticity of host ’172.19.67.49 (172.19.67.49)’ can’t be established. 
ECDSA key fingerprint is 41:19:ea:f6:4f:46:91:29:f5:a0:fd:89:91:f7:28:97. 
Are you sure you want to continue connecting (yes/no)?

    In the current version of the PowerHA SystemMirror GUI, you must also respond to the prompt to establish the SSH connection. You must respond by entering yes to add the host to the ~/.ssh/known_hosts file of the PowerHA SystemMirror GUI server. After adding the host name to the hosts files the prompt is not displayed again.

  • Verify that SSH is configured such that a root user can add existing clusters to the GUI, or create new cluster through the GUI. Verify that the SSH configuration setting for the parameter PermitRootLogin is set to yes in the /etc/ssh/sshd_config file. You must restart the SSH service after you modify the sshd_config file.
  • SSH service can be used with a key or with a password. For a key, the key must not have a passphrase. The configPasswordAuthentication parameter must be set to yes in the /etc/ssh/sshd_config file. You must restart the SSH service after you modify the sshd_config file.
  • In PowerHA SystemMirror GUI, you cannot change the host name of any managed cluster node. If you must change the host name of a cluster node that the PowerHA SystemMirror GUI server is managing, you might need to remove the cluster from the PowerHA SystemMirror GUI server before you change the host name, then add the cluster again after you change the host name. After you perform this step a single time, you do not have to repeat it for every connection.
  • In PowerHA SystemMirror GUI, you cannot change the host name of the PowerHA SystemMirror GUI server host. If you must change the host name of the PowerHA SystemMirror GUI server, you must either remove all your clusters, rediscover them after you change the host name, or manually update the /usr/es/sbin/cluster/ui/agent/configurationagent.json file on every cluster node and replace the old server IP address with the new address in the server URL. Restart the PowerHA SystemMirror GUI agent after this update is complete.
  • If you create a cluster by using the PowerHA SystemMirror GUI wizard, you cannot configure an alternate node name or a persistent IP for the first node that you added to the cluster. The first node is used to authenticate to the remote environment. It is included in the cluster with a default node label that is assigned to it.
  • The option to authenticate by using an SSH key is not available from the open terminal feature. SSH authentication is now supported only by password.
  • It is not required to install the PowerHA SystemMirror GUI server inside a PowerHA SystemMirror cluster, although the same is not true for the PowerHA SystemMirror GUI agent, which must be installed in a PowerHA SystemMirror GUI cluster.
  • When you are upgrading PowerHA SystemMirror, after you install PowerHA SystemMirror for Linux, you must bring the cluster services online from the backend. In offline migration, after all nodes are updated, you must run the clmgr online cluster command to bring the cluster services online. Similarly, in rolling migration,you must run the clmgr online node command on each node after you update the node. After the cluster services are bought online, the cluster configuration can be managed from the PowerHA SystemMirror GUI server. After migration, if you are not logged out of the PowerHA SystemMirror GUI automatically, you must log out and then log in to see the complete changes to the PowerHA SystemMirror GUI.

Additional information

PowerHA SystemMirror GUI

  • When you add a cluster to the PowerHA SystemMirror GUI, verify that SSH is not prompting for any unexpected input other than the password or passphrase. To verify that SSH is working correctly, run the ssh REMOTE_NODE hostname command, where REMOTE_NODE is the node you are using to add the cluster to the PowerHA SystemMirror GUI. When you run this command, only the password prompt is displayed.
  • To display the status in PowerHA SystemMirror GUI, the cluster must notify the PowerHA SystemMirror GUI. All core PowerHA SystemMirror or events are sent to the PowerHA SystemMirror GUI. When the clmgr command changes the configuration, the PowerHA SystemMirror GUI is notified.
  • Node modifications are not supported on the Linux operating system.
  • The default port for PowerHA SystemMirror GUI server is 8080. The default port for the PowerHA SystemMirror GUI agent is 8081. You must ensure that your network allows traffic on these ports. For more information about changing the values for the ports, see the Changing ports.
  • You can use only one PowerHA SystemMirror GUI server to manage your clusters.
  • If you install the PowerHA SystemMirror GUI server within a cluster, you must install it on only one of the nodes in the cluster unless you are configuring the PowerHA SystemMirror GUI for high availability. For more information, see the Configuring the GUI to be highly available topic.
  • By default, the PowerHA SystemMirror GUI server uses the IP address that is associated with the default host name. The PowerHA SystemMirror GUI agents use IP address to communicate cluster status. If you want to use an alternative IP address for the PowerHA SystemMirror GUI communication, specify the IP address in the serverAddress property in the /usr/es/sbin/cluster/ui/server/configuration-server.json file. The specified IP address is only used for clusters that are added to the PowerHA SystemMirror GUI after you add the IP address in the serverAddress property. If PowerHA SystemMirror GUI is already managing clusters and if you want the clusters to switch to the new IP address, you can rediscover the clusters or manually edit the IP address in the ServerURI property in agent configuration file usr/es/sbin/cluster/ui/agent/configurationagent.json. You must restart the PowerHA SystemMirror GUI server or the PowerHA SystemMirror GUI agent by running the systemctl restart phauiserver and systemctl restart phauiagent commands.
  • When Smart Assist SAP HANA operations delete all resource groups, the resource group that is created to keep the PowerHA SystemMirror server highly available is also deleted in earlier releases of PowerHA SystemMirror for Linux. Hence, you must repeat the process of making the PowerHA SystemMirror server highly available. However, in PowerHA SystemMirror Version 7.2.3 for Linux with Service Pack 1 this limitation has been removed.
  • The migration operation must be performed only after disabling the high availability function of the PowerHA SystemMirror GUI server. The process of making the PowerHA SystemMirror GUI server highly available must be repeated after the migration operation.

Documentation

To view the latest updates to the documentation, see the What's new in PowerHA SystemMirror Version 7.2.3 for Linux with Service Pack 1 topic.

To view the documentation in the PDF format, see the PowerHA SystemMirror for Linux PDFs topic.

Man pages

The man pages for the PowerHA SystemMirror Version 7.2.3 for Linux, or later commands are installed in the /usr/share/man/man1 directory. To view the man pages, from the command line, enter man command_name where command_name is the name of the command.

You can use the clmgr command to perform most of the operations in PowerHA SystemMirror.