Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Migrating from an existing GCEMS to two new redundant servers

Introduction

IMG 1010 Integrated Media Server documentation describes how to install two redundant 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 migrate from an existing standalone GCEMS server to a redundant setup using two new servers.

If you wish to add a single new server to create a redundant configuration please see the following article: Add redundancy to an existing non-redundant GCEMS setup

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 GCEMS Clientview

  2. Observe the status of each of the entities listed below. Entities that were not in service before setting up the redundant GCEMS setup should not be expected to be in service after the upgrade.

Spans
Channels
ISDN D-Channels
SS7 Links
Network Interfaces
ClientView users that are logged in. Notify them of the pending upgrade/migration and have them logoff.

  1. Copy the entire  /opt/dialogic/common/config/ directory to the new Primary Server

  2. Copy over the dhcpd.conf from the existing server (located at /etc/ or /etc/dhcp/ depending on the OS version) to both the new Primary and Secondary servers. Also, be sure to update the next server IP of each new 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. 

If you are using an SD card, be sure to update the server address in the bootup.cfg.

Note: Do not start the dhcpd service on the new servers at this stage.

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;

  1. Copy the IMG Integrated Media Gateway licenses from /opt/dialogic/common/license/ directory over from the current standalone server to the 2 new redundant servers into the same /opt/dialogic/common/license/ location.

  2. Stop Clientview and GCEMS on the standalone server by clicking on the Stop GCEMS desktop icon

  3. Stop the dhcpd service on the standalone server from the /etc directory

[root @etc]# service dhcpd stop

  1. Install the GCEMS/Clientview software on the 2 new servers according to IMG documentation:

IMG 1010 - GCEMS_Redundancy_Configuration

  1. Start the dhcpd service on the new Primary redundant server.

[root@etc]# service dhcpd start

 Note: Do not start the dhcpd service on the Secondary server as there will be a conflict with the primary.

10. Reset an IMG to verify that dhcp is working correctly and that the new File Svr IP is that of the Primary server. You can verify from the CLI via the"b" command:

S/W Version: 10.5.3:132, Apr 28 2010 14:25:22
ROM Version: 3.1.0:000, Feb 19 2008 13:53:02
File Loaded: ftpBuilds/img1010_ver1053132_id0101.bin
File Svr IP: 10.129.52.133 IP Assigned: 10.129.52.134:ffffffe0, Gateway: 10.129.52.129
Reset Reason: Power(1) WdCnt 0, New Image
System Time: WED, JUN 02 2010 14:41:54 UTC
System Time: WED, JUN 02 2010 14:41:54 UTC+0000

Boot Flags: x48 Host Flags: x0
Phys Memory: 512 Megs LNI (name): 0 (IMG_LAB1)
MBRD Serial#: 10201537 IO Serial# (PNI): 10300085
MBRD HW Rev: A15 IO HW Rev#: A5
MBRD Type: x0101 IO Type: x0102 (IO E1/T1 RJ48)
System State: ACTIVE HW Watchdog (dip1): Enabled

11. Start GCEMS on the new Primary Server by clicking on the Start GCEMS icon on the desktop and load NEW config. Launch Clientview and open the current *.csa file copied over in Step 3.

12. Verify that the *.csa has been loaded correctly as noted in step 2, and click on the  Query All Tags tab to confirm the config tags are set

13. Start GCEMS on the Secondary server by clicking on the Start GCEMS icon on the desktop and load the previous configuration; once the GCEMS processes are started the Primary server will ftp the required files to the secondary, including the system.cfg and the system_datamodel.xml

14. Clientview can be run on each of the GCEMS servers, however it is normal to start Clientview first on the Primary as it will have the configuration privileges.

Notes:  Free Radius, SNTP, MRTG, and CACTI will normally be installed prior to the migration according to the IMG 1010 and 1004 documentation.

Backout/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. Stop the dhcpd service on the Active GCEMS server, more than likely the Primary

root@etc]# service dhcpd stop

  1. Start the dhcpd service on the old standalone server [root@l etc]# service dhcpd start 

 and reset/powercycle an IMG to confirm dhcp is working to the old standalone server as shown in Step 10 above.

  1. Start GCEMS on the Standalone server by clicking on the Start GCEMS desktop icon and load NEW config

  2. Launch Clientview and load the current *.csa file.

  3. Confirm the system was configured properly as noted in Step 2 above in the Solution section  and Query All Tags by clicking on the Query All Tags tab.

Product List
IMG 1010 Integrated Media Gateway
IMG 1004 Integrated Media Gateway
Gate Control Element Management System 

Glossary of Acronyms / Terms
CLI: Command Line Interface
SNTP: Signaling Network Time Protocol
MRTG: Multi Router Traffic Grapher 

  • No labels

Return to Documentation Home I Return to Sangoma Support