Presence Server 6.2.x in Cluster Mode (Load Balancing ... · Presence Server 6.2.x in Cluster Mode (Load Balancing) Installation, configuration and tests updated by RSE EMEA

Presence Server 6.2.xin Cluster Mode

(Load Balancing)(Load Balancing)

Installation, configuration and tests

updated by RSE EMEA

Cluster Design

Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 2

In this exemple, we will setup a cluster with 3 Presence Services servers

running in version 6.2.1 Patch 10 and SMGR version 6.3.

The main purpose of the SDNS component is to receive packets addressed to

the global presence domain and redirect them to the correct IPS instance that

actually hosts this user.

IPS uses a two-step User Regionalization algorithm to assign users to IPS

instances. First, a user is assigned to a region using the Group Lookup step

and, then, assigned to a particular IPS instance in this region using the Modulo

algorithm.

Based on this User Regionalization algorithm, the packet redirection is also

implemented as a two-step process as follows.

Presence cluster – General Overview


implemented as a two-step process as follows.

Packet Redirection algorithm :

- Each collection of regional IPS servers is assigned an internal sub-domain

name in the form of "region.presence_domain", e.g. "eu.pres.avaya.com".

- Each IPS SDNS component will register for both "presence_domain" and its

"region.presence_domain".

When it receives a packet for a user, it first checks which region a user belongs

to (using the Group Lookup algorithm). If the user belongs to the local region, it

will redirect the packet to the appropriate IPS server (JSM) in this region (based

on the Modulo algorithm). Otherwise, it will redirect the packet to the sub-

domain "user_region.presence_domain", which will be routed by Jabber to

SDNS component in that region.

Presence cluster – General Overview


PS 6.2.x requires RHEL 5 Update 3 or above[root@fr0567svr00920 Server]# cat /etc/redhat-release

Red Hat Enterprise Linux Server release 5.7 (Tikanga)

1/ check the SELinux if disabled when RHEL is already installed ?

[root@presence6 ~]# vi /etc/sysconfig/selinux

# This file controls the state of SELinux on the system.

# SELINUX= can take one of these three values:

# enforcing - SELinux security policy is enforced.

# permissive - SELinux prints warnings instead of enforcing.

Installing Linux – prerequisites for each PS


# permissive - SELinux prints warnings instead of enforcing.

# disabled - SELinux is fully disabled.

SELINUX=disabled

# SELINUXTYPE= type of policy in use. Possible values are:

# targeted - Only targeted network daemons are protected.

# strict - Full SELinux protection.

SELINUXTYPE=targeted

If you changed from Enabled to Disabled or vice versa, you need to restart the

machine for the change to take effect.

[root@presence6 IPS]# reboot

[root@presence6 IPS]# /usr/sbin/getenforce

Disabled

2/ check if Firewall is disabled ?[root@presence6 ~]# service iptables save

[root@presence6 ~]# service iptables stop

[root@presence6 ~]# chkconfig iptables off

[root@presence6 ~]# service iptables status

Firewall is stopped.

[root@fr0567svr00927 ~]# chkconfig --level 2345 iptables off

[root@fr0567svr00927 ~]# chkconfig --list | grep iptables



[root@fr0567svr00927 ~]# chkconfig --list | grep iptables

iptables 0:off 1:off 2:off 3:off 4:off 5:off 6:off

3/ How to synchronize with a NTP server ? Edit the /etc/ntp.conf file

a/ First we specify the servers you're interested in (save & quit) :

# --- OUR TIMESERVERS -----

server ypslave3.dr.avaya.com # drccd.dr.avaya.com [135.9.1.72]

b/ restart the NTP process every time you make a change onto the configuration file :

[root@saumaes ~]# service ntpd start

[root@saumaes ~]# service ntpd stop

[root@saumaes ~]# service ntpd restart

c/ To get NTP configured to start at boot, use the line :

[root@saumaes ~]# chkconfig ntpd on



[root@saumaes ~]# chkconfig ntpd on

d/ To test whether the NTP process is running use the command

[root@saumaes ~]# pgrep ntpd

e/ Determining If NTP Is Synchronized Properly :

Before sync : [root@saumaes ~]# ntpq –p

remote refid st t when poll reach delay offset jitter

drccd.dr.avaya. 198.152.6.12 4 u 32 64 3 0.456

26.359 5.751

After about a minute : it got synchronized (* in front of the server name)[root@fr0567svr00916 ~]# ntpq –p

remote refid st t when poll reach delay offset jitter

*drccd.dr.avaya. 198.152.6.12 4 u - 64 377 166.322 38116.1 5.669


4/ Minimal RHEL installation requires following additional packages (which can be found on the RHEL distribution media) to support PS:

– watchdog[root@]# cd /media/RHEL_5.7\ i386\ DVD/Server/

[root@Server]# rpm -i watchdog-5.6-1.el5.i386.rpm

warning: watchdog-5.6-1.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186

[root@Server]# rpm -qa watchdog

watchdog-5.6-1.el5

– libtool-ltdl

Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.

– libtool-ltdl[root@Server]# rpm -hiv libtool-ltdl-1.5.22-7.el5_4.i386.rpm

warning: libtool-ltdl-1.5.22-6.1.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186

Preparing... ########################################### [100%]

1:libtool-ltdl ########################################### [100%]

– also ensure that the runlevel is set to 5.[root@fr0567svr00920 Server]# runlevel

N 5

8

5/ Java SDK is a prerequisite for Software Only. For System Platform deployment , it comes as part of the template.

� JDK 1.6. Update 18 is recommended (jdk-1.6.0_18) as minimum

– http://java.sun.com/products/archive/j2se/6u18/index.html

� Note that Java SDK has to be installed where it is accessible to non root users as well. e.g. /usr/java/

How to Install Java SDK



� How to Install Java SDK– Change to the directory in which you want to install. cd /usr

– Create a Java folder : sudo mkdir java cd java

– Change the permission of the file you downloaded to be executable.

sudo chmod 755 /usr/java/jdk-6u18-linux-i586.bin

– Start the installation process : sudo ./jdk-6u18-linux-i586.bin

9

Installation of Java SDK B for each PS

� Add Java configuration to environment variablesvi /etc/profile

JAVA_HOME=/usr/java/jdk1.6.0_18

PATH=$JAVA_HOME/bin/:$PATHexport PATH JAVA_HOME

– Apply the changes to the current shell


source /etc/profile

� The installation of Java is now complete.

[root@fr0567svr00920 java]# java -version

java version "1.6.0_18"

Java(TM) SE Runtime Environment (build 1.6.0_18-b07)

Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode, sharing)

