cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1019
Views
0
Helpful
2
Replies
Highlighted
Advocate

Automatic sync in Cisco Prime collaboration

Hello,

How do I setup CPC to do an automatic sync from the processors? The documentation doesnt seem to help.

Thanks!

Please rate useful posts.
Everyone's tags (1)
2 REPLIES 2
Highlighted
Advocate

Re: Automatic sync in Cisco Prime collaboration

I am following the steps as outlined below:

Scheduling Synchronization

Provisioning provides a command line script utility that can be used to schedule periodic processor and Domain synchronizations. The synchronization script enables you to regularly schedule a subset of the synchronization operations at different periodic intervals and across multiple time zones. You should use the sync.sh file available in the /opt/cupm/sep/build/bin/ folder.

However under the above mentioned file, the contents are as follows:

#!/bin/sh

#****************************************************

#         Copyright (c) 2006, 2007, 2008, 2009, 2012 Cisco Systems, Inc.    

#         All rights reserved.                      

#****************************************************

source /opt/env.sh

$DEV_DIR/build/bin/dfcapp.sh dfc.ipt.tools.RunSync $*

Not sure what I should be doing here.


Please rate useful posts.

Not sure if you have solved

Not sure if you have solved this yet or not but this may help

Scheduling Synchronization

Provisioning provides a command line script utility that can be used to schedule periodic processor and Domain synchronizations. The synchronization script enables you to regularly schedule a subset of the synchronization operations at different periodic intervals and across multiple time zones. The sync.sh file is available at /opt/cupm/sep/build/bin/ folder.

To schedule synchronization:


    Step 1   Login to the Provisioning server as root using SSH.
    Step 2  Enter crontab -e to edit a copy of the crontab file in vi editor.
    Step 3  Press the i key to enter insert mode.
    Step 4  To run synchronization at regular intervals, enter the following: minute hour day-of-the-month month day-of-week command-to-be-executed
    where:
    • Minute-Valid range is from 0 to 59.
    • Hour-Valid range is from 0 to 23.
    • Day of the month-Valid range is from 1 to 31.
    • Month-Valid range is from 1 to 12.
    • Day of the week-Valid range is from 0 to 6 (Sunday = 0).

    For example, to run Call Processor synchronization at 3:24 pm every day, enter the following:

    24 15 * * * /opt/cupm/sep/build/bin/sync.sh callprocessor

    To run Message Processor synchronization at 8:24 pm every day, you would enter the following command:

    24 20 * * * /opt/cupm/sep/build/bin/sync.sh messageprocessor

    See Command Line Script Utility Options for information on Command Line Script utility options.

    Note    Run man 5 crontab for information on other cron commands.
    Step 5  Press ESC key to exit insert mode, and then press : to enter the command line.
    Step 6  Enter wq to write and quit the editor.
    Step 7  Enter crontab -l to see if the file is saved.

    Command Line Script Utility Options

    The command line script utility options are as follows:

    Mass Sync Usage: ./sync.sh [callprocessor | messageprocessor | presenceprocessor | activedirectory | domain | all] [<option>]

    Mass Synchronization invokes synchronization operations for all objects of the specified class. Both infrastructure and subscriber synchronizations run for each processor. The order of the synchronization is as follows: call processor, unified message processor, presence processor, and then domain.

    Granular Sync Usage: ./sync.sh [-g <filename>] [<option>]

    Granular Synchronization invokes synchronization operations that are specified in a formatted file, where
    • <filename>—is a text file that has lines of the appropriate format: <object class>.<object name>: <sync type> that is,
      • cp.Test-UCM: infra
      • mp.all: sub
      • pp.all: both—equivalent to the [presenceprocessor] mass sync
      • ad.all:—ActiveDirectory mass sync
      • domain.Test-Dom:
    • <option>—(Optional field) the following are available as options:
      • test—Allows a script to run without performing any syncs, but list the processors and Domains that will be synchronized.
      • abortonfail—Instructs the script to quit after a synchronization failure. If this parameter is not specified, the sync script will continue on success or failure.
      • forcedomainsync—Allows the domain sync to be performed even if one of the devices in the domain had a failed sync. If this parameter is not specified, then the domain sync will not proceed if there are device sync errors.
      • parallel—runs the device syncs in parallel
      • help—Displays usage information.

    For example, if you want to run granular synchronization at 1:15 pm every Saturday, enter the following command:

    15 13 * * 6 /opt/cupm/sep/build/bin/sync.sh -g granularsyncfilename

    CreatePlease to create content