Polycom 7000 User Manual
System Management and Maintenance
Polycom, Inc.
355
Alert 2106
Cluster <cluster>: Failed connection from <server> to Active Directory for user
authentications at YYYY-MM-DD HH:MM GMT+/-H[:MM].
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.
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.
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.
RealPresence DMA system uses to connect to Active Directory are still valid and update them if necessary.
See also:
Alert 2107
Failed connection from <cluster> to Active Directory for user caching at YYYY-MM-DD
HH:MM GMT+/-H[:MM].
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:
Alert 2108
<alerting-cluster>: Active Directory primary cluster <p-cluster> associated with territory
<territory> is not reachable. But backup cluster <c-cluster> is reachable.
<territory> is not reachable. But backup cluster <c-cluster> is reachable.
The territory’s primary cluster assigned to do Active Directory integration is not reachable. The territory’s
backup cluster assigned to do Active Directory integration is reachable.
backup cluster assigned to do Active Directory integration is reachable.
This may indicate a network problem. It’s also possible that someone shut the primary cluster down or that
it failed.
it failed.
Click the link to go to the Network > DMAs page. Log in to the affected cluster, if possible, and check the
health of the cluster. Determine whether the cluster was deliberately shut down. If not, try pinging the
cluster’s IP addresses.
health of the cluster. Determine whether the cluster was deliberately shut down. If not, try pinging the
cluster’s IP addresses.
See also
Exchange Server Integration
The following alerts provide information on changes in Exchange server integration status.