Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Procedure)
m
Line 13: Line 13:
== 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''.  
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''.  
Line 39: Line 38:
===== Related Topics =====
===== Related Topics =====
 +
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Restrictions for Application Server Failover|Restrictions for Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Restrictions for Application Server Failover|Restrictions for Application Server Failover]]
Line 48: Line 48:
== Prerequisites for Application Server Failover ==
== Prerequisites for Application Server Failover ==
 +
* Learn about failover deployment options in the ''Planning Guide for Cisco Unified MeetingPlace'' at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.  
* Learn about failover deployment options in the ''Planning Guide for Cisco Unified MeetingPlace'' at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.  
* Install Cisco Unified MeetingPlace as described in the [[Cisco Unified MeetingPlace Release 8.0 -- Quick Start for Installing and Configuring Cisco Unified MeetingPlace Release 8.0#Quick Start for Installing and Configuring Cisco Unified MeetingPlace Release 8.0|Quick Start for Installing and Configuring Cisco Unified MeetingPlace Release 8.0]] module.
* Install Cisco Unified MeetingPlace as described in the [[Cisco Unified MeetingPlace Release 8.0 -- Quick Start for Installing and Configuring Cisco Unified MeetingPlace Release 8.0#Quick Start for Installing and Configuring Cisco Unified MeetingPlace Release 8.0|Quick Start for Installing and Configuring Cisco Unified MeetingPlace Release 8.0]] module.
Line 59: Line 60:
===== Related Topics =====
===== Related Topics =====
 +
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Restrictions for Application Server Failover|Restrictions for Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Restrictions for Application Server Failover|Restrictions for Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#How to Configure Application Server Failover|How to Configure Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#How to Configure Application Server Failover|How to Configure Application Server Failover]]
Line 65: Line 67:
== Restrictions for 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 [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].
* 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 [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Directory Service|Directory Service]] between two Application Servers is not supported in a failover deployment.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Directory Service|Directory Service]] between two Application Servers is not supported in a failover deployment.
Line 77: Line 80:
===== Related Topics =====
===== Related Topics =====
 +
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#How to Configure Application Server Failover|How to Configure Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#How to Configure Application Server Failover|How to Configure Application Server Failover]]
Line 86: Line 90:
== How to Configure Application Server Failover ==
== How to Configure Application Server Failover ==
 +
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]]
 +
Line 95: Line 101:
===== Before You Begin =====
===== Before You Begin =====
 +
* Complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].
* Complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].
* Read the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Restrictions for Application Server Failover|Restrictions for Application Server Failover]].
* Read the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Restrictions for Application Server Failover|Restrictions for Application Server Failover]].
Line 100: Line 107:
===== Procedure =====
===== Procedure =====
-
 
# Install the first Application Server (Node 1).  
# Install the first Application Server (Node 1).  
Line 133: Line 139:
===== Verifying =====
===== 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.
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.
Line 139: Line 144:
===== Troubleshooting Tips =====
===== Troubleshooting Tips =====
-
 
If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something might have interrupted the process initiated in Step 14. To resolve this issue, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command description in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module.
If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something might have interrupted the process initiated in Step 14. To resolve this issue, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command description in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module.
 +
===== Related Topics =====
===== Related Topics =====
 +
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Application Server Software#Installing the Cisco Unified MeetingPlace Application Server Software|Installing the Cisco Unified MeetingPlace Application Server Software]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Application Server Software#Installing the Cisco Unified MeetingPlace Application Server Software|Installing the Cisco Unified MeetingPlace Application Server Software]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module  
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module  
Line 149: Line 155:
===== What To Do Next =====
===== What To Do Next =====
 +
* If your system is integrated with Cisco WebEx, and your deployment includes the Cisco WebEx Node for MCS, then proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Configuring the Application Server Link on the Cisco WebEx Node for MCS|Configuring the Application Server Link on the Cisco WebEx Node for MCS]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]] module.
* If your system is integrated with Cisco WebEx, and your deployment includes the Cisco WebEx Node for MCS, then proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Configuring the Application Server Link on the Cisco WebEx Node for MCS|Configuring the Application Server Link on the Cisco WebEx Node for MCS]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]] module.
* Otherwise, proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].
* Otherwise, proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].
-
=== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ===
 
 +
=== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ===
In this task:  
In this task:  
Line 162: Line 169:
===== Before You Begin =====
===== Before You Begin =====
 +
* Complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].
* Complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].
* Read the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Restrictions for Application Server Failover|Restrictions for Application Server Failover]].
* Read the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Restrictions for Application Server Failover|Restrictions for Application Server Failover]].
Line 171: Line 179:
===== Procedure =====
===== Procedure =====
-
 
