AVAYA DOCUMENTATION CENTER
Find answers to your technical questions and learn how to use our products
Avaya Aura Presence Services Snap-in Reference
Checklist for deploying a multi-server Presence Services cluster
Prerequisites
You must have the following before deploying Presence Services:
-
For each server in the cluster, VMware ESXi is installed on the server with a host IP address assigned. For the recommended VMware ESXi version, see Deploying Avaya Breeze® platform.
-
VMware vSphere client installed to access the ESXi server. For the recommended VMware vSphere version, see the VMware documentation.
-
Session Manager requires a Listen Port with the Listen Port as 5061, Protocol as TLS, and Default Domain as the login domain of endpoint devices. Without this, PPM will fail for SIP endpoints. For more information, see Administering Avaya Aura® Session Manager.Note:Ensure that you select the Endpoints check box for the Listen Port. For more information, see
Presence and IM fails on SIP endpoints due to the PPM getHomeCapabilities fault.
In the following checklist:
-
n refers to the number of Presence Services instances in the cluster.
-
s refers to the number of deployed Session Managers.
Checklist for deploying a multi-server Presence Services cluster
|
No.
|
Task
|
Reference
|
|
|---|---|---|---|
|
1
|
Administer n DNS A records to resolve Avaya Breeze® platform hostname to Avaya Breeze® platform Management Module IP address.
|
—
|
|
|
2
|
Administer one DNS A record to resolve System Manager hostname to IP address.
|
—
|
|
|
3
|
Administer n DNS A records to resolve Presence Services Cluster FQDN to Avaya Breeze® platform Security Module IP address.
Do not add any reverse lookup or associated pointer (PTR) records for any of these IP addresses.
|
||
|
4
|
Administer n DNS A records to resolve the Avaya Breeze® platform Security Module FQDNs. The FQDNs must be in the following format: <management-hostname>-sm100.domain. For example, mybreeze101-sm100.mycorp.com, where the FQDN of the management address is mybreeze101.mycorp.com.
Also, add reverse lookup or associated pointer (PTR) records for those IP addresses.
|
—
|
|
|
5
|
Deploy n latest available Avaya Breeze® platform instances on m host servers.
|
||
|
6
|
Confirm that n Avaya Breeze® platforms successfully replicate with System Manager.
|
||
|
7
|
Administer n Avaya Breeze® platform SIP Entities.
|
||
|
8
|
Administer n*s Entity Links between Avaya Breeze® platform and Session Manager.
|
||
|
9
|
Administer one Presence Services Cluster SIP Entity.
|
||
|
10
|
Administer s Entity Links between Presence Services Cluster SIP Entity and Session Managers.
|
||
|
11
|
Administer n Avaya Breeze® platform servers.
|
||
|
12
|
Administer one Avaya Breeze® platform cluster and assign n Avaya Breeze® platform servers.
|
||
|
13
|
Do the following:
Note:
If the Avaya Session Border Controller for Enterprise is present in Avaya Aura® solution and Presence Services is cluster of n nodes, then you must do the following:
|
See Certificate management. |
|
|
14
|
Administer one Presence Services on Avaya Breeze® platform Managed Element.
|
||
|
15
|
Administer n System Manager LHNR entries to resolve Presence Services Cluster FQDN to Avaya Breeze® platform Security Module IP address.
|
||
|
16
|
Administer Avaya Breeze® platform alarming.
|
See Deploying Avaya Breeze® platform.
|
|
|
17
|
Specify the IP addresses of the SBCE or proxy servers for Presence Services cluster load balancing.
|
||
|
18
|
Load Presence Services snap-in.
|
||
|
19
|
Ensure that at least one routing domain is configured on System Manager.
|
||
|
20
|
Install Presence Services snap-in on Avaya Breeze® platform cluster.
|
||
|
21
|
Administer Presence Services System service attributes.
|
||
|
22
|
Restart Presence Services.
|
||
|
23
|
Verify that Presence Services snap-in is ready to support Presence and IM.
|