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

When the VCS is using the TMS Provisioning Extension FindMe service, the VCS administrator can only
view the FindMe account information that is being supplied via the FindMe service (by going to
Applications > TMS Provisioning Extension services > FindMe > ...
All FindMe account information is managed within TMS.
TMS Provisioning Extension services not in use
When the TMS Provisioning Extension services are not in use (the VCS is either running in "standalone
FindMe" mode, or is still in TMS Agent legacy mode), FindMe accounts can be managed on the VCS:
The VCS administrator can create or edit users' FindMe account information. The changes can be made on
n
any peer in the cluster and any modifications are replicated to all other peers.
You must define a Cluster name if you are using FindMe, even if the VCS is not part of a cluster.
n
If you change the Cluster name after creating your user accounts you will have to reconfigure those
n
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
guide.
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.
Cisco VCS Administrator Guide (X7.1)
Clustering and peers
and then the relevant table).
FindMe deployment
Maintaining a cluster for more
Page 144 of 479
Status >