Script to Make Distributed Switch Port Groups

One of my customers is running many vCenter servers at many different sites.  Each site has its own distributed vSwitch, which we want to be based on an enterprise standard configuration.  That said, each site has specific needs and so needs to be able to vary from that enterprise standard.  What's that?  A repetitive task where many distinct objects need to have precise configurations applied to them?  Let's write a script!

I'm going to experiment with posting this script to GitHub rather than trying to put the thing in here as text.  It'll hopefully make it easier for people to use and will give me some version control and generally make it easier to access these things.  Before you use the script, make sure that the Distributed vSwitch exists and that your PowerCLI session is connected to vCenter.  So, how's this script work?

Well, you call it like this: make-vdspg.ps1 -vdswitch site-vSwitch

But it actually has more options than that (I've just added defaults to some of the options so that I don't have to type them in all the time).  It has a -configFile option; this option specifies the path to the CSV config file that describes all of the PortGroups that should exist on the distributed vSwitch.  It also has a -fixErrors switch; if this switch is turned on, the script will modify existing Port Groups that do not conform to the specifications in the config file.  Be careful with that one!  The last option is -vdswitch.  This is the name of the distributed vSwitch that you intend to manipulate,

So, what's the config file look like?  Well, it should simply be a CSV with the following columns: Name, VLAN, PortBinding, DVS.  The Name column specifies the name of the Port Group.  The VLAN column specifies the VLAN tag to assign to the port (use 0 for untagged ports).  The PortBinding column is used to make the PortGroup Ephemeral or Static.  The DVS column specifies the name of the DVS on which the PortGroup should be defined.

This is built to accommodate a single configuration file that can be used to control many vSwitches.  These switches have a site prefix and then a suffix that describes the nature of the vSwitch.  My config file has lines that are for specific vSwitches, which contain both the site prefix and the suffix, but most of the lines are generic and only contain the suffix.  When you specify the vSwitch name through the -dvswitch option, it is designed to read in any line for that specific vSwitch or any generic line that only specifies the suffix that belongs to the specified vSwitch.  So, if you're working on the SAC-Production vswitch, it will load all lines that specify "SAC-Production" in the DVS column, as well as all lines that specify "Production" in that column.

Please be careful when running scripts that you find on the internet.  This worked for me in this particular situation, but that's no guarantee that it'll work for you in yours.  Test thoroughly and make sure that you understand the script before executing it!  If you're interested in checking out the script, you can download it at my Github script repository.
I put together a simple sample of the input CSV below.  This file defines 3 Port Groups.  The first one is named "VL1-NetMgmt" and is on VLAN 1 and goes on the SAC-Production vSwitch.  The second one is named "VL2-Servers" and it is on VLAN 2 and goes on all Production vSwitches.  The third one is named "VL3-VDI" and is on VLAN 3 and goes on the SF-Production vSwitch.

