Configuration Guide for Cisco Unified MeetingPlace Release 8.6
Configuring Application Server Failover
Downloads: This chapterpdf (PDF - 174.0KB) The complete bookPDF (PDF - 7.28MB) | Feedback

Configuring Application Server Failover on MeetingPlace-Scheduled and Audio-Only Deployments

Table Of Contents

Configuring Application Server Failover on MeetingPlace-Scheduled and Audio-Only Deployments

Application Server Failover

Prerequisites for Application Server Failover

Restrictions for Application Server Failover

How to Configure Application Server Failover

Setting Up Failover for Two Newly Installed Application Servers (Cisco Unified MeetingPlace 8.6)

Setting Up Failover for One Existing Application Server and One Newly Installed Application Server (Cisco Unified MeetingPlace 8.6)

Configuring the Application Servers in a Failover Deployment

How to Perform Application Server Failover

Performing Application Server Failover (Cisco Unified MeetingPlace 8.6)

Resynchronizing the MCUs (Cisco Unified MeetingPlace 8.6)

Performing Application Server Failover to Switch to the Previous Active Server (Cisco Unified MeetingPlace 8.6)


Configuring Application Server Failover on MeetingPlace-Scheduled and Audio-Only Deployments


Application Server Failover

Prerequisites for Application Server Failover

Restrictions for Application Server Failover

How to Configure Application Server Failover

How to Perform Application Server Failover

Application Server Failover

You can deploy two Application Servers as part of one logical site. Database replication enables the Application Servers to synchronize user profiles, user groups, and meeting data. Only one Application Server is active at any time. If the active server fails, you can activate the standby server and place the previously active server in standby mode. Each Application Server in a site is called a node.

If the site includes two hardware Media Servers, then one Media Server will be associated with each Application Server. If the site includes only one hardware Media Server, it is always associated with the active Application Server.

In a failover deployment, each Application Server is configured with two IP addresses—one for each of these interfaces:

eth0—Physical network interface

Assign the same shared hostname and IP address to eth0 on both Application Servers.

Anyone who tries to access the shared hostname or IP address will reach the active Application Server.

The eth0 interface is disabled on the standby Application Server.

eth0:0—Virtual network interface

Assign a unique hostname and IP address to eth0:0 on each Application Server.

Use the eth0:0 hostname or IP address to access an Application Server that is in standby mode.

The system uses the eth0:0 virtual network interface for database replication between the two nodes.


Note The interface eth0 mentioned throughout this module actually refers to the physical Ethernet port 1 on the Application Server.


A standby node comes up as standby after reboot. An active node comes up as active after reboot with the following exception:

When an active node is rebooted, interface eth0 is initially disabled. However, during startup of the Cisco Unified MeetingPlace application, the node checks for an active application server on the network by attempting to ping the eth0 IP address, which is identical on both nodes. If the ping is successful, the node will come up in standby mode.

Related Topics

Prerequisites for Application Server Failover

Restrictions for Application Server Failover

How to Configure Application Server Failover

How to Perform Application Server Failover

Information About Failover in Cisco WebEx Integrations

Prerequisites for Application Server Failover

Learn about failover deployment options in the Planning Guide for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_implementation_design_guides_list.html.

Determine the hostname, IP address, subnet mask, and default gateway for each node:

Node 1 eth0 and Node 2 eth0—Use the same hostname and IP address for the eth0 network interface on both Node 1 and Node 2, for example: meetings.example.com, 10.0.0.1

Node 1 eth0:0—Use a unique hostname and IP address for this virtual network interface, for example: meetings1.example.com, 10.0.0.2

Node 2 eth0:0—Use a unique hostname and IP address for this virtual network interface, for example: meetings2.example.com, 10.0.0.3

Configure the Domain Name System (DNS) server for forward and reverse DNS lookup of all three hostname-IP address pairs. Verify by running the nslookup hostname and nslookup ip-address commands.

Whether you configure Application Server failover before or after you install any Web Server(s) and your call-control devices (such as Cisco Unified Communications Manager), make sure that these devices identify the active Application Server by using the shared hostname and IP address of eth0.

If you have an existing failover deployment, the migration script and process to restore data must be completed before failover is configured and enabled in Release 8.6. Configuring and enabling failover before running the migration script can cause database issues, requiring a reinstallation of the Release 8.6 server.

