Usage Metering alerts

Last Updated : Aug 01, 2023 |
Prolog information
Metadata
Keywords:
The following table provides the list of Usage Metering alerts along with the possible reasons and solutions:
Alert title
Possible reasons why Usage Metering generated the alert 1
Solution
UM Alert 1: Internal Error
N/A
Contact Avaya Support.
UM Alert 2: Uncaught exception — restart required
N/A
Restart Usage Metering by using the sudo um-restart command after one minute.
UM Alert 3: Service suspended until updated License Terms are accepted
N/A
Log on to the Usage Metering web interface and accept the terms that are displayed.
UM Alert 4: Updated License Terms declined — software uninstalled
N/A
Restore Usage Metering from backup.
For more information, see Usage Metering restore.
UM Alert 9: Email send failed
  • Invalid SMTP server configuration.
  • Network outage.
  • SMTP server outage.
Check the SMTP configuration and the SMTP server.
For more information, see Configuring SMTP mail server to send email notifications
UM Alert 10: Snmp trap send failed
  • Invalid SNMP server configuration.
  • Network outage.
  • SNMP server outage.
Check the SNMP trap server configuration and the SNMP server.
For more information, see Configuring alerts
UM Alert 14: User {EMAIL} locked out
The number of permissible consecutive failed login attempts by user is reached.
Unlock the user account.
For more information, see Enabling or disabling a user account.
UM Alert 30: Failed to connect to data source
  • Invalid data source configuration.
  • Network outage.
  • Metered solution element server outage.
Check the data source connection address and credentials.
For more information, see:
UM Alert 32: Failed to upload collected data
  • Network outage.
  • Man-in-the-middle attacking web proxy is configured, but the web proxy’s CA certificate is not installed.
UM Alert 34: Primary data source failed — data collection succeeded from Secondary data source
Primary credentials failed, but Usage Metering was able to collect data from the Secondary system.
Rectify the Primary credentials for the data source.
UM Alert 35: Deleting local collection folder structure failed
The cleanup task failed to delete the empty folders in the local upload folder structure.
Examine the log files to view the reason for the deletion failure.
For more information, see Viewing the recent logs and downloading the log files.
UM Alert 37: Recollected data for meter
The data is recollected for a meter for which meter collection has failed in the past.
This is an informative alert.
UM Alert 100: Disk space is below threshold
N/A
Free up your disk space, or use a server that has the required disk space to run the Usage Metering software.
UM Alert 101: A certificate is about to expire
N/A
Install a new SSL certificate.
UM Alert 102: A certificate has expired
N/A
Install a new SSL certificate.
UM Alert 104: Auto-update of avaya-usage-metering rpm failed
The upgrade is incompatible with the previous release.
Do the following:
  1. Stop the current Usage Metering instance.
  2. Install a new Usage Metering Collector on another server.
  3. Install the avaya-usage-metering rpm.
  4. Restore from backup.
UM Alert 105: Unable to check for update of Usage Metering
Man-in-the-middle attacking web proxy is configured, but the web proxy’s CA certificate is not installed.
Install the web proxy’s CA certificate.
For more information, see Usage Metering Collector cannot recognize a web proxy CA certificate.
UM Alert 106: Avaya Usage Metering update applied
N/A
This is an informative alert.
UM Alert 109: Avaya Usage Metering server started
N/A
This is an informative alert.
UM Alert 115: New orderable service provisioned and available to configure
New orderable service is added in the current offer.
This is an informative alert.
UM Alert 600: WebLM Operation Failed(<operationName>) for WebLM <WebLMName>
  • Failed to register the Usage Metering Collector with WebLM.
  • Failed to unregister the Usage Metering Collector From WebLM.
  • Failed to retrieve the HostId From WebLM.
  • Failed to install the subscription license file on WebLM.
  • Failed to share list of allowed applications with WebLM.
  • Failed to clear the list of denied applications from WebLM.
UM Alert 601: Subscription License Generation Failed(<operationName>) for WebLM <WebLMName>
  • Subscription license creation request failed.
  • Subscription license retrieval failed.
Usage Metering automatically retries to retrieve the subscription license file within 48 hours of the license generation failure.
However, if the problem persists, contact Avaya Support.
UM Alert 602: Failed to install Subscription license
WebLM sends an error code other than 200 OK.
The system automatically retries to install the subscription license file on the WebLM server within 48 hours of the subscription license installation failure.
You can also re-register Usage Metering Collector to the WebLM server. For more information, see Editing a WebLM server.
However, if the problem persists, contact Avaya Support.
UM Alert 603: State Operation For the System Failed for system <systemName>
  • State retrieval failed.
  • State Change trigger failed.
  • State Change event status retrieval failed.
Contact Avaya Support.
UM Alert 604: Unconfigured applications tried to access the license for WebLM <WebLMName>
An application that is not configured on the Usage Metering Collector tries to acquire the subscription license from the WebLM.
Configure the application on the appropriate Usage Metering Collector and remove the application from this Usage Metering Collector.
UM Alert 605: Collector is not able to reach WebLM for WebLM <WebLMName>
N/A
  • Check if there are any network problems.
  • Ensure that the WebLM server is running.
UM Alert 606: IX Subscription License has been successfully Installed
N/A
This is an informative alert.
UM Alert 990: Test Alert
This is an informative alert.
1 The possible reasons of alert generation are documented in this topic only where the reasons are not obvious in the alert title.
For information about verifying connectivity between Usage Metering Collector and Avaya back-office systems, see Verifying Usage Metering Collector connectivity and operating system parameters.