about 1 week ago - 3 comments
Recently released on the PowerCLI site there has been an updated version of the PowerCLI Poster, this time the PowerCLI Documentation and Engineering teams have done a great job of updating it into a readable poster and have even added my quick reference guide to it to make it an awesome document. Included in this
about 1 week ago - 4 comments
A few times in PowerGUI or generally I have needed the user to select a single entity so that I can use this entity further in the code to narrow down the output, with this in mind i created a quick PrimalForms form which can be used as a function and a single object selected,
about 1 month ago - 2 comments
As we announced in our post “We’re writing a book!”, Luc and myself started writing a PowerCLI book. At about the same time I got a once-in-a-lifetime opportunity to join EMC as a vSpecialist, how could I turn that down ! Now you don’t become a vSpecialist for free, I have been spending a fair
about 1 month ago - 4 comments
Recently at the London VMware User Group I gave an additional presentation on top of the normal PowerCLI session I normally provide (which was interactive this time and I think worked very well). The subject of this session was “Why EMC for VMware”, I have had a number of questions from people who know that
about 1 month ago - 1 comment
I have been given my normal resident slot at the London VMUG this Thursday, 15th July. At the last VMUG I showed how vEcoShell could be used to add the graphical interface back onto our PowerCLI scripts and also gave an overview of the “VMware Community PowerPack”, when performing the demo I showed how easy
about 3 months ago - 1 comment
A little while back I started a PowerPack which could be used in either PowerGUI or vEcoShell – the application formerly known as “The Virtualisation EcoShell or VESI, my PowerPack was a collection of the most used scripts from my site all laid out in a nice GUI format. Now why would you put a
about 4 months ago - 9 comments
Some of you might be interested to know, Alan and Luc are writing a PowerCLI book. We don’t have many more details at the moment but wanted to let you know, as we are both very excited (and nervous by the amount of work) about this project. As you know we both live and breathe PowerCLI. And we
about 4 months ago - 2 comments
I was recently contacted via my blog and asked if there was a way to find the VMs which are not named in vCenter the same as they are in Active Directory or their hostname, the person contacting me had explained that someone had “accidently” renamed a number of VMs and when there was an
about 4 months ago - No comments
You may have noticed a distinct lack of posts from me recently, I have been on holiday, I had a great time staying in Belgium and The Netherlands, a fantastic country which I would recommend to anyone thinking about travelling in northern Europe, not just for the red lights or “space cakes” either ! Whilst
(3) 
(13) 
(0)
about 1 year ago
There seems to be a bit of a bug. When I run the script it runs fine until it gets to host, where one of the vmnics is not assigned to a vSwitch. From that point on it just duplicates the details of the last port down the spreadsheet.
Try removing a vmnic from one of your hosts and run it again.
about 1 year ago
That’s strange, as you can see from my sample output there are hosts with nics not attached to VSwitches and it continues on.
about 1 year ago
OK, very weird. I just ran it again and its fine. Please ignore this (and delete the post if you like), while I try to figure out what was different).
about 1 year ago
forbes, thats fine, let me know if you work it out. Thanks for taking the time to read my blog !
about 1 year ago
Hi, I just noticed something very interesting. This script actually gives the “observed” VLANs, not just the port group VLAN IDs you set on the vSwitches. This is something that you can’t get from your VI client (it only provides observed IP ranges). Looking at the code, I assume that it doesn’t get this via CDP, but from listening to the traffic. Obviously you have to be careful with this type of data, however I think this is a real bonus to the tool. Very useful for troubleshooting network issues! Thanks
about 1 year ago
Well, since you’re asking for feedback – it would be great to see the load balancing method (# “Route based on originating virtual port ID”, “Route based on source MAC hash”, “Use explicit failover order”, or “Route based on ip hash”) and link failure detection method (Beacon or Link).
This should be listed for each vSwitch and the port groups should list if they use the vSwitch settings or if it is being overridden.
Also for the vSwitch and port groups if each vmnic is active or standby.
I wonder if we can use this to make a tool like RANCID http://en.wikipedia.org/wiki/RANCID?
I like your blog. Keep up the great work. very useful. Thanks!
I b e n
about 1 year ago
Iben, Thanks for your kind words, you have some great Ideas there, something for me to tackle when I return from VMworld.
I like the idea of turning it into a tool, might even add a GUI, I have been looking for an excuse to try PrimalForms.
The other additions are great, they will definately be added.
about 1 year ago
Something that would be useful to add, in addition to number of vSwitch ports, is the number of vSwitch ports that are still available. While this hasn’t been much of a problem since the ESX 2.x days (when there were only 32 ports per vSwitch – period) – I can certainly see it becoming more of an issue as people are beginning to stack up 50, 60, or more VMs per host…