Table of Contents
Advertisement
● There may be a network problem.
Click the link to go to the DMAs page.
See also:
Alerts
Territory Status
The following alerts provide information on changes in territory status.
Alert 1103
No clusters assigned to <list of territories>.
The specified territory or territories are not assigned to a cluster, so any responsibilities assigned to the
territories are not being fulfilled.
Click the link to go to the Territories page. Assign a primary and backup cluster for every territory in your
site topology.
See also:
Alerts
Alert 1105
<alerting-cluster>: Primary cluster <p-cluster> and backup cluster <b-cluster> are not
reachable. Territory <territory> may not be functioning.
The cluster from which the alert originated is unable to communicate with the specified territory's primary
and backup clusters.
This may be a temporary problem, in which case this alert will be cleared as soon as the alerting cluster is
once again able to communicate with the clusters in question.
If this alert reoccurs frequently but quickly goes away, that suggests intermittent spurious network problems.
If it persists for more than about 15-30 seconds, it 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
Alert 1106
<alerting-cluster>: Cluster <cluster> is not reachable. Territory <territory> may not be
functioning.
The cluster from which the alert originated is unable to communicate with the specified territory's primary
cluster, and there is no backup cluster.
This may be a temporary problem, in which case this alert will be cleared as soon as the alerting cluster is
once again able to communicate with the cluster in question.
Polycom, Inc.
System Management and Maintenance
350
Advertisement
Table of Contents
