Presence Services alarms

Last Updated : May 21, 2019 |
Prolog information
Metadata
Keywords:
Presence Services alarms can be viewed by using any of the following options:
  • Open an SSH session to Avaya Breeze® platform Management Module IP address, navigate to the event.log file located at /var/log/Avaya/services.
  • On the System Manager web console, navigate to Services Events Alarms.
  • On the System Manager web console, navigate to Services Events Logs Log Viewer.

Presence Services alarms

The following alarms are supported on Presence Services:
Event ID
Alarm name
Severity
Description
CluMon_01
Cluster Monitor
Critical
Raised when the Presence Services node within a cluster has failed.
PresServ_CLR_CluMon_01
Clear Cluster Monitor
Critical
Raised when the Presence Services node is running and clears the PresServ_CluMon_01 alarm.
IMArc_01
Message Archive upload failed
Major
Raised when an attempt to SFTP archived messages to a remote site has failed.
CLR_IMArc_01
Clear Message Archive upload failed
Major
Raised when the Presence Services node is running and clears the IMArc_01 alarm.
IMArc_02
Message Archiving Disabled
Critical
Raised when Message Archiving is disabled due to too many consecutive SFTP failures.
CLR_IMArc_02
Clear Message Archiving disabled
Critical
Raised when the Presence Services node is running and clears the IMArc_02 alarm.
GR_01
Lost Connectivity to remote Geographic Redundancy cluster
Critical
Raised when Presence Services loses connectivity to the remote Geographic Redundancy cluster.
CLR_GR_01
Clear Lost Connectivity to remote Geographic Redundancy cluster
Critical
Raised when Presence Services establishes connectivity to the remote Geographic Redundancy cluster and clears the GR_01 alarm.
GR_02
Presence Services Geographic Redundancy misconfigured
Major
Raised when Presence Services Geographic Redundancy is misconfigured.
CLR_GR_02
Clear Presence Services Geographic Redundancy misconfigured
Major
Raised when Presence Services Geographic Redundancy is configured correctly and clears the GR_02 alarm.
HLTH_01
Cluster Health Check failed
Major
Raised when a Presence Services cluster-level health check has failed.
CLR_HLTH_01
Clear Cluster Health Check failed
Major
Raised when a Presence Services cluster-level health check has passed and clears the HLTL_01 alarm.
SMTPArc_01
SMTP archiving upload failed
Major
Raised when SMTP upload to the SMTP Server is failed.
CLR_SMTPArc_01
Clear SMTP archiving upload failed
Major
Raised when Presence Services clear the SMTPArc_01 alarm.
SMTPArc_02
SMTP archiving Service Disabled — Run time failure
Critical
Raised when SMTP archiving is disabled due to the fact that multiple consecutive attempts of uploading archived messages to the SMTP server are failed.
CLR_SMTPArc_02
Clear SMTP archiving service disabled
Critical
Raised when Presence Services clear the SMTPArc_02 alarm.
SMTPArc_03
SMTP archiving Service Disabled — Configuration failure
Critical
Raised when Presence Services cannot enable the SMTP archiving service due to incorrect configuration.
CLR_SMTPArc_03
Clear SMTP archiving Service Disabled
Critical
Raised when Presence Services clear the SMTPArc_03 alarm.

Causes and resolutions of the alarms

Alarm name
Causes
Resolutions
Cluster Monitor
  • Network outage
  • Hardware failure
  • Software failure
  1. Check the CluMon_01 log to identify the failed server.
  2. On the System Manager web console, navigate to ElementsAvaya Breeze® Server Administration.
  3. Select the failed server.
  4. From the Shutdown System menu, select Reboot.
  5. If this fails, open an SSH session to the Avaya Breeze® platform Management Module IP address as root user.
  6. Run the reboot command.
  7. If this fails, verify the Enet connectivity to the server by pinging the server from a remote server.
  8. If this fails, troubleshoot the server hardware.
