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
