10-29-2008 03:45 AM - edited 03-10-2019 04:09 PM
I have two ACS with configured replication. Manual replication works fine, but when setting up scheduled replication, primary server says "Pre-checks indicate outbound replication not required - cycle completed". Even if new devices were added to the primary server, replication does not take place.
Any thoughts?
Solved! Go to Solution.
10-29-2008 06:48 AM
Please check this bug ,
CSCsd02854 : Automatic replication not triggered after changes in config
components
Symptom: When configured for automatic replication, only changes to Users/Groups/SPC are replicated automatically. Changes to NAS/Admin/NAP/External Databases configuration
components do not trigger replication.
Conditions: This is seen when automatic replication (in intervals or at a specified time)is configured.
Workaround: Initiate manual replication after configuration changes to the affected
components have been made.
http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs
Please ensure that on Secondary ACS server, we have all the Network devices replicated
from the Primary ACS server successfully. If they are not, and we have configured scheduled replication to take place, then we are hitting this bug.
Regards,
~JG
Do rate helpful posts
10-29-2008 06:48 AM
Please check this bug ,
CSCsd02854 : Automatic replication not triggered after changes in config
components
Symptom: When configured for automatic replication, only changes to Users/Groups/SPC are replicated automatically. Changes to NAS/Admin/NAP/External Databases configuration
components do not trigger replication.
Conditions: This is seen when automatic replication (in intervals or at a specified time)is configured.
Workaround: Initiate manual replication after configuration changes to the affected
components have been made.
http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs
Please ensure that on Secondary ACS server, we have all the Network devices replicated
from the Primary ACS server successfully. If they are not, and we have configured scheduled replication to take place, then we are hitting this bug.
Regards,
~JG
Do rate helpful posts
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide