Unified CM Change Notification Feature Alerts¶
The Unified CM Change Notification Feature (CNF) is enabled to display alerts. You don’t have to configure the change notification feature alerts manually in the VOSS-4-UC. The administrator gets the alerts when something goes wrong with the collector process.
The administrators can view the alerts at the hierarchy level they log in and all the levels below that hierarchy. For example, if an alert is raised at the customer level (sys.hcs.provider.reseller.c1), then the provider, reseller, and customer administrators can see that alert but not site administrator. A Site administrator doesn’t have access to view the alert. All the administrators have read and delete permissions to the alerts.
When a change notification feature alert is raised, the Notifications indicator on the VOSS-4-UC Admin GUI shows the alert. Clicking the Notifications button shows a pop-up and a message that alerts have been raised. Clicking on the message, the users are navigated to the list of alert messages under Administration Tools > Alerts.
CNF alerts have the following distinct properties:
- ID: A generated identifier of the target device of the collector For Unified CM, the ID shows the host name, port, and hierarchy
- Code: An error or warning code associated with the alert
- Alert category: The category of the alert - Device Change Notification Collector
- Severity: VOSS-4-UC 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: Displays the last time this alert occurred.
Note
Administrators can also filter alerts by any of the alert fields.
VOSS-4-UC displays change notification feature 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 Change Notification 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 change notification feature alert after resolving it, the alert will still be shown when they log in to VOSS-4-UC. We strongly recommend removing the alert after resolving it.