Deployment Guide for Cisco Unified Presence Release 7
Upload
others
View
8
Download
0
Embed Size (px)
344 x 292
429 x 357
514 x 422
599 x 487
Citation preview
Deployment Guide for Cisco Unified Presence Release 7.0 May 19,
2009
Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San
Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408
526-4000
800 553-NETS (6387) Fax: 408 527-0883
CCVP, the Cisco logo, and Welcome to the Human Network are
trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live,
Play, and Learn is a service mark of Cisco Systems, Inc.; and
Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA,
CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo,
Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the
Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel,
EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare,
GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ
Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study,
LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking
Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet,
StackWise, The Fastest Way to Increase Your Internet Quotient, and
TransPath are registered trademarks of Cisco Systems, Inc. and/or
its affiliates in the United States and certain other
countries.
All other trademarks mentioned in this document or Website are the
property of their respective owners. The use of the word partner
does not imply a partnership relationship between Cisco and any
other company. (0711R)
Deployment Guide for Cisco Unified Presence Release 7.0 © 2009
Cisco Systems, Inc. All rights reserved.
C O N T E N T S
C H A P T E R 1 Overview of this Integration 1-1
About the Interfaces with Cisco Unified Communications Manager
1-1
Main Components 1-1
SIP Interface 1-2
CTI Interface 1-3
AXL/SOAP Interface 1-3
LDAP Interface 1-4
Module Overview 1-4
Cisco Integrations 1-6
Third Party Integrations 1-6
Getting More Information 1-7
C H A P T E R 2 Configuring the Licensing for this Integration
2-1
About the License Requirements 2-1
Cisco Unified Presence License Requirements 2-1
Cisco Unified Personal Communicator License Requirements 2-2
User License Requirements 2-2
Uploading a License File on Cisco Unified Communications Manager
2-5
Assigning the Licensing Capabilities on Cisco Unified
Communications Manager 2-5
Viewing Licensing Information on Cisco Unified Communications
Manager 2-7
C H A P T E R 3 Configuring Cisco Unified Communications Manager
for Integration with Cisco Unified Presence 3-1
User and Device Configuration on Cisco Unified Communications
Manager 3-1
Configuring the Presence Service Parameter 3-3
How to Configure the SIP Trunk on Cisco Unified Communications
Manager 3-3
Configuring the SIP Trunk Security Profile for Cisco Unified
Presence 3-4
Configuring the SIP Trunk for Cisco Unified Presence 3-4
Verifying That the Required Services are Running on Cisco Unified
Communications Manager 3-6
3 Deployment Guide for Cisco Unified Presence Release 7.0.1, 7.0.2
and 7.0.3
Contents
C H A P T E R 4 Planning a Cisco Unified Presence Multi-Node
Deployment 4-1
About the Multi-Node Scalability Feature 4-1
Scalability Enhancements 4-1
Supported Endpoints 4-2
Performance Recommendations 4-2
Balanced Non-Redundant High-Availability Deployment 4-4
Balanced Redundant High-Availability Deployment 4-5
Active/Standby Redundant High-Availability Deployment 4-6
Non High-Availability Deployment 4-7
About DNS Configuration Options for the Multi-Node Feature
4-9
Cluster-wide DNS SRV 4-9
Subcluster-wide DNS SRV 4-9
Multi-Node Hardware Recommendations 4-10
C H A P T E R 5 Performing a Cisco Unified Presence Multi-node
Deployment 5-1
Performing a Fresh Multi-Node Installation 5-1
How to Update a Multi-Node Configuration after Deployment 5-2
Performing a Software Upgrade 5-2
Adding a New Node 5-3
Expanding the Cluster 5-4
Monitoring a Multi-Node System 5-4
Resolving a Hardware Problem 5-5
C H A P T E R 6 Configuring a Cisco Unified Presence Server for
Deployment in the Network 6-1
How to Configure the System Topology on Cisco Unified Presence
6-1
About Subcluster, Node and User Management Recommendations
6-2
Node Creation and Movement Recommendations 6-2
Node Name Recommendations 6-2
User Redistribution 6-4
4 Deployment Guide for Cisco Unified Presence Release 7.0.1, 7.0.2
and 7.0.3
Contents
Creating, Assigning and Moving Nodes in System Topology 6-5
Configuring User Assignment in System Topology 6-7
Configuring a Cluster-Wide Cisco Unified Presence Address 6-8
Uploading the Server Licence File on Cisco Unified Presence
6-9
How to Configure the Presence Information on Cisco Unified Presence
6-10
Presence Gateway Configuration Option 6-10
Configuring the Presence Gateway 6-10
Configuring the Presence Settings 6-11
Configuring the Proxy Server Settings 6-12
How to Turn On the Cisco Unified Presence Services 6-12
Turning On the Sync Agent 6-12
Turning On the Proxy Service 6-13
Turning On the Cisco Unified Presence Services 6-13
C H A P T E R 7 Configuring Security between Cisco Unified
Communications Manager and Cisco Unified Presence 7-1
Prerequisites for Configuring Security 7-1
How to Configure the Certificate Exchange 7-1
Downloading the Certificate from Cisco Unified Communications
Manager 7-2
Downloading the Certificate from Cisco Unified Presence 7-2
Uploading the Cisco Unified Communications Manager Certificate to
Cisco Unified Presence 7-3
Restarting the SIP Proxy Service 7-3
Uploading the Cisco Unified Presence Certificate to Cisco Unified
Communications Manager 7-4
Restarting the Cisco Unified Communications Manager Service
7-4
How to Configure the TLS Settings on Cisco Unified Presence
7-5
Configuring a TLS Peer Subject 7-5
Configuring a TLS Context 7-5
C H A P T E R 8 Configuring the Cisco IP PhoneMessenger Service
8-1
Prerequisites for Integrating Cisco IP PhoneMessenger 8-1
How to Configure Cisco IP PhoneMessenger on Cisco Unified
Communications Manager 8-1
Configuring Cisco IP PhoneMessenger as an Application User
8-2
Configuring a Phone Service for the Cisco IP PhoneMessenger
8-2
Subscribing Phones to the Cisco IP PhoneMessenger Service 8-3
How to Configure Cisco IP PhoneMessenger on Cisco Unified Presence
8-3
Configuring the Cisco IP PhoneMessenger Settings 8-4
Configuring Meeting Notification Settings 8-4
5 Deployment Guide for Cisco Unified Presence Release 7.0.1, 7.0.2
and 7.0.3
Contents
C H A P T E R 9 Configuring the Cisco Unified Personal Communicator
Client 9-1
Prerequisites for Integrating Cisco Unified Personal Communicator
9-1
Do Not Disturb Behavior in Cisco Unified Personal Communicator
9-2
How to Configure Cisco Unified Personal Communicator on Cisco
Unified Communications Manager 9-3
Application Dialing and Directory Lookup Rules 9-4
How Cisco Unified Personal Communicator Transforms Dialed Numbers
9-4
Extension Mobility Configuration 9-5
Guidelines for Configuring the Softphone Device Name 9-5
Creating a Softphone Device for Each Cisco Unified Personal
Communicator User 9-6
How to Configure Cisco Unified Personal Communicator on Cisco
Unified Presence 9-8
TFTP Server Connection 9-8
Configuring the Service Parameter for Cisco Unified Personal
Communicator 9-10
How to Configure CTI Gateway Settings for Desk Phone Control
9-10
Desk Phone Control and the CTI Connection Failures 9-11
Configuring CTI Gateway Server Names and Addresses 9-12
Creating CTI Gateway Profiles 9-13
Configuring Firewalls to Pass Cisco Unified Personal Communicator
Traffic 9-14
Configuring Users for Point-to-Point Video Calls and for Multipoint
Video Conferencing 9-15
A P P E N D I X 10 Additional Deployment Information for Cisco
Unified Personal Communicator 10-1
About Secure Voicemail Messaging 10-1
Secure Voicemail Messaging on Cisco Unity Connection 10-1
Secure Voicemail Messaging on Cisco Unity 10-2
Secure Voicemail Messaging Configuration 10-3
How to Configure Voicemail Servers for Cisco Unified Personal
Communicator 10-3
Configuring Cisco Unity Connection Servers 10-3
Configuring Cisco Unity Servers 10-5
Configuring Voicemail Server Names and Addresses on Cisco Unified
Presence 10-8
Configuring Mailstore Server Names and Addresses on Cisco Unified
Presence 10-9
Creating Voicemail Profiles on Cisco Unified Presence 10-10
How to Configure Conferencing Servers for Cisco Unified Personal
Communicator 10-12
Configuring Cisco Unified MeetingPlace Express and Cisco Unified
MeetingPlace Express VT Servers 10-12
Configuring Cisco Unified MeetingPlace Servers 10-15
Configuring the Cisco Webex Meeting Center Server 10-16
Configuring Conferencing Server Names and Addresses on Cisco
Unified Presence 10-17
Creating Conferencing Profiles on Cisco Unified Presence
10-18
6 Deployment Guide for Cisco Unified Presence Release 7.0.1, 7.0.2
and 7.0.3
Contents
How to Update User Configuration After Deploying Cisco Unified
Personal Communicator 10-21
Application Profiles 10-21
Changing Application Profiles for Multiple Users 10-22
Configuring a New User for Full Cisco Unified Personal Communicator
Functionality 10-23
C H A P T E R 11 Deploying and Upgrading Cisco Unified Personal
Communicator 11-1
How to Deploy the Application 11-1
Installer Package Names 11-1
Software Download Site 11-3
Deploying the Application in a Mac OS Environment 11-3
Deploying the Application and the Camera Drivers in a Microsoft
Windows Environment 11-3
Upgrading the Application 11-4
Installation and Configuration of Headsets and Other Audio Devices
11-5
Use of Third-Party Headsets with Cisco Unified Personal
Communicator 11-6
Information to Provide to Users 11-6
C H A P T E R 12 Integrating the LDAP Directory 12-1
Prerequisites for Integrating the LDAP Directory 12-1
LDAP Integrations 12-1
How to Integrate the LDAP Directory with Cisco Unified
Communications Manager 12-2
Secure Connection Between Cisco Unified Communications Manager and
the LDAP Directory 12-3
Configuring the LDAP Synchronization for User Provisioning
12-3
Configuring LDAP Authentication 12-4
Configuring a Secure Connection Between Cisco Unified Presence and
the LDAP Directory 12-5
How to Integrate the LDAP Directory with Cisco Unified Personal
Communicator 12-6
Rules for a Displayed Contact Name 12-6
Fetch Contact Pictures from a Web Server 12-7
Configuring the LDAP Attribute Map 12-7
Configuring LDAP Server Names and Addresses 12-9
Creating LDAP Profiles and Adding Users to the Profile 12-10
C H A P T E R 13 Configuring a Cisco Unified Presence Intercluster
Deployment 13-1
Prerequisites for Intercluster Deployment 13-1
How to Configure Intercluster Peers 13-2
Configuring an Intercluster Peer 13-2
Turning On the Intercluster Sync Agent 13-3
7 Deployment Guide for Cisco Unified Presence Release 7.0.1, 7.0.2
and 7.0.3
Contents
Verifying the Intercluster Peer Status 13-3
A P P E N D I X A Glossary of Terms A-1
8 Deployment Guide for Cisco Unified Presence Release 7.0.1, 7.0.2
and 7.0.3
Deploy
Overview of this Integration
• About the Interfaces with Cisco Unified Communications Manager,
page 1-1
• Module Overview, page 1-4
• Cisco Integrations, page 1-6
About the Interfaces with Cisco Unified Communications
Manager
• Main Components, page 1-1
• SIP Interface, page 1-2
• CTI Interface, page 1-3
• AXL/SOAP Interface, page 1-3
• LDAP Interface, page 1-4
Main Components Figure 1-1 illustrates a basic Cisco Unified
Presence deployment, including the main components and interfaces
between Cisco Unified Communications Manager and Cisco Unified
Presence.
1-1 ment Guide for Cisco Unified Presence Release 7.0
Chapter 1 Overview of this Integration About the Interfaces with
Cisco Unified Communications Manager
Figure 1-1 Cisco Unified Presence Basic Deployment
SIP Interface A SIP connection handles the presence information
exchange between Cisco Unified Communications Manager and Cisco
Unified Presence. To enable the SIP connection on Cisco Unified
Communications Manager, you must configure a SIP trunk pointing to
the Cisco Unified Presence server.
On Cisco Unified Presence, configuring Cisco Unified Communications
Manager as a Presence Gateway will allow Cisco Unified Presence to
send SIP subscribe messages to Cisco Unified Communications Manager
over the SIP trunk.
Note Cisco Unified Presence does not support clients (Cisco clients
or third party) connecting to Cisco Unified Presence using
SIP/SIMPLE interface over TLS. Only a SIP connection over TCP is
supported.
Related Topics
• How to Configure the SIP Trunk on Cisco Unified Communications
Manager, page 3-3
• How to Configure the Presence Information on Cisco Unified
Presence, page 6-10
Cisco Unified Presence
1-2 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 1 Overview of this Integration About the Interfaces with
Cisco Unified Communications Manager
CTI Interface The CTI (Computer Telephony Integration) interface
handles all the CTI communication for users on the Cisco Unified
Presence server to control phones on Cisco Unified Communications
Manager. The CTI functionality allows users of the Cisco Unified
Personal Communicator client to run the application in desk phone
control mode.
The CTI functionality is also used for the Cisco Unified Presence
remote call control feature on the Microsoft Office Communicator
client. For information on configuring the remote call control
feature, see the Integration Note for Configuring Cisco Unified
Presence with Microsoft OCS for MOC Call Control.
To configure CTI functionality for Cisco Unified Presence users on
Cisco Unified Communications Manager, users must be associated with
a CTI-enabled group, and the primary extension assigned to that
user must be enabled for CTI.
To configure Cisco Unified Personal Communicator desk phone
control, you must configure a CTI server and profile on Cisco
Unified Presence, and assign any users that wish to use the
application in desk phone mode to that profile. However, note that
all CTI communication occurs directly between Cisco Unified
Communications Manager and Cisco Unified Personal Communicator, and
not through the Cisco Unified Presence server.
Related Topics
• User and Device Configuration on Cisco Unified Communications
Manager, page 3-1
• How to Configure CTI Gateway Settings for Desk Phone Control,
page 9-10
• Integration Note for Configuring Cisco Unified Presence with
Microsoft OCS for MOC Call Control:
http://www.cisco.com/en/US/products/ps6837/products_installation_and_configuration_guides_lis
t.html
AXL/SOAP Interface The AXL/SOAP interface handles the database
synchronization from Cisco Unified Communications Manager and
populates the Cisco Unified Presence database. To activate the
database synchronization, you must start the Sync Agent service on
Cisco Unified Presence.
By default the Sync Agent load balances all users equally across
all nodes within the Cisco Unified Presence cluster. You also have
the option to manually assign users to a particular node in the
Cisco Unified Presence cluster.
For guidelines on the recommended synchronization intervals when
executing a database synchronization with Cisco Unified
Communications Manager, for single and dual-node Cisco Unified
Presence, see the Cisco Unified Presence SRND document.
Related Topics
1-3 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 1 Overview of this Integration Module Overview
LDAP Interface Cisco Unified Communications Manager obtains all
user information via manual configuration or synchronization
directly over LDAP. Cisco Unified Presence then synchronizes all
this user information from Cisco Unified Communications Manager
(using the AXL/SOAP interface).
Cisco Unified Presence provides LDAP authentication for users of
the Cisco Unified Personal Communicator client and Cisco Unified
Presence user interface. If a Cisco Unified Personal Communicator
user logs into Cisco Unified Presence, and LDAP authentication is
enabled on Cisco Unified Communications Manager, Cisco Unified
Presence goes directly to the LDAP directory for Cisco Unified
Personal Communicator user authentication. Once Cisco Unified
Personal Communicator is authenticated, Cisco Unified Presence
forwards this information to Cisco Unified Personal Communicator to
continue the user login.
Cisco Unified Personal Communicator also uses the LDAP directory to
allow users to search and add contacts.
Related Topics
Module Overview
Configuring the Licensing for this Integration
• Licensing requirements for Cisco Unified Presence and Cisco
Unified Personal Communicator.
• Instructions on how to obtain and upload a license file, and how
to view license information on Cisco Unified Communications
Manager.
• Certain licensing topics are only applicable if you are deploying
the Cisco Unified Personal Communicator client.
Configuring Cisco Unified Communications Manager for Integration
with Cisco Unified Presence
• Instructions to configure the presence parameters, and the SIP
trunk, on Cisco Unified Communications Manager.
• This is required configuration.
• Make sure that you complete the prerequisite user and device
configuration on Cisco Unified Communications Manager as described
in this module.
Planning a Cisco Unified Presence Multi-node Deployment
• Multi-node scalability feature introduction.
• Different multi-node deployment models.
• DNS configuration options for a multi-node deployment.
• This module is only applicable if you are configuring a
multi-node deployment.
1-4 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 1 Overview of this Integration Module Overview
Performing a Cisco Unified Presence Multi-node Deployment
• A high-level overview of how to perform a multi-node installation
and deployment.
• Describes the high-level sequence of tasks when performing a
fresh multi-node deployment, and updating an existing multi-node
deployment.
• This module is only applicable if you are configuring a
multi-node deployment.
Configuring a Cisco Unified Presence Server for Deployment in the
Network
• System topology configuration (multi-node)
• Cluster-wide SRV address (multi-node)
• Uploading Cisco Unified Presence license file (single node and
multi-node)
• Presence gateway and service parameters (single node and
multi-node)
• Turning on Cisco Unified Presence services (single node and
multi-node)
• Some topics in this module are only applicable to the multi-node
deployment, and some are applicable to both single node and
multi-node deployments.
• You perform certain tasks in this module on the Cisco Unified
Presence publisher node, and certain tasks on all nodes in the
cluster.
Configuring Security between Cisco Unified Communicati ons Manager
and Cisco Unified Presence
• The exchange of self-signed certificates between Cisco Unified
Communications Manager and Cisco Unified Presence.
• This module is only required if you want a secure connection
between these servers.
Configuring the Cisco IP PhoneMessenger Service
• Instructions to configure Cisco IP PhoneMessenger on Cisco
Unified Communications Manager
• Instructions to configure Cisco IP PhoneMessenger on Cisco
Unified Presence
• This module is only required if you are deploying Cisco IP
PhoneMessenger
Configuring the Cisco Unified Personal Communicator
• Instructions to configure Cisco Unified Personal Communicator on
Cisco Unified Communications Manager
• Instructions to configure Cisco Unified Personal Communicator on
Cisco Unified Presence
• Configuring firewalls to pass Cisco Unified Personal Communicator
traffic
• Configuring users for point-to-point video calls and for
multipoint video conferencing
• This module is only required if you are deploying Cisco Unified
Personal Communicator.
Additional Deployment Information for Cisco Unified Personal
Communicator
• Instructions to configure the voicemail servers for Cisco Unified
Personal Communicator
• Instructions to configure the conferencing servers for Cisco
Unified Personal Communicator
• Instructions to configure the video conferencing resources on
Cisco Unified Communications Manager
• Updating user configuration after deploying Cisco Unified
Personal Communicator
• This module describes optional configuration if you are deploying
Cisco Unified Personal Communicator
Module This Module Describes... Notes
1-5 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 1 Overview of this Integration Cisco Integrations
Cisco Integrations For information on integrating Cisco Unified
Presence with Cisco Unified Mobility Advantage, see the Cisco
Unified Mobility Advantage server documentation.
Related Topics
http://www.cisco.com/en/US/products/ps7270/prod_installation_guides_list.html
Third Party Integrations This guide only details how to configure a
basic Cisco Unified Presence deployment. For third party
integrations, see the document references below.
Deploying and Updating Cisco Unified Personal Communicator
• Instructions on deploying and upgrading Cisco Unified Personal
Communicator
• Information on installation and use of headsets and other audio
devices.
• This module is only required if you are deploying Cisco Unified
Personal Communicator.
Integrating the LDAP Directory
• This is recommended configuration.
• Information about intercluster deployments, and how to configure
intercluster peers.
• This module is only required if you are configuring a
multi-cluster deployment.
Module This Module Describes... Notes
Third Party Integration This Guide Describes...
Integrating Cisco Unified Presence with Microsoft Exchange
• Integrating with Microsoft Exchange 2003 and 2007
• Configuring Microsoft Active Directory for this integration
Integrating Cisco Unified Presence with Microsoft OCS/LCS for MOC
Call Control
• Configuring Cisco Unified Presence as a CSTA gateway for remote
call control from the Microsoft Office Communicator client
• Configuring Microsoft Active Directory for this integration
• Load-balancing MOC requests in a dual node Cisco Unified Presence
deployment over TCP
Integrating Cisco Unified Presence with Microsoft OCS/LCS for
Inter-Domain Federation
• Federating between one Cisco Unified Presence enterprise and
another Cisco Unified Presence enterprise
• Federating between a Cisco Unified Presence enterprise and a
Microsoft OCS/LCS enterprise
1-6 Deployment Guide for Cisco Unified Presence Release 7.0
Related Topics
http://www.cisco.com/en/US/products/ps6837/products_installation_and_configuration_guides_lis
t.html
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/uc7_0.html
http://www.cisco.com/en/US/products/ps6837/products_device_support_tables_list.html
http://www.cisco.com/en/US/products/ps6837/prod_release_notes_list.html
http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/ps6844/tsd_products_support_series_home.html
Deploy
Configuring the Licensing for this Integration
May 19, 2009
• About the License Requirements, page 2-1
• Obtaining a License File, page 2-4
• Uploading a License File on Cisco Unified Communications Manager,
page 2-5
• Assigning the Licensing Capabilities on Cisco Unified
Communications Manager, page 2-5
• Viewing Licensing Information on Cisco Unified Communications
Manager, page 2-7
About the License Requirements • Cisco Unified Presence License
Requirements, page 2-1
• Cisco Unified Personal Communicator License Requirements, page
2-2
Cisco Unified Presence License Requirements Table 2-1 describes the
user and server license requirements for Cisco Unified
Presence.
2-1 ment Guide for Cisco Unified Presence Release 7.0
Chapter 2 Configuring the Licensing for this Integration About the
License Requirements
Note End User Licence Agreements (EULA) have been introduced with
Cisco Unified Presence 7.x for compliancy-oriented customers and to
align with the Cisco Unified Communications licensing
structure.
Related Topics
• Cisco Unified Personal Communicator License Requirements, page
2-2
• Uploading a License File on Cisco Unified Communications Manager,
page 2-5
• Uploading the Server Licence File on Cisco Unified Presence, page
6-9
• Assigning the Licensing Capabilities on Cisco Unified
Communications Manager, page 2-5
What To Do Next
Cisco Unified Personal Communicator License Requirements • User
License Requirements, page 2-2
• Adjunct Licensing, page 2-3
User License Requirements
Cisco Unified Communications Manager tracks the number of Cisco
Unified Personal Communicator devices that are connected to it and
compares it with the number of device licenses that have been
purchased.
Table 2-1 describes the user license requirements for Cisco Unified
Personal Communicator.
Table 2-1 Cisco Unified Presence user and server license
requirements
License Requirement Description
Cisco Unified Presence user feature license
You need to assign presence capabilities for each Cisco Unified
Presence user. This will consume one Cisco Unified Communications
Manager Device License Unit (DLU).
You can assign Cisco Unified Presence capabilities on a per user
basis, regardless of the number of clients associated with each
user. When you assign Cisco Unified Presence capabilities for a
user, this enables the user to send and receive presence messaging
updates. If the user is not enabled for Cisco Unified Presence
capabilities, no presence messaging or status updates will be
allowed for that user.
On Cisco Unified Communications Manager, you will need to upload
the user DLU, and then assign Cisco Unified Presence capabilities
for a user.
Cisco Unified Presence server license
You will require one server license for each Cisco Unified Presence
server. This license covers service activation for the Presence
Engine and Proxy services on Cisco Unified Presence.
You can deploy Cisco Unified Presence software as a single server
or as a cluster of up to six servers. You must order a separate
server license for each Cisco Unified Presence server, however, you
only need to upload the license to the first node in a cluster as
the license file contains the number of Cisco Unified Presence
servers in a cluster that are licensed to the customer.
2-2 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 2 Configuring the Licensing for this Integration About the
License Requirements
Related Topics
• Cisco Unified Presence License Requirements, page 2-1
• Uploading a License File on Cisco Unified Communications Manager,
page 2-5
• Assigning the Licensing Capabilities on Cisco Unified
Communications Manager, page 2-5
• Creating a Softphone Device for Each Cisco Unified Personal
Communicator User, page 9-6
Adjunct Licensing
From Cisco Unified Communications Manager Release 6.0(1), you can
associate a secondary device with a primary device and consume only
one device license per device. This is also known as adjunct
licensing. On Cisco Unified Communications Manager, you can
configure adjunct licensing manually on the Phone Configuration
window, using the AXL interface, or using the Bulk Administration
Tool (BAT). For releases prior to Cisco Unified Communications
Manager Release 6.0(1), three device licenses are consumed.
Adjunct licensing has these restrictions:
• You can associate up to two secondary softphone devices to a
primary phone.
• You cannot delete the primary phone unless you remove the
associated secondary softphone devices.
Table 2-2 Cisco Unified Personal Communicator user licensing
requirements
Configuration License Requirement Description
Cisco Unified Personal Communicator basic functionality
Cisco Unified Personal Communicator software license
You will require one Cisco Unified Personal Communicator software
license per user.
The Cisco Unified Personal Communicator software license comes with
one Cisco Unified Communications Manager Device License Unit (DLU).
You need to assign Cisco Unified Personal Communicator capabilities
for a user. This will consume one DLU.
On Cisco Unified Communications Manager, you will need to upload
the software license for a user, and then assign Cisco Unified
Personal Communicator capabilities for a user.
Cisco Unified Personal Communicator user feature license
You will require one Cisco Unified Personal Communicator user
feature license per user. This license is also known as a Cisco
Unified Communications Manager phone device license. You upload
this license on Cisco Unified Communications Manager.
Softphone mode (optional) Cisco Unified Personal Communicator user
feature license registered as Cisco Unified Communications Manager
softphone
In addition to the normal licensing requirements listed above, you
require three Cisco Unified Communications Manager user feature
licenses to register as a Cisco Unified Communications Manager
softphone (three device licenses are consumed).
2-3 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 2 Configuring the Licensing for this Integration Obtaining
a License File
• The primary phone must be the device that consumes the most
licenses. You cannot make the softphone device the primary phone
and associate a Cisco Unified IP Phone as the secondary
device.
• Secondary softphone devices are limited to Cisco IP Communicator,
Cisco Unified Personal Communicator, and Cisco Unified Mobile
Communicator.
Related Topics
• User License Requirements, page 2-2
• Creating a Softphone Device for Each Cisco Unified Personal
Communicator User, page 9-6
• For information on exporting users in bulk using BAT, see the
Configuration and Maintenance Guide for Cisco Unified
Presence.
What To Do Next
Obtaining a License File, page 2-4
Obtaining a License File When you place an order for Cisco
software, Cisco provides a Product Authorization Key (PAK). The PAK
provides the software activation key and the license file.
Before You Begin
• Obtain the MAC address of Cisco Unified Communications Manager
for which you are requesting the licenses.
• Obtain a valid email address.
• Determine the number of device licenses that you need by using
the license unit calculator in Cisco Unified Communications Manager
Administration (System > Licensing > License Unit
Calculator).
Procedure
Step 1 Register the PAK that you received using the License
Registration web tool that is provided on CCO.
Step 2 Enter the following information:
• The MAC address of Cisco Unified Communications Manager for which
you are requesting the licenses.
• Your valid email address.,
• The number of servers and devices for which you want
licenses.
Step 3 Upload the license file to Cisco Unified Communications
Manager.
Related Topics
What To Do Next
Uploading a License File on Cisco Unified Communications Manager,
page 2-5
2-4 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 2 Configuring the Licensing for this Integration Uploading
a License File on Cisco Unified Communications Manager
Uploading a License File on Cisco Unified Communications
Manager
Use this procedure to upload the following licenses:
• User licenses for Cisco Unified Presence capabilities.
• Software and user licenses for Cisco Unified Personal
Communicator.
Before You Begin
Procedure
Step 2 Select Upload License File.
Step 3 Locate the license file on your local computer.
Step 4 Select Upload.
Troubleshooting Tips
Run the License Unit Report to verify that the license files have
uploaded correctly. Select Cisco Unified Communications Manager
Administration > System > Licensing > License Unit
Report.
Related Topics
• Viewing Licensing Information on Cisco Unified Communications
Manager, page 2-7
What To Do Next
Assigning the Licensing Capabilities on Cisco Unified
Communications Manager, page 2-5
Assigning the Licensing Capabilities on Cisco Unified
Communications Manager
Use this procedure to assign Cisco Unified Presence and Cisco
Unified Personal Communicator capabilities for a user.
2-5 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 2 Configuring the Licensing for this Integration Assigning
the Licensing Capabilities on Cisco Unified Communications
Manager
Note Each capability that you assign for a user will consume one
Cisco Unified Communications Manager DLU.
You can also assign licenses by using the Bulk Administration Tool
(BAT). In Cisco Unified Communications Manager Administration,
select Bulk Administration > CUP > Update CUP/CUPC
Users.
Before You Begin
Procedure
Step 2 Select Find.
Step 3 Perform one of the following actions:
a. To assign capabilities to one user, select the user link to view
the Capabilities Assignment Configuration window.
b. To assign capabilities to more than one user, perform the
following:
• Check the users as required.
• Select Bulk Assignment.
Step 4 Check Enable CUP to enable Cisco Unified Presence
capability.
Step 5 Check Enable CUPC to enable Cisco Unified Personal
Communicator capability.
Step 6 Select Save.
• About the License Requirements, page 2-1
• Uploading a License File on Cisco Unified Communications Manager,
page 2-5
• Viewing Licensing Information on Cisco Unified Communications
Manager, page 2-7
What To Do Next
Chapter 2 Configuring the Licensing for this Integration Viewing
Licensing Information on Cisco Unified Communications Manager
Viewing Licensing Information on Cisco Unified Communications
Manager
To... Menu path
Determine the required number of license units Cisco Unified
Communications Manager Administration > System > Licensing
> License Unit Calculator.
Display the number of licensed Cisco Unified Presence and Cisco
Unified Personal Communicator users synchronized from the Cisco
Unified Communications Manager
Cisco Unified Presence Administration > Diagnostics > System
Status
The status window provides this information:
• Number of licensed Cisco Unified Presence and Cisco Unified
Personal Communicator users synchronized from the Cisco Unified
Communications Manager database.
• User IDs and the primary extension, number of devices, and the
number of contacts associated with users.
• Which users are licensed to use Cisco Unified Personal
Communicator.
2-7 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 2 Configuring the Licensing for this Integration Viewing
Licensing Information on Cisco Unified Communications Manager
2-8 Deployment Guide for Cisco Unified Presence Release 7.0
Deploy
Configuring Cisco Unified Communications Manager for Integration
with Cisco Unified Presence
May 19, 2009
• User and Device Configuration on Cisco Unified Communications
Manager, page 3-1
• Configuring the Presence Service Parameter, page 3-3
• How to Configure the SIP Trunk on Cisco Unified Communications
Manager, page 3-3
• Verifying That the Required Services are Running on Cisco Unified
Communications Manager, page 3-6
User and Device Configuration on Cisco Unified Communications
Manager
Before you configure Cisco Unified Communications Manager for
integration with Cisco Unified Presence, make sure that the
following user and device configuration is completed on Cisco
Unified Communications Manager.
3-1 ment Guide for Cisco Unified Presence Release 7.0
Chapter 3 Configuring Cisco Unified Communications Manager for
Integration with Cisco Unified Presence User and Device
Configuration on Cisco Unified Communications Manager
Note Note that because menu options and parameters may vary per
Cisco Unified Communications Manager releases, see the Cisco
Unified Communications Manager documentation appropriate to your
release.
Related Topics
• Integrating the LDAP Directory, page 12-1
• How to Configure CTI Gateway Settings for Desk Phone Control,
page 9-10
Task Notes Menu path
Modify the User Credential Policy
• This procedure is only applicable if you are integrating with
Cisco Unified Communications Manager version 6.0 or a later
release.
• We recommend that you set an expiration date on the credential
policy for users. The only type of user that does not require a
credential policy expiration date is an Application user.
• Cisco Unified Communications Manager does not use the credential
policy if you are using an LDAP server to authenticate your users
on Cisco Unified Communications Manager.
Cisco Unified Communications Manager Administration > User
Management > Credential Policy Default
Configure the phone devices, and associate a Directory Number (DN)
with each device
• Check Allow Control of Device from CTI to allow the phone to
interoperate with the Cisco Unified Personal Communicator
client.
Cisco Unified Communications Manager Administration > Device
> Phone
Configure the users, and associate a device with each user
• If you are planning to deploy Cisco Unified Personal
Communicator, make sure that the user ID value is unique for each
user. The user ID is converted into the softphone device name, and
if two users have the same softphone device name Cisco Unified
Personal Communicator will not be able to derive the softphone
device name, and as a result, will not function properly.
Cisco Unified Communications Manager Administration > User
Management > End User.
Associate a user with a line appearance
• This procedure is only applicable to Cisco Unified Communications
Manager version 6.0 or a later release.
Cisco Unified Communications Manager Administration > Device
> Phone
Add users to CTI-enabled user group
• This procedure is only applicable if you are planning to deploy
Cisco Unified Personal Communicator. To enable Cisco Unified
Personal Communicator desk phone control, you must add the Cisco
Unified Personal Communicator users to a CTI-enabled user
group.
Cisco Unified Communications Manager Administration > User
Management > User Group
3-2 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 3 Configuring Cisco Unified Communications Manager for
Integration with Cisco Unified Presence Configuring the Presence
Service Parameter
Configuring the Presence Service Parameter You enable the
Inter-Presence Group Subscription parameter to allow users in one
Presence Group to subscribe to the availability information for
users in a different presence group.
Restriction
You can only enable the Inter-Presence Group Subscription parameter
when the subscription permission for the default Standard Presence
Group, or any new Presence Groups, is set to Use System Default. To
configure Presence Groups, select Cisco Unified Communications
Manager Administration > System > Presence Groups.
Procedure
Step 1 Select Cisco Unified Communications Manager Administration
> System > Service Parameters.
Step 2 Select Cisco Unified Communications Manager server from the
Server menu.
Step 3 Select Cisco CallManager from the Service menu.
Step 4 Select Allow Subscription for Default Inter-Presence Group
Subscription in the Clusterwide Parameters (System - Presence)
section.
Step 5 Select Save.
Troubleshooting Tips
You no longer have to manually add Cisco Unified Presence as an
Application Server on Cisco Unified Communications Manager:
• When you add or remove a node on the system topology interface,
the node is automatically added to or removed from the Application
Server list on Cisco Unified Communications Manager.
• When you configure the Cisco Unified Communications Manager
publisher on Cisco Unified Presence from Cisco Unified Presence
Administration > System > CUCM Publisher, the Cisco Unified
Presence node is automatically added to the Application Server list
on Cisco Unified Communications Manager.
Related Topics
• How to Configure the System Topology on Cisco Unified Presence,
page 6-1
What To Do Next
How to Configure the SIP Trunk on Cisco Unified Communications
Manager, page 3-3
How to Configure the SIP Trunk on Cisco Unified Communications
Manager
Note The port number that you configure for the SIP Trunk differs
depending on the version of Cisco Unified Presence that you are
deploying:
• For Cisco Unified Presence version 6.x, configure the port number
5070 for the SIP Trunk.
3-3 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 3 Configuring Cisco Unified Communications Manager for
Integration with Cisco Unified Presence How to Configure the SIP
Trunk on Cisco Unified Communications Manager
• For Cisco Unified Presence version 7.x, configure the port number
5060 for the SIP Trunk.
• Configuring the SIP Trunk Security Profile for Cisco Unified
Presence, page 3-4
• Configuring the SIP Trunk for Cisco Unified Presence, page
3-4
Configuring the SIP Trunk Security Profile for Cisco Unified
Presence
Procedure
Step 2 Select Find.
Step 3 Select Non Secure SIP Trunk Profile.
Step 4 Verify that the setting for Device Security Mode is Non
Secure.
Step 5 Verify that the setting for Incoming Transport Type is
TCP+UDP.
Step 6 Verify that the setting for Outgoing Transport Type is
TCP.
Step 7 Check to enable these items:
• Accept Presence Subscription
• Accept Out-of-Dialog REFER
• Accept Unsolicited Notification
• Accept Replaces Header
Configuring the SIP Trunk for Cisco Unified Presence, page
3-4
Configuring the SIP Trunk for Cisco Unified Presence If DNS SRV is
an option in your network, and you want presence messaging to be
shared equally among all the servers used for presence information
exchange, you must configure the SIP trunk for the Cisco Unified
Presence server with a DNS SRV record of the Cisco Unified Presence
publisher and subscriber servers. You must also configure the
Presence Gateway on the Cisco Unified Presence server with a DNS
SRV record of the Cisco Unified Communications Manager subscriber
nodes.
Before You Begin
• Configure the SIP Trunk security profile on Cisco Unified
Communications Manager.
• Read the Presence Gateway configuration options topic.
3-4 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 3 Configuring Cisco Unified Communications Manager for
Integration with Cisco Unified Presence How to Configure the SIP
Trunk on Cisco Unified Communications Manager
Procedure
Step 1 Select Cisco Unified Communications Manager Administration
> Device > Trunk.
Step 2 Select Add New.
Step 3 Select SIP Trunk from the Trunk Type menu.
Step 4 Select SIP from the Device Protocol menu.
Step 5 Select Next.
Step 6 Enter CUPS-SIP-Trunk for the Device Name.
Step 7 Select a device pool from the Device Pool menu.
Step 8 In the SIP Information section at the bottom of the window,
configure the following values:
a. In the Destination Address field, enter the dotted IP address,
or the FQDN (Fully Qualified Domain Name), or the DNS SRV record
for the Cisco Unified Presence server.
Note Check Destination Address is an SRV if you have configured a
DNS SRV record for the Destination Address value.
b. Enter 5060 for the Destination Port.
c. Select Non Secure SIP Trunk Profile from the SIP Trunk Security
Profile menu.
d. Select Standard SIP Profile from the SIP Profile menu.
Step 9 Select Save.
Troubleshooting Tips
• You must configure a SIP trunk for each Cisco Unified Presence
server that is associated with this Cisco Unified Communications
Manager.
• This tip is only applicable if you configure a Publish SIP trunk.
Cisco Unified Communications Manager can transmit changes to the
presence state of IP devices (phones) via a Publish message over a
SIP trunk. The destination address of the SIP trunk can be either
an SRV record or a port number. If you modify the DNS entry of the
Publish SIP Trunk SRV record by changing the port number or IP
address, you must restart all devices that previously Published and
ensure each device points to the correct Cisco Unified Presence
contact.
Related Topics
• Configuring the SIP Trunk Security Profile for Cisco Unified
Presence, page 3-4
• Presence Gateway Configuration Option, page 6-10
What To Do Next
How to Configure Cisco IP PhoneMessenger on Cisco Unified
Communications Manager, page 8-1
or
How to Configure Cisco Unified Personal Communicator on Cisco
Unified Communications Manager, page 9-3
3-5 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 3 Configuring Cisco Unified Communications Manager for
Integration with Cisco Unified Presence Verifying That the Required
Services are Running on Cisco Unified Communications Manager
Verifying That the Required Services are Running on Cisco Unified
Communications Manager
Procedure
Step 1 Select Cisco Unified Communications Manager
Serviceability> Tools > Control Center - Feature
Services.
Step 2 Select a Cisco Unified Communications Manager server from
the Server menu.
Step 3 Make sure that the following services are running:
• Cisco CallManager
• Cisco TFTP
Deploy
Planning a Cisco Unified Presence Multi-Node Deployment
May 19, 2009
• About DNS Configuration Options for the Multi-Node Feature, page
4-9
• Multi-Node Hardware Recommendations, page 4-10
About the Multi-Node Scalability Feature • Scalability
Enhancements, page 4-1
• Supported Endpoints, page 4-2
• Performance Recommendations, page 4-2
Scalability Enhancements The Cisco Unified Presence multi-node
scalability feature supports the following:
• A Cisco Unified Presence cluster containing up to six
nodes:
– These six nodes can support thirty thousand users, where each
user has an average of one hundred contacts.
– This allows Cisco Unified Presence deployments to scale along
with the thirty-thousand user deployment level of Cisco Unified
Communications Manager.
• Five thousand users per node with a Cisco Unified IP Phone and a
presence client (two end points per user, or 10,000 end points per
node).
• A user can have a maximum contact list size of two hundred.
4-1 ment Guide for Cisco Unified Presence Release 7.0
Chapter 4 Planning a Cisco Unified Presence Multi-Node Deployment
About the Multi-Node Scalability Feature
• Cisco Unified Presence continues to support intercluster
deployments with the multi-node feature.
Supported Endpoints The multi-node scalability feature supports the
following end points:
• Cisco Unified Communications Manager (desk phone)
• Cisco Unified Personal Communicator (soft client)
• Cisco Unified Mobile Communicator
• Lotus Sametime (Lotus soft client)
• Third Party Interface clients
Performance Recommendations You can achieve optimum performance
with the multi-node feature when:
• The resources on all Cisco Unified Presence servers are
equivalent in terms of memory, disk size, and age. Mixing hardware
classes results in servers that are under-powered, therefore
resulting in poor performance.
• You deploy hardware that complies with the hardware
recommendations.
• You configure a Balanced Mode deployment model. In this case the
total number of users is equally divided across all nodes in all
subclusters. Cisco Unified Presence defaults to Balanced Mode user
assignment to achieve optimum performance.
Related Topics
• Balanced Non-Redundant High-Availability Deployment, page
4-4
• Balanced Redundant High-Availability Deployment, page 4-5
High-Availability We recommend that you configure your Cisco
Unified Presence deployments as high-availability deployments.
Although mixed mode deployments are permitted, for example
high-availability subclusters and non high-availability subclusters
in a single deployment, we do not recommend this
configuration.
You can achieve a high-availability deployment by configuring the
Balanced Mode (Redundant High-Availability) or the Active/Standby
Redundant High-Availability deployment models.
Related Topics
4-2 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 4 Planning a Cisco Unified Presence Multi-Node Deployment
About the Multi-Node Scalability Feature
Subclusters The multi-node feature introduces the concept of a
subcluster. A subcluster is a single Cisco Unified Presence server,
or a pair of Cisco Unified Presence servers operating with a shared
presence database that is able to support common users.
In a single-node deployment within the subcluster, there is no
high-availability failover protection for the users assigned to
that node. In a dual-node deployment within a subcluster, users
have high- availability failover protection as each node acts as a
backup for the other node allowing clients to fail over in case of
outages of components or nodes. In this high-availability mode, all
users in the subcluster have redundancy and full failover
capabilities.
Related Topics
• Subcluster-wide DNS SRV, page 4-9
• Creating Subclusters in System Topology, page 6-5
User Assignment You can manually or automatically assign users in a
Cisco Unified Presence deployment. You can manage user assignment
using the User Assignment Mode parameter on the Sync Agent on Cisco
Unified Presence.
If you configure automatic user assignment, the Sync Agent assigns
the users to all nodes in all subclusters in an attempt to balance
the user assignment evenly across all nodes. You can also configure
the Sync Agent to assign the total number of users to only the
first (active) node of an subcluster, with a standby node being
used for failover protection.
If you configure manual user assignment, you must manually assign
your users to nodes, and subclusters, using the system topology
interface on Cisco Unified Presence Administration.
Related Topics
• User Assignment Mode Recommendations, page 6-3
• Configuring User Assignment in System Topology, page 6-7
Clustering over WAN Cisco Unified Presence does not fully support
Clustering over WAN (CoW) unless the round-trip time of the WAN is
less than or equal to three milliseconds. Cisco Unified Presence
can be installed at a site where Cisco Unified Communications
Manager publisher is installed, and clients can be configured to
access Cisco Unified Presence over the WAN. For further
information, see the Cisco Unified Presence SRND.
Related Topics
4-3 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 4 Planning a Cisco Unified Presence Multi-Node Deployment
About the Multi-Node Deployment Models
About the Multi-Node Deployment Models You need to consider how you
are going to deploy the multi-node feature in your network. The
Cisco Unified Presence system topology interface allows you to
configure the desired multi-node deployment model for your network.
You access the system topology interface in Cisco Unified Presence
Administration by selecting System > Topology.
This module provides an overview of the deployment model options
for the multi-node feature, and provides examples of these
deployments on the system topology interface.
Note The system topology interface is only used to configure your
local Cisco Unified Presence cluster. See the intercluster peer
module for information on configuring intercluster peer
relationships with remote Cisco Unified Presence clusters.
• Balanced Non-Redundant High-Availability Deployment, page
4-4
• Balanced Redundant High-Availability Deployment, page 4-5
• Active/Standby Redundant High-Availability Deployment, page
4-6
• Non High-Availability Deployment, page 4-7
Balanced Non-Redundant High-Availability Deployment You can achieve
a balanced mode high-availability deployment by evenly balancing
your users across all nodes in the deployment, using up to 70% of
the CPU of each Cisco Unified Presence server.
The balanced mode high-availability deployment option in a
non-redundant manner supports up to thirty thousand users per
cluster. For this deployment model, distribute the users evenly to
each of the Cisco Unified Presence nodes. For example, if you have
six Cisco Unified Presence nodes in your deployment, and thirty
thousand users, you assign five thousand users to each Cisco
Unified Presence node.
When you use the balanced mode high-availability deployment option
in a non-redundant manner, you can assign twice the number of users
compared to the balanced redundant high-availability deployment
option, but you use the Cisco Unified Presence hardware to maximum
capacity.
If one node fails, the other node may handle the full load of the
additional 50% of users in the subcluster, but may not be able to
sustain this full load at peak traffic. This mode can provide
failover protection in low traffic periods, but not during peak
traffic periods.
See Figure 4-1 for an example of this deployment model on the
system topology interface.
4-4 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 4 Planning a Cisco Unified Presence Multi-Node Deployment
About the Multi-Node Deployment Models
Figure 4-1 Balanced Non- Redundant High-Availability
Deployment
Related Topics
• How to Configure the System Topology on Cisco Unified Presence,
page 6-1
• User Assignment Mode Recommendations, page 6-3
• Scalability Options for Your Deployment, page 4-8
• For the hardware user assignment guidelines for the multi-node
feature, see the Cisco Unified Presence compatibility matrices at
this URL:
http://www.cisco.com/en/US/products/ps6837/products_device_support_tables_list.html
Balanced Redundant High-Availability Deployment You can achieve a
balanced mode high-availability deployment by evenly balancing
users across all nodes in the subcluster, but only using up to 35%
of the CPU of each Cisco Unified Presence server.
The balanced mode high-availability deployment option in a
redundant mode supports up to fifteen thousand users per cluster.
For example, if you have six Cisco Unified Presence nodes in your
deployment, and fifteen thousand users, you assign 2.5 thousand
users to each Cisco Unified Presence node.
4-5 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 4 Planning a Cisco Unified Presence Multi-Node Deployment
About the Multi-Node Deployment Models
When you use the balanced mode high-availability deployment option
in a redundant mode, as compared to a non-redundant mode, only half
the number of users are assigned to each node. However, if one node
fails, the other node will handle the full load of the additional
50% of users in the subcluster, even at peak traffic.
Related Topics
• How to Configure the System Topology on Cisco Unified Presence,
page 6-1
• User Assignment Mode Recommendations, page 6-3
• Scalability Options for Your Deployment, page 4-8
• For the hardware user assignment guidelines for the multi-node
feature, see the Cisco Unified Presence compatibility matrices at
this URL:
http://www.cisco.com/en/US/products/ps6837/products_device_support_tables_list.html
Active/Standby Redundant High-Availability Deployment For this
deployment model, assign all your users to the active Cisco Unified
Presence node, and none to the backup node. The standby node can
handle all traffic from the active node if the active node
fails.
See Figure 4-2 for an example configuration for this deployment
model.
Figure 4-2 Active/Standby High Availability Deployment
Related Topics
• Subcluster-wide DNS SRV, page 4-9
• How to Configure the System Topology on Cisco Unified Presence,
page 6-1
4-6 Deployment Guide for Cisco Unified Presence Release 7.0
• User Assignment Mode Recommendations, page 6-3
• Scalability Options for Your Deployment, page 4-8
• For the hardware user assignment guidelines for the multi-node
feature, see the Cisco Unified Presence compatibility matrices at
this URL:
http://www.cisco.com/en/US/products/ps6837/products_device_support_tables_list.html
Non High-Availability Deployment For this deployment, assign all
your users to one node. With this deployment users have no failover
protection if services or hardware failure on this node. In order
to achieve failover protection, you must configure a redundant node
in the subcluster.
Note We do not recommend this deployment model, but it is
permitted.
See Figure 4-3 for an example configuration for this deployment
model.
Figure 4-3 Non High-Availability Deployment
4-7 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 4 Planning a Cisco Unified Presence Multi-Node Deployment
Scalability Options for Your Deployment
Scalability Options for Your Deployment Cisco Unified Presence
clusters can support up to six nodes. If you originally installed
less than six nodes, then you can install additional nodes at any
time. If you want to scale your Cisco Unified Presence deployment
to support more users, you must consider the multi-node deployment
model you have configured. Table 4-1 describes the scalability
options for each multi-node deployment model.
Table 4-1 Multi-node Scalability Options
Deployment Mode
Scalability Option
Add a New Node to an Existing Subcluster Add a New Node to a New
Subcluster
Balanced Non-Redundant High-Availability Deployment
If you add a new node to an existing subcluster, the new node can
support the same number of users as the existing node; the
subcluster can now support twice the number of users. It also
provides balanced high-availability for the users on the existing
node and the new node in that subcluster.
If you add a new node to a new subcluster, you can support more
users in your deployment.
This does not provide balanced high-availability for the users in
the subcluster. To provide balanced high-availability, you must add
a second node to the subcluster.
Balanced Redundant High-Availability Deployment
If you add a new node to an existing subcluster, the new node can
support the same number of users as the existing node; the
subcluster can now support twice the number of users. It also
provides balanced redundant high-availability for the users on the
existing node and the new node in that subcluster.
Note You may have to reassign your users within the subcluster,
depending how many users were on the existing node.
If you add a new node to a new subcluster, you can support more
users in your deployment.
This does not provide balanced high-availability for the users in
the subcluster. To provide balanced high-availability, you must add
a second node to the subcluster.
Active/Standby Redundant High-Availability Deployment
If you add a new node to an existing subcluster, you provide
high-availability for the users in the existing node in the
subcluster. This provides a high-availability enhancement only; it
does not increase the number of users you can support in your
deployment.
If you add a new node in a new subcluster, you can support more
users in your deployment.
This does not provide high-availability for the users in the
subcluster. To provide high-availability, you must add a second
node to the subcluster.
4-8 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 4 Planning a Cisco Unified Presence Multi-Node Deployment
About DNS Configuration Options for the Multi-Node Feature
Related Topics
• Expanding the Cluster, page 5-4
About DNS Configuration Options for the Multi-Node Feature •
Cluster-wide DNS SRV, page 4-9
• Subcluster-wide DNS SRV, page 4-9
Cluster-wide DNS SRV For this DNS configuration, you can define a
cluster-wide Cisco Unified Presence address. This address is used
by the Cisco Unified Communications Manager SIP Publish Trunk to
load-balance SIP PUBLISH messages from Cisco Unified Communications
Manager to all nodes in the Cisco Unified Presence cluster. Notably
this configuration ensures that the initial SIP PUBLISH messages
are load-balanced across all nodes in the Cisco Unified Presence
cluster. This configuration also provides a high-availability
deployment as, in the event of a node failing, DNS will route the
SIP PUBLISH messages to the remaining nodes.
The cluster-wide DNS configuration is not a required configuration.
It is a suggested configuration that provides a method to
load-balance the initial SIP PUBLISH messages across all nodes in
the Cisco Unified Presence cluster. Cisco Unified Presence sends
subsequent SIP PUBLISH messages for each device to the node where
the device is homed on Cisco Unified Presence.
Related Topics
• Subcluster-wide DNS SRV, page 4-9
Subcluster-wide DNS SRV For this DNS configuration, you can define
a subcluster-wide Cisco Unified Presence address. This address
represents both nodes that are defined in the subcluster. You use
the subcluster-wide address to send the SIP SUBSCRIBE and MESSAGE
requests to a node in the destination subcluster. This DNS
configuration enables you to configure advanced load distribution,
for example, you can provision the first node to receive 75% of
messages, while the second node receives only 25% of
messages.
If you leave the subcluster-wide address undefined, Cisco Unified
Presence sends the message to the primary node of the user in the
subcluster first; if this fails Cisco Unified Presence sends the
message to the backup node for the user in the subcluster. We do
not require a subcluster-wide DNS configuration because Cisco
Unified Presence load-balances intercluster messages by default
over both nodes in a subcluster.
We recommend that you use this DNS configuration for the following
deployment scenarios:
• Active/Standby deployments where you wish to route traffic to one
particular node in preference over another node.
• Clustering over Wan (CoW) deployments where each node in the
subcluster is split geographically, and you wish to route local
traffic to a local node.
4-9 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 4 Planning a Cisco Unified Presence Multi-Node Deployment
Multi-Node Hardware Recommendations
• A deployment that contains mismatched hardware, for example if
you wish to route more traffic to a server that has greater
processing power. Note that we do not recommend this type of
deployment.
This sample DNS configuration shows two nodes in a subcluster,
“mal.sip.com” and “inari.sip.com”, both TCP and UDP. Note that with
this sample configuration, the Subcluster SRV value configured on
Cisco Unified Presence server will be 'mal-inara.sip.com.'
_sip._udp.mal-inara.sip.com.IN SRV 1 1 5060 mal.sip.com.
_sip._tcp.mal-inara.sip.com. IN SRV 1 1 5060 mal.sip.com.
_sip._udp.mal-inara.sip.com.IN SRV 2 1 5060 inara.sip.com.
_sip._tcp.mal-inara.sip.com. IN SRV 2 1 5060 inara.sip.com.
Related Topics
• Cluster-wide DNS SRV, page 4-9
Multi-Node Hardware Recommendations When configuring the multi-node
feature, you need to consider the following:
• We recommend the high-availability deployment option.
• Use similar hardware for all nodes in your deployment.
• Minimize your hardware, for example, instead of using six MCS
7825 servers that support a total of six thousand users, choose two
MCS 7835 servers that can support a total of five thousand
users.
• Use the same generation of server hardware.
• If you must mix generations of similar hardware, put the same
generations of older hardware together in a subcluster and put
fewer users on this subcluster than on the more powerful
subclusters. Note that we do not recommend this deployment
practice.
• We recommend the following disk drives for the multi-node
feature:
– MCS 7816: minimum one 160GB drive (a 250GB drive can also be
used)
– MCS 7825: minimum two 160GB drives (two 250GB drives can also be
used, upgrade required from smaller 80GB drives)
– MCS 7835: minimum two 146GB drives (upgrade required from smaller
72GB drives)
– MCS 7845: minimum four 72GB drives (upgrade recommended to four
146GB drives)
Note The MCS 7845 with four 72GB drives can run the scalability
feature, but this hardware with four 146GB drives is
preferred.
• If you have older-generation hardware, follow the disk drive
upgrade recommendations above. You must meet the minimal disk
capacity on each server in the cluster in order to achieve
scale.
Note Upgrading drives will allow older hardware to be used in a
multi-node cluster. However, we recommend that you use the latest
hardware available for the multi-node feature as this hardware will
have more powerful CPU, more memory and faster input/output
processing.
4-10 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 4 Planning a Cisco Unified Presence Multi-Node Deployment
Multi-Node Hardware Recommendations
Related Topics
• For a list of the supported hardware for the multi-node feature,
and hardware user assignment guidelines for the multi-node feature,
see the Cisco Unified Presence compatibility matrices at this
URL:
http://www.cisco.com/en/US/products/ps6837/products_device_support_tables_list.html
4-12 Deployment Guide for Cisco Unified Presence Release 7.0
Deploy
Performing a Cisco Unified Presence Multi-node Deployment
May 19, 2009
• How to Update a Multi-Node Configuration after Deployment, page
5-2
• How to Troubleshoot a Multi-Node Deployment, page 5-4
Note The purpose of this module is to provide the user with the
recommended sequence of high-level tasks for installing and
configuring the multi-node feature.
Performing a Fresh Multi-Node Installation We recommend that you
follow this sequence of tasks when you are configuring your
multi-node Cisco Unified Presence deployment.
The system topology interface allows you to configure the Cisco
Unified Presence multi-node feature, and manage your subclusters,
nodes and users.You access the system topology interface from the
Cisco Unified Presence Administration interface by selecting Cisco
Unified Presence > Topology.
You perform the system topology configuration for your Cisco
Unified Presence multi-node deployment on the Cisco Unified
Presence publisher node.
Before You Begin
Determine the type of multi-node deployment model you are going to
configure.
Restriction
Procedure
Step 1 Install and configure the Cisco Unified Presence publisher
node (the first server in the Cisco Unified Presence
cluster).
Step 2 (On the publisher node) Create all subclusters and nodes in
the cluster using the system topology interface.
5-1 ment Guide for Cisco Unified Presence Release 7.0
Chapter 5 Performing a Cisco Unified Presence Multi-node Deployment
How to Update a Multi-Node Configuration after Deployment
Step 3 (On the publisher node) Associate each of the subsequent
nodes in the cluster with the publisher node using the system
topology interface.
Step 4 Install and configure each of the subsequent nodes in the
cluster.
Step 5 (On the publisher node) Assign these nodes to the subcluster
arrangement as required using the system topology interface.
Step 6 When you have installed all the Cisco Unified Presence nodes
in the cluster, start the Sync Agent service on the publisher node
to synchronize with the Cisco Unified Communications Manager user
and device configuration information.
Step 7 When the synchronization is complete, start the Presence
Engine and Proxy services on each Cisco Unified Presence
node.
Step 8 (On the publisher node) Configure any intercluster peer
relationships with remote Cisco Unified Presence clusters.
Troubleshooting Topics
• Before you perform the installation of a subsequent Cisco Unified
Presence node, you must associate the subsequent node to the
Topology view of the publisher node.
• Do not assign the subsequent node to a subcluster until after you
install it. If you assign a subsequent Cisco Unified Presence node
to a subcluster prior to installing it, users in remote clusters
will not receive availability information. A presence outage will
occur until the node is installed.
Related Topics
• Multi-Node Hardware Recommendations, page 4-10
• Configuring a Cisco Unified Presence Server for Deployment in the
Network, page 6-1
• Creating Subclusters in System Topology, page 6-5
• Creating, Assigning and Moving Nodes in System Topology, page
6-5
• Configuring User Assignment in System Topology, page 6-7
• How to Turn On the Cisco Unified Presence Services, page
6-12
• Configuring a Cisco Unified Presence Intercluster Deployment,
page 13-1
• Installation and Upgrade Guide for Cisco Unified Presence
How to Update a Multi-Node Configuration after Deployment •
Performing a Software Upgrade, page 5-2
• Adding a New Node, page 5-3
• Expanding the Cluster, page 5-4
Performing a Software Upgrade
Your hardware must comply with the multi-node hardware
recommendations.
5-2 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 5 Performing a Cisco Unified Presence Multi-node Deployment
How to Update a Multi-Node Configuration after Deployment
Procedure
Step 1 Upgrade the Cisco Unified Presence publisher node
first.
Step 2 After you have upgraded the Cisco Unified Presence publisher
node, upgrade each subsequent Cisco Unified Presence node in the
cluster.
Step 3 Once all subscriber nodes have completed the upgrade,
sequentially switch the software to the new software release one
node at a time.
Step 4 Once the first subscriber has rebooted and has come back
online with the new software release, switch the software release
on the next subscriber node.
Step 5 Repeat Step 3 until the new software release is running on
all subscriber nodes.
Related Topics
• Installation and Upgrade Guide for Cisco Unified Presence
• Cisco Unified Communications Operating System Maintenance Guide
for Cisco Unified Presence
Adding a New Node Follow this procedure if you need to add new
nodes after a multi-node deployment is running.
Restrictions
Procedure
Step 1 Create a new subcluster in the system topology interface (if
required).
Step 2 Create a new node in the system topology interface.
Step 3 Install the new node.
Step 4 Assign the node to the subcluster (if required).
The node will be pulled into the cluster but will not receive
traffic until users are assigned to it.
Step 5 Assign users from other nodes to the new node as
required.
Related Topics
• Creating Subclusters in System Topology, page 6-5
• Creating, Assigning and Moving Nodes in System Topology, page
6-5
• Configuring User Assignment in System Topology, page 6-7
5-3 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 5 Performing a Cisco Unified Presence Multi-node Deployment
How to Troubleshoot a Multi-Node Deployment
Expanding the Cluster
• Your hardware must comply with the multi-node hardware
recommendations.
• We strongly recommend that any node movements that involve
unassigning or moving a large numbers of users is performed at off
peak times. Such large operations can adversely impact
performance.
Procedure
Step 1 Create the new subcluster(s) in the system topology
interface (if required).
Step 2 Create the new nodes in the system topology interface.
Step 3 Install each new node.
Step 4 Assign the nodes to the (new) subclusters.
Step 5 Once all the nodes are online, assign users to the new nodes
using the following user assignment options:
• Using the Find User Assignment feature, unassign selected users
from each node, and use the User Assignment Mode parameter to
reassign new users to new subcluster(s) and nodes.
• Using the Find User Assignment feature, manually move users to
new nodes.
• Unassign all users, and then reassign the users to the cluster
using the appropriate User Assignment Mode parameter setting for
the whole cluster.
Related Topics
• Creating Subclusters in System Topology, page 6-5
• Creating, Assigning and Moving Nodes in System Topology, page
6-5
• Configuring User Assignment in System Topology, page 6-7
How to Troubleshoot a Multi-Node Deployment • Monitoring a
Multi-Node System, page 5-4
• Resolving a Hardware Problem, page 5-5
Monitoring a Multi-Node System
Restriction
If you need to add hardware to your multi-node deployment, the
hardware must comply with the multi-node hardware
recommendations.
5-4 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 5 Performing a Cisco Unified Presence Multi-node Deployment
How to Troubleshoot a Multi-Node Deployment
Procedure
Step 1 Use the Cisco Unified Presence Real-Time Monitoring Tool
(RTMT) tool to monitor the CPU and memory usage of each Cisco
Unified Presence node in the cluster.
Step 2 Use these guidelines to determine if you need additional
hardware:
Related Topics
• About the Multi-Node Deployment Models, page 4-4
• For information on using the RTMT tool, see the Serviceability
Configuration and Maintenance Guide for Cisco Unified
Presence.
Resolving a Hardware Problem Follow this procedure if there is a
problematic server, or some general hardware failure.
Restrictions
If you need to add hardware to your multi-node deployment, the
hardware must comply with the multi-node hardware
recommendations.
Procedure
Step 1 Create a new node using the system topology interface.
Step 2 Perform a fresh installation on this node.
Step 3 Unassign the users from the problematic node.
Step 4 Stop all services on the problematic node.
Step 5 Unassign the problematic node.
Step 6 Assign the new node to the subcluster, replacing the
problematic node.
Deployment Model Recommendation
No High-Availability or Balanced Non-Redundant
High-Availability
If the CPU reaches more than 70% capacity for a sustained period on
any Cisco Unified Presence node, we recommend that you add hardware
resources to your deployment.
Balanced Redundant High-Availability If the CPU reaches more than
35% capacity for a sustained period on either Cisco Unified
Presence node in the subcluster, we recommend that you add hardware
resources to your deployment.
Active/Standby High-Availability If the CPU reaches more than 70%
capacity for a sustained period of time on the active Cisco Unified
Presence node, we recommend that you add hardware resources to your
deployment.
5-5 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 5 Performing a Cisco Unified Presence Multi-node Deployment
How to Troubleshoot a Multi-Node Deployment
Step 7 Reassign the unassigned users to the new node.
Step 8 Delete the problematic node.
Step 9 Activate all services on the new node.
Related Topics
• Creating, Assigning and Moving Nodes in System Topology, page
6-5
• Configuring User Assignment in System Topology, page 6-7
5-6 Deployment Guide for Cisco Unified Presence Release 7.0
Deploy
C H A P T E R 6
Configuring a Cisco Unified Presence Server for Deployment in the
Network
May 19, 2009
• How to Configure the System Topology on Cisco Unified Presence,
page 6-1 (Publisher node)
• Configuring a Cluster-Wide Cisco Unified Presence Address, page
6-8 (Publisher node)
• Uploading the Server Licence File on Cisco Unified Presence, page
6-9 (Publisher node)
• How to Configure the Presence Information on Cisco Unified
Presence, page 6-10 (All nodes)
• How to Turn On the Cisco Unified Presence Services, page 6-12
(All nodes)
How to Configure the System Topology on Cisco Unified
Presence
Note • This module is only applicable if you are configuring a
multi-node deployment.
• Perform the system topology configuration on the Cisco Unified
Presence publisher node.
• Before configuring the system topology, read the multi-node
planning and deployment information for best practice information
on configuring this type of deployment.
• See the online help in Cisco Unified Presence Administration for
additional instructions on configuring the system topology
interface.
• The system topology interface is only used to configure your
local Cisco Unified Presence cluster. See the intercluster peer
module for information on configuring intercluster peer
relationships with remote Cisco Unified Presence clusters.
• About Subcluster, Node and User Management Recommendations, page
6-2
• Creating Subclusters in System Topology, page 6-5
• Creating, Assigning and Moving Nodes in System Topology, page
6-5
• Configuring User Assignment in System Topology, page 6-7
6-1 ment Guide for Cisco Unified Presence Release 7.0
Chapter 6 Configuring a Cisco Unified Presence Server for
Deployment in the Network How to Configure the System Topology on
Cisco Unified Presence
About Subcluster, Node and User Management Recommendations • Node
Creation and Movement Recommendations, page 6-2
• Node Name Recommendations, page 6-2
• User Assignment Mode Recommendations, page 6-3
• Manual User Assignment Recommendations, page 6-3
• User Redistribution, page 6-4
Node Creation and Movement Recommendations
When you create nodes using the system topology interface you
can:
• Assign the nodes to a subcluster in Cisco Unified Presence, or
allow the nodes to remain unassigned. These states are
interchangeable.
• Assign Cisco Unified Presence users to the nodes, or allow the
nodes to remain without any user assignments.
• Move a node from one subcluster to another if the node is
assigned and has no users.
• Configure real pingable nodes, or logical nodes which can be
installed later and which remain inaccessible until that
time.
To move nodes with users assigned, perform one of the following
actions:
• Unassign the users, move the node, and then reassign the users to
the node. Note that when you unassign the users, they will lose
service.
• If you have a high-availability deployment, move the users to the
second node in the high-availability pair of nodes. Move the first
node and then reassign the users to the first node.
• Create a logical node and move the users to the logical node.
Move the node, reassign the users to the node, and remove the
logical node.
Note • You must remove all users from a node before you can
unassign or move it.
• We strongly recommend that you perform any node movements that
involve unassigning or moving a large numbers of users at off peak
times. Such large operations can adversely impact
performance.
Related Topics
• User Assignment Mode Recommendations, page 6-3
• Creating, Assigning and Moving Nodes in System Topology, page
6-50
Node Name Recommendations
By default, the name for a node is the hostname that you configure
during the Cisco Unified Presence installation. For example, if the
hostname of your Cisco Unified Presence node is called“cup1”, the
node name is “cup 1”. From the system topology interface, you can
change the node name to the dotted IP address or the FQDN, for
example, "192.168.0.1" or "cup1.acme.com". If you change the
default name for the node, note the following:
6-2 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 6 Configuring a Cisco Unified Presence Server for
Deployment in the Network How to Configure the System Topology on
Cisco Unified Presence
• You must be able to resolve the hostname or the FQDN from the
Cisco Unified Presence server, and Cisco Unified Personal
Communicator client computers.
• If either Cisco Unified Presence server or the Cisco Unified
Personal Communicator client computer cannot resolve the hostname
or the FQDN, you must configure the IP address for the node name
value.
• To test the name resolution from the Cisco Unified Presence
server, use the command
utils network ping <node_name>
• To test the name resolution from the Cisco Unified Personal
Communicator client computer, use the command
ping <node_name>
Related Topics
• Creating, Assigning and Moving Nodes in System Topology, page
6-5
User Assignment Mode Recommendations
You can manually or automatically assign users in a Cisco Unified
Presence deployment. You can manage user assignment using the User
Assignment Mode parameter on the Sync Agent on Cisco Unified
Presence.
You can set the User Assignment Mode parameter to Balanced
(automatic), Active/Standby (automatic), or None (manual):
• If set to Balanced, all users are equally divided across all
nodes in all subclusters. This mode is used for the Balanced Mode
Non-Redundant High-Availability and the Balanced Mode Redundant
High-Availability deployment options.
• If set to Active/Standby, all users are assigned only to the
first node of an subcluster. If there is only a single node in the
subcluster then this node is used for assignment regardless of the
location of the node within the subcluster.
• If set to None, the users are not automatically assigned to
subclusters and nodes. You must manually assign your users to nodes
using the system topology interface.
Note • If all hardware in a cluster is the same generation and has
the same capacity, then you should set the User Assignment Mode to
Balanced.
• If you have hardware of mixed generations and capacities in a
node, then you should set the User Assignment Mode to None. You
must then assign users manually to make sure that each server is
not loaded beyond capacity.
Related Topics
• Turning On the Sync Agent, page 6-12
Manual User Assignment Recommendations
If you select to manually assign users from the system topology
interface, note the following:
6-3 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 6 Configuring a Cisco Unified Presence Server for
Deployment in the Network How to Configure the System Topology on
Cisco Unified Presence
• You can manually unassign, assign or reassign users. You can
assign users to a single node, and you can also distribute groups
of users across the node, or nodes, in a cluster, or a given
subcluster.
• If you assign a user to one of the nodes in a subcluster, the
other node in the subcluster becomes the backup (redundant) node
for the user. If you do not configure a backup node in the
subcluster, the user does not have high-availability failover
protection.
• Users who are assigned may be reassigned, that is, moved to
another subcluster, or to a specific node. You can move users
individually or in bulk.
• Users can remain unassigned. Unassigned users do not receive
availability information.
When you are assigning users, note the following:
• You can only assign users if they are licensed.
• Unassigning or reassigning users results in termination of active
sessions. In such instances, clients must reconnect to the new
location.
• You can export users in bulk using the Bulk Administration Tool
(BAT). You can also use BAT to perform bulk user reassignment from
one node to another.
We recommend that you take the Presence Engine and Proxy services
offline when performing bulk operations. Note that taking these
services offline will adversely impact performance.
Related Topics
• Configuring User Assignment in System Topology, page 6-7
• User Redistribution, page 6-4
User Redistribution
After adding or removing nodes, you can redistribute users using
the Rebalance Users parameter on the system topology interface.
This parameter redistributes users based on the configured User
Assignment mode. These are examples of how you can use the
Rebalance Users parameter with the User Assignment mode to manage
user assignment:
• Scenario A: The customer has a subcluster with two nodes, and
each node contains 5000 users. The User Assignment mode is set to
Balanced. The customer then adds a second subcluster with two
nodes, and sets the Rebalance Users parameter, the users are evenly
distributed to the four nodes. Each node now has 2500 users.
• Scenario B: The customer has a subcluster with two nodes, and
each node contains 2500 users. The User Assignment mode is set to
Balanced. The customer wants to add a second subcluster with two
nodes, but also wants to change the User Assignment mode to
Active/Standby. The customer changes the mode to Active/Standby,
whereby all 5000 users are redistributed to the first node in the
subcluster. The customer then adds a second subcluster with two
nodes, and sets the Rebalance Users parameter. The users are evenly
distributed across both first nodes in each subcluster. Each first
node now has 2500 users.
We strongly recommend that any node movements that involve
unassigning or moving a large numbers of users are performed at off
peak times. Such large operations can adversely impact
performance.
Related Topics
• Configuring User Assignment in System Topology, page 6-7
6-4 Deployment Guide for Cisco Unified Presence Release 7.0
Chapter 6 Configuring a Cisco Unified Presence Server for
Deployment in the Network How to Configure the System Topology on
Cisco Unified Presence
Creating Subclusters in System Topology The Cisco Unified Presence
publisher node is automatically assigned to a subcluster in the
system topology interface. Following the installation of the Cisco
Unified Presence publisher node, you must create the required
subclusters and subsequent nodes in your Cisco Unified Presence
cluster.
Repeat this procedure for each subcluster that you require for your
deployment.
Note Perform this procedure on the
LOAD MORE