Polycom RealPresence 800s Administrator's Manual page 557

Table B-1 Active Alarms (Continued)
Alarm Code
Gatekeeper failure
GUI System configuration file is invalid
xml file
Hard disk error
Hot Backup: Master-Slave configuration
conflict.
Hot backup: Network issue
Polycom, Inc.
Alarm Description
Possible reasons for the Gatekeeper failure:
•
Failed to register to alternate Gatekeeper.
•
Gatekeeper discovery state.
- Check GK IP address (GUI, ping)
•
Gatekeeper DNS Host name not found.
•
Gatekeeper Registration Timeout.
•
Gatekeeper rejected GRQ due to invalid revision.
•
Gatekeeper rejected GRQ due to resource unavailability.
•
Gatekeeper rejected GRQ due to Terminal Exclusion.
•
Gatekeeper rejected GRQ due to unsupported feature.
•
Gatekeeper rejected GRQ. Reason 18.
•
Gatekeeper rejected RRQ due to Discovery Required.
•
Gatekeeper rejected RRQ due to duplicate alias.
- Check duplicate in aliases or in prefixes
•
Gatekeeper rejected RRQ due to Generic Data.
•
Gatekeeper rejected RRQ due to invalid alias.
•
Gatekeeper rejected RRQ due to invalid call signaling address.
•
Gatekeeper rejected RRQ due to invalid endpoint ID.
•
Gatekeeper rejected RRQ due to invalid RAS address.
•
Gatekeeper rejected RRQ due to invalid revision.
•
Gatekeeper rejected RRQ due to invalid state.
•
Gatekeeper rejected RRQ due to invalid terminal alias.
•
Gatekeeper rejected RRQ due to resource unavailability.
•
Gatekeeper rejected RRQ due to Security Denial.
•
Gatekeeper rejected RRQ due to terminal type.
•
Gatekeeper rejected RRQ due to unsupported Additive Registration.
•
Gatekeeper rejected RRQ due to unsupported feature.
•
Gatekeeper rejected RRQ due to unsupported QOS transport.
•
Gatekeeper rejected RRQ due to unsupported transport.
•
Gatekeeper rejected RRQ. Full registration required.
•
Gatekeeper rejected RRQ. Reason 18.
•
Gatekeeper Unregistration State.
•
Registration succeeded.
Check the Gatekeeper configuration.
The XML format of the system configuration file that contains the user interface
settings is invalid.
Hard disk not responding.
Possible reasons:
• When both the MCUs are configured as Master or as Slave
• The slave Collaboration Server is defined with the same IP as the Master.
Appendix B-Active Alarms
B-5