We are on the home stretch of our Automating your vSphere Upgrade blog series. The final step of completing our upgrade will be upgrading our Virtual Distributed Switch (VDS). When upgrading your VDS on vSphere 6.7 the version is actually 6.6 (we will cover the details later). Please make sure prior to upgrading your VDS to 6.6 all ESXi hosts have been upgraded to ESXi 6.7, if you still have hosts on ESXi 6.5 you will only be able to upgrade to version 6.5.

I have been waiting for native GUI support for L2TP vpn with local users and it is finally here! Ubiquiti Unifi Equipment now supports local radius auth using the 5.5.x code of controller! Please see below on how you can get this setup. For my example i will be using the Stable Candidate 5.5.11.

Unifi Controller 5.5.11

Configuration is quite simple! Just follow these few easy steps and you will be up in no time.

I have been using Ubiquiti equipment for awhile at home and I figured i would finally write a blog post about it. Ubiquiti equipment is “enterprise class” equipment for the consumer.

I figured I would create a post that goes over two ways of loading the controller. The first option will be installing it on Ubuntu on bare metal or a VM, the second option is a docker container.

If you are installing this on a bare metal or virtual machine, i suggest a debian based image. My preference is Ubuntu.

I have been in process in configuring traffic shaping for multiple port groups. It seems with PowerCLI 6.3 R1 there are no native Powershell Cmdlets. Luckily I stumbled across @Lucd and his PowerCLI functions to manage these settings, i have put these into a script to mass get and set the settings for all port groups of a DVS’s.

Pre-Requsites

• VMware PowerCLI

Link to Script

• Get-VMwareTrafficShapingSettings.ps1
• Set-VMwareTrafficShapingSettings.ps1

Preparing to Execute the Script

The script is pretty straight forward, just need to define a few variables seen below and then you execute …

Ever needed to modify a DVS uplink configuration from ESXi Shell? I am currently troubleshooting some issues with DVS uplinks no longer being assigned on reboot.

As a heads up. If you are doing this on ESXi 6.0.. don’t. It can cause an issue with the proxy DVS having different ID than the actual DVS causing my original issue, still working with VMware Support to find out more details.

After “Restoring Network Configuration” a few too many times, I finally realized I could just add the uplinks back via CLI until support can figure out why this is occurring, here are the …

We are currently working on some Cisco ACI Integration and wanted to add a large VLAN Pool to a UCS Configuration.

Since currently Cisco UCS does not allow selecting multiple VLAN’s easily when adding to a VLAN Group or vNIC Template, we now have a pretty decent script that will do it for you.

The script can be found here.

 1# PowerCLI Script for adding VLAN to VLAN Group and vNIC Template
 2# @davidstamen
 3# http://davidstamen.com
 4
 5#Define Variables
 6$cred = Get-Credential
 7$ucs = "ucs01"
 8$startvlan = "100"
 9$endvlan = "150"
10$vnictemplate = …

Ever wonder why a VM isn’t on the network?

I was working on deploying some test VM’s and for some reason all the VM’s that were cloned decided to start with the network disconnected, and the connect on power on was also not selected.

I decided to throw together this quick one-liner that will make sure every VM is set to start connected on power on and is currently connected.

When setting up a cluster for testing you may not have 2 nics to use for management. to bypass the warning you can configure HA to not alert you for this issue.

To perform the steps in the c# client.

1. From the VMware Infrastructure Client, right-click on the cluster and click Edit Settings.
2. Select vSphere HA and click Advanced Options.
3. In the Options column, enter das.ignoreRedundantNetWarning
4. In the Value column, type true
5. Click OK.
6. Right-click the host and click Reconfigure for vSphere HA. This reconfigures HA.

To perform the steps in the webclient.

1. From the vSphere Web Client, right click …

I was working today on configuring NFS/Openfiler in my lab and came across an issue that my nested ESXi host’s couldn’t talk over the VSS (Standard Switch) I created. Upon further research when using nested ESXi you need to enable “Promiscuous Mode” on the VSS to allow the traffic to pass.