IMG 1010 - GCEMS_Redundancy_Configuration
- Kelli Higdon
Â
Installation:
The first step to configuring GCEMS redundancy is done when GCEMS is initially installed on the GCEMS server. Questions of whether redundancy is going to be configured are asked. Follow the procedure below to configure the GCEMS as a redundant system.
Steps:
Load the IMG_10.5.x.bin and IMGUserInterface_10.5.x.bin file into /home/excelsw/ftpBuilds folder.
As a SuperUser, install the GCEMS file. See IMG 1010 - Installing GCEMS Software. During installation you will be asked whether this will be a redundant system. Select 1 = Yes. See below.
In next screen decide whether this will be configured as primary or not. If GCEMS redundancy is being configured and the GCEMS application on this host will be the Primary select Yes. When configuring the secondary GCEMS for this redundant system select No.
ÂEnter IP addresses for Primary and Secondary Host. See below. It is important that the IP address given to the primary host is the IP address from the host given Primary status from previous step above.
Follow the rest of the prompts and install IMG_10.5.x.bin.
Install IMGUserInterface_10.5.x.bin. See IMG 1010 - Installing GCEMS Software for more information.
Once both IMG_10.5.x.bin and IMGUserInterface_10.5.x.bin have been installed, add the IP addresses of the PC's that the Primary and Secondary GCEMS are located on to the /etc/hosts file. See example below.
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
10.129.39.53 pc1_gcems_pri
10.129.39.59 pc1_gcems_secÂ
Configuring GCEMS as a Redundant System by Script (Linux only):
Steps:
Stop GCEMS.
As a SuperUser, go to /opt/dialogic/osconfig on the GCEMS server:
To add redundancy, run redconfig and you will be asked whether this will be a redundant system. Type y. Enter IP addresses for Primary and Secondary Host. See below.
To remove redundancy configuration, run redconfig and you will be asked whether this will be a redundant system. Type n. See below.
Â
Â
Starting GCEMS:
Steps:
Start GCEMS.
Start ClientView.
Once ClientView opens select the IMG EMS object and the following pane will appear.
Â
IP Address 1Â - IP Address of the Host which Primary GCEMS is running.
Port Number 1Â - Port number being used to communicate with IMG.
Connection State 1Â - What is the state of the connection between IMG and Primary GCEMS.
IP Address 2Â - IP Address of the Host which Secondary GCEMS is running.
Port Number 2Â - Port number being used to communicate with IMG.
Connection State 2Â - What is the state of the connection between IMG and Secondary GCEMS.
Number of App Count - This is the number of applications (DataManager, GateManager, etc) that are connected to the GCEMS application. This can also be seen in the Object Table. See screen capture below showing.
Â
Additional Information:
If the system was loaded as a Redundant System (Primary/Secondary GCEMS) the Defaults file located at /opt/dialogic/IMG/GateControl EMS will have the entries for RLLC and LLC along with their correct IP addresses as displayed below.
 |
llc_host:10.129.39.53 |
rllc_host: 10.129.39.59 |
When GCEMS on the primary/active server is started, GateManager on the primary/active server creates a system.cfg file which is used to configure the IMG. When the GCEMS on the secondary/standby server is started, it synchronizes with the GCEMS on the primary server and the system.cfg file is created using DataManager. Because the system.cfg file is created by GateManager on the primary/active GCEMS server and the system.cfg file on the secondary/standby GCEMS server is created by DataManager the two files are not the same size. The system.cfg file created by DataManager is formatted differently. This however has no affect when configuring the IMG. The configuration will be the same whether the IMG is configured from the primary or secondary server.
Along with the system.cfg file, the System_DataModel.xml and System_RouteTable(n).xml files are also automatically synchronized on the Standby GCEMS server. As changes are made in ClientView and written to the active GCEMS server, the same changes are also sent to the standby server to be synchronized.
When a user selects File > Save, the .csa file is written by the ClientView application to the active server only. When the .csa file is written, a folder with the same name is also created and a copy of the System_RouteTable(n).xml files are copied to this subfolder.
The .csa file and subfolder for the route tables are only saved on the active host.
When a GCEMS switchover occurs the following files are loaded by the host that just became active.
 |
GateManager - Loads the system.cfg file and continues to process requests for configuration changes. |
DataManager - Loads the System_DataModel.xml , and System_RouteTable(n).xml files that are used to display the configuration in ClientView. In ClientView if the user selects the File > Save option, ClientView then writes the .csa configuration file and other route tables as described above on this host. |
When a GCEMS switchover occurs, the EventView application displays the switchover process. Below is a screen capture and a step by step description of each step that occurs. The numbers in the screen capture below correspond to the descriptions in the table just below it.
Â
Key | Â |
1 | Primary/Active and Secondary/Standby have sync'd. |
2 | Primary/Active link goes down. |
3 | Secondary/Standby receives configuration file. |
4 | Secondary/Standby receives configuration. |
5 | Subsequent change to configuration causes Secondary/Standby to save. |
Â
Related Topics:
IMG 1010 - GCEMS Installation Script