10

Verify /etc/hosts file for each PS� The /etc/hosts file must contain the following two lines:

– 127.0.0.1 localhost.localdomain localhost

– Machine_IP host_FQDN host_name

For example :

– 127.0.0.1 localhost.localdomain localhost

– 198.152.1.2 myserver.mycompany.com myserver

� The installer will check above


� The installer will check above

11

#LAB exercise example :

127.0.0.1 localhost.localdomain localhost

135.64.96.85 fr0567svr00920.rsesaumur.avaya.com fr0567svr00920 #presence1



135.64.96.182 smgr-rse.rsesaumur.avaya.com smgr-rse #System Manager

135.64.96.159 fr0567svr00925.rsesaumur.avaya.com fr0567svr00925 #1XCES_server

Verify DNS Look Ups

�Check you can resolve to the FQDN of the System Manager and all other servers e.g. 1XCEServer, Presence Services.

– Edit /etc/hosts files on servers

� Edit /etc/resolv.conf


� Edit /etc/resolv.conf [root@fr0567svr00927 /]# more /etc/resolv.conf

search rsesaumur.avaya.com

nameserver 135.64.96.227

� nslookup <host>

�Changing IP Address or FQDN after install is not currently supported

12

Installing Presence Server Software

�Copy Install Bundle Zip File to System

– PS-6.2.1.0-<Build No>.zip

– Unzip to get all required files : [root@fr0567svr00927 ~]# unzip PS-6.2.1.0-201.zip -d PS-6.2.1.0

Archive: PS-6.2.1.0-201.zip


inflating: PS-6.2.1.0/PS-6.2.1.0-201.sh

inflating: PS-6.2.1.0/PS-6.2.1.0-201.jar

extracting: PS-6.2.1.0/CAF.zip

inflating: PS-6.2.1.0/autoInstall_PS.properties

inflating: PS-6.2.1.0/autoUpgrade_PS.properties

inflating: PS-6.2.1.0/autoUninstall.properties

inflating: PS-6.2.1.0/IPS_RTC_01.00.00.msi

13

Graphical Install of PS

�To Run the Graphical Installation

– Needs an X Windows environment (i.e. vncserver)

• Could log directly into the Linux Server.

• Could use vncserver to drive the installer on another machine.

• Could ssh –X into the Server so that the display is exported


• Could ssh –X into the Server so that the display is exported

– ./PS-6-2.1.00-<Build No>.sh –ci

– Enter an Encryption Key (Password) or blank

• This protects the installer configuration parameters

• Must be remembered – used during upgrades and un-install

14

Software only GUI based Installation Screens



