Get-EsxCli on steroids V2

Get-EsxCli on steroids updated for V2

Get-EsxCli on steroids 18/10/2015

Update 18/10/2015: v2.0.3 – minor update – six ESXi build added and 8 new functions
3086167 – ESXi 5.0 Patch 12
3070626 – ESXi 5.1 Patch 8
3029944 – ESXi 5.5 Update 3
3116895 – ESXi 5.5 Update 3a
3029758 – ESXi 6.0 U1
3073146 – ESXi 6.0 U1a

New functions introduced in vSphere 6 Update 1:
add-vsan.cluster.unicastagent
enable-storage.iofilter
get-vsan.cluster.preferredfaultdomain
list-storage.iofilter
list-vsan.cluster.unicastagent
remove-vsan.cluster.unicastagent
set-storage.core.device.vaai.status
set-vsan.cluster.preferredfaultdomain

New functions introduced in vSphere 5.5 Update 3 (alredy in vSphere 6):
unmount-vsan.storage.diskgroup
mount-vsan.storage.diskgroup

Get-EsxCli on steroids 18/08/2015

472 cmdlets
Works with ESXi version 5 / 5.1 / 5.5 / 6.0

Build added for this version:

Build tested so far:

Known issues:
All ESXi version 6.0.0 – issue with device alias namespace.
The “esxcli device alias” namespace is present when connected to the host with “ssh”
However for this version only, in my test environment, it is not available with “Get-esxcli”
Consequently the two functions below are not available for this build:
Get-device.alias
lis-device.alias

The following build are missing:

I never managed to create an ESXi host with the build 653509 in a lab environment
The build 2702864 has been recalled

Get-EsxCli on steroids 14 /06 /2015

472 cmdlets
Works with ESXi version 5 / 5.1 / 5.5 / 6.0

Build added for this version:

Build tested so far:

Known issues:
All ESXi version 6.0.0 – issue with device alias namespace.
The “esxcli device alias” namespace is present when connected to the host with “ssh”
However for this version only, in my test environment, it is not available with “Get-esxcli”
Consequently the two functions below are not available for this build:
Get-device.alias
lis-device.alias

The following build are missing:

I never managed to create an ESXi host with the build 653509 in a lab environment
The build 2702864 has been recalled

Get-EsxCli on steroids 29 /04 /2015

472 cmdlets
Works with ESXi version 5 / 5.1 / 5.5 / 6.0

Major version change from 1.0.0 to 2.0.0
The previous approach below was not convenient when working with only one host:
$esxcliOutput = $esxcli.network.vswitch.dvs.vmware.vxlan.get()
$FinalTable = New-Object -Type PSObject -Prop ([ordered]@{
"VMHost" = $VMHost;
"esxcliOutput" = $esxcliOutput;
})
Return $FinalTable
}

The output is now directly the output of the esxcli command:
Return $esxcli.network.vswitch.dvs.vmware.vxlan.get()

Fix issues with 5 functions.
The condition to check if a parameter exist for this build was not correct

Example of a fix
2615704 {
If(($enabled -ne $Null)){
Write-error "At least one parameter is not compatible with this ESXi build:$Build "
}
Else{
Return $esxcli.iscsi.physicalnetworkportal.param.set($adapter,$nic,$option,$value)
}
}

Build test so far

Known issues:

ESXi 6.0 GA – issue with device alias namespace.
The “esxcli device alias” namespace is present when connected to the host with “ssh”
However for this build only, in my test environment, it is not available with “Get-esxcli”
Consequently the two functions below are not available for this build:
Get-device.alias
lis-device.alias

The following build is missing.
I never managed to create an ESXi host with this build number in a lab environment.

Get-EsxCli on steroids 22 /04 /2015

472 cmdlets
Works with ESXi version 5 / 5.1 / 5.5 / 6.0

Known issues:

ESXi 6.0 GA – issue with device alias namespace.
The “esxcli device alias” namespace is present when connected to the host with “ssh”
However for this build only, in my test environment, it is not available with “Get-esxcli”
Consequently the two functions below are not available for this build:
Get-device.alias
lis-device.alias

The following build is missing.