Message Archive upload failed
Messaging Archiving attributes have been misconfigured.
For example, an invalid Remote Server Address has been entered.
Reconfigure the Message Archiving attributes on System Manager at ElementsAvaya Breeze® Configuration Attributes.
Message Archive upload failed
EXPORT_FAILED: Presence Services failed to store the archived messages in XML format.
Raise a ticket.
Message Archive upload failed
ZIP_FAILED: Presence Services failed to create a ZIP file.
Raise a ticket.
Message Archive upload failed
UPLOAD_FAILED: Remote server is reachable, but SFTP to the remote server failed for an unknown reason.
Troubleshoot the remote server to ensure that the remote server successfully accept files through SFTP.
Message Archive upload failed
EXCEPTION or UNKNOWN: Internal Presence Services failure.
Raise a ticket.
Message Archiving Disabled
Messaging Archiving is enabled and configured through the service attributes at ElementsAvaya Breeze® Configuration Attributes Group. This alarm is raised when the Message Archive upload failed alarm is continually raised for the duration specified in the Message Archiving Remote Upload Failures Threshold attribute.
Clear the condition that has caused the Message Archive upload failed alarm, that is, IMArc_01 to be raised. Once IMArc_01 is cleared, the system will clear the IMArc_02 alarm.
Lost Connectivity to remote Geographic Redundancy cluster
  • Network outage
  • Hardware failure
  • Software failure
In the following example:
  • Clusters A and B are configured on System Manager at Elements Avaya Breeze®Cluster Administration, each with multiple Avaya Breeze® platform servers assigned.
  • Managed Elements A and B are configured at Services Inventory Managed Element of type Presence Services on Avaya Breeze® with GEO Redundant Avaya Breeze Cluster as cluster B and A.
  • Geographic Redundancy works correctly, then cluster A detects loss of connectivity to cluster B.
Cluster A raises a Lost Connectivity to Geographic Redundancy cluster alarm, which includes fields:
  • Host Name: Short host name of one server in cluster A.
  • Source IP Address: IP address of same server as earlier.
  • Description: Lost connectivity to Geographic Redundancy cluster B.
To clear this alarm:
  1. Restart Presence Services on cluster B. See Restarting Presence Services.
  2. If alarm does not clear within 2-15 minutes, verify Enet connectivity between clusters by opening an SSH connection to one server in cluster A and pinging the Avaya Breeze® platform Security Module IP address of a server in cluster B, and vice versa. If this fails, troubleshoot the network.
  3. If no Enet connectivity issues detected, troubleshoot the hardware of servers in cluster B.
Presence Services Geographic Redundancy misconfigured
  • Geographic Redundancy is misconfigured.
  • Geographic Redundancy cluster restart is pending after configuration.
  • Primary and geo-redundant clusters are configured with the same data center value.
In the following example:
Clusters A and B are configured at Elements Avaya Breeze®Cluster Administration.
To clear this alarm:
  1. On the System Manager web console, navigate to Services Inventory Manage Elements.
  2. On the Manage Elements tab, select the managed element of type Presence Services on Avaya Breeze® with Primary Avaya Breeze Cluster field as cluster A, and then click Edit to edit the managed element.
  3. On the Manage Elements tab, do the following:
    1. In the Data Center field, select the data center that is configured to host cluster B.
    2. In the GEO Redundant Avaya Breeze Cluster field, select B.
    3. Click Commit.
  4. On the Manage Elements tab, select the managed element of type Presence Services on Avaya Breeze® with Primary Avaya Breeze Cluster field as cluster B, and then click Edit to edit the managed element.
  5. On the Manage Elements tab, do the following:
    1. In the Data Center field, select the data center that is configured to host cluster A.
    2. In the GEO Redundant Avaya Breeze Cluster field, select A.
    3. Click Commit.
    Note:
    Ensure that the data centers that host cluster A and cluster B are different.
    For more information about specifying a data center for the Presence Services cluster, see Administering geographic-redundant Avaya Breeze platform cluster to a managed element.
  6. Restart Presence Services for both the clusters. For more information, see Restarting Presence Services.
SMTP archiving upload failed
  • Network outage.
  • SMTP server is offline.
  • Troubleshoot the network connectivity to the SMTP server.
  • Contact the SMTP server administrator to resolve the server offline issue.
SMTP archiving Service Disabled — Run time failure
The SMTP Archiving attribute is enabled, but the SMTP Archiving failure occurs after the SMTP Upload Failures Threshold is reached.
Clear the condition that causes the SMTP archiving upload failed: SMTPArc_01 being raised alarm. With the SMTPArc_01 alarm is cleared, the system will also clear this SMTPArc_02 alarm.
SMTP archiving Service Disabled — Configuration failure
  • SMTP Archiving Service attributes were incorrectly configured.
  • At the time of configuration, the SMTP server is either offline or not reachable.
  • Reconfigure the SMTP Archiving Service attributes on System Manager at ElementsAvaya Breeze®ConfigurationAttributes.
  • Ensure that the SMTP server is operating and that the data path from the Presence Services server to the SMTP server is good.
Cluster Health Check failed
See Cluster Health Check failed alarms section.
Related links