Planning for PowerHA SystemMirror for Linux

All the relevant Red Hat Package Manager (RPM) are installed automatically on starting the PowerHA® SystemMirror® installation script.

To install the PowerHA SystemMirror for Linux, the following RPMs are used internally:
  • powerhasystemmirror
  • powerhasystemmirror.adapter
  • powerhasystemmirror.policies
  • powerhasystemmirror.policies.one
  • powerhasystemmirror.policies.two
  • powerhasystemmirror.sappolicy
PowerHA SystemMirror internally uses Reliable Scalable Cluster Technology (RSCT) for the clustering technology. The required versions of the RSCT RPM are installed automatically by default when you install the PowerHA SystemMirror. During installation of the PowerHA SystemMirror, if RSCT is detected, and the level of RSCT is lower than the required RSCT package, then the currently installed RSCT package is upgraded. PowerHA SystemMirror for Linux installs the following RSCT RPMs:
  • rsct.basic
  • rsct.core
  • rsct.core.utils
  • rsct.opt.storagerm
  • src
  • If you define the disk tiebreaker resources, the disk on which IBM®. TieBreaker resources are stored must not be used to store file systems.
  • Internet Protocol version 6 (IPv6) configuration is not supported in the PowerHA SystemMirror for Linux.
  • You can check the firewall status by running the systemctl status firewalld.service command. Firewall must be disabled or you must open the below ports:
    657/tcp
    16191/tcp
    657/udp
    12143/udp
    12347/udp 
    12348/udp

When a node is configured with multiple connections to a single network, the network interfaces serve different functions in the PowerHA SystemMirror.

A service interface is a network interface that is configured with the PowerHA SystemMirror service IP label. The service IP label is used by clients to access application programs. The service IP is only available when the corresponding resource group is online.

A persistent node IP label is an IP alias that can be assigned to a specific node on a cluster network. A persistent node IP label always stays on the same node (node-bound), and coexists on an NIC that already has a service or boot IP label defined. A persistent node IP label does not require installing an extra physical NIC on that node.

If you assign a persistent node IP label, it provides a node-bound address that you can use for administrative purposes because a connection to a persistent node IP label always goes to a specific node in the cluster. You can have one persistent node IP label per node.

For PowerHA SystemMirror, you must configure a persistent IP label for each cluster node. This is useful to access a particular node in a PowerHA SystemMirror cluster for running reports or for diagnostics. This provides advantage that the PowerHA SystemMirror can access the persistent IP label on the node despite individual NIC failures, provided spare NICs are present on the network.

If you assign IP aliases to NICs, it allows you to create more than one IP label on the same network interface. During an IP address takeover by using the IP aliases, when an IP label moves from one NIC to another, the target NIC receives the new IP label as an IP alias and keeps the original IP label and hardware address.

Configuring networks for IP address takeover (IPAT) by using IP aliases simplifies the network configuration in the PowerHA SystemMirror. You can configure a service address and one or more boot addresses for NICs.

PowerHA SystemMirror uses a technology referred to as IPAT by using IP aliases for keeping IP addresses highly available.

If you are planning for IP address takeover by using IP aliases, review the following information:
  • Each network interface must have a boot IP label that is defined in the PowerHA SystemMirror. The interfaces that are defined in the PowerHA SystemMirror are used to keep the service IP addresses highly available.
  • The following subnet requirements apply if multiple interfaces are present on a node that is attached to the same network:
    • All boot addresses must be defined on different subnets.
    • Service addresses must be on a different subnet from all boot addresses and persistent addresses.
  • Service address labels that are configured for IP address takeover by using IP aliases can be included in all nonconcurrent resource groups.
  • The netmask for all IP labels in a PowerHA SystemMirror for Linux network must be the same.

During a node fallover event, the service IP label that is moved is placed as an alias on the NIC of target node in addition to any other service labels configured on that NIC.

If your environment has multiple adapters on the same subnet, all the adapters must have the same network configuration and the adapters must be part of the PowerHA SystemMirror configuration.

Linux operating system requirements

The cluster node on which you want to install PowerHA SystemMirror for Linux must be running on either 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
Note: PowerHA SystemMirror Version 7.2.2 for Linux is not supported on SLES 11 for SAP.