Appendix - Modular MCU
Polycom, Inc. 371
For both of non-modular MCU and modular MCU, to upgrade from any versions earlier than version 8.5 to
version 8.7.1, the intermediate upgrade to 8.5, 8.6 or the maintenance releases of both versions is needed.
Virtual Edition Modular MCU Upgrade Storage Requirements
If the modular MCU is virtual edition, sufficient storage for modular MCU and its soft blades is required:
● For modular MCU storage requirements, see Virtual Edition Host Server Platform Profile.
● For soft blades storage requirements, see Soft Blade Prerequisites.
In case of insufficient storage, the upgrade will not start, and an active alarm “Insufficient storage space for
upgrade” will be raised.
Monitor Soft Blades Upgrade
The modular MCU and its soft blades upgrade process can be monitored through the RMX Management >
MMCU System Monitor.
● If soft blades upgrade normally, Upgrading displays in each soft blade row.
The following table shows other soft blades status and behaviors:
● If any soft blades failed to be upgraded, Upgrade failed displays in the modular MCU row.
During the modular reboot process, once the modular MCU is verified as an invalid system, the
modular MCU will use the previous version software instead and issue an active alarm, in this
case, the soft blades will be downgraded automatically to match the main MCU version.
You can manually install the new version software on soft blades, which failed to be upgraded. For
information of installing soft blades, see Deployment of Soft Blades in a Modular MCU.
Only the soft blades are upgraded successfully will work actively with the modular MCU.
Soft blade status and expected behavior
Status Behaviors
Pending authentication No action.
Once the modular MCU is authenticated it will be upgraded.
Soft blade pending
authentication
No action.
Once the soft blade is authenticated it will be upgraded.
Rejected Remain rejected.
Initializing Start upgrade.
Ready Start upgrade.
Faulty Start upgrade.
Disconnected No action.
Disabled Start upgrade.