NSX-v with Brocade 6740 Hardware VTEP – additional considerations | Telecom Occasionally

This means that when we design solutions using these products, we need to keep these capabilities in mind and configure things accordingly.

Source: NSX-v with Brocade 6740 Hardware VTEP – additional considerations | Telecom Occasionally

Advertisements

The Vitual SAN host cannot be moved to the destination cluster

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:

 

Verification:

  1. From Storage inventory view in vCenter, verify a VSAN datastore still exists.
  2. If it does, Putty into the ESXi host or access it via its ESXi Shell & execute the command:
    esxcli vsan cluster get
  3. If results appear, proceed to the solution …

Solution:

  1. From previous command line (SSH or ESXi Shell) to the affected host, execute the following command:
    esxcli vsan cluster leave
  2. Now add the host to the existing Host Cluster…

Both Verification and Solution steps together look like this:

List VM host network details

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

 

https://www.vmadmin.co.uk/resources/48-vspherepowercli/251-powerclinetworkoutputcsv