Polycom 3725-76302-001O manual Polycom, Inc 348

(Conference Manager and/or Call Server), so you may need to assign the affected territory to some other cluster.

We recommend assigning a backup cluster for each territory. See also:

Alerts on page 342

Alert 2106

Cluster <cluster>: Failed connection from <server> to Active Directory for user authentications at YYYY-MM-DD HH:MM GMT+/-H[:MM].

The specified server tried to connect to the Active Directory in order to authenticate a user’s credentials and was unable to do so. This may indicate a network problem or a problem with the AD itself.

If the network and the AD itself both appear to be OK, the connection attempt may have failed because the cluster was unable to log into the AD server.

Click the link to go to the Microsoft Active Directory page. Make sure the login credentials that the RealPresence DMA system uses to connect to Active Directory are still valid and update them if necessary.

See also:

Alerts on page 342

Alert 2107

Failed connection from <cluster> to Active Directory for caching at YYYY-MM-DD HH:MM GMT+/-H[:MM].

The cluster responsible for Active Directory integration was unable to log into the AD server. Click the link to go to the Microsoft Active Directory page.

See also:

Alerts on page 342

Alert 2201

Exchange server integration primary cluster <p-cluster> is not operational. Integration by backup cluster <b-cluster>.

The primary cluster for the territory responsible for Exchange server integration is unreachable, and its backup cluster has taken over responsibility for monitoring the Polycom Conferencing user mailbox and accepting or declining the meeting invitations received.

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 RealPresence DMAs page to begin troubleshooting.

See also:

Alerts on page 342

Polycom, Inc. 348