Comments on: More Network Info

By: Alan

Alan — Thu, 02 Feb 2012 13:17:08 +0000

No probs Fred, answered in vCheck comments

By: Fred Witteman

Fred Witteman — Thu, 02 Feb 2012 13:04:08 +0000

ooops excuse… me this was meant to be posted in the vcheck5.ps1

By: Fred Witteman

Fred Witteman — Thu, 02 Feb 2012 13:01:53 +0000

I have 2 ntp servers:
10.10.10.80
and
10.10.10.85
How should i define the $ntpserver ?

By: Script: Detailed NIC Information Report « Micronauts

Script: Detailed NIC Information Report « Micronauts — Mon, 22 Aug 2011 21:06:37 +0000

[...] I strolled over to Alan Reneuf's website (www.virtu-al.net). I had remembered seeing a script ("More Network Info") he created that I knew could collect the info we wanted. Thank you, [...]

By: Matt

Matt — Wed, 16 Mar 2011 03:49:05 +0000

great script!
Is it possible to add the load balancing setting for each vswitch? Ip_hash, src_id etc? I’ve been trying to do this myself but not having much luck so far.

By: PowerCLI: Host Network Config « Virtu-Al

PowerCLI: Host Network Config « Virtu-Al — Sat, 19 Feb 2011 15:45:46 +0000

[...] There is also some more advanced network information available via this script. [...]

By: Ken Cline

Ken Cline — Sun, 01 Mar 2009 17:10:03 +0000

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…

By: Virtu-Al

Virtu-Al — Fri, 20 Feb 2009 09:00:00 +0000

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.

By: Iben Rodriguez

Iben Rodriguez — Fri, 20 Feb 2009 04:58:00 +0000

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

By: forbes

forbes — Tue, 17 Feb 2009 18:04:00 +0000

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