Filter
Top Products
Polycom, Inc. 362
See also:
Alerts on page 342
Alert 4004
MCU <MCUname> is configured with insufficient user connections.
The system was unable to establish an additional management session connection to the specified MCU.
Possible explanations:
● IP connectivity between the system and the MCU has been lost.
● This MCU doesn’t allow sufficient connections per user.
Polycom MCUs use synchronous communications. In order to efficiently manage multiple calls as quickly
as possible, the Polycom RealPresence DMA system uses multiple connections per MCU. By default, a
RealPresence Collaboration Server or RMX MCU allows up to 20 connections per user (the
MAX_NUMBER_OF_MANAGEMENT_SESSIONS_PER_USER system flag). We recommend not
reducing this setting. If you have a RealPresence DMA supercluster with three Conference Manager
clusters and a busy conferencing environment, we recommend increasing this value to 30.
After a connection attempt fails and this alert is triggered, the system tries every 60 seconds to establish 5
connections to this MCU. If it succeeds, this alert is automatically cleared.
Click the link to go to the Network > MCU > MCUs page.
See also:
Alerts on page 342
Alert 4005
MCU <MCUname> disconnected.
The reporting cluster is unable to connect to the specified MCU.
This may indicate a network problem. It’s also possible that someone shut the MCU down or that it failed.
Click the link to go to the Network > MCU > MCUs page for more information.
See also:
Alerts on page 342
Alert 4009
MCU <mcu> disconnect rate is > 1 and < 4.
The RealPresence DMA cluster has lost connection with the specified MCU between one and four times in
the past 24 hours.
This most likely indicates a network problem, but it could also indicate that the MCU or RealPresence DMA
system is under very heavy load. If the MCU stays connected for more than 24 hours, this alert is cleared,
but if the RealPresence DMA system loses connection with this MCU more than 4 times in 24 hours, this
alert is replaced with Alert 4010.