Currently I have installed 2 ACS 5.x with one of them defined as primary. When checking the health status of the 2 devices via "Monitoring and Reports - Dashboard" I get an "Status not available" for the secondary device which on the other hand results in a bunch of alarms mentioning "No status updates were received beweeen ..........". I'm able to ping the second ACS from the primary device and the config-synchronization between the 2 devices works perfectly.
Also the necessary processes are up an running on both boxes.
Please can anyone give me an advice where to check or change something ?
many thanks for your reply and sorry: i did not exactly specify the ACS version I'm running; it is 188.8.131.52 so I assume it is not a "bug-related" problem.
Today the situation changed dramatically since i also didn't receive any health status messages from the primary server; this issue has been solved after about 30 minutes without any intervention at all.
I will reload the secondary ACS tonight and hopefully everything will again come back to normal.
What I was talking about was CSCsu69983Restoring a configuration disconnects deployment and causes replication issues
And it also affects ACS 5.2
It's fixed in 5.2 patch 1.
After restoring a backup database to a primary database, the deployment is disconnected.
When a backup database is restored, the database no longer contains correct deployment information for the secondary instance that belonged to the previous database. To avoid sending replication updates to the wrong secondary instances, the underlying replication communication system is changed so that only reconnected or newly registered Secondaries will receive replication updates.
After a database restore on the primary, you must re-register each secondary instance again to the primary instance in the deployment. The registration should be performed using the "Hardware Replacement" option to indicate that the server being registered already exists within the deployment configuration.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...