DMA Operations Guide

Alerts

 

 

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 359

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 359

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).

Click the link to go to the Territories page. To enable conferencing to continue in the territory (at diminished capacity), assign it to some other cluster.

See also:

“Alerts” on page 359

Alert 1102

Territory <territory> not active; cluster <cluster> is not operational.

The territory’s primary cluster is unreachable and it has no backup cluster.

This may indicate a network problem. It’s also possible that someone shut the cluster down or that it failed.

360

Polycom, Inc.

Page 372
Image 372
Polycom 3725-76302-001LI manual Hhmm GMT+/-HMM