The Installation Path is

fixed – this panel lets the

user know what the

installer is going to do

Then click Ok


Then click Ok

To create the target dir


Confirmation of packages

being installed :

-SAL agent

-Presence Services



Note: It is recommended,

(but not required) that all

of these tests pass.



Because the Standard

Installation mode applies

reasonable defaults to

most parameters, this is

the recommended

installation mode.



Note: Host name must not be

an IP Address but a FQDN

that is of course resolved

from Presence Services

servers.

Note: The System Manager


Note: The System Manager

login is “admin” or another

equivalent created.


In cluster mode, the Realm of each PS server must be different

as shown (presence1, presence2, presence3, ..etc)

And Router Service Name has to be the same for each PS core

as this is the Presence Services SIP domain.



Check those 2 options :

- Load Balancing for each PS

server in the cluster.

- AES Collector : to support

h323 phones.



Multiple Session

Managers can be

configured by entering a

comma or space

separated list of their IP

addresses



Add a valid TSAPI created

account for AES Collector

to connect to AES and

get/send presence states.



For Load Balancing (or

cluster mode), enter the JSM

value of each PS as follows:

jsm-1.presenceX

presenceX is the Realm value

of the concerned PS server.


of the concerned PS server.

Need System Manager Information






e.g. avaya123 – from System Manager � Security �Certificates � Enrollment Password



PS installation starts B


You should get those screens after about 40 minutes, click OK & done.


Eventual installation issue

While installing PS, PS installation hangs at step 36

Installer Hanging - Step 36

Description

Installation hangs at step 36 on "Waiting for 10 seconds for registration to complete"

Details

SMGR cannot connect to the PS server for registration

Solution(s)

Check that there is an entry on the SMGR system for the current PS server under /etc/hosts file

Check that the PS /etc/hosts file does not have an entry for its hostname under 127.0.0.1, the

entry should only be for a non-localhost IP address.

For 2 An example of an incorrect entry

127.0.0.1 pssrv.du.rnd.avaya.com pssrv localhost.localdomain localhost

192.168.122.3 pssrv.du.rnd.avaya.com pssrv


The correct entry should be

127.0.0.1 localhost.localdomain localhost

192.168.122.3 pssrv.du.rnd.avaya.com pssrv

Comments¶

1. johnreynolds --

The Redhat installer by default creates the hostname under the 127.0.0.1 in the /etc/hosts. In

future the installer may check and correct this.

Post Installation

�To secure the system the installer will prevent most users, including root, from remotely logging into the server. If you require root access then you will need to remotely log in as either “craft” ,“cust”, “init” or “rsaccess” and then su to root.

�Set up the Licensing on the System Manager server


�Set up the Licensing on the System Manager server

�Change the passwords for the services users such as “craft”

�If you are upgrading from an earlier release of PS 6.0 (post alpha), then you can use the update utility to restore your configuration.

�For Load Balancing, configure the cluster as explained here.

32

Post-installation : WebLM Presence license

Once licence file is added, check the licence usage per PS on the SMGR Menu


Presence Administration

Log in to the Presence Services XCP

Controller Web interface

https://<IPaddress>:7300/admin

The default user name and password cust and cust01 respectively.


Integrating Presence Services with Session Manager

Check if the Session Manager IP address is set ?

If you did not enter the Asset IP address then, you can enter it after the Presence Services

installation.

1. Log in to Presence Services XCP Controller Web interface > advanced view.

2. Edit Global Router settings

3. Check the IP address of the Session Manager if setup in ”Mutually Trusted Hostnames”

field

4. If not there, add it and click Submit

5. Restart Presence Services


5. Restart Presence Services

Adding Presence Services as a SIP entity in System Manager

1. Log in to System Manager ( as « admin » account)

2. On the System Manager Dashboard, click Routing.

3. On the System Manager left navigation pane, click SIP Entities.

4. On the SIP Entities page, click New.

5. On the SIP Entities Details page, enter the following details:

a. Name. Example, PresenceServer

b. FQDN or IP Address. Presence Services IP address

c. Type : Presence Services

d. SIP Link Monitoring. Use Session Manager Configuration



d. SIP Link Monitoring. Use Session Manager Configuration

6. Click Commit.

Adding an Entity Link

1. Log in to System Manager.

2. On the System Manager Dashboard, click Routing.

3. On the System Manager left navigation pane, click Entity Links.

4. On the Entity Links page, click New.

5. On the Entity Links page, enter the following details:

a. Name. Link name (Example: PresenceServerLink )

b. SIP Element 1. Select Session Manager from the list

c. Protocol. TLS

d. Port. 5061



