Month: December 2013

Winners of the Troubleshooting vSphere Storage eBook

Well the dust has settled and three winners have been randomly picked to receive an eBook copy of Troubleshooting vSphere Storage.  For the rest of you don't be saddened – Packt is running a $5.00 eBook sale from now through Jan 3rd so you can go on over to the books landing page and pick yourself up a copy for only 5 bucks 🙂 Thanks so much to everyone who entered.  This was certainly the most participated contest that I have had on this blog thus far.  Thank you all for your support and kind words.  Now I've heard back from 2 of the 3 winners, so if I fail to hear back from the third I'll most certainly pick another winner! And the winners are…. Eric Beach Bonnie Bauder Sean Thulin Also, starting December 30th I will be opening up my annual #HappyNewSphere contest so be sure to check back.  I've got some great sponsors this year including VMware Press and Pluralsight – so you can imagine what the prizes might be...

Read More

8 weeks of #VCAP – The rest of Section 2 – Port Binding, CLI, and DPIO

Section 2 of the blueprint is a pretty big one, and some of the pieces warranted their own post – however there are a lot of small little skills that don’t really require a complete tutorial so I thought I would just slam them all in here! Determine use cases for and apply Port Binding settings vSphere offers three types of port binding in their vSwitch settings (Distributed Virtual Switch only)– all of which are explained below Static – the port will be assigned immediately on connection to the vSwitch.  The VM will stay connected to this port even when it’s powered off.  The only way to free up the port is to explicitly remove the NIC from the VM.  Static Ports are managed through vCenter Server Dynamic – Port is connected when the VM is powered on and then disconnected when the VM is powered off.  Dynamic ports are managed through vCenter Server.  This method has been depreciated in vSphere 5.x Ephemeral – Both static and dynamic port binding has a set number of ports, in ephemeral, the ports are actually created and destroyed on the VM power on/power off event therefore requiring a bit more overhead.  That said, these are managed by the host, therefore, networking can still be connected/disconnected in the event that vCenter Server is unavailable. Choosing a port binding method is pretty easy –...

Read More

Kerberos authentication for the PowerShell plugin in vCO 5.5

The ability to have vCO kick off PowerShell scripts is pretty awesome!  And the fact that you can kick these off contextually inside of the vSphere Web Client is even more awesome!  Even more awesome than that, yes, that’s a lot of awesome is the new features offered with vCenter Orchestrator 5.5 – So, I’ve taken the plunge on one of my environments and upgraded.  Since then I’ve been slowly migrating workflows over – one of which utilized the PowerShell plug-in.  Now, since the appliance mode of vCO requires you to do a rip and replace rather than an upgrade (because I’m using the embedded database) I had to reinstall the PS plugin, therefore forcing me to reconfigure the Kerberos settings on vCO.   During this I realized that things are a little bit different than when I first blogged about vCO and PowerShell here.  Below is how I got it to work… First up is the WinRM setup on your PowerShell host.  This process  hasn’t changed from 5.1, however I’ll still include the steps and commands that need to be run below.  Remember these are to be executed on the Windows box that you wish to run the PowerShell script from. To create a winrm listener and open any required firewall ports winrm quickconfig To enable kerberos authentication winrm set winrm/config/service/auth @{Kerberos=”true”} Allow transfer of unencrypted data winrm set...

Read More

8 weeks of #VCAP – CDP and LLDP

Well, 8 weeks of VCAP has dwindled down into a serious 8 days of VCAP – and for now, how about a little bit of random information from the Networking section of the blueprint. First up, CDP and LLDP These are relatively easy to configure, however there are a few different modes that they can be run in, therefore I thought it would be best if I write them down in hopes that maybe I’ll remember them if any scenarios require me to configure them. Basically the functionality of the two protocols is identical – they both provide discovery of ports connected to a virtual switch.  CDP however supports just Cisco physical switches whereas LLDP supports any switch supporting LLDP.  Another note, CDP can be enabled on both vSphere Standard Switches and vSphere Distributed Switches – LLDP – dvSwitch only! So let’s have a look at the dvSwitch config first.  Like I mentioned earlier it’s pretty simple. From the properties tab of a vSphere Distributed Switch select ‘Advanced’.  From here its as simple as setting the status to Enabled, the type to either CDP or LLDP, and the Operation mode (explained below). Listen – ESXi detects and displays information from the associated physical switch port, but all information in regards to the virtual switch is not available to the physical switch. Advertise – ESXi presents information in regards to...

Read More

8 weeks of #VCAP – Syslog scenario by @tomverhaeg

Company policies state that every syslog capable device or server should send these logs to an appropriate syslog collector. Your colleague has already set up the VMware syslog collector on a separate machine, located at You have been tasked with setting up the syslog clients on the ESXi hosts, and ensuring that syslogs arrive on the syslog server. To configure the syslog collector on the ESXi hosts, we will be using the esxcli system syslog namespace. This allows us to set different options regarding the local and remote (which is what we want) syslog. Let’s review the default config first by using the following command: ~ # esxcli system syslog config get Default Rotation Size: 1024 Default Rotations: 8 Log Output: /scratch/log Log To Unique Subdirectory: false Remote Host: <none> We see that no remote syslog is being used. Let’s configure one, using this command: ~ # esxcli system syslog config set –loghost= Now that we have configure a remote loghost, we need to reload the syslog daemon to apply the configuration changes. Esxcli can help us once again: ~ # esxcli system syslog reload You might think that we’re ready now, but when we check our syslog, we don’t see syslog yet. Bummer! For this problem, I’ll reference to the ESXi firewall post ( as with the default security level, this outgoing traffic will be dropped. We...

Read More
  • 1
  • 2