Polycom 3725-76302-001O Manual De Usuario
Polycom, Inc.
347
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.
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.
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.
ID Generation section. If necessary, check the Active Directory and determine an appropriate directory
attribute to use.
See also:
Alert 2104
Active Directory service is not available. Both primary cluster <p-cluster> and
backup cluster <b-cluster> are not operational.
backup cluster <b-cluster> are not operational.
The primary and backup cluster for the territory responsible for Active Directory integration are both
unreachable.
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).
shut down one and the other then failed, or both failed (unlikely).
Click the link to go to the RealPresence DMAs page to begin troubleshooting. Determine whether the
clusters were deliberately shut down. If not, try pinging the clusters’ IP addresses.
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).
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:
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.
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 RealPresence DMAs page to begin troubleshooting. Determine whether the
cluster was deliberately shut down. If not, try pinging the cluster’s IP addresses.
cluster was deliberately shut down. If not, try pinging the cluster’s 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 cluster probably has other territory-related responsibilities
AD-related problem. But the unavailable cluster probably has other territory-related responsibilities