SFCFSHA 6.0 clusters (application clusters) support coordination point servers (CP servers) which are hosted on the following VCS and SFHA versions:
VCS 6.0, 5.1SP1, or 5.1 single-node cluster
Single-node VCS clusters with VCS 5.1 SP1 RP1 and later or VCS 6.0 and later that hosts CP server does not require LLT and GAB to be configured.
SFHA 6.0, 5.1SP1, or 5.1 cluster
Make sure that you meet the basic hardware requirements for the VCS/SFHA cluster to host the CP server.
See the Veritas Cluster Server Installation Guide or the Veritas Storage Foundation High Availability Installation Guide.
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.
Table: CP server hardware requirements
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
Following are the CP server networking requirements and recommendations:
Symantec 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 14250. This is the default port that can be changed during a CP server configuration.
Symantec 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 one of the other available virtual IP addresses.
The CP server supports either Internet Protocol version 4 or version 6 (IPv4 or IPv6 addresses) when communicating with the application clusters. If the CP server is configured to use an IPv6 virtual IP address, then the application clusters should also be on the IPv6 network where the CP server is being hosted.
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, Symantec 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 the number of hops between the nodes.
For secure communication between the SFCFSHA cluster (application cluster) and the CP server, review the following support matrix:
For secure communications between the SFCFSHA cluster and CP server, consider the following requirements and suggestions:
In a secure communication environment, all CP servers that are used by the application cluster must be configured with security enabled. A configuration where the application cluster uses some CP servers running with security enabled and other CP servers running with security disabled is not supported.
For non-secure communication between CP server and application clusters, there is no need to configure Symantec Product Authentication Service. In non-secure mode, authorization is still provided by CP server for the application cluster users. The authorization that is performed only ensures that authorized users can perform appropriate actions as per their user privileges on the CP server.
For information about establishing secure communications between the application cluster and CP server, see the Veritas Storage Foundation Cluster File System High Availability Administrator's Guide.