Cisco Cisco MeetingPlace Gateway SIM Anleitung Für Quick Setup

Log in to the CLI of Node 1.

If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.

Enter the following commands to initialize and start database replication:

mp_replication init -n 1 -r remote-eth0:0 [-v]

mp_replication switchON [-v]

Enter the following command to change Node 1 from standby mode to active mode:

failoverUtil setServer active 

Node must be active to add licenses (step 7).

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of 
each node, and verify that the correct failover deployment mode (active or standby) appears at the top of 
the page.

To verify that the replication was successful, log in to both nodes (eth0:0 interface) as root user and enter 
the mp_replication status command. The following should display in your output: 

If the Administration Center in both nodes displays “Failover deployment. Standby server,” then 
something may have interrupted the process initiated in 

. To resolve this issue, see the 

 command description in the 

 module.

If you switch on replication with sync via the mp_replication switchON command and replication 
fails, it is possible that a table is locking due to the processes on an active server. To resolve this 
issue, run the mp_replication switchON with sync command again. 

During this process, you may see several error messages. These error messages are expected 
behavior and informational only. The final message of the command explicitly says if the command 
ran successfully or not. 

An example of an error message that you can ignore is: 

Replication Type: Local 

Replication Type: Intra-site 

Site: 1 

Site: 1 

Node: 1 

Node: 2

State: Active 

State: Active 

Status: Local 

Status: Connected