Polycom RealPresence 1800 Administration Manual page 379

 If the Soft Blade resources are all consumed, an Active Alarm is generated indicating no
resources are available on this Soft Blade.
Click the Up-Arrow on the monitor until the original System Monitor is displayed.
3 Right-click on the Main MCU to display its properties.
Or
Right-click on any of the Soft Blades to select one of the currently available actions for this Soft Blade.
Note: Monitoring Dependency on MCU Infrastructure
When not in MMCU mode, the MCU operates as it used to before this infrastructure was created: Soft
Blades are not visible, and Main is replaced by RMX (for HW MCUs).
Monitoring Guidelines
● Only an Administrator user may perform actions or changes on any of the Soft Blades.
● All columns specific to MMCU mode are hidden while not in MMCU mode, for Main MCU, Soft Blades
and participants.
MMCU Impact on Participant Monitoring
The MMCU infrastructure impacts not only in the general system operation, but also the participant
monitoring in general, as well as the Participant Properties - General tab.
When monitoring conference participants, the participant type is indicated by the Alias Name.
In the Participant Properties - General tab, when in MMCU mode, and for participants using a Translator
(such as RDP content), the Participant Properties reflect the Soft Blade IP address, as well as the
Translator ID and type, which reflect the endpoint type, thus making the Endpoint Type field at the top
(disabled) irrelevant.
Note that a Translator ID equaling 0, denotes a non-Translator participant, since it is either AVC or SVC.
In addition, viewing a specific Translator Properties (or double-clicking it), results in opening the Participant
Properties for the participant serviced by that Translator, meaning the information reflects the endpoint and
not the translator itself.
Also, no Translator information is displayed for WebRTC participants in 8.7.1, since in that version, these
participants are handled by the main MCU, and not by Translators residing in Soft Blades.
Faults and Active Alarms
When an attempt is made to assign a Soft Blade to a Main MCU with full Soft Blade assignment, a fault event
is generated indicating the maximum number of Soft Blades was reached for this Main MCU.
In the Main MCU, there are two generated Active Alarms:
● When the Main MCU cannot communicate with the Soft Blade application, though it does manage to
ping it - Soft Blade <name> status has changed to Faulty.
● When the Main MCU cannot communicate with the Soft Blade application, nor ping it - Soft Blade
<name> status has changed to Disconnected.
Polycom, Inc.
Appendix - Modular MCU
358