Clustering And Findme; Clustering And Presence; Clustering And Cisco Tms - Cisco TelePresence Administrator's Manual

Grey Headline (continued)
Managing clusters and peers

Clustering and FindMe

Overview
Clustering supports the use of FindMe. Each peer has its own
FindMe database containing all user account information for
the cluster. When a user account is created or edited on one
peer, that peer shares the information about the changes to all
other peers in the cluster, which then update their own FindMe
databases accordingly.
There is a limit of 10,000 FindMe user accounts per VCS
cluster. Multiple clusters are required if you have more
than 10,000 users.
Note that the replication of FindMe database information uses
a different mechanism (the TMS Agent) to that used to replicate
configuration information. Configuration information must
be changed on the master peer only, but changes to FindMe
information can be made on any peer and will be shared with all
other peers.
If you are part of a large enterprise with, for example, Cisco
TMS managing several VCS clusters, the FindMe database
may contain details of users and devices in other VCS clusters.
Different clusters are distinguished by their Cluster name (see
below). You cannot modify the details of accounts that are not
managed in your cluster.
Cluster name
You must define a Cluster name if you are using FindMe, even if
the VCS is not part of a cluster.
If you change the cluster name after creating your user accounts
you will have to reconfigure those accounts to associate them
with the new cluster name. You can do this by running the
transferfindmeaccounts script. Instructions for how to do this are
contained in the FindMe Deployment Guide
Alterntively, if you try to edit an account that belongs in a
different cluster the system gives you an option to Move this
account to local cluster. Selecting this option updates that
particular account so that it now belongs to your local VCS
cluster and hence lets you edit that account's details.
See Configuring clusters for more information on configuring the
cluster name.
Overview and System
Introduction
status configuration
D14049.08
November 2010
Clustering supports the use of Presence.
All peers in the cluster must have identical SIP domain,
Presence Server and Presence User Agent (PUA) configuration.
If peers in the cluster have the PUA enabled, each peer
publishes information about its own local registrations. This
information is routed to a Presence Server authoritative for the
cluster's domain.
If peers have the Presence Server enabled, the Presence
database is replicated across all peers in the cluster.
When viewing presence status
•
Publishers will show all presentities across the cluster for
whom presence information is being published.
•
Presentities will show any presentity for whom a subscription
request has been received on the local VCS only.
•
Subscribers will show each endpoint from which a
subscription request has been received on the local VCS only.
[29].
Cisco VCS Zones and
configuration neighbors

Clustering and Presence

on a peer in a cluster:
Clustering and Call Bandwidth
peers processing control
82
CISCO TELEPRESENCE VIDEO COMMUNICATION SERVER

Clustering and Cisco TMS

You are recommended to use Cisco TMS when running a
cluster of VCSs. For full information, refer to the Cisco TMS
documentation.
•
Cisco TMS (version 12.5 or later) is mandatory if your cluster
is configured to use FindMe or Device Provisioning.
If you were using Cisco TMS to manage a cluster running
a version of the VCS software prior to X5, refer to the
Deployment Guide - Creating a Cluster of VCS peers [27]
upgrade instructions.
In previous VCS releases, replication between peers was
managed by Cisco TMS. From VCS version X4 onwards,
replication is managed by the VCSs themselves.
Firewall
Applications Maintenance
traversal
ADMINISTRATOR GUIDE
VCS
for
Appendices