I have some problems adding a cluster to my env. Well, I can add it if I skip the Cluster validation test, and it works. But I dont want to skip that. :-) I am somewhat new on scvmm, it might be some very basic.
Here is the error message I am getting:
Error (20400)3 parallel subtasks failed during execution.
Error (2931)
VMM is unable to complete the request. The connection to the VMM agent on the virtualization server (hyperv1.lab.local) was lost.
Unknown error (0x80338029)
Recommended Action
Ensure that the Windows Remote Management (WS-Management) service and the VMM agent are installed and running and that a firewall is not blocking HTTPS traffic.
This can also happen due to DNS issues. Try and see if the server (hyperv1.lab.local) is reachable over the network and can be looked up in DNS. You can ping the virtualization server from VMM management server and make sure that the IP address returned matches the IP address locally obtained from the virtualization server.
If the error still persists, restart the virtualization server, and then try the operation again.
Error (2931)
VMM is unable to complete the request. The connection to the VMM agent on the virtualization server (hyperv1.lab.local) was lost.
Unknown error (0x80338029)
Recommended Action
Ensure that the Windows Remote Management (WS-Management) service and the VMM agent are installed and running and that a firewall is not blocking HTTPS traffic.
This can also happen due to DNS issues. Try and see if the server (hyperv1.lab.local) is reachable over the network and can be looked up in DNS. You can ping the virtualization server from VMM management server and make sure that the IP address returned matches the IP address locally obtained from the virtualization server.
If the error still persists, restart the virtualization server, and then try the operation again.
Error (2931)
VMM is unable to complete the request. The connection to the VMM agent on the virtualization server (hyperv1.lab.local) was lost.
Unknown error (0x80338029)
Recommended Action
Ensure that the Windows Remote Management (WS-Management) service and the VMM agent are installed and running and that a firewall is not blocking HTTPS traffic.
This can also happen due to DNS issues. Try and see if the server (hyperv1.lab.local) is reachable over the network and can be looked up in DNS. You can ping the virtualization server from VMM management server and make sure that the IP address returned matches the IP address locally obtained from the virtualization server.
If the error still persists, restart the virtualization server, and then try the operation again.
Warning (26165)
The volume MSFT Virtual HD Multi-Path Disk Device on host hyperv1.lab.local is already formatted as NTFS. In order to prevent data loss, the volume has not been formatted.
Recommended Action
To format this volume, use the -ForceFormat parameter, or format the volume manually.