The primary appliance cannot connect to the replica appliance and/or the status of the Replica is unknown.
If the replica appliance’s SSH daemon is responsive by opening a Windows command prompt and telnet to the replica’s ip via port 22. If the replica is responsive check for any network issues between the two appliances.
If the replica is unresponsive over port 22 then check the replica’s /parconfig web interface via https://replicaipaddress:8443/parconfig/forcereplica.asp and login as parmaster or a Sys-Admin equivalent account.
If you can login, verify what mode the replica appliance is currently running in. If replica mode, placing it in primary mode would begin a process that would reboot the appliance (and restart the SSH daemon). Upon reboot you could then check the primary’s HA settings page to see if communication was reestablished.
If you cannot access the force replica page you would need to physically see if the appliance is powered on or not. If it is powered on, then please connect a monitor and see if its system console is reporting any errors. If errors are reported please document them and forward them to Quest Support. You would then need to power down the appliance and power it back on. Allow the appliance a few minutes for all the necessary services to start and then check the HA Settings page of the primary appliance to verify if the primary can once again see the replica.