Presence 8.1 Building 3 Breeze OVA in a single cluster

[bankingguy]

thread690-1796663

In relation to my previous post regarding Presence 8.1

My current status now is i have uploaded 3 OVA of Breeze 3.6 with the following hostname and FQDN

192.168.40.11 - hknode1.myproddom.com
192.168.40.12 - hknode1a.myproddom.com (SM100)
192.168.40.13 - hknode2.myproddom.com
192.168.40.14 - hknode2a.myproddom.com (SM100)
192.168.40.15 - hknode3.myproddom.com
192.168.40.16 - hknode3a.myproddom.com (SM100)
192.168.40.17 - hknodecluster.myproddom.com

The cluster is built based on the following IP address and hostname. Replication is in Sync all 3 nodes, SIP Entities are all UP. The question now for me is how to build the configuration for Presence. Here is what i have so far.

1. The Presence Snap-in is already installed in the 3 nodes
2. I have created 1 SIP entity for the Node1 using the SM100 interface IP address 192.168.40.12. The entity links to SM is port 5062 and on Presence its 5061. Avaya's recommendation well as per backbone's comment is to put "-sm100" on the hostname assign for the SM100 interface. So i used hknode1-sm100.myproddom.com
3. Should i build 2 more SIP entity for Node2 and Node3 SM100? - yes or no?
4. If item 3 above is yes, should i use hknode2-sm100.myproddom.com & hknode3-sm100.myproddom.com
5. If No, should i use LHNR and put hknode1-sm100.myproddom.com and configure the 3 IP addresses of all SM100?
6. Or Should i use the "cluster" FQDN when i build the presence SIP Entity and use the Cluster IP address define above and follow the rest of the steps done in step 2.

Appreciate if you can answer me line by line so I can track how can i progress.

 

[kyle555]

What I see immediately wrong is that you don't have a Presence Cluster FQDN that points to all your SM100s.
You need 2 cluster FQDNs - one for the Breeze cluster, with its own IP - like you would for any Breeze cluster.
And, you need a Presence cluster FQDN that doesn't have an IP but instead has A records to the SM100s of the Breezes in the cluster.
So, i'd just add hkprescluster.myproddom.com and resolve it to 12,14,16.



See p.45. I spent the better part of an afternoon trying to read through that and make sense of it. Step 3 is the part you're missing.
Read page 44 - for a 5 server cluster, presuming dedicated ESXi hosts, it says you need 16 IPs and a Presence Cluster FQDN - 5 ESXi, 5 Breeze mgmt, 5 SM100, 1 Cluster IP and 1 Presence FQDN. The Presence FQDN doesn't map to the cluster IP, it maps to all the IPs of the SM100s

https://downloads.avaya.com/css/P8/documents/101058218

Personally, I like breaking it into 10's for the IPs.
So, 192.168.40.1x for the Breeze mgmt
192.168.40.2x for the SM100s
192.168.40.3x for the cluster IPs

192.168.40.11 - breezec1s1.myproddom.com
192.168.40.21 - breezec1s1-sm100.myproddom.com
192.168.40.12 - breezec1s2.myproddom.com
192.168.40.22 - breezec1s2-sm100.myproddom.com
192.168.40.13 - breezec1s3.myproddom.com
192.168.40.23 - breezec1s3-sm100.myproddom.com
192.168.40.31 - breezec1.myproddom.com

and then in your DNS, the FQDN presencec1.myproddom.com would have A records to .21,22,23

When creating the -sm100 FQDN A records you'd also add the reverse lookup.

So, if you did nslookup for presencec1.myproddom.com, you'd get results for 21,22,23

If you did nslookup on 192.168.40.21, you'd get breezec1s1-sm100.myproddom.com

 

[bankingguy]

Thank you, so the presence cluster FQDN that you mentioned will be used as my SIP entity?

 

[kyle555]

That's steps 7 thru 10

So, you'll have entities for each SM100. Build a entity link 5061-->5061 for each Breeze to each SM

Then see the section named:
Administering System Manager LHNR to resolve Presence Services Cluster FQDN to Avaya Breeze® platform Security Module IP address

Then you'll build presencec1.myproddom.com in LHNR with 2 entries that map to the SM100s on port 5061 and build another entity with FQDN presencec1.myproddom.com and have entity links from SM port 5062 to Presence FQDN entity port 5061