Clustering And Presence; Clustering And Tms; About The Cluster Subzone - Cisco TelePresence Administrator's Manual

If you are part of a large enterprise with, for example, TMS managing several VCS clusters, the FindMe
n
database may contain details of users and devices in other VCS clusters. Different clusters are
distinguished by their Cluster name.
You cannot modify the details of accounts that are not managed in your cluster. If you try to edit an
l
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
information on configuring the cluster name.

Clustering and Presence

Clustering supports the use of Presence.
All peers in the cluster must have identical SIP domain, Presence Server and Presence User Agent (PUA)
n
configuration.
If peers in the cluster have the PUA enabled, each peer publishes information about its own local
n
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
n
cluster.
When viewing presence status on a peer in a cluster:
Publishers shows all presentities across the cluster for whom presence information is being published.
n
Presentities shows any presentity for whom a subscription request has been received on the local VCS
n
only.
Subscribers shows each endpoint from which a subscription request has been received on the local VCS
n
only.

Clustering and TMS

You are recommended to use TMS when running a cluster of VCSs.
TMS (version 12.6 or later) is mandatory if your cluster is configured to use FindMe or Device Provisioning.
n
See VCS Cluster creation and maintenance deployment guide
TMS.

About the Cluster Subzone

When two or more VCSs are clustered together, a new subzone is created within the cluster's Local Zone.
This is the Cluster Subzone (see the diagram in the
the cluster will briefly pass via this subzone during call setup.
The Cluster Subzone is (like the Traversal Subzone) a virtual subzone used for call routing only, and
endpoints cannot register to this subzone. After a call has been established between two peers, the Cluster
Subzone will no longer appear in the call route and the call will appear as having come from (or being routed
to) the Default Subzone.
The two situations in which a call will pass via the Cluster Subzone are:
Cisco VCS Administrator Guide (X7.2)
Maintaining a cluster
for more information about using clusters with
About clusters section). Any calls between two peers in
Clustering and peers
for more
Page 157 of 498