Quick Tip – PowerCLI Invalid server certificate

When trying to connect with PowerCLI to a vCenter Server Appliance the following error occurred:

Connect-vIServer : 18-7-2018 13:20:10 Connect-VIServer Error: Invalid server certificate. Use Set-PowerCLIConfiguration to set the value for the InvalidCertificateAction option to Prompt if you’d like to connect once or to add a permanent exception for this server.

As stated in the error, the Set-PowerCLIConfiguration command can be used to ignore the certificate check using the following syntax:

Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -Confirm:$false

After this command you’re able to connect to the vCenter without the certificate error.

Slow network throughput between Ubiquiti EdgeRouter VLANs

After putting my NAS in a separate storage VLAN I noticed that my network throughput was slow to and from the NAS. The throughput of a simple file copy from a windows laptop (wired at 1 GbE) to a SMB share on the NAS was only 17,7 MB. The Windows laptop was on a different VLAN then the NAS.

After some troubleshooting I noticed that the throughput within the VLAN was okay  (120 MB/s on a 1 GbE network). The routing between the VLANs is done by Ubiquiti EdgeRouter Lite. I investigated the Ubiquiti EdgeRouter settings by using SSH and noticed that VLAN forwarding for IPv4 was disabled by using the following command:

ubnt@ubnt:~$ show ubnt offload

IP offload module : loaded
forwarding: enabled
vlan : disabled
pppoe : disabled
gre : disabled
forwarding: disabled
vlan : disabled
pppoe : disabled

IPSec offload module: loaded

Traffic Analysis :
export : disabled
dpi : disabled
version : 1.354

The following commands enable VLAN forwarding for IPv4 and save the setting:

ubnt@ubnt:~$ configure
ubnt@ubnt:# set system offload ipv4 vlan enable
ubnt@ubnt: commit
ubnt@ubnt:# save
Saving configuration to '/config/config.boot' ...

This config change can be done without a reboot of the router. After making this change the network throughput was as expected. So make sure to do some tests and check VLAN offloading in the Ubiquiti EdgeRouter (it’s default disabled).

Configure VM autostart in the ESXi Embedded Host Client

For a standalone ESXi host I manage the host with the ESXi Embedded Host Client (HTML client). So no vCenter Server is used to manage this host. The standalone ESXi host is 24×7 up and running and has some critical infrastructure VMs for my lab and home environment. The critical VMs are automatically powered-on when when the ESXi host is booted with the autostart option in the host client.

In the latest versions of the Host Client (In vSphere 6.7 version 1.25 is included that already contains the autostart improvements) the autostart configuration is greatly improved what result in an easier configuration of autostart. if you are on vSphere 6.0 or 6.5 I suggest to upgrade to the latest ESXi Embedded Host Client before configuring autostart.

The upgrade of the Host client is easy, no maintenance mode and reboot of the ESXi host is needed. The upgrade can be done by following these steps:

  • Download the latest VIB for here, link
  • Upload the VIB on a datastore on your ESXi host
  • SSH to the ESXi host
  • Enter the following command to update the host client
esxcli software vib update -v /vmfs/volumes/<datastore>/<vibname.vib>

  • Refesh the host client webpage (https://<esxihostname>/ui/)
  • Check the version information in the host client (Help -> About)

Configure autostart in the ESXi Embedded Host Client

  • Open the ESXi host client by using the following URL:  https://<esxihostname>/ui/
  • Go to: Manage -> System -> Autostart->Edit Settings
    • Enable: Yes
    • Start delay: 60 seconds
    • Stop delay: 60 seconds
    • Stop action: shut down
    • Wait for heartbeat: yes
    • Save

  • Below the screen are the VMs listed. First enable autostart per VM by using the “Enable  autostart for this VM” button.
  • Once the autostart is enabled per VM, the order can be configured by increase or decrease the start order. The autostart order is displayed in the “autostart order” field.
  • Configure the autostart and order for the VMs you want to automatically start when the ESXi server is booted.
  • Reboot the ESXi host to test the autostart

With older versions of the ESXi Embedded Host Client it is “more complicated” to set the start order per VM. To set the autostart order with older versions:

  • Enable autostart as described above

  • In the Virtual Machines section, right click on the  field row and “Select columns”. Select the following columns:
    • Autostart order
    • Start delay
    • Stop delay

  • Right click on the VM with the “Autostart order” status on Unset and select “increase” to enable autostart and set the order

  • Configure the autostart and order for the VMs you want to automatically start when the ESXi server is booted.
  • Reboot the ESXi host to test the autostart