I have been adding a Dell VRTX as a Hyper-V 2012 R2 cluster to my System Center Virtual Machine Manager 2012 R2 system.
I have two nodes M620 nodes and some shared storage in the VRTX chassis. I created the cluster, added the storage as a Cluster Shared Volume, then added the Hyper-V role onto each of the nodes manually.
Next I went to VMM and chose the option Add Hyper-V Hosts and Clusters. I gave it the cluster management name, and from this it identified the two nodes. The Discover clusters and their nodes job completed successfully, as did the Create new host cluster job. After that good start I then had two failures, one for each node:
Error (10400) Before Virtual Machine Manager can perform the current operation, the virtualization server must be restarted. Recommended Action Restart VRTXNode1.rcmtech.co.uk and then try the current operation again.
These were followed by a “Completed w/ Info”, that actually contained two errors:
Error (441) Agent communication is blocked. On VRTXNode1.rcmtech.co.uk, the version of virtualization software or the VMM agent is unsupported. Recommended Action Update the agent and virtualization software, and then try the operation again. Error (441) Agent communication is blocked. On VRTXNode2.rcmtech.co.uk, the version of virtualization software or the VMM agent is unsupported. Recommended Action Update the agent and virtualization software, and then try the operation again. Warning (13926) Host cluster VRTX-HVC01.rcmtech.co.uk was not fully refreshed because not all of the nodes could be contacted. Highly available storage and virtual switch information reported for this cluster might be inaccurate. Recommended Action Ensure that all the nodes are online and do not have Not Responding status in Virtual Machine Manager. Then refresh the host cluster again.
I checked that the firewall was correctly configured, and that WinRM was working correctly. This is easily done by running:
winrm quickconfig
and also by doing a PowerShell Invoke-Command to verify remote communication, e.g. I used:
Invoke-Command -Computername vrtxnode1 -ScriptBlock {Get-ChildItem -Path C:\}
Everything was fine, so I rebooted the nodes, per the errors above. This was a bit strange as the nodes had rebooted twice as part of the process of adding the Hyper-V role. Once they were back up, from the VMs and Services view in VMM, I right-clicked the first node and chose the Add host to cluster option. This completed “w/ info”, with an error from the second node again saying that agent communication was blocked. But the first node had added successfully. I then repeated the Add host to cluster operation on the second node, which also completed “w/ info” but only contained a warning about multipath I/O not being enabled. This is to be expected as the dual PERC8 option isn’t quite available yet, so I only have a single controller in my VRTX chassis.
