Polycom 7000 User Manual
System Management and Maintenance
Polycom, Inc.
349
Supercluster Status
The following alerts provide information on changes in cluster and supercluster status.
Alert 1001
Cluster <cluster> is busied out as of YYYY-MM-DD HH:MM GMT+/-H[:MM].
You or another administrator busied out the cluster, perhaps for maintenance.
A busied-out cluster allows existing calls and conferences to continue and accepts new calls for existing
conferences, but doesn’t accept other new calls and conferences.
conferences, but doesn’t accept other new calls and conferences.
Once all existing calls and conferences have ended, the cluster is out of service.
Click the link to go to the DMAs page.
See also:
Alert 1002
Cluster <cluster> is out of service as of YYYY-MM-DD HH:MM GMT+/-H[:MM].
You or another administrator took the cluster out of service (or busied out the cluster, and now all calls and
conferences have ended).
conferences have ended).
An out-of-service cluster is still running and accessible via the management interface, but doesn’t accept
any calls or registrations.
any calls or registrations.
Click the link to go to the DMAs page.
See also:
Alert 1003
Cluster <cluster> is orphaned.
The replication link with the specified cluster seems to be corrupted.
Click the link to go to the DMAs page. Try removing that cluster from the supercluster and then rejoining.
See also:
Alert 1004
Cluster <cluster> is not reachable. Last heartbeat received YYYY-MM-DD HH:MM
GMT+/-H[:MM].
GMT+/-H[:MM].
The specified cluster is not sending scheduled heartbeats. Possible reasons include:
● The cluster may simply be very busy and have fallen behind in sending heartbeats.
● An internal process could be stuck.
● The server(s) may be offline or rebooting.
● An internal process could be stuck.
● The server(s) may be offline or rebooting.