Polycom RMX 1500 Administrator's Manual page 655

Table B-1 Alarms (Continued)
Alarm Code
Security mode failed. Certificate not yet
valid.
Security mode failed. Error in certificate
file.
Single clock source
SIP registrations limit reached
SIP TLS: Certificate has expired
SIP TLS: Certificate is about to expire
SIP TLS: Certificate subject name is not
valid or DNS failed to resolve this name
SIP TLS: Failed to load or verify certificate
files
SIP TLS: Registration handshake failure
SIP TLS: Registration server not
responding
SIP TLS: Registration transport error
Smart Report found errors on hard disk
Polycom, Inc.
Alarm Description
No Backup clock could be established as only one span is connected to the
system or, there is a synchronization failure with another span. This alarm can
be cancelled by adding the appropriate flag is the system configuration.
SIP registrations limit reached.
The current TLS certificate files have expired and must be replaced with new
files.
The current TLS certificate files will expire shortly and will have to be replaced
to ensure the communication with the OCS.
This alarm is displayed if the name of the RMX in the certificate file is different
from the FQDN name defined in the OCS.
This alarm indicates that the certificate files required for SIP TLS could not be
loaded to the RMX. Possible causes are:
•
Incorrect certificate file name. Only files with the following names can be
loaded to the system: rootCA.pem, pkey.pem, cert.pem and
certPassword.txt
• Wrong certificate file type. Only files of the following types can be loaded to
the system: rootCA.pem, pkey.pem and cert.pem and certPassword.txt
• The contents of the certificate file does not match the system parameters
This alarm indicates a mismatch between the security protocols of the OCS
and the RMX, preventing the Registration of the RMX to the OCS.
This alarm is displayed when the RMX does not receive a response from the
OCS to the registration request in the expected time frame. Possible causes
are:
•
The RMX FQDN name is not defined in the OCS pool, or is defined
incorrectly.
•
The time frame for the expected response was too short and it will be
updated with the next data refresh. The alarm may be cleared
automatically the next time the data is refreshed.
•
The RMX FQDN name is not defined in the DNS server. Ping the DNS
using the RMX FQDN name to ensure that the RMX is correctly registered
to the DNS.
This alarm indicates that the communication with the SIP server cannot be
established. Possible causes are:
•
Incorrect IP address of the SIP server
•
The SIP server listening port is other than the one defined in the system
• The OCS services are stopped
Smart Report found errors on hard disk.
Appendix B-Alarms and Faults
B-9