On 2020/02/21 14:53:32, Andrija Panic wrote:
> Reason is misconfigured SSVM (by ACS) due to some other possible human
> misconfiguration (usually, can't say your case)
>
> 1.Can you ping the actual IP of the Secondary Storage NFS from inside the
> SSVM?
> 2. Did you try destroying the SSVM,
Reason is misconfigured SSVM (by ACS) due to some other possible human
misconfiguration (usually, can't say your case)
1.Can you ping the actual IP of the Secondary Storage NFS from inside the
SSVM?
2. Did you try destroying the SSVM, new one will be created
On Fri, 21 Feb 2020 at 13:07,
Hi,
We are trying to test the host HA, we have correctly configured OOBM and
KVMHAProvider (together with the NFS pool). Unfortunately, during testing we
cannot leave the suspect-degraded state loop. All values in the global
settings are default. My question is how are you organized HA for KVM?
On 2020/02/21 09:07:56, Andrija Panic wrote:
> Hi,
>
> your NFS server (secondary storate) is reported as 255.255.255.0 - which is
> obviously wrong, and indicates that SSVM was not correctly configured,
> which is usually due to wrong network configuration.
> Did you "really" follow the
Hi,
your NFS server (secondary storate) is reported as 255.255.255.0 - which is
obviously wrong, and indicates that SSVM was not correctly configured,
which is usually due to wrong network configuration.
Did you "really" follow the guide?
As NFS is not mounted, you can't register new
