Update sync operations

Partners can use Cisco UCM’s Change Notification functionality to process update sync operations faster. By default, this feature is disabled, but can be enabled by the partner.

This topic provides guidelines for setting up a sync schedule, and lists associated performance implications. Further details for using Change Notification is provided elsewhere in the Automate documentation. The changes described here are not transactions. For this reason, details don’t display in the transaction log; instead, these display in special logs created for this feature.

These guidelines are derived from concepts related to total processing capacity. The total number of updates processed in a time period is the sum of all updates across the customers selected for update in that time period. In this case, the time period is one hour. In this example, it is assumed that each customer has 1000 UCM-related changes in that hour.

Recommendations provided in the following table indicates that 5 customers can run in parallel (concurrently), and therefore a total of 5,000 changes processed in total. Partners exceeding the recommendation of 5 concurrent customers may notice a performance degradation, and the full set of required changes may not complete within that hour. Alternatively, if the number of changes for any customer is significantly higher than 1,000, or if the total number of changes is significantly greater than 5,000, the supported concurrency number may be less than 5.

If some of the planned changes do not complete within the hour noted in the table, those changes are completed the next time that particular customer is scheduled for a sync.

If the number of changes for any customer is so large that the changes continually exceed those that can be processed in one hour, it will eventually result in a full sync. For such customers, it is recommended to schedule within an hour where less than 5 customers execute concurrently.

Configuration	Recommendation
Maximum number of concurrent CNF sync	5
Maximum number of changes processed per CNF sync	1,000
CNF sync schedule frequency	Once per hour per customer - This is subject to the staggering of CNF sync across customers.
Staggering of CNF syncs across customers	Factor of maximum changes processed and maximum number of concurrent CNF syncs.
CNF collector frequency	Initial recommendation is 15 minutes.
When is full sync required?	Weekends only or when there are CNF alerts prompting for full sync.

Note

It is recommended that you disable the functionality if you experience significant performance degradation. Contact your support representative if you have any performance concerns.