Do not block ping traffic to the Network Time Protocol (NTP) Server while you are configuring Application Server failover. Part of the failover set up process is to ping the NTP Server to check for connectivity. If you have not opened up Internet Control Message Protocol (ICMP) echo to the NTP Server, you may see the error, "All configured NTP servers are down".

Related Topics

Configuring Application Server Failover on MeetingPlace-Scheduled and Audio-Only Deployments

Restrictions for Application Server Failover

How to Configure Application Server Failover

Restrictions for Application Server Failover

Not all Application Server configurations are replicated between the active and standby servers. If you make any configuration changes after you set up Application Server failover, make sure you follow the "Configuring the Application Servers in a Failover Deployment" section.

Only the database and Apache Tomcat processes run on a standby server, which you will notice if you enter the operating status command on the standby server.

The time must be synchronized between the two application servers. This is required for replication to work properly. One way to make sure that time is synchronized is to configure NTP servers on both the active and the standby servers.

The Informix database runs on the same machine as the application server. Port 2008 is configured in the application servers for database replication purposes.

If the primary and failover application servers share a common set of Audio and Video Blades, you must add all the Audio Blades to both Applications Servers. Be sure to use exactly the same passwords and SNMP community names on the two systems or the failover mechanism will not work.

Completion of and later changes to the Application Server failover deployment require that you update the Application Server Link. After the failover configuration is completed, complete the procedure in Configuring the Application Server Link on the Cisco WebEx Node.

Related Topics

Configuring Application Server Failover on MeetingPlace-Scheduled and Audio-Only Deployments

Prerequisites for Application Server Failover

How to Configure Application Server Failover

How to Perform Application Server Failover

Configuring Directory Service on MeetingPlace-Scheduled and Audio-Only Deployments

Information About Failover in Cisco WebEx Integrations

How to Configure Application Server Failover

Setting Up Failover for Two Newly Installed Application Servers (Cisco Unified MeetingPlace 8.6)

Setting Up Failover for One Existing Application Server and One Newly Installed Application Server (Cisco Unified MeetingPlace 8.6)

Setting Up Failover for One Existing Application Server and One Newly Installed Application Server (Cisco Unified MeetingPlace 8.6)

Configuring the Application Servers in a Failover Deployment

Configuring the Application Servers in a Failover Deployment

Setting Up Failover for Two Newly Installed Application Servers (Cisco Unified MeetingPlace 8.6)

Before You Begin

Complete the "Prerequisites for Application Server Failover" section.

Read the "Restrictions for Application Server Failover" section.

Procedure


Step 1 Install the first Application Server (Node 1).

During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.

Step 2 Install any licenses on the first application server (Node 1). For details, see the Installing and Managing Licenses.

Step 3 Sign in to the Administration Center of Node 1.

If you are signing in remotely, use the eth0 IP address or hostname.

Step 4 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 5 Configure the virtual network interface (eth0:0) with an IP address, hostname, subnet mask and default gateway.

Step 6 Select Save to save entered parameters.

Step 7 Select Set Failover Deployment Mode.

The setting failover deployment mode process is started and a progress report is displayed.

Step 8 After the process is complete, select Start System Restart.

Node 1 automatically restarts, enters failover standby mode, and redirects to the eth0:0 hostname.

Step 9 Sign in to the Administration Center of Node 1.

The Failover Status page is displayed.

Step 10 Select Show Failover Status to ensure that Node 1 is in failover standby mode.

Step 11 Install the second Application Server (Node 2), ensuring the following:

Node 1 and Node 2 use the exact same IP address and hostname for eth0.

The time is synchronized between Node 1 and Node 2.

Step 12 Install any licenses on the second application server (Node 2) and reboot the system. For more information, see the Installing and Managing Licenses module.

Step 13 Sign in to the Administration Center of Node 2. Use the eth0 IP address or hostname.

Step 14 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 15 Configure the virtual network interface (eth0:0) with an IP address, hostname, subnet mask, and default gateway.

Step 16 Select Save.

Step 17 Select Set Failover Deployment Mode.

The setting failover deployment mode process is started and a progress report is displayed.

Step 18 After the process is complete, select Start System Restart.

Node 2 automatically restarts, enters failover standby mode and redirects to eth0:0 hostname.

Step 19 Sign in to the Administration Center of Node 2.

The Failover Status page is displayed. Select Show Failover Status to ensure that Node 2 is in failover standby mode.