# Install the second Application Server (Node 2), ensuring the following:  
# Install the second Application Server (Node 2), ensuring the following:  
Line 203: Line 210:
#: '''failoverUtil setServer active'''
#: '''failoverUtil setServer active'''
-
===== Verifying =====
 
 +
===== 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.
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.
Line 210: Line 217:
===== Troubleshooting Tips =====
===== Troubleshooting Tips =====
-
 
If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something might have interrupted the process initiated in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command description in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module.
If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something might have interrupted the process initiated in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command description in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module.
Line 216: Line 222:
===== Related Topics =====
===== Related Topics =====
 +
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Application Server Software#Installing the Cisco Unified MeetingPlace Application Server Software|Installing the Cisco Unified MeetingPlace Application Server Software]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Application Server Software#Installing the Cisco Unified MeetingPlace Application Server Software|Installing the Cisco Unified MeetingPlace Application Server Software]] module
===== What To Do Next =====
===== What To Do Next =====
 +
* If your system is integrated with Cisco WebEx, and your deployment includes the Cisco WebEx Node for MCS, then proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Configuring the Application Server Link on the Cisco WebEx Node for MCS|Configuring the Application Server Link on the Cisco WebEx Node for MCS]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]] module.
* If your system is integrated with Cisco WebEx, and your deployment includes the Cisco WebEx Node for MCS, then proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Configuring the Application Server Link on the Cisco WebEx Node for MCS|Configuring the Application Server Link on the Cisco WebEx Node for MCS]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]] module.
* Otherwise, proceed to the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].
* Otherwise, proceed to the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].
 +
=== Configuring the Application Servers in a Failover Deployment ===
=== 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.
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.
Line 231: Line 239:
===== Before You Begin =====
===== Before You Begin =====
 +
* Complete one of these tasks:
* Complete one of these tasks:
** [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
** [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
Line 240: Line 249:
===== Procedure =====
===== Procedure =====
-
 
# Go to '''http://'''''application-server'''''/admin/'''.  
# Go to '''http://'''''application-server'''''/admin/'''.  
Line 269: Line 277:
===== Related Topics =====
===== Related Topics =====
 +
* [[Cisco Unified MeetingPlace Release 8.0 -- Signing In to the Cisco Unified MeetingPlace Administration Center#Signing In to the Cisco Unified MeetingPlace Administration Center|Signing In to the Cisco Unified MeetingPlace Administration Center]] module  
* [[Cisco Unified MeetingPlace Release 8.0 -- Signing In to the Cisco Unified MeetingPlace Administration Center#Signing In to the Cisco Unified MeetingPlace Administration Center|Signing In to the Cisco Unified MeetingPlace Administration Center]] module  
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module  
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module  
Line 276: Line 285:
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#How to Perform Application Server Failover|How to Perform Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#How to Perform Application Server Failover|How to Perform Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Application Server Software#Installing the Cisco Unified MeetingPlace Application Server Software|Installing the Cisco Unified MeetingPlace Application Server Software]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Application Server Software#Installing the Cisco Unified MeetingPlace Application Server Software|Installing the Cisco Unified MeetingPlace Application Server Software]] module
 +
 +
== How to Perform Application Server Failover ==
== How to Perform Application Server Failover ==
 +
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]
Line 283: Line 295:
=== Performing Application Server Failover  ===
=== Performing Application Server Failover  ===
-
 
Before you perform this task:
Before you perform this task:
* Node 1 is the current active server.
* Node 1 is the current active server.
* Node 2 is the current standby server.
* Node 2 is the current standby server.
-
 
After you complete the task:
After you complete the task:
Line 296: Line 306:
===== Before You Begin =====
===== Before You Begin =====
-
 
Set up Application Server failover by completing one of these sections:
Set up Application Server failover by completing one of these sections:
Line 307: Line 316:
===== Procedure =====
===== Procedure =====
-
 
# If the Node 1 is up, then complete these steps:  
# If the Node 1 is up, then complete these steps:  
Line 321: Line 329:
===== Verifying =====
===== 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.
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.
Line 327: Line 334:
===== Troubleshooting Tips =====
===== 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 [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command. To resolve this issue, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command description in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module.  
If the Administration Center displays the wrong failover mode on either or both servers, something might have interrupted the process initiated by the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command. To resolve this issue, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command description in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module.  
Line 333: Line 339:
===== Related Topics =====
===== Related Topics =====
 +
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module   
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module   
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Failover in Cisco WebEx Integrations|Failover in Cisco WebEx Integrations]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Failover in Cisco WebEx Integrations|Failover in Cisco WebEx Integrations]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]] module
 +
 +
=== Performing Application Server Failover to Switch to the Previous Active Server ===
=== Performing Application Server Failover to Switch to the Previous Active Server ===
-
 
Before you perform this task:
Before you perform this task:
* Node 1 is the current standby server.
* Node 1 is the current standby server.
* Node 2 is the current active server.
* Node 2 is the current active server.
-
 
After you complete the task:
After you complete the task:
Line 351: Line 358:
===== Before You Begin =====
===== Before You Begin =====
-
 
'''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 maintenance period.  
'''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 maintenance period.  
Line 359: Line 365:
===== Procedure =====
===== Procedure =====
-
 
# If Node 1 was brought to single-server mode, perform these steps:  
# If Node 1 was brought to single-server mode, perform these steps:  
Line 386: Line 391:
# Enter this command to change Node 1 to ''active ''mode:  
# Enter this command to change Node 1 to ''active ''mode:  
#: '''failoverUtil setServer active'''
#: '''failoverUtil setServer active'''
 +
===== Verifying =====
===== 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.
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.
Line 394: Line 399:
===== Troubleshooting Tips =====
===== 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 [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command. To resolve this issue, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command description in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module.
If the Administration Center displays the wrong failover mode on either or both servers, something might have interrupted the process initiated by the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command. To resolve this issue, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setServer|failoverUtil setServer]] command description in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module.
Line 400: Line 404:
===== Related Topics =====
===== Related Topics =====
 +
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module   
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module   
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]

