Viewing alarms

tls_certificate_missing_management

tls_certificate_missing

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_not_supported

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 (see Enhanced vMotion Compatibility (EVC) for more information).

eventsink_maximum_backoff

An event cannot be delivered to an event sink, and the system has reached its retry timeout limit.

See Troubleshooting event sink failures.

eventsink_maximum_posts

See Troubleshooting event sink failures.

azure_key_vault_certificate_expired

ntp_not_synchronised

A node has failed to synchronize with the configured NTP servers.

A virtual machine on VMware has been migrated.

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.

See https://kb.vmware.com/s/article/2108828 for VMware migration issues.

configuration_sync_failure

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.

scheduling_connection_failure

autobackup_upload_failed

ldap_sync_failure

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).

azure_teamsconnector_scheduledscaling_failure

This is raised if Pexip Infinity requests more instances than Azure will allow (above the limit set by the instance count (slider) configuration in the Azure portal for the Virtual machine scale set in your Teams Connector resource group).

Note that Azure will still create as many instances as it can up to the maximum.

You should review your maximum instances setting (slider) in Azure and your scheduled scaling policies to ensure you do not request scaling up beyond your maximum limit.

See Scheduling scaling and managing Teams Connector capacity for more information.

azure_teamsconnector_scheduledscaling_notenoughinstances_failure

This is raised if the number of required instances (Minimum number of instances plus the policy's Number of instances to add) are not running at the policy's activation date/time.

This can occur if Azure failed to start the instances, running instances have failed, or there is some other problem with Azure's scaling/provisioning processes.

It can also occur if the Azure Event Hub connection string field is not configured correctly.

This alarm can also be raised temporarily if the Minimum number of instances is increased. It will last for a few minutes until the new instances are up and running. This is expected behavior and can occur with or without any scheduled scaling policies.

This requires investigation of the VM scale set in the Azure portal as to the cause of failure, and manual intervention to resolve the issue. Problem scenarios could include:

• The instance may be running but not sending heartbeat events.
• The instance failed to start.

In most cases the resolution is to restart the instance via the Azure portal.

Also check that the Azure Event Hub connection string field in Pexip Infinity is configured correctly (see Configuring your Teams Connector (addresses, Event Hub, minimum capacity)).

azure_teamsconnector_scheduledscaling_endpoint_not_found

This is raised if "Enable Azure Event Hub" is enabled but Pexip Infinity cannot connect to the Azure Event Hub queue for scheduled scaling.

The most likely reason for this is that you have not created the Teams Connector API app.

Disabling the "Enable Azure Event Hub" setting will lower the alarm.

However, to use scheduled scaling you must follow the instructions to create the Teams Connector API app and redeploy your Teams Connector.

You need to perform a full redeploy of your platform.

You should also notify your security administrator if the source of the event is unknown.

licenses_exhausted

• Wait until one or more of the existing conferences have finished and the licenses have been returned to the pool.
• Contact your Pexip authorized support representative to purchase more licenses.

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.

licenses_expiring

capacity_exhausted

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.

• Deploy more Conferencing Nodes in either the proxying or transcoding location as appropriate.
• Move existing Conferencing Nodes onto more powerful servers.
• Allocate more virtual CPUs for Conferencing Nodes on existing servers (if there are sufficient CPU cores). Note that the Conferencing Node will have to be rebooted for this to take effect.
• Configure each location with a primary and secondary overflow location.
• If a call is received in a location that contains Proxying Edge Nodes, that location must be configured with a Transcoding location that contains your Transcoding Conferencing Nodes.

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_exhausted

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.

trustedca_expiring

tls_certificate_expiring

tls_certificate_chains

syslog_inaccessible

• Check your network connectivity.
• Check that the syslog server is running.

connectivity_lost

Communication to a Pexip Infinity node has been lost.

More information

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, these alarms are raised (for each combination of affected nodes) if all of the nodes in the proxying node location's Transcoding location (and any configured media overflow locations) are in maintenance mode, or if there are no transcoding nodes in those locations.

irregular_pulse

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_deprecated

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.

io_high_latency

• Avoid having multiple VMs using the same physical hard drive.
• Check the hard drive for failures.

possible_voip_scanner_ips_blocked

service_access_quarantined

scheduled_maintenance_event_freeze

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

scheduled_maintenance_event_preempt

azure_key_vault_certificate_expiring

gms_gateway_token_expiring

mjx_google_gatherer_failure

mjx_exchange_gatherer_failure

mjx_endpoint_configurator_failure

mjx_meeting_processor_failure

mjx_poly_failure

Ensure thatEnable support for Pexip Infinity Connect clients and Client API is enabled.

Ensure that the configuration for endpoint on Pexip Infinity and on the endpoint itself is correct, in particular that the username and password configured on both match.

Ensure that the endpoint is showing as registered to the calendaring service.

Restart the endpoint.

mjx_webex_failure

One-Touch Join has received an error from Webex when attempting to send the request. Examples of these messages include:

• Cloud Calendar is configured
• Device has not registered as an XAPI provider
• Webex Request Error
• No response received from request
• The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request

The resolution will depend on the issue, for example:

• Disable the cloud calendar.
• Check that the Device ID is correct.
• Confirm that the correct ports are open, and that Pexip Infinity can reach Webex.
• Confirm that the endpoint is switched on and connected to the internet, and that Webex can reach it.

mjx_graph_gatherer_failure

A successful connection to the Graph API could not be made for any room. Possible causes:

• A network connection issue between the Conferencing Node and Graph API (https://graph.microsoft.com).
• The room email addresses (for the OTJ Endpoints used by this O365 Graph Integration) are incorrect.
• The application permission (the Application set up in Azure for OAuth) has not been granted for the rooms.

• Check network connectivity.
• Check the email addresses used by the rooms.
• Check the Azure App registration configuration.

There was a problem getting an OAuth access token that could be used to connect to the Graph API.

Possible causes:

• There is a network connection issue between the Conferencing Node and the token endpoint URI (which is https://login.microsoftonline.com by default).
• The OAuth Client ID, Client secret, or OAuth 2.0 token endpoint URL are not entered correctly in the O365 Graph Integration configuration on the Pexip Infinity Management Node.
• The Azure application is not set up correctly (for example, the correct API permissions were not added, or admin consent was not provided).

• Check network connectivity.
• Check the O365 Graph integration configuration.
• Check the Azure App registration configuration.

• Check that the room email address is correct.
• Check the application permission is configured correctly to allow OTJ to read this room's calendar.