VMware Cloud Community
scottcofcqld
Contributor
Contributor
Jump to solution

Vmotion Vlan HP 2920


Hi. This may be a general or HP network question but I thought i would try here first.

I am trying to setup a Vmotion VLAN on a HP 2920 Switch as per this article VMware KB: Multiple-NIC vMotion in vSphere

I have the ports on the HP switch set as untagged to vlan 50, no trunking or aggregation as per the article.

I have a vswitch with 2 nics just for this. Management and VM Portgroup traffic is on another v switch.

It all works perfectly if I set the VLANs on the 2 vmotion vmkernel ports to None(0). If I set the VLAN to 50 then it stops working.

Is this as expected? In my other vswitch I have multiple VM Portgroups with different VLANS but these are connected to ports on the HP switch where the VLAN is tagged (not untagged)

Much appreciated

Scott

1 Solution

Accepted Solutions
a_p_
Leadership
Leadership
Jump to solution

It all works perfectly if I set the VLANs on the 2 vmotion vmkernel ports to None(0). If I set the VLAN to 50 then it stops working.

That's how it is supposed to work with the current switch port configuration. "Untagged" means that the physical switch port expects untagged packages, and adds/removes the VLAN ID to/from the packages itself.

André

View solution in original post

3 Replies
linotelera
Hot Shot
Hot Shot
Jump to solution

Hi

this happens because you set untagged ports to physical switch... If you would to make it works, you should modify switch port as tagged with vlan 50.

Hope this help

a_p_
Leadership
Leadership
Jump to solution

It all works perfectly if I set the VLANs on the 2 vmotion vmkernel ports to None(0). If I set the VLAN to 50 then it stops working.

That's how it is supposed to work with the current switch port configuration. "Untagged" means that the physical switch port expects untagged packages, and adds/removes the VLAN ID to/from the packages itself.

André

scottcofcqld
Contributor
Contributor
Jump to solution

Thanks to all responders. So it is my understanding of vlans and not a vmware/hp issue. Thanks again


Reply
0 Kudos