Step 20 Sign in to the Administration Center of Node 1. Use the eth0:0 IP address or hostname.

Step 21 Select System Configuration > Failover Configuration > Add Failover Node.

Step 22 Specify the relevant parameters for Node 2: hostname (use the eth0:0 hostname), mpxadmin user password, mpxadmin user password confirmation and description.

Step 23 If you want to indicate the data synchronization between the two nodes, check Sync and specify the hostname of the source node in the Hostname for sync field (use the eth0:0 hostname).

Step 24 Select Save.

Step 25 Select Add Failover Node.

Step 26 The adding failover node process is started and a progress report is displayed. Replication is initialized between these two nodes.

Step 27 After the first part of the process is complete, select Continue With Replication.

The adding failover node process is continued and a progress report is displayed. Data synchronization is performed (if it was indicated in Step 22) and replication is switched on.

Step 28 After the process is complete, select Start System Restart.

Node 1 automatically restarts.

Step 29 Sign in to the Administration Center of Node 1.

The Failover Status page is displayed. Select Show Replication Status to ensure that replication is established between Node 1 and Node 2.

Step 30 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 31 Select Set Active to change Node 1 from standby mode to active mode.

The setting the node to active mode process is started and a progress report is displayed.

Step 32 After the process finishes, select Start System Restart.

Step 33 Node 1 restarts, enters failover active mode, and redirects to the eth0 hostname.

Step 34 Sign in to the Administration Center of Node 1.

The Failover Status page is automaticaly displayed. Select Show Failover Status to ensure that Node 1 is in failover active mode.


Verifying

Using the hostname or IP address of the virtual eth0:0 interface, sign 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. On each node: Select Configuration > Failover Configuration > Failover Status, select Show Failover Status and verify that each node is in the correct failover deployment mode (active or standby). Select Show Replication Status and verify on each node that replication is successfully established.

Related Topics

Using the Command-Line Interface (CLI) on the Application Server

Configuring Application Server Failover on MeetingPlace-Scheduled and Audio-Only Deployments

What To Do Next

If your system is integrated with Cisco WebEx, and your deployment includes the Cisco WebEx Node, then proceed to Configuring the Application Server Link on the Cisco WebEx Node.

Otherwise, proceed to Configuring the Application Servers in a Failover Deployment.

Setting Up Failover for One Existing Application Server and One Newly Installed Application Server (Cisco Unified MeetingPlace 8.6)

In this task:

Node 1 is the existing Application Server.

Node 2 is the new Application Server.

Before You Begin

Complete the "Prerequisites for Application Server Failover" section.

Read the "Restrictions for Application Server Failover" section.

Back up and archive the data on the existing Application Server (Node 1). See Backing Up, Archiving, and Restoring Data on the Application Server.


Caution Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Proceed only during a scheduled maintenance period.

Procedure

Step 35 Sign in to the Administration Center of Node 1.

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

Step 36 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 37 Configure the virtual network interface (eth0:0) with an IP address, hostname, subnet mask, and default gateway.

Step 38 Select Save.

Step 39 Select Set Failover Deployment Mode.

The setting failover deployment mode process is started and a progress report is displayed.

Step 40 After the process is complete, select Start System Restart.

Node 1 automatically restarts, enters failover standby mode, and redirects to eth0:0 hostname.

Step 41 Sign in to the Administration Center of Node 1.

The Failover Status page is displayed. Select Show Failover Status to ensure that Node 1 is in failover standby mode.

Step 42 Sign in to the CLI of Node 2.

If you are signing in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in Step 35.

Step 43 Enter the net 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 44 Enter mpx_sys restart to restart Node 2.

Step 45 Sign in to the Administration Center of Node 2. Use the eth0 IP address or hostname.

Step 46 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 47 Configure the virtual network interface (eth0:0) with an IP address, hostname, subnet mask, and default gateway.

Step 48 Select Save.

Step 49 Select Set Failover Deployment Mode.

The setting failover deployment mode process is started and a progress report is displayed.

Step 50 After the process is complete, select Start System Restart.

Node 2 automatically restarts, enters failover standby mode, and redirects to the eth0:0 hostname.

Step 51 Sign in to the Administration Center of Node 2.

The Failover Status page is displayed. Select Show Failover Status to ensure that Node 2 is in failover standby mode.

Step 52 Sign in to the Administration Center of Node 1. Use the eth0:0 IP address or hostname.

