19.08.2013 Views

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Appendix B-Alarms and Faults<br />

Table B-1 Alarms (Continued)<br />

Alarm Code Alarm Description<br />

Backup of CDR files is required If the ENABLE_CYCLIC_FILE_SYSTEM_ALARMS is<br />

set to YES (default setting when JITC_MODE System<br />

Flag is set to YES) and a Cyclic File reaches a file<br />

retention time or file storage capacity limit, the user is<br />

alerted that CDR files need to be backed up.<br />

Backup of log files is required If the ENABLE_CYCLIC_FILE_SYSTEM_ALARMS is<br />

set to YES (default setting when JITC_MODE System<br />

Flag is set to YES) and a Cyclic File reaches a file<br />

retention time or file storage capacity limit, the user is<br />

alerted that log files need to be backed up.<br />

Bios version is not compatible with<br />

Enhanced Security Mode.<br />

Card failed to switch to Enhanced<br />

Security Mode<br />

B-2<br />

The current BIOS version is not compatible with<br />

Enhanced Security Mode (JITC_MODE=YES).<br />

Card failure occured when the system was set to<br />

Enhance Security Mode (JITC_MODE=YES).<br />

Card failure Possible reasons for the card failure:<br />

• Resetting Card<br />

• Resetting component<br />

• Unknown shelf error<br />

• Unknown card error<br />

Card not found This occurs when: the system does not receive an<br />

indication about the card (since it does not exist…)<br />

usually when the card was removed from the MCU and<br />

the system did not have a chance to recalculate it<br />

resources.<br />

Card not responding Possible reasons for the card not responding:<br />

• No connection with MPM card.<br />

• No connection with the Switch.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!