PowerHA SystemMirror Version 7.2.4 for AIX Standard Edition Release Notes

Edit online

Software requirements

Edit online

Before you install PowerHA® SystemMirror® Version 7.2.4, you must install all available service packs for AIX® and PowerHA SystemMirror from the IBM® Fix Central website.

PowerHA SystemMirror Version 7.2.4 is supported on the following versions of the AIX operating system:
  • IBM AIX 7.1 with Technology Level 4 with Service Pack 8, or later
  • IBM AIX 7.1 with Technology Level 5 with Service Pack 4, or later
  • IBM AIX 7.2 with Technology Level 1 with Service Pack 6, or later
  • IBM AIX 7.2 with Technology Level 2 with Service Pack 4, or later
  • IBM AIX 7.2 with Technology Level 3 with Service Pack 3, or later
  • IBM AIX 7.2 with Technology Level 4 with Service Pack 1, or later
PowerHA SystemMirror GUI
PowerHA SystemMirror GUI is supported only on the following web browsers:
  • Google Chrome Version 57, or later
  • Firefox Version 54, or later

The PowerHA SystemMirror GUI requires that OpenSSL is installed on the PowerHA SystemMirror GUI server to generate a unique set of security files (keys and certificate). Secure Shell (SSH) must be configured on the PowerHA SystemMirror GUI server and on all nodes in the cluster. SSH is used to add clusters to the PowerHA SystemMirror GUI to restore snapshots, create new clusters from the PowerHA SystemMirror GUI, and to restore cluster snapshots. To perform these tasks from the PowerHA SystemMirror GUI as a non-root user, you must configure the sudo command on cluster nodes. For more information, see Logging in as a non-root user. After a cluster is successfully added to the PowerHA SystemMirror GUI, the root access or sudo access is no longer required to manage the cluster through the PowerHA SystemMirror GUI.

PowerHA SystemMirror GUI can also manage clusters that are running earlier versions of PowerHA SystemMirror. When you manage older clusters in the PowerHA SystemMirror GUI, you can use only the capabilities that are associated with the PowerHA SystemMirror version of the cluster. For example, with PowerHA SystemMirror Version 7.2.4 GUI server, if you select a cluster in the PowerHA SystemMirror GUI and that cluster is running PowerHA SystemMirror Version 7.2.1, some of the PowerHA SystemMirror Version 7.2.4 capabilities might not be available for the selected cluster.

CAA auto start on DR site
CAA auto start on Disaster Recovery (DR) site is supported only on the following versions of the AIX operating system:
  • IBM AIX 7.1 with Technology Level 5, or later
  • IBM AIX 7.2 with Technology Level 2, or later
Cloud backup management options
To use the PowerHA SystemMirror cloud backup management options, you can use any one of the following versions of Python:
  • Python version 2.7.x
  • Python version 3.x.x
Availability metrics options
To use the PowerHA SystemMirror availability metrics options, you can use any one of the following versions of Python:
  • Python version 2.7.x
  • Python version 3.x.x

Hardware requirements

Edit online

PowerHA SystemMirror graphical user interface (GUI) requires IBM POWER7® or later technology-based servers.

Installation and migration

Edit online

For more information, see Supported upgrade PowerHA SystemMirror versions.

PowerHA SystemMirror GUI

You do not need to install the PowerHA SystemMirror GUI server in a PowerHA SystemMirror cluster, but the PowerHA SystemMirror GUI agent must be installed in a cluster. When you migrate a PowerHA SystemMirror GUI agent, an attempt is made to restart the agent service when the migration completes. When you migrate a PowerHA SystemMirror GUI server, an attempt is made to maintain the original state of the agent service. If the PowerHA SystemMirror GUI server is active when the migration begins, an attempt is made to restart the PowerHA SystemMirror GUI server when the migration completes.