Revision as of 14:46, 30 August 2010

Main page: Cisco Unified MeetingPlace, Release 8.0

Up one level: Configuration



Contents

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.


When a 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 unsuccessful, the rebooted node enables the eth0 interface and becomes the active server.


Related Topics


Prerequisites for Application Server Failover

  • Learn about failover deployment options in the Planning Guide for Cisco Unified MeetingPlace at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.
  • Install Cisco Unified MeetingPlace as described in the Quick Start for Installing and Configuring Cisco Unified MeetingPlace Release 8.0 module.
  • 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.


Related Topics


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.
  • Directory Service between two Application Servers is not supported in a failover deployment.
  • 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.
  • When you configure the Application Server for the Express Media Server, both the primary and secondary failover Express Media Servers must have the same licenses and port distribution for scheduled and ad-hoc meetings.
  • The time must be synchronized between the two Application Servers. This is required to resolve conflicts when the same piece of data is modified simultaneously in both Application 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 for MCS in the Integrating Cisco Unified MeetingPlace with Cisco WebEx module.
  • If you need to upgrade your system after setting up Application Server failover, make sure that you follow the failover-specific upgrade instructions in Upgrading Application Servers that are Used in a Failover Deployment in the Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0 module.


Related Topics


How to Configure Application Server Failover


Setting Up Failover for Two Newly Installed Application Servers

Before You Begin


Procedure
  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.
  2. Install any licenses on the first Application Server (Node 1). For details, see the Installing and Managing Licenses for Cisco Unified MeetingPlace module.
  3. Sign in to the CLI of Node 1.
    If you are signing in remotely, use the eth0 IP address or hostname.
  4. Enter this command to set up Node 1 for failover:
    failoverUtil setDeployment failover
  5. 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.
  6. 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.
    • Time is synchronized between Node 1 and Node 2.
  7. Install any licenses on the second Application Server (Node 2), and reboot the system. For details, see the Installing and Managing Licenses for Cisco Unified MeetingPlace module.
  8. Sign in to the CLI of Node 2.
    If you are signing in remotely, use the eth0 IP address or hostname.
  9. Enter this command to set up Node 2 for failover:
    failoverUtil setDeployment failover
  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.
  11. Enter this command to initialize database replication:
    mp_replication init -s 1 -n 2 -l node2-eth0:0-hostname -r node1-eth0:0-hostname -h
  12. Sign in to the CLI of Node 1.
    If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
  13. Enter this commands to initialize and start database replication:
    mp_replication init -s 1 -n 1 -l node1-eth0:0-hostname -r node2-eth0:0-hostname -h
    mp_replication switchON -r node2-eth0:0-hostname
  14. Enter this 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, 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.


Troubleshooting Tips

If the Administration Center in both nodes displays "Failover deployment. Standby server," something might have interrupted the process initiated in Step 14. To resolve this issue, see the failoverUtil setServer command description in the Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server module.


Related Topics


What To Do Next


Setting Up Failover for One Existing Application Server and One Newly Installed Application Server

In this task:

  • Node 1 is the existing Application Server.
  • Node 2 is the new Application Server.


Before You Begin


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


