|Applies To||AM 8.1, AM 8.0, AM 8.x, Authentication Manager 8.1|
|Issue||AM 8.1 Replication Critical Event Notification not sent when Primary down|
Attention! The following critical system event occurred: The replica instance on host am81r1.vcloud.local has changed from an undesirable state to a desirable state. The current replication status is HEALTHY
Attention! The following critical system event occurred: The replica instance on host am81r1.vcloud.local has changed from a desirable state to an undesirable state. The current replication status is UNHEALTHY. To troubleshoot this issue, see the Operations Console Help for instructions on downloading troubleshooting files.
|Resolution||Works as designed, the assumption that replication is for replicas, and Admins are logged into Primary most of the time. RFE has been created|
work-around, any simple SNMP server could be programmed to send a TCP connection to the Primary on one of the RSA ports, I recommend TCP port 5580 which is the offline authentication port used by agent ? this port should be up if authentication and all other services are working. That could be your early warning system to monitor the Primary if you do not have Administrators logged in all day. This is more conclusive of health than a Ping, but very simple to setup instead of setting up SNMP traps, etc?
|Notes||Critical Event Notification emails for Replication are not sent if the Primary is offline or shutdown. Replica OC shows Status Internal Error, but no email is sent until the Primary is powered back up, which is a false positive that the Replica is unhealthy. 5 minutes later email notification sent that replication is healthy.|
|Legacy Article ID||a68232|