First, make sure you’re using a version of PowerCLI that supports the get-esxcli cmdlet. In this case, I used a fresh install of PowerCLI 5.5.

First, get-esxcli needs to be run against a single host individually, you can loop through you’re hosts later, but again, one at a time. So I did:

In my case, I wanted to remove a “greyed out” NFS mount, and in esxcli, I would run: More »

Here is a PowerCLI script I use to find all orphaned VMDK’s in my vCenter environment.

I wrote this a long time ago, hopefully it still works

After installing Cisco UCS and performing the initial setup of the UCS Fabric Interconnects; there is a lot of work that needs to be completed prior to configuring the blade Service Profiles.

This can be done a multitude of ways, manually through UCSM, scripted through SSH or now through PowerShell using Cisco PowerTool. This allows us to use variables at the top of the script; these variables allow us to make the script portable for various customer deployments.

There are a couple features that are not working yet:

  1. Setting the Global Power Allocation Policy – due to the enormous lack of detail in the get-help sections of Cisco’s PowerTool, I have been unable to find which function controls the Global Power Allocation Policy.  I believe it to be the set-ucspowergroup cmd-let but I have been unable to make it work correctly.
  2. Adding custom roles with customer permissions – the add-ucsuserrole cmd-let is not very well documented either, like others; I cannot seem to figure out how to get this cmd-let to create a new role with custom permissions.

Using powershell, I was able to configure all the hosts in my vCenter instance

First, I needed to configure the syslog host

I then needed to open the appropriate firewall ports for the traffic to get through

On the C220 M3’s, we had to re-create vSwitch0 due to it using the legacy incorrect MAC (from the step above).