Straight forward deployment of an OVA..
Provide basic configuration setup..IP/DNS/NTP..
There are advanced configuration options to:
- Provide HTTP proxy information or the log server information.
- “Log Push to the Cloud Setting” option is also provided here. If you select this option then the logs will be pushed to VMware server in Cloud.
Once deployed browse to https://<IP or FQDN of the appliance>
- Accept certificate
- Add you license key and validate
- Click Generate the shared secret for the proxy.
At this point you deploy the proxy OVA – The deployment is similar to any OVA deployment. One difference is, in this case you need to provide the above generated secret at the deployment stage of the OVA.
If the pairing status is showing “Failed” or “Not Detected Yet”, then the shared secret key specified during vRealize Network Insight Proxy OVA deployment could be wrong. To fix this problem, use set-proxy-shared-secret command to set the correct secret key. This command replaces the old key with the new one, and therefore, vRealize Network Insight Platform can detect vRealize Network Insight Proxy.
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
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