Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

ACS Replication of Shared Profile Components

We're running ACS 3.2(3)Build 11. We have setup CiscoWorks LMS 2.5 to authenticate via ACS. Also, user roles were created and are defined in ACS.

However, when we perform replication to our backup ACS server, we don't see these components replicated.

I don't see anywhere in the documentation where it says that these components are not replicated. Am I to assume that this is the proper behavior and that it is not supposed to be replicated and that the statement that the "All external user database configurations, including Network Admission Control (NAC) databases" are not replicated is to include these shared profile components automatically created by CiscoWorks LMS?

Thanks,

3 REPLIES
New Member

Re: ACS Replication of Shared Profile Components

This information indeed can be replicated

From a configuration standpoint,

On the Master confirm that you have the Send checkbox is checked for User and group database

And on the machine being replicated too that thre Receive checkbox is checked for this entry

If that all checks out any chance of attaching the Database replication report, located under

Reports & activities -> Database Replication

New Member

Re: ACS Replication of Shared Profile Components

Andrew,

Thanks for your answer. Other shared profile compents and username/DB components are properly replicated. And yes, all the boxes are checked on the send (Master) and the receive (slave) (except the EAP-FAST policies). Replication of users, groups, and other shared profile components other than CiscoWorks are replicated.

Have you been able to do this successfully for the CiscoWorks Shared Profile components?

Thanks,

Jeff

New Member

Re: ACS Replication of Shared Profile Components

Turns out that this was bug ID CSCsa15456. Upgrading to ACS 3.3(2) immediately resolved the issue.

136
Views
0
Helpful
3
Replies
CreatePlease login to create content