Alerts System Management and Maintenance
Polycom, Inc. 343
See also:
“Alerts” on page 338
Alert 2103 Active Directory primary caching cluster <p-cluster> is not operational.
Caching by backup cluster <b-cluster>.
The primary cluster for the territory responsible for Active Directory
integration is unreachable, and its backup cluster has taken over responsibility
for the caching of AD data.
This may indicate a network problem. It’s also possible that someone shut the
cluster down or that it failed.
Click the link to go to the DMAs page. Determine whether the cluster was
deliberately shut down. If not, try pinging the cluster’s IP addresses.
If this is a two-server cluster, and you can’t ping either the virtual or physical
IP addresses, look for a network problem. It’s unlikely that both servers have
failed simultaneously.
If you can ping the cluster, the OS is running, but the application may be in a
bad state. Try rebooting the server(s).
See also:
“Alerts” on page 338
Alert 2104 Active Directory service is not available. Both primary cluster <p-cluster> and
backup cluster <b-cluster> are not operational.
The primary and backup cluster for the territory responsible for Active
Directory integration 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 DMAs page to begin troubleshooting. Determine
whether the clusters were deliberately shut down. If not, try pinging the
clusters’ IP addresses.
Other clusters can continue using the shared data store from the last cache
update, so there is no immediate AD-related problem. But the unavailable
clusters probably have other territory-related responsibilities (Conference
Manager and/or Call Server), so you may need to assign the affected territory
to some other cluster(s).