Here’s a quick and dirty one-liner to find the total allocated CPU & Memory per ESXi host basis. This is useful when you want to get a quickly get your over-commitment ratios.
$TotalMem=0; Get-VMHost myESXiHost1 | Get-VM | ?{$_.PowerState -match 'PoweredOn'} | %{$TotalMem=$TotalMem+$_.MemoryGB};Write-Host $TotalMem
$TotalCPU=0; Get-VMHost myESXiHost2 | Get-VM | ?{$_.PowerState -match 'PoweredOn'} | %{$TotalCPU = $TotalCPU+$_.numCPU};Write-Host $TotalCPU
Get-VM foo* | %{
$VM=$_; $Snapshot= $VM
| Get-Snapshot;
if ($Snapshot -eq $null) { Write-Host $VM.Name }
}
Most vSphere Administrators need to inspect the LUN runtime names discovered by the ESXi hosts. What usually gets overlooked is that runtimes name across different hosts could be different. Hence I like to look at all the runtime names discovered across all hosts for that ‘said’ LUN. Here is an oneliner which does the same, pass the CanonicalName (NaaID) and it will tell you the RuntimeName:
function Get-DatastoreRuntimeName() {
param (
[string]$CanonicalName = $(Read-Host -prompt "Enter a CanonicalName")
)
Get-VMHost `
| Get-VMHostStorage `
| Select-Object -ExpandProperty ScsiLun `
| ?{$_.LunType -like "disk"} `
| Select-Object VMHost,CanonicalName,RuntimeName,@{Name="CapacityGB";Expression={[int]$_.CapacityGB}} `
| ?{$_.CanonicalName -like $CanonicalName}
}
What I usually do is find the NaaID for a Datastore and then use the NaaID to query the RuntimeName. Yes that’s a 2 step process. There might be an better way, but haven’t tried to explore it, since this gets my job done. 😉
I needed to generate a Datastore report. All the information I was interested in was available in via the Get-Datastore cmdlet, however it was nested deep. Hence churned up a quicky PowerCLI oneliner:
Get-Datastore `
| Select-Object -ExpandProperty ExtensionData `
| Select-Object `
@{Name="Name"; Expression={$_.Name}},`
@{Name="CanonicalName"; Expression={$_.Info.Vmfs.Extent.DiskName}},`
@{Name="CapacityGB"; Expression={[int]($_.Summary.Capacity/1GB)}},`
@{Name="FreeGB"; Expression={[int]($_.Summary.FreeSpace/1GB)}},`
@{Name="ProvisionedGB";Expression={[int](($_.Summary.Capacity - $_.Summary.FreeSpace + $_.Summary.Uncommitted)/1GB)}},`
@{Name="Moref"; Expression={$_.MoRef}} `
| ft
In case you are interested in the details of a specific datastore, you can filter the output from the previous oneliner, using the Where-Object cmdlet.
I needed a quick way to generate a report about VAAI status for all hosts in the vCenter Server. Hence wrote a PowerCLI oneliner to get the job done:
Get-VMHost | %{
Get-AdvancedSetting -Name DataMover.HardwareAcceleratedMove -Entity $_
Get-AdvancedSetting -Name DataMover.HardwareAcceleratedInit -Entity $_
Get-AdvancedSetting -Name VMFS3.HardwareAcceleratedLocking -Entity $_
} | Select-Object `
@{Name="Name"; Expression={$_.Entity}},`
@{Name="PropertyName"; Expression={$_.Name}},`
@{Name="Status"; Expression={ if($_.Value){"Enabled"} else{"Disabled"}}}
In case you are not aware of what VAAI is read about it here at KB#1021976.
Hmmm. Today I was looking up for how to test the existence of a variable a quick google search turned up a solution on stackoverflow.
Here’s the gist of is, you can use the ‘variable PsProvider’ to test the existence of a variable.
Test-Path variable:global:SomeVariable
Read the entire thread over here.
Mentioned here only for my convenience and archival purposes. The entire credit goes to the post on stackoverflow.
Here’s a quick oneliner to generate a nice report about the version, build and bios details on each host.
Get-VMHost | Select-Object -Property Name,Version,Build,@{Name='BIOS Version';Expression={(($_|Select-Object -ExpandProperty ExtensionData).Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo | ?{$_.Name -like "*bios*"}).Name.Split(' ')[4]}}
PS: there are no spaces or new lines in the code.
Enjoy!
