Polycom RealPresence 1800 Administration Manual page 382

Collaboration server
Hide thumbs Also See for RealPresence 1800:
Table of Contents

Advertisement

MMCU Components Restart
The MMCU system strives to return to the state it was in at the point of restart, or improve it, whether the
restart was performed on the Main MCU or on one of the Soft Blades.
The most significant point of improvement being when a Soft Blade had a Disconnected status before its
restart, and could be pinged right after it, in which case it goes through the process described above from
its starting point, and ends either as Ready or Faulty.
There is however, a single irregular behavior if a Soft Blade is in Soft Blade Pend Authentication state prior
to the Main MCU restart. In this case following this restart, due to the lack of Salt ping, the Soft Blade is
perceived by the Main MCU as Disconnected, and is displayed as such. Thus, once the Administrator enters
the password at the Soft Blade, the Soft Blade is ready to continue from Soft Blade Pend Authentication (and
not from Disconnected), and its state becomes Installing.
During restart of:
● Soft Blade - The Main MCU modifies the Soft Blade state to Disconnected.
● Main MCU - All conferences and translators, both on the Main MCU and the Soft Blades, are
disconnected.
IP Address Management
The Soft Blades' initial IP address is provided by the DHCP server. An Administrator user is then required
to log on using the console wizard, and configure the Main MCU (Salt master) IP address mode, either as
DHCP or as static.
Note: IP Address Type
Currently, only IPv4 address type is supported for Soft Blade IP addresses.
However, the Soft Blades management is independent of their IP addresses. Therefore, following restart,
though some of the Soft Blades may be assigned a new IP address by the DHCP server during their
Initialization state, the Main MCU is not affected by that change - the Soft Blades are recognized in the
system, and are assigned a state relevant to their state before restart. For example, if a Soft Blade already
passed both authentication states, it does not require re-acceptance by the Administrator.
If a new Soft Blade is assigned an IP address which was previously assigned to a currently Disconnected
Soft Blade, it goes through the authentication phases from the beginning. The Disconnected machine,
when it becomes operable, is reassigned a new IP address by the DHCP server, though during its
Disconnected state it does appear in the list of Soft Blades in the UI.
When a Soft Blade is re-assigned to an alternate Main MCU, until deleted from its original Main MCU, it is
considered as Disconnected by this MCU.
RDP Content
Skype for Business clients can share content using a Remote Desktop Protocol (RDP). Standard endpoints
does not support RDP and hence it uses the H.239 (for H.323 endpoints) or BFCP (for SIP endpoints). In
order to enable content sharing between Skype for Business clients and standard room endpoints,
RealPresence Collaboration Server can be used (when configured to work in Modular MCU mode).
Polycom, Inc.
Appendix - Modular MCU
361

Advertisement

Table of Contents
loading

This manual is also suitable for:

Realpresence 2000Realpresence 4000

Table of Contents