Step 53 Select System Configuration > Failover Configuration > Add Failover Node.

Step 54 Specify relevant parameters for Node 2: hostname (use the eth0:0 hostname), mpxadmin user password, mpxadmin user password confirmation, and description.

If you want to configure data synchronization between the two nodes, check Sync and, in the Hostname for sync field, specify the hostname of the source node (use the eth0:0 hostname).

Step 55 Select Save.

Step 56 Select Add Failover Node.

The adding failover node process is started and a progress report is displayed. Replication is initialized between these two nodes.

Step 57 After the first part of the process finishes, select Continue With Replication.

Step 58 The adding failover node process resumes and a progress report is displayed. Data synchronization is performed (if it was indicated in Step 55) and replication is switched on.

Step 59 After the process is complete, select Start System Restart.

Node 1 automatically restarts.

Step 60 Sign in to the Administration Center of Node 1.

The Failover Status page is automaticaly displayed. Select Show Replication Status to ensure that replication is established between Node 1 and Node 2.

Step 61 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 62 Select Set Active to change Node 1 from standby mode to active mode.

The setting node to active mode process is started and progress report is displayed.

Step 63 After the process is complete, select Start System Restart.

Node 1 automatically restarts, enters failover active mode, and redirects to eth0 hostname.

Step 64 Sign in to the Administration Center of Node 1.

The Failover Status page is displayed. Select Show Failover Status to ensure that Node 1 is in failover active mode.


Verifying

Using the hostname or IP address of the virtual eth0:0 interface, sign 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.

Installing the Cisco Unified MeetingPlace Application Server Software in the Installation, Upgrade, and Migration Guide for Cisco Unified MeetingPlace

What To Do Next

If your system is integrated with Cisco WebEx, and your deployment includes the Cisco WebEx Node, then proceed to Configuring the Application Server Link on the Cisco WebEx Node.

Otherwise, proceed to the "Configuring the Application Servers in a Failover Deployment" section.

Configuring the Application Servers in a Failover Deployment

Whenever you need to configure the Application Server in a failover deployment, use this procedure to make sure that both the active and standby servers have the same configuration.

Before You Begin

Complete one of these tasks:

Set up failover for two newly installed application servers. See Setting Up Failover for Two Newly Installed Application Servers (Cisco Unified MeetingPlace 8.6).

Set up failover for one existing application server and one newly installed application server. See Setting Up Failover for One Existing Application Server and One Newly Installed Application Server (Cisco Unified MeetingPlace 8.6).

Determine the hostname or IP address of both of these virtual network interfaces:

eth0:0 of the active server

eth0:0 of the standby server

Procedure


Step 1 Go to http://application-server/admin/.

Use the shared eth0 hostname or IP address, which always goes to the active Application Server.

Step 2 Sign in as a System administrator.

Step 3 Configure the active server.

Take note of any changes you make on pages or fields that are labeled as:

Copied

Server-specific

Partially replicated

Step 4 Perform the following steps if you made changes to any copied pages or parameters or to replicate recorded names:

a. Sign in to the CLI of the active server.

If you are signing in remotely, use the eth0 IP address or hostname.

b. Enter this command to compress and transfer the files from the active server to the standby server:

failoverUtil copyConfigFiles

c. Sign in to the CLI of the standby server.

If you are signing in remotely, use eth0:0 IP address or hostname.

d. Enter this command to decompress the transferred files and put them in the correct directories on the standby server:

failoverUtil restoreConfigFiles

Step 5 If you made changes to any server-specific pages or parameters, then perform these steps.


Tip If your workstation screen is large enough to accommodate two full web browser windows without overlapping, then you can simultaneously view the Administration Center for both the active and standby servers. This might help you configure the server-specific parameters to match between the active and standby servers.


a. Go to http://standby-eth0:0/admin/.

Use either the hostname or IP address of the virtual eth0:0 interface of the standby Application Server.

b. Sign in as a System administrator.

c. Verify that "Failover deployment. Standby server." appears at the top of the page.

d. Configure the server-specific parameters on the standby server.


Related Topics

Signing In to the Administration Center

Configuring Application Server Failover on MeetingPlace-Scheduled and Audio-Only Deployments

Using the Command-Line Interface (CLI) on the Application Server

About Integrating with Cisco WebEx

Customizing Music and Voice Prompts

