CUCM Change Notification Alerts#
Overview#
The Cisco Unified Communications Manager (CUCM) change notification (CNF) feature is enabled to display alerts. There is no need to configure CNF alerts manually in Automate - admin users receive alerts when the collector process is in an error state.
Administrators can view and delete alerts at the hierarchy they log in at, and at lower hierarchies. For example, Provider, Reseller, and Customer administrators can view alerts raised at the Customer level (sys.hcs.provider.reseller.customer), but a Site admin cannot view such alerts.
When a CNF alert is raised, you’re notified of the alert via the toolbar Messages icon in the Admin Portal. Click the Messages or Notifications toolbar button to view the alerts, or go to (default menus) Administration Tools > Alerts.
Properties of CNF Alerts#
Change notification (CNF) alerts have the following properties:
ID |
A generated unique identifier of the target device of the collector. For CUCM, the ID displays the host name, port, and hierarchy. |
Code |
An error or warning code associated with the alert. |
Category |
The alert category - Device Change Notification Collector |
Severity |
VOSS Automate displays severity codes and messages as follows (“{}” indicate device or number placeholders in the messages). Each alert has some properties, for example, severity (Error, Warning or Info), the number of times that the same alert has been raised, and the time stamp of the last alert instance. |
Message |
Displays error message description and the statement to fix the error. |
Count |
Displays the number of times the alert has occurred for a specific device. |
Latest Alert |
The last time this alert occurred. |
Note
Administrators can filter alerts by any of the alert fields.
CNF Error Scenarios#
VOSS Automate displays change notification (CNF) alerts for the following error scenarios:
Warning:
45000: Unprocessed changes at 75% of limit for device {}. Please configure and run the necessary data syncs.
Error:
40000: Device change notifications are not supported for device {}.
40001: Device change notification data for device {} has been lost. Tracking data has been repaired and collector process will continue. Some changes may have been lost, please run a full sync on the device.
40002: Device change notification tracking data for device {} has become corrupted. Tracking data has been repaired and collector process will continue. Some changes may have been lost, please run a full sync on the device.
40003: Device change notification tracking DB write for device {} failed. The collector process will continue to attempt DB writes. Please investigate the database write failure.
40004: Device change notification data DB write for device {} failed. The collector process will continue to attempt DB writes. Please investigate the database write failure.
40005: Unable to repair device change notification tracking data for device {}.
40006: Too many unprocessed changes recorded for device {}. No new changes will be recorded until at least {} changes are processed. Please configure and run the necessary data syncs.
40008: Could not update pending changes data for device {}. {}.
The administrator reads, inspects, acts on (for example, run a full sync on the device), and then manages alerts of the CNF collection service. The administrator can delete the alert from the list only when the issue that raised the alert has been resolved.
Note
If the Administrators forget to remove the CNF alert after resolving it, the alert will still be shown when they log in to VOSS Automate. We strongly recommend removing the alert after resolving it.