Comments

  1. gergOctober 26, 2015 at 7:19 AM

    Hi Jason,

    This looks really useful. Is there any chance we could get some examples on how to run the script and what the csv should look like please?

    Thanks,
    Gerg

    ReplyDelete
    Replies
    1. Jason ColemanOctober 26, 2015 at 8:14 AM

      I went ahead and posted an example CSV. Do you have any specific questions about how to use the script, as I tried to explain its use in the body of the post?

      Delete
  2. UnknownFebruary 9, 2016 at 11:16 AM

    Jason,

    How are you setting the number of ports on each vlan?

    ReplyDelete
    Replies
    1. Jason ColemanFebruary 9, 2016 at 12:42 PM

      I haven't been, as the customer for whom I wrote this only uses Ephemeral Port Groups. It should be easy to add a column to the CSV and then read that in. Alternately, if you have a standardized size, you could just hard code it with the -NumPorts arguement on the set-dvportgroup cmdlet.

      Delete
    2. UnknownFebruary 9, 2016 at 1:00 PM

      Ahh I see. Yeah, I'm going to add a column in the .csv named NumPorts and then try adding -NumPorts $_.NumPorts after the new-vdportgroup -name $thisPortGroup.name

      Delete
  3. MaxJanuary 17, 2017 at 7:54 AM

    Hi Jason!

    Just wanted to say thank you for your script that helped me a lot during a migration from a Nexus 1000V to a virtual distributed switch from VMware.
    Based on your script, I have written a script for creating Virtual Port Group on Virtual Standard Switch.

    I have to say that your code is very clean from dev point of view and well indent.

    Thanks a lot!

    Best regards,

    ReplyDelete
    Replies
    1. Jason ColemanJanuary 17, 2017 at 7:57 AM

      I'm glad that you found it helpful!

      Delete
    2. UnknownMay 30, 2018 at 8:49 PM

      In vSphere 6.x when you create an new Distributed Port group it defaults to 8 ports right, however claims to increase decrease as needed right? When I run this vice create my own it sets to 128?

      Delete
    3. UnknownMay 30, 2018 at 9:00 PM

      Additionally would you know how to resolve this?

      My one liner to get a current vDS Port group listing (that I would later use this script with is:
      Get-VDSwitch -Name "01 DMZ dvSwitch" | Get-VDPortGroup |Select Name, @{N="VLANId";E={$_.Extensiondata.Config.DefaultPortCOnfig.Vlan.VlanId}}, PortBinding, VDSwitch |Export-CSV C:\temp\Scripts\ScriptInput\DVS.csv -NoTypeInformation -Force

      If we have IP block info in the name, example---
      MyFavPortGroup (172.31.139.0/24)
      The one-liner cant handle the / and puts a %2f and renames the output to MyFavPortGroup (172.31.139.0%2f24)
      Any idea how to defeat other than NOT put special char in PortGroup name. :-)

      Delete
    4. Jason ColemanJune 8, 2018 at 2:37 PM

      Edward - the first thing that I'd look at is the output from the get-vdportgroup command, to make sure that it's coming through correctly. I just did a quick test for export-csv and it looks like it has no problems with the forward slash, so I would expect that it's an issue with get-vdportgroup.

      It's ugly, but you could fix it with string replacement after the fact, by doing something like this in your Select:

      @{N="Name";E={$_.name.replace('%2f','/')}}

      Delete

Post a Comment

Sorry guys, I've been getting a lot of spam recently, so I've had to turn on comment moderation. I'll do my best to moderate them swiftly after they're submitted,

Popular posts from this blog

PowerShell Sorting by Multiple Columns

PowerShell's Sort-Object cmdlet is super useful, especially when preparing output for human consumption.  A few people have found my blog while looking for more information about its use, specifically while looking for how to sort by multiple columns (well, properties, technically).  I've never done so (much less written about it), so I hope those folks found answers elsewhere.  But, it got me curious... and it turns out that it's really easy. The Technet article on Sort-Object has the answer directly spelled out: just use commas to create a list of properties to sort by (in order to precedence).  Let's look at some examples!  First, prepare a variable with some good sortable data: $myData = get-eventlog System -newest 25 And then we can get to sorting!  Say you want to sort primarily by EntryType (Warning, Information, Error) and then by Source.  Easy-peasy: $myData | sort EntryType,Source How about if you want it to be in descending order?  Yeah, there&
Read more

Clone a Standard vSwitch from one ESXi Host to Another

One of my customers is standardizing the configurations on their HP C7000 enclosures (they've been set up at various sites by various administrators with varying involvement from the architecture team).  As such, we need to stand up some temporary resources so that we can take down the main enclosure for reconfiguration.  That's fine, we can easily ship a smaller enclosure to each site for temporary compute resources.  Some of the sites are using Standard vSwitches, so we need to be able to quickly copy the networking configuration over from their existing blades to these new, slightly different blades.  As I see it, we had 2 good options: 1) Capture a Host Profile with the desired vSwitch configuration.  Delete every other component of the Host Profile so that only the networking section is applied; design the new ESXi hosts so that the vSwitches'll work with the old vmnic-to-vswitch configurations. 2) Write a script to clone the vSwitch from ones ESXi host to another.
Read more

Deleting Orphaned (AKA Zombie) VMDK Files

A problem that most Virtualization Administrators need to deal with is Orphaned VMDK files (or Zombie VMDK files, as some people call them).  These are Virtual Machine hard drive files that are just hanging out, taking up storage, but are attached to no VMs.  How can this happen?  Well, the most common way is when an administrator needs to delete a VMDK but isn't quite ready to commit... so, after pressing "remove", they select "remove from virtual machine" rather than "remove and delete files".  The intent is always good: "I want to be able to restore this if it turns out to be necessary... so I'll just come back and delete it next week if nothing breaks!"  But, of course, next week something else happens and the file doesn't get deleted.  After a little while, it turns into "which files did I rename, again?" and nothing seems to happen. So, how do you deal with these orphaned files?  Well, a few years ago I found a scrip
Read more