PowerCLI Script to Ping Guest VMs by IP v4 address on ESXi

PowerCLI Script to Ping Guest VMs by IP v4 address on ESXi

PowerCLI 6.5.4 – A single ESXi host. Seeking to view the IPV4 only address for .guest.IPaddress (not the IPV6 address) to ping. Why? If a VM name is web102-IIS, but the DNS entry is web102; you can not ping web102-IIS.

Trying to tune https://github.com/alanrenouf/PowerActions/blob/master/PingVMsOnHost.ps1 $computer = ($computer).guest.IPaddress to ping the IPV4 address (not IPV6).
The end result would be 1 ping attempt to all guest VMs on the host using the IPV4 address and write VMNAME 192.168.1.200 is pingable. VMNAME 192.168.1.205 is NOT pingable (in red)

Use case – create quick baseline of guest VM state before and after an ESXi host change.

The Ask

PowerCLI 6.5.4 – A single ESXi host. Seeking to view the IPV4 only address for .guest.IPaddress (not the IPV6 address) to ping. Why? If a VM name is web102-IIS, but the DNS entry is web102; you can not ping web102-IIS.

Trying to tune https://github.com/alanrenouf/PowerActions/blob/master/PingVMsOnHost.ps1 $computer = ($computer).guest.IPaddress to ping the IPV4 address (not IPV6).
The end result would be 1 ping attempt to all guest VMs on the host using the IPV4 address and write VMNAME 192.168.1.200 is pingable. VMNAME 192.168.1.205 is NOT pingable (in red)

Use case – create quick baseline of guest VM state before and after an ESXi host change.

PowerCLI Script

[crayon-61091d48cec07814481389/]

Menu