This is very simple function that you can add to your ISE profile that allows a file-open dialog box that looks specifically for ISO files and uses the Mount-DiskImage Command.
Function Mount-ISO {
$FileBrowser = New-Object System.Windows.Forms.OpenFileDialog -Property @{
InitialDirectory = [Environment]::GetFolderPath('Desktop')
Filter = 'ISO-Images (*.ISO)|*.iso'
}
$null = $FileBrowser.ShowDialog()
Mount-DiskImage -ImagePath $FileBrowser.FileName
}
This simple powershell script will merge multiple CVS files into a single. Run this script from working directory where the CVS files are located:
$CSVFiles = Get-ChildItem -Filter *.csv | Select-Object -ExpandProperty FullName
$OutputFile = "c:\temp\merged.csv"
$Output = @();
foreach($CSV in $CSVFiles) {
if(Test-Path $CSV) {
$FileName = [System.IO.Path]::GetFileName($CSV)
$temp = Import-CSV -Path $CSV | select *, @{Expression={$FileName};Label="FileName"}
$Output += $temp
} else {
Write-Warning "$CSV : No such file found"
}
}
$Output | Export-Csv -Path $OutputFile -NoTypeInformationWhen troubleshooting an ESXi host one of the most common problems is testing connectivity. A tool that used on the console or ssh session of the ESXi host is vmkping. Use cases are testing connectivity from vmkernel to other servers in cluster like vMotion or vSAN connectivity.
This article from VMware KB article 1003728 shows use case on how to use vmkping.
There are situations where you may not have access to the root account to ssh into the box. There is way to still troubleshooting vmkernel network connectivity by using PowerCLi and ESXCli.
$esxcli = Get-EsxCli -VMHost (Get-VMHost "testesxihost") -V2
$params = $esxcli.network.diag.ping.CreateArgs()
$params.host = '10.1.1.2'
$params.interface = 'vmk0'
$params.size = '1472' #use 1472 for 1500 MTU or 8972 for 9000 MTU (VMware uses these values on MTU pings on ESXi)
$res = $esxcli.network.diag.ping.Invoke($params)
$res.summaryYou will then get output like this:
<
Duplicated : 0
HostAddr : 10.1.1.2
PacketLost : 0
Recieved : 3
RoundtripAvg : 49
RoundtripAvgMS : 0
RoundtripMax : 61
RoundtripMaxMS : 0
RoundtripMin : 42
RoundtripMinMS : 0
Transmitted : 3You can get further script options for ESXCLI for networking.diag.ping by:
PS C:\> $params
Name Value
---- -----
host Unset, ([string], optional)
wait Unset, ([string], optional)
df Unset, ([boolean], optional)
interval Unset, ([string], optional)
ttl Unset, ([long], optional)
debug Unset, ([boolean], optional)
nexthop Unset, ([string], optional)
count Unset, ([long], optional)
netstack Unset, ([string], optional)
size Unset, ([long], optional)
ipv4 Unset, ([boolean], optional)
ipv6 Unset, ([boolean], optional)
interface Unset, ([string], optional)
For help:
PS C:\> $esxcli.network.diag.ping.Help()
vim.EsxCLI.network.diag.ping
-----------------------------------------------------------------------------------------------------------------------
Send ICMP echo requests to network hosts.
Param
-----------------------------------------------------------------------------------------------------------------------
- count | Specify the number of packets to send.
- debug | VMKPing debug mode.
- df | Set DF bit on IPv4 packets.
- host | Specify the host to send packets to. This parameter is required when not executing ping in debug mode (-D)
- interface | Specify the outgoing interface.
- interval | Set the interval for sending packets in seconds.
- ipv4 | Ping with ICMPv4 echo requests.
- ipv6 | Ping with ICMPv6 echo requests.
- netstack | Specify the TCP/IP netstack which the interface resides on
- nexthop | Override the system's default route selection, in dotted quad notation. (IPv4 only. Requires int
| erface option)
- size | Set the payload size of the packets to send.
- ttl | Set IPv4 Time To Live or IPv6 Hop Limit
- wait | Set the timeout to wait if no responses are received in seconds.
I was asked to find a solution to automate importing OS customization Specs to our Vcenters. Its a task that not difficult but better if was scripted. I found this code located at ForwardorReverse blog. Export function allows you to export the OS customization Spec to $secname.xml and the import allows you to import them. These two functions are few years old according to the Blog but still work on Vsphere 6.5 without issue.
Function Export-OSCustomizationSpec {
param (
[string]$specName,
[string]$exportFile = "$specname.xml"
)
$csmgr = Get-View CustomizationSpecManager
if ($csmgr.DoesCustomizationSpecExist($specName)) {
$spec = $csmgr.GetCustomizationSpec($specName)
$csmgr.CustomizationSpecItemToXml($spec) | Out-File $exportFile
}
else {
throw "Spec $specName not found"
}
}
Function Import-OSCustomizationSpec {
param (
[string]$importFile,
[string]$specName #Use to change the spec name from that defined in the file
)
$specXml = Get-Content $importFile
$csmgr = Get-View CustomizationSpecManager
$spec = $csmgr.XmlToCustomizationSpecItem($specXml)
# Change the name if a new one was given.
if ($specName) {
$spec.Info.Name = $specName
}
if ($csmgr.DoesCustomizationSpecExist($spec.Info.Name)) {
throw "Spec $specName already exists."
}
else {
$csmgr.CreateCustomizationSpec($spec)
}
}
So I was building out a 44 node vSAN cluster last week and I ran into an issue where 12 of the ESXi hosts had their own network Partition group different than the other 32. I had no issues with the vSAN network, I was able to use vmkping every server so there was no communication issue with any of the hosts in the cluster via the vSAN kernel. In most cases vSAN Network partitioning occurs when there was issue with vSAN kernel communicating with other hosts.
After several attempts of removing the diskgroups, removing vSAN kernel, moving out of cluster and away from DVS then back I had no luck. I knew based on VMware supported Maximum that I could create a 64 node vSAN cluster. I was at a loss so after several hours troubleshooting and Google searching I ended up opening a SR with VMware after about hour or so troubleshooting the VMware engineer was at loss until he found an article that indicates that you must create some advanced settings on the ESXi hosts in order to see above 32 nodes and once we made those settings rebooted the hosts we had a single network partition our issue was resolved.
The KB article (2110081) shows how to perform task via esxcli via SSH logged into root but does not show how to do it via PowerCli.
$vcenter = Read-Host "Enter Vcenter connecting to"
Connect-VIserver $vcenter
$cluster = Read-host "Cluster Name"
foreach ($host in (Get-Vmhost -Location $cluster)){
Get-VMhost $host | Get-AdvancedSetting -Name "VSAN.goto11" | Set-AdvancedSetting -value 1 -confirm:$false
Get-VMhost $host | Get-AdvancedSetting -Name "Net.TcpipHeapMax" | Set-AdvancedSetting -value 1536 -confirm:$false
}Then reboot your hosts.
That’s it!
You would think that supported maximums would occur out of box but according to VMware they did not want smaller vSAN cluster to sacrifice memory overhead that would be required for larger vSAN clusters to run efficiently.