Bes4dmin
asked on
vMotion and Management on same vswitch
Hi
I'm trying to setup vMotion and Management on the same vswitch using 3 vmnics. But vMotion doesn't work. It get stuck on 14% and then gives fails.
This is how it looks like..
vSwitch0, > Properties
vSwitch > Edit > Nic Teaming
Active = vmnic0, vmnic7, vmnic11
standby = [none]
unused = [none]
vMotion > Edit > Nic Teaming
Active = vmnic11
standby = vmnic0, vmnic7
unused = [empty]
Management > Edit > Nic Teaming
active = vmnic0, vmnic7
standby = vmnic11
unused = [empty]
I have the relevant tick boxes against the management and vmotion traffic types within each port group. The vswitch configuration is mostly default stuff, promiscuous = reject, mac address change = accept, forged transmits = accept, traffic shaping = disabled. MTU across the vswitch, port groups and physical switches is 1500.
Load balancing= Route based on the originating virtual port ID
Network Failover Detection= Link status only
Notify Switches= Yes
Failback= Yes
The thing is that if try this configuration with only 2 vmics it works. So what's the deal using 3 vmnics?
I'm trying to setup vMotion and Management on the same vswitch using 3 vmnics. But vMotion doesn't work. It get stuck on 14% and then gives fails.
This is how it looks like..
vSwitch0, > Properties
vSwitch > Edit > Nic Teaming
Active = vmnic0, vmnic7, vmnic11
standby = [none]
unused = [none]
vMotion > Edit > Nic Teaming
Active = vmnic11
standby = vmnic0, vmnic7
unused = [empty]
Management > Edit > Nic Teaming
active = vmnic0, vmnic7
standby = vmnic11
unused = [empty]
I have the relevant tick boxes against the management and vmotion traffic types within each port group. The vswitch configuration is mostly default stuff, promiscuous = reject, mac address change = accept, forged transmits = accept, traffic shaping = disabled. MTU across the vswitch, port groups and physical switches is 1500.
Load balancing= Route based on the originating virtual port ID
Network Failover Detection= Link status only
Notify Switches= Yes
Failback= Yes
The thing is that if try this configuration with only 2 vmics it works. So what's the deal using 3 vmnics?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yeah, that's the way to go but in this particular host I don't have enough nics to do that I'm afraid.
Are all you physical network ports, tagged with VLAN 300?
Have you confirmed using vmkping (source to target server IP Address)
there is good communication there?
do you not have another nic, and then create a two nic vSwitch dedicated for vMotion ?