Polycom, Inc. 363
Click the link to go to the Network > MCU > MCUs page to begin troubleshooting. Check the network
connection between this MCU and the RealPresence DMA cluster.
See also:
Alerts on page 342
Alert 4010

MCU <mcu> disconnect rate is > 4.

The DMA cluster has lost connection with the specified MCU more than 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.
Click the link to go to the Network > MCU > MCUs page to begin troubleshooting. Check the network
connection between this MCU and the RealPresence DMA cluster.
See also:
Alerts on page 342
Alert 4011

MCU <mcu> call failure rate is > 0.4 and < 0.8.

The specified MCU’s number of consecutive failed calls has changed, and the calculated failure rate metric
is now between 0.4 (some calls are failing) and 0.8 (most calls are failing).
The RealPresence DMA system keeps track of per-MCU call failure rates not only to alert administrators to
call failures, but also to ensure that calls will be routed less often to MCUs with high call failure rates. See
MCU Availability and Reliability Tracking on page148 for more information.
Click the link to go to the Network > MCU > MCUs page to begin troubleshooting.
See also:
Alerts on page 342
Alert 4012

MCU <mcu> call failure rate is > 0.8.

The specified MCU’s number of consecutive failed calls has changed, and the calculated failure rate metric
is now above 0.8.
This indicates that most of the specified MCU’s calls are failing. The RealPresence DMA system keeps track
of per-MCU call failure rates not only to alert administrators to call failures, but also to ensure that calls will
be routed less often to MCUs with high call failure rates. See MCU Availability and Reliability Tracking on
page 148 for more information.
Click the link to go to the Network > MCU > MCUs page to begin troubleshooting.
See also:
Alerts on page 342