How to Perform Application Server Failover

Installing the Cisco Unified MeetingPlace Application Server Software in the Installation, Upgrade, and Migration Guide for Cisco Unified MeetingPlace

How to Perform Application Server Failover

Performing Application Server Failover (Cisco Unified MeetingPlace 8.6)

Resynchronizing the MCUs (Cisco Unified MeetingPlace 8.6)

Performing Application Server Failover to Switch to the Previous Active Server (Cisco Unified MeetingPlace 8.6)

Performing Application Server Failover (Cisco Unified MeetingPlace 8.6)

Before you perform this task:

Node 1 is the current active server.

Node 2 is the current standby server.

After you complete the task:

Node 1 will be the standby server.

Node 2 will be the active server.

Before You Begin

Set up Application Server failover by completing one of these sections:

Setting Up Failover for Two Newly Installed Application Servers (Cisco Unified MeetingPlace 8.6)

Setting Up Failover for One Existing Application Server and One Newly Installed Application Server (Cisco Unified MeetingPlace 8.6)


Caution Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Perform this task only if the current active server fails, or during a scheduled maintenance period.

Procedure


Step 1 Sign in to the Administration Center of Node 1. Use the eth0 IP address or hostname.

Step 2 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 3 Select Set Standby to change the server from active mode to standby mode.

Step 4 Setting node to standby mode process is started and progress report is displayed.

Step 5 After the process is complete, select Start System Restart.

Node 1 automatically restarts, enters failover standby mode, and redirects to eth0:0 hostname.

Step 6 Sign in to the Administration Center of Node 1.

The Failover Status page is displayed. Select Show Failover Status to ensure that Node 1 is in failover standby mode.


Note When you use this command to set your server to standby, the server starts shutting down services. During the "Stopping MeetingPlace application" phase of the shutdown, an alarm might occur that indicates the system has crashed and the core files are being generated. This does not indicate a system problem.


Step 7 Sign in to the Administration Center of Node 2. Use the eth0:0 IP address or hostname.

Step 8 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 9 Select Set Active to change the server from standby mode to active mode.

The setting node to active mode process is started and a progress report is displayed.

Step 10 After the process is complete, select Start System Restart.

Node 2 automatically restarts, enters failover active mode, and redirects to eth0 hostname.

Step 11 Sign in to the Administration Center of Node 2.

The Failover Status page is displayed. Select Show Failover Status to ensure that Node 2 is in failover active mode.

Step 12 Restart the MCUs manually to resynchronize them or complete the steps in Resynchronizing the MCUs (Cisco Unified MeetingPlace 8.6).


Verifying

Using the hostname or IP address of the virtual eth0:0 interface, sign 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. Then select Configuration > Failover Configuration > Failover Status, select Show Failover Status, and verify that each node is in the correct failover deployment mode (active or standby). Then select Show Replication Status and verify that replication has been successfully established on each node.

Troubleshooting Tips

If the Administration Center displays the wrong failover mode on either or both servers, something might have interrupted the process initiated by the failoverUtil setServer command. To resolve this issue, see the failoverUtil setServer command description.

Related Topics

Using the Command-Line Interface (CLI) on the Application Server

Configuring Application Server Failover on MeetingPlace-Scheduled and Audio-Only Deployments

Information About Failover in Cisco WebEx Integrations

Resynchronizing the MCUs (Cisco Unified MeetingPlace 8.6)

What to Do Next

Proceed to the "Resynchronizing the MCUs (Cisco Unified MeetingPlace 8.6)" section.

Resynchronizing the MCUs (Cisco Unified MeetingPlace 8.6)

Procedure


Step 1 Sign in to Media Server Administration for the Hardware Media Server.

Step 2 Select Resource Management > MCU from the left panel.

Step 3 Select the name of the Audio Blade.

Step 4 Select Synchronize on the Resource Management page.

Step 5 Select OK on the informational message.

Step 6 Select Synchronize on the Active Meeting Types page.

The system displays a message that the meetings were downloaded successfully.

Step 7 Select OK.


Performing Application Server Failover to Switch to the Previous Active Server (Cisco Unified MeetingPlace 8.6)

Before you perform this task:

Node 1 is the current active server.

Node 2 is the current standby server.

After you complete the task:

Node 1 will be the standby server.

Node 2 will be the active server.

Before You Begin

Set up Application Server failover by completing one of these sections:

