DMA Operations Guide

Alerts

 

 

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 359

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

See also:

“Alerts” on page 359

Alert 2105

Active Directory service is not available. Cluster <p-cluster> is not operational.

The primary cluster for the territory responsible for Active Directory integration 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.

Click the link to go to the DMAs page to begin troubleshooting. We recommend assigning a backup cluster for each territory. See also:

“Alerts” on page 359

364

Polycom, Inc.

Page 376
Image 376
Polycom 3725-76302-001LI manual 364