Filter
Top Products
Alerts System Management and Maintenance
Polycom, Inc. 339
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).
An out-of-service cluster is still running and accessible via the management
interface, but doesn’t accept any calls or registrations.
Click the link to go to the DMAs page.
See also:
“Alerts” on page 338
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:
“Alerts” on page 338
Alert 1004
Cluster <cluster> is not reachable. Last heartbeat received YYYY-MM-DD
HH:MM GMT+/-H[:MM].
The specified cluster is no longer communicating with the supercluster. The
server(s) may be offline or rebooting, or there may be a network problem.
Click the link to go to the DMAs page.
See also:
“Alerts” on page 338
Alert 1101
Territory <territory> not active; Both primary cluster <p-cluster> and backup
cluster <b-cluster> are not operational.
The territory’s primary and backup cluster are both unreachable.
This may indicate serious network problems. It’s also possible that someone
shut both clusters down, or shut down one and the other then failed, or both
failed (unlikely).