Setting Up Failover for Two Newly Installed Application Servers (Cisco Unified MeetingPlace 8.6)

Setting Up Failover for One Existing Application Server and One Newly Installed Application Server (Cisco Unified MeetingPlace 8.6)


Caution Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Perform this task only if the current active server fails, or during a scheduled maintenance period.

Complete the "Prerequisites for Application Server Failover" section.

Back up and archive the data on the currently active Application Server (Node 1). See the Backing Up, Archiving, and Restoring Data on the Application Server module.

Procedure


Step 1 If Node 1 was brought to single-server mode, then you will need to do the following:

a. Sign in to the Administration Center of Node 1. Use the eth0 IP address or hostname.

b. Select System Configuration > Failover Configuration > Failover Deployment Setup.

c. Configure the virtual network interface (eth0:0) with an IP address, hostname, subnet mask and default gateway.

d. Select Save.

e. Select Set Failover Deployment Mode.

The setting failover deployment mode process is started and progress report is displayed.

f. After the process is complete, select Start System Restart.

Node 1 automatically restarts, enters failover standby mode, and redirects to eth0:0 hostname.

g. Sign in to the Administration Center of Node 1.

The Failover Status page is displayed. Select Show Failover Status to ensure that Node 1 is in failover standby mode.

Step 2 If the database replication configuration was removed from Node 1, then you will need to do the following:

a. Sign in to the Administration Center of Node 1. Use the eth0:0 IP address or hostname.

b. Select System Configuration > Failover Configuration > Add Failover Node.

c. Specify the relevant parameters for Node 2: hostname (use the eth0:0 hostname), mpxadmin user password, mpxadmin user password confirmation, and description.

d. If you want to indicate data synchronization between the two Nodes, check Sync and, in the Hostname for sync field, specify the hostname of the source Node (use the eth0:0 hostname).

e. Select Save.

f. Select Add Failover Node.

The adding failover node process is started and progress report is displayed. Replication will be initialized between these two Nodes.

g. After the first part of the process is complete, select Continue With Replication.

The adding failover node process is continued and a progress report is displayed. Data synchronization will be performed (if it was indicated in Step 2c) and replication is switched on.

After the process is complete, select Start System Restart.

Node 1 automatically restarts.

h. Sign in to the Administration Center of Node 1.

The Failover Status page is automaticaly displayed. Select Show Replication Status to ensure that replication is established between Node 1 and Node 2.

Step 3 Sign in to the Administration Center of Node 2. Use the eth0 IP address or hostname.

Step 4 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 5 Select Set Standby to change the server from active mode to standby mode.

The setting node to standby mode process is started and a progress report is displayed.

Step 6 After the process is complete, select Start System Restart.

Node 2 automatically restarts, enters failover standby mode, and redirects to the eth0:0 hostname.

Step 7 Sign in to the Administration Center of Node 2.

The Failover Status page is displayed. Select Show Failover Status to ensure that Node 2 is in failover standby mode.


Note When you use this command to set your server to standby, the server starts shutting down services. During the "Stopping MeetingPlace application" phase of the shutdown, an alarm might occur that indicates the system has crashed and the core files are being generated. This does not indicate a system problem.


Step 8 Sign in to the Administration Center of Node 1. Use the eth0:0 IP address or hostname.

Step 9 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 10 Select Set Active to change the server from standby mode to active mode.

The setting node to active mode process is started and a progress report is displayed.

Step 11 After the process finishes, select Start System Restart.

Node 1 automatically restarts, enters failover active mode, and redirects to eth0 hostname.

Step 12 Sign in to the Administration Center of Node 1.

The Failover Status page is displayed. Select Show Failover Status to ensure that Node 1 is in failover active mode.

Step 13 Restart the MCUs manually to resynchronize them or complete the steps in Resynchronizing the MCUs (Cisco Unified MeetingPlace 8.6).


Verifying

Using the hostname or IP address of the virtual eth0:0 interface, sign 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. Then select Configuration > Failover Configuration > Failover Status, select Show Failover Status and verify that each node is in the correct failover deployment mode (active or standby). Then select Show Replication Status and verify on each node that replication is successfully established.

Related Topics

Using the Command-Line Interface (CLI) on the Application Server

Configuring Application Server Failover on MeetingPlace-Scheduled and Audio-Only Deployments

Information About Failover in Cisco WebEx Integrations