Add redundancy to an existing non-redundant GCEMS setup
- Kelli Higdon
Introduction
Dialogic IMG 1010 Integrated Media Server documentation describes how to install two redundant Dialogic Gate Control Element Management (GCEMS) servers in a new installation, but does not describe how to migrate to a redundant configuration after you have already established a single server (non-redundant) configuration.
This article describes how to implement redundant GCEMS servers starting with a single stand-alone (non-redundant) server, by adding a single new server.
If you wish to install two new servers please see the following article: Migrating from an existing GCEMS to two new redundant servers
Procedure
Below is a step-by-step procedure for the migration:
1. Query All Tags on the current Standalone server by clicking on the Query All Tags tab in Clientview
2. Click on the Refresh Config tab in ClientView
Click on the following image to display it full-size
3. Copy over the dhcpd.conf from the existing standalone server located at /etc/ to the new Secondary GCEMS server. Also, be sure to update the next server IP of the secondary GCEMS server. Below is an example of a dhcpd.conf file. In the example the next-server 10.129.52.133 is that of the Primary Server IP. You will also need to update the Secondary server's dhcpd.conf with a next-server IP of that secondary server. In the case you are using an SD card, be sure to update the server address in the bootup.cfg.
host IMG_CPU1_T1
{
hardware Ethernet 00:20:1C:11:04:fd;
fixed-address 10.129.52.134;
# ftp server name (IP Address of the LINUX PC running FTP)
next-server 10.129.52.133;
# IMG bin file (software load)
#option routers 10.129.52.1
filename "ftpBuilds/img1010_ver1053132_id0101.bin";
option Host_1010_Flag 0;
4. Copy the IMG licenses from /opt/dialogic/common/license/ directory over from the current standalone server to the new secondary GCEMS server in the same /opt/dialogic/common/license/ location.
5. Close Clientview and GCEMS on the standalone server by clicking on the Stop GCEMS desktop icon
6. Install the GCEMS software on the 2 servers according to Dialogic IMG documentation for IMG 1010 - GCEMS_Redundancy_Configuration
7. Start GCEMS on the Primary GCEMS by clicking on the StartGCEMS icon on the desktop and when prompted enter "2" to not load new config. When selecting this option the Primary GCEMS will load the current system.cfg and will not result in any downtime.
8. Start GCEMS on the Secondary GCEMS and when prompted enter "2" to not load new config. When selecting this option the Primary GCEMS will ftp the current system.cfg and system_datamodel.xml to the Secondary GCEMS.
9. Clientview can be ran on each of the GCEMS servers, however it is normal to start Clientview first on the Primary as it will have the configuration privileges. When launching Clientview you will need to either enter the IP or hostname of the Primary and Secondary GCEMS servers.
Note:
In the case of Free Radius, SNTP, MRTG, and CACTI should normally be installed before the migration (see the Dialogic IMG 1010 and 1004 documentation for more information).
Back out/Revert
For any reason, the GCEMS migration may be reverted to its pre-migration state, using the following steps:
1.Close Clientview and Stop GCEMS by clicking on the desktop icon on both the Primary and Secondary GCEMS servers
2. Install the GCEMS/Clientview software on the Primary servers according to Dialogic IMG documentation for a standalone GCEMS setup, which is the default install.
3. Start GCEMS on the Standalone server by clicking on the Start GCEMS desktop icon and select "2" to not load new config.
4. Launch Clientview by clicking on the Clientview desktop icon
6. Query All Tags by clicking on the Query All Tags tab.
Product List
Dialogic IMG 1010 Integrated Media Gateway
Dialogic IMG 1004 Integrated Media Gateway
Dialogic Gate Control Element Management System (GCEMS)
Glossary of Acronyms / Terms
CLI: Command Line Interface
SNTP: Signaling Network Time Protocol
MRTG: Multi Router Traffic Grapher