本文共 1526 字，大约阅读时间需要 5 分钟。
At one of my customers' sites today, I saw an error message that I've not seen before: VM MAC Conflict. "Well, that's certainly not good," I thought, as I poked around at the error message. To my chagrin, I could only find that error message for a single VM in the environment, and that error message wouldn't tell me with which other VM it was conflicting. So, I could only think of one way to figure out what was going on with this conflict: look at the MAC Address assigned to every NIC on every VM in the environment, and figure out what was causing the conflict. Easy! No, really, it was easy. Had I done it by hand, I would certainly have driven myself crazy, but PowerCLI made it nice and easy. I just used this command: (get-vm | get-networkadapter | ? {$_.MacAddress -eq "<offending MAC Address>").parent Lo-and-behold, it returned 2 VMs. One was the known VM that had flagged the error and the other was a powered-off VM. Maybe that's why it wasn't also flagging the error, but regardless, we easily identified the source of the problem and were able to resolve it. P.S. if you ever need to find all duplicate MAC addresses in an environment, you can use these commands: $allNICs = get-vm | get-networkAdapter $dupeMACs = (compare-object $allNICs.macAddress ($allNICs.macAddress | select -unique)).inputObject foreach ($thisMAC in $dupeMACs){ "="*17 + "`n$thisMAC`n" + "="*17 ($allNICs | ? {$_.macAddress -eq $thisMAC}).parent.name }
本文转自学海无涯博客51CTO博客，原文链接http://blog.51cto.com/549687/1981255如需转载请自行联系原作者
520feng2007