vSphere 5.1 and later provides several schemes for automatic allocation of MAC addresses in vCenter Server. You can select the scheme that best suits your requirements for MAC address duplication, OUI requirements for locally administered or universally administered addresses, and so on.
The following schemes of MAC address generation are available in vCenter Server:
After the MAC address is generated, it does not change unless the virtual machine's MAC address conflicts with that of another registered virtual machine. The MAC address is saved in the configuration file of the virtual machine.
Next, choose a destination folder for VMware vCenter Converter Standalone and click Next. Then choose a setup-type: local installation to deploy only VMware vCenter Converter Standalone, or Client-Server installation if you want to install agent and client additionally. I choose local installation because I don’t want to convert the server.
Include two or more physical NICs in a team to increase the network capacity of a vSphere Standard Switch or standard port group. Configure failover order to determine how network traffic is rerouted in case of adapter failure. Select a load balancing algorithm to determine how the standard switch distributes the traffic between the physical NICs in a team. VMware Organizationally Unique Identifier (OUI) allocation assigns MAC addresses based on the default VMware OUI 00:50:56 and the vCenter Server ID. Prefix-Based MAC Address Allocation On ESXi hosts 5.1 and later, you can use prefix-based allocation to specify an OUI other than the default one 00:50:56 by VMware, or to introduce Locally.
The MAC address of a powered off virtual machine is not checked against the addresses of running or suspended virtual machines.
When a virtual machine is powered on again, it might acquire a different MAC address. The change might be caused by an address conflict with another virtual machine. While this virtual machine has been powered off, its MAC address has been assigned to another virtual machine that has been powered on.
If you reconfigure the network adapter of a powered off virtual machine, for example, by changing the automatic MAC address allocation type or setting a static MAC address, vCenter Server resolves MAC address conflicts before the adapter reconfiguration takes effect.
For information about resolving MAC address conflicts, see the vSphere Troubleshooting Download deep freeze serial number. documentation.
Include two or more physical NICs in a team to increase the network capacity of a vSphere Standard Switch or standard port group. Configure failover order to determine how network traffic is rerouted in case of adapter failure. Select a load balancing algorithm to determine how the standard switch distributes the traffic between the physical NICs in a team.
Configure NIC teaming, failover, and load balancing depending on the network configuration on the physical switch and the topology of the standard switch. See Teaming and Failover Policy and Load Balancing Algorithms Available for Virtual Switches for more information.
If you configure the teaming and failover policy on a standard switch, the policy is propagated to all port groups in the switch. If you configure the policy on a standard port group, it overrides the policy inherited from the switch.
|Standard port group|
|Route based on the originating virtual port||Select an uplink based on the virtual port IDs on the switch. After the virtual switch selects an uplink for a virtual machine or a VMkernel adapter, it always forwards traffic through the same uplink for this virtual machine or VMkernel adapter.|
|Route based on IP hash|
Select an uplink based on a hash of the source and destination IP addresses of each packet. For non-IP packets, the switch uses the data at those fields to compute the hash .
IP-based teaming requires that the physical switch is configured with EtherChannel.
|Route based on source MAC hash||Select an uplink based on a hash of the source Ethernet.|
|Use explicit failover order||From the list of active adapters, always use the highest order uplink that passes failover detection criteria. No actual load balancing is performed with this option.|
|Link status only|
Relies only on the link status that the network adapter provides. This option detects failures such as removed cables and physical switch power failures.
Sends out and listens for beacon probes on all NICs in the team, and uses this information, in addition to link status, to determine link failure.ESXi sends beacon packets every second.
The NICs must be in an active/active or active/standby configuration because the NICs in an unused state do not participate in beacon probing.
If failback is set to Yes, the default selection, the adapter is returned to active duty immediately upon recovery, displacing the standby adapter that took over its slot, if any.
If failback is set to No for a standard port, a failed adapter is left inactive after recovery until another currently active adapter fails and must be replaced.
|Active adapters||Continue to use the uplink if the network adapter connectivity is up and active.|
|Standby adapters||Use this uplink if one of the active physical adapter is down.|
|Unused adapters||Do not use this uplink.|