d. Port. 5061

e. SIP Element 2. Choose the same Presence Services name you created in the

previous procedure (Example: PresenceServer )

f. Port. 5061

6. Select Trusted.

7. Click Commit.

Administering System Manager for Presence Services

Check if set as follows for each PS server in SMGR Menu Home /Services / Inventory / Manage Elements ?

Click on each PS server anc click on «Show Status »


Administering System Manager for Presence Services


Presence configuration properties

Administering Presence configuration properties

1. Log in to the Avaya Aura® System Manager Web interface as an administrator.

2. On the System Manager Dashboard, under Elements, click Presence.

3. On the Presence page, click Configuration in the left navigation pane.

You can review all global Presence configuration properties on this page


Check if PS Replica Node is sync’ed ?SMGR Menu : Home /Services / Replication


Post-installation configuration

On each of the Presence Services node, you must modify the JID of a

provisioning-admin user. The JID of a provisioning-admin user is a hidden

configuration parameter within the presence container configuration.

1. Log in to the Presence server as a root user.

2. Go to the /opt/Avaya/Presence/jabber/xcp/etc directory.

3. Edit the presence-container-1.xml file and make the following changes

Change the configuration parameter, adminUserId, to include the number of the

node associated with the provisioning admin user. For example, in the three

nodes, cluster node 1 has a realm of presence1, node has a realm of


nodes, cluster node 1 has a realm of presence1, node has a realm of

presence2, and node 3 has a realm of presence 3. Thus, change the

provisioning admin user to as [email protected] on

node 1; [email protected] on node 2; and cluster-

[email protected] on node 3.

<provisioning adminUserId="[email protected]"/>



Configuring the Single Domain Name Support (SDNS) component


1. Components area, click Go to Add new SDNS component.

2. In the Single Domain Name Support section, set the Runlevel field to 5.

3. In the Single Domain Name Support Configuration section, perform the

following:

a. Set the Number of threads to dedicate to Single Domain Name

Support tasks field to 6.

b. Select Modulo Mapping Algorithm


b. Select Modulo Mapping Algorithm

To save the changes, click Submit.

Configuring the Router to Router component


1. Components area, from the Add a new drop-down list, select Router-to-

Router Connection and then click Go.

2. In the Router-to-Router Connection section, set the Runlevel field to 10

Node 1 : R2R to 2


Node 2 : R2R to 3

Node 3 : R2R to 1

Modifying JSM configuration


To provision users on a node, you must define the provisioning-admin user in the

admin user list of a JSM.

1. In the Routers area, click Edit next to the JSM (Presence Session

Manager) component.

2. In the Presence Administrators field, add the component name from each

of the other remote nodes in the cluster and add the provisioning-admin

user from each of the remote Presence Services nodes.


For example, [email protected]

provisioning.presence1

[email protected]


[email protected]


1XC presence config & checking

In the 1XC Presence settings, enter either :

-Presence1

-Presence2

-Or Presence3

Then once logged in, the Presence icon should be displayed in front of the user


Then once logged in, the Presence icon should be displayed in front of the user

Then add contacts as Favorite with the IM field = extension id to get its presence.

1XC presence config & check user

registrations

command to display the USERs list from each PS server:[root@fr0567svr00920 ~]# psql -U presence_user -d presence -c "select * from csuser;“

id | updatedatetime | version | commpassword | encryptionkeyid| isdeleted | isenabled | loginname| contactlistdefaultaclid | userdefaultaclid

-----+-------------------------+---------+------------------+-----------+------------------------------+-------------------------+------------------

800 | 2013-05-16 13:19:03.928 | 0 | JN0HVSoUz8yEVovltiIlsA== | febd0291-016d-4c45-9d0b-0d2ab3c772d7 | f | t | [email protected]

86 |750 | 700

801 | 2013-05-16 14:54:37.039 | 0 | QzeFPYkt0P63dB2/R08+AA== | 4d479518-0826-43e6-9f98-24c99da5d525 | f | t | [email protected]

86 |751 | 701

650 | 2013-04-02 15:17:22.037 | 4 | jUgYh7Kijj+l0REXZXDqNA== | a548bed2-2f6d-439b-95b5-74014719ac36 | f | t | [email protected]

86 |600 | 550

602 | 2013-01-31 15:33:07.576 | 1 | O+ZcMeLFWa0RJQIBnbEwcw== | 46fb6af9-8a6f-4fdc-a579-0e72cab9190d | f | t |

[email protected] 86 552 | 502

904 | 2013-07-08 10:30:19.12 | 3 | bpeGfCdxF+E8Gl3HK1/LcA== | 9b3c2b8a-b1e3-452b-b2cc-0dbeeab61242 | f | t | [email protected]

