When there are active alarms on your Pexip Infinity deployment, a flashing blue triangle appears at the top right of each page of the Administrator interface. To view details of the current alarms, click on this icon or go to the page ( ).
- Alarms remain in place for as long as the issue exists. After the issue has been resolved (for example, if a conference ends, therefore freeing up licenses) the associated alarm will automatically disappear from the page.
- Multiple instances of the same type of alarm can be raised. For example if two Conferencing Nodes are not correctly synchronized to an NTP server, you will see an alarm for each node.
- You can select individual alarms and view the associated documentation (this guide) for suggested causes and resolutions.
Thepage shows the details of all historic alarms including the severity level, and the time the alarm was raised and lowered.
An alarm is raised in each of the following situations:
|Alarm||ID||Logged as Alarm =||Level||Cause||Suggested resolutions|
|The Management Node does not have a TLS certificate||20||
|Critical||The Management Node has no associated TLS certificate.||Upload a TLS certificate and associate it with the Management Node.|
|A Conferencing Node does not have a TLS certificate||9||
|Critical||A Conferencing Node has no associated TLS certificate.||
Upload a TLS certificate and associate it with the Conferencing Node.
Alternatively, and if appropriate for your deployment, associate an existing certificate with your Conferencing Node. When doing this, the existing certificate should already contain a SAN (Subject Alternative Name) that matches your Conferencing Node's FQDN.
See Managing a node's TLS server certificate for more information.
|CPU instruction set not supported||10||
A Conferencing Node has gone into maintenance mode because it was deployed on a server with an unsupported processor instruction set (e.g. SSE4.1).
This could also be caused by setting the EVC mode on a VMware cluster to too low a level, such as Westmere
|Deploy the Conferencing Node on a server with AVX or later.|
|Eventsink Reached Maximum Backoff||36||
An event cannot be delivered to an event sink, and the system has reached its retry timeout limit.
|Eventsink Reached Maximum Concurrent POSTs||37||
|Critical||More than the configured Maximum number of background POSTs events (default 1000) are queued for an event sink but have not been sent.|
|NTP not synchronized||11||
|Error||A node has failed to synchronize with the configured NTP servers.||Ensure that NTP is enabled on the Management Node, and that NTP servers are assigned to, and accessible from, each location. See Syncing with NTP servers for more information.|
|Configuration not synchronized||18||
|Error||This alarm is raised if the Conferencing Node status “Last contacted” time has not been updated within the last 2 expected replication intervals (typically no contact within the last 3 minutes).||
In typical deployments, configuration replication is performed approximately once per minute. However, in very large deployments (more than 60 Conferencing Nodes), configuration replication intervals are extended, and it may take longer for configuration changes to be applied to all Conferencing Nodes (the administrator log shows when each node has been updated).
If configuration synchronization fails this may indicate network connectivity or routing issues between the Management Node and the Conferencing Node, which could be due to a malfunction or misconfiguration of devices such as routers or firewalls etc.
Ensure that all of the appropriate Pexip nodes are fully routable to each other in both directions. See General network requirements.
|MS Exchange Connection Failure||22||
|Error||The Management Node cannot connect to the Exchange server.||Check that the details entered in the EWS URL ( ) are correct and the Exchange server is online.|
|Automatic backup upload failed||25||
|Error||The Management Node cannot connect to the FTP server to upload a backup file.||Check that the Upload URL (supported schemes are FTPS and FTP) and the Username and Password credentials of the FTP server are correct ( ) and that the Management Node can reach the FTP server.|
|LDAP sync failed||28||
|Error||An LDAP template synchronization process has failed. This alarm duplicates the information shown for the error listed at .||
See Troubleshooting LDAP server connections for help with resolving LDAP connection issues.
The alarm is lowered when you resync the template (although it will get re-raised if the issue has not been resolved).
|Pexip Private Cloud gateway failure||34||
|Error||There was a problem connecting to the Pexip Private Cloud via the configured gateway ( ).||
|License limit reached||2||
|Warning||A Conferencing Node is unable to accept a call because there are not enough concurrent licenses available on the system at this time. For more information, see Pexip Infinity license installation and usage.||
Note that when a license subsequently becomes available (e.g. because a participant leaves a conference, or because the administrator adds more licenses), the alarm is not cleared immediately; the alarm is cleared after the next participant successfully joins a conference.
|Warning||One or more of your licenses is due to expire within the next 60 days.||Contact your Pexip authorized support representative to renew your licenses.|
|Call capacity limit reached||1||
A call has not been accepted because all Conferencing Nodes that are able to take the media for this call are at capacity. It could be either Proxying Edge Nodes or Transcoding Conferencing Nodes that are out of capacity.
Note: to understand how often this issue is occurring in your deployment, search the Administrator log for "out of proxying resource" or "out of transcoding resource".
This alarm clears either when an existing call is disconnected or the next time a new call is successfully placed.
Note that some types of call consume more resources than other calls. Thus, for example, if you are at full capacity and an audio-only call disconnects, there may still not be sufficient free resource to connect a new HD video call. For further information on capacity and how calls consume resources, see Hardware resource allocation rules.
|Management Node limit reached||5||
|Warning||The Management Node does not have sufficient resources for the current deployment size (number of Conferencing Nodes).||
Increase the amount of RAM and the number of virtual CPUs assigned to the Management Node.
See the recommended hardware requirements in Server design recommendations.
|Trusted CA certificates expiring||6||
|Warning||One or more of your trusted CA certificates is due to expire within the next 30 days, or has already expired.||Obtain and upload an updated certificate for the certificate authority.|
|TLS certificates expiring||7||
|Warning||One or more of your TLS certificates is due to expire within the next 30 days, or has already expired.||Obtain and upload an updated TLS certificate. You may also need to delete the old certificate.|
|Incomplete TLS certificate chains||8||
|Warning||A TLS certificate has an incomplete chain of trust to the root CA certificate.||Obtain and upload the appropriate chain of intermediate CA certificates to the Management Node (the certificate provider normally provides the relevant bundle of intermediate CA certificates).|
|Syslog server inaccessible||4||
|Warning||A syslog server has been configured to use TCP or TLS but either is not responding to contact requests, or the connection has dropped.||
|Connectivity lost between nodes||19||
Communication to a Pexip Infinity node has been lost.
When a connection is lost, Pexip Infinity tries to contact the node every 5 seconds until the connection is re-established. In large deployments with many connectivity failures, it attempts to re-establish connections to a maximum of 10 nodes at a time.
Intermittent short-lived "Connectivity lost between nodes" alarms may be an indication of an unreliable network.
These alarms may be raised for a short period of time — as expected behavior — if a node is placed into maintenance mode and Proxying Edge Nodes need to establish new connectivity paths.
They may occur during initial deployment or an upgrade, and is also expected behavior. They automatically clear as each node is upgraded to the new software version, has restarted and is ready to handle calls.
When restricted routing for Proxying Edge Nodes is enabled, you may see these alarms (and is expected behavior):
|Check network connectivity and routing as for "Configuration not synchronized" above, or in the case of a software upgrade, wait for the upgrade process to complete.|
|Hardware instability detected||21||
|Warning||Pexip Infinity has detected that the underlying VM infrastructure has paused the Pexip virtual machine. This is usually indicative of over-committed hardware, which we do not support. Pexip Infinity is a real time system and requires dedicated access to the underlying CPU and RAM resources of the hardware host.||
Ensure that the Management Node and all Conferencing Nodes have dedicated access to their own RAM and CPU cores.
See the recommended hardware requirements in Server design recommendations.
|CPU instruction set is deprecated||23||
The node is deployed on a server that is not using the AVX or later CPU instruction set (e.g. if it uses SSE4.2).
This alarm is raised when a Conferencing Node restarts and is automatically cleared after 48 hours.
|Deploy the Conferencing Node on a server with AVX or later.|
|Hardware IO (input/output) instability detected||24||
|Warning||Pexip Infinity has recently detected consistent read latency greater than 100ms or write latency greater than 400ms.||
|VOIP scanner resistance has detected excessive incorrect aliases being dialed in a short period||26||
|Warning||Pexip Infinity's VOIP scanner resistance has detected excessive incorrect aliases being dialed in a short period, and has temporarily blocked access attempts from the suspected VOIP scanner IP addresses.||See the administrator log for details of the calls.|
|PIN brute force resistance has detected excessive incorrect PIN entry attempts in a short period||27||
|Warning||Pexip Infinity's PIN brute force resistance has detected excessive incorrect PIN entry attempts in a short period, and has temporarily blocked access attempts to one or more conferencing services.||See the administrator log for details of the calls.|
|Pexip Private Cloud configuration failed||33||
|Warning||A configuration change to a Pexip Smart Scale location could not be applied.||Check that there are no issues communicating with the PPC gateway. Otherwise, contact your Pexip authorized support representative.|
|Scheduled maintenance event (freeze)||39||
|Warning||A scheduled maintenance event in Microsoft Azure has been detected.||
No action is required.
Any Conferencing Node running on the affected VM is automatically placed into maintenance mode until the event completes.
|Scheduled maintenance event (redeploy)||40||
|Scheduled maintenance event (preemption)||41||
The following alarms may be raised in relation to issues with dynamic cloud bursting. See Dynamic bursting to a cloud service for more information about resolving these alarms.
The following alarms may be raised in relation to issues with One-Touch Join:
|Alarm||ID||Logged as Alarm =||Level||Instance||Cause||Suggested resolutions|
|OTJ Google Gatherer Error||29||
|Error||Google Connection Test Failure||The connection test to Google Workspace has failed. This could be because your service account credentials are incorrect.||Check your service account details, specifically the service account email and private key.|
|Google Room Connection Failure||OTJ has been unable to connect to one of the rooms you have specified. This could be because the room is misconfigured within Google Workspace.||Check the steps to set up a new room. Is the room resource email correct? Has it been shared with the service account?|
|OTJ Exchange Gatherer Error||30||
|Error||Exchange Connection Test Error||The connection test to Exchange has failed. This could be because your service account credentials are incorrect.||Check your Exchange service account username and password.|
|Exchange OAuth Error||OTJ is unable to use OAuth to sign into Exchange.||Check your OAuth credentials.|
|Exchange Room Connection Error||OTJ is unable to connect to the room specified in the alarm description. This could be because the room is misconfigured.||Check the room has been correctly set up.|
|OTJ Endpoint Configurator Error||31||
|Error||Endpoint Misconfigured Error||The OTJ endpoint does not have a username and password configured, and there is no default username and password.||Provide a username and password for the OTJ endpoint or for the associated OTJ profile.|
|Endpoint Request Error||OTJ is unable to connect to the endpoint.||Check that the endpoint is configured correctly.|
|Endpoint Non-200 Status Code||The endpoint returns a non-200 status code.||Check the status code that is given in the logs. This is likely a configuration error with the endpoint.|
|OTJ Meeting Processor Failure||32||
|Error||Meeting Processor Rendering Error, Template Error or Runtime Error||The meeting processing rule could not extract a meeting alias.||Check and edit the rule using the test tool.|
|OTJ Poly Endpoint Error||35||
|Error||Poly Endpoint Not Polled||A Poly endpoint that has Raise alarms enabled has not made contact with the OTJ calendaring service within the last 10 minutes.||
Ensure that the endpoint is showing as registered to the calendaring service.Restart the endpoint.
|OTJ Webex Failure||38||
|Error||Webex Endpoint failed with <Webex error message>||
One-Touch Join has received an error from Webex when attempting to send the request. Examples of these messages include:
The resolution will depend on the issue, for example:
|Webex OAuth Error||We are unable to get an access token for your webex integration.||Sign in with the webex service account again.|
|Webex Configuration Error||A webex endpoint is configured but there is no webex integration configured on the OTJ profile.||Make sure you configure a webex integration on the OTJ profile.|