Procedure
  1. Install the second Application Server (Node 2), ensuring the following:
    • To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.
      This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.
    • Node 1 and Node 2 server times must be synchronized with each other.
  2. Sign in to the CLI of Node 1.
    If you are signing in remotely, use the Node 1 eth0 IP address or hostname.
  3. Enter this command to set up Node 1 for failover:
    failoverUtil setDeployment failover
  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.
  5. 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 1.
  6. 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.
  7. Enter mpx_sys restart to restart Node 2.
  8. Sign in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
  9. Enter this command to set up Node 2 for failover:
    failoverUtil setDeployment failover
  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.
  11. Enter this command to initialize database replication:
    mp_replication init -s 1 -n 2 -l node2-eth0:0-hostname -r node1-eth0:0-hostname -h
  12. Sign in to the CLI of Node 1.
    If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
  13. Enter these commands to initialize and start database replication and synchronize existing data:
    mp_replication init -s 1 -n 1 -l node1-eth0:0-hostname -r node2-eth0:0-hostname -h
    mp_replication switchON -r node2-eth0:0-hostname -S -F node1-eth0:0-hostname
  14. Enter this 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, 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.


Troubleshooting Tips

If the Administration Center in both nodes displays "Failover deployment. Standby server," something might have interrupted the process initiated in Step 14. To resolve this issue, see the failoverUtil setServer command description in the Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server module.


Related Topics


What To Do Next


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


Procedure
  1. Go to http://application-server/admin/.
    Use the shared eth0 hostname or IP address, which always goes to the active Application Server.
  2. Sign in as a System administrator.
  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
  4. If you made changes to any copied pages or parameters, then perform these steps:
    1. Sign in to the CLI of the active server.
      If you are signing in remotely, use the eth0 IP address or hostname.
    2. Enter this command to compress and transfer the files from the active server to the standby server:
      failoverUtil copyConfigFiles
    3. Sign in to the CLI of the standby server.
      If you are signing in remotely, use eth0:0 IP address or hostname.
    4. Enter this command to decompress the transferred files and put them in the correct directories on the standby server:
      failoverUtil restoreConfigFiles
  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.
    1. 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.
    2. Sign in as a System administrator.
    3. Verify that "Failover deployment. Standby server." appears at the top of the page.
    4. Configure the server-specific parameters on the standby server.


Related Topics


How to Perform Application Server Failover


Performing Application Server Failover

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:


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
  1. If the Node 1 is up, then complete these steps:
    1. Sign in to the CLI of Node 1.
      If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
    2. Enter this command to change the server to standby mode:
      failoverUtil setServer standby
  2. Sign in to the CLI of Node 2.
    If you are signing in remotely, use the Node 2 eth0:0 IP address or hostname.
  3. Enter this command to change the server to active mode:
    failoverUtil setServer active


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.


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 in the Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server module.


Related Topics


Performing Application Server Failover to Switch to the Previous Active Server

Before you perform this task:

  • Node 1 is the current standby server.
  • Node 2 is the current active server.

After you complete the task:

  • Node 1 will be the active server.
  • Node 2 will be the standby server.


Before You Begin

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 maintenance period.


Procedure
  1. If Node 1 was brought to single-server mode, perform these steps:
    1. Sign in to Node 2 using eth0:0 to bring Node 2 into Standby mode.
      failoverUtil setServer standby
    2. Sign in to the Node 1 CLI using the console.
    3. Enter this command to set up failover:
      failoverUtil setDeployment failover
    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.
    5. Enter this command to initialize database replication:
      mp_replication init -s 1 -n 1 -l node1-eth0:0-hostname -r node2-eth0:0-hostname -h
    6. Enter this command to synchronize existing data from Node 2 and start database replication:
      mp_replication switchON -r node2-eth0:0-hostname -S -F node2-eth0:0-hostname
  2. If Node 1 was never brought to single-server mode, but database replication configuration was removed from Node 1, do the following:
    1. Sign in to the CLI of Node 1.
      If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
    2. Enter this command to initialize database replication:
      mp_replication init -s 1 -n 1 -l node1-eth0:0-hostname -r node2-eth0:0-hostname -h
    3. Enter this command to synchronize existing data from Node 2 and start database replication:
      mp_replication switchON -r node2-eth0:0-hostname -S -F node2-eth0:0-hostname
  3. Sign in to the CLI of Node 2.
  4. Enter this command to change Node 2 to standby mode:
    failoverUtil setServer standby
  5. Sign in to the CLI of Node 1.
  6. Enter this command to change Node 1 to active mode:
    failoverUtil setServer active


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.


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 in the Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server module.


Related Topics

Rating: 0.0/5 (0 votes cast)

Personal tools