~ # vsish -e ls /net/portsets/vSwitch0/ports/16777220/Īs you can see it is pretty tedious to go through each of the ports and it does not easily allow you to figure out what is exactly connected to the port until you view the " status" property. When looking at a particular port, it provides quite a bit of information on what is connected and various metrics/statistics: ~ # vsish -e ls /net/portsets/vSwitch0/ports The "ports" section is what we are interested in: Here are some of things you can view for a given vSwitch using vsish: The solution described above is the proper and most flexible way of solving this problem, but what if you really wanted to query the internal vSwitch and extract out the MAC Addresses that way? Well the answer is, you can so using vsish on ESXi (vsish is not available on ESX unless you have the VMware debugging RPM package installed).
I am sure there is most likely a PowerCLI solution to solving this problem as well. You can easily do this through a script such as using the vSphere SDK for Perl script: which supports both stand vSwitch and distributed vSwitch or if you prefer a GUI, you can use the popular RVTools. You can search for all virtual machines and dump out their associated MAC Addresses and correlate that back to a particular vSwitch. However, you can still perform a lookup of all the MAC Addresses found on a particular ESX(i)/vCenter host by using the vSphere APIs. The vSwitch is not exposed like a traditional physical switch in which you can run commands against such as " show mac-address-table" to display the MAC addresses found on the switch. The internal VMware vSwitch is pretty much closed off as a blackbox.
The user was trying to locate a particular virtual machine's MAC Address due to an IP conflict that was identified. There was an interesting question this week on the VMTN community forums about querying a vSwitch on an ESX(i) host.
0 kommentar(er)
