SMG Database Replication

**btoth** · 05-23-2012, 10:44 AM

You need to add an elan gateway route for data replication on a CoRes SMG

In the UCM select the element for the SMG.
Open IP Network then select Host Routes and Tables.
Select Route Table then select add.

For the destination ip address Use the main network ELAN ip address the Main Callserver is on.
Its "USUALLY" the gateway ip address the main callserver is on minus 1. ie: the main callserver elan gateway is 192.168.0.97 the main elan network ip would be 192.168.0.96. But to be sure confirm that with your network guy.

Keep the gateway ip address thats present. It should be the ELAN gateway ip of the CoRes server.
Uncheck the host route
Destination netmask should be the subnet mask of the main site.

**anaya** · 06-11-2012, 08:25 AM

Just to put the resolution here.

You program all the GR items in the Main site. Before you transfer the data, you have to build a Backup Schedule and GRDRC block in the SMG side.

I was reading this and it just looked a little wierd that you would put a backup schedule in the Remote Side, but in essence what it does is allows the SMG to receive the file.

Once I did this, I did an EDD on the Main and it sent over the database. The SMG received the database, copied and sysloaded to take the database and all has been working fine.

**jmccallister** · 09-07-2012, 06:58 AM

I did the above and the SMG acts correctly and receives th e file and acts on it and sysloads etc.. but on the MO side it still says it fails when in fact it went through just fine.

Any ideas?

**anaya** · 12-11-2012, 10:47 AM

If this is a Co-res system the reason the Main site shows failure is because the default route on the Co-res side is the TLAN Gateway. This is set up during the Linux OS load.

To resolve this issue, you can do two things:

1. Trunk your VLAN segments so that traffice from the TLAN will flow to the ELAN IP Addresses if needed, or

2. Add a default route in the Co-res Signalign Server at the Co-res side
1.1.1.1 (your Main site ELAN IP Address) to the ELAN Gateway

The reason this is happening is because is because the Main Office sends over the database file, the SMG recevies it and sends back a successful transfer message, but it is trying to send it over the ELAN segment and there is no route defined.

Do either of these and your issues will be resolved.

So the amended process for replicating the database to a Co-res system, assuming you have done the above. If not a Co-res system, then build all your IP information in the SMG side first.

1. Build the Main Call Server
2. Add a backup rule in ld 117
=>new bkpr X scs 2 <ELAN IP Address of SMG>
3. Complete a backup (Run EDD - the replication happens not from the active database, but rather from the last reten backup file)
4. At the main site, from LD 43 - .bkr X (X being the rule number for the SMG)
5. At the SMG site BEFORE DOING ANYTHING WITH THE REPLICATED DATABASE - create a backup rule in ld 117 =>new bkpr 1 scs <ELAN IP of the main site>
6. Create GRDRC in SMG in ld 117 =>new grdrc 1 schd 1 no no (make it just like this)
7. Go to ld 135 and do - .stat gr (you will see your file that came over)
8. in the SMG go to ld 43 and do: .rsr 1 (TYPE YES FOR IP FILTERING - VERY IMPORTANT YOU TYPE YES. IF YOU DO NOT YOU WILL NEED TO REBUILD THE CALL SERVER. IT WON'T BRING OVER ANY PROGRAMMED MEDIA GATEWAY INFORMATION IF YOU DO NOT TYPE YES.
9. After the database populates the SMG go to LD 135 and do: .sysload active (type Yes to reboot the system.
10. Once the system comes up, it may replicate again, let it do it's job and it will automatically sysload.
11. Go into your SMG signaling server and build your Node for the system, and all the other work for the Signaling Server.
12. Go have a beer. You should be done.

SMG Database Replication

SMG Database Replication

Comment

Comment

Comment

Comment