CP server requirements
VCS 9.2.0 clusters (application clusters) support coordination point servers (CP servers) that are hosted on the following VCS and SFHA versions:
-
VCS 7.3.1 or later single-node cluster
-
SFHA 7.3.1 or later cluster
Upgrade considerations for CP servers
-
Upgrade VCS or SFHA on CP servers to version 9.2.0 if the current release version is prior to version 7.3.1.
-
You do not need to upgrade CP servers to version 9.2.0 if the release version is 7.3.1 or later.
-
CP servers on version 7.3.1 or later support HTTPS-based communication with application clusters on version 7.3.1 or later.
-
You need to configure VIPs for HTTPS-based communication if release version of application clusters is 7.3.1 or later.
Make sure that you meet the basic hardware requirements for the VCS/SFHA cluster to host the CP server.
See the InfoScale InfoScale Installation Guide.
Note: While InfoScale recommends at least three coordination points for fencing, a single CP server as coordination point is a supported server-based fencing configuration. Such single CP server fencing configuration requires that the coordination point be a highly available CP server that is hosted on an SFHA cluster.
Make sure you meet the following additional CP server requirements which are covered in this section before you install and configure CP server:
-
Hardware requirements
-
Operating system requirements
-
Networking requirements (and recommendations)
-
Security requirements
Table: CP server hardware requirements lists additional requirements for hosting the CP server.
Related information
Table: CP server hardware requirements
| Hardware required | Description |
|---|---|
| Disk space | To host the CP server on a VCS cluster or SFHA cluster, each host requires the following file system space\: |
| - 550 MB in the /opt directory (additionally, the language pack requires another 15 MB) | |
| - 300 MB in /usr | |
| - 20 MB in /var | |
| - 10 MB in /etc (for the CP server database) | |
| Storage | When CP server is hosted on an SFHA cluster, there must |
| be shared storage between the nodes of this SFHA cluster. | |
| RAM | Each CP server requires at least 512 MB. |
| Network | Network hardware capable of providing TCP/IP connection between CP servers and VCS clusters (application clusters). |
Table: CP server supported operating systems and versions displays the CP server supported operating systems and versions. An application cluster can use a CP server that runs any of the following supported operating systems.
Table: CP server supported operating systems and versions
| CP server | Operating system and version |
|---|---|
| CP server hosted on a VCS single-node cluster or on an SFHA cluster | CP server supports any of the following operating systems\: |
| - AIX 7.2 and 7.3 | |
| Review other details such as supported operating system levels and architecture for the supported operating systems. | |
| See the InfoScale InfoScale Release Notes for that platform. |
Following are the CP server networking requirements and recommendations:
-
InfoScale recommends that network access from the application clusters to the CP servers should be made highly-available and redundant. The network connections require either a secure LAN or VPN.
-
The CP server uses the TCP/IP protocol to connect to and communicate with the application clusters by these network paths. The CP server listens for messages from the application clusters using TCP port 443 if the communication happens over the HTTPS protocol. TCP port 443 is the default port that can be changed while you configure the CP server.
InfoScale recommends that you configure multiple network paths to access a CP server. If a network path fails, CP server does not require a restart and continues to listen on all the other available virtual IP addresses.
-
The CP server only supports Internet Protocol version 4 (IPv4) when communicating with the application clusters over the HTTPS protocol.
-
When placing the CP servers within a specific network configuration, you must take into consideration the number of hops from the different application cluster nodes to the CP servers. As a best practice, InfoScale recommends that the number of hops and network latency from the different application cluster nodes to the CP servers should be equal. This ensures that if an event occurs that results in an I/O fencing scenario, there is no bias in the race due to difference in number of hops or network latency between the CPS and various nodes.
For information about establishing secure communications between the application cluster and CP server, see the InfoScale Cluster Server Administrator's Guide.