Solved

vSwitch settings

Posted on 2014-02-21
7
431 Views
Last Modified: 2014-02-22
If I select ESX hosts, then configuration tab then networking the properties of vSwitch then select Management Network the Edit… I can see vMotion checkbox and management Traffic checkbox…

 I though Management Traffic and Vmotion are the same, and VM Network if for VMs t=network traffic.

I do not see anything for VMHA traffic…is there any dedicated network…or it uses Vmkernel?

Thanks
vmnetworkvmnetwork
0
Comment
Question by:jskfan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
7 Comments
 
LVL 120

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 334 total points
ID: 39878973
Management Traffic and vMotion traffic are different.

e.g. when a vMotion is in operation, traffic for vMotion is sent across the network interfaces and vSwitch which have been define by vMotion, as per the tick box you have discovered.

Management traffic, e.g. SSH access to the ESXi host IP Address is sent across the Management Network.

VMware "HA Traffic" is sent across the Management Network, as HA is management related, e.g. it looks at the default gateway, DNS resolution to test if the server is isolated.
0
 
LVL 13

Assisted Solution

by:Abhilash
Abhilash earned 166 total points
ID: 39879159
The vMotion traffic and management traffic are two different things. When a machine is vMotioned the memory bitmap file is moved between the hosts, this traffic is passed on the vMotion network. Management traffic carries the heartbeat and other management related traffic. These traffics are collectively related to management but they are all different.
When you say HA traffic it's just heartbeat traffic between slave and master hosts. This anyway is carried on management traffic.
0
 

Author Comment

by:jskfan
ID: 39879290
To my understanding VMKernel and Management Network look the same when I look at their display in the right pane:
VmMvmM
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
LVL 120
ID: 39879298
They may appear to look the same, but look carefully

1. Management Traffic is TAGGED as Management Traffic - has a unique IP Address e.g. Management Traffic is selected to pass on this VMKernel portgroup

2. VMKernel - is TAGGED as VMKernel - has a unique IP Address, it does not carry Management Traffic, because it's not selected.

that is the different, Management "VMKernel" Network Portgroup carries Management Traffic.

A normal VMKernel Prtgroup, does not, but it could carry Management Traffic, vMNotion, iSCSI and FT.

In an ideal world, you would try to isolate different types of traffic onto seperate vSwitches, and seperate physical network interfaces.
0
 

Author Comment

by:jskfan
ID: 39879432
Vmkernel and Management Network are 2 different names, but parameters are the same.

if I look under the Summary column, I see both of them  say "Vmotion and IP storage Port"
but the best practice, I guess is to enable vMotion on Vmkernel and disable Management traffic, and enable Management Traffic on VM Network  and disable vMotion.
0
 
LVL 120

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 334 total points
ID: 39879564
Best Practice is to have Management Network on one vSwitch, VMKernel for Storage Traffic on another vSwitch, and vMotion on another vSwitch.

Minimum 4 vSwitches, and 3 pairs of Network Interfaces, if you go by VMware Recommendations and Best Practice, and finally a vSwitch which carries VM Network Traffic.


What you are trying to do, is to ensure, that ALL traffic is isolated on it's OWN LAN.

So traffic does not mix or swamp a network.
0
 

Author Closing Comment

by:jskfan
ID: 39880087
Thank you Guys
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Ransomware is a malware that is again in the list of security  concerns. Not only for companies, but also for Government security and  even at personal use. IT departments should be aware and have the right  knowledge to how to fight it.
Teach the user how to install ESXi 5.5 and configure the management network System Requirements: ESXi Installation:  Management Network Configuration: Management Network Testing:
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question