Polycom 7000 User Manual
System Management and Maintenance
Polycom, Inc.
353
Try logging into the Polycom RealPresence Resource Manager system. If you can do so, make sure the
login credentials that the RealPresence DMA system uses to connect to it are still valid.
login credentials that the RealPresence DMA system uses to connect to it are still valid.
See also:
Alert 2004
Resource management server <system-name> has inconsistent territory definitions in its
site topology.
site topology.
The system is integrated with a Polycom RealPresence Resource Manager system, and there is a problem
with the territory definitions or responsibility assignments in the site topology data imported from that
system.
with the territory definitions or responsibility assignments in the site topology data imported from that
system.
On the Polycom RealPresence Resource Manager system, configure territories properly (for instance, no
duplicate names) and in way that meets the needs of the RealPresence DMA system. Assign
responsibilities (primary and backup) for the territories to the appropriate RealPresence DMA clusters. A
territory can only host conference rooms if it’s assigned to a RealPresence DMA cluster.
duplicate names) and in way that meets the needs of the RealPresence DMA system. Assign
responsibilities (primary and backup) for the territories to the appropriate RealPresence DMA clusters. A
territory can only host conference rooms if it’s assigned to a RealPresence DMA cluster.
See also:
Active Directory Integration
The following alerts provide information on changes in Active Directory integration status.
Alert 2101
Active Directory user and group cache update was not successful on cluster <cluster>.
The cluster responsible for Active Directory integration was unable to update the cache of user and group
data.
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.
section.
See also:
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.