A failover relationship has been created between servers {0} and {1} with the following configuration parameters: name: {2}, mode: hot standby, maximum client lead time: {3} seconds, reserve address percentage on standby server: {4}, auto state switchover interval: {5} seconds, standby server: {6}.
A failover relationship has been created between servers %1 and %2 with the following configuration parameters: name: %3, ...
A failover relationship has been created between servers {0} and {1} with the following configuration parameters: Name: {2} ...
A failover relationship has been created between servers {0} and {1} with the following configuration parameters: Name: {2} ...
A failover relationship has been created between servers {0} and {1} with the following configuration parameters: name: {2}, ...
A failover relationship has been created between servers {0} and {1} with the following configuration parameters: name: {2}, ...
A failure occurred while the reporting mechanism processed version vectors on the reference member. Version vectors are used ...
A failure of the host bus adapter might block the Fibre Channel connection between the storage and the virtual machines. ...
A failure response was sent. The HCAP Server sent Negatively Acknowledgment (NAK) for unsupported mandatory TLVs. HCAP client ...
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol ...