How to fix an IP address conflict on your network caused by a VM using VMware PowerCLI
Got an IP conflict and traced it to a MAC address in your VMware cluster? This PowerCLI one-liner finds the exact VM and NIC causing it across all your ESX hosts.
IP Address conflict? Have you narrowed the MAC down to being a VM in one of your ESX/vSphere clusters? Well use vSphere PowerCLI to figure out what device and adapter is causing the conflict. Example, if your MAC is 005056b60b13:
Get-vm | Select Name, @{N="Network";E={$_ | Get-networkAdapter | ? {$_.macaddress -eq "00:50:56:b6:0b:13"}}} |Where {$_.Network-ne ""}
And it will output the VM name and the Network Adapter causing the conflict. :)
Jason Samuel
Product leader, advisor, and international speaker with 27+ years in enterprise end-user computing, security, and cloud. Has deployed infrastructure at Fortune 500 scale across 34 countries. 1 of 3 people globally to hold Citrix CTP + VMware vExpert + VMware EUC Champion concurrently. 200+ articles, 1,000+ reader discussions.
VMware PowerCLI script to set the Memory Resources limit on your VMs to Unlimited in bulk
If you need to reset memory limits to Unlimited on all your VMs during a migration, this PowerCLI one-liner does it in bulk.
vmware-esxiVMkernel ports change automatically when applying a Host Profile
If your vMotion and Management VMkernel ports get swapped when you apply a Host Profile, you need to reorder the kernel port entries in the profile first. Here's the fix.
vmware-esxivMotion fails saying the operation is not allowed in the current state
If vMotion fails with 'The operation is not allowed in the current state', your ESX host is stuck in phantom maintenance mode. Restart mgmt-vmware and vmware-vpxa to clear it.