This means that when we design solutions using these products, we need to keep these capabilities in mind and configure things accordingly.
The Vitual SAN host cannot be moved to the destination cluster: destination cluster vim.ClusterComputeResource:domain-### is Virtual SAN disabled
To resolve the problem we did the following:
- From Storage inventory view in vCenter, verify a VSAN datastore still exists.
- If it does, Putty into the ESXi host or access it via its ESXi Shell & execute the command:
esxcli vsan cluster get
- If results appear, proceed to the solution …
- From previous command line (SSH or ESXi Shell) to the affected host, execute the following command:
esxcli vsan cluster leave
- Now add the host to the existing Host Cluster…
Both Verification and Solution steps together look like this:
List VM host network details and output to the PowerCLI console:
Get-VMHostNetworkAdapter | select VMhost, Name, IP, SubnetMask, Mac, PortGroupName, vMotionEnabled, mtu, FullDuplex, BitRatePerSec
Output to CSV VM host network details:
Get-VMHostNetworkAdapter | select VMhost, Name, IP, SubnetMask, Mac, PortGroupName, vMotionEnabled, mtu, FullDuplex, BitRatePerSec | Export-Csv C:\VMHostNetworkDetails.csv
configure virtual router using Python