The previous parts (Part1, Part2 & Part 3) in the dvSwitch series showed how to create a dvSwitch, a portgroup for Virtual Machines and a Service Console & vmKernle portgroup. The test setup now looks something like this:
The double Service Consoles and vmKernel connection might look confusing at first. But when you select one these connections, the vSphere client will show you to which uplink a specific connection is going.
Continue reading dvSwitch scripting – Part 4 – NIC teaming
In the previous dvSwitch posts (see Part1 & Part2) I created a dvSwitch with a dvPortgroup, and we migrated some guests to this dvSwitch .
In this part I’ll show you how to create Service Console and vmKernel portgroups over the dvSwitch. Again, all the shown scripts will do a minimal configuration of the new portgroups. More advanced configurations will be discussed in future posts in the dvSwitch series.
This is the schematic view of the configuration that we currently have.
With the introduction of vSPhere the types of Tasks you can select when you create a new Scheduled Task has increased. This is a very useful feature that allows you to schedule for example your (s)vMotions, your Snapshots, your Imports and Exports and so on.
In the PowerCLI Community there was a recent question on how these Scheduled Tasks can be created from PowerShell (see relocate vm’s from csv file and create schedule task in VC).
Being able to create a Scheduled Task for a svMotion for several guests from a PowerShell script, instead of clicking away in the vSphere Client, would be another step on the path of vSphere automation. Continue reading Scheduled Tasks – MethodAction
In Part 1 of the dvSwitch scripting series I created a simple dvSwitch with 2 uplinks, which I connected to all the ESX hosts that were returned as possible candidates. In this part I will show you how to add a dvPortgroups and how you can connect Virtual Machines to this dvPortgroup.
This is the schematic of what we have so far.
Continue reading dvSwitch scripting – Part 2 – dvPortgroup
With the introduction of vSphere one of the new features that was introduced was the vNetwork Distributed Switch. This new type of switch offers many more features than the “classical” vSwitch we knew.
In the current PowerCLI build there are no cmdlets present to create, configure, manage and remove this new type of switch. Surely this will change in one of the upcoming PowerCLI releases.
To bridge the time till the next release, I decided to write a number of functions that would allow PowerCLI users to work with the vNetwork Distributed Switch. Continue reading dvSwitch scripting – Part 1 – Creation
On Carter’s vSPhere PowerCLI Blog site we learned, just before VMworld, about Project Onyx. The program that will come out of this project will allow users to generate PowerShell code from actions done in the vSphere Client. But while we wait till the program comes in GA, is there an alternative for finding out what API call(s) an action in the vSphere Client generates ? In fact there is. And it’s free ! Continue reading The Onyx alternative ?
When you attend a conference like VMworld you get lots of goodies pushed your way. With some of these you only realise when you are back home what you were given. The vSphere 4.0 Quick Start Guide is a good example of such a little gem that came my way during the last VMworld. Continue reading The vSphere 4.0 Quick Start Guide – A little gem from VMworld