For more information, see Knowledge Base article KB 2034795.Īs a result only enable virtual distributed switch health check mechanism for troubleshooting and disable on production environments as it may cause problems on your VM’s. After you disable vSphere Distributed Switch health check, the generated MAC addresses age out of your physical network environment according to your network policy. Use health check to troubleshoot network problems, and then disable it after you identify and resolve the problem.
These MAC addresses result in extra network traffic, which can affect network performance. Depending on the options that you select, vSphere Distributed Switch health check can generate a significant number of MAC addresses for testing teaming policy, MTU size, and VLAN configuration. Step 0: Power off your Virtual machine (VM) in the VMWare Console, remote console or web client.
#Physical vs vmware mac address how to
How To Change E1000 into VMXNET3 without changing a MAC Address The steps. Which, after all, probably isnt the case. For information on MAC address generation in later versions, see:ESX/ESXi 3.x: The Setting Up MAC Addresses section of the ESX. You can enable health check to identify and resolve network problems you might be experiencing. And filtering by corresponding IP address in the VI client only works if your VMware tools are installed and working. VSphere Distributed Switch health check helps you identify and troubleshoot configuration problems with the vSphere Distributed Switch (VDS), and mismatched configurations between the VDS and your environment’s physical network. The problem occurred due to Distributed switch health check mechanism. This number is approximately the number of VLANs x host number = 20 x 210 = 4200 Everytime a new chassis was active on the switch around 3000 new MAC addresses created. Those chassis contain around 20 servers each that were included in the virtual Distributed switch. In the infrastructure two new chassis with Flex nodes have been added. But how so many addresses have been created on VMware infrastructure?
It seemed that a limitation of 70.000 MAC addresses created this problem. The investigation of the vendor (Cisco) showed that the problem was due to a hard limitation of MAC addresses on the switch.