Cisco Cisco MeetingPlace Gateway SIM Anleitung Für Quick Setup

Seite von 766
 
Configuring Application Server Failover for Cisco Unified MeetingPlace
How to Configure Application Server Failover
7
 
Step 3
Enter the following command to set up Node 1 for failover:
failoverUtil setDeployment failover 
Step 4
Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet 
mask, default gateway, and hostname.
Node 1 automatically restarts and enters standby mode. 
Step 5
Log in to the CLI of Node 2.
If you are logging in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered 
during installation in 
Step 6
Enter the 
 command to change the Node 2 eth0 IP address and hostname to match the Node 1 eth0 IP 
address and hostname.
Because Node 1 is still in standby mode, Node 2 is now the active server.
Step 7
Enter reboot to restart Node 2.
Step 8
Log in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
Step 9
Enter the following command to set up Node 2 for failover:
failoverUtil setDeployment failover 
Step 10
Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet 
mask, default gateway, and hostname.
Node 2 automatically restarts and enters standby mode. 
Step 11
Enter the following command to initialize database replication:
mp_replication init -n 2 -r remote-eth0:0 [-v]
Step 12
Log in to the CLI of Node 1.
If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
Step 13
Enter the following commands to initialize and start database replication and synchronize existing data:
mp_replication init -n 1 -r remote-eth0:0 [-v]
mp_replication switchON -S -F from-sync [-v]
Step 14
Enter the following command to change Node 1 from standby mode to active mode:
failoverUtil setServer active 
Verifying
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: 
Local Server 
Remote Server 
Replication Type: Local 
Replication Type: Intra-site 
Site: 1 
Site: 1 
Node: 1 
Node: 2