phillbl
Enthusiast
Enthusiast

host profile creates local switch for vmotion even though its configured for Distributed Switch

Jump to solution

Hi,

I have a server and we use auto deploy to boot to esxi 5.5.  when the host comes online the server is loaded back into to vcentre & the cluster.  The host profile is then applied which also seems to work.

the strange thing is, when the server boots it creates a standard switch called M-dvSwitch, vmkernal port P-vMotion_Cluster Name.  This contains the nics from the HP VC.

once the host profile has applied all the correct setings occur.  we have other servers with distributed switch and this does not happen.

thanks

0 Kudos
1 Solution

Accepted Solutions
phillbl
Enthusiast
Enthusiast

hi, I think this is the reason

or VMkernel network adapters connected to the standard switch, it creates VMkernel network adapters and connects them to port groups.

For each VMkernel network adapter connected to a distributed switch, it creates a temporary standard switch (as needed) with uplinks bound to the VMkernel network adapter. It creates a temporary port group with VLAN and teaming policies based on recorded information. Specifically, IP‐hash is used if Etherchannel was used in the distributed switch.


Configures all VMkernel network adapter settings (assigns address, gateway, MTU, and so forth).

Basic connectivity is functioning, and the networking setup is complete if there is no distributed switch present.

If there is a distributed switch present, the system stays in maintenance mode until distributed switch remediation is complete. No virtual machines are started at this time. Because distributed switches requires vCenter Server, the boot process continues until vCenter Server connectivity is established, and vCenter Server notices that the host should be part of a distributed switch. It issues a distributed switch host join, creating a distributed switch proxy standard switch on the host, selects appropriate uplinks, and migrates the vmknic from the standard switch to the distributed switch. When this operation is complete, it deletes the temporary standard switch and port groups.

At the end of the remediation process, the ESXi host is taken out of maintenance mode, and HA or DRS can start virtual machines on the host.

View solution in original post

0 Kudos
2 Replies
antonmajor
Enthusiast
Enthusiast

doublecheck your licensing and ensure you have enough to cover the new host you are introducing.

0 Kudos
phillbl
Enthusiast
Enthusiast

hi, I think this is the reason

or VMkernel network adapters connected to the standard switch, it creates VMkernel network adapters and connects them to port groups.

For each VMkernel network adapter connected to a distributed switch, it creates a temporary standard switch (as needed) with uplinks bound to the VMkernel network adapter. It creates a temporary port group with VLAN and teaming policies based on recorded information. Specifically, IP‐hash is used if Etherchannel was used in the distributed switch.


Configures all VMkernel network adapter settings (assigns address, gateway, MTU, and so forth).

Basic connectivity is functioning, and the networking setup is complete if there is no distributed switch present.

If there is a distributed switch present, the system stays in maintenance mode until distributed switch remediation is complete. No virtual machines are started at this time. Because distributed switches requires vCenter Server, the boot process continues until vCenter Server connectivity is established, and vCenter Server notices that the host should be part of a distributed switch. It issues a distributed switch host join, creating a distributed switch proxy standard switch on the host, selects appropriate uplinks, and migrates the vmknic from the standard switch to the distributed switch. When this operation is complete, it deletes the temporary standard switch and port groups.

At the end of the remediation process, the ESXi host is taken out of maintenance mode, and HA or DRS can start virtual machines on the host.

View solution in original post

0 Kudos