After you install filesets that are available on the PowerHA SystemMirror Version 7.2.4 for AIX media, you must run the /usr/es/sbin/cluster/ui/server/bin/smuiinst.ksh command to complete the installation process. The smuiinst.ksh command automatically downloads and installs the remaining files that are required to complete the PowerHA SystemMirror GUI installation process. These downloaded files are not included in the PowerHA SystemMirror filesets because the files are licensed under the General Public License (GPL).

You must migrate the PowerHA SystemMirror GUI server before you migrate any cluster that is managed by the PowerHA SystemMirror GUI server. New clusters cannot be managed by an earlier version of the PowerHA SystemMirror GUI server. If the PowerHA SystemMirror GUI server is configured for high availability, you must disable high availability of the PowerHA SystemMirror GUI server before you migrate the PowerHA SystemMirror GUI server. You can enable the PowerHA SystemMirror GUI server for high availability after the migration process is complete. For more information, see Configuring the PowerHA SystemMirror GUI server to be highly available.

For more information about migration, see the Upgrading a PowerHA SystemMirror cluster topic.

Additional information

Edit online

PowerHA SystemMirror GUI

  • If you cannot add a cluster to the PowerHA SystemMirror GUI, or create a new cluster from the PowerHA SystemMirror GUI, consider the following points:
    • Verify that the nodes in the cluster have a host name that can be routed to the PowerHA SystemMirror GUI server. You cannot use a routed service IP addresses to manage a cluster.
    • Verify that SSH connection from the PowerHA SystemMirror GUI server to the remote system that you are trying to connect 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 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.
    • Only a root user can create or add a cluster. After the cluster is added in the PowerHA SystemMirror GUI, a non-root user can also manage clusters through the PowerHA SystemMirror GUI. If you do not have root credentials, a root user must configure the sudo command such that it can be run on one of the nodes in the cluster. For more information, see Logging in as a non-root user. If you have root credentials, Secure Shell (SSH) service must be configured on the cluster to allow root access. The value of the PermitRootLogin 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.
    • 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.
  • If the status of a cluster is incorrect in the PowerHA SystemMirror GUI, consider the following points:
    • The PowerHA SystemMirror GUI server does not poll the cluster nodes for status. The PowerHA SystemMirror GUI listens for status change notifications from each node as indicated in the following actions:
      • Core PowerHA SystemMirror GUI events are sent to the PowerHA SystemMirror GUI server immediately after they occur.
      • When the clmgr command is used to modify the configuration of a cluster, a notification is sent to the PowerHA SystemMirror GUI server.
    • Verify that the network and firewall settings are allowing traffic between the PowerHA SystemMirror GUI server and PowerHA SystemMirror GUI agents by checking the following items:
      • The default port for the PowerHA SystemMirror GUI server is 8080. You can specify a different value for the port in the /usr/es/sbin/cluster/ui/server/configuration-server.json file.
      • The default port for the PowerHA SystemMirror GUI agent is 8081. You can specify a different value for the port in the /usr/es/sbin/cluster/ui/agent/configuration-agent.json file.

      For more information about changing the values for the ports, see the Changing ports.

    • Synchronize the cluster by running the following command: 
      clmgr synchronize cluster

      After you synchronize the cluster, if the sync PASSED event does not appear in the event viewer for that cluster or if the cluster status in the PowerHA SystemMirror GUI is not correct, the problem might require IBM Support assistance.

      See Troubleshooting the PowerHA SystemMirror GUI for more assistance.

  • In the PowerHA SystemMirror GUI, you must avoid changing the host name of the PowerHA SystemMirror GUI server. If you must modify the host name of the PowerHA SystemMirror GUI server, clusters that are managed by the PowerHA SystemMirror GUI might not be able to communicate status updates to the PowerHA SystemMirror GUI server. You can avoid this issue in one of the following ways:
    • Remove the cluster from the PowerHA SystemMirror GUI server before you modify the host name, and add the cluster after you modify the host name.
    • Modify the host name of the PowerHA SystemMirror GUI server, and manually update the /usr/es/sbin/cluster/ui/agent/configuration-agent.json file on each cluster node. Replace the old server IP address with the new IP address in the serverURI property. Restart the PowerHA SystemMirror GUI agent after you modify the file.
  • PowerHA SystemMirror GUI cannot identify temporary host name changes that are made by using the hostname command. You can modify the host name permanently in the following ways:
    • Use the/usr/es/sbin/cluster/ui/agent/bin/cl_set_hostname utility. 
      cl_set_hostname -p [-P] [-a <ADDRESS>] <NEW_HOSTNAME>
    • Update the /etc/hosts file and add the new host name. The previous host name must not be removed.
    • Run smitty hostname and set the new hostname.
    • Run any of the following commands: 
      chdev -l inet0 -a hostname=<NEW_HOSTNAME>
      /usr/sbin/hostid [hostname]
      /usr/lib/lpd/pio/etc/piodmgr -c > /dev/null 2>&1
  • The option to authenticate by using an SSH key is not available from the open terminal feature. SSH authentication is supported only though a password.
  • You do not need to install the PowerHA SystemMirror GUI server in a PowerHA SystemMirror cluster, but the PowerHA SystemMirror GUI agent must be installed in a cluster. If the PowerHA SystemMirror GUI server is installed within a PowerHA SystemMirror cluster, the PowerHA SystemMirror GUI can be used to keep the PowerHA SystemMirror GUI server highly available.
  • The PowerHA SystemMirror GUI can manage AIX and Linux® clusters concurrently, and with full multi-tenancy support. For more information, see Cluster zones.
  • 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 Configuring the GUI to be highly available.
  • By default, the PowerHA SystemMirror GUI server uses the IP address that is associated with the default host name of the system on which it is running. The PowerHA SystemMirror GUI agents use IP address of the host name to communicate the cluster status to the PowerHA SystemMirror GUI server. 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. For more information, see Configuring the PowerHA SystemMirror GUI.

