cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1082
Views
5
Helpful
4
Replies

Best Practices. Schedule Synchronization - Prime Collaboration Provisioning

Romi Clemente
Level 1
Level 1

Hi all,

I'm currently working with PCP 11.5; and I would like to Cisco Prime do an auto sync every considered time.

After looked for information about How to schedule Synchronization for Infrastructure, Users and Domains. I know there is a new option to schedule the Synchronizations:

But, I would like to be sure about the best practices to do it.

My question is...If there is any risk to apply the mass sync (for all sync types) or It would be better create a separate schedules for each one of them?

Thanks in advance.

1 Accepted Solution

Accepted Solutions

Anthony Gerbic
Cisco Employee
Cisco Employee

Romi,

The product is designed to allow any configuration to run. You need to decide why you want to do a sync and that will determine how you set this up.

If you have CUCM revs lower than 10.0, you will need to sync the lower rev CUCMs if you make any changes on the CUCM related to users, user services or infrastructure objects PCP uses, such as CSS, translation patterns, device pools, or similar. CUCM has no way to alert PCP that changes have been made. If all actions are done from PCP then you may consider a weekly or monthly sync to be sure nothing is missed.  If you make changes in these areas on CUCM then you should consider nightly syncs. This advice is the same for any rev of CUC. The point of syncing is to pick up changes made to the UC apps done on their native interfaces.

In cases where you are using 10.0 and later CUCMs, there is a change notification service that runs between CUCM and PCP that automatically takes care of syncing change. It runs periodically, and keeps the products in sync if you make changes on CUCM or if you are using the CUCM self provisioned endpoint service to attach endpoints or CUCM self-care.  It is a good practice to do a weekly or monthly sync in case something is missed.

It is not a bad idea to do a sync to CUCM occasionally.

The product has always been able to do mass syncs. The problem with mass syncs is that it generally will take a long time to run all the syncs in large networks and during that time you cannot do any provisioning.  The best practice is to setup only the syncs you need and only run them as often as you need.  The provisioning product has been getting many updates in UC app support this year so you have less reason to use the UC app native interfaces.

View solution in original post

4 Replies 4

Anthony Gerbic
Cisco Employee
Cisco Employee

Romi,

The product is designed to allow any configuration to run. You need to decide why you want to do a sync and that will determine how you set this up.

If you have CUCM revs lower than 10.0, you will need to sync the lower rev CUCMs if you make any changes on the CUCM related to users, user services or infrastructure objects PCP uses, such as CSS, translation patterns, device pools, or similar. CUCM has no way to alert PCP that changes have been made. If all actions are done from PCP then you may consider a weekly or monthly sync to be sure nothing is missed.  If you make changes in these areas on CUCM then you should consider nightly syncs. This advice is the same for any rev of CUC. The point of syncing is to pick up changes made to the UC apps done on their native interfaces.

In cases where you are using 10.0 and later CUCMs, there is a change notification service that runs between CUCM and PCP that automatically takes care of syncing change. It runs periodically, and keeps the products in sync if you make changes on CUCM or if you are using the CUCM self provisioned endpoint service to attach endpoints or CUCM self-care.  It is a good practice to do a weekly or monthly sync in case something is missed.

It is not a bad idea to do a sync to CUCM occasionally.

The product has always been able to do mass syncs. The problem with mass syncs is that it generally will take a long time to run all the syncs in large networks and during that time you cannot do any provisioning.  The best practice is to setup only the syncs you need and only run them as often as you need.  The provisioning product has been getting many updates in UC app support this year so you have less reason to use the UC app native interfaces.

Anthony,

Many thanks for your time to reply.

Just another question....Do you know which is the service that runs between the CUCM and PCP that automatically takes care of syncing changes?. I would like to be sure that It is currently running.

Thanks again, Really helpful your answer. :)

Romi CM

Change notification. There is a service that monitors the CUCM db for changes. If tsmith's info or services change, it will be noted in a buffer that tsmith must be resynced. Same if the translation patterns change. PCP will look at the change notification buffer ever few minutes. In this case tsmith's record will be synced with PCP and then the translation patterns will be pulled in. That is essentially what it is doing and keeps the products synchronized.

Thanks for your information. :)