Filter
Top Products
Polycom, Inc. 346
Alert 2002
Resource management system <system-name> unreachable. Last contact on:
YYYY-MM-DD HH:MM GMT+/-H[:MM].
The cluster responsible for RealPresence Resource Manager or CMA integration was unable to connect to
the Polycom RealPresence Resource Manager or CMA system.
This may indicate a network problem or a problem with the Polycom RealPresence Resource Manager or
CMA system.
Try logging into the Polycom RealPresence Resource Manager or CMA system. If you can do so, make sure
the login credentials that the RealPresence DMA system uses to connect to it are still valid.
See also:
Alerts on page 342
Alert 2004
Resource management system <system-name> has inconsistent territory
definitions in its site topology.
The system is integrated with a Polycom RealPresence Resource Manager or CMA system, and there is a
problem with the territory definitions or responsibility assignments in the site topology data imported from
that system.
On the Polycom RealPresence Resource Manager or CMA 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.
See also:
Alerts on page 342
Alert 2101
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 342