DMAs Superclustering
Polycom, Inc. 231
The Stop Using command takes the selected cluster immediately out of
service:
•Existing calls and conferences on the selected cluster are disconnected. No
new calls or conferences are allowed to start. All registrations are rejected.
The cluster ceases to manage bandwidth.
•Territories for which the selected cluster has primary responsibility and a
different cluster has backup responsibility are transferred to the backup
cluster.
•Registrations are seamlessly transferred to the backup cluster (for
endpoints that support this). Bandwidth usage data for ongoing calls is
seamlessly transferred to the backup cluster.
The Start Using command puts the selected cluster back into service:
•New calls and conferences are allowed to start. The cluster begins
bandwidth management.
•The cluster assumes control of any territories for which it has primary
responsibility, or for which it has backup responsibility and the primary
cluster is offline.
•For territories for which the restarted cluster is the primary, existing calls
and conferences on the backup cluster continue, but no new conferences
are allowed to start. New calls are allowed to start only if they are
associated with existing conferences. The backup cluster ceases to manage
bandwidth.
•Registrations are seamlessly transferred to the restarted primary cluster,
where supported by the endpoint. Bandwidth usage data for ongoing calls
is seamlessly transferred to the restarted primary cluster.
The following table describes the fields on the page.
Warnin g
Restart Supercluster Services and Reset Supercluster Services are
emergency actions that should only be taken when instructed to do so by a
Polycom Global Services representative. They’re intended only for resolving data
store replication problems that can’t be resolved by other means.
Restart Supercluster Services restarts supercluster services on the selected
cluster. All calls are terminated and the cluster becomes unresponsive for a short
period of time.
Reset Supercluster Services hard-resets supercluster services on the selected
cluster and resets the cluster to its initial defaults. This results in the loss of data.
All calls are terminated, and the cluster is forced to leave the supercluster and
rebooted.