Alerts System Management and Maintenance
Polycom, Inc. 363
Active Directory integration was not successful on cluster <cluster>.
The cluster responsible for Active Directory integration was unable to update
the cache of user and group data.
This may indicate a network problem or a problem with the AD.
If the cluster was unable to log into the AD server, alert 2107 is also generated.
Click the link to go to the Microsoft Active Directory page and check the
Active Directory Connection section.
See also:
“Alerts” on page 359
Alert 2102 Zero enterprise conference rooms exist on cluster <cluster>.
The cluster responsible for Active Directory integration successfully retrieved
user and group data, but no conference rooms were generated.
This may indicate that no directory attribute was specified from which to
generate conference room IDs, or that the chosen attribute resulted in empty
(null) conference room IDs after the system removed the characters to remove.
Click the link to go to the Microsoft Active Directory page and check the
Enterprise Conference Room ID Generation section. If necessary, check the
Active Directory and determine an appropriate directory attribute to use.
See also:
“Alerts” on page 359
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.