Polycom RealPresence 1800 Administration Manual page 391

 A specific conference
 A specific participant in a conference
● The resulting log files are stored in the Main MCU, under MMCU/Logger/Collector FS as follows:
 CollectInfo_<begin date&time>-<end date&time>.tgz - A log file for the Main MCU.
 A folder named Blades, for log files filtered from all the Soft Blades. Under this folder there are:
 Folders named Translator.<ID>, for each of the Soft Blades log files.
 A folder named Translator.777777, for log files filtered from the local Translators (i.e.
Translators residing on the Main MCU, such as for WebRTC).
● Each of the filtered log files is limited to 100MB.
● Furthermore, when a filter specifies a conference/participant, for which one of the involved Soft
Blades is inoperable, the user is notified that the returned logs are partial (for a conference), or cannot
be supplied (for a participant in the specified conference).
To filter logs according to conference and/or participants:
1 In the Collaboration Server main menu, select Administration > Tools > Information Collector.
2 Determine the time frame of the desired logs.
3 To filter the logs of a specific conference beginning within this time frame:
a Click Select Conference.
b Select the conference to use for the filter, and click OK.
The time frame you previously selected, is modified to that of the selected conference; for an ongoing
conference, the end time is determined to be the current time.
4 To filter the logs of a specific participant in the selected conference:
a Click Select Participants.
b Select the participant to use for the filter, and click OK.
5 Determine the location in which the filtered logs are stored, by entering it or via Browse.
6 Click Collect Information to generate the appropriate log files.
Error Handling
Should a failure occur at one of the Soft Blades - from best case scenario of the Collaboration Server
application level, down to the worst case scenario of the Soft Blade machine termination - all retrievable log
files are sent to the Main MCU, accompanied by a notification listing the files which could not be retrieved.
Modular MCU Upgrade Process
The modular MCU and its soft blades can be upgraded together with one upgrade software (*.bin for RMX
1800/2000/4000, *.upg for Virtual Edition) that also being used for non-modular MCU upgrade, all soft
blades will be upgraded automatically during the modular MCU reboot.
You can upgrade modular MCU in the same way of upgrading non-modular MCU, the only difference is that
upgrading modular-MCU may take extra 1 or 2 minutes. and you can monitor the soft blades upgrade status
on the MMCU System Monitor pane.
Polycom, Inc.
Appendix - Modular MCU
370