DocWiki - User contributions [en]

Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing

2012-11-10T00:35:59Z

Cgriffen: /* To Create a Least-Privileged SQL Account for Web Conferencing */

[[Cisco Unified MeetingPlace, Release 6.x]] > [[Cisco Unified MeetingPlace, Release 6.x#Web Conferencing|Web Conferencing]] > [[Cisco Unified MeetingPlace, Release 6.x -- Installing and Upgrading Web Conferencing|Installing and Upgrading]] > [[Cisco Unified MeetingPlace, Release 6.x -- Installing Web Conferencing|Installing Web Conferencing]]

We recommend that you complete the following optional tasks as applicable after installing the web conferencing software:
* [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Defining the Web Conferencing Server Hostname Information|Defining the Web Conferencing Server Hostname Information]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Testing the Web Conferencing Installation|Testing the Web Conferencing Installation]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Installing the Cisco Security Agent for Cisco Unified MeetingPlace Web Conferencing|Installing the Cisco Security Agent for Cisco Unified MeetingPlace Web Conferencing]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Creating and Using a Least-Privileged SQL Account for Web Conferencing|Creating and Using a Least-Privileged SQL Account for Web Conferencing]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Configuring SSL|Configuring SSL]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Installing Additional Fonts|Installing Additional Fonts]]

== Defining the Web Conferencing Server Hostname Information ==

If you want users to be able to access the Web Conferencing server by using the fully qualified domain name (FQDN) of the server, or if you plan to configure SSL for this server, do the following procedure.

'''Note: ''' If the web server is not in a Domain Name Server (DNS), do not perform these procedures.

===== To Access the Web Conferencing Home Page =====

Open your web browser, and enter the URL of your web server.
* For all releases, for internal web servers, the default URL structure is <nowiki>http://</nowiki> <server>, where <server> is the name of your internal web server.

* For Cisco Unified MeetingPlace Release 6.0 Maintenance Release 3 and earlier: For external web servers, the default URL structure is <nowiki>http://</nowiki> <server>/mpweb/admin/, where <server> is the name of your external web server.

* For Cisco Unified MeetingPlace Release 6.0 Maintenance Release 4 and later: You can only access the administration pages for the external (DMZ) server from the server box itself and only through port 8002. If you try to access the administration pages on the external (DMZ) server by using <nowiki>http://</nowiki> <server>/mpweb/admin/, the system will display a 404 "Page Not Found" error.

:To access the administration pages for the external (DMZ) server, you must be on the web server box and enter the following URL:

: http://localhost:8002/mpweb/admin/

:'''NOTE:''' If SSL is enabled on your system, you must still enter the URL with http and not https.

:The system automatically logs you in as the user called "technician" with technician privileges.

===== To Define the Cisco Unified MeetingPlace Web Conferencing Server Hostname Information =====

# When the Web Conferencing home page appears, sign in by using your System Manager-level user ID and password, then click ''' Sign In Now '''.
#: If you are on an internal web server, the Welcome page appears with your name displayed at the top. To access the administrative page, click ''' Admin '''.
#: If you are on an external web server, the administrative page appears.
# From the Admin page, click ''' Web Server '''.
# From the View section of the page, click the name of the web server that you want to configure.
#: Information about this web server populates the Edit section of the page.
# For Hostname [Home Page], enter the fully qualified domain name (FQDN) of the primary network interface on the web server, for example, ''' hostname.domain.com'''. Note the following considerations:
#* To use SSL, you must enter the FQDN.
#* This hostname must be resolvable by its intended users. (For details, see the [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Testing the Web Server Home Page Connection|Testing the Web Server Home Page Connection]] section.)
# For Hostname [Web Conferencing], enter the FQDN of the secondary network interface on the web server, for example, ''' hostnamewc.domain.com '''. Note the following considerations:
#* To use SSL, you must enter the FQDN.
#* This hostname must be resolvable by its intended users. (For details, see the [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Testing the Meeting Console Connection|Testing the Meeting Console Connection]] section.)
# Click ''' Submit '''.

== Testing the Web Conferencing Installation ==

After you install Cisco Unified MeetingPlace Web Conferencing, test the installation by completing the following tasks:

# [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Testing the Web Server Home Page Connection|Testing the Web Server Home Page Connection]]
# [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Testing the Meeting Console Connection|Testing the Meeting Console Connection]]

=== Testing the Web Server Home Page Connection ===

Confirm that the web server can resolve itself using the hostname configured on the Web Server administrative page. This is the hostname that you configured in [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Step 5|Step 5]] of the preceding section, [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Defining the Web Conferencing Server Hostname Information|Defining the Web Conferencing Server Hostname Information]], and is also the hostname that end users use to connect to this web server.

===== To Test the Web Server Home Page Connection =====

# From the web server, use a web browser to connect to ''' <nowiki> http://hostname.domain.com </nowiki>''', the Fully Qualified Domain Name, or FQDN, of the web server.
#: or
#: If the web server is not in a Domain Name Server (DNS), use a web browser to connect to an IP address from the web server.
# If the Cisco Unified MeetingPlace Web Conferencing home page appears, the connection is successful.
#: If an error message appears, see [[Cisco Unified MeetingPlace, Release 6.x -- Web Conferencing Server Connection Problems# Web Conferencing Server Connection Problems| Web Conferencing Server Connection Problems]].

=== Testing the Meeting Console Connection ===

===== To Test the Meeting Console Connection =====

# From an end-user system, open a web browser and enter the Cisco Unified MeetingPlace Web Conferencing URL in the address field and click ''' Enter '''.
# Sign in by using your System Manager-level user ID and password.
# From the Welcome page, click ''' Schedule Meeting '''.
# From the New Meeting scheduling page, fill in your meeting details, then click ''' Schedule '''.
# Return to the Welcome page and enter the meeting ID of the meeting you just scheduled, then click ''' Attend Meeting '''.
# Confirm that the meeting console loads properly.

== Installing the Cisco Security Agent for Cisco Unified MeetingPlace Web Conferencing ==

For instructions on installing the Cisco Security Agent, refer to the applicable'' Release Notes for Cisco Security Agent for Cisco Unified MeetingPlace '' at
http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html.

== Creating and Using a Least-Privileged SQL Account for Web Conferencing ==

By default, the Cisco Unified MeetingPlace Web Conferencing installer suggests using the SQL built-in sa administrator account as the SQL Server user name. Often, a strong password for the sa account is sufficiently secure to protect your system from unauthorized access. However, if you do not want to continue to use a SQL account that has full administration rights after the installation is complete, you can create a SQL account with minimal privileges that is dedicated to Web Conferencing use, and configure the Web Conferencing server to use this account.

To create and use a least-privileged SQL account, do the following tasks in the order presented:

# [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Creating a Least-Privileged SQL Account for Web Conferencing|Creating a Least-Privileged SQL Account for Web Conferencing]]
# [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility|Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility]]

=== Creating a Least-Privileged SQL Account for Web Conferencing ===

'''Caution! ''' If you choose to create a SQL account that is dedicated to Web Conferencing use, ensure that it meets all the specified database role requirements in this procedure. Failure to do so can cause a database connection failure between Web Conferencing and the SQL Server and result in a total outage or broken features.

'''Note: ''' If Cisco TAC determines that your SQL account does not meet requirements, you will be asked to reconfigure your SQL account and to delete any existing Cisco Unified MeetingPlace Web Conferencing database so that a new database can be created once the account problem is remedied.

===== To Create a Least-Privileged SQL Account for Web Conferencing =====

# Open the SQL Server Enterprise Manager and create a new login:
## On the Start menu, click ''' Programs > SQL Server 2000 > Enterprise Manager '''.
## Click a server group to expand it, then click the name of a server.
## Click ''' Security ''' to expand it.
## Click ''' New Login '''. The SQL Server Login Properties window opens.
# On the General tab, enter a name for the login.
# Click ''' SQL Server Authentication ''', then enter a password for the account.
# In the Database drop-down menu, click ''' MPWEB ''' to set the MPWEB database as the default database.
# Click the ''' Database Access ''' tab.
# Specify the database roles for the MPWEB database:
## In the Databases table, click the check box for the MPWEB database.
## In the Database Roles table, click the check boxes for the following roles:
##* ''' db_datareader '''
##* ''' db_datawriter '''
##* ''' db_ddladmin '''
##* ''' db_owner '''
# Repeat [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#Step 6|Step 6]] for each additional MPWEB slave database. The slave databases have names that begin with "MPWEB_". Depending on your deployment, your SQL Server will have either one or two slave databases.
# Click ''' OK ''' to complete the account configuration.

=== Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility ===

The MeetingPlace Gateway Configurations utility allows you to update the web server with the least-privileged SQL login account that you created in [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#To Create a Least-Privileged SQL Account for Web Conferencing|To Create a Least-Privileged SQL Account for Web Conferencing]]. It does not create a SQL Server login for you.

===== To Update SQL Account Access from the MeetingPlace Gateway Configurations Utility =====

# Stop the Cisco Unified MeetingPlace Web Conferencing Service:
## From the Windows Start menu, choose ''' Settings > Control Panel > Administrative Tools > Services '''.
## Right-click Cisco Unified MeetingPlace Web Conferencing and choose ''' Stop '''.
## (Optional) To stop other Cisco Unified MeetingPlace gateway services, including Gateway SIM, right-click the service and choose ''' Stop '''.
## If the IIS Admin Service is still running, right-click the service and choose ''' Stop '''.
## Close the Services control panel.
# Open the MeetingPlace Gateway Configurations utility:
## From your system tray, right-click the Cisco Unified MeetingPlace icon.
## Choose ''' Properties '''.
# Click the ''' Web Conferencing ''' tab.
# For Server, enter the hostname or IP address of the SQL Server you want to update. For a local server, enter ''' local '''.
# For Username and Password, enter the login account username and password you applied to the SQL Server in [[Cisco Unified MeetingPlace, Release 6.x -- Postinstallation Tasks: Web Conferencing#To Create a Least-Privileged SQL Account for Web Conferencing|To Create a Least-Privileged SQL Account for Web Conferencing]].
# Click ''' OK '''.
# Restart the Cisco Unified MeetingPlace Web Conferencing Service:
## From the Windows Start menu, choose''' Settings > Control Panel > Administrative Tools > Services. '''
## Right-click Cisco Unified MeetingPlace Web Conferencing and choose ''' Start '''.
## If you stopped any other gateway services, restart them by right-clicking the applicable service and choosing ''' Start '''.
## Close the Services control panel.

== Configuring SSL ==

For instructions on configuring SSL, see [[Cisco Unified MeetingPlace, Release 6.x -- Configuring External Access to Web Conferencing|Configuring External Access to Web Conferencing]]

== Installing Additional Fonts ==

In order for Web Conferencing to work with other languages, you must install all of your corporate fonts, including Microsoft PowerPoint fonts, on to the web server.

If you do not do this, PowerPoint presentations that are uploaded or attached to your meeting will not be converted correctly if they use unavailable fonts.

[[Cisco Unified MeetingPlace, Release 6.x]] > [[Cisco Unified MeetingPlace, Release 6.x#Web Conferencing|Web Conferencing]] > [[Cisco Unified MeetingPlace, Release 6.x -- Installing and Upgrading Web Conferencing|Installing and Upgrading]] > [[Cisco Unified MeetingPlace, Release 6.x -- Installing Web Conferencing|Installing Web Conferencing]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing

2012-11-09T22:29:53Z

Cgriffen: /* Procedure */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

By default, the Cisco Unified MeetingPlace Web Conferencing installer suggests using the SQL built-in sa administrator account as the SQL Server user name. Often, a strong password for the sa account is sufficiently secure to protect your system from unauthorized access. However, if you do not want to continue to use a SQL account that has full administration rights after the installation is complete, you can create a SQL account with minimal privileges that is dedicated for use with Cisco Unified MeetingPlace Web Conferencing, and configure the Web Server to use this account.

Complete the following procedures in the order shown to create and use a least-privileged SQL account:

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing#Creating a Least-Privileged SQL Account for Web Conferencing|Creating a Least-Privileged SQL Account for Web Conferencing]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing#Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility|Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility]]

== Creating a Least-Privileged SQL Account for Web Conferencing ==

'''Caution! ''' If you choose to create a SQL account that is dedicated for use with Cisco Unified MeetingPlace Web Conferencing, ensure that it meets all the specified database role requirements in this procedure. Failure to do so can cause a database connection failure between the web conferencing application and the SQL Server and result in a total outage or broken features.

'''Note: ''' If Cisco TAC determines that your SQL account does not meet requirements, you will be asked to reconfigure your SQL account and to delete any existing Cisco Unified MeetingPlace Web Conferencing database so that a new database can be created once the account problem is remedied.

===== Procedure =====

# Open the SQL Server Enterprise Manager and create a new login:
## On the Start menu, click '''Programs > SQL Server 2000 > Enterprise Manager'''.
## Click a server group to expand it, then click the name of a server.
## Click '''Security > New Login'''.
#: The SQL Server Login Properties window displays.
# Enter a name for the login on the General tab.
# Click '''SQL Server Authentication'''.
# Enter a password for the account.
# Click '''MPWEB''' from the Database drop-down menu to set the MPWEB database as the default database.
# Click the '''Database Access''' tab.
# Specify the database roles for the MPWEB database:
## Check the '''MPWEB''' database in the Databases table.
## Check the boxes for the following roles in the Database Roles table:
#** db_datareader
#** db_datawriter
#** db_ddladmin
#** db_owner
# Repeat [[Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing#Step 7|Step 7]] for each additional MPWEB slave database.
#: The slave databases have names that begin with "MPWEB_". Depending on your deployment, your SQL Server will have either one or two slave databases.
# Click '''OK''' to complete the account configuration.

== Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility ==

The MeetingPlace Gateway Configurations utility allows you to update the Web Server with the least-privileged SQL login account that you have already created. It does not create a SQL Server login or update the SQL Server for you.

===== Before You Begin =====

Change the username and password on SQL Server. See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing#Creating a Least-Privileged SQL Account for Web Conferencing|Creating a Least-Privileged SQL Account for Web Conferencing]] for instructions.

===== Procedure =====

# Stop the Cisco Unified MeetingPlace Web Conferencing Service.
# Open the MeetingPlace Gateway Configurations utility.
# Click the '''Web Conferencing''' tab.
# Enter the hostname or IP address of the SQL Server that you want to update in the Server field.
#* Enter '''local''' for a local server.
# Enter the username and password that you applied to the SQL Server.
# Click '''OK'''.
# Restart the Cisco Unified MeetingPlace Web Conferencing Service.

'''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost.

===== Related Topics =====
* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Use the Cisco Unified MeetingPlace Web Conferencing Service#Stopping All Web Conferencing Services|Stopping All Web Conferencing Services]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Use the Cisco Unified MeetingPlace Web Conferencing Service#Restarting All Web Conferencing Services|Restarting All Web Conferencing Services]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Opening the MeetingPlace Gateways Configuration Utility|Opening the MeetingPlace Gateways Configuration Utility]]

[[Category: Configuring Web Conferencing for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.1 -- Integration Requirements

2012-11-02T00:38:11Z

Cgriffen: /* Microsoft Outlook Integration */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.1]]

'''Previous page:''' [[Cisco Unified MeetingPlace, Release 7.1 -- System Requirements|System Requirements]]

== Cisco WebEx Integration==

'''Table: Requirements for the Cisco WebEx integration with Cisco Unified MeetingPlace Release 7.1'''

{| border = 1
|-
!Component
!Requirement
|-
|

Hardware
|

* For Integration Option 1 (schedule and attend Cisco WebEx meetings from Cisco Unified MeetingPlace) only:
** Cisco Unified MeetingPlace requires that your system contain at least one internal Cisco Unified MeetingPlace Web Server (or cluster). The system can optionally also contain an external Web Server(or cluster).
** Part of the Cisco WebEx gateway software is installed on the Web Server.

* Cisco Unified MeetingPlace URLs are published in Cisco Unified MeetingPlace notifications that provide automatic redirect to the Cisco WebEx MeetingCenter upon joining, for both internal users and external guest users via the Cisco Unified MeetingPlace Web Servers deployed.

* A Cisco MCS-7835 can be used for web scheduling and up to 250 concurrent web redirect sessions.

* A Cisco MCS-7845 can be used for up to 500 concurrent web redirect per Web Server with a maximum of 100 meetings.

* No Cisco Unified MeetingPlace web user licenses are required or used with Cisco WebEx.

|-
|
Software
|
* Cisco Unified MeetingPlace Release 7.1 requires Cisco WebEx Release WBS 27 on the Cisco WebEx site.

* Cisco Unified MeetingPlace requires Cisco WebEx MeetingCenter or Cisco WebEx MeetingCenter Pro.
|}

=== Limitations and Restrictions ===

* MeetingPlace Application Server WebEx TSP only support SOCKS web proxy servers (not HTTP proxy). Allow direct firewall access to WebEx Site IPs directly. Often there are delay issues when proxy servers are used. The system must be able to continuously maintain its links to the WebEx integration, otherwise user response times may be affected.

* A Cisco WebEx integration can have a maximum of 1000 user ports per system.

* The Cisco WebEx integration on the Cisco Unified MeetingPlace Application Server does not support redundancy and failover deployments.

* The Media Servers may be redundant (which provides active DSP redundancy).

* Cisco WebEx is only supported for use with Cisco Unified MeetingPlace web conferencing and the Cisco Unified MeetingPlace for Microsoft Outlook integration. It cannot be used with the IBM Lotus Notes for Cisco Unified MeetingPlace integration.

* Cisco WebEx does not support Cisco Unified MeetingPlace for Microsoft Office Communicator.

* Cisco WebEx does not support Cisco Unified MeetingPlace RSNA.

* Cisco Unified MeetingPlace unique profile numbers must be eight digits or less. The profile number is typically the telephone number of an end user and usually does not include the country code or area code.

* If scheduling from the Cisco Unified MeetingPlace web user portal, the meeting scheduler can choose to define certain users as "alternate hosts". Alternate hosts can start the meeting if the meeting scheduler does not arrive on time.
** If you schedule your meeting from an alternate scheduling interface, such as the Microsoft Outlook integration, you can still define certain users as alternate hosts from the Cisco Unified MeetingPlace web user portal.
**Users must have their e-mail address, first name, and last name set in their user profiles in order to be listed as alternate hosts.
** If any user who is defined as an alternate host does ''not'' have this information listed, the system marks the meeting invalid and locks it. This prevents any user from attending the meeting, including the meeting scheduler, even if all other alternate hosts and the meeting host have an e-mail address, first name, and last name set in their user profiles.
** If a user defined as an alternate host does not have their e-mail address, first name, and last name set in their user profile, the system will set the accounts of all other users who are attempting to attend the ''same'' meeting to inactive on Cisco WebEx and remove their ability to attend any meetings. This includes users who have their e-mail address, first name, and last name set in their user profiles.
** If you invite an alternate host whose Cisco WebEx user account is inactive, the system will "hang" and the alternate host will see a blank window.

'''Note:''' We highly recommend that you populate the user profile for anyone who will ever be invited to a Cisco WebEx meeting with an e-mail address, first name, and last name.

=== Types of Cisco WebEx Service Contracts ===

'''Minutes'''

With this model, Cisco WebEx charges the customer for web-meeting minutes consumed by attendees.

'''Concurrent Ports'''

With this model, the customer purchases a certain number of Cisco WebEx ports. A port corresponds to a web-meeting attendee. The number of attendees that can join meetings system-wide is limited to the number of ports purchased; hence the term "concurrent ports".

'''Named Host'''

With this model, only someone who is explicitly named as a host can schedule a meeting.

The Named Host license requires a Cisco WebEx user account for each profiled user of Cisco Unified MeetingPlace. If there are more Cisco Unified MeetingPlace users than Cisco WebEx users, some users will be able to schedule but not actually join the meeting.

== IBM Lotus Notes Integration ==

For the IBM Lotus Notes with Cisco Unified MeetingPlace integration, you need an Application Server, a Web Server (which also hosts the integration), and an IBM Lotus Domino server.

'''Note:''' Multiple clusters are not supported for the IBM Lotus Notes integration for Cisco Unified MeetingPlace.

'''Table: Requirements for the IBM Lotus Notes integration with Cisco Unified MeetingPlace Release 7.1'''

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Domino Server
|

'''Hardware'''
* Microsoft Windows computer.

'''Operating System'''
* Windows.

'''Software'''
* IBM Lotus Domino Release 6.0x, 6.5x, 7.0x, 8.0x or 8.5
|-
|
Cisco Unified MeetingPlace Web Server

'''Note: ''' The Cisco Unified MeetingPlace for IBM Lotus Notes integration is installed on the Web Server.
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later.

'''License'''
* The Cisco Unified MeetingPlace ''lotusnotes'' license.

'''Software'''
* IBM Lotus Notes client Release 6.0.x, 6.5.x, 7.0.x, 8.0.x or 8.5
* Microsoft Internet Information Server (IIS) Release 6.0.

'''Note: ''' Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.
|-
|
Cisco Unified MeetingPlace Application Server
|
See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-

|

End-User System
|
''' Hardware'''
* Microsoft Windows computer.

''' Software'''
* Templates 6.0.4, 6.0.5, 6.5.4, 6.5.5, 6.5.6, 7.0.2, 7.0.3, 8.0 and 8.5
* Users of IBM Lotus Domino Server Release 6 require:
** IBM Lotus Notes Release 6.0.4 or 6.0.5
** Template of the same release as the client or an earlier release
* Users of IBM Lotus Domino Server Release 6.5 require:
** IBM Lotus Notes Release 6.54., 6.5.5, or 6.5.6
** Template of the same release as the client or an earlier release
* Users of IBM Lotus Domino Server Release 7 require:
** IBM Lotus Notes Release 7.0.2 or 7.0.3
** Template of the same release as the client or an earlier release
* Users of IBM Lotus Domino Server Release 8 require:
** IBM Lotus Notes Release 8.0 and 8.5
** Template of the same release as the client or an earlier release

''' Operating System'''
* One of the following:
** Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 Server Edition (Service Pack 2 or later)
** Windows 2000 Advanced Server Edition (Service Pack 2 or later)
** Windows XP
|}

== IBM Lotus Sametime Instant Messaging Integration ==

For the IBM Lotus Sametime Instant Messaging integration, you need the following servers:
* Cisco Unified MeetingPlace Application Server
* Cisco Unified MeetingPlace Media Server
* IBM Lotus Sametime Server

'''Table: Requirements for the IBM Lotus Sametime Instant Messaging integration with Cisco Unified MeetingPlace Release 7.1'''

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Sametime Server
|

'''Software'''
* IBM Lotus Sametime Release 7.5.1
* IBM Lotus Notes Release 8.0.1
|-
|
Cisco Unified MeetingPlace Application Server

|
See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

|-
|

Cisco Unified MeetingPlace Media Server
|
See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Media Server Requirements|Media Server Requirements]].
|-
|

End-User System
|
''' Hardware'''
* Microsoft Windows

''' Software'''
* IBM Lotus Sametime Connect Client Version 7.5.1
* Client Browsers
** Mozilla 1.7.12 on Windows XP
** Firefox 1.5 on Windows XP
** Firefox 2.0
** Internet Explorer 6.0, 7.0 on Windows XP Professional, Windows XP Professional 64-bit

''' Operating System'''
* Microsoft Windows
** Windows XP Professional Service Pack 2
** Windows XP Professional 64-bit only for Web Conferencing
** Windows 2000
** Microsoft Vista
|}

== IBM Lotus Sametime Web Integration ==

For the IBM Lotus Sametime Web integration, you need the following servers:
* Cisco Unified MeetingPlace Application Server
* Cisco Unified MeetingPlace Media Server
* IBM Lotus Sametime Standard Server

'''Notes: '''
* Because the IBM Lotus Sametime Server cannot support multiple Telephony Conferencing Service Provider Interface (TCSPI) server-side integrations, you cannot use both of the following integrations at the same time:
** Cisco Unified MeetingPlace for IBM Lotus Sametime Web Standard (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified MeetingPlace)
** Cisco Click to Call and Conference with IBM Lotus Sametime (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified Communications Manager)
*: These two server-side integrations are mutually exclusive and cannot both be deployed at the same time.
* You can, however, deploy Cisco Unified MeetingPlace for IBM Lotus Sametime Web with either or both of the following client-side integrations:
** Cisco Unified Messaging with IBM Lotus Sametime
** Cisco Phone Control and Presence with IBM Lotus Sametime

''' Table: Requirements for the IBM Lotus Sametime Web integration with Cisco Unified MeetingPlace Release 7.1 '''

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Sametime Server (Standard)
|

'''Hardware'''
* Microsoft Windows computer

'''Operating System'''
* Windows 2000 Server
* Windows Server 2003 Standard
* Windows Server 2003 Enterprise Edition Service Pack 2

'''Software'''
* IBM Lotus Sametime Standard Server 7.5.1 CF1
: Also see the server requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.
* IBM Lotus Sametime Standard Server 8.0.1
: Also see the server requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.

'''Note: ''' If you also deploy the Cisco Phone Control and Presence with IBM Lotus Sametime integration, then you must use IBM Lotus Sametime Server 8.0.1 and install the following IBM patches to disable the IBM phone icon: 3AAAFEAB, 49D5219C, 643A31, 662A775A, 77D5E39D.
|-

|
Cisco Unified MeetingPlace Application Server

|
See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

|-
|

Cisco Unified MeetingPlace Media Server
|
See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Media Server Requirements|Media Server Requirements]].
|-
|

End-User System
|
* IBM Lotus Sametime Connect Client Version 7.5.1 CF1
: Also see the client requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.
* IBM Lotus Sametime Connect Client Version 8.0
: Also see the client requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.
|}

== Jabber Integration ==

For the Jabber with Cisco Unified MeetingPlace integration, you need an Application Server, a Web Server, and a Jabber XCP server.

''' Table: Requirements for the Jabber integration with Cisco Unified MeetingPlace Release 7.1 '''

{| border = 1
|-
!Component
!Requirement
|-
|

Jabber XCP server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Windows.

'''Software'''
* Jabber XCP server Release 5.1
* Sun Java Runtime Environment (JRE) Release 1.4.2.xx
|-
|
Cisco Unified MeetingPlace Web Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later

'''Software'''
* Jabber XCP server Release 5.1
* Sun Java Runtime Environment (JRE) Release 1.4.2.xx

'''License'''
* Cisco Unified MeetingPlace ''jabber'' license

'''Other'''
* Microsoft Internet Information Server (IIS) Release 6.0

'''Note: ''' Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.
|-
|

Cisco Unified MeetingPlace Application Server

|

See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|

End-User System
|

'''Hardware'''
* Microsoft Windows computer

'''Software'''
* Jabber Messenger Release 3.2, Windows version

'''Operating System'''
* Windows

'''Other'''
* End users who initiate Cisco Unified MeetingPlace meetings from Jabber Messenger must be profiled users in Cisco Unified MeetingPlace.
|}

== Microsoft Office Communicator (MOC) Integration ==

For the Cisco Unified MeetingPlace for Microsoft Office Communicator (MOC) integration, you need an Application Server, a Web Server (which also hosts the integration), and a Live Communications Server (LCS).

''' Table: Requirements for the Microsoft Office Communicator integration with Cisco Unified MeetingPlace Release 7.1 '''

{| border = 1
|-
!Component
!Requirement
|-
|

LCS Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Microsoft Windows 2003

'''Software'''
* Microsoft Live Communications Server (LCS) 2005 Standard or Enterprise Edition
|-
|

Cisco Unified MeetingPlace Application Server
|
See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|
Cisco Unified MeetingPlace Web Server

|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later.

'''Software'''
* Windows 2003

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.

'''Other'''
* Microsoft .NET 2.0
|-
|

End user
|

'''Hardware'''
* Microsoft Windows computer

'''Software'''
* Microsoft Office Communicator 2005

'''Operating System'''
* Microsoft Windows 2003
|}

== Microsoft Outlook Integration ==

'''Note:''' Cisco Unified MeetingPlace for Microsoft Outlook does not support "thin clients" (Citrix or Terminal Server).

''' Table: Requirements for the Microsoft Outlook integration with Cisco Unified MeetingPlace Release 7.1'''

{| border = 1
|-
!System
!Requirements
|-
|

Microsoft Exchange Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Software'''
* Microsoft Exchange Server 2003 Service Pack 2
: Enable WebDAV access from Cisco Unified MeetingPlace.
* Microsoft Exchange Server 2007 Service Pack 1 and later
: Enable EWS access from Cisco Unified MeetingPlace and use the Client Access server role.
* Microsoft Exchange Server 2010, Microsoft Exchange Server 2010 Service Pack 1, or Microsoft Exchange 2010 Service Pack 2
: Microsoft Exchange Server 2010 has SSL encryption turned on by default. Make sure that the proper SSL certificate is generated or that SSL is turned off on the Exchange server.

'''Note:''' EWS replaces CDO as the interface to integrate with Microsoft Exchange 2007. EWS retrieves data from the Cisco Unified MeetingPlace mailbox in order to be able to send update notifications for those meetings scheduled from MP Web. It is also used to perform maintenance tasks, such as deleting old inbox items, for the Cisco Unified MeetingPlace mailbox.

|-

|

Cisco Unified MeetingPlace Application Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.1 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|

End-user system
|

'''Hardware'''
* Microsoft Windows computer

''' Software'''
* One of the following:
** Microsoft Outlook XP
** Microsoft Outlook 2003 Service Pack 3
** Microsoft Outlook 2007 Service Pack 2
** Microsoft Outlook 2010 (32-Bit or 64-Bit Edition)
* An HTTP or HTTPS connection to Cisco Unified MeetingPlace for Microsoft Outlook
* Cisco Unified MeetingPlace for Microsoft Outlook plug-in
*:'''Note:''' If you are upgrading from Release 7.0.2 or 7.0.3 to 7.1 and you currently have a plug-in for Microsoft Outlook 2007, you must upgrade your plug-in as part of your upgrade to Release 7.1. If you are upgrading from Release 7.0.2 or 7.0.3 and have a plug-in for Microsoft Outlook 2003, we strongly recommend that you also upgrade your Microsoft Outlook plug-in.

''' Operating System'''
* One of the following:
** Microsoft Windows ME
** Windows 2000 Professional
** Windows 2000 SE with Service Pack 2
** Windows 2000 AS with Service Pack 2
** Windows XP Professional
** Windows Server 2003
** Windows 7 32-Bit or 64-Bit Edition (Professional, Business, or Ultimate)
** Windows Vista 32-Bit or 64-Bit Edition (Enterprise, Business, or Ultimate)

|}

== Supported Cisco Unified IP Phones for Cisco Unified MeetingPlace PhoneView ==

The following Cisco Unified IP Phones are supported in Cisco Unified MeetingPlace Release 7.1:
* Cisco Unified IP Phone 9971
* Cisco Unified IP Phone 7940 and 7960 models (SCCP only)
* Cisco Unified IP Phone 7941 and 7961 models
* Cisco Unified IP Phone 7970 and 7971 models
* Cisco IP Communicator 1.1(5) or later
* Cisco Unified IP Phone 7942 and 7945 models
* Cisco Unified IP Phone 7962 and 7965 models
* Cisco Unified IP Phone 7975 model

[[Category:Requirements for Cisco Unified MeetingPlace, Release 7.1]]

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

2012-10-31T05:10:34Z

Cgriffen: /* How to Configure Application Server Failover */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|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#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 Perform 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. Profile recorded names are not replicated automically. 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 =====

* [[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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[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

== 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 [[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.
* 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 =====

* [[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]]

== 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]].
* 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 [[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 you need to upgrade your system after setting up Application Server failover, make sure that you follow the failover-specific upgrade instructions in [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0|Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0]] module.

===== 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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] 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

== How to Configure Application Server Failover (Cisco Unified MeetingPlace 8.0.2) ==

* [[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#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 ===

===== 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]].
* 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]].

===== Procedure =====

# 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.
# Install any licenses on the first Application Server (Node 1). For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter this commands to initialize and start database replication:
#: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
#: '''mp_replication switchON -S -F''' ''from-sync'' '''[-v]'''
# 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 [[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 =====

* [[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

===== 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.
* 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 ===

In this task:
* Node 1 is the existing Application Server.
* Node 2 is the new Application Server.

===== 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]].
* 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]].
* Back up and archive the data on the existing Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

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

===== Procedure =====

# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the Node 1 eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in Step 1.
# Enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#net|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.
# Enter '''mpx_sys restart''' to restart Node 2.
# Sign in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter these 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]'''
# 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 [[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.

===== 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

===== 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.
* 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 ===

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:
** [[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]]
* 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 =====

# Go to '''http://'''''application-server'''''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Sign in as a System administrator.
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
#: The "copyConfigFiles" commands will include recorded name files as well.

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

===== What to Do Next =====

Perform the following from both Application Servers to replicate custom prompts and some configurations from the Primary application server to the Standby application server during a maintenance window or off-peak hours.

# Log in to the CLI of the active server.
#:If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to compress and transfer the files from the active server to the standby server:
#:'''failoverUtil copyConfigFiles'''
#:This will compress and copy over configuration files and user prompts to the remote server.
# Log in to the CLI of the standby server.
#:If you are logging in remotely, use eth0:0 IP address or hostname.
# Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
#:'''failoverUtil restoreConfigFiles'''
#: This action copies over custom prompts including customized system prompts and user name recordings. Without this action .wav files are not replicated to the standby server.

===== 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 -- 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
* ''Integration Guide for Installing and Configuring Microsoft Outlook with Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html
* [[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 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace#Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]] module
* [[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

== How to Configure Application Server Failover (Cisco Unified MeetingPlace 8.0.1) ==

===== Before You Begin =====
* Note the following nomenclature that is used for clarity: node 1 is the server that originally is the active Application Server and node 2 is the server that originally is the standby Application Server.
* Turn off failover before you begin.

===== Procedure =====

#Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Enter '''su - '''to switch to the root user.
#Enter '''mp_replication status''' on node 1 to ensure that all database changes have been synchronized.
#:The system displays the queue column as zeroes.
#Enter '''mp_replication switchOFF -r'''''node_2_eth0:0 ''on node 1, to switch off replication between the two Application Servers, where ''node_2_eth0:0''is the eth0:0 address for node 2.
#Enter '''mp_replication teardown -r '''''node_2_eth0:0 ''on node 1, to tear down the replication setup with the remote Application Server, where ''node_2_eth0:0''is the eth0:0 address for node 2.
#Archive and save the configuration data on node 1.
#Enter '''failoverUtil setDeployment singleServer '''to change the mode of node 1 to SingleServer.
#Upgrade node 1. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading_the_Application_Server_by_Using_the_Console|Upgrading the Application Server by Using the Console]].
#Enter '''failoverUtil setDeployment failover '''on node 1 to change the mode of node 1 to failover.
#:'''Note: ''' This disables the eth0 interface of node 1, so that node 2 can become active.
#Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Enter '''su - '''to switch to the root user.
#Enter '''failoverUtil setServer active''' on node 2 to change its mode from standby to active.
#Enter '''mp_replication teardown -r '''''node_1_eth0:0 ''on node 2, to tear down the replication setup with the remote Application Server, where ''node_1_eth0:0''is the eth0:0 address for node 1.
#Enter '''failoverUtil setDeployment singleServer''' on node 2 to change its mode to SingleServer.
#Upgrade node 2. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading_the_Application_Server_by_Using_the_Console|Upgrading the Application Server by Using the Console]].
#Enter '''failoverUtil setDeployment failover''' on node 2 to change its mode to failover.

 At this point, both Application Servers are in standby mode.

#Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Initialize database replication:
#*Release 8.0 MR1--Enter '''mp_replication init -n 2 -r <''node1-eth0:0-hostname''> [-v]'''
#*Release 8.0 FCS-- Enter'''mp_replication init -s 1 -n 2 -l node2-eth0:0 -r node1-eth0:0 -h'''
#Sign in to the CLI of Node 1. If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
#Enter the following to initialize and start database replication:
#*Release 8.0 MR1
#::'''mp_replication init -n 1 -r <''node2-eth0:0-hostname''> [-v]'''
#::'''mp_replication switchON '''
#*Release 8.0 FCS
#::'''mp_replication init -s 1 -n 1 -l node1-eth0:0 -r node2-eth0:0 -h'''
#::'''mp_replication switchON -r node2-eth0:0'''
#Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Enter '''failoverUtil setServer active''' on node 1 to change its mode to active.
#:Node 1 is the active Application Server and node 2 is the standby Application Server.

===== 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 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server Remotely|Upgrading the Application Server Remotely]]

== 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 to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]

=== 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:
* [[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]]

'''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 =====

# If the Node 1 is up, then complete these steps:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## Enter this command to change the server to ''standby'' mode:
##: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 2.
#: If you are signing in remotely, use the Node 2 eth0:0 IP address or hostname.
# Enter this command to change the server to ''active ''mode:
#: '''failoverUtil setServer active'''
# Restart the MCUs manually to resynchronize them or complete the steps in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Resynchronizing the MCUs|Resynchronizing the MCUs]].

===== 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 [[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.

===== 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 -- 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

=== 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.
* 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]].
* Back up and archive the data on the currently active Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

===== Procedure =====

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

===== 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 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]
* [[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

===Resynchronizing the MCUs===

=====Procedure=====

#Sign in to the Media Server Administration for the Hardware Media Server.
#Select '''Resource Management > MCU''' from the left panel.
#Select the name of the Audio Blade.
#Select '''Synchronize''' on the Resource Management page.
#Select '''OK''' at the informational message.
#Select '''Synchronize''' on the Active Meeting Types page.
#:The system displays a message that the meetings were downloaded successfully.
#Select '''OK'''.

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace Release 8.5 -- System Requirements for Audio-Only Deployments

2012-10-30T17:40:37Z

Cgriffen: /* Network Requirements */

'''Main page:''' [[Cisco Unified MeetingPlace Release 8.5]]

'''One page up:''' [[Cisco Unified MeetingPlace Release 8.5 -- System Requirements|System Requirements]]

'''Print PDF:''' [[Cisco Unified MeetingPlace Release 8.5 -- Print System Requirements]]

The audio-only deployment supports a maximum of two nodes in an active/standby configuration.

==Hardware and Software Requirements==

Audio-only deployments require the following components:

{| border = 1
|-
!Component
!Requirement
|-
|

Cisco Unified MeetingPlace Application Server

|

'''Hardware'''

See the [[Cisco Unified MeetingPlace Release 8.5 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

'''Software'''

* Cisco Unified MeetingPlace Application Server Release 8.5/Express Media Server (EMS)
* Cisco Security Agent Release 6.0.1.112

'''Notes:'''

*The Express Media Server is a set of software modules that reside on the Application Server. During installation, you will have the option to choose either the Hardware Media Server or the Express Media Server. For details about the EMS, see the [[Cisco Unified MeetingPlace Release 8.5 -- Hardware Requirements#Express Media Server Requirements|Express Media Server Requirements]].
* The Cisco Security Agent software is packaged and installed during the Application Server installation. For details, see the "Using Cisco Security Agent (CSA) on the Application Server" in the ''Configuration Guide for Cisco Unified MeetingPlace Release 8.5'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.
* The Cisco Unified MeetingPlace integration for Microsoft Outlook scheduling is included on the Application Server.

|-
|

Cisco Unified MeetingPlace Web Server

'''Note:''' This is an optional component based on your deployment requirements.
|

An internally deployed Cisco Unified MeetingPlace Web Server can be used for the following:

*Audio or audio/video recordings with optional customer-provided SAN/NAS storage option
* Installation of the Cisco Unified MeetingPlace integration for IBM Lotus Notes

'''Note:''' If you plan to use the MeetingPlace web scheduling interface, see the [[Cisco Unified MeetingPlace Release 8.5 -- System Requirements for MeetingPlace-Scheduling Deployments|System Requirements for MeetingPlace-Scheduling Deployments]] instead.

'''Hardware'''

See the [[Cisco Unified MeetingPlace Release 8.5 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Software'''

*(Optional) Cisco Security Agent Release 6.0.1.117 for Cisco Unified MeetingPlace
*(Optional) Cisco Unified MeetingPlace Web Server Release 8.5

|-
|

Cisco Unified Communications Manager
|

'''Hardware'''

Cisco Media Convergence Server (MCS)

For information about physically installing the Cisco MCS, see the documentation at this location: http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_installation_guides_list.html

'''Note:''' Make sure that the specific Cisco MCS model supports the number of SIP sessions that are required by your Cisco Unified MeetingPlace system.

'''Software'''

Cisco Unified MeetingPlace Release 8.5 supports the following versions of Cisco Unified Communications Manager (CUCM):

*CUCM 6.1(5), 7.0(2), 7.1(5), 8.0(1), 8.0(2), 8.0(3), 8.5(1), 8.6(1)
*CUCM-SME 7.1(3), 8.0, 8.5

'''Notes:'''
* CUCM 8.6 is supported in Cisco Unified MeetingPlace Release 8.5.2 and later.
* Ad-hoc (SCCP) meetings are supported in Cisco Unified MeetingPlace Release 8.5.2 and later. Ad-hoc meetings are not supported with CUCM 8.5.
* CUCM 8.0(3) is the only release that supports SIP Refers for multinode Cisco Unified MeetingPlace systems (WebEx-scheduling deployments). If you require this support, open a case with Cisco TAC against the Cisco Unified Communications Manager to obtain the latest Engineering Special (ES) or Service Update (SU) version of CUCM 8.0(3).

|-
|

Hardware Media Server (HMS)

|
If your deployment requires a HMS, see the [[Cisco Unified MeetingPlace Release 8.5 -- Hardware Requirements#Hardware Media Server Requirements|Hardware Media Server Requirements]].

'''Notes:'''
*During installation, you will have the option to choose either the Hardware Media Server or the Express Media Server. You do not require both.
* The Hardware Media Server should be on the same local network segment as the Application Server. Cisco Unified MeetingPlace does not support Hardware Media Server blades that are remotely located.

|-
|
Cisco Unified MeetingPlace PhoneView
|
Cisco Unified MeetingPlace PhoneView is available only to Cisco Unified IP Phones that are registered to Cisco Unified Communications Manager.

Cisco Unified MeetingPlace PhoneView is not supported with the following:
*Cisco Unified CallManager Express
*Cisco Unified Communications Manager Express
*Cisco Unified MeetingPlace Web Servers with SSL enabled
*Cisco Unified MeetingPlace Application Servers with SSL enabled

'''Hardware'''

For a list of supported Cisco Unified IP Phones, see [[Cisco Unified MeetingPlace Release 8.5 -- Compatibility Matrix#Audio Endpoint Compatibility|Audio Endpoint Compatibility]].

|-
|
Video option
|
See the [[Cisco Unified MeetingPlace Release 8.5 -- Hardware Requirements#Video Requirements|Video Requirements]].

|}

== License Requirements ==

This release of Cisco Unified MeetingPlace uses host-based licensing. The system uses an audit mechanism to track the number of users who have created meetings and compare that to the number of licenses that are installed. An alarm is raised when the number of users who create meetings exceeds the number of licenses installed.

If you have no licenses installed the system will allow only a single meeting at a time.

'''Note:''' If you are completing a Cisco UCS installation under VMware, note that the Cisco Unified MeetingPlace system produces a randomly generated 12-digit "MAC address" that you will require for licensing. To obtain the MAC address, make sure that you install the Meeting Directors first. You can then obtain the randomly generated MAC address and register your license key.

== Failover Requirements ==

To configure failover, you need two Application Servers with a high-speed network connection of 100Mpbs or better between them. Failover configuration requires the following:
* 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.
* The active and standby Application Servers can be on different timezones, but the time must be synchronized between them. This is required to resolve conflicts when the same piece of data is modified simultaneously in both Application Servers.
* To ensure that times are synchronized, we recommend that both Application Servers are synchronized to the same NTP server. If different NTP servers are used, make sure that these NTP servers are high-Stratum servers, that is, stratum-1 or stratum-2, to minimize the chance of an Application Server synchronizing to an inaccurate clock.

'''Note: ''' Directory Service between two Application Servers is not supported in a failover deployment.

==Network Requirements==

This section lists the incoming and outgoing ports that are used by the various components of the Cisco Unified MeetingPlace Release 8.5 system. The information refers to Audio-only deployments.

Use these tables to make sure that your firewalls do not block access to Cisco Unified MeetingPlace from users or integrated systems, and to make sure that you do not block communication among the Cisco Unified MeetingPlace components and servers.

The ports that you do ''not'' need to expose to system administrators or end users are used for local communication between the Cisco Unified MeetingPlace elements or between Cisco Unified MeetingPlace and local services such as Cisco Unified Communications Manager. Such ports should be blocked in the DMZ or external firewall, but should not be blocked between internal components of the Cisco Unified MeetingPlace solution.

'''Note:''' Signaling between Cisco Unified MeetingPlace and Cisco Unified Communications Manager must be TCP.

===DNS Recommendations===

*All FQDNs of meeting director nodes (if applicable), conferencing nodes, and Cisco WebEx nodes are required for DNS resolution between all servers.
*No multiple names to IP addresses.
*Reverse IP lookup is required.
*Classless DNS is not supported.
*CUCM must have DNS enabled to resolve the Cisco Unified MeetingPlace hostnames for the SIP refer commands to be successful.

=== Incoming Ports Used in Audio-Only Deployments===

{| border = 1
|-
!Protocol
!Source
!Destination
!Port Type
!Ports
!Port Usage
!Special Requirements
|-
|colspan="7" rowspan="1"|'''Application Server/Express Media Server'''

|-
|

SSH
|
Administrator PC
|
Application Server
|
TCP
|

22
|

Secure access
|

Expose to system administrators
|-
|

SNMP
|
Administrator PC
|
Application Server
|
UDP
|

161
|

SNMP configuration
|

Expose to system administrators; optional
|-
|

MP_REPL
|
Application Server 1
|
Application Server 2
|
TCP
|

2008
|

Database replication between the active and standby servers for Application Server failover
|
Optional; only if failover is configured

|-
|

SIP
|
Cisco Unified Communications Manager (CUCM)
|
Application Server
|
TCP UDP
|

5060
|

SIP B2BUA; UDP optional
|
--

|-
|

SIP over TLS
|
Cisco Unified Communications Manager (CUCM)
|
Application Server
|
TCP UDP
|

5061
|

SIP B2BUA; UDP optional
|
--

|-
|
HTTP
|
Cisco IP Phones PhoneView XML application

|
Application Server

|
TCP
|

8080
|

HTTP services used by Cisco Unified MeetingPlace PhoneView XML on IP Phones (optional)

|
--

|-
|

HTTP
|
Application Server
|
Hardware Media Server
|
TCP
|

9090
|

Media Server Administration
|

Expose to system administrators
|-
|

SIP
|
External Web Server

|
Application Server
|
TCP UDP
|

61002
|

Recording signaling
|
--
|-
|

Recording control
|
External Web Server
|
Application Server
|

TCP
|

61003
|

Recording control
|

For remote RSS servers only
|-
|
HTTP, HTTPS
|
Administrator PC
|

Application Server

|

TCP
|

80, 443
|

Administrator web access for both MeetingPlace Applications Admin and Cisco WebEx Site Admin

|

Expose to system administrators

|-
|

RTP/RTCP
|
Phones, video devices, gateway
|
Application Server/EMS, HMS
|
UDP
|

16384-32767
|

Recording media for both Hardware Media Server and Express Media Server
|

--
|-
|colspan="7" rowspan="1"|'''Hardware Media Server'''

|-
|

FTP
|
Application Server
|
HMS

|

TCP
|

21
|

Retrieving log files
|

Expose to system administrators
|-
|

Telnet
|

Application Server
|
HMS
|
TCP
|

23
|

Telnet
|

Expose to system administrators
|-
|

NTP
|
Application Server
|
HMS
|

UDP
|

123
|

Network Time Protocol
|

--
|-
|

SNMP
|
Application Server
|
HMS
|

UDP
|

161
|

SNMP configuration
|

Expose to system administrators
|-
|

MPI
|
Application Server
|
HMS
|

TCP
|

2010
|

MPI (Pompa control protocol)
|

--
|-
|

DCI
|
Application Server
|
HMS
|

TCP
|

3333
|

DCI (DCS control protocol)
|

--
|-
|

XML control
|
Application Server
|
HMS
|

TCP
|

3336
|

XML control
|

--
|-
|

XML cascading
|
Application Server
|
HMS
|

TCP
|

3337
|

XML cascading
|

--
|-
|

File server
|
Application Server
|
HMS
|

TCP
|

3340
|

File server
|

--
|-
|

SIP
|
Application Server
|
HMS
|

TCP UDP
|

5060
|

SIP
|

--
|-
|

RTP/RTCP
|
Phones
|
HMS
|

UDP
|

16384-16683
|

Audio Media
|

Expose to system administrators and end users
|-
|

RTP/RTCP
|
--
|
HMS
|

UDP
|

20000-21799
|

Video Media
|

Expose to system administrators and end users
|-
|

Video Blade control
|
HMS - Audio Blade
|
HMS - Video Blade
|

TCP
|

2944-2945
|

Video Blade control (H.248)
|

--
|-
|colspan="7" rowspan="1"|'''Web Server (optional component)'''

|-
|

HTTP
|
Administrator PC
|

Web Server

|

TCP
|

80
|

Client communication for user web access

|

Expose to system administrators and end users

|-
|

HTTPS
|
Administrator PC
|

Web Server

|

TCP
|

443
|

Client communication for secure user web access

|

(Optional) Expose to system administrators and end users.
|-
|

Control connection
|
Web Servers
|
Application Servers
|

TCP
|

5003
|

Control connection between Web Servers and the Application Server
|

Expose to Application Server

|-
|colspan="7" rowspan="1"|'''User PC/Phones/Gateways'''

|-
|

RTP/RTCP
|
Application Server
|
Cisco Unified Personal Communicator (CUPC), IP Phones, Gateways
|
UDP
|
16384-32526
|
Voice and video
|
--

|-
|colspan="7" rowspan="1"|'''Cisco Unified Communications Manager (CUCM) '''

|-
|

SIP
|
Application Server
|
CUCM
|
TCP UDP
|
5060
|
SIP
|
--
|-
|

SIP over TLS
|
Application Server
|
CUCM
|
TCP UDP
|
5061
|
SIP
|
--
|-
|

SCCP
|
Phones
|
CUCM
|
TCP
|
2000
|
--
|
--
|-
|
SIP
|
CUPC
|
CUCM
|
TCP UDP
|
5060
|
--
|
--
|-
|

SIP over TLS
|
CUPC
|
CUCM
|
TCP UDP
|
5061
|
--
|
--
|-
|

AXL
|
Application Server
|
CUCM
|
TCP
|
8443
|
AXL SOAP connection
|
--

|}

=== Outgoing Ports Used in Audio-Only Deployments ===

'''Note: ''' This section contains a partial list of outgoing ports only.

{| border = 1
|-
!Protocol
!Source
!Destination
!Port Type
!Port
!Usage
!Special Requirements
|-
|colspan="7" rowspan="1"|'''Application Server'''

|-
|

SMTP
|
Application Server
|
SMTP or Microsoft Exchange Server
|
TCP
|

25
|

Send information for email notification
|

--
|-
|

HTTP
|
Application Server
|
Microsoft Exchange Server
|
TCP
|

80
|

Send information for Microsoft Exchange integration
|

--
|-
|

HTTPS
|
Application Server
|
Microsoft Exchange Server
|

TCP
|

443
|

Send information to the Microsoft Exchange Server when SSL is enabled

|

--

|-
|colspan="7" rowspan="1"|'''Web Server'''
|-
|

NTP
|
Web Servers
|
Application Servers
|

UDP
|

123
|

Time synchronization
|

--
|-
|

Control connection
|
Web Servers
|
Application Server
|

TCP
|

5003
|

Control connection between Web Servers and the Application Server
|
--
|-
|
HTTP
|
--
|
--
|

TCP
|

61004
|

Recording control
|

--
|}

==Integration Requirements==

'''Note: ''' The Cisco Unified MeetingPlace integrations for IBM Lotus Notes and Microsoft Outlook are only supported if your deployment is configured for MeetingPlace-scheduling or audio-only. Deployments configured for WebEx-scheduling use WebEx Productivity Tools.

For more information about deployment options, see [[Cisco Unified MeetingPlace Release 8.5 -- Planning Your Deployment|Planning Your Deployment]].

* For information about the IBM Lotus Notes integration, see [[Cisco Unified MeetingPlace Release 8.5 -- System Requirements for MeetingPlace-Scheduling Deployments#IBM Lotus Notes Integration with Cisco Unified MeetingPlace Release 8.5|IBM Lotus Notes Integration with Cisco Unified MeetingPlace Release 8.5]].
* For information about the Microsoft Outlook integration, see [[Cisco Unified MeetingPlace Release 8.5 -- System Requirements for MeetingPlace-Scheduling Deployments#Microsoft Outlook Integration with Cisco Unified MeetingPlace Release 8.5|Microsoft Outlook Integration with Cisco Unified MeetingPlace Release 8.5]].

[[Category:Requirements for Cisco Unified MeetingPlace Release 8.5]]

Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration

2012-10-30T15:59:33Z

Cgriffen: /* Restrictions for Recording Cisco WebEx Web Meetings */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Integrations|Integrations]]

This module describes how to configure recordings when Cisco Unified MeetingPlace is integrated with Cisco WebEx.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Recording Information for Specific Cisco WebEx Integration Deployments|Recording Information for Specific Cisco WebEx Integration Deployments]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Restrictions for Recording Cisco WebEx Web Meetings|Restrictions for Recording Cisco WebEx Web Meetings]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#How to Configure Recording for Cisco WebEx Meetings|How to Configure Recording for Cisco WebEx Meetings]]

== Recording Information for Specific Cisco WebEx Integration Deployments ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Recording Information for Internal Meetings that are Scheduled from Cisco Unified MeetingPlace|Recording Information for Internal Meetings that are Scheduled from Cisco Unified MeetingPlace]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Recording Information for External Meetings that are Scheduled from Cisco Unified MeetingPlace|Recording Information for External Meetings that are Scheduled from Cisco Unified MeetingPlace]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Recording Information for External Meetings that are Scheduled from Cisco WebEx|Recording Information for External Meetings that are Scheduled from Cisco WebEx]]

=== Recording Information for Internal Meetings that are Scheduled from Cisco Unified MeetingPlace ===

{| border = 1
|-
!Topic
!Details
|-
|

Access
|
* Users access meeting recordings from the Cisco Unified MeetingPlace web user portal.
* User access privileges are determined by Cisco Unified MeetingPlace.* Users download the synchronized voice and web recording (.arf) files and use the Cisco WebEx player to play back the recordings.
|-
|

Storage
|
* Recording files are stored on the Cisco Unified MeetingPlace Web Server.
|-
|

Restrictions
|
* Avoid using the TUI to start and stop recordings for internal meetings. Specifically:
** (Recommended method) If a user starts recording from the Cisco WebEx web meeting room, then the audio, video, and web portions will be recorded. Subsequent stopping and starting from the web meeting room will affect all portions of the recording, as users would expect.** If a user starts recording from the TUI by pressing #61, then only the audio and video portions will be recorded. The web portion will ''not'' be recorded.
** If a user presses #61 after the recording was already started from the web meeting room, then the audio recording is stopped while the web recording continues. The resulting synchronized audio and web recording will be silent during the periods when the audio recording is stopped.
:: Note also that the Cisco WebEx web meeting room will ''not'' indicate that the audio recording has stopped or started due to a user pressing #61. Audio meeting participants will, however, hear voice prompts indicating that the recording has stopped or started.
* The Cisco WebEx player is supported only on Mac and Windows user systems.
* One .arf recording file is created for each instance of the user starting and stopping the recording of a meeting. Each meeting is limited to 30 .arf recording files.
|-
|

Internal Implementation
|
* Cisco Unified MeetingPlace records the audio and video portions of the meeting.
* The Cisco WebEx Node for MCS records the web portion directly onto the Application Server through a secure NFS (*1) mount which is tunneled over SSH (*2). This connection is called the Application Server Link.* The Cisco WebEx Appliance on the Application Server creates the synchronized audio and web recording (.arf) file, which is transferred to the Web Server.
|}

===== Footnotes =====

*1: NFS = Network File System

*2: SSH = Secure Shell

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Restrictions for Recording Cisco WebEx Web Meetings|Restrictions for Recording Cisco WebEx Web Meetings]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#How to Configure Recording for Cisco WebEx Meetings|How to Configure Recording for Cisco WebEx Meetings]]

=== Recording Information for External Meetings that are Scheduled from Cisco Unified MeetingPlace ===

{| border = 1
|-
!Topic
!Details
|-
|

Access
|
* Users access meeting recordings from the Cisco Unified MeetingPlace web user portal.
* User access privileges are determined by Cisco Unified MeetingPlace.* Users download the synchronized audio and web recording (.arf) files and use the Cisco WebEx player to play back the recordings.
|-
|

Storage
|
* Synchronized audio and web recording files are stored on the Cisco WebEx site.
* Audio and video recording files are stored on the Cisco Unified MeetingPlace Web Server.
|-
|

Restrictions
|
* If a user starts recording from the Cisco WebEx web meeting room:
** The audio and web portions will be recorded.** The video portion will ''not'' be recorded.
* If a user starts recording from the TUI:
** The audio and video portions will be recorded.
** The web portion will ''not'' be recorded.
** Users cannot pause or stop the audio and video recording of the external meeting from the Cisco WebEx web meeting room. They may do so only from the TUI.
* The Cisco WebEx player is supported only on Mac and Windows user systems.
|-
|

Internal Implementation
|
* For recordings started form the Cisco WebEx web meeting room:
** Cisco WebEx NBR (1) dials in to Cisco Unified MeetingPlace to record the audio portion of the meeting.** Cisco WebEx site merges the audio and web portions after the meeting ends.
* For recordings started from the TUI:
** Cisco Unified MeetingPlace records the audio and video portions as if the system was not integrated with Cisco WebEx.
|}

Footnote 1: NBR = Network-Based Recording

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Restrictions for Recording Cisco WebEx Web Meetings|Restrictions for Recording Cisco WebEx Web Meetings]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#How to Configure Recording for Cisco WebEx Meetings|How to Configure Recording for Cisco WebEx Meetings]]

=== Recording Information for External Meetings that are Scheduled from Cisco WebEx ===

No recording configuration is required for deployments in which users schedule meetings from Cisco WebEx.

{| border = 1
|-
!Topic
!Details
|-
|

Access
|
* Users access meeting recordings from the Cisco WebEx site.
* User access privileges are determined by Cisco WebEx.* Users choose from these playback options:
** Watch and listen to a streaming playback of the synchronized audio and web recording.
** Download the synchronized audio and web recording (.arf) files and use the Cisco WebEx player to play back the recordings.
|-
|

Storage
|
* Recording files are stored on the Cisco WebEx site.
|-
|

Restrictions
|
* The video portion of a meeting cannot be recorded.
* The Cisco WebEx player is supported only on Mac and Windows user systems.
|-
|

Internal Implementation
|
* Cisco WebEx NBR (1) dials in to Cisco Unified MeetingPlace to record the audio portion of the meeting.
* Cisco WebEx site merges the audio and web portions after the meeting ends.
|}

Footnote 1: NBR = Network-Based Recording

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Restrictions for Recording Cisco WebEx Web Meetings|Restrictions for Recording Cisco WebEx Web Meetings]]
* [[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

== Restrictions for Recording Cisco WebEx Web Meetings ==

'''Note: ''' For deployment-specific restrictions, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Recording Information for Specific Cisco WebEx Integration Deployments|Recording Information for Specific Cisco WebEx Integration Deployments]].
* Meeting recordings are not supported for internal meetings that are scheduled from Cisco WebEx.
* Continuous meetings cannot be recorded.
* Your meetings must be unlocked for your network-based recorder to record the meeting.
* If the user starts a recording from the telephone user interface (TUI), then the web portion of the meeting will not be recorded until the user also starts recording from the web meeting room.
: The synchronized audio and web recording will ''not'' include the portion of the meeting that occurred before the recording was started from the web meeting.
: (For Cisco Unified MeetingPlace scheduling only) The complete audio and video recordings will be available from the Cisco Unified MeetingPlace web user portal.
* Web recording files cannot exceed 2 GB due to a Linux limitation. If this limit is reached, then the meeting host will not be able to record any more meetings until the problematic recording file is removed.
** For meetings scheduled from Cisco Unified MeetingPlace, you can remove the recording file from the Recordings page in the web user portal.
** For meetings scheduled from Cisco WebEx, the meeting host can delete the recording file from the Cisco WebEx site.
: As an extreme example, if the web meeting includes a Flash movie, then the web recording may reach 2 GB in approximately 1.5 hours.
: Similarly, for internal meetings scheduled from Cisco Unified MeetingPlace, if the recording files exceed the limit for the Application Server, then no users will be able to record meetings until space becomes available.

===== Related Topics =====
* [[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 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration|Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration]] module

== How to Configure Recording for Cisco WebEx Meetings ==

No recording configuration is required for deployments in which users schedule meetings from Cisco WebEx. Complete the following tasks to configure recording for deployments in which users schedule meetings from Cisco Unified MeetingPlace:
# [[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 -- Configuring Audio and Video Recordings for Cisco Unified MeetingPlace#Configuring Audio and Video Recordings for Cisco Unified MeetingPlace|Configuring Audio and Video Recordings for Cisco Unified MeetingPlace]] module
# [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Cisco Unified MeetingPlace Web Server for Optimal Data Storage#Configuring the Cisco Unified MeetingPlace Web Server for Optimal Data Storage|Configuring the Cisco Unified MeetingPlace Web Server for Optimal Data Storage]] module
# [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Conversion of Recording Files#Configuring the Conversion of Recording Files|Configuring the Conversion of Recording Files]] module
# [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Configuring Who Can Start and Stop Recording from the Cisco WebEx Web Meeting Room|Configuring Who Can Start and Stop Recording from the Cisco WebEx Web Meeting Room]]

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Recording Information for Specific Cisco WebEx Integration Deployments|Recording Information for Specific Cisco WebEx Integration Deployments]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#Restrictions for Recording Cisco WebEx Web Meetings|Restrictions for Recording Cisco WebEx Web Meetings]]

=== Configuring Who Can Start and Stop Recording from the Cisco WebEx Web Meeting Room ===

'''Notes: '''
* This topic applies only to deployments in which users schedule meetings from Cisco Unified MeetingPlace.
* Your Cisco WebEx administrator may have already completed part or all of this task for you.

If you or your Cisco WebEx administrator complete this task, then the Cisco WebEx web meeting room will enforce the recording privileges that are configured in Cisco Unified MeetingPlace user profiles. Only meeting ''hosts'' with recording privileges can start and stop recording from the Cisco WebEx web meeting room.

If you or your Cisco WebEx administrator do ''not'' complete this task:
* ''All'' meeting hosts will be able to start and stop recording from the Cisco WebEx web meeting room.
* The Cisco Unified MeetingPlace recording privileges only affect whether users can start and stop recording from the telephone user interface (TUI).

Users who join the audio meeting via a dial-out call are always treated as guests on the phone, even if they were authenticated over the web. Therefore, the TUI recording privileges of these users are determined by the ''guest'' profile in Cisco Unified MeetingPlace.

If, however, the user is a meeting host or alternate host who is authenticated over the web, then the recording privileges in the user profile are enforced for the recording menu in web meeting room.

===== Before You Begin =====
* Complete the procedure in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Audio and Video Recordings for Cisco Unified MeetingPlace#Enabling Users to Record Meetings|Enabling Users to Record Meetings]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Audio and Video Recordings for Cisco Unified MeetingPlace#Configuring Audio and Video Recordings for Cisco Unified MeetingPlace|Configuring Audio and Video Recordings for Cisco Unified MeetingPlace]] module.
* Have your Cisco WebEx administrator configure your site to allow custom session types.

===== Procedure =====

# Go to the Cisco WebEx Site Administration:
## Select '''System Configuration > Cisco WebEx Configuration > Cisco WebEx Certificate'''.
## Select the Cisco WebEx Site Administration URL link.
## Sign in if prompted:
##* Enter the User ID of your Cisco Unified MeetingPlace system administrator user profile.
##* Enter the Cisco WebEx site administration password that was provided by your Cisco WebEx administrator.
# Verify that no session types other than '''Meeting Center MP Single''' and '''Meeting Center E2E''' are available on your Cisco WebEx site:
## Select '''Home'''.
## Find the '''Session Types''' column.
## If you see any session types that are ''not'' '''Meeting Center MP Single''' or '''Meeting Center E2E''', then tell your Cisco WebEx administrator to disable them.
#: Until the other session types are disabled on the Cisco WebEx site, the web meeting room may not enforce the recording privileges that are configured in Cisco Unified MeetingPlace user profiles.
# Select '''Session Type List'''.
# If you see a "non-recording" entry in the Session Name column:
## Check the '''Active''' check box for that entry.
## Select the entry in the Session Code column.
## Proceed to Step 6.
# If there is no existing "non-recording" entry in the Session Name column:
## Select '''Add Custom Type'''.
## Enter '''non-recording''' as the Session name.
# Uncheck these features:
#* '''Recording client-side'''
#* '''Recording network-based'''
# (Optional) Set the web meeting room features to appear as your users would expect or want them to appear.
#: For example, if your users are accustomed to seeing the '''Chat''' and '''Participant''' list features in the web meeting room, then do the following for each of those features:
## Check the check box for the feature.
## Select '''Open''' under Default Behavior.
# Select '''Add''' or '''Update'''.
# Enable the new custom session type for your users:
## Select '''Edit Privileges'''.
## Find '''non-recording''' in the "Change meeting privileges for all users" area.
## Select '''Enable all''' for non-recording.
## Select '''Submit'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Recordings for Cisco Unified MeetingPlace-Cisco WebEx Integration#How to Configure Recording for Cisco WebEx Meetings|How to Configure Recording for Cisco WebEx Meetings]]
* [[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 -- Troubleshooting Cisco Unified MeetingPlace Integration with Cisco WebEx#Chat, Participant List, or Other Features Do Not Appear in the Cisco WebEx Web Meeting Room|Chat, Participant List, or Other Features Do Not Appear in the Cisco WebEx Web Meeting Room]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Cisco Unified MeetingPlace Integration with Cisco WebEx#Troubleshooting Cisco Unified MeetingPlace Integration with Cisco WebEx|Troubleshooting Cisco Unified MeetingPlace Integration with Cisco WebEx]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Profiles and User Groups for Cisco Unified MeetingPlace#Configuring User Profiles and User Groups for Cisco Unified MeetingPlace|Configuring User Profiles and User Groups for Cisco Unified MeetingPlace]] module

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace Release 8.0 -- About Microsoft System Updates or Patches and the Cisco MCS

2012-06-18T19:33:56Z

Cgriffen: /* About Microsoft System Updates or Patches and the Cisco MCS */

== About Microsoft System Updates or Patches and the Cisco MCS ==

Cisco will provide an installer with Microsoft operating system updates on cisco.com, with instructions to download and deploy these updates.

Software downloads for the Web Server Windows 2003 operating system is located in the Cisco Unified MeetingPlace Security Updates folder at the following URL:

http://www.cisco.com/cisco/software/type.html?mdfid=282879185&flowid=5383

Frequency of updates: Two weeks after Microsoft Patch Tuesday (Microsoft Patch Tuesday is the second Tuesday of each month).

Sign up to receive a notification whenever new versions are posted to the software download site. Use the Cisco Notification Service to create customized, flexible notification alerts to be sent to you using email or by RSS feed, on critical product support subjects: Security Advisories, Field Notices, End of Sale/Support statements, Software Updates, and Known Bugs:

http://www.cisco.com/cisco/support/notifications.html

Cisco Unified MeetingPlace Release 8.0 -- About Microsoft System Updates or Patches and the Cisco MCS

2012-06-18T19:31:33Z

Cgriffen: Created page with "== About Microsoft System Updates or Patches and the Cisco MCS == Cisco will provide an installer with Microsoft operating system updates on cisco.com, with instructions to down..."

== About Microsoft System Updates or Patches and the Cisco MCS ==

Cisco will provide an installer with Microsoft operating system updates on cisco.com, with instructions to download and deploy these updates.

Software downloads for the Web Server Windows 2003 operating system is located in the Cisco Unified MeetingPlace Security Updates folder at the following URL:

http://www.cisco.com/cisco/software/type.html?mdfid=282340975&flowid=5382

Frequency of updates: Two weeks after Microsoft Patch Tuesday (Microsoft Patch Tuesday is the second Tuesday of each month).

Sign up to receive a notification whenever new versions are posted to the software download site. Use the Cisco Notification Service to create customized, flexible notification alerts to be sent to you using email or by RSS feed, on critical product support subjects: Security Advisories, Field Notices, End of Sale/Support statements, Software Updates, and Known Bugs:

http://www.cisco.com/cisco/support/notifications.html

Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting

2012-06-18T19:31:06Z

Cgriffen:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Print PDF: '''[[Cisco Unified MeetingPlace Release 8.0 -- Print Troubleshooting]]

*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Problems When Scheduling Meetings|Troubleshooting Problems When Scheduling Meetings]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Password Recovery for the Cisco Unified MeetingPlace Application Server|Password Recovery for the Cisco Unified MeetingPlace Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting User Access Issues for Cisco Unified MeetingPlace|Troubleshooting User Access Issues for Cisco Unified MeetingPlace]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Phone Issues for Cisco Unified MeetingPlace|Troubleshooting Phone Issues for Cisco Unified MeetingPlace]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Video Issues for Cisco Unified MeetingPlace|Troubleshooting Video Issues for Cisco Unified MeetingPlace]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Email Notifications for Cisco Unified MeetingPlace|Troubleshooting Email Notifications for Cisco Unified MeetingPlace]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting the Cisco Unified MeetingPlace Web Server|Troubleshooting the Cisco Unified MeetingPlace Web Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting SSL for the Cisco Unified MeetingPlace Application Server|Troubleshooting SSL for the Cisco Unified MeetingPlace Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Cisco Unified MeetingPlace Integration with Cisco WebEx |Troubleshooting Cisco Unified MeetingPlace Integration with Cisco WebEx]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Cisco Unified MeetingPlace Scheduling from Microsoft Outlook|Troubleshooting Cisco Unified MeetingPlace Scheduling from Microsoft Outlook]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal|Troubleshooting Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Time and Time Zone Issues for Cisco Unified MeetingPlace|Troubleshooting Time and Time Zone Issues for Cisco Unified MeetingPlace]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Problems with the Hardware Media Server|Troubleshooting Problems with the Hardware Media Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- About Microsoft System Updates or Patches and the Cisco MCS|About Microsoft System Updates or Patches and the Cisco MCS]]

[[Category: Troubleshooting Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Licenses for your Cisco Unified MeetingPlace System

2012-04-20T18:51:21Z

Cgriffen:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 8.0 -- Planning Your Deployment|Planning Your Deployment]]

Licenses enable specific features and capabilities on the system. You purchase license SKUs with your Cisco Unified MeetingPlace order and install the license file for that order to enable the features and capabilities that you purchased. You may also upgrade your system by purchasing and installing additional licenses. The maximum number of port licenses that you can apply is 2,000 per license.

Use the information in this section to determine if you need to purchase and install additional licenses.

[[Cisco Unified MeetingPlace Release 8.0 -- Licenses for your Cisco Unified MeetingPlace System#Table: Licenses for Cisco Unified MeetingPlace Release 8.0|Table: Licenses for Cisco Unified MeetingPlace Release 8.0]] describes the available licenses for Cisco Unified MeetingPlace Release 8.0.

===== Table: Licenses for Cisco Unified MeetingPlace Release 8.0 =====

{| border = 1
|-
!License
!Description
!Type
|-
!<td colspan="3" rowspan="1">|Conferencing Licenses
|-
|

videoconf
|

The videoconf license limits the number of concurrent video participants in meetings. The available number of video ports may be further limited by the [[Cisco Unified MeetingPlace Release 8.0 -- Licenses for your Cisco Unified MeetingPlace System#maxvideo|maxvideo]] license.

If you do ''not'' install the videoconf license, the system can use only the six trial video ports for meetings. (A port is defined as a single video caller connecting at any rate.)
|

counted
|-
|

voiceconf
|

The voiceconf license limits the number of concurrent voice participants in meetings, including:
* Calls to and from the system
* Voice participants in meetings

The available number of voice ports may be further limited by the [[Cisco Unified MeetingPlace Release 8.0 -- Licenses for your Cisco Unified MeetingPlace System#maxvoice|maxvoice]] license.

If you do ''not'' install the voiceconf license, the system can use only the six trial voice ports for premium (scheduled) meetings.
|

counted
|-
!<td colspan="3" rowspan="1">|Maximum Licenses
|-
|

maxvideo
|

The maxvideo license denotes the maximum number of video licenses that can be used for meetings on this particular system. If the [[Cisco Unified MeetingPlace Release 8.0 -- Licenses for your Cisco Unified MeetingPlace System#videoconf|videoconf]] license count exceeds the value of the maxvideo license, the system uses the value of the maxvideo license instead.

The system displays any maxvideo license limitations in the Comment field on the Licenses Summary page.

Restriction: If you purchase and install a new maxvideo license, it overwrites the old one. The new port count is not added to the previous port count.
|

counted
|-
|

maxvoice
|

The maxvoice license denotes the maximum number of voice licenses that can be used for meetings on this particular system. If the [[Cisco Unified MeetingPlace Release 8.0 -- Licenses for your Cisco Unified MeetingPlace System#voiceconf|voiceconf]] license count exceeds the value of the maxvoice license, the system uses the value of the maxvoice license instead.

The system displays any maxvoice license limitations in the Comment field on the Licenses Summary page.

Restriction: If you purchase and install a new maxvoice license, it overwrites the old one. The new port count is not added to the previous port count.
|

counted
|-
!<td colspan="3" rowspan="1">|Additional Feature Licenses
|-
|

languages
|

The languages license enables the simultaneous use of up to four supported languages on a system. If you do ''not'' install the languages license, you can enable only one language.
|

yes/no
|-
|

videorecording
|

The videorecording license allows you to video record meetings. When turned on, it allows the system to video record up to 100 meetings at a time.

If you do ''not'' install the videorecording license, you cannot video record meetings.
|

yes/no
|-
!<td colspan="3" rowspan="1">|Integration Licenses
|-
|

jabber
|

The jabber license enables you to integrate your Cisco Unified MeetingPlace system with Jabber.

If you do ''not'' install the jabber license, you cannot integrate Cisco Unified MeetingPlace with Jabber.
|

yes/no
|-
|

lotusnotes
|

The lotusnotes license enables you to integrate your Cisco Unified MeetingPlace system with IBM Lotus Notes.

If you do ''not'' install the lotusnotes license, you cannot integrate Cisco Unified MeetingPlace with IBM Lotus Notes.
|

yes/no
|-
|

msft_int
|

The msft_int license enables you to integrate your Cisco Unified MeetingPlace system with Microsoft Outlook.

If you do ''not'' install the msft_int license, you cannot integrate Cisco Unified MeetingPlace with Microsoft Outlook.
|

yes/no
|}

===== Related Topics =====

For information about how to install the licenses, see the online help in the administrator interface or the ''Configuration Guide for Cisco Unified MeetingPlace Release 8.0'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

[[Category: Planning for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace

2012-04-20T18:49:20Z

Cgriffen: /* Restrictions for Licenses */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

Licenses enable specific features and capabilities on the system. You purchase license SKUs with your Cisco Unified MeetingPlace order and install the license file for that order to enable the features and capabilities that you purchased. You can also upgrade your system by purchasing and installing additional licenses.
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Restrictions for Licenses|Restrictions for Licenses]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#How to Install and Manage Licenses|How to Install and Manage Licenses]]

== Restrictions for Licenses ==
* By default, every Cisco Unified MeetingPlace system comes with six trial voice licenses and six trial video licenses.
* You cannot install more video licenses than voice licenses.
* Depending on your system configuration, you might not be able to take advantage of all the licenses you purchase. The Cisco Unified MeetingPlace system lets you purchase more licenses than your current system capacity.
* The maximum number of port licenses that you can apply is 2,000 per license.

===== Related Topics =====
* [[Cisco Unified MeetingPlace, Release 8.0 -- Planning Your Deployment]]

== How to Install and Manage Licenses ==

If you purchase license SKUs with your Cisco Unified MeetingPlace order, your order comes with a Product Authorization Key (PAK). You obtain a license file by providing the PAK and the MAC address of your server in a form on Cisco.com. Through the Administration Center, you upload the license file to Cisco Unified MeetingPlace to install all purchased licenses in that order.

'''Note: ''' The new licenses take effect immediately on the Cisco Unified MeetingPlace Application Server. You do ''not'' need to reinstall or restart the Cisco Unified MeetingPlace operating system and application when you add licenses. However, if you added the license file after starting the Cisco Unified MeetingPlace Web Server, you must restart the Cisco Unified MeetingPlace Web Master Service or reboot the Web Server. License options are loaded only during Web Server startup. See the [[Cisco Unified MeetingPlace Release 8.0 -- Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service#Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service|Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service]] module.
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Determining the MAC Address of your System|Determining the MAC Address of your System]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Obtaining the License File|Obtaining the License File]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing the License File|Installing the License File]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Displaying Licenses|Displaying Licenses]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Downloading Licenses|Downloading Licenses]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Verifying that the Cisco Unified MeetingPlace License Manager is Running|Verifying that the Cisco Unified MeetingPlace License Manager is Running]]

=== Determining the MAC Address of your System ===

===== Procedure =====

# Sign in to the Administration Center.
# Select '''Maintenance''' > '''Licenses''' > '''Install Licenses'''.
#: The MAC address is listed in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (I - L pages)#Install Licenses Page|Host ID (MAC address)]] field.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (I - L pages)#Install Licenses Page|Install Licenses Page]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (I - L pages)|Administration Center Page References for Cisco Unified MeetingPlace (I - L pages)]]

=== Obtaining the License File ===

The license file contains all the purchased licenses in your order.

===== Before You Begin =====
* Find the Product Authorization Key (PAK) that came with your order.
* Complete the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Determining the MAC Address of your System|Determining the MAC Address of your System]].

===== Procedure =====

# Go to http://www.cisco.com/go/license.
# If prompted, sign in with your Cisco.com username and password.
# Enter the PAK from your Cisco Unified MeetingPlace order.
# Confirm the order information and select '''Continue'''.
# Fill out all the required fields on the registration form. In particular:
#* Make sure that your email address is correct because the license file will be emailed to you.
#* Enter the MAC address of your Cisco Unified MeetingPlace server.
# Select '''Submit'''.
#: Cisco Systems sends you an email containing the license file.
# Save the license file to a location where you can access it from the Administration Center.

===== Related Topics =====
* [[Cisco Unified MeetingPlace, Release 8.0 -- Planning Your Deployment]]

=== Installing the License File ===

===== Before You Begin =====
* Complete the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Obtaining the License File|Obtaining the License File]].
* In an [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|Application Server Failover]] deployment, make sure that the node is ''active''.

===== Procedure =====

# Sign in to the Administration Center.
# Select '''Maintenance > Licenses''' > '''Install Licenses'''.
# Select one of these radio buttons:
#* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Upload new license file|Upload new license file]]-Choose this option to delete all previously installed licenses before installing the license file. Select this option only when uploading licenses to your system for the first time, or in the unlikely event that you must install an entirely new set of licenses.
#* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Append incremental license file|Append incremental license file]]-Choose this option to keep all the previously installed licenses and to add additional licenses from the license file.
# Enter the fully-qualified filename in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#License file to use|License file to use]] field or select '''Browse''' to search for the file.
# Select '''Install License'''.

===== Troubleshooting Tips =====

If the Application Server hostname is longer than 32 characters, you might not be able to install licenses. If this occurs, use the '''net''' command to change the hostname. Note, however, that changing the Application Server hostname requires a system restart and might require other configuration tasks. See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#net|net]] 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 you added the license file after starting the Cisco Unified MeetingPlace Web Server, you must restart the Web Server. License options are loaded only during Web Server startup. Failure to restart the server might result in the Microsoft Outlook plug-in download link from appearing on the Cisco Unified MeetingPlace user web interface.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Install Licenses Page|Install Licenses Page]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Administration Center Page References for Cisco Unified MeetingPlace|Administration Center Page References for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace, Release 8.0 -- Planning Your Deployment]]

===== What to Do Next =====

Proceed to the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Displaying Licenses|Displaying Licenses]] to verify license installation.

=== Displaying Licenses ===

Complete this task to display the number and types of licenses that are installed on your system, which licenses are enabled, and any further license limitations that are specific to your system.

===== Procedure =====

# Sign in to the Administration Center.
# Select '''Maintenance > Licenses''' > '''Licenses Summary'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace, Release 8.0 -- Planning Your Deployment]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (I - L pages)#Licenses Summary Page|Licenses Summary Page]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (I - L pages)|Administration Center Page References for Cisco Unified MeetingPlace (I - L pages)]]

=== Downloading Licenses ===

Use this task to back up your license files.

===== Procedure =====

# Sign in to the Administration Center.
# Select '''Maintenance > Licenses''' > '''Licenses Summary''' or '''Install Licenses'''.
# Select '''Download License'''.
# In the File Download dialog box, select '''Save'''.
# Navigate to the directory where you want to save the exported file.
# Select '''Save'''.
# If the Download Complete dialog box appears, select '''Close'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Displaying Licenses|Displaying Licenses]]
* [[Cisco Unified MeetingPlace, Release 8.0 -- Planning Your Deployment]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (I - L pages)#Install Licenses Page|Install Licenses Page]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (I - L pages)|Administration Center Page References for Cisco Unified MeetingPlace (I - L pages)]]

=== Verifying that the Cisco Unified MeetingPlace License Manager is Running ===

===== Before You Begin =====

In an [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|Application Server Failover]] deployment, the License Manager is always stopped on the ''standby'' server. If you need the License Manager to be running, for example, to configure the Microsoft Exchange Server, then first make sure that the Application Server is ''active''.

===== Procedure =====

# Sign in to the Application Server CLI as the ''root'' user.
# Enter '''mpx_sys status'''.
# Verify that the output indicates that the License Manager is ''running''.
# If the output indicates that the License Manager is ''stopped'':
## Enter '''mpx_sys restart'''.
## Repeat [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Step 1|Step 1]] through [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Step 3|Step 3]].

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal#Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal|Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal#Troubleshooting Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal|Troubleshooting Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal]] module

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace, Release 7.0 -- About Licenses

2012-04-20T18:47:50Z

Cgriffen: /* Limitations for Cisco Unified MeetingPlace Licenses */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Planning Your Deployment|Planning Your Deployment]]

Licenses enable specific features and capabilities on the system. You purchase license SKUs with your Cisco Unified MeetingPlace order and install the license file for that order to enable the features and capabilities that you purchased. You may also upgrade your system by purchasing and installing additional licenses.

Use the information in this section to determine if you need to purchase and install additional licenses.

'''Note: ''' Meetings that use Cisco WebEx do not use Cisco Unified MeetingPlace web licenses.

== Limitations for Cisco Unified MeetingPlace Licenses ==

* You cannot install more video licenses than voice licenses.

* You can install more licenses than your hardware can support; that is, you can manually override the system capacity. This is for your convenience when upgrading your system, so that you can upgrade the number of licenses before you physically upgrade your hardware. However, every time you restart the system with this configuration, the system will generate an alarm.
: To avoid generating an alarm, change the values for the Override System Capacity parameters on the Meeting Configuration page in the Administration Center so that the licensed capacity matches the physical capacity. The system will use the values you enter when calculating the capacity for scheduling. Correctly configuring these values will also prevent inadvertent meeting extension failures caused by mismatches between licensed and actual resource values.

* Node must be active to add licenses.

* The maximum number of port licenses that you can apply is 2,000 per license.

== License Expiration ==

* By default, every Cisco Unified MeetingPlace system comes with six trial voice licenses, six trial web licenses, and six trial video licenses. If you do not purchase additional licenses, the six trial web licenses expire after 60 days.

* All licenses used for customer demonstration purposes expire.

* The system does not consider the expiration date of a license when users ''schedule'' meetings; instead, the system checks and enforces the expiration date when users ''join'' meetings.

== License Descriptions ==

[[Cisco Unified MeetingPlace, Release 7.0 -- About Licenses#Table: Licenses for Cisco Unified MeetingPlace Release 7.0|Table: Licenses for Cisco Unified MeetingPlace Release 7.0]] describes the available licenses for Cisco Unified MeetingPlace Release 7.0.

===== Table: Licenses for Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!License
!Description
!Type
|-
|<td colspan="3" rowspan="1">|''' Conferencing Licenses'''
|-
|

videoconf
|

The videoconf license limits the number of concurrent video participants in meetings. The available number of video ports may be further limited by the [[Cisco Unified MeetingPlace, Release 7.0 -- About Licenses#maxvideo|maxvideo]] license.

If you do ''not'' install the videoconf license, the system can use only the six trial video ports for meetings. (A port is defined as a single video caller connecting at any rate.)
|

counted
|-
|

voiceconf
|

The voiceconf license limits the number of concurrent voice participants in meetings, including:
* Calls to and from the system
* Voice participants in meetings

The available number of voice ports may be further limited by the [[Cisco Unified MeetingPlace, Release 7.0 -- About Licenses#maxvoice|maxvoice]] license.

If you do ''not'' install the voiceconf license, the system can use only the six trial voice ports for premium (scheduled) meetings.
|

counted
|-
|

webconf
|

The webconf license limits the number of concurrent participants using the full web meeting room. This number may be further limited by the [[Cisco Unified MeetingPlace, Release 7.0 -- About Licenses#maxweb|maxweb]] license.

'''Note: ''' If you want all or most users to be able to schedule full web meetings, install an equal number of voice ports and web ports through the [[Cisco Unified MeetingPlace, Release 7.0 -- About Licenses#voiceconf|voiceconf]] and webconf licenses.

If you do ''not'' install the webconf license, the system can use only the six trial web ports, which expire 60 days after system installation. If you purchase a base software SKU, your order comes with a trial webconf license that makes the six trial web ports permanent after you install the license.
|

counted
|-
|<td colspan="3" rowspan="1">|''' Maximum Licenses'''
|-
|

maxvideo
|

The maxvideo license denotes the maximum number of video licenses that can be used for meetings on this particular system. If the [[Cisco Unified MeetingPlace, Release 7.0 -- About Licenses#videoconf|videoconf]] license count exceeds the value of the maxvideo license, the system uses the value of the maxvideo license instead.

The system displays any maxvideo license limitations in the Comment field on the Licenses Summary page.

Restriction: If you purchase and install a new maxvideo license, it overwrites the old one. The new port count is not added to the previous port count.
|

counted
|-
|

maxvoice
|

The maxvoice license denotes the maximum number of voice licenses that can be used for meetings on this particular system. If the [[Cisco Unified MeetingPlace, Release 7.0 -- About Licenses#voiceconf|voiceconf]] license count exceeds the value of the maxvoice license, the system uses the value of the maxvoice license instead.

The system displays any maxvoice license limitations in the Comment field on the Licenses Summary page.

Restriction: If you purchase and install a new maxvoice license, it overwrites the old one. The new port count is not added to the previous port count.
|

counted
|-
|

maxweb
|

The maxweb license denotes the maximum number of web ports that can be used for meetings on this particular system. If the [[Cisco Unified MeetingPlace, Release 7.0 -- About Licenses#webconf|webconf]] license count exceeds the value of the maxweb license, the system uses the value of the maxweb license instead.

The system displays any maxweb license limitations in the Comment field on the Licenses Summary page.

Restriction: If you purchase and install a new maxweb license, it overwrites the old one. The new port count is not added to the previous port count.
|

counted
|-
|<td colspan="3" rowspan="1">|''' Additional Feature Licenses'''
|-
|

languages
|

The languages license enables the simultaneous use of up to four supported languages on a system. If you do ''not'' install the languages license, you can enable only one language.
|

on/off
|-
|

videorecording
|

The videorecording license allows you to video record meetings. When turned on, it allows the system to video record up to 100 meetings at a time.

If you do ''not'' install the videorecording license, you cannot video record meetings.
|

on/off
|-
|<td colspan="3" rowspan="1">|''' Integration Licenses'''
|-
|

jabber
|

The jabber license enables you to integrate your Cisco Unified MeetingPlace system with Jabber.

If you do ''not'' install the jabber license, you cannot integrate Cisco Unified MeetingPlace with Jabber.
|

on/off
|-
|

lotusnotes
|

The lotusnotes license enables you to integrate your Cisco Unified MeetingPlace system with IBM Lotus Notes.

If you do ''not'' install the lotusnotes license, you cannot integrate Cisco Unified MeetingPlace with IBM Lotus Notes.
|

on/off
|-
|

msft_int
|

The msft_int license enables you to integrate your Cisco Unified MeetingPlace system with Microsoft Outlook and Microsoft Office Communicator.

If you do ''not'' install the msft_int license, you cannot integrate Cisco Unified MeetingPlace with Microsoft Outlook and Microsoft Office Communicator.
|

on/off
|}

[[Category: Planning Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Licenses

2012-04-20T18:10:21Z

Cgriffen:

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Maintenance Page|Maintenance Page]]

* By default, every Cisco Unified MeetingPlace system comes with six trial voice licenses, six trial web licenses, and six trial video licenses. If you do not purchase additional licenses, the six trial web licenses expire after 60 days.

* Depending on your system configuration, you may not be able to take advantage of all the licenses you purchase. The Cisco Unified MeetingPlace system lets you purchase more licenses than your current system capacity. The maximum number of port licenses that you can apply is 2,000 per license.

* The system does not consider the expiration date of a license when users ''schedule'' meetings; instead, the system checks and enforces the expiration date when users ''join'' meetings. The system displays a message if a license is about to expire.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Planning the Capacity of your Cisco Unified MeetingPlace System|Planning the Capacity of your Cisco Unified MeetingPlace System]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key

2012-02-15T23:38:23Z

Cgriffen: /* Copying and Saving the Private Key for Future Use */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.

== Exporting the Private Key ==

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

==== Procedure ====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

== Copying and Saving the Private Key for Future Use ==

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Open a DOS prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
# Enter the path to your desktop in the cmd.exe window.
#:<tt> Example: C:\> cd "Documents and Settings\Administrator\Desktop" </tt>
# Enter the full path to OpenSSL.exe keeping the following in mind:
#* After -in, enter the full path to where you placed the file when you exported the private key.
#* After -out, enter the full path to where you want to send the exported file.
#*:<tt> Example:C:\Documents and Settings\Administrator\Desktop>"\Program Files\Cisco Systems\MPWeb\DataSvc\openssl.exe" pkcs12 -in "\Documents and Settings\Administrator\Desktop\mycertificate.pfx" -out "\Documents and Settings\Administrator\Desktop\mycertificate.pem" -nodes </tt>
#: This converts the PFX format to a PEM format. The mycertificate.pem file will have all the certificates starting with the Private key.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

=== Backing Up the Breeze Certificate ===

===== Procedure =====

# Open a DOS prompt.
# Enter the following command: '''Copy c:\Program Files\Cisco Systems\MPWeb\WebConf\comserv\win32\conf\_defaultRoot_\cert.pem file to''' ''backup path''.

=== About Restoring Breeze and Home Page Certificates ===

See the [[Cisco_Unified_MeetingPlace,_Release_7.0_--_How_to_Configure_Secure_Sockets_Layer#Applying_the_SSL_Certificate|Applying the SSL Certificate]] section for more information on restoring Breeze and home page certificates.

== Importing the Private Key in to the MPWEB Database ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].
* Back up the complete database before performing this procedure.

===== Procedure =====

# Open the SQL Query Analyzer.
# Select '''Start > All Programs > Microsoft SQL Server > Query Analyzer'''.
# Log in with your SQL username, ”sa,” and password (which you set during the installation of MPWeb).
# Type in the following commands:
#:* '''use mpweb'''
#:* '''update web'''
#:* '''set sslprivatekey='Your private key' '''
# Your private key begins with “BEGIN RSA PRIVATE KEY” and ends with “END RSA PRIVATE KEY”. Copy your private key and paste it between the quotes. You can find your Private key in your PEM file that you saved when you copied and saved the private key for future use.
#: '''Note''': Make sure you include the quotation marks.
# Select the green arrow to Execute Query.
# Determine if your Private Key insertion was successful by entering the following commands in the Query Analyzer window:
#:* '''use mpweb'''
#:* '''select sslprivatekey from web'''
# Select the green arrow to Execute Query and your private key appears the following window.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]]

=== About Home Page and Web Conf SSL certificates ===

When you import the private key using SQL query Analyzer enable SSL by performing the procedure described in the [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]] section.

===== Procedure =====

# Change the web server hostname from an IP Address to a hostname.
# Apply the SSL certificate.
# Enable SSL.

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key

2012-02-15T23:37:57Z

Cgriffen: /* About Restoring Breeze and Home Page Certificates */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.

== Exporting the Private Key ==

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

==== Procedure ====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

== Copying and Saving the Private Key for Future Use ==

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Open a DOS prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
# Enter the path to your desktop in the cmd.exe window.
#:<tt> Example: C:\> cd "Documents and Settings\Administrator\Desktop" </tt>
# Enter the full path to OpenSSL.exe keeping the following in mind:
#* After -in, enter the full path to where you placed the file when you exported the private key.
#* After -out, enter the full path to where you want to send the exported file.
#*:<tt> Example:C:\Documents and Settings\Administrator\Desktop>"\Program Files\Cisco Systems\MPWeb\DataSvc\openssl.exe" pkcs12 -in "\Documents and Settings\Administrator\Desktop\mycertificate.pfx" -out "\Documents and Settings\Administrator\Desktop\mycertificate.pem" -nodes </tt>
#: This converts the PFX format to a PEM format. The mycertificate.pem file will have all the certificates starting with the Private key.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

=== Backing Up the Breeze Certificate ===

===== Procedure =====

# Open a DOS prompt.
# Enter the following command: '''Copy c:\Program Files\Cisco Systems\MPWeb\WebConf\comserv\win32\conf\_defaultRoot_\cert.pem file to''' ''backup path''.

=== About Restoring Breeze and Home Page Certificates ===

See the [[Cisco_Unified_MeetingPlace,_Release_7.0_--_How_to_Configure_Secure_Sockets_Layer#Applying_the_SSL_Certificate|Applying the SSL Certificate]] section for more information on restoring Breeze and home page certificates.

== Importing the Private Key in to the MPWEB Database ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].
* Back up the complete database before performing this procedure.

===== Procedure =====

# Open the SQL Query Analyzer.
# Select '''Start > All Programs > Microsoft SQL Server > Query Analyzer'''.
# Log in with your SQL username, ”sa,” and password (which you set during the installation of MPWeb).
# Type in the following commands:
#:* '''use mpweb'''
#:* '''update web'''
#:* '''set sslprivatekey='Your private key' '''
# Your private key begins with “BEGIN RSA PRIVATE KEY” and ends with “END RSA PRIVATE KEY”. Copy your private key and paste it between the quotes. You can find your Private key in your PEM file that you saved when you copied and saved the private key for future use.
#: '''Note''': Make sure you include the quotation marks.
# Select the green arrow to Execute Query.
# Determine if your Private Key insertion was successful by entering the following commands in the Query Analyzer window:
#:* '''use mpweb'''
#:* '''select sslprivatekey from web'''
# Select the green arrow to Execute Query and your private key appears the following window.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]]

=== About Home Page and Web Conf SSL certificates ===

When you import the private key using SQL query Analyzer enable SSL by performing the procedure described in the [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]] section.

===== Procedure =====

# Change the web server hostname from an IP Address to a hostname.
# Apply the SSL certificate.
# Enable SSL.

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key

2012-02-15T23:21:53Z

Cgriffen: /* Backing Up the Breeze Certificate */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.

== Exporting the Private Key ==

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

==== Procedure ====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

== Copying and Saving the Private Key for Future Use ==

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Open a DOS prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
# Enter the path to your desktop in the cmd.exe window.
#:<tt> Example: C:\> cd "Documents and Settings\Administrator\Desktop" </tt>
# Enter the full path to OpenSSL.exe keeping the following in mind:
#* After -in, enter the full path to where you placed the file when you exported the private key.
#* After -out, enter the full path to where you want to send the exported file.
#*:<tt> Example:C:\Documents and Settings\Administrator\Desktop>"\Program Files\Cisco Systems\MPWeb\DataSvc\openssl.exe" pkcs12 -in "\Documents and Settings\Administrator\Desktop\mycertificate.pfx" -out "\Documents and Settings\Administrator\Desktop\mycertificate.pem" -nodes </tt>
#: This converts the PFX format to a PEM format. The mycertificate.pem file will have all the certificates starting with the Private key.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

=== Backing Up the Breeze Certificate ===

===== Procedure =====

# Open a DOS prompt.
# Enter the following command: '''Copy c:\Program Files\Cisco Systems\MPWeb\WebConf\comserv\win32\conf\_defaultRoot_\cert.pem file to''' ''backup path''.

=== About Restoring Breeze and Home Page Certificates ===

See the
Complete [[Cisco_Unified_MeetingPlace,_Release_7.0_--_How_to_Configure_Secure_Sockets_Layer#Applying_the_SSL_Certificate|Applying the SSL Certificate]] section for more information on restoring Breeze and home page certificates.

== Importing the Private Key in to the MPWEB Database ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].
* Back up the complete database before performing this procedure.

===== Procedure =====

# Open the SQL Query Analyzer.
# Select '''Start > All Programs > Microsoft SQL Server > Query Analyzer'''.
# Log in with your SQL username, ”sa,” and password (which you set during the installation of MPWeb).
# Type in the following commands:
#:* '''use mpweb'''
#:* '''update web'''
#:* '''set sslprivatekey='Your private key' '''
# Your private key begins with “BEGIN RSA PRIVATE KEY” and ends with “END RSA PRIVATE KEY”. Copy your private key and paste it between the quotes. You can find your Private key in your PEM file that you saved when you copied and saved the private key for future use.
#: '''Note''': Make sure you include the quotation marks.
# Select the green arrow to Execute Query.
# Determine if your Private Key insertion was successful by entering the following commands in the Query Analyzer window:
#:* '''use mpweb'''
#:* '''select sslprivatekey from web'''
# Select the green arrow to Execute Query and your private key appears the following window.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]]

=== About Home Page and Web Conf SSL certificates ===

When you import the private key using SQL query Analyzer enable SSL by performing the procedure described in the [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]] section.

===== Procedure =====

# Change the web server hostname from an IP Address to a hostname.
# Apply the SSL certificate.
# Enable SSL.

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key

2012-02-15T17:57:35Z

Cgriffen: /* Copying and Saving the Private Key for Future Use */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.

== Exporting the Private Key ==

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

==== Procedure ====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

== Copying and Saving the Private Key for Future Use ==

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Open a DOS prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
# Enter the path to your desktop in the cmd.exe window.
#:<tt> Example: C:\> cd "Documents and Settings\Administrator\Desktop" </tt>
# Enter the full path to OpenSSL.exe keeping the following in mind:
#* After -in, enter the full path to where you placed the file when you exported the private key.
#* After -out, enter the full path to where you want to send the exported file.
#*:<tt> Example:C:\Documents and Settings\Administrator\Desktop>"\Program Files\Cisco Systems\MPWeb\DataSvc\openssl.exe" pkcs12 -in "\Documents and Settings\Administrator\Desktop\mycertificate.pfx" -out "\Documents and Settings\Administrator\Desktop\mycertificate.pem" -nodes </tt>
#: This converts the PFX format to a PEM format. The mycertificate.pem file will have all the certificates starting with the Private key.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

=== Backing Up the Breeze Certificate ===

===== Procedure =====

# Open a DOS prompt.
# Enter the following command: '''Copy c:\Program Files\Cisco Systems\MPWeb\WebConf\comserv\win32\conf\_defaultRoot_\cert.pem file to''' ''backup path''.

== Importing the Private Key in to the MPWEB Database ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].
* Back up the complete database before performing this procedure.

===== Procedure =====

# Open the SQL Query Analyzer.
# Select '''Start > All Programs > Microsoft SQL Server > Query Analyzer'''.
# Log in with your SQL username, ”sa,” and password (which you set during the installation of MPWeb).
# Type in the following commands:
#:* '''use mpweb'''
#:* '''update web'''
#:* '''set sslprivatekey='Your private key' '''
# Your private key begins with “BEGIN RSA PRIVATE KEY” and ends with “END RSA PRIVATE KEY”. Copy your private key and paste it between the quotes. You can find your Private key in your PEM file that you saved when you copied and saved the private key for future use.
#: '''Note''': Make sure you include the quotation marks.
# Select the green arrow to Execute Query.
# Determine if your Private Key insertion was successful by entering the following commands in the Query Analyzer window:
#:* '''use mpweb'''
#:* '''select sslprivatekey from web'''
# Select the green arrow to Execute Query and your private key appears the following window.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]]

=== About Home Page and Web Conf SSL certificates ===

When you import the private key using SQL query Analyzer enable SSL by performing the procedure described in the [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]] section.

===== Procedure =====

# Change the web server hostname from an IP Address to a hostname.
# Apply the SSL certificate.
# Enable SSL.

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace Release 6.1 -- About Backing Up Information

2011-12-24T00:08:37Z

Cgriffen:

[[Cisco Unified MeetingPlace Release 6.1]] >
[[Cisco Unified MeetingPlace Release 6.1 -- Cisco Unified MeetingPlace Audio Server, Release 6.1|Cisco Unified MeetingPlace Audio Server]]
> [[Cisco Unified MeetingPlace Release 6.1 -- Maintaining the Audio Server|Maintaining]]
> [[Cisco Unified MeetingPlace Release 6.1 -- Managing and Maintaining Cisco Unified MeetingPlace|Managing and Maintaining]]

== About System Backups ==

Backing up the information stored on your system is essential for recovering from a hardware or software failure, from a user error, or in any other emergency.

If your system suffers a hardware or software failure, you will probably need to restore your system files from backup directories.

[[Cisco Unified MeetingPlace Release 6.1 -- About Backing Up Information#Table: System Backup Methods|Table: System Backup Methods]] describes three backup methods.

'''Table: System Backup Methods'''

{| border = 1
|-
!Method
!Description
|-
|

Disk backup
|

As a redundancy feature, the Cisco Unified MeetingPlace server database is stored on two separate disk drives (Disk 1 and Disk 2). One is established as the primary drive, the other as a backup. Assuming the database on Disk 1 is the active one, the system periodically takes a "snapshot" of its contents and copies all database contents to the database on Disk 2.

By default, the system backs up the database from several times a day to once every two to three days. The frequency of the database backup depends on the amount of data in the active database, particularly user profiles and future and past meeting records. The database back up process occurs in the background, while the system is in operation and can have a moderate impact on system performance. For heavily used systems, we recommend that you configure the system to back up the database during periods of light usage (such as nights or weekends). Use the "configdiskbackup" utility to configure the day and time that the database backup will run.

If Disk 1 fails, the system can be restarted using Disk 2 with the latest copy of the database, but voice files on Disk 1 are lost. If Disk 2
fails, the system continues to operate; however, voice files on Disk 2 are lost.

'''Note: ''' Make sure that you remove the failing drive and replace it as soon as possible. For troubleshooting, see the '' MeetingPlace Server Disk Failure Recovery '' tech note at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_tech_notes_list.html. For more information about replacing a drive, see the '' Hard Disk Replacement Procedure for Cisco Unified MeetingPlace 8106 '' or the '' Hard Disk Replacement Procedure for Cisco Unified MeetingPlace 8112 '', at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_maintenance_guides_list.html.
|-
|

Shadow Server backup
|

The Shadow Server can replace the conference server in case of system or site failure. The switchover of the shadow server ensures that complete functionality (excluding voice and attachment data) can be returned with a minimum loss of time and disruption in service. For more information, see [[Cisco Unified MeetingPlace Release 6.1 -- Configuring a Shadow Server|Configuring a Shadow Server]].
|-
|

Network backup
|

As a second line of resort, you can schedule and run regular file transfers to a computer on your LAN. You can then back up the files according to your company's established procedures. A network backup copies only the configuration and scheduled meeting information in your Cisco Unified MeetingPlace database. No voice recordings, such as profile names and meeting recordings, are included in the backup.

The amount of load on your system determines how long a backup takes. In general, backing up a database takes one hour. Backup could take longer if your system is heavily loaded with meetings and scheduling activity at the time of the backup.

When and how often you schedule backups depend on the number of users, the frequency of configuration changes that occur in your system, and your corporate backup guidelines.
|}

== Performing a Network Backup ==

Before you can perform a network backup, Cisco Unified MeetingPlace Network Backup must be installed and configured.

Follow these guidelines when you perform a network backup:
* Schedule regular daily backups.
* Schedule backups at night.

== Starting a Network Backup ==

You can schedule a backup during normal business hours, even when the system is being used. To ensure that changes made to the database during the day are included in the backup, however we recommend backing up your system at night.

===== To Start a Network Backup =====

# Make sure that Cisco Unified MeetingPlace Network Backup application is installed and configured.
# From your workstation, log in to MeetingTime.
# In the System tab, select the ''' Database Backup '''action.
# For the Frequency attribute, choose how often and when to perform the backup.

{| border = 1
|-
!To Perform
!Choose
|-
|

A single backup immediately
|

''' Once ''', then click ''' Execute '''.
|-
|

A backup at a specified time
|

''' Recurring '''. Then, for the If Recurring, Hr. of Day attribute, enter the time to begin the backup. For the Recurring Every '' x '' Days attribute, enter the number of days between backups. (For example, to back up every other day, enter ''' 2 '''.) Then click ''' Execute '''.
|}

== Viewing Network Backup Results ==

The system performs a full backup of all the information in the system and displays the outcome of the backup in the Results of Last Backup attribute.

===== To View Network Backup Results =====

# In MeetingTime System tab, select the ''' Database Backup '''action.
# For the Results of Last Backup attribute, click in the Values area.
#: A window displays the results of the backup.
#: If a problem occurs during the backup, the system generates an alarm, and a description of the problem is logged in the results of last backup field.

[[Category: Unified MeetingPlace Release 6.1]]

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

2011-12-10T01:17:29Z

Cgriffen: /* Procedure */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|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#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 Perform 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. Profile recorded names are not replicated automically. 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 =====

* [[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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[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

== 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 [[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.
* 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 =====

* [[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]]

== 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]].
* 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 [[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 you need to upgrade your system after setting up Application Server failover, make sure that you follow the failover-specific upgrade instructions in [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0|Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0]] module.

===== 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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] 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

== 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 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]]

=== Setting Up Failover for Two Newly Installed Application Servers ===

===== 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]].
* 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]].

===== Procedure =====

# 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.
# Install any licenses on the first Application Server (Node 1). For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter this commands to initialize and start database replication:
#: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
#: '''mp_replication switchON -S -F''' ''from-sync'' '''[-v]'''
# 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 [[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 =====

* [[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

===== 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.
* 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 ===

In this task:
* Node 1 is the existing Application Server.
* Node 2 is the new Application Server.

===== 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]].
* 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]].
* Back up and archive the data on the existing Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

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

===== Procedure =====

# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the Node 1 eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in Step 1.
# Enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#net|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.
# Enter '''mpx_sys restart''' to restart Node 2.
# Sign in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter these 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]'''
# 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 [[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.

===== 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

===== 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.
* 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 ===

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:
** [[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]]
* 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 =====

# Go to '''http://'''''application-server'''''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Sign in as a System administrator.
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
#: The "copyConfigFiles" commands will include recorded name files as well.

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

===== What to Do Next =====

Perform the following from both Application Servers to replicate custom prompts and some configurations from the Primary application server to the Standby application server during a maintenance window or off-peak hours.

# Log in to the CLI of the active server.
#:If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to compress and transfer the files from the active server to the standby server:
#:'''failoverUtil copyConfigFiles'''
#:This will compress and copy over configuration files and user prompts to the remote server.
# Log in to the CLI of the standby server.
#:If you are logging in remotely, use eth0:0 IP address or hostname.
# Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
#:'''failoverUtil restoreConfigFiles'''
#: This action copies over custom prompts including customized system prompts and user name recordings. Without this action .wav files are not replicated to the standby server.

===== 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 -- 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
* ''Integration Guide for Installing and Configuring Microsoft Outlook with Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html
* [[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 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace#Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]] module
* [[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

== 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 to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]

=== 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:
* [[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]]

'''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 =====

# If the Node 1 is up, then complete these steps:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## Enter this command to change the server to ''standby'' mode:
##: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 2.
#: If you are signing in remotely, use the Node 2 eth0:0 IP address or hostname.
# Enter this command to change the server to ''active ''mode:
#: '''failoverUtil setServer active'''
# Restart the MCUs manually to resynchronize them or complete the steps in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Resynchronizing the MCUs|Resynchronizing the MCUs]].

===== 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 [[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.

===== 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 -- 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

=== 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.
* 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]].
* Back up and archive the data on the currently active Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

===== Procedure =====

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

===== 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 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]
* [[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

===Resynchronizing the MCUs===

=====Procedure=====

#Sign in to the Media Server Administration for the Hardware Media Server.
#Select '''Resource Management > MCU''' from the left panel.
#Select the name of the Audio Blade.
#Select '''Synchronize''' on the Resource Management page.
#Select '''OK''' at the informational message.
#Select '''Synchronize''' on the Active Meeting Types page.
#:The system displays a message that the meetings were downloaded successfully.
#Select '''OK'''.

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

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

2011-12-10T01:16:34Z

Cgriffen: /* Procedure */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|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#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 Perform 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. Profile recorded names are not replicated automically. 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 =====

* [[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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[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

== 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 [[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.
* 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 =====

* [[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]]

== 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]].
* 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 [[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 you need to upgrade your system after setting up Application Server failover, make sure that you follow the failover-specific upgrade instructions in [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0|Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0]] module.

===== 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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] 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

== 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 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]]

=== Setting Up Failover for Two Newly Installed Application Servers ===

===== 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]].
* 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]].

===== Procedure =====

# 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.
# Install any licenses on the first Application Server (Node 1). For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter this commands to initialize and start database replication:
#: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
#: '''mp_replication switchON -S -F''' ''from-sync'' '''[-v]'''
# 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 [[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 =====

* [[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

===== 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.
* 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 ===

In this task:
* Node 1 is the existing Application Server.
* Node 2 is the new Application Server.

===== 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]].
* 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]].
* Back up and archive the data on the existing Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

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

===== Procedure =====

# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the Node 1 eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in Step 1.
# Enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#net|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.
# Enter '''mpx_sys restart''' to restart Node 2.
# Sign in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter these 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]'''
# 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 [[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.

===== 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

===== 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.
* 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 ===

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:
** [[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]]
* 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 =====

# Go to '''http://'''''application-server'''''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Sign in as a System administrator.
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
#: The "copyConfigFiles" commands will include recorded name files as well.

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

===== What to Do Next =====

Perform the following from both Application Servers to replicate custom prompts and some configurations from the Primary application server to the Standby application server during a maintenance window or off-peak hours.

# Log in to the CLI of the active server.
#:If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to compress and transfer the files from the active server to the standby server:
#:'''failoverUtil copyConfigFiles'''
#:This will compress and copy over configuration files and user prompts to the remote server.
# Log in to the CLI of the standby server.
#:If you are logging in remotely, use eth0:0 IP address or hostname.
# Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
#:'''failoverUtil restoreConfigFiles'''
#: This action copies over custom prompts including customized system prompts and user name recordings. Without this action .wav files are not replicated to the standby server.

===== 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 -- 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
* ''Integration Guide for Installing and Configuring Microsoft Outlook with Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html
* [[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 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace#Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]] module
* [[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

== 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 to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]

=== 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:
* [[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]]

'''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 =====

# If the Node 1 is up, then complete these steps:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## Enter this command to change the server to ''standby'' mode:
##: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 2.
#: If you are signing in remotely, use the Node 2 eth0:0 IP address or hostname.
# Enter this command to change the server to ''active ''mode:
#: '''failoverUtil setServer active'''
# Restart the MCUs manually to resynchronize them or complete the steps in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Resynchronizing the MCUs|Resynchronizing the MCUs]].

===== 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 [[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.

===== 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 -- 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

=== 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.
* 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]].
* Back up and archive the data on the currently active Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

===== Procedure =====

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

===== 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 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]
* [[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

===Resynchronizing the MCUs===

=====Procedure=====

#Sign in to the Media Server Administration for the Hardware Media Server.
#Select '''Resource Management > MCU''' from the left panel.
#Select the name of the Audio Blade.
#Select '''Synchronize''' on the Resource Management page.
#Select '''OK''' at the informational message.
#Select '''Synchronize''' on the Active Meeting Types page.
#:The system displays a message that the meetings were downloaded successfully.
#Select '''OK'''.

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

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

2011-12-10T01:12:39Z

Cgriffen: /* Procedure */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|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#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 Perform 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. Profile recorded names are not replicated automically. 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 =====

* [[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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[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

== 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 [[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.
* 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 =====

* [[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]]

== 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]].
* 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 [[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 you need to upgrade your system after setting up Application Server failover, make sure that you follow the failover-specific upgrade instructions in [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0|Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0]] module.

===== 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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] 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

== 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 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]]

=== Setting Up Failover for Two Newly Installed Application Servers ===

===== 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]].
* 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]].

===== Procedure =====

# 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.
# Install any licenses on the first Application Server (Node 1). For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter this commands to initialize and start database replication:
#: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
#: '''mp_replication switchON -S -F''' ''from-sync'' '''[-v]'''
# 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 [[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 =====

* [[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

===== 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.
* 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 ===

In this task:
* Node 1 is the existing Application Server.
* Node 2 is the new Application Server.

===== 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]].
* 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]].
* Back up and archive the data on the existing Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

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

===== Procedure =====

# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the Node 1 eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in Step 1.
# Enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#net|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.
# Enter '''mpx_sys restart''' to restart Node 2.
# Sign in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter these 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]'''
# 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 [[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.

===== 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

===== 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.
* 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 ===

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:
** [[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]]
* 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 =====

# Go to '''http://'''''application-server'''''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Sign in as a System administrator.
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
#: The "copyConfigFiles" commands will include recorded name files as well.

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

===== What to Do Next =====

Perform the following from both Application Servers to replicate custom prompts and some configurations from the Primary application server to the Standby application server during a maintenance window or off-peak hours.

# Log in to the CLI of the active server.
#:If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to compress and transfer the files from the active server to the standby server:
#:'''failoverUtil copyConfigFiles'''
#:This will compress and copy over configuration files and user prompts to the remote server.
# Log in to the CLI of the standby server.
#:If you are logging in remotely, use eth0:0 IP address or hostname.
# Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
#:'''failoverUtil restoreConfigFiles'''
#: This action copies over custom prompts including customized system prompts and user name recordings. Without this action .wav files are not replicated to the standby server.

===== 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 -- 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
* ''Integration Guide for Installing and Configuring Microsoft Outlook with Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html
* [[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 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace#Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]] module
* [[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

== 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 to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]

=== 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:
* [[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]]

'''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 =====

# If the Node 1 is up, then complete these steps:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## Enter this command to change the server to ''standby'' mode:
##: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 2.
#: If you are signing in remotely, use the Node 2 eth0:0 IP address or hostname.
# Enter this command to change the server to ''active ''mode:
#: '''failoverUtil setServer active'''
# Restart the MCUs manually to resynchronize them or complete the steps in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Resynchronizing the MCUs|Resynchronizing the MCUs]].

===== 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 [[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.

===== 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 -- 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

=== 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.
* 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]].
* Back up and archive the data on the currently active Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

===== Procedure =====

# If Node 1 was brought to single-server mode, perform these steps:
## Sign in to Node 2 using eth0:0 to bring Node 2 into Standby mode.
##: '''failoverUtil setServer standby'''
## Sign in to the Node 1 CLI using the console.
## Enter this command to set up failover:
##: '''failoverUtil setDeployment failover'''
## 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.
## Enter this command to initialize database replication:
##: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
## 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''
# If Node 1 was never brought to single-server mode, but database replication configuration was removed from Node 1, do the following:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## Enter this command to initialize database replication:
##: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
## 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''
# Sign in to the CLI of Node 2.
# Enter this command to change Node 2 to ''standby'' mode:
#: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 1.
# 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 [[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.

===== 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 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]
* [[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

===Resynchronizing the MCUs===

=====Procedure=====

#Sign in to the Media Server Administration for the Hardware Media Server.
#Select '''Resource Management > MCU''' from the left panel.
#Select the name of the Audio Blade.
#Select '''Synchronize''' on the Resource Management page.
#Select '''OK''' at the informational message.
#Select '''Synchronize''' on the Active Meeting Types page.
#:The system displays a message that the meetings were downloaded successfully.
#Select '''OK'''.

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

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

2011-12-10T01:11:32Z

Cgriffen: /* Procedure */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|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#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 Perform 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. Profile recorded names are not replicated automically. 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 =====

* [[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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[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

== 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 [[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.
* 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 =====

* [[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]]

== 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]].
* 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 [[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 you need to upgrade your system after setting up Application Server failover, make sure that you follow the failover-specific upgrade instructions in [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0|Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0]] module.

===== 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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] 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

== 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 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]]

=== Setting Up Failover for Two Newly Installed Application Servers ===

===== 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]].
* 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]].

===== Procedure =====

# 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.
# Install any licenses on the first Application Server (Node 1). For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter this commands to initialize and start database replication:
#: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
#: '''mp_replication switchON''' ''[-S -F from-sync]'' '''[-v]'''
# 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 [[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 =====

* [[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

===== 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.
* 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 ===

In this task:
* Node 1 is the existing Application Server.
* Node 2 is the new Application Server.

===== 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]].
* 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]].
* Back up and archive the data on the existing Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

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

===== Procedure =====

# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the Node 1 eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in Step 1.
# Enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#net|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.
# Enter '''mpx_sys restart''' to restart Node 2.
# Sign in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter these 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]'''
# 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 [[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.

===== 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

===== 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.
* 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 ===

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:
** [[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]]
* 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 =====

# Go to '''http://'''''application-server'''''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Sign in as a System administrator.
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
#: The "copyConfigFiles" commands will include recorded name files as well.

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

===== What to Do Next =====

Perform the following from both Application Servers to replicate custom prompts and some configurations from the Primary application server to the Standby application server during a maintenance window or off-peak hours.

# Log in to the CLI of the active server.
#:If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to compress and transfer the files from the active server to the standby server:
#:'''failoverUtil copyConfigFiles'''
#:This will compress and copy over configuration files and user prompts to the remote server.
# Log in to the CLI of the standby server.
#:If you are logging in remotely, use eth0:0 IP address or hostname.
# Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
#:'''failoverUtil restoreConfigFiles'''
#: This action copies over custom prompts including customized system prompts and user name recordings. Without this action .wav files are not replicated to the standby server.

===== 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 -- 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
* ''Integration Guide for Installing and Configuring Microsoft Outlook with Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html
* [[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 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace#Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]] module
* [[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

== 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 to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]

=== 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:
* [[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]]

'''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 =====

# If the Node 1 is up, then complete these steps:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## Enter this command to change the server to ''standby'' mode:
##: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 2.
#: If you are signing in remotely, use the Node 2 eth0:0 IP address or hostname.
# Enter this command to change the server to ''active ''mode:
#: '''failoverUtil setServer active'''
# Restart the MCUs manually to resynchronize them or complete the steps in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Resynchronizing the MCUs|Resynchronizing the MCUs]].

===== 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 [[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.

===== 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 -- 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

=== 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.
* 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]].
* Back up and archive the data on the currently active Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

===== Procedure =====

# If Node 1 was brought to single-server mode, perform these steps:
## Sign in to Node 2 using eth0:0 to bring Node 2 into Standby mode.
##: '''failoverUtil setServer standby'''
## Sign in to the Node 1 CLI using the console.
## Enter this command to set up failover:
##: '''failoverUtil setDeployment failover'''
## 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.
## Enter this command to initialize database replication:
##: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
## 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''
# If Node 1 was never brought to single-server mode, but database replication configuration was removed from Node 1, do the following:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## Enter this command to initialize database replication:
##: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
## 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''
# Sign in to the CLI of Node 2.
# Enter this command to change Node 2 to ''standby'' mode:
#: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 1.
# 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 [[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.

===== 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 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]
* [[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

===Resynchronizing the MCUs===

=====Procedure=====

#Sign in to the Media Server Administration for the Hardware Media Server.
#Select '''Resource Management > MCU''' from the left panel.
#Select the name of the Audio Blade.
#Select '''Synchronize''' on the Resource Management page.
#Select '''OK''' at the informational message.
#Select '''Synchronize''' on the Active Meeting Types page.
#:The system displays a message that the meetings were downloaded successfully.
#Select '''OK'''.

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

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

2011-12-10T01:09:51Z

Cgriffen: /* Procedure */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|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#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 Perform 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. Profile recorded names are not replicated automically. 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 =====

* [[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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[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

== 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 [[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.
* 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 =====

* [[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]]

== 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]].
* 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 [[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 you need to upgrade your system after setting up Application Server failover, make sure that you follow the failover-specific upgrade instructions in [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0|Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0]] module.

===== 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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] 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

== 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 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]]

=== Setting Up Failover for Two Newly Installed Application Servers ===

===== 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]].
* 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]].

===== Procedure =====

# 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.
# Install any licenses on the first Application Server (Node 1). For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter this commands to initialize and start database replication:
#: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
#: '''mp_replication switchON [-v]'''
# 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 [[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 =====

* [[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

===== 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.
* 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 ===

In this task:
* Node 1 is the existing Application Server.
* Node 2 is the new Application Server.

===== 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]].
* 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]].
* Back up and archive the data on the existing Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

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

===== Procedure =====

# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the Node 1 eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in Step 1.
# Enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#net|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.
# Enter '''mpx_sys restart''' to restart Node 2.
# Sign in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter these 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]'''
# 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 [[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.

===== 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

===== 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.
* 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 ===

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:
** [[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]]
* 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 =====

# Go to '''http://'''''application-server'''''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Sign in as a System administrator.
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
#: The "copyConfigFiles" commands will include recorded name files as well.

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

===== What to Do Next =====

Perform the following from both Application Servers to replicate custom prompts and some configurations from the Primary application server to the Standby application server during a maintenance window or off-peak hours.

# Log in to the CLI of the active server.
#:If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to compress and transfer the files from the active server to the standby server:
#:'''failoverUtil copyConfigFiles'''
#:This will compress and copy over configuration files and user prompts to the remote server.
# Log in to the CLI of the standby server.
#:If you are logging in remotely, use eth0:0 IP address or hostname.
# Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
#:'''failoverUtil restoreConfigFiles'''
#: This action copies over custom prompts including customized system prompts and user name recordings. Without this action .wav files are not replicated to the standby server.

===== 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 -- 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
* ''Integration Guide for Installing and Configuring Microsoft Outlook with Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html
* [[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 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace#Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]] module
* [[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

== 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 to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]

=== 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:
* [[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]]

'''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 =====

# If the Node 1 is up, then complete these steps:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## Enter this command to change the server to ''standby'' mode:
##: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 2.
#: If you are signing in remotely, use the Node 2 eth0:0 IP address or hostname.
# Enter this command to change the server to ''active ''mode:
#: '''failoverUtil setServer active'''
# Restart the MCUs manually to resynchronize them or complete the steps in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Resynchronizing the MCUs|Resynchronizing the MCUs]].

===== 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 [[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.

===== 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 -- 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

=== 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.
* 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]].
* Back up and archive the data on the currently active Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

===== Procedure =====

# If Node 1 was brought to single-server mode, perform these steps:
## Sign in to Node 2 using eth0:0 to bring Node 2 into Standby mode.
##: '''failoverUtil setServer standby'''
## Sign in to the Node 1 CLI using the console.
## Enter this command to set up failover:
##: '''failoverUtil setDeployment failover'''
## 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.
## Enter this command to initialize database replication:
##: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
## 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''
# If Node 1 was never brought to single-server mode, but database replication configuration was removed from Node 1, do the following:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## Enter this command to initialize database replication:
##: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
## 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''
# Sign in to the CLI of Node 2.
# Enter this command to change Node 2 to ''standby'' mode:
#: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 1.
# 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 [[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.

===== 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 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]
* [[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

===Resynchronizing the MCUs===

=====Procedure=====

#Sign in to the Media Server Administration for the Hardware Media Server.
#Select '''Resource Management > MCU''' from the left panel.
#Select the name of the Audio Blade.
#Select '''Synchronize''' on the Resource Management page.
#Select '''OK''' at the informational message.
#Select '''Synchronize''' on the Active Meeting Types page.
#:The system displays a message that the meetings were downloaded successfully.
#Select '''OK'''.

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

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

2011-12-10T01:03:41Z

Cgriffen: /* Procedure */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|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#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 Perform 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. Profile recorded names are not replicated automically. 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 =====

* [[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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[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

== 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 [[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.
* 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 =====

* [[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]]

== 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]].
* 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 [[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 you need to upgrade your system after setting up Application Server failover, make sure that you follow the failover-specific upgrade instructions in [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0|Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0]] module.

===== 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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] 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

== 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 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]]

=== Setting Up Failover for Two Newly Installed Application Servers ===

===== 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]].
* 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]].

===== Procedure =====

# 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.
# Install any licenses on the first Application Server (Node 1). For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter this commands to initialize and start database replication:
#: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
#: '''mp_replication switchON [-v]'''
# 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 [[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 =====

* [[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

===== 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.
* 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 ===

In this task:
* Node 1 is the existing Application Server.
* Node 2 is the new Application Server.

===== 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]].
* 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]].
* Back up and archive the data on the existing Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

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

===== Procedure =====

# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the Node 1 eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in Step 1.
# Enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#net|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.
# Enter '''mpx_sys restart''' to restart Node 2.
# Sign in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter these 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]'''
# 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 [[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.

===== 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

===== 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.
* 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 ===

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:
** [[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]]
* 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 =====

# Go to '''http://'''''application-server'''''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Sign in as a System administrator.
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
#: The "copyConfigFiles" commands will include recorded name files as well.

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

===== What to Do Next =====

Perform the following from both Application Servers to replicate custom prompts and some configurations from the Primary application server to the Standby application server during a maintenance window or off-peak hours.

# Log in to the CLI of the active server.
#:If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to compress and transfer the files from the active server to the standby server:
#:'''failoverUtil copyConfigFiles'''
#:This will compress and copy over configuration files and user prompts to the remote server.
# Log in to the CLI of the standby server.
#:If you are logging in remotely, use eth0:0 IP address or hostname.
# Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
#:'''failoverUtil restoreConfigFiles'''
#: This action copies over custom prompts including customized system prompts and user name recordings. Without this action .wav files are not replicated to the standby server.

===== 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 -- 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
* ''Integration Guide for Installing and Configuring Microsoft Outlook with Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html
* [[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 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace#Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]] module
* [[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

== 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 to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]

=== 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:
* [[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]]

'''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 =====

# If the Node 1 is up, then complete these steps:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## Enter this command to change the server to ''standby'' mode:
##: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 2.
#: If you are signing in remotely, use the Node 2 eth0:0 IP address or hostname.
# Enter this command to change the server to ''active ''mode:
#: '''failoverUtil setServer active'''
# Restart the MCUs manually to resynchronize them or complete the steps in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Resynchronizing the MCUs|Resynchronizing the MCUs]].

===== 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 [[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.

===== 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 -- 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

=== 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.
* 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]].
* Back up and archive the data on the currently active Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

===== Procedure =====

# If Node 1 was brought to single-server mode, perform these steps:
## Sign in to Node 2 using eth0:0 to bring Node 2 into Standby mode.
##: '''failoverUtil setServer standby'''
## Sign in to the Node 1 CLI using the console.
## Enter this command to set up failover:
##: '''failoverUtil setDeployment failover'''
## 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.
## 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'''
## 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''
# If Node 1 was never brought to single-server mode, but database replication configuration was removed from Node 1, do the following:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## 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'''
## 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''
# Sign in to the CLI of Node 2.
# Enter this command to change Node 2 to ''standby'' mode:
#: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 1.
# 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 [[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.

===== 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 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]
* [[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

===Resynchronizing the MCUs===

=====Procedure=====

#Sign in to the Media Server Administration for the Hardware Media Server.
#Select '''Resource Management > MCU''' from the left panel.
#Select the name of the Audio Blade.
#Select '''Synchronize''' on the Resource Management page.
#Select '''OK''' at the informational message.
#Select '''Synchronize''' on the Active Meeting Types page.
#:The system displays a message that the meetings were downloaded successfully.
#Select '''OK'''.

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

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

2011-12-10T00:57:33Z

Cgriffen: /* Procedure */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|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#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 Perform 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. Profile recorded names are not replicated automically. 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 =====

* [[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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[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

== 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 [[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.
* 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 =====

* [[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]]

== 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]].
* 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 [[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 you need to upgrade your system after setting up Application Server failover, make sure that you follow the failover-specific upgrade instructions in [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0|Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0]] module.

===== 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#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 Perform Application Server Failover|How to Perform Application Server Failover]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] 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

== 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 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]]

=== Setting Up Failover for Two Newly Installed Application Servers ===

===== 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]].
* 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]].

===== Procedure =====

# 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.
# Install any licenses on the first Application Server (Node 1). For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Enter this command to initialize database replication:
#: '''mp_replication init -n 2 -r''' ''remote-eth0:0'' '''[-v]'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter this commands to initialize and start database replication:
#: '''mp_replication init -n 1 -r''' ''remote-eth0:0'' '''[-v]'''
#: '''mp_replication switchON [-v]'''
# 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 [[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 =====

* [[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

===== 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.
* 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 ===

In this task:
* Node 1 is the existing Application Server.
* Node 2 is the new Application Server.

===== 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]].
* 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]].
* Back up and archive the data on the existing Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

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

===== Procedure =====

# 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.
# Install failover licenses on the second Application Server (Node 2), and reboot the system. For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
# Sign in to the CLI of Node 1 - login as root.
#: If you are signing in remotely, use the Node 1 eth0 IP address or hostname.
# Enter this command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# Sign in to the CLI of Node 2 - login as root.
#: If you are signing in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in Step 1.
# Enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#net|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.
# Enter '''mpx_sys restart''' to restart Node 2.
# Sign in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter this command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# 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.
# 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'''
# Sign in to the CLI of Node 1.
#: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
# 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''
# 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 [[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.

===== 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

===== 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.
* 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 ===

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:
** [[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]]
* 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 =====

# Go to '''http://'''''application-server'''''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Sign in as a System administrator.
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
#: The "copyConfigFiles" commands will include recorded name files as well.

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

===== What to Do Next =====

Perform the following from both Application Servers to replicate custom prompts and some configurations from the Primary application server to the Standby application server during a maintenance window or off-peak hours.

# Log in to the CLI of the active server.
#:If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to compress and transfer the files from the active server to the standby server:
#:'''failoverUtil copyConfigFiles'''
#:This will compress and copy over configuration files and user prompts to the remote server.
# Log in to the CLI of the standby server.
#:If you are logging in remotely, use eth0:0 IP address or hostname.
# Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
#:'''failoverUtil restoreConfigFiles'''
#: This action copies over custom prompts including customized system prompts and user name recordings. Without this action .wav files are not replicated to the standby server.

===== 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 -- 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
* ''Integration Guide for Installing and Configuring Microsoft Outlook with Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html
* [[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 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace#Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]] module
* [[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

== 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 to Switch to the Previous Active Server|Performing Application Server Failover to Switch to the Previous Active Server]]

=== 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:
* [[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]]

'''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 =====

# If the Node 1 is up, then complete these steps:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## Enter this command to change the server to ''standby'' mode:
##: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 2.
#: If you are signing in remotely, use the Node 2 eth0:0 IP address or hostname.
# Enter this command to change the server to ''active ''mode:
#: '''failoverUtil setServer active'''
# Restart the MCUs manually to resynchronize them or complete the steps in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Resynchronizing the MCUs|Resynchronizing the MCUs]].

===== 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 [[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.

===== 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 -- 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

=== 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.
* 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]].
* Back up and archive the data on the currently active Application Server (Node 1). See the [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

===== Procedure =====

# If Node 1 was brought to single-server mode, perform these steps:
## Sign in to Node 2 using eth0:0 to bring Node 2 into Standby mode.
##: '''failoverUtil setServer standby'''
## Sign in to the Node 1 CLI using the console.
## Enter this command to set up failover:
##: '''failoverUtil setDeployment failover'''
## 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.
## 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'''
## 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''
# If Node 1 was never brought to single-server mode, but database replication configuration was removed from Node 1, do the following:
## Sign in to the CLI of Node 1.
##: If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
## 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'''
## 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''
# Sign in to the CLI of Node 2.
# Enter this command to change Node 2 to ''standby'' mode:
#: '''failoverUtil setServer standby'''
# Sign in to the CLI of Node 1.
# 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 [[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.

===== 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 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Performing Application Server Failover|Performing Application Server Failover]]
* [[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

===Resynchronizing the MCUs===

=====Procedure=====

#Sign in to the Media Server Administration for the Hardware Media Server.
#Select '''Resource Management > MCU''' from the left panel.
#Select the name of the Audio Blade.
#Select '''Synchronize''' on the Resource Management page.
#Select '''OK''' at the informational message.
#Select '''Synchronize''' on the Active Meeting Types page.
#:The system displays a message that the meetings were downloaded successfully.
#Select '''OK'''.

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Usage Configuration Page

2011-11-02T21:01:19Z

Cgriffen: /* Table: Field Reference: Usage Configuration Page */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Reference Information| Reference Information]]

To find this page, click '''System Configuration > Usage Configuration'''.

===== Table: Field Reference: Usage Configuration Page =====

{| border = 1
|-
!Field
!Description
|-
|<td colspan="2" rowspan="1">|'''Usage Configuration'''
|-
|

Attendant phone
|

Phone number that callers are routed to if they do not press a number at a voice prompt or press 0 for operator assistance.1

'''Tip: ''' Make sure that the people at this phone number are available and trained to provide assistance for Cisco Unified MeetingPlace.

Restriction: The + character is allowed only as the first character in the field.
|-
|

24-hour time
|

Whether to show meeting times by a 24-hour clock.

Default: No
|-
|

Dial attendant on timeout
|

Whether callers are transferred to the attendant in the following situations:
* Caller dials 0 for operator assistance.
* Caller does not enter a number at a voice prompt.

Default: No
|-
|

Language 1

Language 2

Language 3

Language 4
|

Enabled languages. The [[Cisco Unified MeetingPlace, Release 7.0 -- Usage Configuration Page#Language 1|Language 1]] field sets the default system-wide language.
* If the languages license is installed, the number of active language fields (up to four fields) is determined by the number of installed languages.
* If the languages license is ''not'' installed, only the [[Cisco Unified MeetingPlace, Release 7.0 -- Usage Configuration Page#Language 1|Language 1]] field appears.

Restriction: You must restart2 the system to enable or disable a language.

'''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage.

Default: English (US)
|-
|

Guests can lock and record meetings
|

If set to No, then guest users cannot lock or record meetings.

If set to Yes:
* Guests can lock meetings.
* If the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Can record meetings|Can record meetings]] field in the preconfigured [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure User Profiles#Guest Profile|Guest Profile]] is also set to Yes, guests can use the TUI7 to start and stop the meeting recording. Guests cannot start and stop recordings from the web meeting room, because only meeting moderators may do so.
|-
|

Route calls to meeting ID that matches DID
|

Whether to enable the DID3 feature, which routes incoming calls directly to meetings based on DID and DNIS4. When the DID feature is enabled, the caller is routed to the meeting ID that is equal to the DID phone number.

See [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Direct Inward Dial for Cisco Unified MeetingPlace|Configuring Direct Inward Dial for Cisco Unified MeetingPlace]].
|-
|<td colspan="2" rowspan="1">|'''Security'''
|-
|

Minimum profile password length
|

Number of numeric characters required in the [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile password|Profile password]] for each user.

Restriction: This field does not apply to Directory Service users. See [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]].

Default: 5
|-
|

Change profile password (days)
|

Frequency, in days, at which the [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile password|Profile password]] must be changed in each user profile.

A value of 0 means that the [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile password|Profile password]] never needs to change.

Restriction: This field does not apply to Directory Service users. See [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]].

Default: 90
|-
|

Minimum user password length
|

Number of alphanumeric characters required in the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password|User password]] for each user.

Restriction: This field does not apply to Directory Service users. See [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]].

Default: 5
|-
|

Change user password (days)
|

Frequency, in days, at which the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password|User password]] must be changed in each user profile.

A value of 0 means that the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password|User password]] never needs to change.

Restriction: This field does not apply to Directory Service users. See [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]].

Default: 90
|-
|

Maximum profile login attempts
|
Release 7.0.1: Number of consecutive sign-in attempts within a session before a user profile is locked.

Release 7.0.2: Number of times that a user may try to:
*Sign in to Cisco Unified MeetingPlace before the user profile is locked.
*Enter a meeting password before the call is transferred to the attendant. If no attendant is available, then the call is disconnected.
*Enter a Profile PIN to start a reservationless meeting from the TUI before the user profile is locked.

A value of 0 means that there is no limit to the number of attempts.

Before reaching the maximum number of attempts, the user can restart the counter by taking one of these actions:
*Close the browser and open a new one.
*End the call to Cisco Unified MeetingPlace and begin a new call.

Restriction: Preconfigured user profiles cannot be locked.

Default: 3
|-
|

User locked interval
|

The amount of time for which a user profile stays locked if the user fails to sign into the
Administration Center. The lock expires after the specified period for administrative
users but it does not expire for end users. An administrator must manually unlock an end
user’s user profile.

A value of 0 means the user profile stays locked until the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]] unlocks it.

Default: 0
|-
|
|

This field was introduced in Release 7.0.2.
|-
|<td colspan="2" rowspan="1">|'''Click-to-Attend Link Configuration'''
|-
|

External web server hostname
|

FQDN5 of the Web Server in the DMZ6.

Example: meetings.example.com
|-
|

Internal web server hostname
|

FQDN of the Web Server on the intranet.

Example: meetingsint.example.com
|-
|

SSL enabled on external web server

SSL enabled on internal web server
|

Determines whether the click-to-attend URLs begin with "https" or "http".

For information about configuring SSL on the Web Servers, see [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Web Conferencing Security Features|Configuring Cisco Unified MeetingPlace Web Conferencing Security Features]].
|-
|<td colspan="2" rowspan="1">|'''Access Information'''
|-
|

Label for access phone number 1
|

Text used to describe the first meeting access phone number that is displayed in the following places:
* E-mail notifications
* Telephone pop-up notification box in the full web meeting room
* Cisco Unified IP Phone screens (only when subscribed to the Cisco Unified MeetingPlace service for the PhoneView.)

Example: "Dial-In"

Restrictions:
* Changes to this field take effect only after restarting the system.2
* (For full web meeting rooms only) See [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Access Phone Numbers and Notification Labels|Restrictions for Access Phone Numbers and Notification Labels]].
|-
|

Access phone number 1
|

First meeting access phone number.1

Restrictions:
* Changes to this field take effect only after restarting the system.2
* (For Find Me feature with pagers only) Only the characters 0-9, #, and * are processed and sent to pagers at the start of a meeting. See [[Cisco Unified MeetingPlace, Release 7.0 -- About the Find Me Feature|About the Find Me Feature]].
* The + character is allowed only as the first character in the field.
|-
|

Label for access phone number 2
|

Text used to describe the second meeting access phone number.

Example: "Toll-Free"

Restrictions:
* Changes to this field take effect only after restarting the system.2
* (For full web meeting rooms only) See [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Access Phone Numbers and Notification Labels|Restrictions for Access Phone Numbers and Notification Labels]].
|-
|

Access phone number 2
|

Second meeting access phone number.1

Restrictions:
* Changes to this field take effect only after restarting the system.2
* The + character is allowed only as the first character in the field.
|-
|

Label for access phone number 3
|

Text used to describe the third meeting access phone number.

Example: "Internal"

Restrictions:
* Changes to this field take effect only after restarting the system.2
* (For full web meeting rooms only) See [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Access Phone Numbers and Notification Labels|Restrictions for Access Phone Numbers and Notification Labels]].
|-
|

Access phone number 3
|

Third meeting access phone number.1

Restrictions:
* Changes to this field take effect only after restarting the system.2
* The + character is allowed only as the first character in the field.
|-
|

Label for access phone number 4
|

Text used to describe the fourth meeting access phone number.

Example: "International"

Restrictions:
* Changes to this field take effect only after restarting the system.2
* (For full web meeting rooms only) See [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Access Phone Numbers and Notification Labels|Restrictions for Access Phone Numbers and Notification Labels]].
|-
|

Access phone number 4
|

Fourth meeting access phone number.1

Restrictions:
* Changes to this field take effect only after restarting the system.2
* The + character is allowed only as the first character in the field.
|-
|<td colspan="2" rowspan="1">|'''Reservationless Meetings'''
|-
|

Enable reservationless meetings
|

Whether reservationless meetings are enabled on the system.

Default: Yes
|-
|

Allow any profiled user to initiate
|

Whether any profiled user can start a reservationless meeting from the TUI before the meeting owner joins.

Release 7.0.1 and 7.0.2(MR1): Options are Yes or No.

Default: Yes

Release 7.0.3 (MR2): The following options apply:
* No -- Profiled users cannot start a reservationless meeting before the meeting owner joins.
* Yes, by pressing 3 -- Profiled users can start a reservationless meeting by pressing 3 on their phones.
* Yes, by joining -- Profiled users can start a reservationless meeting by joining the meeting.

Default: Yes, by pressing 3

|-
|

Bill initiator
|

Who gets billed for each reservationless meeting:
* Yes -- Bill the user who starts the meeting.
* No -- Bill the meeting owner.

Restriction: This field is always set to No when the [[Cisco Unified MeetingPlace, Release 7.0 -- Usage Configuration Page#Allow any profiled user to initiate|Allow any profiled user to initiate]] field is set to No.

Default: Yes
|-
|

TUI menu is reservationless only
|

Whether users can schedule meetings or only start reservationless meetings from the TUI7.

Default: No
|-
|

Owner can press 2 in TUI to initiate
|

Whether meeting owners can initiate reservationless meetings more quickly by skipping the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile number|Profile number]] entry.
* Yes -- Meeting owner can start a reservationless meeting from the TUI waiting room by pressing '''2''' and entering the [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile password|Profile password]].
* No -- Meeting owner starts the reservationless meeting from the TUI waiting room by pressing '''3''' and entering both the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile number|Profile number]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile password|Profile password]].
: If the [[Cisco Unified MeetingPlace, Release 7.0 -- Usage Configuration Page#Allow any profiled user to initiate|Allow any profiled user to initiate]] field is set to Yes, any profiled user may press '''3''' to start the reservationless meeting with both the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile number|Profile number]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile password|Profile password]].

Default: No
|-
|<td colspan="2" rowspan="1">|'''Alarms'''
|-
|

Call out on major alarm

Phone number to call on alarm
|

Whether the system places a call to the specified phone number1 if an error condition affects system operation.

Recommendation: Yes

Restriction: The + character is allowed only as the first character in the field.

Default: No
|-
|<td colspan="2" rowspan="1">|'''Outdial Meetings'''
|-
|

Number of retry attempts
|

Number of times the system tries to call each person, when dial out is enabled for a meeting. This setting also determines the number of times the system goes through the [[Cisco Unified MeetingPlace, Release 7.0 -- Dial-Out Features and Voice Prompt Languages#Find Me|Find Me]] sequence for each user.

Default: 2
|-
|

Delay between retries (sec)
|

Number of seconds between dial-out retries. This setting also determines the number of seconds between each set of [[Cisco Unified MeetingPlace, Release 7.0 -- Dial-Out Features and Voice Prompt Languages#Find Me|Find Me]] calls.

Restriction: The actual time between dial-out attempts may be longer due to network delays.

Default: 300
|-
|<td colspan="2" rowspan="1">|'''Pager Settings'''
|-
|

Prefix string
|

Number string required by certain paging services in some counties. Cisco Unified MeetingPlace adds this string at beginning of all pages.

Keep this field blank if users' paging services do not require prefix string.

Supported characters: 0, 1, 2, 3, #, and *
|-
|

Suffix string
|

Number string required by certain paging services in some counties. Cisco Unified MeetingPlace adds this string at the end of all pages.

Keep this field blank if users' paging services do not require suffix string.

Supported characters: 0, 1, 2, 3, #, and *
|-
|<td colspan="2" rowspan="1">|'''[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Attendant|Attendant]] Privileges'''
|-
|

Create user profiles and user groups

Delete user profiles and user groups

Modify user profiles and user groups

Lock and unlock user profiles
|

Whether attendants can create, delete, edit, lock, and unlock user profiles and user groups from the Administration Center and MeetingPlace Conference Manager.

Default: Yes
|-
|

Run reports
|

Whether attendants can run and view formatted reports in the Administration Center.

Default: No
|-
|

View alarms
|

Whether attendants can view alarms from the Administration Center.

Default: No
|-
|

End meetings
|

Whether attendants can end meetings from MeetingPlace Conference Manager and the Cisco Unified MeetingPlace end-user web interface.

Default: Yes
|-
|<td colspan="2" rowspan="1">|'''Password Complexity Checks'''
|-
|

Password contains characters from at least three classes
|

Whether each new or modified [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password|User password]] must contain characters from at least ''three'' of the following character classes:
* lowercase letters
* uppercase letters
* digits
* special characters

This field was introduced in Release 7.0.2.

Default: No
|-
|

No character in the new password repeated more than three times
|

Whether each new or modified [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password|User password]] is restricted from containing a character that is repeated more than ''three'' times consecutively.

This field was introduced in Release 7.0.2.

Default: No
|-
|

Password does not repeat or reverse the user name
|

Whether each new or modified [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password|User password]] is restricted from being a repeat or the reverse of the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User ID|User ID]].

This field was introduced in Release 7.0.2.

Default: No
|-
|

Password is not "cisco", "ocsic" or variation of these
|

Whether each new or modified [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password|User password]] is restricted from being any variant of "cisco" that was obtained by modifying the order of the characters or by changing the capitalization of any letters.

This field was introduced in Release 7.0.2.

Default: No
|-
|<td colspan="2" rowspan="1">|'''Miscellaneous'''
|-
|

Preserve mute status in meetings
|

Whether to preserve speaker mute status during meetings when users are removed from the floor or placed in the waiting room.

This field was called "Preserve mute status" in Release 7.0.1.
|}

'''Footnotes:'''

1. The required format for phone numbers is determined by the call-control device for your IP telephony network. Therefore, enter phone numbers in the same format used to dial similar numbers from a phone on the same IP telephony network as Cisco Unified MeetingPlace. For example, if calls within your company are made by dialing the last four digits of a phone number, then enter only the last four digits in Cisco Unified MeetingPlace for internal phone numbers. If, however, you want Cisco Unified MeetingPlace to call a phone in a different area code, then you may need to include 91 and the complete telephone number including the area code.

2. A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage. To restart the system, enter sudo mpx_sys restart in the CLI. For information about logging into the CLI, see the Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace module.

'''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost.

3. DID = Direct Inward Dial

4. DNIS = Dialed Number Identification Service

5. FQDN = fully-qualified domain name

6. DMZ = demilitarized zone

7. TUI = telephone user interface

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Access Phone Numbers and Notification Labels for Cisco Unified MeetingPlace|Configuring Access Phone Numbers and Notification Labels for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Languages for Cisco Unified MeetingPlace|Configuring Languages for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Recordings for Cisco Unified MeetingPlace|Configuring Recordings for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring E-Mail Notifications for Cisco Unified MeetingPlace|Configuring E-Mail Notifications for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Attendant Settings for Cisco Unified MeetingPlace|Configuring Attendant Settings for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Call Control for Cisco Unified MeetingPlace|Configuring Call Control for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Direct Inward Dial for Cisco Unified MeetingPlace|Configuring Direct Inward Dial for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]]

[[Category: Reference Information for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key

2011-10-18T22:45:17Z

Cgriffen: /* Importing the Private Key in to the MPWEB Database */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.

== Exporting the Private Key ==

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

==== Procedure ====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

== Copying and Saving the Private Key for Future Use ==

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Open a DOS prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
# Enter the path to your desktop in the cmd.exe window.
#:<tt> Example: C:\> cd "Documents and Settings\Administrator\Desktop" </tt>
# Enter the full path to OpenSSL.exe keeping the following in mind:
#* After -in, enter the full path to where you placed the file when you exported the private key.
#* After -out, enter the full path to where you want to send the exported file.
#*:<tt> Example:C:\Documents and Settings\Administrator\Desktop>"\Program Files\Cisco Systems\MPWeb\DataSvc\openssl.exe" pkcs12 -in "\Documents and Settings\Administrator\Desktop\mycertificate.pfx" -out "\Documents and Settings\Administrator\Desktop\mycertificate.pem" -nodes </tt>
#: This converts the PFX format to a PEM format. The mycertificate.pem file will have all the certificates starting with the Private key.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

== Importing the Private Key in to the MPWEB Database ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].
* Back up the complete database before performing this procedure.

===== Procedure =====

# Open the SQL Query Analyzer.
# Select '''Start > All Programs > Microsoft SQL Server > Query Analyzer'''.
# Log in with your SQL username, ”sa,” and password (which you set during the installation of MPWeb).
# Type in the following commands:
#:* '''use mpweb'''
#:* '''update web'''
#:* '''set sslprivatekey='Your private key' '''
# Your private key begins with “BEGIN RSA PRIVATE KEY” and ends with “END RSA PRIVATE KEY”. Copy your private key and paste it between the quotes. You can find your Private key in your PEM file that you saved when you copied and saved the private key for future use.
#: '''Note''': Make sure you include the quotation marks.
# Select the green arrow to Execute Query.
# Determine if your Private Key insertion was successful by entering the following commands in the Query Analyzer window:
#:* '''use mpweb'''
#:* '''select sslprivatekey from web'''
# Select the green arrow to Execute Query and your private key appears the following window.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]]

=== About Home Page and Web Conf SSL certificates ===

When you import the private key using SQL query Analyzer enable SSL by performing the procedure described in the [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]] section.

===== Procedure =====

# Change the web server hostname from an IP Address to a hostname.
# Apply the SSL certificate.
# Enable SSL.

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key

2011-10-18T22:43:23Z

Cgriffen: /* Importing the Private Key in to the MPWEB Database */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.

== Exporting the Private Key ==

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

==== Procedure ====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

== Copying and Saving the Private Key for Future Use ==

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Open a DOS prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
# Enter the path to your desktop in the cmd.exe window.
#:<tt> Example: C:\> cd "Documents and Settings\Administrator\Desktop" </tt>
# Enter the full path to OpenSSL.exe keeping the following in mind:
#* After -in, enter the full path to where you placed the file when you exported the private key.
#* After -out, enter the full path to where you want to send the exported file.
#*:<tt> Example:C:\Documents and Settings\Administrator\Desktop>"\Program Files\Cisco Systems\MPWeb\DataSvc\openssl.exe" pkcs12 -in "\Documents and Settings\Administrator\Desktop\mycertificate.pfx" -out "\Documents and Settings\Administrator\Desktop\mycertificate.pem" -nodes </tt>
#: This converts the PFX format to a PEM format. The mycertificate.pem file will have all the certificates starting with the Private key.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

== Importing the Private Key in to the MPWEB Database ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].
* Back up the complete database before performing this procedure.

===== Procedure =====

# Open the SQL Query Analyzer.
# Select '''Start > All Programs > Microsoft SQL Server > Query Analyzer'''.
# Log in with your SQL username, ”sa,” and password (which you set during the installation of MPWeb).
# Type in the following commands:
#:* '''use mpweb'''
#:* '''update web'''
#:* '''set sslprivatekey='Your private key' '''
# Your private key begins with “BEGIN RSA PRIVATE KEY” and ends with “END RSA PRIVATE KEY”. Copy your private key and paste it between the quotes. You can find your Private key in your PEM file that you saved when you copied and saved the private key for future use.
#: '''Note''': Make sure you include the quotation marks.
# Select the green arrow to Execute Query.
# Determine if your Private Key insertion was successful by entering the following commands in the Query Analyzer window:
#:* '''use mpweb'''
#:* '''select sslprivatekey from web'''
# Select the green arrow to Execute Query and your private key appears the following window.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key

2011-10-18T22:41:37Z

Cgriffen: /* Procedure */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.

== Exporting the Private Key ==

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

==== Procedure ====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

== Copying and Saving the Private Key for Future Use ==

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Open a DOS prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
# Enter the path to your desktop in the cmd.exe window.
#:<tt> Example: C:\> cd "Documents and Settings\Administrator\Desktop" </tt>
# Enter the full path to OpenSSL.exe keeping the following in mind:
#* After -in, enter the full path to where you placed the file when you exported the private key.
#* After -out, enter the full path to where you want to send the exported file.
#*:<tt> Example:C:\Documents and Settings\Administrator\Desktop>"\Program Files\Cisco Systems\MPWeb\DataSvc\openssl.exe" pkcs12 -in "\Documents and Settings\Administrator\Desktop\mycertificate.pfx" -out "\Documents and Settings\Administrator\Desktop\mycertificate.pem" -nodes </tt>
#: This converts the PFX format to a PEM format. The mycertificate.pem file will have all the certificates starting with the Private key.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

== Importing the Private Key in to the MPWEB Database ==

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

===== Procedure =====

# Open SQL Server Enterprise Manager.
#: Click '''Start > All Programs > Microsoft SQL Server > Enterprise Manager'''.
# Navigate to the MPWEB database.
#: Click the''' + '''sign next to SQL Server Group > LOCAL > Databases > MPWEB to open the appropriate directory trees.
# Click '''Tables''' in the MPWEB directory.
#: A list of tables opens in the right pane.
# Right-click '''Web''' in the right pane.
# Select '''Open table > Return all rows'''.
#: The Web database table displays.
# Scroll to the right until you see the SSLPrivateKey column.
# Open the PEM file in Notepad.
#: You saved the PEM file when you copied and saved the private key for future use.
# Copy the private key in its entirety.
#: The private key begins with "Begin RSA Private key" and ends with "end RSA private key".
# Paste the private key into the SSLPrivateKey field.
## Click the field before the SSLPrivateKey column.
## Press the Tab key on your keyboard to select all of the data in the SSLPrivateKey field.
## Right-click and select '''Paste''' to paste the value you copied from Notepad.
# Click somewhere else on the screen to remove your cursor from the SSLPrivateKey field.
# Close SQL Server Enterprise Manager.
# (Optional) Enable SSL if it is not already enabled.
# Reboot the server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key

2011-10-18T22:40:32Z

Cgriffen: /* Exporting the Private Key */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.

== Exporting the Private Key ==

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

==== Procedure ====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

== Copying and Saving the Private Key for Future Use ==

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Copy your PFX file to C:\Program Files\Cisco Systems\MPWeb\DataSvc (on the MPWeb server).
# Open a DOS prompt.
## Click '''Start > Run'''.
## Enter '''cmd'''.
# Enter '''cd Program Files\Cisco Systems\MPWeb\DataSvc'''.
# Enter '''openssl.exe'''.
# Enter '''pkcs12 –in mycertificate.pfx –out mycertificate.pem –nodes'''.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

== Importing the Private Key in to the MPWEB Database ==

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

===== Procedure =====

# Open SQL Server Enterprise Manager.
#: Click '''Start > All Programs > Microsoft SQL Server > Enterprise Manager'''.
# Navigate to the MPWEB database.
#: Click the''' + '''sign next to SQL Server Group > LOCAL > Databases > MPWEB to open the appropriate directory trees.
# Click '''Tables''' in the MPWEB directory.
#: A list of tables opens in the right pane.
# Right-click '''Web''' in the right pane.
# Select '''Open table > Return all rows'''.
#: The Web database table displays.
# Scroll to the right until you see the SSLPrivateKey column.
# Open the PEM file in Notepad.
#: You saved the PEM file when you copied and saved the private key for future use.
# Copy the private key in its entirety.
#: The private key begins with "Begin RSA Private key" and ends with "end RSA private key".
# Paste the private key into the SSLPrivateKey field.
## Click the field before the SSLPrivateKey column.
## Press the Tab key on your keyboard to select all of the data in the SSLPrivateKey field.
## Right-click and select '''Paste''' to paste the value you copied from Notepad.
# Click somewhere else on the screen to remove your cursor from the SSLPrivateKey field.
# Close SQL Server Enterprise Manager.
# (Optional) Enable SSL if it is not already enabled.
# Reboot the server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server

2011-10-18T22:31:20Z

Cgriffen: /* Importing the Private Key in to the MPWEB Database */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

'''Note: ''' This topic does ''not'' apply to deployments in which users schedule meetings from the Cisco WebEx site. For information about Cisco WebEx integration deployments, see the ''Planning Guide for Cisco Unified MeetingPlace'' at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Secure Sockets Layer for the Web Server|How to Configure Secure Sockets Layer for the Web Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Replace an Expired Intermediate Certificate for the Home Page|How to Replace an Expired Intermediate Certificate for the Home Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Replace an Expired Intermediate Certificate for Web Conferencing|How to Replace an Expired Intermediate Certificate for Web Conferencing]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Back Up and Restore the SSL Private Key|How to Back Up and Restore the SSL Private Key]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Allowing Guests to Search Through Public Meetings|Allowing Guests to Search Through Public Meetings]]

== How to Configure Restricted Meeting ID Patterns ==

As a system administrator, you can restrict Cisco Unified MeetingPlace from accepting certain meeting ID patterns that you consider unsecure. For example, you can restrict meeting ID patterns that repeat the same digit three times in a row, such as 111 or 222.

Keep the following points in mind when determining which meeting ID patterns to restrict:
*Restricted meeting ID patterns affect both numerical and vanity meeting IDs. Therefore, if you select to restrict patterns that repeat the same digit three times, Cisco Unified MeetingPlace will disallow both the numerical meeting ID "333" and the vanity meeting ID "deepdive," because "deepdive" translates to 3337383.
*Keep the length of your minimum meeting ID requirement in mind. Repeating the same digit three times when the length of your minimum meeting ID is four digits long can be considered a security risk. However, repeating the same digit three times when the length of your minimum meeting ID is eight digits long may not.
*There is always the chance of a meeting ID hitting the rule pattern and causing a problem. Judicious use of the rule is critical for the reduction of such incidents.
:Specifically, only meeting IDs that schedulers manually enter via the Cisco Unified MeetingPlace web user portal or Microsoft Outlook are immediately checked against the restricted meeting ID patterns that you configure on the Web Server. If a conflict is found, then the scheduler is prompted to enter an unrestricted meeting ID.
:In contrast, the configured restricted meeting ID patterns will cause errors if they conflict with meeting IDs that are entered or generated using one of the following methods:
:*Scheduler leaves the meeting ID field blank, so the system randomly generates the meeting ID.
:*User schedules the meeting via the TUI or Cisco Unified MeetingPlace PhoneView.
:*A reservationless meeting uses the profile number of the meeting owner as the meeting ID.

'''Note: ''' You cannot schedule a meeting with a supported meeting ID pattern through the phone or other scheduling endpoint, then attempt to modify it or reschedule it through the web. This rescheduling behavior is not supported.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Adding Restricted Meeting ID Patterns|Adding Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Deleting Restricted Meeting ID Patterns|Deleting Restricted Meeting ID Patterns]]

=== Adding Restricted Meeting ID Patterns ===

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Restricted Meeting ID Patterns'''.
# For Pattern, enter the restricted meeting ID pattern as a regular expression using the Perl syntax.
#:<tt> Example: .*(012|123|234|345|456|567|678|789|890|098|987|876|765|654|543|432|321|210).* </tt>
# Enter a brief description to explain the intent of the pattern in the field provided.
#:<tt> Example: Block sequences of 3 increasing or decreasing numbers. </tt>
# Select '''Add'''.
#: The pattern displays in the "View" section of the page.
# Repeat Step 4 through Step 6 for each additional restricted ID pattern.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Restricting the Use of Vanity Meeting IDs|Restricting the Use of Vanity Meeting IDs]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module

=== Deleting Restricted Meeting ID Patterns ===

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Restricted Meeting ID Patterns'''.
# Scroll down to the "View" section of the screen.
# Locate the pattern you want to delete.
# Select '''Delete'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Restricting the Use of Vanity Meeting IDs|Restricting the Use of Vanity Meeting IDs]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module

== How to Configure Secure Sockets Layer for the Web Server ==

Secure Sockets Layer (SSL) secures information by encrypting the data for travel across the network. Complete the following procedures in the order shown to configure SSL.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Restrictions for Configuring Secure Sockets Layer|Restrictions for Configuring Secure Sockets Layer]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Changing the Web Server Hostname From an IP Address to a Hostname|Changing the Web Server Hostname From an IP Address to a Hostname]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Testing the Web Server Over an HTTPS Connection|Testing the Web Server Over an HTTPS Connection]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#(Optional) Disabling Support for Low Encryption Ciphers and SSL v2|(Optional) Disabling Support for Low Encryption Ciphers and SSL v2]]

=== Restrictions for Configuring Secure Sockets Layer ===
* If you are using SSL on an external Web Server, make sure that the hostname on the SSL certificate resolves to the external Web Server IP address.
* If you are using SSL on a system with a segmented DNS, make sure that the hostname on the SSL certificate differs from the segmented DNS name.
* Self-signed certificates are not supported.
* Make sure that the Hostname [Home Page] field value is a hostname, not an IP address.
: The same restriction applies to the Hostname [Web Conferencing] field, which appears only if you upgraded from Release 7.0 to Release 8.0.
* If users will access your Web Server through a firewall, make sure that TCP port 443 is open inbound on your firewall for both of the hostnames or IP addresses on your server.
* You can use SSL on any Web Server (internal or DMZ); however, you cannot use or configure WIA (Windows Integrated Authentication) on that server.
* We do not support SSL certificates that require a key stronger than 1024 bits.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Secure Sockets Layer for the Web Server|How to Configure Secure Sockets Layer for the Web Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Authentication for the Cisco Unified MeetingPlace Web Server#Windows Integrated Authentication|Windows Integrated Authentication]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Authentication for the Cisco Unified MeetingPlace Web Server#Configuring User Authentication for the Cisco Unified MeetingPlace Web Server|Configuring User Authentication for the Cisco Unified MeetingPlace Web Server]] module

=== Changing the Web Server Hostname From an IP Address to a Hostname ===

The Web Server hostname was populated during the Cisco Unified MeetingPlace Web Server software installation. The Hostname [Home Page] was assigned the first IP address in the operating system. If you upgraded from Release 7.0 to Release 8.0, then the Hostname [Web Conferencing] was assigned the second IP address in the operating system.

You should not need to redefine these unless either of the following applies:
* You want users to be able to access the Cisco Unified MeetingPlace Web Server by using the fully qualified domain name (FQDN) of the server or
* You plan to configure SSL for this server. If enabling SSL, you must use hostnames rather than IP addresses.

===== Before You Begin =====

This procedure assumes that you have already installed the Cisco Unified MeetingPlace Web Server software.

===== Restrictions =====

Do not perform this procedure if the Web Server is not in a Domain Name Server (DNS).

===== Procedure =====

# Open your web browser and enter the URL of your Web Server.
#* For internal Web Servers, the default URL structure is '''http://'''''server'', where ''server'' is the name of your internal Web Server.
#* For external (DMZ) Web Servers, you can only access the administration pages from the server box itself and only through port 8002. If you try to access the administration pages on the external Web Server by using http://''server''/mpweb/admin/, the system will display a 404 "Page Not Found" error.
#: To access the administration pages for the external (DMZ) server, you must be on the web server box and enter the following URL: '''http://localhost:8002/mpweb/admin/'''
#: '''Note: ''' If SSL is enabled on your system, you must still enter the URL with http and not https.
#: The system automatically signs you in using the preconfigured ''admin'' profile.
# Sign in to the web user portal.
# Select '''Admin''' if you are not already on the Cisco Unified MeetingPlace Web Administration page.
# Select '''Web Server'''.
# Scroll down to the "View" section of the page.
# Select the name of the Web Server that you want to configure.
#:Information about this Web Server populates the "Edit" section of the page.
# For Hostname [Home Page], enter the fully qualified domain name (FQDN) of the primary network interface on the Web Server.
#:<tt> Example: hostname.domain.com. </tt>
#: '''Note: ''' This hostname must be resolvable by its intended users.
# For Hostname [Web Conferencing], enter the FQDN of the secondary network interface on the Web Server.
#:<tt> Example: hostnamewc.domain.com. </tt>
#: '''Note: ''' This field appears only if you upgraded from Release 7.0 to Release 8.0.
#: '''Note: ''' This hostname must be different from that used for Hostname [Home Page]. It must be resolvable by its intended users. Depending on your hostname choice, the hostnames might not have been automatically registered with the DNS during the OS installation. We recommend that you check the DNS, both the forward and reverse lookup zones, and add entries manually if needed.
# Select '''Submit'''.
# (Optional) If you are working on a Windows system with Internet Explorer, select '''Test Server Configuration'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings#Signing In to the Cisco Unified MeetingPlace Web Administration|Signing In to the Cisco Unified MeetingPlace Web Administration]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings#Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings|Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Field Reference: Web Server Specific Fields|Field Reference: Web Server Specific Fields]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Web Administration References for Cisco Unified MeetingPlace|Web Administration References for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting the Cisco Unified MeetingPlace Web Server#How to Resolve Test Server Configuration Problems|How to Resolve Test Server Configuration Problems]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting the Cisco Unified MeetingPlace Web Server#Troubleshooting the Cisco Unified MeetingPlace Web Server|Troubleshooting the Cisco Unified MeetingPlace Web Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#How to Switch the Order of IP Addresses on the Web Server|How to Switch the Order of IP Addresses on the Web Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server|Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server]] module

===== What to Do Next =====
* If you changed the Hostname [Web Conferencing] field, then you must restart the Cisco Unified MeetingPlace Web Master Service for the field change to take effect. See the [[Cisco Unified MeetingPlace Release 8.0 -- Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service#Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service|Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service]] module.
* If you are configuring SSL, proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]].

=== Creating a New Certificate Signing Request and Obtaining a Certificate File ===

Use the SSL/TLS configuration page to generate certificate signing requests to send to an authorized Certificate Authority in order to apply for digital identity certificates. You need a certificate for the Home Page hostname. If you upgraded from Release 7.0 to Release 8.0, then you also need a certificate for the Web Conferencing hostname.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Changing the Web Server Hostname From an IP Address to a Hostname|Changing the Web Server Hostname From an IP Address to a Hostname]].

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''SSL/TLS'''.
# Select the '''Edit''' icon for the Web Conferencing hostname.
# Enter your company name and organization unit/department in the applicable fields.
# Enter the complete, official names of your city/locality and state/province in the applicable fields.
#: '''Note: ''' Do not use abbreviations.
# Select your country/region.
# Select '''Generate Request'''.
#: The new certificate signing request (CSR) displays in the text box. The request is signed with an auto-generated private key.
# Select the '''Private Key''' link to see the value of the private key.
# Copy the contents of the CSR text box to a text file and send this file to your certificate provider in return for a certificate file.
#:'''Caution! ''' If your certificate provider asks for your server type, specify Apache or Custom, not Microsoft or IIS. If you attempt to install a Microsoft or IIS certificate by using the SSL/TLS configuration pages, the Cisco Unified MeetingPlace Web Server software will not restart when you attempt to reboot the system. Instead it will log an error about the certificate and disable SSL so that you can restart and fix the problem.
# Select '''Back''' to return to the main Administration page.
# Repeat Step 3 through Step 11 for the Web Conferencing hostname.

===== What to Do Next =====

When you receive the .cer file from your certificate provider, proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]].

=== Applying the SSL Certificate ===

When you receive the certificate from your certificate provider, apply the certificate to the Cisco Unified MeetingPlace website by completing the following procedure.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]].

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''SSL/TLS'''.
# Select the '''Edit''' icon for the Web Conferencing hostname.
# Open the certificate file for the Web Conferencing hostname in a text editor, and copy the text to the clipboard.
# In the text box at the bottom of the page, paste the text from the certificate you obtained for this hostname.
#: Make sure the text you paste includes the begin and end certificate delimiters.
# Select '''Install Certificate'''.
#: The host is now set up with a certificate.
# Select '''Back''' to return to the main Administration page.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]].

=== Enabling SSL ===

Complete this procedure to enable the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Require SSL|Require SSL]] field on the Web Server administration page.

===== Before You Begin =====
* Complete Applying the SSL Certificate.
* Make sure that you are still on the SSL/TLS page.

===== Procedure =====

#Select '''Toggle SSL''' to turn SSL on.
#Select '''Reboot Server'''.
::The server shuts down and restarts.
::'''Note: ''' If the Web Server cannot validate the SSL certificates, the server will log an error and toggle SSL to off. In this case, you will need to restart the Cisco Unified MeetingPlace Web Master Service and fix the issue, then repeat the steps in this procedure.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service#Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service|Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service]] module

===== What to do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Testing the Web Server Over an HTTPS Connection|Testing the Web Server Over an HTTPS Connection]].

=== Testing the Web Server Over an HTTPS Connection ===

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]].

===== Procedure =====

# Use a web browser to connect to https://hostname.domain.com, the Fully Qualified Domain Name, of the Web Server.
#* If the Cisco Unified MeetingPlace home page displays, the connection to the Home Page hostname is successful.
#* If any security warning dialog boxes appear, configure SSL not to show the dialog boxes.
#*: For detailed information, see Microsoft Knowledge Base Articles 813618 and 257873 on the Microsoft website.
# If your system was upgraded from Release 7.0 to Release 8.0, then complete these steps to test the connection to the Web Conferencing hostname:
## Find a meeting that meets the following conditions:
##* Meeting occurred before the upgrade from Release 7.0 to Release 8.0.
##* The meeting has a recording.
## Verify that you can access and play the meeting recording.

===== Related Topics =====
* For information about finding meetings and playing recordings, see the ''User Guide for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_user_guide_list.html.

=== (Optional) Disabling Support for Low Encryption Ciphers and SSL v2 ===

Cisco authorizes Cisco Unified MeetingPlace customers to disable the support for low encryption ciphers and SSL v2 on their Cisco Unified MeetingPlace Web Servers based on their security requirements.

You must assume all work related to this security hardening as well as the operational consequences of this security lock-down, including the fact that some end-users might be unable to use the Cisco Unified MeetingPlace Web Servers because of incompatible browsers/ client SSL implementation, or encryption strength limitations.

To perform this lock-down for the Microsoft IIS web server component used by Cisco Unified MeetingPlace, see the following Microsoft Knowledge Base articles:

How to Control the Ciphers for SSL and TLS on IIS (IIS restart required): http://support.microsoft.com/default.aspx?scid=KB;en-us;q216482

How to Restrict the Use of Certain Cryptographic Algorithms and Protocols in Schannel.dll (Windows restart required): http://support.microsoft.com/default.aspx?scid=kb;EN-US;245030

How to disable PCT 1.0, SSL 2.0, SSL 3.0, or TLS 1.0 in Internet Information Services (Windows restart required): http://support.microsoft.com/default.aspx?scid=kb;en-us;187498

To perform this lock-down for the Adobe Connect application web server used by Cisco Unified MeetingPlace Web Conferencing, see the following Adobe article: http://livedocs.adobe.com/fms/2/docs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Parts&file=00000300.html

'''Note: ''' You can find the Server.xml file that contains the SSLCipherSuite tag to be edited in the following folder on the Cisco Unified MeetingPlace Web Server: C:\Program Files\Cisco Systems\MPWeb\WebConf\comserv\win32\conf

'''Caution! ''' Any upgrade of the Cisco Unified MeetingPlace Web Server software with a maintenance release will overwrite the changes that you have made in Server.xml. These changes must be re-applied after the upgrade.

== How to Replace an Expired Intermediate Certificate for the Home Page ==

'''Note: ''' As of April 2006, all SSL certificates issued by VeriSign require the installation of an intermediate Certificate Authority (CA) certificate. The SSL certificates are signed by an intermediate CA using a two-tier hierarchy (also known as trust chain) which enhances the security of SSL certificates.

For more information, go to: https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR657&actp=RELATED_RESOURCE.

Topics in this section include:
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Downloading the Updated VeriSign Intermediate CA|Downloading the Updated VeriSign Intermediate CA]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a Certificate Snap-In|Creating a Certificate Snap-In]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Removing the Expired Intermediate CA|Removing the Expired Intermediate CA]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Installing the New Intermediate CA|Installing the New Intermediate CA]]

=== Downloading the Updated VeriSign Intermediate CA ===

When downloading the intermediate CA certificate, ensure that you select the appropriate one for your SSL certificate: either Secure Site with EV Certificates (Secure Server) or Secure Site Pro with EV Certificates (Global).

===== Procedure =====

# If you are not sure which certificate you have purchased, follow these steps:
## Go to VeriSign Search Certificates page.
## Type your Common Name or Order Number.
## Select Search.
## Select the certificate name for your certificate.
# Go to the VeriSign intermediate CA certificates web page and select the CA certificate for your product.
# Copy and paste the contents into a text (Notepad) file.
# Save the file as newintermediate.cer.

=== Creating a Certificate Snap-In ===

===== Procedure =====

# From the Web server, select '''Start > Run'''.
# In the text box, type '''mmc'''.
# Select '''OK'''.
# For IIS 5.0: From the Microsoft Management Console (MMC) menu bar, select '''Console > Add/Remove Snap-in'''.
# For IIS 6.0: From the Microsoft Management Console (MMC) menu bar, select '''File > Add/Remove Snap-in'''.
# Select '''Add'''.
# From the list of snap-ins, select '''Certificates'''.
# Select '''Add'''.
# Select '''Computer account'''.
# Select '''Next'''.
# Select '''Local computer''' (the computer this console is running on).
# Select '''Finish'''.
# In the snap-in list window, select '''Close'''.
# In the Add/Remove Snap-in window, select '''OK'''.
# Save these console settings for future use.

=== Removing the Expired Intermediate CA ===

===== Procedure =====

# From the left pane, double-click '''Certificate (Local Computer)'''.
# Select '''Intermediate Certification Authorities > Certificates'''.
# Locate the certificate issued to www.verisign.com/CPS Incorp.by Ref.LIABILITY LTD. (C)97 VeriSign (expiration date of 1/7/2004).
# Right-click the certificate.
# Select '''Delete'''.
# From the left pane, select '''Trusted Root Certification Authorities > Certificates'''.
# Locate the certificate issued to Class 3 Public Primary Certification Authority (expiration date of 1/7/2004).
# Right-click the certificate.
# Select '''Delete'''.

=== Installing the New Intermediate CA ===

===== Procedure =====

# From the left pane, select '''Intermediate Certification Authorities'''.
# Right-click '''Certificates'''.
# Select '''All Tasks > Import'''.
# At the Certificate Import Wizard, select '''Next'''.
# Select the Intermediate CA Certificate file.
# Select '''Next'''.
# Select '''Place all certificate in the following store: Intermediate Certification Authorities'''.
# Select '''Next'''.
# Select '''Finish'''.
# Restart the Web Server.
#: If this does not resolve the issue, then physically reboot the Web Server. The Web Server should now only have one Intermediate CA that expires in 2016.

== How to Replace an Expired Intermediate Certificate for Web Conferencing ==

This topic applies only if you upgraded from Release 7.0 to Release 8.0.

'''Note: ''' As of April 2006, all SSL certificates issued by VeriSign require the installation of an intermediate Certificate Authority (CA) certificate. The SSL certificates are signed by an intermediate CA using a two-tier hierarchy (also known as trust chain) which enhances the security of SSL certificates.

For more information, go to: https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR657&actp=RELATED_RESOURCE.

# Follow the steps in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Downloading the Updated VeriSign Intermediate CA|Downloading the Updated VeriSign Intermediate CA]].
#: In that procedure, you copied the contents of the intermediate CA certificate into a file called newintermediate.cer.
# Follow the steps in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]].
# When prompted to copy the certificate, copy the text from file called newintermediate.cer.
# Add the intermediate certificate provided by your certificate authority provider to the SSL certificate PEM files.

'''Note: ''' When pasting these two certificates within the same PEM file, the order of these certificates matters. The signed server certificate has to be pasted first and then the intermediate certificate should be pasted below the signed server certificate. Be careful when pasting these certificates into the file as extra spaces or dashes can cause problems with the certificate file. Once you make the changes, restart Flash Communication services and the Breeze Application service.

== How to Back Up and Restore the SSL Private Key ==

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Importing the Private Key in to the MPWEB Database|Importing the Private Key in to the MPWEB Database]]

=== Exporting the Private Key ===

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

===== Procedure =====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

=== Copying and Saving the Private Key for Future Use ===

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Open a DOS prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
# Enter the path to your desktop in the cmd.exe window.
#:<tt> Example: C:\> cd "Documents and Settings\Administrator\Desktop" </tt>
# Enter the full path to OpenSSL.exe keeping the following in mind:
#* After -in, enter the full path to where you placed the file when you exported the private key.
#* After -out, enter the full path to where you want to send the exported file.
#*:<tt> Example:C:\Documents and Settings\Administrator\Desktop>"\Program Files\Cisco Systems\MPWeb\DataSvc\openssl.exe" pkcs12 -in "\Documents and Settings\Administrator\Desktop\mycertificate.pfx" -out "\Documents and Settings\Administrator\Desktop\mycertificate.pem" -nodes </tt>
#: This converts the PFX format to a PEM format. The mycertificate.pem file will have all the certificates starting with the Private key.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]]

=== Importing the Private Key in to the MPWEB Database ===

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].
* Back up the complete database before performing this procedure.

===== Procedure =====

# Open the SQL Query Analyzer.
# Select '''Start > All Programs > Microsoft SQL Server > Query Analyzer'''.
# Log in with your SQL username, ”sa,” and password (which you set during the installation of MPWeb).
# Type in the following commands:
#:* '''use mpweb'''
#:* '''update web'''
#:* '''set sslprivatekey='Your private key' '''
# Your private key begins with “BEGIN RSA PRIVATE KEY” and ends with “END RSA PRIVATE KEY”. Copy your private key and paste it between the quotes. You can find your Private key in your PEM file that you saved when you copied and saved the private key for future use.
#: '''Note''': Make sure you include the quotation marks.
# Select the green arrow to Execute Query.
# Determine if your Private Key insertion was successful by entering the following commands in the Query Analyzer window:
#:* '''use mpweb'''
#:* '''select sslprivatekey from web'''
# Select the green arrow to Execute Query and your private key appears the following window.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]]

=== About Home Page and Web Conf SSL certificates ===

When you import the private key using SQL query Analyzer enable SSL by performing the procedure described in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]] section.

===== Procedure =====

# Change the web server hostname from an IP Address to a hostname.
# Apply the SSL certificate.
# Enable SSL.

== Allowing Guests to Search Through Public Meetings ==

Guest users have fewer privileges than users who sign in with their profiles. Complete this procedure to allow guests to search through public meetings.

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Web Server'''.
# Scroll down to the "View" section of the page.
# Select the name of the Web Server that you want to configure.
#: Information about this server populates the "Edit" section of the page.
# Select '''Yes''' for Allow Public Meetings in Find Meeting List.
# Select '''Yes''' for Allow Guest Access to Find Meetings Page.
# Select '''Submit'''.

'''Tip: ''' To allow external users (those outside your firewall) and sites (Cisco Unified MeetingPlace systems outside your network) to access a meeting and the associated meeting materials, make sure that Allow External Web Participants is set to Yes for the meeting. This parameter is set by the meeting scheduler from the New Meeting scheduling page, and it is only visible if your Cisco Unified MeetingPlace system has an external site-that is, a Web Server located in an Internet-accessible segment of your network, such as in a DMZ zone.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Field Reference: Web Server Customization Values|Field Reference: Web Server Customization Values]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Web Administration References for Cisco Unified MeetingPlace|Web Administration References for Cisco Unified MeetingPlace]] module

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server

2011-10-18T22:13:50Z

Cgriffen: /* Importing the Private Key in to the MPWEB Database */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

'''Note: ''' This topic does ''not'' apply to deployments in which users schedule meetings from the Cisco WebEx site. For information about Cisco WebEx integration deployments, see the ''Planning Guide for Cisco Unified MeetingPlace'' at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Secure Sockets Layer for the Web Server|How to Configure Secure Sockets Layer for the Web Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Replace an Expired Intermediate Certificate for the Home Page|How to Replace an Expired Intermediate Certificate for the Home Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Replace an Expired Intermediate Certificate for Web Conferencing|How to Replace an Expired Intermediate Certificate for Web Conferencing]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Back Up and Restore the SSL Private Key|How to Back Up and Restore the SSL Private Key]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Allowing Guests to Search Through Public Meetings|Allowing Guests to Search Through Public Meetings]]

== How to Configure Restricted Meeting ID Patterns ==

As a system administrator, you can restrict Cisco Unified MeetingPlace from accepting certain meeting ID patterns that you consider unsecure. For example, you can restrict meeting ID patterns that repeat the same digit three times in a row, such as 111 or 222.

Keep the following points in mind when determining which meeting ID patterns to restrict:
*Restricted meeting ID patterns affect both numerical and vanity meeting IDs. Therefore, if you select to restrict patterns that repeat the same digit three times, Cisco Unified MeetingPlace will disallow both the numerical meeting ID "333" and the vanity meeting ID "deepdive," because "deepdive" translates to 3337383.
*Keep the length of your minimum meeting ID requirement in mind. Repeating the same digit three times when the length of your minimum meeting ID is four digits long can be considered a security risk. However, repeating the same digit three times when the length of your minimum meeting ID is eight digits long may not.
*There is always the chance of a meeting ID hitting the rule pattern and causing a problem. Judicious use of the rule is critical for the reduction of such incidents.
:Specifically, only meeting IDs that schedulers manually enter via the Cisco Unified MeetingPlace web user portal or Microsoft Outlook are immediately checked against the restricted meeting ID patterns that you configure on the Web Server. If a conflict is found, then the scheduler is prompted to enter an unrestricted meeting ID.
:In contrast, the configured restricted meeting ID patterns will cause errors if they conflict with meeting IDs that are entered or generated using one of the following methods:
:*Scheduler leaves the meeting ID field blank, so the system randomly generates the meeting ID.
:*User schedules the meeting via the TUI or Cisco Unified MeetingPlace PhoneView.
:*A reservationless meeting uses the profile number of the meeting owner as the meeting ID.

'''Note: ''' You cannot schedule a meeting with a supported meeting ID pattern through the phone or other scheduling endpoint, then attempt to modify it or reschedule it through the web. This rescheduling behavior is not supported.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Adding Restricted Meeting ID Patterns|Adding Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Deleting Restricted Meeting ID Patterns|Deleting Restricted Meeting ID Patterns]]

=== Adding Restricted Meeting ID Patterns ===

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Restricted Meeting ID Patterns'''.
# For Pattern, enter the restricted meeting ID pattern as a regular expression using the Perl syntax.
#:<tt> Example: .*(012|123|234|345|456|567|678|789|890|098|987|876|765|654|543|432|321|210).* </tt>
# Enter a brief description to explain the intent of the pattern in the field provided.
#:<tt> Example: Block sequences of 3 increasing or decreasing numbers. </tt>
# Select '''Add'''.
#: The pattern displays in the "View" section of the page.
# Repeat Step 4 through Step 6 for each additional restricted ID pattern.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Restricting the Use of Vanity Meeting IDs|Restricting the Use of Vanity Meeting IDs]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module

=== Deleting Restricted Meeting ID Patterns ===

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Restricted Meeting ID Patterns'''.
# Scroll down to the "View" section of the screen.
# Locate the pattern you want to delete.
# Select '''Delete'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Restricting the Use of Vanity Meeting IDs|Restricting the Use of Vanity Meeting IDs]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module

== How to Configure Secure Sockets Layer for the Web Server ==

Secure Sockets Layer (SSL) secures information by encrypting the data for travel across the network. Complete the following procedures in the order shown to configure SSL.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Restrictions for Configuring Secure Sockets Layer|Restrictions for Configuring Secure Sockets Layer]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Changing the Web Server Hostname From an IP Address to a Hostname|Changing the Web Server Hostname From an IP Address to a Hostname]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Testing the Web Server Over an HTTPS Connection|Testing the Web Server Over an HTTPS Connection]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#(Optional) Disabling Support for Low Encryption Ciphers and SSL v2|(Optional) Disabling Support for Low Encryption Ciphers and SSL v2]]

=== Restrictions for Configuring Secure Sockets Layer ===
* If you are using SSL on an external Web Server, make sure that the hostname on the SSL certificate resolves to the external Web Server IP address.
* If you are using SSL on a system with a segmented DNS, make sure that the hostname on the SSL certificate differs from the segmented DNS name.
* Self-signed certificates are not supported.
* Make sure that the Hostname [Home Page] field value is a hostname, not an IP address.
: The same restriction applies to the Hostname [Web Conferencing] field, which appears only if you upgraded from Release 7.0 to Release 8.0.
* If users will access your Web Server through a firewall, make sure that TCP port 443 is open inbound on your firewall for both of the hostnames or IP addresses on your server.
* You can use SSL on any Web Server (internal or DMZ); however, you cannot use or configure WIA (Windows Integrated Authentication) on that server.
* We do not support SSL certificates that require a key stronger than 1024 bits.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Secure Sockets Layer for the Web Server|How to Configure Secure Sockets Layer for the Web Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Authentication for the Cisco Unified MeetingPlace Web Server#Windows Integrated Authentication|Windows Integrated Authentication]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Authentication for the Cisco Unified MeetingPlace Web Server#Configuring User Authentication for the Cisco Unified MeetingPlace Web Server|Configuring User Authentication for the Cisco Unified MeetingPlace Web Server]] module

=== Changing the Web Server Hostname From an IP Address to a Hostname ===

The Web Server hostname was populated during the Cisco Unified MeetingPlace Web Server software installation. The Hostname [Home Page] was assigned the first IP address in the operating system. If you upgraded from Release 7.0 to Release 8.0, then the Hostname [Web Conferencing] was assigned the second IP address in the operating system.

You should not need to redefine these unless either of the following applies:
* You want users to be able to access the Cisco Unified MeetingPlace Web Server by using the fully qualified domain name (FQDN) of the server or
* You plan to configure SSL for this server. If enabling SSL, you must use hostnames rather than IP addresses.

===== Before You Begin =====

This procedure assumes that you have already installed the Cisco Unified MeetingPlace Web Server software.

===== Restrictions =====

Do not perform this procedure if the Web Server is not in a Domain Name Server (DNS).

===== Procedure =====

# Open your web browser and enter the URL of your Web Server.
#* For internal Web Servers, the default URL structure is '''http://'''''server'', where ''server'' is the name of your internal Web Server.
#* For external (DMZ) Web Servers, you can only access the administration pages from the server box itself and only through port 8002. If you try to access the administration pages on the external Web Server by using http://''server''/mpweb/admin/, the system will display a 404 "Page Not Found" error.
#: To access the administration pages for the external (DMZ) server, you must be on the web server box and enter the following URL: '''http://localhost:8002/mpweb/admin/'''
#: '''Note: ''' If SSL is enabled on your system, you must still enter the URL with http and not https.
#: The system automatically signs you in using the preconfigured ''admin'' profile.
# Sign in to the web user portal.
# Select '''Admin''' if you are not already on the Cisco Unified MeetingPlace Web Administration page.
# Select '''Web Server'''.
# Scroll down to the "View" section of the page.
# Select the name of the Web Server that you want to configure.
#:Information about this Web Server populates the "Edit" section of the page.
# For Hostname [Home Page], enter the fully qualified domain name (FQDN) of the primary network interface on the Web Server.
#:<tt> Example: hostname.domain.com. </tt>
#: '''Note: ''' This hostname must be resolvable by its intended users.
# For Hostname [Web Conferencing], enter the FQDN of the secondary network interface on the Web Server.
#:<tt> Example: hostnamewc.domain.com. </tt>
#: '''Note: ''' This field appears only if you upgraded from Release 7.0 to Release 8.0.
#: '''Note: ''' This hostname must be different from that used for Hostname [Home Page]. It must be resolvable by its intended users. Depending on your hostname choice, the hostnames might not have been automatically registered with the DNS during the OS installation. We recommend that you check the DNS, both the forward and reverse lookup zones, and add entries manually if needed.
# Select '''Submit'''.
# (Optional) If you are working on a Windows system with Internet Explorer, select '''Test Server Configuration'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings#Signing In to the Cisco Unified MeetingPlace Web Administration|Signing In to the Cisco Unified MeetingPlace Web Administration]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings#Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings|Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Field Reference: Web Server Specific Fields|Field Reference: Web Server Specific Fields]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Web Administration References for Cisco Unified MeetingPlace|Web Administration References for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting the Cisco Unified MeetingPlace Web Server#How to Resolve Test Server Configuration Problems|How to Resolve Test Server Configuration Problems]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting the Cisco Unified MeetingPlace Web Server#Troubleshooting the Cisco Unified MeetingPlace Web Server|Troubleshooting the Cisco Unified MeetingPlace Web Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#How to Switch the Order of IP Addresses on the Web Server|How to Switch the Order of IP Addresses on the Web Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server|Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server]] module

===== What to Do Next =====
* If you changed the Hostname [Web Conferencing] field, then you must restart the Cisco Unified MeetingPlace Web Master Service for the field change to take effect. See the [[Cisco Unified MeetingPlace Release 8.0 -- Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service#Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service|Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service]] module.
* If you are configuring SSL, proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]].

=== Creating a New Certificate Signing Request and Obtaining a Certificate File ===

Use the SSL/TLS configuration page to generate certificate signing requests to send to an authorized Certificate Authority in order to apply for digital identity certificates. You need a certificate for the Home Page hostname. If you upgraded from Release 7.0 to Release 8.0, then you also need a certificate for the Web Conferencing hostname.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Changing the Web Server Hostname From an IP Address to a Hostname|Changing the Web Server Hostname From an IP Address to a Hostname]].

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''SSL/TLS'''.
# Select the '''Edit''' icon for the Web Conferencing hostname.
# Enter your company name and organization unit/department in the applicable fields.
# Enter the complete, official names of your city/locality and state/province in the applicable fields.
#: '''Note: ''' Do not use abbreviations.
# Select your country/region.
# Select '''Generate Request'''.
#: The new certificate signing request (CSR) displays in the text box. The request is signed with an auto-generated private key.
# Select the '''Private Key''' link to see the value of the private key.
# Copy the contents of the CSR text box to a text file and send this file to your certificate provider in return for a certificate file.
#:'''Caution! ''' If your certificate provider asks for your server type, specify Apache or Custom, not Microsoft or IIS. If you attempt to install a Microsoft or IIS certificate by using the SSL/TLS configuration pages, the Cisco Unified MeetingPlace Web Server software will not restart when you attempt to reboot the system. Instead it will log an error about the certificate and disable SSL so that you can restart and fix the problem.
# Select '''Back''' to return to the main Administration page.
# Repeat Step 3 through Step 11 for the Web Conferencing hostname.

===== What to Do Next =====

When you receive the .cer file from your certificate provider, proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]].

=== Applying the SSL Certificate ===

When you receive the certificate from your certificate provider, apply the certificate to the Cisco Unified MeetingPlace website by completing the following procedure.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]].

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''SSL/TLS'''.
# Select the '''Edit''' icon for the Web Conferencing hostname.
# Open the certificate file for the Web Conferencing hostname in a text editor, and copy the text to the clipboard.
# In the text box at the bottom of the page, paste the text from the certificate you obtained for this hostname.
#: Make sure the text you paste includes the begin and end certificate delimiters.
# Select '''Install Certificate'''.
#: The host is now set up with a certificate.
# Select '''Back''' to return to the main Administration page.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]].

=== Enabling SSL ===

Complete this procedure to enable the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Require SSL|Require SSL]] field on the Web Server administration page.

===== Before You Begin =====
* Complete Applying the SSL Certificate.
* Make sure that you are still on the SSL/TLS page.

===== Procedure =====

#Select '''Toggle SSL''' to turn SSL on.
#Select '''Reboot Server'''.
::The server shuts down and restarts.
::'''Note: ''' If the Web Server cannot validate the SSL certificates, the server will log an error and toggle SSL to off. In this case, you will need to restart the Cisco Unified MeetingPlace Web Master Service and fix the issue, then repeat the steps in this procedure.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service#Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service|Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service]] module

===== What to do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Testing the Web Server Over an HTTPS Connection|Testing the Web Server Over an HTTPS Connection]].

=== Testing the Web Server Over an HTTPS Connection ===

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]].

===== Procedure =====

# Use a web browser to connect to https://hostname.domain.com, the Fully Qualified Domain Name, of the Web Server.
#* If the Cisco Unified MeetingPlace home page displays, the connection to the Home Page hostname is successful.
#* If any security warning dialog boxes appear, configure SSL not to show the dialog boxes.
#*: For detailed information, see Microsoft Knowledge Base Articles 813618 and 257873 on the Microsoft website.
# If your system was upgraded from Release 7.0 to Release 8.0, then complete these steps to test the connection to the Web Conferencing hostname:
## Find a meeting that meets the following conditions:
##* Meeting occurred before the upgrade from Release 7.0 to Release 8.0.
##* The meeting has a recording.
## Verify that you can access and play the meeting recording.

===== Related Topics =====
* For information about finding meetings and playing recordings, see the ''User Guide for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_user_guide_list.html.

=== (Optional) Disabling Support for Low Encryption Ciphers and SSL v2 ===

Cisco authorizes Cisco Unified MeetingPlace customers to disable the support for low encryption ciphers and SSL v2 on their Cisco Unified MeetingPlace Web Servers based on their security requirements.

You must assume all work related to this security hardening as well as the operational consequences of this security lock-down, including the fact that some end-users might be unable to use the Cisco Unified MeetingPlace Web Servers because of incompatible browsers/ client SSL implementation, or encryption strength limitations.

To perform this lock-down for the Microsoft IIS web server component used by Cisco Unified MeetingPlace, see the following Microsoft Knowledge Base articles:

How to Control the Ciphers for SSL and TLS on IIS (IIS restart required): http://support.microsoft.com/default.aspx?scid=KB;en-us;q216482

How to Restrict the Use of Certain Cryptographic Algorithms and Protocols in Schannel.dll (Windows restart required): http://support.microsoft.com/default.aspx?scid=kb;EN-US;245030

How to disable PCT 1.0, SSL 2.0, SSL 3.0, or TLS 1.0 in Internet Information Services (Windows restart required): http://support.microsoft.com/default.aspx?scid=kb;en-us;187498

To perform this lock-down for the Adobe Connect application web server used by Cisco Unified MeetingPlace Web Conferencing, see the following Adobe article: http://livedocs.adobe.com/fms/2/docs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Parts&file=00000300.html

'''Note: ''' You can find the Server.xml file that contains the SSLCipherSuite tag to be edited in the following folder on the Cisco Unified MeetingPlace Web Server: C:\Program Files\Cisco Systems\MPWeb\WebConf\comserv\win32\conf

'''Caution! ''' Any upgrade of the Cisco Unified MeetingPlace Web Server software with a maintenance release will overwrite the changes that you have made in Server.xml. These changes must be re-applied after the upgrade.

== How to Replace an Expired Intermediate Certificate for the Home Page ==

'''Note: ''' As of April 2006, all SSL certificates issued by VeriSign require the installation of an intermediate Certificate Authority (CA) certificate. The SSL certificates are signed by an intermediate CA using a two-tier hierarchy (also known as trust chain) which enhances the security of SSL certificates.

For more information, go to: https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR657&actp=RELATED_RESOURCE.

Topics in this section include:
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Downloading the Updated VeriSign Intermediate CA|Downloading the Updated VeriSign Intermediate CA]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a Certificate Snap-In|Creating a Certificate Snap-In]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Removing the Expired Intermediate CA|Removing the Expired Intermediate CA]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Installing the New Intermediate CA|Installing the New Intermediate CA]]

=== Downloading the Updated VeriSign Intermediate CA ===

When downloading the intermediate CA certificate, ensure that you select the appropriate one for your SSL certificate: either Secure Site with EV Certificates (Secure Server) or Secure Site Pro with EV Certificates (Global).

===== Procedure =====

# If you are not sure which certificate you have purchased, follow these steps:
## Go to VeriSign Search Certificates page.
## Type your Common Name or Order Number.
## Select Search.
## Select the certificate name for your certificate.
# Go to the VeriSign intermediate CA certificates web page and select the CA certificate for your product.
# Copy and paste the contents into a text (Notepad) file.
# Save the file as newintermediate.cer.

=== Creating a Certificate Snap-In ===

===== Procedure =====

# From the Web server, select '''Start > Run'''.
# In the text box, type '''mmc'''.
# Select '''OK'''.
# For IIS 5.0: From the Microsoft Management Console (MMC) menu bar, select '''Console > Add/Remove Snap-in'''.
# For IIS 6.0: From the Microsoft Management Console (MMC) menu bar, select '''File > Add/Remove Snap-in'''.
# Select '''Add'''.
# From the list of snap-ins, select '''Certificates'''.
# Select '''Add'''.
# Select '''Computer account'''.
# Select '''Next'''.
# Select '''Local computer''' (the computer this console is running on).
# Select '''Finish'''.
# In the snap-in list window, select '''Close'''.
# In the Add/Remove Snap-in window, select '''OK'''.
# Save these console settings for future use.

=== Removing the Expired Intermediate CA ===

===== Procedure =====

# From the left pane, double-click '''Certificate (Local Computer)'''.
# Select '''Intermediate Certification Authorities > Certificates'''.
# Locate the certificate issued to www.verisign.com/CPS Incorp.by Ref.LIABILITY LTD. (C)97 VeriSign (expiration date of 1/7/2004).
# Right-click the certificate.
# Select '''Delete'''.
# From the left pane, select '''Trusted Root Certification Authorities > Certificates'''.
# Locate the certificate issued to Class 3 Public Primary Certification Authority (expiration date of 1/7/2004).
# Right-click the certificate.
# Select '''Delete'''.

=== Installing the New Intermediate CA ===

===== Procedure =====

# From the left pane, select '''Intermediate Certification Authorities'''.
# Right-click '''Certificates'''.
# Select '''All Tasks > Import'''.
# At the Certificate Import Wizard, select '''Next'''.
# Select the Intermediate CA Certificate file.
# Select '''Next'''.
# Select '''Place all certificate in the following store: Intermediate Certification Authorities'''.
# Select '''Next'''.
# Select '''Finish'''.
# Restart the Web Server.
#: If this does not resolve the issue, then physically reboot the Web Server. The Web Server should now only have one Intermediate CA that expires in 2016.

== How to Replace an Expired Intermediate Certificate for Web Conferencing ==

This topic applies only if you upgraded from Release 7.0 to Release 8.0.

'''Note: ''' As of April 2006, all SSL certificates issued by VeriSign require the installation of an intermediate Certificate Authority (CA) certificate. The SSL certificates are signed by an intermediate CA using a two-tier hierarchy (also known as trust chain) which enhances the security of SSL certificates.

For more information, go to: https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR657&actp=RELATED_RESOURCE.

# Follow the steps in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Downloading the Updated VeriSign Intermediate CA|Downloading the Updated VeriSign Intermediate CA]].
#: In that procedure, you copied the contents of the intermediate CA certificate into a file called newintermediate.cer.
# Follow the steps in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]].
# When prompted to copy the certificate, copy the text from file called newintermediate.cer.
# Add the intermediate certificate provided by your certificate authority provider to the SSL certificate PEM files.

'''Note: ''' When pasting these two certificates within the same PEM file, the order of these certificates matters. The signed server certificate has to be pasted first and then the intermediate certificate should be pasted below the signed server certificate. Be careful when pasting these certificates into the file as extra spaces or dashes can cause problems with the certificate file. Once you make the changes, restart Flash Communication services and the Breeze Application service.

== How to Back Up and Restore the SSL Private Key ==

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Importing the Private Key in to the MPWEB Database|Importing the Private Key in to the MPWEB Database]]

=== Exporting the Private Key ===

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

===== Procedure =====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

=== Copying and Saving the Private Key for Future Use ===

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Open a DOS prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
# Enter the path to your desktop in the cmd.exe window.
#:<tt> Example: C:\> cd "Documents and Settings\Administrator\Desktop" </tt>
# Enter the full path to OpenSSL.exe keeping the following in mind:
#* After -in, enter the full path to where you placed the file when you exported the private key.
#* After -out, enter the full path to where you want to send the exported file.
#*:<tt> Example:C:\Documents and Settings\Administrator\Desktop>"\Program Files\Cisco Systems\MPWeb\DataSvc\openssl.exe" pkcs12 -in "\Documents and Settings\Administrator\Desktop\mycertificate.pfx" -out "\Documents and Settings\Administrator\Desktop\mycertificate.pem" -nodes </tt>
#: This converts the PFX format to a PEM format. The mycertificate.pem file will have all the certificates starting with the Private key.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]]

=== Importing the Private Key in to the MPWEB Database ===

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].
* Back up the complete database before performing this procedure.

===== Procedure =====

# Open the SQL Query Analyzer.
# Select '''Start > All Programs > Microsoft SQL Server > Query Analyzer'''.
# Log in with your SQL username, ”sa,” and password (which you set during the installation of MPWeb).
# Type in the following commands:
#:* '''use mpweb'''
#:* '''update web'''
#:* '''set sslprivatekey='Your private key' '''
# Your private key begins with “BEGIN RSA PRIVATE KEY” and ends with “END RSA PRIVATE KEY”. Copy your private key and paste it between the quotes. You can find your Private key in your PEM file that you saved when you copied and saved the private key for future use.
#: '''Note''': Make sure you include the quotation marks.
# Select the green arrow to Execute Query.
# Determine if your Private Key insertion was successful by entering the following commands in the Query Analyzer window:
#:* '''use mpweb'''
#:* '''select sslprivatekey from web'''
# Select the green arrow to Execute Query and your private key appears the following window.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]]

== Allowing Guests to Search Through Public Meetings ==

Guest users have fewer privileges than users who sign in with their profiles. Complete this procedure to allow guests to search through public meetings.

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Web Server'''.
# Scroll down to the "View" section of the page.
# Select the name of the Web Server that you want to configure.
#: Information about this server populates the "Edit" section of the page.
# Select '''Yes''' for Allow Public Meetings in Find Meeting List.
# Select '''Yes''' for Allow Guest Access to Find Meetings Page.
# Select '''Submit'''.

'''Tip: ''' To allow external users (those outside your firewall) and sites (Cisco Unified MeetingPlace systems outside your network) to access a meeting and the associated meeting materials, make sure that Allow External Web Participants is set to Yes for the meeting. This parameter is set by the meeting scheduler from the New Meeting scheduling page, and it is only visible if your Cisco Unified MeetingPlace system has an external site-that is, a Web Server located in an Internet-accessible segment of your network, such as in a DMZ zone.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Field Reference: Web Server Customization Values|Field Reference: Web Server Customization Values]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Web Administration References for Cisco Unified MeetingPlace|Web Administration References for Cisco Unified MeetingPlace]] module

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server

2011-10-18T22:13:29Z

Cgriffen: /* Importing the Private Key in to the MPWEB Database */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

'''Note: ''' This topic does ''not'' apply to deployments in which users schedule meetings from the Cisco WebEx site. For information about Cisco WebEx integration deployments, see the ''Planning Guide for Cisco Unified MeetingPlace'' at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Secure Sockets Layer for the Web Server|How to Configure Secure Sockets Layer for the Web Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Replace an Expired Intermediate Certificate for the Home Page|How to Replace an Expired Intermediate Certificate for the Home Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Replace an Expired Intermediate Certificate for Web Conferencing|How to Replace an Expired Intermediate Certificate for Web Conferencing]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Back Up and Restore the SSL Private Key|How to Back Up and Restore the SSL Private Key]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Allowing Guests to Search Through Public Meetings|Allowing Guests to Search Through Public Meetings]]

== How to Configure Restricted Meeting ID Patterns ==

As a system administrator, you can restrict Cisco Unified MeetingPlace from accepting certain meeting ID patterns that you consider unsecure. For example, you can restrict meeting ID patterns that repeat the same digit three times in a row, such as 111 or 222.

Keep the following points in mind when determining which meeting ID patterns to restrict:
*Restricted meeting ID patterns affect both numerical and vanity meeting IDs. Therefore, if you select to restrict patterns that repeat the same digit three times, Cisco Unified MeetingPlace will disallow both the numerical meeting ID "333" and the vanity meeting ID "deepdive," because "deepdive" translates to 3337383.
*Keep the length of your minimum meeting ID requirement in mind. Repeating the same digit three times when the length of your minimum meeting ID is four digits long can be considered a security risk. However, repeating the same digit three times when the length of your minimum meeting ID is eight digits long may not.
*There is always the chance of a meeting ID hitting the rule pattern and causing a problem. Judicious use of the rule is critical for the reduction of such incidents.
:Specifically, only meeting IDs that schedulers manually enter via the Cisco Unified MeetingPlace web user portal or Microsoft Outlook are immediately checked against the restricted meeting ID patterns that you configure on the Web Server. If a conflict is found, then the scheduler is prompted to enter an unrestricted meeting ID.
:In contrast, the configured restricted meeting ID patterns will cause errors if they conflict with meeting IDs that are entered or generated using one of the following methods:
:*Scheduler leaves the meeting ID field blank, so the system randomly generates the meeting ID.
:*User schedules the meeting via the TUI or Cisco Unified MeetingPlace PhoneView.
:*A reservationless meeting uses the profile number of the meeting owner as the meeting ID.

'''Note: ''' You cannot schedule a meeting with a supported meeting ID pattern through the phone or other scheduling endpoint, then attempt to modify it or reschedule it through the web. This rescheduling behavior is not supported.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Adding Restricted Meeting ID Patterns|Adding Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Deleting Restricted Meeting ID Patterns|Deleting Restricted Meeting ID Patterns]]

=== Adding Restricted Meeting ID Patterns ===

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Restricted Meeting ID Patterns'''.
# For Pattern, enter the restricted meeting ID pattern as a regular expression using the Perl syntax.
#:<tt> Example: .*(012|123|234|345|456|567|678|789|890|098|987|876|765|654|543|432|321|210).* </tt>
# Enter a brief description to explain the intent of the pattern in the field provided.
#:<tt> Example: Block sequences of 3 increasing or decreasing numbers. </tt>
# Select '''Add'''.
#: The pattern displays in the "View" section of the page.
# Repeat Step 4 through Step 6 for each additional restricted ID pattern.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Restricting the Use of Vanity Meeting IDs|Restricting the Use of Vanity Meeting IDs]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module

=== Deleting Restricted Meeting ID Patterns ===

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Restricted Meeting ID Patterns'''.
# Scroll down to the "View" section of the screen.
# Locate the pattern you want to delete.
# Select '''Delete'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Restricting the Use of Vanity Meeting IDs|Restricting the Use of Vanity Meeting IDs]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module

== How to Configure Secure Sockets Layer for the Web Server ==

Secure Sockets Layer (SSL) secures information by encrypting the data for travel across the network. Complete the following procedures in the order shown to configure SSL.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Restrictions for Configuring Secure Sockets Layer|Restrictions for Configuring Secure Sockets Layer]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Changing the Web Server Hostname From an IP Address to a Hostname|Changing the Web Server Hostname From an IP Address to a Hostname]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Testing the Web Server Over an HTTPS Connection|Testing the Web Server Over an HTTPS Connection]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#(Optional) Disabling Support for Low Encryption Ciphers and SSL v2|(Optional) Disabling Support for Low Encryption Ciphers and SSL v2]]

=== Restrictions for Configuring Secure Sockets Layer ===
* If you are using SSL on an external Web Server, make sure that the hostname on the SSL certificate resolves to the external Web Server IP address.
* If you are using SSL on a system with a segmented DNS, make sure that the hostname on the SSL certificate differs from the segmented DNS name.
* Self-signed certificates are not supported.
* Make sure that the Hostname [Home Page] field value is a hostname, not an IP address.
: The same restriction applies to the Hostname [Web Conferencing] field, which appears only if you upgraded from Release 7.0 to Release 8.0.
* If users will access your Web Server through a firewall, make sure that TCP port 443 is open inbound on your firewall for both of the hostnames or IP addresses on your server.
* You can use SSL on any Web Server (internal or DMZ); however, you cannot use or configure WIA (Windows Integrated Authentication) on that server.
* We do not support SSL certificates that require a key stronger than 1024 bits.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Secure Sockets Layer for the Web Server|How to Configure Secure Sockets Layer for the Web Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Authentication for the Cisco Unified MeetingPlace Web Server#Windows Integrated Authentication|Windows Integrated Authentication]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Authentication for the Cisco Unified MeetingPlace Web Server#Configuring User Authentication for the Cisco Unified MeetingPlace Web Server|Configuring User Authentication for the Cisco Unified MeetingPlace Web Server]] module

=== Changing the Web Server Hostname From an IP Address to a Hostname ===

The Web Server hostname was populated during the Cisco Unified MeetingPlace Web Server software installation. The Hostname [Home Page] was assigned the first IP address in the operating system. If you upgraded from Release 7.0 to Release 8.0, then the Hostname [Web Conferencing] was assigned the second IP address in the operating system.

You should not need to redefine these unless either of the following applies:
* You want users to be able to access the Cisco Unified MeetingPlace Web Server by using the fully qualified domain name (FQDN) of the server or
* You plan to configure SSL for this server. If enabling SSL, you must use hostnames rather than IP addresses.

===== Before You Begin =====

This procedure assumes that you have already installed the Cisco Unified MeetingPlace Web Server software.

===== Restrictions =====

Do not perform this procedure if the Web Server is not in a Domain Name Server (DNS).

===== Procedure =====

# Open your web browser and enter the URL of your Web Server.
#* For internal Web Servers, the default URL structure is '''http://'''''server'', where ''server'' is the name of your internal Web Server.
#* For external (DMZ) Web Servers, you can only access the administration pages from the server box itself and only through port 8002. If you try to access the administration pages on the external Web Server by using http://''server''/mpweb/admin/, the system will display a 404 "Page Not Found" error.
#: To access the administration pages for the external (DMZ) server, you must be on the web server box and enter the following URL: '''http://localhost:8002/mpweb/admin/'''
#: '''Note: ''' If SSL is enabled on your system, you must still enter the URL with http and not https.
#: The system automatically signs you in using the preconfigured ''admin'' profile.
# Sign in to the web user portal.
# Select '''Admin''' if you are not already on the Cisco Unified MeetingPlace Web Administration page.
# Select '''Web Server'''.
# Scroll down to the "View" section of the page.
# Select the name of the Web Server that you want to configure.
#:Information about this Web Server populates the "Edit" section of the page.
# For Hostname [Home Page], enter the fully qualified domain name (FQDN) of the primary network interface on the Web Server.
#:<tt> Example: hostname.domain.com. </tt>
#: '''Note: ''' This hostname must be resolvable by its intended users.
# For Hostname [Web Conferencing], enter the FQDN of the secondary network interface on the Web Server.
#:<tt> Example: hostnamewc.domain.com. </tt>
#: '''Note: ''' This field appears only if you upgraded from Release 7.0 to Release 8.0.
#: '''Note: ''' This hostname must be different from that used for Hostname [Home Page]. It must be resolvable by its intended users. Depending on your hostname choice, the hostnames might not have been automatically registered with the DNS during the OS installation. We recommend that you check the DNS, both the forward and reverse lookup zones, and add entries manually if needed.
# Select '''Submit'''.
# (Optional) If you are working on a Windows system with Internet Explorer, select '''Test Server Configuration'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings#Signing In to the Cisco Unified MeetingPlace Web Administration|Signing In to the Cisco Unified MeetingPlace Web Administration]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings#Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings|Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Field Reference: Web Server Specific Fields|Field Reference: Web Server Specific Fields]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Web Administration References for Cisco Unified MeetingPlace|Web Administration References for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting the Cisco Unified MeetingPlace Web Server#How to Resolve Test Server Configuration Problems|How to Resolve Test Server Configuration Problems]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting the Cisco Unified MeetingPlace Web Server#Troubleshooting the Cisco Unified MeetingPlace Web Server|Troubleshooting the Cisco Unified MeetingPlace Web Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#How to Switch the Order of IP Addresses on the Web Server|How to Switch the Order of IP Addresses on the Web Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server|Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server]] module

===== What to Do Next =====
* If you changed the Hostname [Web Conferencing] field, then you must restart the Cisco Unified MeetingPlace Web Master Service for the field change to take effect. See the [[Cisco Unified MeetingPlace Release 8.0 -- Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service#Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service|Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service]] module.
* If you are configuring SSL, proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]].

=== Creating a New Certificate Signing Request and Obtaining a Certificate File ===

Use the SSL/TLS configuration page to generate certificate signing requests to send to an authorized Certificate Authority in order to apply for digital identity certificates. You need a certificate for the Home Page hostname. If you upgraded from Release 7.0 to Release 8.0, then you also need a certificate for the Web Conferencing hostname.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Changing the Web Server Hostname From an IP Address to a Hostname|Changing the Web Server Hostname From an IP Address to a Hostname]].

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''SSL/TLS'''.
# Select the '''Edit''' icon for the Web Conferencing hostname.
# Enter your company name and organization unit/department in the applicable fields.
# Enter the complete, official names of your city/locality and state/province in the applicable fields.
#: '''Note: ''' Do not use abbreviations.
# Select your country/region.
# Select '''Generate Request'''.
#: The new certificate signing request (CSR) displays in the text box. The request is signed with an auto-generated private key.
# Select the '''Private Key''' link to see the value of the private key.
# Copy the contents of the CSR text box to a text file and send this file to your certificate provider in return for a certificate file.
#:'''Caution! ''' If your certificate provider asks for your server type, specify Apache or Custom, not Microsoft or IIS. If you attempt to install a Microsoft or IIS certificate by using the SSL/TLS configuration pages, the Cisco Unified MeetingPlace Web Server software will not restart when you attempt to reboot the system. Instead it will log an error about the certificate and disable SSL so that you can restart and fix the problem.
# Select '''Back''' to return to the main Administration page.
# Repeat Step 3 through Step 11 for the Web Conferencing hostname.

===== What to Do Next =====

When you receive the .cer file from your certificate provider, proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]].

=== Applying the SSL Certificate ===

When you receive the certificate from your certificate provider, apply the certificate to the Cisco Unified MeetingPlace website by completing the following procedure.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]].

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''SSL/TLS'''.
# Select the '''Edit''' icon for the Web Conferencing hostname.
# Open the certificate file for the Web Conferencing hostname in a text editor, and copy the text to the clipboard.
# In the text box at the bottom of the page, paste the text from the certificate you obtained for this hostname.
#: Make sure the text you paste includes the begin and end certificate delimiters.
# Select '''Install Certificate'''.
#: The host is now set up with a certificate.
# Select '''Back''' to return to the main Administration page.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]].

=== Enabling SSL ===

Complete this procedure to enable the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Require SSL|Require SSL]] field on the Web Server administration page.

===== Before You Begin =====
* Complete Applying the SSL Certificate.
* Make sure that you are still on the SSL/TLS page.

===== Procedure =====

#Select '''Toggle SSL''' to turn SSL on.
#Select '''Reboot Server'''.
::The server shuts down and restarts.
::'''Note: ''' If the Web Server cannot validate the SSL certificates, the server will log an error and toggle SSL to off. In this case, you will need to restart the Cisco Unified MeetingPlace Web Master Service and fix the issue, then repeat the steps in this procedure.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service#Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service|Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service]] module

===== What to do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Testing the Web Server Over an HTTPS Connection|Testing the Web Server Over an HTTPS Connection]].

=== Testing the Web Server Over an HTTPS Connection ===

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]].

===== Procedure =====

# Use a web browser to connect to https://hostname.domain.com, the Fully Qualified Domain Name, of the Web Server.
#* If the Cisco Unified MeetingPlace home page displays, the connection to the Home Page hostname is successful.
#* If any security warning dialog boxes appear, configure SSL not to show the dialog boxes.
#*: For detailed information, see Microsoft Knowledge Base Articles 813618 and 257873 on the Microsoft website.
# If your system was upgraded from Release 7.0 to Release 8.0, then complete these steps to test the connection to the Web Conferencing hostname:
## Find a meeting that meets the following conditions:
##* Meeting occurred before the upgrade from Release 7.0 to Release 8.0.
##* The meeting has a recording.
## Verify that you can access and play the meeting recording.

===== Related Topics =====
* For information about finding meetings and playing recordings, see the ''User Guide for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_user_guide_list.html.

=== (Optional) Disabling Support for Low Encryption Ciphers and SSL v2 ===

Cisco authorizes Cisco Unified MeetingPlace customers to disable the support for low encryption ciphers and SSL v2 on their Cisco Unified MeetingPlace Web Servers based on their security requirements.

You must assume all work related to this security hardening as well as the operational consequences of this security lock-down, including the fact that some end-users might be unable to use the Cisco Unified MeetingPlace Web Servers because of incompatible browsers/ client SSL implementation, or encryption strength limitations.

To perform this lock-down for the Microsoft IIS web server component used by Cisco Unified MeetingPlace, see the following Microsoft Knowledge Base articles:

How to Control the Ciphers for SSL and TLS on IIS (IIS restart required): http://support.microsoft.com/default.aspx?scid=KB;en-us;q216482

How to Restrict the Use of Certain Cryptographic Algorithms and Protocols in Schannel.dll (Windows restart required): http://support.microsoft.com/default.aspx?scid=kb;EN-US;245030

How to disable PCT 1.0, SSL 2.0, SSL 3.0, or TLS 1.0 in Internet Information Services (Windows restart required): http://support.microsoft.com/default.aspx?scid=kb;en-us;187498

To perform this lock-down for the Adobe Connect application web server used by Cisco Unified MeetingPlace Web Conferencing, see the following Adobe article: http://livedocs.adobe.com/fms/2/docs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Parts&file=00000300.html

'''Note: ''' You can find the Server.xml file that contains the SSLCipherSuite tag to be edited in the following folder on the Cisco Unified MeetingPlace Web Server: C:\Program Files\Cisco Systems\MPWeb\WebConf\comserv\win32\conf

'''Caution! ''' Any upgrade of the Cisco Unified MeetingPlace Web Server software with a maintenance release will overwrite the changes that you have made in Server.xml. These changes must be re-applied after the upgrade.

== How to Replace an Expired Intermediate Certificate for the Home Page ==

'''Note: ''' As of April 2006, all SSL certificates issued by VeriSign require the installation of an intermediate Certificate Authority (CA) certificate. The SSL certificates are signed by an intermediate CA using a two-tier hierarchy (also known as trust chain) which enhances the security of SSL certificates.

For more information, go to: https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR657&actp=RELATED_RESOURCE.

Topics in this section include:
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Downloading the Updated VeriSign Intermediate CA|Downloading the Updated VeriSign Intermediate CA]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a Certificate Snap-In|Creating a Certificate Snap-In]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Removing the Expired Intermediate CA|Removing the Expired Intermediate CA]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Installing the New Intermediate CA|Installing the New Intermediate CA]]

=== Downloading the Updated VeriSign Intermediate CA ===

When downloading the intermediate CA certificate, ensure that you select the appropriate one for your SSL certificate: either Secure Site with EV Certificates (Secure Server) or Secure Site Pro with EV Certificates (Global).

===== Procedure =====

# If you are not sure which certificate you have purchased, follow these steps:
## Go to VeriSign Search Certificates page.
## Type your Common Name or Order Number.
## Select Search.
## Select the certificate name for your certificate.
# Go to the VeriSign intermediate CA certificates web page and select the CA certificate for your product.
# Copy and paste the contents into a text (Notepad) file.
# Save the file as newintermediate.cer.

=== Creating a Certificate Snap-In ===

===== Procedure =====

# From the Web server, select '''Start > Run'''.
# In the text box, type '''mmc'''.
# Select '''OK'''.
# For IIS 5.0: From the Microsoft Management Console (MMC) menu bar, select '''Console > Add/Remove Snap-in'''.
# For IIS 6.0: From the Microsoft Management Console (MMC) menu bar, select '''File > Add/Remove Snap-in'''.
# Select '''Add'''.
# From the list of snap-ins, select '''Certificates'''.
# Select '''Add'''.
# Select '''Computer account'''.
# Select '''Next'''.
# Select '''Local computer''' (the computer this console is running on).
# Select '''Finish'''.
# In the snap-in list window, select '''Close'''.
# In the Add/Remove Snap-in window, select '''OK'''.
# Save these console settings for future use.

=== Removing the Expired Intermediate CA ===

===== Procedure =====

# From the left pane, double-click '''Certificate (Local Computer)'''.
# Select '''Intermediate Certification Authorities > Certificates'''.
# Locate the certificate issued to www.verisign.com/CPS Incorp.by Ref.LIABILITY LTD. (C)97 VeriSign (expiration date of 1/7/2004).
# Right-click the certificate.
# Select '''Delete'''.
# From the left pane, select '''Trusted Root Certification Authorities > Certificates'''.
# Locate the certificate issued to Class 3 Public Primary Certification Authority (expiration date of 1/7/2004).
# Right-click the certificate.
# Select '''Delete'''.

=== Installing the New Intermediate CA ===

===== Procedure =====

# From the left pane, select '''Intermediate Certification Authorities'''.
# Right-click '''Certificates'''.
# Select '''All Tasks > Import'''.
# At the Certificate Import Wizard, select '''Next'''.
# Select the Intermediate CA Certificate file.
# Select '''Next'''.
# Select '''Place all certificate in the following store: Intermediate Certification Authorities'''.
# Select '''Next'''.
# Select '''Finish'''.
# Restart the Web Server.
#: If this does not resolve the issue, then physically reboot the Web Server. The Web Server should now only have one Intermediate CA that expires in 2016.

== How to Replace an Expired Intermediate Certificate for Web Conferencing ==

This topic applies only if you upgraded from Release 7.0 to Release 8.0.

'''Note: ''' As of April 2006, all SSL certificates issued by VeriSign require the installation of an intermediate Certificate Authority (CA) certificate. The SSL certificates are signed by an intermediate CA using a two-tier hierarchy (also known as trust chain) which enhances the security of SSL certificates.

For more information, go to: https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR657&actp=RELATED_RESOURCE.

# Follow the steps in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Downloading the Updated VeriSign Intermediate CA|Downloading the Updated VeriSign Intermediate CA]].
#: In that procedure, you copied the contents of the intermediate CA certificate into a file called newintermediate.cer.
# Follow the steps in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]].
# When prompted to copy the certificate, copy the text from file called newintermediate.cer.
# Add the intermediate certificate provided by your certificate authority provider to the SSL certificate PEM files.

'''Note: ''' When pasting these two certificates within the same PEM file, the order of these certificates matters. The signed server certificate has to be pasted first and then the intermediate certificate should be pasted below the signed server certificate. Be careful when pasting these certificates into the file as extra spaces or dashes can cause problems with the certificate file. Once you make the changes, restart Flash Communication services and the Breeze Application service.

== How to Back Up and Restore the SSL Private Key ==

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Importing the Private Key in to the MPWEB Database|Importing the Private Key in to the MPWEB Database]]

=== Exporting the Private Key ===

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

===== Procedure =====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

=== Copying and Saving the Private Key for Future Use ===

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Open a DOS prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
# Enter the path to your desktop in the cmd.exe window.
#:<tt> Example: C:\> cd "Documents and Settings\Administrator\Desktop" </tt>
# Enter the full path to OpenSSL.exe keeping the following in mind:
#* After -in, enter the full path to where you placed the file when you exported the private key.
#* After -out, enter the full path to where you want to send the exported file.
#*:<tt> Example:C:\Documents and Settings\Administrator\Desktop>"\Program Files\Cisco Systems\MPWeb\DataSvc\openssl.exe" pkcs12 -in "\Documents and Settings\Administrator\Desktop\mycertificate.pfx" -out "\Documents and Settings\Administrator\Desktop\mycertificate.pem" -nodes </tt>
#: This converts the PFX format to a PEM format. The mycertificate.pem file will have all the certificates starting with the Private key.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]]

=== Importing the Private Key in to the MPWEB Database ===

===== Before You Begin =====

# Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].
# Back up the complete database before performing this procedure.

===== Procedure =====

# Open the SQL Query Analyzer.
# Select '''Start > All Programs > Microsoft SQL Server > Query Analyzer'''.
# Log in with your SQL username, ”sa,” and password (which you set during the installation of MPWeb).
# Type in the following commands:
#:* '''use mpweb'''
#:* '''update web'''
#:* '''set sslprivatekey='Your private key' '''
# Your private key begins with “BEGIN RSA PRIVATE KEY” and ends with “END RSA PRIVATE KEY”. Copy your private key and paste it between the quotes. You can find your Private key in your PEM file that you saved when you copied and saved the private key for future use.
#: '''Note''': Make sure you include the quotation marks.
# Select the green arrow to Execute Query.
# Determine if your Private Key insertion was successful by entering the following commands in the Query Analyzer window:
#:* '''use mpweb'''
#:* '''select sslprivatekey from web'''
# Select the green arrow to Execute Query and your private key appears the following window.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]]

== Allowing Guests to Search Through Public Meetings ==

Guest users have fewer privileges than users who sign in with their profiles. Complete this procedure to allow guests to search through public meetings.

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Web Server'''.
# Scroll down to the "View" section of the page.
# Select the name of the Web Server that you want to configure.
#: Information about this server populates the "Edit" section of the page.
# Select '''Yes''' for Allow Public Meetings in Find Meeting List.
# Select '''Yes''' for Allow Guest Access to Find Meetings Page.
# Select '''Submit'''.

'''Tip: ''' To allow external users (those outside your firewall) and sites (Cisco Unified MeetingPlace systems outside your network) to access a meeting and the associated meeting materials, make sure that Allow External Web Participants is set to Yes for the meeting. This parameter is set by the meeting scheduler from the New Meeting scheduling page, and it is only visible if your Cisco Unified MeetingPlace system has an external site-that is, a Web Server located in an Internet-accessible segment of your network, such as in a DMZ zone.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Field Reference: Web Server Customization Values|Field Reference: Web Server Customization Values]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Web Administration References for Cisco Unified MeetingPlace|Web Administration References for Cisco Unified MeetingPlace]] module

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server

2011-10-18T22:11:28Z

Cgriffen: /* Procedure */

'''Main page:''' [[Cisco Unified MeetingPlace, Release 8.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Configuration|Configuration]]

'''Note: ''' This topic does ''not'' apply to deployments in which users schedule meetings from the Cisco WebEx site. For information about Cisco WebEx integration deployments, see the ''Planning Guide for Cisco Unified MeetingPlace'' at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Secure Sockets Layer for the Web Server|How to Configure Secure Sockets Layer for the Web Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Replace an Expired Intermediate Certificate for the Home Page|How to Replace an Expired Intermediate Certificate for the Home Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Replace an Expired Intermediate Certificate for Web Conferencing|How to Replace an Expired Intermediate Certificate for Web Conferencing]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Back Up and Restore the SSL Private Key|How to Back Up and Restore the SSL Private Key]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Allowing Guests to Search Through Public Meetings|Allowing Guests to Search Through Public Meetings]]

== How to Configure Restricted Meeting ID Patterns ==

As a system administrator, you can restrict Cisco Unified MeetingPlace from accepting certain meeting ID patterns that you consider unsecure. For example, you can restrict meeting ID patterns that repeat the same digit three times in a row, such as 111 or 222.

Keep the following points in mind when determining which meeting ID patterns to restrict:
*Restricted meeting ID patterns affect both numerical and vanity meeting IDs. Therefore, if you select to restrict patterns that repeat the same digit three times, Cisco Unified MeetingPlace will disallow both the numerical meeting ID "333" and the vanity meeting ID "deepdive," because "deepdive" translates to 3337383.
*Keep the length of your minimum meeting ID requirement in mind. Repeating the same digit three times when the length of your minimum meeting ID is four digits long can be considered a security risk. However, repeating the same digit three times when the length of your minimum meeting ID is eight digits long may not.
*There is always the chance of a meeting ID hitting the rule pattern and causing a problem. Judicious use of the rule is critical for the reduction of such incidents.
:Specifically, only meeting IDs that schedulers manually enter via the Cisco Unified MeetingPlace web user portal or Microsoft Outlook are immediately checked against the restricted meeting ID patterns that you configure on the Web Server. If a conflict is found, then the scheduler is prompted to enter an unrestricted meeting ID.
:In contrast, the configured restricted meeting ID patterns will cause errors if they conflict with meeting IDs that are entered or generated using one of the following methods:
:*Scheduler leaves the meeting ID field blank, so the system randomly generates the meeting ID.
:*User schedules the meeting via the TUI or Cisco Unified MeetingPlace PhoneView.
:*A reservationless meeting uses the profile number of the meeting owner as the meeting ID.

'''Note: ''' You cannot schedule a meeting with a supported meeting ID pattern through the phone or other scheduling endpoint, then attempt to modify it or reschedule it through the web. This rescheduling behavior is not supported.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Adding Restricted Meeting ID Patterns|Adding Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Deleting Restricted Meeting ID Patterns|Deleting Restricted Meeting ID Patterns]]

=== Adding Restricted Meeting ID Patterns ===

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Restricted Meeting ID Patterns'''.
# For Pattern, enter the restricted meeting ID pattern as a regular expression using the Perl syntax.
#:<tt> Example: .*(012|123|234|345|456|567|678|789|890|098|987|876|765|654|543|432|321|210).* </tt>
# Enter a brief description to explain the intent of the pattern in the field provided.
#:<tt> Example: Block sequences of 3 increasing or decreasing numbers. </tt>
# Select '''Add'''.
#: The pattern displays in the "View" section of the page.
# Repeat Step 4 through Step 6 for each additional restricted ID pattern.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Restricting the Use of Vanity Meeting IDs|Restricting the Use of Vanity Meeting IDs]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module

=== Deleting Restricted Meeting ID Patterns ===

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Restricted Meeting ID Patterns'''.
# Scroll down to the "View" section of the screen.
# Locate the pattern you want to delete.
# Select '''Delete'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Restricted Meeting ID Patterns|How to Configure Restricted Meeting ID Patterns]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Restricting the Use of Vanity Meeting IDs|Restricting the Use of Vanity Meeting IDs]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module

== How to Configure Secure Sockets Layer for the Web Server ==

Secure Sockets Layer (SSL) secures information by encrypting the data for travel across the network. Complete the following procedures in the order shown to configure SSL.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Restrictions for Configuring Secure Sockets Layer|Restrictions for Configuring Secure Sockets Layer]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Changing the Web Server Hostname From an IP Address to a Hostname|Changing the Web Server Hostname From an IP Address to a Hostname]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Testing the Web Server Over an HTTPS Connection|Testing the Web Server Over an HTTPS Connection]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#(Optional) Disabling Support for Low Encryption Ciphers and SSL v2|(Optional) Disabling Support for Low Encryption Ciphers and SSL v2]]

=== Restrictions for Configuring Secure Sockets Layer ===
* If you are using SSL on an external Web Server, make sure that the hostname on the SSL certificate resolves to the external Web Server IP address.
* If you are using SSL on a system with a segmented DNS, make sure that the hostname on the SSL certificate differs from the segmented DNS name.
* Self-signed certificates are not supported.
* Make sure that the Hostname [Home Page] field value is a hostname, not an IP address.
: The same restriction applies to the Hostname [Web Conferencing] field, which appears only if you upgraded from Release 7.0 to Release 8.0.
* If users will access your Web Server through a firewall, make sure that TCP port 443 is open inbound on your firewall for both of the hostnames or IP addresses on your server.
* You can use SSL on any Web Server (internal or DMZ); however, you cannot use or configure WIA (Windows Integrated Authentication) on that server.
* We do not support SSL certificates that require a key stronger than 1024 bits.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#How to Configure Secure Sockets Layer for the Web Server|How to Configure Secure Sockets Layer for the Web Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Authentication for the Cisco Unified MeetingPlace Web Server#Windows Integrated Authentication|Windows Integrated Authentication]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Authentication for the Cisco Unified MeetingPlace Web Server#Configuring User Authentication for the Cisco Unified MeetingPlace Web Server|Configuring User Authentication for the Cisco Unified MeetingPlace Web Server]] module

=== Changing the Web Server Hostname From an IP Address to a Hostname ===

The Web Server hostname was populated during the Cisco Unified MeetingPlace Web Server software installation. The Hostname [Home Page] was assigned the first IP address in the operating system. If you upgraded from Release 7.0 to Release 8.0, then the Hostname [Web Conferencing] was assigned the second IP address in the operating system.

You should not need to redefine these unless either of the following applies:
* You want users to be able to access the Cisco Unified MeetingPlace Web Server by using the fully qualified domain name (FQDN) of the server or
* You plan to configure SSL for this server. If enabling SSL, you must use hostnames rather than IP addresses.

===== Before You Begin =====

This procedure assumes that you have already installed the Cisco Unified MeetingPlace Web Server software.

===== Restrictions =====

Do not perform this procedure if the Web Server is not in a Domain Name Server (DNS).

===== Procedure =====

# Open your web browser and enter the URL of your Web Server.
#* For internal Web Servers, the default URL structure is '''http://'''''server'', where ''server'' is the name of your internal Web Server.
#* For external (DMZ) Web Servers, you can only access the administration pages from the server box itself and only through port 8002. If you try to access the administration pages on the external Web Server by using http://''server''/mpweb/admin/, the system will display a 404 "Page Not Found" error.
#: To access the administration pages for the external (DMZ) server, you must be on the web server box and enter the following URL: '''http://localhost:8002/mpweb/admin/'''
#: '''Note: ''' If SSL is enabled on your system, you must still enter the URL with http and not https.
#: The system automatically signs you in using the preconfigured ''admin'' profile.
# Sign in to the web user portal.
# Select '''Admin''' if you are not already on the Cisco Unified MeetingPlace Web Administration page.
# Select '''Web Server'''.
# Scroll down to the "View" section of the page.
# Select the name of the Web Server that you want to configure.
#:Information about this Web Server populates the "Edit" section of the page.
# For Hostname [Home Page], enter the fully qualified domain name (FQDN) of the primary network interface on the Web Server.
#:<tt> Example: hostname.domain.com. </tt>
#: '''Note: ''' This hostname must be resolvable by its intended users.
# For Hostname [Web Conferencing], enter the FQDN of the secondary network interface on the Web Server.
#:<tt> Example: hostnamewc.domain.com. </tt>
#: '''Note: ''' This field appears only if you upgraded from Release 7.0 to Release 8.0.
#: '''Note: ''' This hostname must be different from that used for Hostname [Home Page]. It must be resolvable by its intended users. Depending on your hostname choice, the hostnames might not have been automatically registered with the DNS during the OS installation. We recommend that you check the DNS, both the forward and reverse lookup zones, and add entries manually if needed.
# Select '''Submit'''.
# (Optional) If you are working on a Windows system with Internet Explorer, select '''Test Server Configuration'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings#Signing In to the Cisco Unified MeetingPlace Web Administration|Signing In to the Cisco Unified MeetingPlace Web Administration]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings#Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings|Quick Start Configuration for Cisco Unified MeetingPlace Web User Portal for Scheduling and Joining Meetings]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Field Reference: Web Server Specific Fields|Field Reference: Web Server Specific Fields]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Web Administration References for Cisco Unified MeetingPlace|Web Administration References for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting the Cisco Unified MeetingPlace Web Server#How to Resolve Test Server Configuration Problems|How to Resolve Test Server Configuration Problems]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting the Cisco Unified MeetingPlace Web Server#Troubleshooting the Cisco Unified MeetingPlace Web Server|Troubleshooting the Cisco Unified MeetingPlace Web Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#How to Switch the Order of IP Addresses on the Web Server|How to Switch the Order of IP Addresses on the Web Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server|Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server]] module

===== What to Do Next =====
* If you changed the Hostname [Web Conferencing] field, then you must restart the Cisco Unified MeetingPlace Web Master Service for the field change to take effect. See the [[Cisco Unified MeetingPlace Release 8.0 -- Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service#Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service|Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service]] module.
* If you are configuring SSL, proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]].

=== Creating a New Certificate Signing Request and Obtaining a Certificate File ===

Use the SSL/TLS configuration page to generate certificate signing requests to send to an authorized Certificate Authority in order to apply for digital identity certificates. You need a certificate for the Home Page hostname. If you upgraded from Release 7.0 to Release 8.0, then you also need a certificate for the Web Conferencing hostname.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Changing the Web Server Hostname From an IP Address to a Hostname|Changing the Web Server Hostname From an IP Address to a Hostname]].

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''SSL/TLS'''.
# Select the '''Edit''' icon for the Web Conferencing hostname.
# Enter your company name and organization unit/department in the applicable fields.
# Enter the complete, official names of your city/locality and state/province in the applicable fields.
#: '''Note: ''' Do not use abbreviations.
# Select your country/region.
# Select '''Generate Request'''.
#: The new certificate signing request (CSR) displays in the text box. The request is signed with an auto-generated private key.
# Select the '''Private Key''' link to see the value of the private key.
# Copy the contents of the CSR text box to a text file and send this file to your certificate provider in return for a certificate file.
#:'''Caution! ''' If your certificate provider asks for your server type, specify Apache or Custom, not Microsoft or IIS. If you attempt to install a Microsoft or IIS certificate by using the SSL/TLS configuration pages, the Cisco Unified MeetingPlace Web Server software will not restart when you attempt to reboot the system. Instead it will log an error about the certificate and disable SSL so that you can restart and fix the problem.
# Select '''Back''' to return to the main Administration page.
# Repeat Step 3 through Step 11 for the Web Conferencing hostname.

===== What to Do Next =====

When you receive the .cer file from your certificate provider, proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]].

=== Applying the SSL Certificate ===

When you receive the certificate from your certificate provider, apply the certificate to the Cisco Unified MeetingPlace website by completing the following procedure.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a New Certificate Signing Request and Obtaining a Certificate File|Creating a New Certificate Signing Request and Obtaining a Certificate File]].

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''SSL/TLS'''.
# Select the '''Edit''' icon for the Web Conferencing hostname.
# Open the certificate file for the Web Conferencing hostname in a text editor, and copy the text to the clipboard.
# In the text box at the bottom of the page, paste the text from the certificate you obtained for this hostname.
#: Make sure the text you paste includes the begin and end certificate delimiters.
# Select '''Install Certificate'''.
#: The host is now set up with a certificate.
# Select '''Back''' to return to the main Administration page.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]].

=== Enabling SSL ===

Complete this procedure to enable the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Require SSL|Require SSL]] field on the Web Server administration page.

===== Before You Begin =====
* Complete Applying the SSL Certificate.
* Make sure that you are still on the SSL/TLS page.

===== Procedure =====

#Select '''Toggle SSL''' to turn SSL on.
#Select '''Reboot Server'''.
::The server shuts down and restarts.
::'''Note: ''' If the Web Server cannot validate the SSL certificates, the server will log an error and toggle SSL to off. In this case, you will need to restart the Cisco Unified MeetingPlace Web Master Service and fix the issue, then repeat the steps in this procedure.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service#Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service|Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service]] module

===== What to do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Testing the Web Server Over an HTTPS Connection|Testing the Web Server Over an HTTPS Connection]].

=== Testing the Web Server Over an HTTPS Connection ===

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]].

===== Procedure =====

# Use a web browser to connect to https://hostname.domain.com, the Fully Qualified Domain Name, of the Web Server.
#* If the Cisco Unified MeetingPlace home page displays, the connection to the Home Page hostname is successful.
#* If any security warning dialog boxes appear, configure SSL not to show the dialog boxes.
#*: For detailed information, see Microsoft Knowledge Base Articles 813618 and 257873 on the Microsoft website.
# If your system was upgraded from Release 7.0 to Release 8.0, then complete these steps to test the connection to the Web Conferencing hostname:
## Find a meeting that meets the following conditions:
##* Meeting occurred before the upgrade from Release 7.0 to Release 8.0.
##* The meeting has a recording.
## Verify that you can access and play the meeting recording.

===== Related Topics =====
* For information about finding meetings and playing recordings, see the ''User Guide for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_user_guide_list.html.

=== (Optional) Disabling Support for Low Encryption Ciphers and SSL v2 ===

Cisco authorizes Cisco Unified MeetingPlace customers to disable the support for low encryption ciphers and SSL v2 on their Cisco Unified MeetingPlace Web Servers based on their security requirements.

You must assume all work related to this security hardening as well as the operational consequences of this security lock-down, including the fact that some end-users might be unable to use the Cisco Unified MeetingPlace Web Servers because of incompatible browsers/ client SSL implementation, or encryption strength limitations.

To perform this lock-down for the Microsoft IIS web server component used by Cisco Unified MeetingPlace, see the following Microsoft Knowledge Base articles:

How to Control the Ciphers for SSL and TLS on IIS (IIS restart required): http://support.microsoft.com/default.aspx?scid=KB;en-us;q216482

How to Restrict the Use of Certain Cryptographic Algorithms and Protocols in Schannel.dll (Windows restart required): http://support.microsoft.com/default.aspx?scid=kb;EN-US;245030

How to disable PCT 1.0, SSL 2.0, SSL 3.0, or TLS 1.0 in Internet Information Services (Windows restart required): http://support.microsoft.com/default.aspx?scid=kb;en-us;187498

To perform this lock-down for the Adobe Connect application web server used by Cisco Unified MeetingPlace Web Conferencing, see the following Adobe article: http://livedocs.adobe.com/fms/2/docs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Parts&file=00000300.html

'''Note: ''' You can find the Server.xml file that contains the SSLCipherSuite tag to be edited in the following folder on the Cisco Unified MeetingPlace Web Server: C:\Program Files\Cisco Systems\MPWeb\WebConf\comserv\win32\conf

'''Caution! ''' Any upgrade of the Cisco Unified MeetingPlace Web Server software with a maintenance release will overwrite the changes that you have made in Server.xml. These changes must be re-applied after the upgrade.

== How to Replace an Expired Intermediate Certificate for the Home Page ==

'''Note: ''' As of April 2006, all SSL certificates issued by VeriSign require the installation of an intermediate Certificate Authority (CA) certificate. The SSL certificates are signed by an intermediate CA using a two-tier hierarchy (also known as trust chain) which enhances the security of SSL certificates.

For more information, go to: https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR657&actp=RELATED_RESOURCE.

Topics in this section include:
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Downloading the Updated VeriSign Intermediate CA|Downloading the Updated VeriSign Intermediate CA]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Creating a Certificate Snap-In|Creating a Certificate Snap-In]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Removing the Expired Intermediate CA|Removing the Expired Intermediate CA]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Installing the New Intermediate CA|Installing the New Intermediate CA]]

=== Downloading the Updated VeriSign Intermediate CA ===

When downloading the intermediate CA certificate, ensure that you select the appropriate one for your SSL certificate: either Secure Site with EV Certificates (Secure Server) or Secure Site Pro with EV Certificates (Global).

===== Procedure =====

# If you are not sure which certificate you have purchased, follow these steps:
## Go to VeriSign Search Certificates page.
## Type your Common Name or Order Number.
## Select Search.
## Select the certificate name for your certificate.
# Go to the VeriSign intermediate CA certificates web page and select the CA certificate for your product.
# Copy and paste the contents into a text (Notepad) file.
# Save the file as newintermediate.cer.

=== Creating a Certificate Snap-In ===

===== Procedure =====

# From the Web server, select '''Start > Run'''.
# In the text box, type '''mmc'''.
# Select '''OK'''.
# For IIS 5.0: From the Microsoft Management Console (MMC) menu bar, select '''Console > Add/Remove Snap-in'''.
# For IIS 6.0: From the Microsoft Management Console (MMC) menu bar, select '''File > Add/Remove Snap-in'''.
# Select '''Add'''.
# From the list of snap-ins, select '''Certificates'''.
# Select '''Add'''.
# Select '''Computer account'''.
# Select '''Next'''.
# Select '''Local computer''' (the computer this console is running on).
# Select '''Finish'''.
# In the snap-in list window, select '''Close'''.
# In the Add/Remove Snap-in window, select '''OK'''.
# Save these console settings for future use.

=== Removing the Expired Intermediate CA ===

===== Procedure =====

# From the left pane, double-click '''Certificate (Local Computer)'''.
# Select '''Intermediate Certification Authorities > Certificates'''.
# Locate the certificate issued to www.verisign.com/CPS Incorp.by Ref.LIABILITY LTD. (C)97 VeriSign (expiration date of 1/7/2004).
# Right-click the certificate.
# Select '''Delete'''.
# From the left pane, select '''Trusted Root Certification Authorities > Certificates'''.
# Locate the certificate issued to Class 3 Public Primary Certification Authority (expiration date of 1/7/2004).
# Right-click the certificate.
# Select '''Delete'''.

=== Installing the New Intermediate CA ===

===== Procedure =====

# From the left pane, select '''Intermediate Certification Authorities'''.
# Right-click '''Certificates'''.
# Select '''All Tasks > Import'''.
# At the Certificate Import Wizard, select '''Next'''.
# Select the Intermediate CA Certificate file.
# Select '''Next'''.
# Select '''Place all certificate in the following store: Intermediate Certification Authorities'''.
# Select '''Next'''.
# Select '''Finish'''.
# Restart the Web Server.
#: If this does not resolve the issue, then physically reboot the Web Server. The Web Server should now only have one Intermediate CA that expires in 2016.

== How to Replace an Expired Intermediate Certificate for Web Conferencing ==

This topic applies only if you upgraded from Release 7.0 to Release 8.0.

'''Note: ''' As of April 2006, all SSL certificates issued by VeriSign require the installation of an intermediate Certificate Authority (CA) certificate. The SSL certificates are signed by an intermediate CA using a two-tier hierarchy (also known as trust chain) which enhances the security of SSL certificates.

For more information, go to: https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR657&actp=RELATED_RESOURCE.

# Follow the steps in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Downloading the Updated VeriSign Intermediate CA|Downloading the Updated VeriSign Intermediate CA]].
#: In that procedure, you copied the contents of the intermediate CA certificate into a file called newintermediate.cer.
# Follow the steps in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Applying the SSL Certificate|Applying the SSL Certificate]].
# When prompted to copy the certificate, copy the text from file called newintermediate.cer.
# Add the intermediate certificate provided by your certificate authority provider to the SSL certificate PEM files.

'''Note: ''' When pasting these two certificates within the same PEM file, the order of these certificates matters. The signed server certificate has to be pasted first and then the intermediate certificate should be pasted below the signed server certificate. Be careful when pasting these certificates into the file as extra spaces or dashes can cause problems with the certificate file. Once you make the changes, restart Flash Communication services and the Breeze Application service.

== How to Back Up and Restore the SSL Private Key ==

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Importing the Private Key in to the MPWEB Database|Importing the Private Key in to the MPWEB Database]]

=== Exporting the Private Key ===

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

===== Procedure =====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Select '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Select the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Select the '''Directory Security''' tab.
# Select '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Select '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Select '''Next'''.
# Select '''Browse''' and select to save the certificate file to your desktop.
# Select '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Select '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Select '''Next'''.
# Select '''Finish''' to close the Web Server Certificate wizard.
# Select '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

=== Copying and Saving the Private Key for Future Use ===

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Open a DOS prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
# Enter the path to your desktop in the cmd.exe window.
#:<tt> Example: C:\> cd "Documents and Settings\Administrator\Desktop" </tt>
# Enter the full path to OpenSSL.exe keeping the following in mind:
#* After -in, enter the full path to where you placed the file when you exported the private key.
#* After -out, enter the full path to where you want to send the exported file.
#*:<tt> Example:C:\Documents and Settings\Administrator\Desktop>"\Program Files\Cisco Systems\MPWeb\DataSvc\openssl.exe" pkcs12 -in "\Documents and Settings\Administrator\Desktop\mycertificate.pfx" -out "\Documents and Settings\Administrator\Desktop\mycertificate.pem" -nodes </tt>
#: This converts the PFX format to a PEM format. The mycertificate.pem file will have all the certificates starting with the Private key.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Exporting the Private Key|Exporting the Private Key]]

=== Importing the Private Key in to the MPWEB Database ===

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

===== Before You Begin =====

Back up the complete database before performing this procedure.

===== Procedure =====

# Open the SQL Query Analyzer.
# Select '''Start > All Programs > Microsoft SQL Server > Query Analyzer'''.
# Log in with your SQL username, ”sa,” and password (which you set during the installation of MPWeb).
# Type in the following commands:
#:* '''use mpweb'''
#:* '''update web'''
#:* '''set sslprivatekey='Your private key' '''
# Your private key begins with “BEGIN RSA PRIVATE KEY” and ends with “END RSA PRIVATE KEY”. Copy your private key and paste it between the quotes. You can find your Private key in your PEM file that you saved when you copied and saved the private key for future use.
#: '''Note''': Make sure you include the quotation marks.
# Select the green arrow to Execute Query.
# Determine if your Private Key insertion was successful by entering the following commands in the Query Analyzer window:
#:* '''use mpweb'''
#:* '''select sslprivatekey from web'''
# Select the green arrow to Execute Query and your private key appears the following window.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Enabling SSL|Enabling SSL]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Security Features for the Cisco Unified MeetingPlace Web Server#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]]

== Allowing Guests to Search Through Public Meetings ==

Guest users have fewer privileges than users who sign in with their profiles. Complete this procedure to allow guests to search through public meetings.

===== Procedure =====

# Sign in to the Cisco Unified MeetingPlace web user portal.
# Select '''Admin'''.
# Select '''Web Server'''.
# Scroll down to the "View" section of the page.
# Select the name of the Web Server that you want to configure.
#: Information about this server populates the "Edit" section of the page.
# Select '''Yes''' for Allow Public Meetings in Find Meeting List.
# Select '''Yes''' for Allow Guest Access to Find Meetings Page.
# Select '''Submit'''.

'''Tip: ''' To allow external users (those outside your firewall) and sites (Cisco Unified MeetingPlace systems outside your network) to access a meeting and the associated meeting materials, make sure that Allow External Web Participants is set to Yes for the meeting. This parameter is set by the meeting scheduler from the New Meeting scheduling page, and it is only visible if your Cisco Unified MeetingPlace system has an external site-that is, a Web Server located in an Internet-accessible segment of your network, such as in a DMZ zone.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Field Reference: Web Server Customization Values|Field Reference: Web Server Customization Values]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Web Administration References for Cisco Unified MeetingPlace|Web Administration References for Cisco Unified MeetingPlace]] module

[[Category: Configuration Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)

2011-10-11T20:40:19Z

Cgriffen: /* Table: Field Reference: Add User Profile Page and Edit User Profile Page */

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace|Administration Center Page References for Cisco Unified MeetingPlace]]

In the Cisco Unified MeetingPlace Administration Center, the title of each page appears in the blue bar beneath the "Cisco Unified MeetingPlace System Administration Center" banner.

This section describes the fields and options on each page, presented in alphabetical order by page titles '''A - C'''.

== Ad-Hoc Cisco Unified Communications Manager Configuration Page ==

Use this page to configure TFTP server IP addresses for ad-hoc conferencing.

To find this page, select '''System Configuration > Call Configuration > Ad-Hoc Cisco Unified Communications Manager Configuration'''.

===== Table: Field Reference: Ad-Hoc Cisco Unified Communications Manager Configuration Page =====

{| border = 1
|-
!Field
!Description
|-
|

Enable SCCP
|

Use this field to enable or to disable Skinny Client Control Protocol (SCCP) for ad-hoc conferencing on the server.

Default: No
|-
|

Primary TFTP server
|

Primary Cisco Unified Communications Manager (formerly called Cisco Unified CallManager) TFTP server IP address.

Default: 0
|-
|

Port
|

Primary TFTP server port number.

'''Note: ''' The Cisco Unified Communications Manager TFTP server typically runs on port 69.

Range: 1 to 65535

Default: 69
|-
|

Backup TFTP server 1
|

First backup Cisco Unified Communications Manager TFTP server IP address.

Default: 0
|-
|

Port
|

First backup TFTP server port number.

'''Note: ''' The Cisco Unified Communications Manager TFTP server typically runs on port 69.

Range: 1 to 65535

Default: 69
|-
|

Backup TFTP server 2
|

Second backup Cisco Unified Communications Manager TFTP server IP address.

Default: 0
|-
|

Port
|

Second backup TFTP server port number.

'''Note: ''' The Cisco Unified Communications Manager TFTP server typically runs on port 69.

Range: 1 to 65535

Default: 69
|-
|

Application server MAC address
|

''Display only''. MAC address of the Cisco Unified MeetingPlace Application Server.

Use the value in this field to identify the Cisco Unified MeetingPlace server as the conference bridge in Cisco Unified Communications Manager configuration.
|-
|colspan="2" rowspan="1"|'''Cisco Unified Communications Manager Registration Information'''
|-
|

Current Cisco Unified Communications Manager
|

''Display only''. The current Cisco Unified Communications Manager TFTP server that is currently in use.
|-
|

Status
|

''Display only''. Whether Cisco Unified MeetingPlace is registered with the Cisco Unified Communications Manager TFTP server.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Ad-Hoc Conferencing for Cisco Unified MeetingPlace#Configuring Ad-Hoc Conferencing for Cisco Unified MeetingPlace|Configuring Ad-Hoc Conferencing for Cisco Unified MeetingPlace]] module

== Add Meeting Categories Page ==

To find this page, select '''System Configuration > Meeting Categories > Add New'''.

===== Table: Field Reference: Add Meeting Categories Page and Edit Meeting Categories Page=====

{| border = 1
|-
!Field
!Description
|-
|

Name
|

Identifies the meeting category on the scheduling page and in meeting details.
|-
|

Owner
|

[[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|User ID]] of the meeting category owner.
|-
|

Description
|

Enter a description that will help system administrators maintain the meeting categories, for example, how to distinguish one meeting category from another.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meeting Categories|Configuring Meeting Categories]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Meeting Categories Page|Meeting Categories Page]]

== Add Server Configuration Page ==

To find this page, select '''System Configuration > Remote Server Configuration > Add New'''.

'''Note: ''' In this document, a "system" refers to a complete Cisco Unified MeetingPlace site installation, which includes one active Application Server and one active Media Server. The system can also include one or more Web Servers.

===== Table: Field Reference: Add Server Configuration Page and Edit Server Configuration Page =====

{| border = 1
|-
!Field
!Description
|-
|

Name
|

Name of the remote system.
|-
|

Home Server number
|

Enter a unique number that identifies the remote server on all RSNA systems.

This same value must be used in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Schedule home server]] user profile field for users that are local to the server.

If you check '''Reserved Meeting Server''':
* The Home Server number field is cleared and cannot be modified.
* In the database, this remote server record is assigned the Home Server number of 777777.
|-
|

Reserved Meeting Server
|

Whether the remote server is the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#RSNA Reserved Meeting Server|RSNA Reserved Meeting Server]].

If you check this:
* The Home Server number field is cleared and cannot be modified.
* In the database, this remote server record is assigned the Home Server number of 777777.
|-
|

Dialable Phone Number
|

Enter the '''User ID''' of the remote server that is configured on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (R - S pages)#SIP Configuration Page|SIP Configuration Page]].
|-
|

SIP Agent Address 1

SIP Agent Address 2
|

IP address of the remote Application Server(s).

The second remote server entry is optional.
|-
|

Routing Unit Number
|

(Optional) Combined with the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add Server Configuration Page and Edit Server Configuration Page|Routing Codec]], the system uses this information to generate an [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#Extended dial prefix|Extended dial prefix]] for the remote server:
* If you set this field to 0, the system uses the value in the Dial prefix field on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (R - S pages)#Table: Field Reference: Remote Server Configuration Page|Remote Server Configuration Page]].
* (Recommended) If you set this field to 0 and leave the Dial prefix field blank, the system generates a default dial prefix.

For details, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#Dial Prefixes|Dial Prefixes]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace|Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace]] module.

Default: 0
|-
|

Routing Codec
|

Select a codec to enable the system to generate an [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#Extended dial prefix|Extended dial prefix]] for the remote server.

To enable the RSNA systems to generate the same extended dial prefix for this server, the same codec must be configured for this particular remote server entry on all RSNA systems:
* (Cisco Unified MeetingPlace Release 8.0 systems) Routing Codec remote server field

Select '''None''' in either of the these cases:
* You want all RSNA systems to use a [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#Common dial prefix|Common dial prefix]].
* You want the system to generate a [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#Default dial prefix|Default dial prefix]] for the remote server.
: For simplicity, we recommend that you configure each RSNA system to use the default dial prefix.

For details, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#Dial Prefixes|Dial Prefixes]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace|Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace]] module.

Default: None
|-
|

Web conferencing enabled
|

Whether web server software is installed and operational on the remote system.

Default: No
|-
|

Web URL
|

URL of the primary Web Server for the remote system.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace|Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#Configuring Endpoints for Cisco Unified MeetingPlace|Configuring Endpoints for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (R - S pages)#Remote Server Configuration Page|Remote Server Configuration Page]]

== Add SNMP Community String Page ==

To find this page, select '''Maintenance > SNMP > Community Strings > Add New'''.

===== Table: Field Reference: Add SNMP Community String Page and Edit SNMP Community String Page =====

{| border = 1
|-
!Field
!Description
|-
|

Community string
|

Name of the SNMP community string.

Restriction: No spaces allowed.
|-
|

Accept SNMP packets from any host
|

Allows the SNMP community string to accept SNMP packets from any host.
|-
|

Accept SNMP packets only from these hosts
|

Allows the SNMP community string to accept SNMP packets only from hosts that you specify.
|-
|

Host IP address
|

If you select the '''Accept SNMP packets only from these hosts''' radio button, enter an IP address and select '''Insert''' to allow the SNMP community string to accept SNMP packets from this host.
|-
|

Host IP addresses
|

If you select the '''Accept SNMP packets only from these hosts''' radio button, this field lists all hosts from which this SNMP community string can accept SNMP packets. To remove a host from this list, highlight the IP address and select '''Remove'''.
|-
|

Access privileges
|

The access privilege given to this SNMP community string. Access privileges provide security by restricting the ability to alter the Cisco Unified MeetingPlace system.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SNMP on the Cisco Unified MeetingPlace Application Server#Configuring SNMP on the Cisco Unified MeetingPlace Application Server|Configuring SNMP on the Cisco Unified MeetingPlace Application Server]] module

== Add SNMP Notification Destination Page ==

To find this page, select '''Maintenance > SNMP > Notification Destinations > Add New'''.

===== Table: Field Reference: Add SNMP Notification Destination Page and Edit SNMP Notification Destination Page =====

{| border = 1
|-
!Field
!Description
|-
|

Destination IP address
|

Restriction: Each notification destination must have a unique IP address.
|-
|

Port number
|

The port number for the notification destination.
|-
|

SNMP version
|

SNMP version 1 supports only traps. SNMP version 2c supports both traps and inform notification types.
|-
|

Notification type
|

Dimmed if you select SNMP version 1.
|-
|

Security level
|

''Display only''. Value is determined by the selected Community string.
|-
|

Community string
|

SNMP community string to associate with this notification destination.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SNMP on the Cisco Unified MeetingPlace Application Server#Configuring SNMP on the Cisco Unified MeetingPlace Application Server|Configuring SNMP on the Cisco Unified MeetingPlace Application Server]] module

== Add Translation Rule Page ==

To find this page, select '''System Configuration > Call Configuration > Auto Attend Translation Configuration > Add New'''.

===== Table: Field Reference: Add Translation Rule Page and Edit Translation Rule Page =====

{| border = 1
|-
!Field
!Description
|-
|

Description
|

Enter information to help you and other system administrators understand the translation rule.

Example: Converts a 7-digit number to a 5-digit extension.
|-
|

Digits to match
|

Number of digits that must be in the incoming ANI (1) in order for this rule to be applied.

Example: Suppose this field is set to 5:
* If the ANI is 50123, the system applies this rule.
* If the ANI is 0123 or 5550123, the system does not apply this rule.

Recommendation: The ANI can vary depending on whether calls are received from internal, external, long distance, or international sources. Use a large enough value to preserve uniqueness for ANI matches. We recommend a value of 4 or 5.

Restriction: You cannot modify the preconfigured translation rule, in which this field is set to 0. The system uses the preconfigured translation rule to find a user profile phone number that matches the incoming ANI exactly without adding or deleting any digits.
|-
|

Match string
|

Apply this rule if this string matches the beginning of the ANI digits.

This string is removed from the ANI.

Example: If this field is set to 555, and the ANI is 5550123, remove the 555 to make the modified ANI equal to 0123.
|-
|

Replace by
|

Insert these digits at the beginning of the ANI.

Example: If this field is set to 5 and the ANI is 0123, the ANI becomes 50123.
|}

Footnote 1: ANI = automatic number ID, or the phone number from which the user called.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Auto Attend Feature for Cisco Unified MeetingPlace#Configuring the Auto Attend Feature for Cisco Unified MeetingPlace|Configuring the Auto Attend Feature for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Auto Attend Translation Configuration Page|Auto Attend Translation Configuration Page]]

== Add User Group Page ==

To find this page, select '''User Configuration > User Groups > Add New'''.

'''Note: ''' Most user group fields are identical to user profile fields. Therefore, [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Group Page and Edit User Group Page|Table: Field Reference: Add User Group Page and Edit User Group Page]] describes only the fields that are specific to user groups. For descriptions of all other user group fields, see [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Table: Field Reference: Add User Profile Page and Edit User Profile Page]].

===== Table: Field Reference: Add User Group Page and Edit User Group Page =====

{| border = 1
|-
!Field
!Description
|-
|

Name
|

Name by which you want to identify the user group.

Recommendation: Use a name that describes the users in the group, such as "Marketing."

Restriction: Unicode is not supported.
|-
|

Number
|

Number used to identify this user group.
|-
|

Phone number for non-direct-dial pagers
|

Shared phone number for a non-direct-dial pager system. (1)

PIN numbers to access individual pagers are configured in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Pager number]] field in individual user profiles.

Restrictions:
* This field applies only to users whose individual user profiles are configured with a non-direct-dial pager PIN number in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Pager type]] field.
* Only these characters are used to call the pager: 0-9, #, and *.
: All other characters are ignored by the system but generate INFO events in the system log.
|-
|colspan="2" rowspan="1"|'''Video Preferences'''
|-
|

Available video types
|

Video type that is made available as the group default in the Video Preferences section of the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add User Profile Page|Add User Profile Page]]. This group default can be inherited by a user profile.

Restriction: If [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Video usage]] is set to [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Can attend + host video meetings]], the fields in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Video Preferences]] section are available.
|-
|

Selected video type details
|

Details about the selected video type including the name, codec type, and bit rates.
|-
|colspan="2" rowspan="1"|All other user group fields are described in [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Table: Field Reference: Add User Profile Page and Edit User Profile Page]].
|}

Footnote 1: The required format for phone numbers is determined by the call-control device for your IP telephony network. Therefore, enter phone numbers in the same format used to dial similar numbers from a phone on the same IP telephony network as Cisco Unified MeetingPlace. For example, if calls within your company are made by dialing the last four digits of a phone number, enter only the last four digits in Cisco Unified MeetingPlace for internal phone numbers. If, however, you want Cisco Unified MeetingPlace to call a phone in a different area code, you might need to include 91 and the complete phone number including the area code.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Profiles and User Groups for Cisco Unified MeetingPlace#Adding or Editing a User Group Manually|Adding or Editing a User Group Manually]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Profiles and User Groups for Cisco Unified MeetingPlace#Configuring User Profiles and User Groups for Cisco Unified MeetingPlace|Configuring User Profiles and User Groups for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Languages for Cisco Unified MeetingPlace#Specifying Languages for Users|Specifying Languages for Users]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Languages for Cisco Unified MeetingPlace#Configuring Languages for Cisco Unified MeetingPlace|Configuring Languages for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Reservationless Meetings|Configuring Reservationless Meetings]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Continuous Meetings|Configuring Continuous Meetings]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Configuring Requirements for Meeting Passwords|Configuring Requirements for Meeting Passwords]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Restricting Access to Scheduled Meetings|Restricting Access to Scheduled Meetings]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Email Notifications for Cisco Unified MeetingPlace#Configuring User Preferences for Email Notifications|Configuring User Preferences for Email Notifications]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Email Notifications for Cisco Unified MeetingPlace#Configuring Email Notifications for Cisco Unified MeetingPlace|Configuring Email Notifications for Cisco Unified MeetingPlace]] module

== Add User Profile Page ==

To find this page, select '''User Configuration > User Profiles > Add New'''.

'''Note: ''' [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Table: Field Reference: Add User Profile Page and Edit User Profile Page]] also describes fields for these pages:
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add User Group Page|Add User Group Page]] and Edit User Group page in the Administration Center
: For information about fields that are specific to user groups (not user profiles), see [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Group Page and Edit User Group Page|Table: Field Reference: Add User Group Page and Edit User Group Page]].
* Add User Profile page and Edit User Profile page in MeetingPlace Conference Manager
: For information about finding these pages in MeetingPlace Conference Manager:
:* [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Adding a User Profile|Adding a User Profile]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Using MeetingPlace Conference Manager|Using MeetingPlace Conference Manager]] module
:* [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Updating a User Profile|Updating a User Profile]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Using MeetingPlace Conference Manager|Using MeetingPlace Conference Manager]] module

===== Table: Field Reference: Add User Profile Page and Edit User Profile Page =====

{| border = 1
|-
!Field
!Description
|-
|colspan="2" rowspan="1"|'''Identification'''
|-
|

First name
|

First name of the user. Used in meeting participant lists and in reports. For the guest profile, used in video labels of live conferences.

The value of this field in the guest profile is applied to guest users. In the guest profile, keep the default value or select a name that clearly indicates a guest meeting participant.

If you are creating a user profile for an auto-answer device, enter "autoanswerdevice" in this field. See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#How to Configure Auto-Answer Devices|How to Configure Auto-Answer Devices]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#Configuring Endpoints for Cisco Unified MeetingPlace|Configuring Endpoints for Cisco Unified MeetingPlace]] module.

Restriction: (Cisco WebEx integration only) Do not leave this field blank.

Defaults for preconfigured user profiles: Guest (guest), Administrator (admin), Voice Recorder (recorder).
|-
|

Last name
|

Last name of the user. Used in meeting participant lists and reports.

The value of this field in the guest profile is applied to guest users. In the guest profile, keep the default value or select a name that clearly indicates a guest meeting participant.

Defaults for preconfigured user profiles: User (guest), Cisco Unified MeetingPlace (admin), Cisco WebEx (recorder).
|-
|

User ID
|

Unique ID by which the user signs in to Cisco Unified MeetingPlace from a workstation.

'''Note: ''' Users enter the User ID and User password to sign in to Cisco Unified MeetingPlace from a workstation. Users enter the Profile number and Profile PIN to authenticate to Cisco Unified MeetingPlace from a touch-tone phone.

Restrictions:
* Unicode is not supported.
* Uppercase characters are automatically converted to lowercase characters.
* If this field is dimmed and marked with a padlock icon, the user is authenticated by an external directory, and you cannot modify this field. See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Profiles and User Groups for Cisco Unified MeetingPlace#Methods for Adding User Profiles|Methods for Adding User Profiles]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Profiles and User Groups for Cisco Unified MeetingPlace#Configuring User Profiles and User Groups for Cisco Unified MeetingPlace|Configuring User Profiles and User Groups for Cisco Unified MeetingPlace]] module.
* For Cisco WebEx integration:
** Special characters such as !@#$%^&() are not supported.
** Do not modify this field in an existing user profile. Doing so disables future sign ins to Cisco WebEx by the user. This is also true for system administrator access to the Cisco WebEx Site Administration.
:: Instead of modifying the User ID, create a new user profile in Cisco Unified MeetingPlace and deactivate the previous user profile through the Cisco WebEx Site Administration.

Defaults for preconfigured user profiles: guest (cannot modify), admin, recorder.
|-
|

User password

User password confirm
|

Password used to sign in to Cisco Unified MeetingPlace from a workstation.

Restrictions:
* Unicode is not supported.
* If this field is dimmed and marked with a padlock icon, the user is authenticated by an external directory, and you cannot modify this field. See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Profiles and User Groups for Cisco Unified MeetingPlace#Methods for Adding User Profiles|Methods for Adding User Profiles]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Profiles and User Groups for Cisco Unified MeetingPlace#Configuring User Profiles and User Groups for Cisco Unified MeetingPlace|Configuring User Profiles and User Groups for Cisco Unified MeetingPlace]] module.
* (Guest profile only) Leave this field blank in the preconfigured guest profile, because this guest profile field is inherited in all new user profiles.
* Password for the admin profile is set during the installation of the Application Server software.

'''Note: ''' If you are adding this information from MeetingPlace Conference Manager, the system permits you to see the password as you type it so that you can easily spell it out to users you are assisting.
|-
|

Last changed
|

''Display only.'' Date when the User password was last modified.

Restriction: This date does not apply to Directory Service users, whose passwords are stored and controlled by an external device. See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Directory Service User Profile Configuration|Directory Service User Profile Configuration]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] module.
|-
|

Force user password change at next sign-in
|

Force a user password change at the next sign-in.

Default: the default value that appears on this page is copied from the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Table: Field Reference: Usage Configuration Page|New users must change passwords on first sign-in]] on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Usage Configuration Page|Usage Configuration Page]].
|-
|

Profile number
|

Unique number that identifies this user profile. Used to authenticate to Cisco Unified MeetingPlace from a touch-tone phone.

Recommendation: Use the phone extension or voice-mail number of the user.

Restrictions:
* If reservationless meetings are enabled on the system, these restrictions apply:
** You cannot configure a profile number that matches an existing meeting ID. Similarly, users will not be able to schedule a meeting whose meeting ID matches an existing profile number.
** If the profile number is longer than 17 digits, the user cannot own reservationless meetings. This is because meeting IDs cannot be longer than 17 digits.
: For more information about reservationless meetings, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Reservationless Meetings|Configuring Reservationless Meetings]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module.
* This field is dimmed for the preconfigured recorder profile. To modify, see [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Configuring the Cisco WebEx Audio Recorder|Configuring the Cisco WebEx Audio Recorder]] 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.

Defaults for preconfigured user profiles: 0000 (guest, cannot modify), 0001 (admin), 0002 (recorder).
|-
|

Profile PIN

Profile PIN confirm
|

PIN used to authenticate to Cisco Unified MeetingPlace from a touch-tone phone.

Set this as a temporary default PIN. Users must change their profile PIN when they first connect to Cisco Unified MeetingPlace.

Restrictions:
* If this field is dimmed and marked with a padlock icon, the user is authenticated by an external directory, and you cannot modify this field. See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Profiles and User Groups for Cisco Unified MeetingPlace#Methods for Adding User Profiles|Methods for Adding User Profiles]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Profiles and User Groups for Cisco Unified MeetingPlace#Configuring User Profiles and User Groups for Cisco Unified MeetingPlace|Configuring User Profiles and User Groups for Cisco Unified MeetingPlace]] module.
* This field is dimmed for the preconfigured guest profile.
* This field is dimmed for the preconfigured recorder profile. To modify, see [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Configuring the Cisco WebEx Audio Recorder|Configuring the Cisco WebEx Audio Recorder]] 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.

'''Note: ''' If you are adding this information from MeetingPlace Conference Manager, the system permits you to see the password as you type it so that you can easily spell it out to users you are assisting.

Default for the admin profile: 24726 (CISCO)
|-
|

Last changed
|

''Display only.'' Date when the Profile PIN was last modified.

Restriction: This date does not apply to Directory Service users, whose passwords are stored and controlled by an external device. See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Directory Service User Profile Configuration|Directory Service User Profile Configuration]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] module.
|-
|

Force PIN change at next sign-in
|

Force a PIN change at the next sign-in.

Default: the default value that appears on this page is copied from the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Table: Field Reference: Usage Configuration Page|New users must change passwords on first sign-in]] on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Usage Configuration Page|Usage Configuration Page]].
|-
|

User status
|

Whether this profile is active, inactive, or locked.

A user with an inactive user profile cannot sign in. The user can still attend meetings that are not restricted to profiled users. See the [[Cisco Unified MeetingPlace Release 8.0 -- Changing the User Status in Cisco Unified MeetingPlace User Profiles#Changing the User Status in Cisco Unified MeetingPlace User Profiles|Changing the User Status in Cisco Unified MeetingPlace User Profiles]] module.

Restriction: The preconfigured admin and recorder profiles cannot be locked.

Default: Group default (Active)
|-
|

Type of user
|

Type of user, the configuration of which restricts the privileges and access available to that user in Cisco Unified MeetingPlace. See the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#About User Types|About User Types]].

Defaults:
* Guest profile: [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users |End user]] (cannot modify)
* Admin profile: [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users |System administrator]] (cannot modify)
* All others: [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users |End user]]
|-
|

Group name
|

Name of user group to which this user profile belongs.

Default: System
|-
|

Email address
|

Email address used in email notifications. Must be in this format:
# a-z, A-Z, 0-9
# Optional:
## One of these characters: _,.,-
## a-z, A-Z, 0-9
# @
# a-z, A-Z, 0-9, -
# .
# a-z, A-Z, 0-9-Only 2-6 characters are allowed at the end

Examples:
* me.myself@example.com
* someone@example.com

Restrictions (Cisco WebEx integration only):
* Cannot exceed 64 characters.
* Must be unique, even among deactivated users on the Cisco WebEx site.

Recommendations:
* Admin profile-Enter a email ''alias''. For Cisco WebEx integration, using a unique email alias will prevent email address conflicts with other user profiles.
* Guest profile-Leave this field blank, because this field is inherited by all new user profiles.
|-
|

Email type and format
|

Determines the following:
* Type of email notification sent to this user for scheduled meetings.
* Format in which this user sends and receives email notifications.

The value of this field in the guest profile is applied to guest users, who in this case are all meeting invitees that are ''not'' invited by profile.

Restriction: To enable the use of the Microsoft Exchange or IBM Lotus Notes formats, you first need to set up the integrations. See one of these documents:
* ''Integration Note for Installing and Configuring IBM Lotus Notes with Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html
* [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal#Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal|Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal]] module

Default: Group default (SMTP (HTML))
|-
|

Main phone number

Alternate phone number
|

Phone number (1) for the system to dial out to the user.

Restrictions:
* Only these characters are allowed:
** numeric
** space ( )
** (),-.
** The + character is allowed only as the first character in the field.
* (Cisco WebEx integration only) Cannot exceed 30 characters.

Recommendation: (Guest profile only) Leave this field blank, because this field is inherited by all new user profiles.
|-
|

Pager number
|

Pager number (1) of user, used for dial-out features. The number you enter depends on the Pager type:
* For a direct-dial pager, enter the phone number that directly reaches the pager.
* For a non-direct-dial pager, enter the PIN used to access the specific pager.
: You configure the shared phone number that the system calls first to reach the pager system in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Group Page and Edit User Group Page|Phone number for non-direct-dial pagers]] field in the user group.

See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Dial-Out Features for Cisco Unified MeetingPlace#How the Find Me Feature Works with Pagers|How the Find Me Feature Works with Pagers]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Dial-Out Features for Cisco Unified MeetingPlace#Configuring Dial-Out Features for Cisco Unified MeetingPlace|Configuring Dial-Out Features for Cisco Unified MeetingPlace]] module.

Restrictions:
* The + character is allowed only as the first character in the field.
* Only these characters are used to call the pager: 0-9, #, and *.
* All other characters are ignored by the system but generate INFO events in the system log.
* See the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Dial-Out Features for Cisco Unified MeetingPlace#Restrictions for Using the Find Me Feature with Pagers|Restrictions for Using the Find Me Feature with Pagers]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Dial-Out Features for Cisco Unified MeetingPlace#Configuring Dial-Out Features for Cisco Unified MeetingPlace|Configuring Dial-Out Features for Cisco Unified MeetingPlace]] module.

Recommendation: (Guest profile only) Leave this field blank, because this field is inherited by all new user profiles.
|-
|

Pager type
|

Type of pager:
* Direct-dial pager-Pager is reached directly by dialing a phone number.
* Non-direct-dial pager-Pager is reached by dialing a phone number ''and'' entering a PIN that specifically identifies the pager.
: You configure the shared phone number that the system calls first to reach the pager system in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Group Page and Edit User Group Page|Phone number for non-direct-dial pagers]] field in the user group.

Default: Direct-dial pager
|-
|

Method of attending
|

The method by which this user joins meetings that are scheduled by this user, reservationless meetings that this user starts, and meetings to which this user is invited by profile.

Options:
* Have user call in-User either calls into meetings or uses the Call Me dial-out feature from the web.
* Have system find user-Enables the Find Me dial-out feature for this user.

Default: Have user call in
|-
|

Search order for find me
|

The order in which the system attempts to call the user for the Find Me dial-out feature.

See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Dial-Out Features for Cisco Unified MeetingPlace#About the Find Me Feature|About the Find Me Feature]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Dial-Out Features for Cisco Unified MeetingPlace#Configuring Dial-Out Features for Cisco Unified MeetingPlace|Configuring Dial-Out Features for Cisco Unified MeetingPlace]] module.

Defaults:
* First: Main phone
* Second: Alternate phone
* Third: Pager
|-
|

User ID of delegate
|

User ID of the person who is allowed to view, reschedule, end, and delete meetings on behalf of this user. Only users of type [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users|Delegate]] can be entered in this field.

If this field is left blank, only users of type [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users|Attendant]] and [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users|System administrator]] can manage meetings on behalf of this user.

Restrictions:
* When a meeting is ''rescheduled'' by a [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users|Delegate]], [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users|Attendant]], or [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users|System administrator]] on behalf of another user, the meeting attributes are not changed unless specifically modified through the More Options page.
* (Microsoft Outlook front-end integration) Specifying the User ID of delegate in a Cisco Unified MeetingPlace user profile does ''not'' automatically enable Microsoft Outlook delegation. You need to separately add assign delegates from the Microsoft Outlook client. For details, see [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Prerequisites for Scheduling From Microsoft Outlook|Prerequisites for Scheduling From Microsoft Outlook]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook|Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook]] module.

Default: Group default (None)
|-
|

Region
|

Geographical region that determines which options become available in the Time zone field.

Default: Other
|-
|

Time zone
|

Time zone in which the user typically conducts business. The drop-down menu options depend on which Region is selected.

Recommendations:
* Do not use the default "Local time of Cisco Unified MeetingPlace server," which is configured during installation and can be modified at any time through the CLI of the Application Server. Instead, set this field to a specific time zone; for example, to PST, EST, AST and so forth. Time discrepancies can occur between meetings that are scheduled before and after each server time change.
* See the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#About Time Zones|About Time Zones]].

Default: Group default (Local time of Cisco Unified MeetingPlace server)
|-
|

Language
|

Select from the languages that were previously installed and activated on the system. See the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Languages for Cisco Unified MeetingPlace#Configuring Languages for Cisco Unified MeetingPlace|Configuring Languages for Cisco Unified MeetingPlace]] module.

The value of this field in the guest profile is applied to guest users.

Default: Group default (English (US))
|-
|

Billing code
|

Billing code that is applied to meetings scheduled by the user. Meeting schedulers can modify the billing code for each meeting. Billing reports are sorted by billing code and then by User ID.

'''Note: ''' If an [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users|Attendant]] or [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users|System administrator]] schedules a meeting on behalf of another user, the meeting uses the billing code of the meeting scheduler, but the system counts the minutes against the meeting owner (on whose behalf the meeting was scheduled).

Recommendations:
* Follow existing conventions at your company, such as department codes.
* (Guest profile only) Leave this field blank, because this field is inherited by all new user profiles.

Default: Group default (None)
|-
|

Default meeting category
|

Meeting category that appears by default on the scheduling page for this user.

Unless you hide the field on the Cisco Unified MeetingPlace web user portal, meeting schedulers can specify the meeting category for each meeting. See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meeting Categories|Configuring Meeting Categories]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module.

Default: Group default (Standard)
|-
|

Schedule home server
|

Local Cisco Unified MeetingPlace Application Server assigned to this user.

When the user schedules a meeting, the system attempts to schedule the meeting through this Application Server first. If the server does not have enough resources, the system tries another Application Server, for example, a remote RSNA system.

Requirement: This number must match the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add Server Configuration Page and Edit Server Configuration Page|Home Server number]] that identifies this server.

'''Note: ''' If you want to assign an [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#RSNA Reserved Meeting Server|RSNA Reserved Meeting Server]] to this user, make sure that the system has two remote server records for the reserved meeting server: one with a [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add Server Configuration Page and Edit Server Configuration Page|Home Server number]] in the range 0 to 999, and one with a checked [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add Server Configuration Page and Edit Server Configuration Page|Reserved Meeting Server]] check box. For details, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#RSNA Reserved Meeting Server|RSNA Reserved Meeting Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace|Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace]] module.

Default: Group default (0)
|-
|colspan="2" rowspan="1"|'''Permissions'''
|-
|

Use reservationless
|

Whether the user can own reservationless meetings.

Default: Group default (Yes)
|-
|

Maximum meeting length (minutes)
|

User cannot schedule meetings longer than this number of minutes.

Restrictions:
* This field does not apply to continuous meetings.
* If this value differs from the following, the system uses the lowest value:
** [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Meeting Configuration Page|Maximum meeting length (minutes)]] field on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Meeting Configuration Page|Meeting Configuration Page]].
** Maximum Call Duration Timer service parameter in Cisco Unified Communications Manager.
:: See [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager#Configuring the Maximum Call Duration in Cisco Unified Communications Manager|Configuring the Maximum Call Duration in Cisco Unified Communications Manager]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager#Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager|Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager]] module.
* If your User Groups Maximum meeting length setting is lower than your User Profiles setting your User Groups setting is used. Your User Profiles setting must be lower than your User Groups setting.

Default: Group default (240)
|-
|

Scheduling restriction (meetings to start within 6 hours of scheduling)
|

Scheduling restrictions for this user:
* Unrestricted-User can schedule an unlimited number of meetings.
* Cannot schedule-User cannot schedule meetings, regardless of start time.
* ''Numeric value''-Maximum number of meetings that the user can schedule to begin within six hours after the time of scheduling.
: Each time the user attempts to schedule a meeting, the system counts the number of meetings owned by the user that are scheduled to begin within the next six hours. If this number is greater than the field value, the user cannot schedule any more meetings to begin within the next six hours. Note that the user can still schedule an unlimited number of meetings to begin more than six hours after the time of scheduling.

Default: Group default (Unrestricted)
|-
|

Can change meeting ID via phone
|

Whether the user can change the meeting ID over the phone for meetings owned by the user.

Default: Group default (Yes)
|-
|

Video usage
|

Whether the user can attend or attend and host video meetings.
* Can attend video meetings
** User can attend video-enabled meetings as a video participant.
** User ''cannot'' schedule meetings that allow video participants.
* Can attend + host video meetings
** User can attend video-enabled meetings as a video participant.
** User schedules video-enabled meetings, which means that video participants can attend.

'''Note: ''' When you select Can attend + host video meetings, you can specify options in the Video Preferences section.

Default: Can attend video meetings
|-
|

Can dial out (does not apply to Cisco WebEx meetings)

or, in guest profile:

Can dial out
|

Whether dial-out privileges are enabled or disabled for this user.

'''Note: ''' Dial-out privileges from the Cisco WebEx site are determined by the Cisco Unified MeetingPlace ''guest'' profile, not by individual user profiles.

Default: Group default (Yes)
|-
|

Maximum TUI dial-out attempts per meeting
|

Maximum number of TUI (#31) dial-out calls that this user can attempt from within a meeting.
* Failed dial-out attempts from the TUI count against this number.
* Dial-out attempts from the web meeting room do ''not'' count against this number.

A value of 0 means that the user cannot press #3 to dial out from within a meeting.

Default: Group default (Unrestricted)
|-
|

Can send notifications
|

Whether notifications are sent for meetings scheduled by the user through Cisco Unified MeetingPlace.

Restriction: Notifications are never sent for reservationless meetings.

Recommendations: Use a consistent setting across your user base. Also, avoid changing this setting once Cisco Unified MeetingPlace is in use because users might expect and rely on the current email notification behavior.

Default: Group default (Yes)
|-
|

Can receive notifications
|

Whether to send email notifications to the user through Cisco Unified MeetingPlace.

Recommendations: Use a consistent setting across your user base. Also, avoid changing this setting once Cisco Unified MeetingPlace is in use because users might expect and rely on the current email notification behavior.

Default: Group default (Yes)
|-
|

Auto attend mode
|

Enables or disables the auto attend feature for the user. When enabled, you specify whether the caller automatically joins meetings or is only authenticated.

For details, see the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Auto Attend Feature for Cisco Unified MeetingPlace#Configuring the Auto Attend Feature for Cisco Unified MeetingPlace|Configuring the Auto Attend Feature for Cisco Unified MeetingPlace]] module.

Default: Group default (None)
|-
|

Auto attend requires profile PIN
|

When the auto attend feature is enabled, this field specifies whether the user must enter the Profile PIN before being automatically authenticated or placed into meetings.

Default: Group default (Yes)
|-
|

Meeting password required
|

Whether scheduled and reservationless meetings owned by this user require a meeting password.

Restrictions:
* This field is ignored if the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Meeting Configuration Page|Minimum meeting password length]] field on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Meeting Configuration Page|Meeting Configuration Page]] is set to 0.
* In reservationless meetings, meeting passwords are not required to join the web meeting room.

Default: Group default (No)
|-
|

Can record meetings
|

Determines who can record meetings:
* If set to Yes, the user can start and stop the recording of any meeting from the TUI, regardless of who scheduled the meeting.
* If set to No, the user cannot start or stop meeting recordings.

'''Note: ''' For Cisco WebEx integrated deployments, when Cisco MeetingPlace is configured to use Cisco WebEx for scheduling, this field is not available and the TUI cannot start/stop any recordings.

Restriction (guest profile only): When set to Yes, this field enables guest users to start and stop meeting recordings:
* From the TUI.
* Only if the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Table: Field Reference: Usage Configuration Page |Guests can lock and record meetings]] field on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Usage Configuration Page|Usage Configuration Page]] is also set to Yes.

Default: Group default (No)
|-
|colspan="2" rowspan="1"|'''Recordings'''
|-
|

Who can access
|

Who can listen to recordings for scheduled meetings owned by this user.

Restriction: This field does not apply to reservationless meetings. Anyone can access reservationless meeting recordings.

Default: Group default (Anyone)
|-
|

Auto-start recording
|

When set to Yes, the system automatically records all meetings that are scheduled by the user.

When set to No, a meeting participant (with recording privileges) must manually start the recording.

Restrictions:
* This field is always set to No when the Can record meetings field is set to No.
* This field is not available when a Cisco WebEx site is configured.

Default: Group default (No)

'''Note: ''' When you reconfigure your deployment from Audio/video only to a WebEx-managed deployment, auto-start recording is still configured regardless of user profile settings.

|-
|colspan="2" rowspan="1"|'''Meeting Preferences'''
|-
|

Entry announcement
|

Announcement played when callers join meetings scheduled by this user.

Default: Group default (Beep + name)
|-
|

Departure announcement
|

Announcement played when callers leave meetings scheduled by this user.

Default: Group default (Beep + name)
|-
|

Meeting entry mode
|

Whether participants hear one, both, or none of the following items when they join the audio portion of meetings scheduled by this user:
* Meeting ID confirmation
* Name recording option

Restriction: Participants who automatically join a meeting through the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Auto Attend Feature for Cisco Unified MeetingPlace#Auto Attend Feature|Auto Attend Feature]] will hear the meeting ID confirmation, even if the Meeting entry mode for the meeting is configured to skip the meeting ID.

Recommendation: For Cisco WebEx integration, select '''Skip ID repeat and skip names'''. Otherwise, users will be required to record a name each time they use a dial-out call from the Cisco WebEx site to join meetings scheduled by this user. This is because Cisco WebEx dial-out calls are not associated with individual Cisco Unified MeetingPlace user profiles, even when users are properly signed in over the web.

Default: Group default (Skip ID repeat)
|-
|

Who may skip password
|

Specifies who can join a meeting scheduled by this user without entering a meeting password.

Default: Group default (Nobody)
|-
|

Who can attend
|

Specifies who can attend meetings scheduled by this user.

Restrictions:
* This field is ignored for reservationless meetings, which anyone can attend.
* If meeting attendance is restricted to profiled users, then:
** Unprofiled external users (such as your customers or business partners) and users with locked profiles cannot attend meetings, even if they are invited.
** Only those who successfully authenticate to Cisco Unified MeetingPlace can attend these meetings.

Default: Group default (Anyone)
|-
|

Show meetings in public listing
|

Whether to publicly list the meetings scheduled by this user in the Cisco Unified MeetingPlace web user portal.

Unless you hide the field on the web user portal, meeting schedulers can override this setting.

Default: Group default (No)
|-
|

Show reservationless meetings in public listing
|

Whether to publicly display reservationless meetings owned by this user in the web user portal.

Default: Group default (Yes)
|-
|

Can host web meetings
|

Whether to provide the Cisco WebEx web meeting room with audio and video, or an audio and video meeting only.
* Yes-Cisco WebEx web meeting room including audio and video
* No-audio and video meeting only; no meeting room

'''Note: ''' This field applies to both scheduled and reservationless meetings set up through the Cisco WebEx interface.

Restriction: If the user is signed in when this field is modified, the previous setting applies until the user signs out and signs in again.

Default: Group default (Yes)
|-
|

End of meeting announcement
|

Whether the end-of-meeting announcement is played in meetings scheduled by this user.

Default: Group default (No)
|-
|

Meeting extension announcement
|

Whether meeting-extension announcements are played in meetings scheduled by this user.

Default: Group default (No)
|-
|

Screened entry
|

Whether screened entry is enabled in meetings scheduled by this user.

Default: Group default (No)
|-
|

Disable roll call
|

Whether to disable roll call in meetings scheduled by this user.

Default: Group default (No)
|-
|

Allow Internet access
|

Whether, by default, the meetings of this user will be scheduled on a Web Server in the DMZ.
* Yes-By default, meetings scheduled by this user are held on the Web Server in the DMZ and are accessible by anyone on the Internet or intranet.
* No-By default, meetings scheduled by this user are held on the Web Server in the intranet and are accessible by anyone on the intranet only.

'''Note: ''' Users can change this value at schedule time and schedule web meetings on the Internet or intranet.

Default: Group default (No)
|-
|

Reservationless allow Internet access
|

Whether this user can host reservationless meetings on a Web Server in the DMZ.
* Yes-User can host reservationless web meetings that are accessible by anyone on the Internet or intranet.
* No-User can host reservationless web meetings for users on the intranet only.

'''Note: ''' Users can change this value at schedule time and schedule web meetings on the Internet or intranet.

Default: Group default (Yes)
|-
|colspan="2" rowspan="1"|'''Video Preferences'''
|-
|

Available on the system
|

List of video types available on the system. The list includes video types that are preconfigured on the system and all the video types you added through the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add Video Type Page|Add Video Type Page]].

Restriction: If Video usage is set to Can attend + host video meetings, the fields in the Video Preferences section are available.
|-
|

Available to the user
|

The video types listed in the '''Available to the user''' box appear in the web user portal.

To add a video type that is listed in the '''Available on the system''' box to the '''Available to the user''' box, perform one of these actions:
* Highlight the video type, and select the arrow between the tables.
* Double-click the video type.

You can remove a video type (except for the Group default) from the '''Available to the user''' table by double-clicking it or by clicking the left arrow. See Restrictions.

You can change the order of the video types by selecting the up and down arrow keys. The video codec that is listed first is the default, and the system tries to use this one first.

You can make the Group default video type available to the user profile if these conditions are met:
* If the User group for this user has Video usage set to Can attend + host video meetings on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add User Group Page|Add User Group Page]].
* If the User profile for the user has Video usage set toCan attend + host video meetings on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add User Profile Page|Add User Profile Page]].
* The Group default type becomes the default for the user when it is the first entry in the Available to the user list.

Restrictions: You cannot remove the Group default video type from the list. If you do not want to use it, you can move it to the bottom of the list.

Default: Group default
|-
|

Selected video type details
|

Displays details about the highlighted video type.
|-
|colspan="2" rowspan="1"|'''Notifications'''
|-
|

Priority
|

Priority of email notifications for meetings scheduled by the user.

Default: Group default (Normal)
|-
|

Send if meeting changes
|

Whether email notifications are sent when the following parameters change for meetings scheduled by the user through Cisco Unified MeetingPlace:
* Date or time
* Password
* Meeting ID
* List of invitees

Recommendations: Use a consistent setting across your user base. Also, avoid changing this setting once Cisco Unified MeetingPlace is in use because users might expect and rely on the current email notification behavior.

Default: Group default (Yes)
|-
|

Include invitee list when scheduled from web
|

Whether to include a list of invitees in email notifications for meetings that the user schedules from the Cisco Unified MeetingPlace web user portal.

Note that a list of meeting invitees is ''not'' included in email notifications for meetings that are scheduled from IBM Lotus Notes or the Microsoft Outlook calendar. Users can view the list of invitees through the Microsoft Outlook Scheduling tab.

Default: Group default (Yes)
|-
|

Include meeting password
|

Whether the meeting password (if any) is included in email notifications for meetings scheduled by the user.

Default: Group default (No)
|-
|colspan="2" rowspan="1"|'''Flex Fields'''
|-
|colspan="2" rowspan="1"|If profile flex fields are configured, they appear in this area. See the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Flex Fields for Cisco Unified MeetingPlace#Configuring Flex Fields for Cisco Unified MeetingPlace|Configuring Flex Fields for Cisco Unified MeetingPlace]] module.
|}

Footnote 1: The required format for phone numbers is determined by the call-control device for your IP telephony network. Therefore, enter phone numbers in the same format used to dial similar numbers from a phone on the same IP telephony network as Cisco Unified MeetingPlace. For example, if calls within your company are made by dialing the last four digits of a phone number, enter only the last four digits in Cisco Unified MeetingPlace for internal phone numbers. If, however, you want Cisco Unified MeetingPlace to call a phone in a different area code, you might need to include a 9 and the complete phone number including the area code.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring User Profiles and User Groups for Cisco Unified MeetingPlace#Configuring User Profiles and User Groups for Cisco Unified MeetingPlace|Configuring User Profiles and User Groups for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Audio and Video Recordings for Cisco Unified MeetingPlace#Configuring Audio and Video Recordings for Cisco Unified MeetingPlace|Configuring Audio and Video Recordings for Cisco Unified MeetingPlace]] module
* [[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 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Dial-Out Features for Cisco Unified MeetingPlace#Configuring Dial-Out Features for Cisco Unified MeetingPlace|Configuring Dial-Out Features for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Flex Fields for Cisco Unified MeetingPlace#Configuring Flex Fields for Cisco Unified MeetingPlace|Configuring Flex Fields for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace#Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace|Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace]] module

=== Reference Information about User Profile Fields ===
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#About User Types|About User Types]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#About Time Zones|About Time Zones]]

==== About User Types ====

The [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Type of user]] field in each user profile determines the user privileges and capabilities in Cisco Unified MeetingPlace. See [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Types of Users|Table: Types of Users]].

===== Table: Types of Users =====

{| border = 1
|-
![[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Type of user]]
!Description
|-
|

End user
|
* Can schedule and control meetings, attend meetings to which they have been invited, attend any publicly listed meeting, and modify preferences in their own user profiles.
* Cannot access the Administration Center or MeetingPlace Conference Manager.
|-
|

Delegate
|
* Can view, reschedule, end, or delete meetings on behalf of users whose user profiles specify that delegate in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|User ID of delegate]] field.
* Can change the permissions of invitees for meetings owned by users whose user profiles specify that delegate in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|User ID of delegate]] field.
* Cannot ''schedule'' meetings on behalf of other users, even those whose user profiles specify that delegate in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|User ID of delegate]] field.
* Cannot access the Administration Center or MeetingPlace Conference Manager.

'''Note: ''' (Microsoft Outlook front-end integration) Specifying the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|User ID of delegate]] in a Cisco Unified MeetingPlace user profile does ''not'' automatically enable Microsoft Outlook delegation. You need to separately add assign delegates from the Microsoft Outlook client. For details see [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Prerequisites for Scheduling From Microsoft Outlook|Prerequisites for Scheduling From Microsoft Outlook]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook|Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook]].
|-
|

Attendant
|
* Can view, schedule, reschedule, end, and delete meetings on behalf of all users.
* Has limited access to the Administration Center, depending on the configured [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Table: Field Reference: Usage Configuration Page|Attendant Privileges]] on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Usage Configuration Page|Usage Configuration Page]].
* Can download and use MeetingPlace Conference Manager, though capabilities are affected by the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Table: Field Reference: Usage Configuration Page|Attendant Privileges]] on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Usage Configuration Page|Usage Configuration Page]].
|-
|

System administrator
|
* Can join ''any'' meeting, even if the maximum number of ports per meeting are in use, as long as floater ports are available. Can join password-protected meetings without the meeting password, even if uninvited.
* Can view, schedule, reschedule, end, and delete meetings on behalf of all users.
* Has full access to the Administration Center.
* Can download and use MeetingPlace Conference Manager.

Restriction: The preconfigured ''admin'' profile provides access only to the Administration Center on the Application Server. It does not provide access to the Web Administration on the Web Server.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add User Group Page|Add User Group Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add User Profile Page|Add User Profile Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Attendant Settings for Cisco Unified MeetingPlace#Configuring Attendant Privileges|Configuring Attendant Privileges]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Attendant Settings for Cisco Unified MeetingPlace#Configuring Attendant Settings for Cisco Unified MeetingPlace|Configuring Attendant Settings for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Using MeetingPlace Conference Manager|Using MeetingPlace Conference Manager]] module

==== About Time Zones ====

Each user profile has a [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Time zone]] setting. Things you should know about time zones in Cisco Unified MeetingPlace:
* After you install Cisco Unified MeetingPlace Release 8.0, it assigns a special attribute to any scheduled meeting. This attribute is the time requested by the scheduler in their local time zone along with the time zone; for example, "12/10/2009 3:00 PM America/Los_Angeles."
: When you perform a daylight saving or time zone (DST/TZ) update on the Application Server, meetings with this special attribute are automatically changed according to the new DST/TZ definition if the user profile of the scheduler is in the time zone that had the DST/TZ update.
: However, meetings that were scheduled before you installed Cisco Unified MeetingPlace Release 8.0 do not have this attribute and are not automatically changed when you perform a DST/TZ update. The system sends email notifications for meetings that were originally scheduled through the Lotus Notes or Microsoft Outlook interface to the scheduler. The notifications inform the schedulers that their meetings are affected by DST and that they need to delete and reschedule the affected meetings. For meetings that are impacted by DST and that were originally scheduled through the web user portal or through MeetingPlace Conference Manager, the system sends an update notification to the scheduler and to all other invitees in the meeting.
: Note that meetings scheduled by users configured to use "local time" are not updated (as described next).
* Do not use the default "Local time of Cisco Unified MeetingPlace server," which is configured during installation and can be modified at any time through the CLI of the Application Server. Instead, set this field to a specific time zone.
* For each meeting, Cisco Unified MeetingPlace accepts and reports the start time in the time zone of the meeting scheduler.
* All email notifications use the time zone of the meeting scheduler, even those that are sent to invitees in different time zones.
* On the Find Meeting and Meeting Details pages in the web user portal, the meeting times appear in the time zone of the user who is signed into the web user portal.
* All instances of recurring meetings take place at the same time of day in the time zone configured in the user profile of the meeting scheduler. Meeting invitees must adjust for time zone differences. Remember that some locations, such as Arizona, do not use daylight saving time.
* Time zones for users and groups are not retained after migration.
* You download time-zone tables from Cisco.com.
** Load the Linux time-zone update on the Cisco Unified MeetingPlace Application server so that correct times are sent in email notifications.
** For clients running MeetingPlace Conference Manager, load the time-zone update provided by Sun Microsystems so that meeting times are displayed correctly in MeetingPlace Conference Manager after a time-zone rule change.
: '''Note: ''' After installing the time-zone updates on the Application Server, you must restart this server.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add User Group Page|Add User Group Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add User Profile Page|Add User Profile Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Troubleshooting Time and Time Zone Issues for Cisco Unified MeetingPlace#Troubleshooting Time and Time Zone Issues for Cisco Unified MeetingPlace|Troubleshooting Time and Time Zone Issues for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Time and Time Zones for Cisco Unified MeetingPlace#Configuring Time and Time Zones for Cisco Unified MeetingPlace|Configuring Time and Time Zones for Cisco Unified MeetingPlace]] module

== Add Video Terminal Profile Page ==

To find this page, select '''User Configuration > Video Terminal Profiles > Add New'''.

===== Table: Field Reference: Add Video Terminal Profile Page and Edit Video Terminal Profile Page =====

{| border = 1
|-
!Field
!Description
|-
|colspan="2" rowspan="1"|'''Identification'''
|-
|

Video terminal name
|

Name used in meeting participant lists and reports. For example, enter the name or location of the conference room that contains the video terminal.

Recommendation: Consider adding text that reflects the Method of attending field value, so that meeting schedulers can perform these actions:
* If multiple video terminals are required for a meeting, the meeting scheduler might want to invite video terminals that have the same Method of attending.
* If the Method of attending is set to Have terminal call in, the meeting scheduler might want to invite only video terminals and no users. Any users who are invited will also be dialed out when a meeting participant (with dial-out privileges) enters #33 in the TUI.

Restriction: At most, only the first 60 characters of the Video terminal name will appear on the scheduling page. Depending on the specific web browser and window size, even a smaller number of characters might appear. Therefore, make sure that you use concise video terminal names.
|-
|

Endpoint E.164 number
|

Phone number (1) for the system to dial out to the video endpoint.

Restriction: Only these characters are allowed: (),-. and 0-9.
|-
|

Group name
|

Name of user group to which this VTP (2) belongs.

Default: System
|-
|

Email address
|

Where to send email notifications when this video terminal is invited to a meeting. Typically, you configure this field with the address of help desk staff or whoever is in charge of reserving the video terminal and conference room.

(Microsoft Outlook integration only) See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#Requirements for Inviting Video Terminal Profiles from Microsoft Outlook|Requirements for Inviting Video Terminal Profiles from Microsoft Outlook]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#Configuring Endpoints for Cisco Unified MeetingPlace|Configuring Endpoints for Cisco Unified MeetingPlace]] module.

For format requirements, see the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Email address]] user profile field.
|-
|

Region
|

See the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Region]] user profile field.

Default: Other
|-
|

Time zone
|

See the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Time zone]] user profile field.

Default: Group default (Local time of Cisco Unified MeetingPlace server)
|-
|

Skip meeting entry voice prompts for dial-out calls
|

Whether this video terminal joins meetings directly without hearing voice prompts to record a name or enter a password.

Restriction: This field applies only when the Method of attending field is set to Dial out to terminal at meeting start.

Recommendation: Select Yes if any of these statements are true:
* You want to configure the VTP for [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#Direct-to-Meeting Mode for Invited Terminals|Direct-to-Meeting Mode for Invited Terminals]].
* The video terminal is incapable of using the TUI.
* Your users are not proficient with this video terminal.

Default: Yes
|-
|

Method of attending
|

The method by which this video terminal joins meetings:
* (Recommended) Dial out to terminal at meeting start-System dials out to the video terminal at meeting start. Use this setting for [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#Direct-to-Meeting Mode for Invited Terminals|Direct-to-Meeting Mode for Invited Terminals]].
* Have terminal call in-Video terminal can join meetings in any of the these ways:
** (Recommended) Meeting owner dials out to all missing invitees by entering '''#33''' in the TUI. Only meeting participants with dial-out privileges can perform this task. This is the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#Alternative to Direct-to-Meeting Mode for Invited Terminals|Alternative to Direct-to-Meeting Mode for Invited Terminals]].
** User calls into the meeting from this video terminal.
** Meeting participant dials out to the phone number (Endpoint E.164 number) of the video terminal. This can be performed from the web meeting room or by entering '''#31''' in the TUI. Only meeting participants with dial-out privileges can perform this task.

Restriction: Some video terminals might not successfully negotiate video unless one of the recommended options are used.

Default: Have user call in
|-
|

Video terminal codec
|

This option is available only when the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Type of media server]] is set to Hardware Media Server.

Which codec to use when the video terminal dials directly in to Cisco Unified MeetingPlace, or when the system dials directly out to the video terminal:
* H.261
* H.263
* H.264
* Use default (H.264)

Restrictions:
* The selected codec is ''not'' applied to calls that are transferred to Cisco Unified MeetingPlace from another phone. For transferred calls, Cisco Unified MeetingPlace uses the Video terminal codec in the VTP associated with the originally connected phone or terminal, not the terminal that is transferred.
* H.261 is available only when a meeting is using the High Rate video type. If a meeting is using the Standard Rate video type and a video with Video terminal codec is set to H.261, this video terminal uses H.263 instead.

Default: H.264
|-
|colspan="2" rowspan="1"|'''Notifications'''
|-
|

Can receive notifications
|

Whether to send email notifications to the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Email address]] in this VTP.

Recommendations: Avoid changing this setting once Cisco Unified MeetingPlace is in use, because users might expect and rely on the current email notification behavior.

Default: Group default (Yes)
|-
|

Receive attachments
|

Whether to include attachments in email notifications sent to the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Email address]] in this VTP.

Default: Group default (No)
|}

Footnote 1: The required format for phone numbers is determined by the call-control device for your IP telephony network. Therefore, enter phone numbers in the same format used to dial similar numbers from a phone on the same IP telephony network as Cisco Unified MeetingPlace. For example, if calls within your company are made by dialing the last four digits of a phone number, enter only the last four digits in Cisco Unified MeetingPlace for internal phone numbers. If, however, you want Cisco Unified MeetingPlace to call a phone in a different area code, you might need to include a 9 and the complete phone number including the area code.

Footnote 2: VTP = video terminal profile

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Video Terminal Profiles Page|Video Terminal Profiles Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#Adding or Editing a Video Terminal Profile|Adding or Editing a Video Terminal Profile]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#Configuring Endpoints for Cisco Unified MeetingPlace|Configuring Endpoints for Cisco Unified MeetingPlace]] module

== Add Video Type Page ==

To find this page, select '''System Configuration > Video Type Management > Add New''' or select '''System Configuration > Video Type Management''' and select '''Edit''' next to the video type that you want to modify.

You make these video types available to users through [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Video Preferences]] on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add User Profile Page|Add User Profile Page]] and the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add User Group Page|Add User Group Page]]. Users are required to select a video format when they schedule a meeting.

===== Table: Field Reference: Add Video Type Page and Edit Video Type Page =====

{| border = 1
|-
!Field
!Description
|-
|

Video format name
|

Name of this video format. This name appears on the user configuration pages and must be unique.

For details about these video formats and the user experience, see the'' Planning Guide for Cisco Unified MeetingPlace''.
|-
|

Video mode
|

Select a video mode from the list.

When the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Type of media server]] is set to Express Media Server, these preconfigured video modes are available:
* H.263
* Mobile
* Compatibility
* High Quality
* HD

When the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Type of media server]] is set to Hardware Media Server, these preconfigured video modes are available:
* Standard Rate
* High Rate

Restrictions:
* When the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Type of media server]] is set to Express Media Server, use this page to add a new video type. You can modify only the video types that you add to the system. You cannot modify the preconfigured ones.
* When the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Type of media server]] is set to Hardware Media Server, you cannot modify preconfigured video types or create new video types.

Default:
* Compatibility (when the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Type of media server]] is set to Express Media Server)
* Standard Rate (when the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Type of media server]] is set to Hardware Media Server)
|-
|

Minimum bit rate (kbps)
|

The minimum video bit rate that will be assigned to meetings using the selected format. The minimum rate is determined by the Video mode selected.

This is used to prevent endpoints from establishing a video session with a low bit rate that could degrade the quality of the meeting. If the video endpoint cannot meet the minimum bit rate, the system treats it as an audio-only endpoint.

Default: depends on the Video mode selected
|-
|

Maximum bit rate (kbps)
|

The maximum bit rate at which a video caller can connect to the system. The maximum rate is determined by the Video mode selected.

If you allocate more bandwidth, the user requires more SRUs.

Meeting participants cannot join at a rate higher than the value of this field. If a participant joins at a rate lower than the value of the maximum bit rate, the system retains the additional SRUs allowing additional participants to join the meeting.

Only signaled rates are taken into account. Flow-controlled bit rates are not taken into account. For example, if a meeting was scheduled with a maximum bit rate of 768 kbps, and a caller joins at that rate and the system later sets the flow to a lower rate, the unused capacity is not returned to the system.

Restriction: The maximum bandwidth of video calls can also be limited by the following settings, the lowest of which is enforced:
* Video Call Bandwidth region parameter in Cisco Unified Communications Manager. See [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager#Configuring the Maximum Video Call Bandwidth in Cisco Unified Communications Manager|Configuring the Maximum Video Call Bandwidth in Cisco Unified Communications Manager]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager#Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager|Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager]] module.
* Bandwidth capabilities and configurations of the video endpoints.

Default: depends on the Video mode selected
|-
|

Note
|

Section for notes about this video; for example, under which conditions it should be used.

Restriction: This field is not available when the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Type of media server]] is set to Hardware Media Server.

Default: Blank
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Video Type Management Page|Video Type Management Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module
* ''Planning Guide for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_implementation_design_guides_list.html

== Alarms Page ==

Use this page to display the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Alarm Table|Alarm Table]] and clear alarms. To find this page, select '''Services > Alarms'''.

===== Table: Field Reference: Alarms Page =====

{| border = 1
|-
!Field
!Description
|-
|

Severity
|

Magnitude of the alarm. Can be major or minor.
|-
|

Code
|

Exception code.
|-
|

Count
|

Number of alarms that were combined into the one table entry.
|-
|

First Time
|

When the alarm was first added to the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Alarm Table|Alarm Table]], not including any alarms that were previously cleared.
|-
|

Last Time
|

When the most recent alarm occurred for this table entry.
|-
|

Unit
|

Unit number reporting the alarm.
* This is always 0 for alarms generated within the Application Server.
* For alarms that are reported through the Cisco Unified MeetingPlace Gateway System Integrity Manager (Gateway SIM), this is the unit number used by Gateway SIM to identify the device.
|-
|

Software Module
|

Number that identifies a specific software module.
|}

'''Note: ''' The brief description for the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Alarm Table|Alarm Table]] entry might contain values that are specific to one alarm occurrence, such as an IP address. These values might differ in all alarms that are combined into one table entry, but only the values for the ''first'' alarm are displayed. To see the individual alarms, view the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception Log|Exception Log]].

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using Alarms and Logs on Cisco Unified MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module
* ''Alarm and Exception Code Reference for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_technical_reference_list.html
* [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Module Numbers|Module Numbers]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using Alarms and Logs on Cisco Unified MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module

== Auto Attend Translation Configuration Page ==

Use this page to define Automatic Number Identification (ANI) translation rules for the auto attend feature. These translation rules enable the system to match different ANI formats to the phone numbers in user profiles.

To find this page, select '''System Configuration > Call Configuration > Auto Attend Translation Configuration'''.

===== Table: Navigation Reference: Auto Attend Translation Configuration Page =====

{| border = 1
|-
!To
!Do This
|-
|

Sort by number of digits to match, string to match, or string to replace with
|

Select the '''Digits to match''', '''Match string, '''or '''Replace by '''column heading.
|-
|

Change the alphanumeric sort order to ascending or descending
|

Select the column heading to change the arrow direction:
* Down arrow-ascending sort
* Up arrow-descending sort
|-
|

Display a shorter or longer list of auto attend translation rules in one view
|

At the bottom of the page, in the Rows per page field, select the number of entries to display.
|-
|

Display a different page of auto attend translation rules
|

At the bottom of the page, perform one of these actions:
* In the Go field, enter the page number to display, and select '''Go'''.
* Select the arrows to page through the list.
|-
|

Edit an existing auto attend translation rule
|

Select '''edit''' in the same row as the auto attend translation rule.
|-
|

Create a new auto attend translation rule
|

Select '''Add New'''.
|-
|

Delete one or more auto attend translation rule
|

Check the appropriate check boxes in the far left column, and select '''Delete Selected'''.

Restriction: You cannot delete the preconfigured translation rule, in which the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add Translation Rule Page and Edit Translation Rule Page|Digits to match]] field is set to 0. The check box is dimmed for the preconfigured auto attend translation rule.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Auto Attend Feature for Cisco Unified MeetingPlace#Configuring the Auto Attend Feature for Cisco Unified MeetingPlace|Configuring the Auto Attend Feature for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add Translation Rule Page|Add Translation Rule Page]]

== Backup and Archive Page ==

Use this page to configure automatic system backups and archiving. To find this page, select '''Maintenance > Backup and Archive'''.

===== Table: Field Reference: Backup and Archive Page =====

{| border = 1
|-
!Field
!Description
|-
|

Enable automatic backup
|

Default: Yes
|-
|

Enable automatic archiving
|

Whether to automatically archive the database after a backup.

Default: No
|-
|

Archiving method
|

Whether to enable archiving through FTP or SSH/rsync.

Default: Remote (SSH/rsync)
|-
|

Pathname location of archive
|

Directory in which the archived database is saved.

Requirement: Include a leading slash before the directory name.

Example: '''/folder_name'''
|-
|

Remote archive host
|

Host name or IP address of the remote server to which the files are archived.
|-
|

Remote host user ID

Remote host password
|

User ID and password to authenticate to the remote server.

Requirement: Use an account that has the privileges to create, access, and write to directories.
|-
|

Notification email
|

Email address to which the system sends archive execution status.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module

== Billing Report Page ==

The Billing Report page provides billing information for all meetings held in the specified date range. To find this page, select '''Reports > Billing Report'''.

===== Table: Field Reference and Output Field Reference: Billing Report Page =====

{| border = 1
|-
!Field
!Description
|-
|

Report type
|

Output format, either text or HTML.
|-
|

Destination
|

Output destination. For restrictions and recommendations for each option, see [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Reports and Exported Data|Reports and Exported Data]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Running Reports and Exporting Data from Cisco Unified MeetingPlace|Running Reports and Exporting Data from Cisco Unified MeetingPlace]] module.
|-
|

Billing code
|

See [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Billing code]].
|-
|

Start date
|

Default: yesterday (mm/dd/yyyy)
|-
|

End date
|

Default: today (mm/dd/yyyy)
|-
|

Billing rate (voice)
|

Billing rate, in cents, used to calculate the usage cost for voice meetings.

Default: 20
|-
|

Billing rate (video)
|

Billing rate, in cents, used to calculate the usage cost for video meetings.

Default: 20
|-
|colspan="2" rowspan="1"|'''Check Boxes and Output Fields'''
|-
|

Show all fields
|

Displays all fields in the report output.

Unchecking this clears all check boxes, except [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Billing code]], Owner ID, and Meeting ID.
|-
|

Billing code
|

''Display only''. See [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Billing code]].
|-
|

Owner ID
|

''Display only''. [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|User ID]] of the meeting owner.
|-
|

Owner name
|

[[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Last name]] and [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Add User Profile Page and Edit User Profile Page|First name]] of the meeting owner.
|-
|

Date/time
|

Date and time the meeting started.
|-
|

Meeting ID
|

''Display only''. Meeting ID, which uniquely identifies the meeting.
|-
|

Voice minutes
|

Number of minutes used for all voice meetings.
|-
|

Voice cost
|

Cost of all voice meetings. Calculated by multiplying the Voice minutes output field by the value configured in the Billing rate (voice) field.
|-
|

Video minutes
|

Number of minutes used for all video meetings.
|-
|

Video cost
|

Cost of all video meetings. Calculated by multiplying the Video minutes output field by the value configured in the Billing rate (video) field.
|-
|

Total cost
|

Sum of the Voice cost and Video cost.
|-
|colspan="2" rowspan="1"|''' Additional Output Fields'''
|-
|

Total Meeting Stats User <User ID>
|

Total sum of the following fields for the specified user:
* Voice minutes
* Voice cost
* Video minutes
* Video cost
* Total cost
|-
|

Total Meetings for User <User ID>
|

Total number of meetings billed to the specified user.
|-
|

Total Meeting Stats for Bill Code <Billing Code>
|

Sum of the following fields for all users assigned to the specified billing code:
* Voice minutes
* Voice cost
* Video minutes
* Video cost
* Total cost
|-
|

Total Meetings for Bill Code <Billing Code>
|

Total number of meetings billed to this billing code.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Running Reports and Exporting Data from Cisco Unified MeetingPlace|Running Reports and Exporting Data from Cisco Unified MeetingPlace]] module

== Call Configuration Page ==

Use this page to perform these tasks:
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Call Control for Cisco Unified MeetingPlace#Configuring Call Control for Cisco Unified MeetingPlace|Configuring Call Control for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Ad-Hoc Conferencing for Cisco Unified MeetingPlace#Configuring Ad-Hoc Conferencing for Cisco Unified MeetingPlace|Configuring Ad-Hoc Conferencing for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Parameters that Affect Sound and Video Quality|Configuring Parameters that Affect Sound and Video Quality]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Auto Attend Feature for Cisco Unified MeetingPlace#Configuring the Auto Attend Feature for Cisco Unified MeetingPlace|Configuring the Auto Attend Feature for Cisco Unified MeetingPlace]] module

== Cisco WebEx Certificate Page ==

Use this page to create a certificate and upload it to the Cisco WebEx Site Administration. To find this page, select '''System Configuration > Cisco WebEx Configuration > Cisco WebEx Certificate'''.

===== Table: Field Reference: Cisco WebEx Certificate =====

{| border = 1
|-
!Field
!Description
|-
|

Certificate location
|

Select this link to save a local copy of the certificate.

If the directory path is not an active link, then you have not yet created the certificate. See [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Creating and Uploading the Cisco WebEx Certificate|Creating and Uploading the Cisco WebEx Certificate]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]] module.
|-
|

Cisco WebEx Site Administration URL
|

Use this URL to upload the certificate to the Cisco WebEx Site Administration.

If no link appears, you first need to configure the fields on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Cisco WebEx Site and Server Page|Cisco WebEx Site and Server Page]].

If selecting the link results in one of the following errors, then complete [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Setting Up the Cisco Unified MeetingPlace Administrator Profile on the Cisco WebEx Site|Setting Up the Cisco Unified MeetingPlace Administrator Profile on the Cisco WebEx Site]] 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:
** SSO Error -1.
** Cannot create account. Contact your administrator. Error -32.
|-
|

Create Certificate
|

Creates a new certificate and saves it to the stated Certificate location.

Restriction: If you create a certificate when one is already in place, you will block further user access to Cisco WebEx through Cisco Unified MeetingPlace. You must upload the new certificate to the Cisco WebEx Site Administration to re-enable user access.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Creating and Uploading the Cisco WebEx Certificate|Creating and Uploading the Cisco WebEx Certificate]] 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 WebEx Site and Server Page ==

To find this page, select '''System Configuration > Cisco WebEx Configuration > Cisco WebEx Site and Server'''.

===== Table: Field Reference: Cisco WebEx Site and Server Page =====

{| border = 1
|-
!Field
!Description
|-
|

Conference scheduling
|

Determines whether your system uses Cisco WebEx web conferencing. If yes, then also determines whether users will schedule meetings from the Cisco WebEx site or from the Cisco Unified MeetingPlace web user portal.

The value of this field determines which other fields appear on this page.

Restriction: Changes to this field take effect only after you perform these steps:
# Select '''Save'''.
# Select the Restart Cisco WebEx Adapter or Reset TSP Connection button.
# If your deployment includes a Cisco Unified MeetingPlace Web Server:
## Wait 10 minutes for the system to transfer the configuration to the Web Server.
## Restart the Web Master Service service on the Web Server. See the [[Cisco Unified MeetingPlace Release 8.0 -- Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service#Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service|Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service]] module.

Default: Audio/video only-schedule from Cisco Unified MeetingPlace

'''Note: ''' When you reconfigure your deployment from Audio/video only to a WebEx-managed deployment, automatic recording is still configured regardless of user profile settings.

|-
|

Cisco WebEx site ID

Cisco WebEx site name

Cisco WebEx partner ID
|

Cisco WebEx site parameters provided by your Cisco WebEx administrator.

The Cisco WebEx site name identifies your organization and becomes part of the URL for your Cisco WebEx site. Enter the company site name only, do not enter the "webex.com" this is appended automically for communications.
|
|

Cisco WebEx site administration password
|

Enter the password that you assigned to the Cisco Unified MeetingPlace administrator profile on the Cisco WebEx site.

See [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Setting Up the Cisco Unified MeetingPlace Administrator Profile on the Cisco WebEx Site|Setting Up the Cisco Unified MeetingPlace Administrator Profile on the Cisco WebEx Site]] 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 uses this password to connect to the Cisco WebEx site to perform administrative tasks, such as importing certificates or user profiles.
|-
|

Cisco WebEx site version
|

''Display only''. Cisco WebEx release number.
|-
|

Proxy configuration required (SOCKS Proxy only supported, not HTTP proxy)

Proxy server hostname

Proxy server port
|

Provided by your network administrator.

Proxy servers are often used with firewalls.

Requirement: If you modify these fields after the connection with Cisco WebEx is already established, you must select the Restart Cisco WebEx Adapter button.

'''Caution! ''' This button causes the system to drop all Cisco WebEx meetings that are active.
|-
|

Cisco WebEx adapter status
|

''Display only''. Whether or not the adapter process is running.
|-
|

Reset TSP Connection
|

Establishes or resets the telephony connection between Cisco Unified MeetingPlace and Cisco WebEx.

Updates the TSP primary host and TSP secondary host configuration from the Cisco WebEx site and then restarts the adapter.

'''Caution! ''' This button causes the system to drop all Cisco WebEx meetings that are active.
|-
|

Restart Cisco WebEx Adapter
|

Restarts the adapter using the existing configuration for the TSP primary host and TSP secondary host.

Use this button only if requested by Cisco TAC, by your Cisco WebEx service administrator, or after you modify these fields:
* Conference scheduling
* Proxy configuration required
* Proxy server hostname
* Proxy server port

'''Caution! ''' This button causes the system to drop all Cisco WebEx meetings that are active.
|}

===== Related Topics =====
* [[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

== Community Strings Page ==

To find this page, select '''Maintenance > SNMP > Community Strings'''.

===== Table: Fields Reference: Community Strings Page=====

{| border = 1
|-
!Field
!Description
|-
|

Community string name
|

The name of the SNMP community string. Select the underlined name of the SNMP community string to edit it.
|-
|

Access privileges
|

The level of access for this SNMP community string. Access privileges provide security by restricting the ability to alter the Cisco Unified MeetingPlace system.

Allowable access privileges for the community strings are:
* Read only
* Read write
* Read write notify
* Notify only
* None
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SNMP on the Cisco Unified MeetingPlace Application Server#Adding or Editing SNMP Community Strings|Adding or Editing SNMP Community Strings]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SNMP on the Cisco Unified MeetingPlace Application Server#Configuring SNMP on the Cisco Unified MeetingPlace Application Server|Configuring SNMP on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SNMP on the Cisco Unified MeetingPlace Application Server#Displaying or Deleting SNMP Community Strings|Displaying or Deleting SNMP Community Strings]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SNMP on the Cisco Unified MeetingPlace Application Server#Configuring SNMP on the Cisco Unified MeetingPlace Application Server|Configuring SNMP on the Cisco Unified MeetingPlace Application Server]] module

== Configure Logging Levels Page ==

Use this page to define log levels for the Cisco Unified MeetingPlace web applications and for the Media Server. The system collects messages for the specified log level and all the levels below it. The higher the log level you specify, the more information is collected. Debug is the highest log level.

To find this page, select '''Services > Logs > Configure Logging Levels'''.

'''Caution! ''' Increasing log levels can severely decrease system performance and even freeze Cisco Unified MeetingPlace. Only change the log levels if Cisco TAC requests that you change them.

===== Table: Field Reference: Configure Logging Levels Page =====

{| border = 1
|-
!Field
!Description
|-
|colspan="2" rowspan="1"|''' Web Applications'''
|-
|

Root
|

Main web application consisting of the Cisco Unified MeetingPlace web user portal and the Administration Center.

Default: Info
|-
|

RCMS
|

MailService used for creating and sending all back-end e-mail notifications (SMTP and Exchange integration) for meetings, alarms, backup and archiving; also used for generating reports.

Default: Info
|-
|

Outlook Web
|

Microsoft Outlook plug-in (running on client) connects to this web application (running on the server) and uses it to schedule and view meetings from Microsoft Outlook.

Default: Info
|-
|

IpPhone
|

Cisco Unified IP Phone interface used for scheduling and viewing meetings.

Default: Debug
|-
|

Web Services
|

Used for various external integrations, for example, Cisco Unity Connection.

Default: Info
|-
|

Web Services 7.0.2
|

Used for older releases of web services for various external integration of clients developed for Cisco Unified MeetingPlace Release 7.0.2.

Default: Info
|-
|

Web Services 8.0
|

Used for older releases of web services for various external integration of clients developed for Cisco Unified MeetingPlace Release 8.0

Default: Info
|-
|td colspan="2" rowspan="1"|''' Media Server (available only when the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Type of media server]] is set to Hardware Media Server)'''
|-
|

Media Server Administration logging level
|

Component responsible for communication with SIP back-to-back user agent (B2BUA) and the hardware MCU.

Default: Info
|-
|

SIP B2BUA logging level
|

Component that handles the SIP communication.

Default: Warn
|-
|

Enable phone keypad input logging
|

Enables (or disables) the Media Server administrator to log the DTMF digits.

Default: Yes
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#How to Configure Logging Levels|How to Configure Logging Levels]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using Alarms and Logs on Cisco Unified MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module

== Custom Prompts Page ==

Use this page to add custom voice prompts to the Cisco Unified MeetingPlace database. To find this page, select '''Maintenance > Custom Prompts'''.
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Field Reference: Custom Prompts Page|Table: Field Reference: Custom Prompts Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Table: Navigation Reference: Custom Prompts Page|Table: Navigation Reference: Custom Prompts Page]]

===== Table: Field Reference: Custom Prompts Page =====

{| border = 1
|-
!Field
!Description
|-
|

Disable music
|

Select '''Yes''' to disable (or '''No''' to enable) music, and select '''Save'''.

Default: No
|-
|

Language
|

Select the language of the custom prompt that you will upload.

Default: English (US)
|-
|

File to upload
|

Browse to the custom voice prompt file that you want to add.
|-
|

Upload File
|

Select this button after you specify the language and voice prompt file.
|}

===== Table: Navigation Reference: Custom Prompts Page =====

{| border = 1
|-
!To
!Do This
|-
|

Display a shorter or longer list of entries in one view
|

At the bottom of the page, in the Rows per page field, select the number of entries to display.
|-
|

Change the alphanumeric sort order to ascending or descending
|

Select the column heading to change the arrow direction:
* Down arrow-ascending sort
* Up arrow-descending sort
|-
|

Display a different page of entries
|

At the bottom of the page, perform one of these actions:
* In the Go field, enter the page number to display, and select '''Go'''.
* Select the arrows to page through the list.
|-
|

Delete entries
|

Check the appropriate check boxes in the far left column, and select '''Delete Selected'''.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace#Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]] module

== Customize Outlook Interface ==

To find this Administration Center page, select '''System Configuration > Customize Outlook Interface'''.

'''Note: ''' This page appears only when the msft_int license is installed.

===== Table: Field Reference: Customize Outlook Interface =====

{| border = 1
|-
!Field
!Definition
|-
|

Language
|

Specifies which scheduling form to modify. The system has a separate scheduling form for each language.

Recommendation: Use consistent customizations for all languages on your system.

Default: Value of the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Table: Field Reference: Usage Configuration Page|Language 1]] field on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (U - W pages)#Usage Configuration Page|Usage Configuration Page]].
|-
|

Field Name
|

Default field labels for scheduling form.
*Meeting ID
*Subject
*Number of Participants
*List meeting publicly
*Meeting password
*Billing code
*Language
*Who can attend
*Entry announcement
*Exit announcement
*Servers
*Web meeting room access
*No external web participants
*Allow external web participants
|-
|

Custom Label
|

Customized field label for scheduling form.
|-
|

Enabled
|

Whether to show (Yes) or hide (No) the field on the scheduling form.
|-
|

Default Enabled
|

Default value of the Enabled field.
|-
|

Save
|

Saves the settings for the scheduling form specific to the selected Language.

Recommendation: Use consistent customizations for all languages on your system by making similar changes for each Language option.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Customizing the Cisco Unified MeetingPlace Scheduling Form for Microsoft Outlook|Customizing the Cisco Unified MeetingPlace Scheduling Form for Microsoft Outlook]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook|Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook]] module

[[Category: Reference Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key

2011-10-07T17:34:33Z

Cgriffen: /* Procedure */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

This section describes how to export and subsequently reimport the SSL private key into the MPWEB database. We recommend that you make this part of your standard backup procedure. You will need to complete these procedures any time you need to move the SSL certificate, for example, from an old Web Server computer to a new Web Server computer or when you are rebuilding a computer.

== Exporting the Private Key ==

This procedure describes how to export the private key/certificate pair on the Web Server so that you can manually copy the SSL files in case you need to restore SSL on the Web Server.

===== Procedure =====

# Open the Internet Services Manager on the Cisco Unified MeetingPlace Web Server.
#: Click '''Start > Programs > Administrative Tools > Internet Information Services Manager'''.
# Navigate to Default Web Site.
#: Click the '''+''' sign beside Local Server > Web Sites to open the appropriate directory trees.
# Right-click '''Default''' '''Web Site'''.
# Select '''Properties'''.
#: The Default Web Site Properties window displays.
# Click the '''Directory Security''' tab.
# Click '''Server Certificate'''.
#: The Web Server Certificate wizard displays.
# Click '''Next'''.
# Select '''Export the current certificate to a pfx file'''.
# Click '''Next'''.
# Click '''Browse''' and select to save the certificate file to your desktop.
# Click '''Next'''.
# Enter a password to encrypt the certificate.
# Enter the password again to confirm it.
# Click '''Next'''.
#: The Export Certificate Summary Screen displays and the exported certificate file is now on your desktop.
# Click '''Next'''.
# Click '''Finish''' to close the Web Server Certificate wizard.
# Click '''OK''' or '''Cancel''' to close the Default Web Site Properties window.
# Close IIS Manager.

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

== Copying and Saving the Private Key for Future Use ==

We recommend that you complete this procedure as part of your standard backup procedure on the Web Server.

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Exporting the Private Key|Exporting the Private Key]].

===== Procedure =====

# Copy your PFX file to C:\Program Files\Cisco Systems\MPWeb\DataSvc (on the MPWeb server).
# Open a DOS prompt.
## Click '''Start > Run'''.
## Enter '''cmd'''.
# Enter '''cd Program Files\Cisco Systems\MPWeb\DataSvc'''.
# Enter '''openssl.exe'''.
# Enter '''pkcs12 –in mycertificate.pfx –out mycertificate.pem –nodes'''.
# Enter the import password when prompted.
#: This is the password you defined in the Web Server Certificate wizard during the export process.
# Save the PEM file. You will need it whenever you need to reapply the certificate.

== Importing the Private Key in to the MPWEB Database ==

===== Before You Begin =====

Complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Back Up and Restore the SSL Private Key#Copying and Saving the Private Key for Future Use|Copying and Saving the Private Key for Future Use]].

===== Procedure =====

# Open SQL Server Enterprise Manager.
#: Click '''Start > All Programs > Microsoft SQL Server > Enterprise Manager'''.
# Navigate to the MPWEB database.
#: Click the''' + '''sign next to SQL Server Group > LOCAL > Databases > MPWEB to open the appropriate directory trees.
# Click '''Tables''' in the MPWEB directory.
#: A list of tables opens in the right pane.
# Right-click '''Web''' in the right pane.
# Select '''Open table > Return all rows'''.
#: The Web database table displays.
# Scroll to the right until you see the SSLPrivateKey column.
# Open the PEM file in Notepad.
#: You saved the PEM file when you copied and saved the private key for future use.
# Copy the private key in its entirety.
#: The private key begins with "Begin RSA Private key" and ends with "end RSA private key".
# Paste the private key into the SSLPrivateKey field.
## Click the field before the SSLPrivateKey column.
## Press the Tab key on your keyboard to select all of the data in the SSLPrivateKey field.
## Right-click and select '''Paste''' to paste the value you copied from Notepad.
# Click somewhere else on the screen to remove your cursor from the SSLPrivateKey field.
# Close SQL Server Enterprise Manager.
# (Optional) Enable SSL if it is not already enabled.
# Reboot the server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Secure Sockets Layer#Enabling SSL|Enabling SSL]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]