Dialogic IMG - EMS Installation on RHEL-9
Table of Contents
Configuring IMG2020 EMS on RHEL9
This document provides a step-by-step guide for installing and configuring the IMG2020 Element Management System (EMS) on RHEL9 including necessary packages and dependencies.
Install RHEL9
Ensure that RHEL9 is installed on the target machine before proceeding with the configuration steps.
Register the System
Open a terminal and run the following command to register the system with Red Hat Subscription Manager:
subscription-manager register
Disable SELinux
Open the SELinux configuration file for editing:
vi /etc/selinux/configModify the following line:
SELINUX=disabledSave and exit the file.
Disable the Firewall
Run the following command to stop and disable the firewall service:
sudo systemctl disable firewalld
Install Prerequisite Packages
Install the necessary dependencies and utilities by running the following commands:
yum install yum-utils
yum install httpd
yum install mod_ssl
yum install libstdc++
yum install gcc
yum install gcc-c++
yum install libstdc++.i686
yum install glibc-devel.i686
yum install libcurl-devel.i686
yum install openssl-devel.i686
yum install unzip
yum install wget
yum install git
yum install rpm-build
yum install java-1.8.0-openjdk-devel
yum install systemd
yum install openssh-server
sudo dnf install nss
yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
yum --enablerepo=epel install monit
Install Packages for Redundant EMS
Install additional packages required for redundant EMS functionality:
sudo dnf install rsync -y
sudo dnf install ntpstat -y
sudo dnf install ipcalc -y
sudo yum install -y sqlite
Create the Dialogic User Profile
As a root or superuser, create a group labeled dialogic. The example will create a group profile labeled dialogic in /home. Refer to the example below.
[root@localhost ftpBuilds]# groupadd dialogic
Create a user labeled dialogic under the group dialogic.
[root@localhost ftpBuilds]# useradd -g dialogic dialogic
Add a password of Dial0gic to the user. (Capital D, Zero for 0)
[root@localhost etc]# passwd dialogic
New password: <Dial0gic>
Retype new password: <Dial0gic>
Within the /home/dialogic directory, a new directory labeled ftpBuilds should be created. Open a terminal window and go to /home/dialogic. Create the ftpBuilds directory as a dialogic user.
[dialogic@localhost]$ mkdir ftpBuilds
Install IMG2020 EMS RPM
Install the WebUI RPM package from the specified build path:
sudo rpm -ivh /path/to/webuid-2.3.12-5-LinuxRHEL9.rpm
Configuring NTP
For proper functionality of the redundant EMS, it is imperative that both EMS systems have the exact same time. To achieve this, NTP must be configured on both EMS systems.
You can easily verify if NTP is already configured by typing in “ntpstat”. If the NTP is properly configured then it should show something like this:
[dialogic@localhost osconfig]$ ntpstat
synchronised to NTP server (158.69.125.231) at stratum 3
time correct to within 61 ms
polling server every 1024 s
Configuring the ssh key
The redundant EMS systems synchronize database files using the rsync command. It is therefore required to configure the ssh key on both systems for proper functionality.
Generate key
Switch to dialogic user, Type in the following: “ssh-keygen -t rsa” then type in enter multiple times and accept overwrite questions until the public key is saved.
Copy the key
Type in the following: “ssh-copy-id dialogic@IP_ADDRESS_OF_SECONDARY” and type in “yes” followed by the dialogic user password (Dial0gic by default). Here’s an example:
[dialogic@Redhat6 bin]$ ssh-copy-id dialogic@172.21.5.236---
The authenticity of host '172.21.5.236 (172.21.5.236)' can't be established.
RSA key fingerprint is 97:44:3b:fb:79:ed:a8:cb:81:5b:92:ba:fb:c2:db:c2.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '172.21.5.236' (RSA) to the list of known hosts.
dialogic@172.21.5.236's password: <------ Dial0gic
Please verify that this is done on both EMS systems.
Configuring the redundant EMS
Each EMS system has to be configured as the primary or secondary system. The file used to for the EMS configuration is named /opt/dialogic/bin/EMSRedund.conf. Type in the following commands to configure the EMS system:
cd /opt/dialogic/bin
./EMSSetup.sh
You should see this :
###################################################################
# EMS REDUNDANCY CONFIGURATION #
###################################################################
Press 1 for STANDALONE, 2 for PRIMARY or 3 for SECONDARY:
If this is the primary EMS, type in 2 and if it’s the secondary system type in 3. If we want to revert back to a standalone EMS without any redundancy, type in 1.
EMS system set in PRIMARY mode - EMS redundancy will be configured
Enter IP address of peer EMS: 172.21.5.123
In this example we’ve entered 2 as we are configuring this EMS as the PRIMARY EMS. It then asks for the IP address of the peer EMS (IP address of SECONDARY EMS in our example).
Enter mail address for EMS notifications (Optional): someone@xyz.com
We can enter an e-mail address if we want to receive an e-mail notification when the EMS changes state.
Once this is entered the content of the EMSRedund.conf file is displayed. Verify that everything is correct. Finally it shows
###################################################################
# EMS REDUNDANCY CONFIGURED #
# #
# Press ENTER - This will restart the EMSRedund process #
###################################################################
Press enter and the EMSRedund process will restart with the new configuration.
Please verify that both EMS systems are properly configured.
Checking status of EMS
We can verify that status of the EMS by typing in the following: “service webuid status”
As an example, the primary system is the active system and we get:
[root@Redhat9 bin]# service webuid status
WebUI Status...
oampManager (pid 29765) is running...
DBSyncEntity (pid 29860) is running...
SS7Redund (pid 29851) is running...
backupmgr (pid 13958) is running...
EMSRedund.sh (pid 29272) is running...
We see that all services are running. We can use the web browser to connect to this EMS system.
Calling the same “service webuid status” command on the secondary system, we should get:
[dialogic@localhost bin]$ service webuid status
WebUI Status...
oampManager is stopped
DBSyncEntity is stopped
SS7Redund is stopped
backupmgr is stopped
EMSRedund.sh (pid 25949) is running...
We see that all services are stopped except for the EMSRedund process. We will not be able to logon with the web browser on this standby system.