Support matrix for PowerHA SystemMirror Smart Assists

The following table describes the versions of middleware that can be configured and managed with PowerHA SystemMirror Smart Assists. For information about supported PowerHA SystemMirror version, see PowerHA SystemMirror for AIX Reference Information.start of change
Table 1. Support matrix for PowerHA SystemMirror Smart AssistsThe table describes the middleware application versions that are supported on PowerHA SystemMirror with different versions of the AIX operating system.
Middleware application AIX 7.2 AIX Version 7.3
AIX print subsystem, DHCP, and DNS 7.2 7.3
Oracle Database Server 19C 19C
SAP Netweaver 7.52 7.52
Db2® 11.5 11.5
WebSphere® MQSeries® 9.3 9.3
IBM Tivoli® Directory Server 6.4 6.4
IBM Lotus® Domino® Server
Note: Support is withdrawn for this product from PowerHA SystemMirror 7.2.8 or later.
 NA NA
SAP liveCache Hot Standby
Note: Support is withdrawn for this product from PowerHA SystemMirror 7.2.8 or later.
 NA NA
MaxDB 7.9.08 7.9.08
IBM Tivoli Storage Manager
Note: The product is now known as IBM Spectrum® Protect™.
 8.1.8 8.1.8
end of change

Documentation

To view the latest updates to the documentation, see the What's new in PowerHA SystemMirror Version 7.2.4 for AIX topic.

To view the documentation in PDF files, see the PowerHA SystemMirror for AIX PDFs topic.

Man pages

The man pages for the PowerHA SystemMirror commands are provided in the cluster.man.en_US.es.data fileset. To view the man pages, from the command line, enter man command_name (where command_name is the name of the command). You can also view the man pages in the IBM Knowledge Center, PowerHA SystemMirror commands.

You can use the clmgr command to perform most of the PowerHA SystemMirror operations. For more information about the operations that you can perform by using the clmgr command, see the clmgr command: Quick reference topic.