But sometimes one of the PowerCLI cmdlets is missing a parameter you would like to use or has a parameter you don’t want to use in your environment. With the advent of PowerShell v2 you can now customise the PowerCLI cmdlets to your liking with the help of proxy cmdlets.
When you are using NIC Teaming you have a number of possible options to define the failover criteria. The failover criteria define when a NIC Team will switch from an active to a standby NIC. When you examine the HostNicFailureCriteria object in the API Reference Guide, you will notice that there are more criteria available than those that are accessible through the vSphere Client. Continue reading TA2650 scripts – Part 4 – NIC Teaming – “hidden” failure criteria
With the cluster profile XML file created in TA2650 scripts – Part 1 – Profiling your vSphere environment you can verify the configuration of the nodes against a reference node.
The XML file that can be created with the script from TA2650 scripts – Part 1 – Profiling your vSphere environment can also be used to assist you when you need to use the SDK. Continue reading TA2650 scripts – Part 2 – Using the profile XML file for SDK programming
During VMworld 2009 in San Francisco, Hal Rottenberg and myself presented a session called “TA2650 – Take PowerCLI to the Next Level”. During the session we promised to publish the scripts we showed (and those we did not show due to lack of time).
This is part 1 of these scripts. This script shows and explains how I used PowerShell to export the configuration of my vSphere environment, or part of it, to an XML file. Continue reading TA2650 scripts – Part 1 – Profiling your vSphere environment