PowerCLI 6.5 Release 1 and vSAN

powercliThe first email I saw this morning in my inbox was from my good pal, Alan Renouf. Alan is our product line manager for APIs, SDKs, CLIs and Automation Frameworks (congrats on the promotion Alan). Anyway, Alan was announcing the General Availability of VMware vSphere PowerCLI 6.5 Release 1. There are a whole bunch of improvements in this release, and much kudos must go to the PowerCLI team. However from a vSAN perspective, things look really cool. [Update] This version of PowerCLI also works with vSAN 6.2 and 6.0, so there is no need for customers to upgrade to vSAN 6.5 to leverage these new features of PowerCLI.

In Alan’s own words, “The PowerCLI Storage module has been a big focus on this release. A lot of functionality has been added around vSAN, Virtual Volumes (VVols), and the handling of virtual disks. The vSAN cmdlets have been bolstered to more than a dozen cmdlets which are focused on the entire life-cycle of a vSAN cluster. The entire vSAN cluster creation process can be automated with PowerCLI as well as running tests, updating the HCL database, and much more!” Here is a list of the vSAN cmdlets:

  • Get-VsanClusterConfiguration
  • Get-VsanDisk
  • Get-VsanDiskGroup
  • Get-VsanFaultDomain
  • Get-VsanResyncingComponent
  • Get-VsanSpaceUsage
  • New-VsanDisk
  • New-VsanDiskGroup
  • New-VsanFaultDomain
  • Remove-VsanDisk
  • Remove-VsanDiskGroup
  • Remove-VsanFaultDomain
  • Set-VsanClusterConfiguration
  • Set-VsanFaultDomain
  • Test-VsanClusterHealth
  • Test-VsanNetworkPerformance
  • Test-VsanStoragePerformance
  • Test-VsanVMCreation
  • Update-VsanHclDatabase

I am only highlighting the vSAN specific items in this post, but as Alan mentions, there are also a bunch of enhancements in other storage areas, such as the management of VMDKs, and new cmdlets for Storage Policy Based Management (SPBM) and VVols.

For more information on changes made in VMware PowerCLI 6.5 Release 1, including improvements, security enhancements, and deprecated features, see the VMware PowerCLI Change Log. For more information on specific product features, see the VMware PowerCLI 6.5 Release 1 User’s Guide. For more information on specific cmdlets, see the VMware PowerCLI 6.5 Release 1 Cmdlet Reference.

You can find the PowerCLI 6.5 Release 1 download HERE. Get it today!

7 Replies to “PowerCLI 6.5 Release 1 and vSAN”

  1. Wow great news ,Finally VMware has announced the general availability of VMware PowerCLI 6.5 Release 1 . This is amazing that VMware has added new features in PowerCLI 6.5 release 1 and these features are easy to use. All the new features are really great and very important. The good thing is that this version of PowerCLI also works with vSAN 6.2 and 6.0, so there is no need to upgrade to vSAN 6.5 to leverage these new features of PowerCLI. Thanks for sharing. The way you explained each and everything about the PowerCLI 6.5 Release 1 is really good. Thanks once again.

  2. There is still no option in powercli 6.5, to create a new vvol based datastore.
    The “New-datastore” CLI only has NFS/VMFS options

    1. I spoke to Alan Renouf about this. He said that you are the first customer to raise particular this request. A lot of the PowerCLI features are based on customer feedback, and clearly this is a gap at the moment. He said he will add it to the PowerCLI backlog as a high priority item.

  3. Unable to find type [VMware.VimAutomation.Sdk.Util10.ProductInfo]. Make sure
    that the assembly that contains this type is loaded.
    At C:\Program Files (x86)\VMware\Infrastructure\PowerCLI\Scripts\Initialize-Pow
    erCLIEnvironment.ps1:71 char:1
    + $powerCliFriendlyVersion =
    [VMware.VimAutomation.Sdk.Util10.ProductInfo]::PowerC …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~
    + CategoryInfo : InvalidOperation: (VMware.VimAutom…l10.Product
    Info:TypeName) [], RuntimeException
    + FullyQualifiedErrorId : TypeNotFound

Comments are closed.