86 |854 | 804

902 | 2013-06-21 12:04:18.636 | 2 | VSQYwzqgd22qvQD4zMIlOg== | 2e54e8b8-73d9-404f-8fb0-0977c58ca8a2 | f | t | [email protected]


902 | 2013-06-21 12:04:18.636 | 2 | VSQYwzqgd22qvQD4zMIlOg== | 2e54e8b8-73d9-404f-8fb0-0977c58ca8a2 | f | t | [email protected]

86 |852 | 802

903 | 2013-06-21 12:08:58.712 | 2 | mX612z9YpFHopiWY+3e0oA== | 415640c8-4737-44fb-8b70-de23e142026e | f | t | [email protected]

86 |853 | 803

700 | 2013-04-25 17:46:24.611 | 1 | 9NEcqyUJzakcrx3eyG3LVw== | 51a32bb5-4102-4b3f-bc18-b58129cea519 | f | t | [email protected]

86 |650 | 600

601 | 2013-01-29 11:56:30.568 | 3 | tXdGmzGpntIeCQWsRwLzYw== | b59cf846-b699-42da-812a-a3a48c395efd | f | t |

[email protected] 86 551 | 501

900 | 2013-06-20 16:39:58.884 | 2 | HEvxkvXIRzuOibPYXjAqrg== | 2b7f94b5-bd3f-4108-a336-d060669cd222 | f | t | [email protected]

86 |850 | 800

951 | 2013-08-27 17:26:08.594 | 1 | Ue2E2S+vX175OoF2KZOQ2A== | c7c9aea8-6c57-4e26-bcbc-570cd386b70b | f | t | [email protected]

86 |901 | 851

950 | 2013-08-27 12:38:49.92 | 2 | 0dq4KuYo0ITx12iaKdCJKQ== | 8e0183ef-237f-4ef3-9fc9-166b4bdf2d0c | f | t | [email protected]

86 |900 | 850

850 | 2013-05-27 15:51:19.482 | 3 | zmA1Ge1VQ215M4gUk5GDYQ== | 121d43fb-4098-4318-86ff-7d24bdad5ffd | f | t | [email protected]

86 |800 | 750

952 | 2013-08-29 18:13:02.741 | 12 | 4d+BfWPNjBSOpTf7R32VfQ== | caed256e-cc61-4e31-bb19-5e6566171015 | f | t | [email protected]

86 |902 | 852

(37 rows)

Each PS server database is replicated from SMGR database, so their content is

exactly the same.

Presence cluster installation checkup Check the installation LOG file : more /opt/Avaya/Presence/ps_process_panel_2012-11-02_06.08.50.log>> If successful you will see the Monit Status showing all processes running

Snippet :

Monit status:(components should be started or starting)

The Monit daemon 5.1.1 uptime: 0m

Process 'xcp_sip_proxy' Does not exist

Process 'xcp_presence_model' Does not exist

Process 'xcp_presence_container' Does not exist

Process 'spiritAgent' running

Process 'log-harvester' running

Process 'postmaster' running

Process 'drs' running

Process 'jabberd' running

Process 'cm' running

Process 'tomcat' running


Process 'tomcat' running

System 'fr0567svr00920.rsesaumur.avaya.com' running

You can also check the PS license file usage (on SMGR menu), which is shared

across each PS node.

As there is no HA (High Availability mode) in load balancing as yet, then if one the

PS server in the cluster is lost or damaged, the concerned 1XC users connected to

it will be loosing the Presence service as shown.

Presence cluster – one PS failure

Before the 1XC logs off, the presence

state of other users remain unchanged.

And the message « connection to the IM

services was lost » is displayed.

After 1XC logs off & logback in, the

presence state of other users remain

unknown. And the message « connection

to the IM services was lost » is displayed.


Even if the 1XC Presence server is changed to another PS Server (from presence1

to presence2 as shown), the issue persists as this is NOT a HA environment.



Presence Services HA is planned for FY14 in next release.

Once the concerned PS fully recovers, all its services are back in green state, then


Without logging out 1XC, the presence is

not reconnecting automatically. After 1XC logs off & log back in, the

presence service is back active & state of

other users is then displayed !


Presence Services HA is planned for FY14 in next release.

Thank youB.

Fred Candeias


Fred Candeias

Regional Solutions Engineering EMEA

Documents

Presence Server 6.2.x in Cluster Mode (Load Balancing ... · Presence Server 6.2.x in Cluster Mode (Load Balancing) Installation, configuration and tests updated by RSE EMEA