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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

ACS 5.5 Cluster

Hello,

we´ve a Cluster with 3 ACS5.5 Patch 3. Yesterday i´ve configured a lot. This morning the replication-id of the secondary Members differs.

Master: 16587 ;  Secondary 16502.

This results in a lot of problems, when the first server for authentication is a secondary. Reload does not solve the problem.

"Full replication" under "System Adininstration/Operations/Distributed System Management" solved the problem.

MY QUESTION. Is there a possibility to generate a Alarm/Syslog message when the ID from Secondary differs of 5 to the Primary?

 

Regards Horst

 

 

5 REPLIES

Hey, The feature set in ACS 5

Hey,
 
The feature set in ACS 5.5 might cater to your requirement:
 
Support for new diagnostic messages and alarms for replication failures—ACS 5.5 triggers new replication-related diagnostic messages and alarms to alert the administrator of replication issues in a deployment.
New Diagnostic Messages
 
Secondary node cannot establish communication channel against primary node on Heartbeat/Replication/Replay topic.
 
Primary node cannot establish communication channel against secondary node on Heartbeat/Replication/Replay topic.
 
Heartbeat from primary/secondary indicates that secondary is not synchronized with primary for long time.
 
No heartbeat status is received from secondary during certain amount of time.
 
No heartbeat status is received from primary node during certain amount of time.
 
New Alarms
 
Secondary node stopped from processing replications.
 
Secondary node cannot establish communication channel against Primary node on Heartbeat/Replication/Replay topic.
 
Primary node cannot establish communication channel against secondary node on Heartbeat/Replication/Replay topic.
 
Heartbeat from Primary/Secondary indicates that Secondary is not synchronized with Primary for a long time.
 
No heartbeat status is received from secondary during certain amount of time.
 
No heartbeat status is received from primary node during certain amount of time.
 
You can view these alarms in your Alarms Inbox from the ACS web interface. The new messages and alarms allow you to easily identify the root cause of the replication issue. ACS displays a workaround for the replication issues along with the alarm messages. You can use the workaround to fix the replication issues.
 
Ref: http://www.cisco.com/c/en/us/td/docs/net_mgmt/cisco_secure_access_control_system/5-5/release/notes/acs_55_rn.html

Rate if Useful :)

Sharing knowledge makes you Immortal.

Regards,

Ed

New Member

Hi Ed,thx for the fast reply.

Hi Ed,

thx for the fast reply. But i´m still a little bit confused. What kind of workaround is meant?

The Alarm that is displayed is 

sorad1Wed Jun 04 14:15:06 CEST 2014CSCOacs_Internal_Operations_DiagnosticsFATALApplying configuration changes failed

 

I have no Alarms, which indicates replication problems.

 

Horst

Hi Horst,This workaround is

Hi Horst,

This workaround is in 5.5, not in 5.3.

Rate if Useful :)

Sharing knowledge makes you Immortal.

Regards,

Ed

New Member

i´m using a cluster 5.5 Patch

i´m using a cluster 5.5 Patch 3.

New Member

Hi Ed,i can´t find the

Hi Ed,

i can´t find the workaround!

718
Views
10
Helpful
5
Replies