Checklist for deploying geographically redundant Presence Services clusters

Last Updated : Sep 23, 2019 |
Prolog information
A geographically redundant Presence Services solution requires deployment of two multi-server Presence Services clusters that are located in different data centers or sites.

Prerequisites

Get the following before deploying Presence Services:
  1. A Geographic Redundancy enabled Avaya Aura® deployment in which:
    1. System Manager must be deployed in a geographic-redundant mode. See Administering Avaya Aura® System Manager.
    2. Session Manager must be deployed in both data centers and be geographically redundant. See Administering Avaya Aura® Session Manager.
    3. Communication Manager must be deployed in both data centers and must be geographically redundant aware. See Administering Avaya Aura® Communication Manager.
    4. Other components, such as Application Enablement Services must be deployed accordingly. See respective documentation.
  2. Two data centers with separate DNS servers.

Considerations

  1. Geographic redundancy for Presence Services is only supported on High Available deployments.
  2. Each data center must have enough capacity to service the complete set of users, that is local users and the users from the other data center, to ensure continued service to all after one of the data centers is nonfunctional.
    Note:
    The Number of Users attribute must be configured with the combined number of users in both data centers and must have the same value on both clusters.
    For more information, see Configuring number of users for a Presence Services cluster.
  3. Configuration of Presence Services in both data centers must be identical. That is, the clusters must have the same set of service attributes. See Chapter 9, Administration.
  4. For all solution components to detect the geographically redundant event, ensure that the data access to the damaged data center (DC) is completely disabled.
In the following checklist:
  • DC-1 refers to data center 1.
  • DC-2 refers to data center 2.
  • n refers to the number of servers in each Presence Services clusters.
Checklist for deploying a geographically redundant Presence Services cluster.
No.
Task
Reference
1
Administer one multi-server Presence cluster in DC-1.
2
Administer one multi-server Presence cluster in DC-2.
3
Administer additional n DNS A records on DC-1 to resolve Presence Services cluster FQDN of DC-2 to Avaya Breeze® platform Security Module IP address of DC-1.
4
Administer additional n DNS A records on DC-2 to resolve Presence Services cluster FQDN of DC-1 to Avaya Breeze® platform Security Module IP address of DC-2.
5
Administer additional n System Manager LHNR entries to resolve Presence Services cluster FQDN of DC-1 to Avaya Breeze® platform Security Module IP addresses of DC-2.
6
Administer additional n System Manager LHNR entries to resolve Presence Services Cluster FQDN of DC-2 to Avaya Breeze® platform Security Module IP addresses of DC-1.
7
In the DNS server in DC-1, add two new DNS A records for:
  1. DC1 Service FQDN resolving to the cluster IP address of the cluster in DC-1
  2. DC2 Service FQDN resolving to the cluster IP address of the cluster in DC-1.
8
In the DNS server in DC-2, add two new DNS A records for:
  1. DC2 Service FQDN resolving to the cluster IP address of the cluster in DC-2.
  2. DC1 Service FQDN resolving to the cluster IP address of the cluster in DC-2.
9
Add Service FQDNs of both DC-1 and DC-2 to the SAN field of the “Security Module HTTP Service” and “Websphere Service” identity certificates in each cluster node, in both data centers.
10
In the DNS server in DC-1, add an SRV record resolving the HTTPS service to the Service FQDN in DC-1.
11
In the DNS server in DC-2, add an SRV record resolving the HTTPS service to the Service FQDN in DC-2.
12
Administer DC-2 as Geo Redundant Cluster of DC-1.
13
Administer DC-1 as Geo Redundant Cluster of DC-2.
14
Restart Presence Services on both Presence Clusters.
15
Verify that Presence Services snap-in is ready to support Presence and IM.
16
Administer Aura users for Geographic Redundancy.
17
Administer devices for Geographic Redundancy.