Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

Dedicating specific NICs to portgroups while maintaining NIC teaming and failover for the vSwitch (1002722)

Last Updated: 10/29/2010Categories: Total Views: 24632Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

The following describes ESX supported NIC team policy:

ESX supports the combination of multiple physical network adapters (vmnics) into NIC teams.

NIC teaming allows ESX hosts to take advantage of the additional network connection for additional network sessions
and utilize the additional throughput for increased redundancy, fail over, and performance.

For more information about NIC teaming and Ether-Channel, see Sample configuration of EtherChannel / Link aggregation with ESX 3.x and Cisco /HP switches (1004048).

By default, ESX host directs network traffic for all defined portgroups out every available vmnic in the team. For example:

One virtual switch, vSwitch0, with three teamed physical NICs, vmnic0, vmnic1, and vmnic2

One Service Console portgroup, named Service Console

One Virtual Machine Network portgroup, named Production

One VMkernel portgroup, named VMotion

In this example, there are three portgroups in vSwitch0. Based on the default NIC teaming policy, all three portgroups may transmit and receive out of any available interface. As a result, the network traffic generated by one portgroup may affect the performance of another. In the sample configuration above, it is possible that high-volume VMotion activity may adversely affect communications on the other portgroups. The adverse affect on communication is because the default NIC teaming policy does not provide for isolation of one portgroup from another.

Solution

To provide isolation between different portgroups while still reaping the benefits of NIC teaming and its reliable failover mechanisms, you can modify the default NIC teaming policy to provide each portgroup with its own dedicated active network adapter.

To accomplish NIC teaming:

Note: These instructions use the example configuration from above.

Open the VMware Infrastructure Client and connect to the ESX host (or VirtualCenter) that you want to configure.

Select the ESX host object in the inventory and click the Configuration tab.

Click the Networking option under Hardware.

Locate the virtual switch containing the portgroups you want to modify. In this case, it is vSwitch0.

Verify that all three physical network adapters, vmnic0, vmnic1, and vmnic2, are assigned to vSwitch0.

Click Properties. The Properties window for vSwitch0 displays.

Click the first object in the list, vSwitch, and click Edit.

In the window that opens, click the NIC Teaming tab and verify that all three vmnics are displayed under Active Adapters.

Click OK to close the vSwitch Properties window.

Click the Service Console portgroup and click Edit.

In the window that opens, click the NIC Teaming tab and verify that all three vmnics are displayed under Active Adapters.
You want the Service Console to be dedicated to its own vmnic, vmnic0, under normal circumstances. To achieve this, select vmnic1 and click Move Down to move vmnic1 into a Standby Adapter role.

Select vmnic2 and click Move Down to move it to the list of Standby Adapters. At this point, vmnic0 is dedicated to the Service Console, but if vmnic0 fails, the Service Console will fail over to vmnic1 and then vmnic2.

Click OK.

Click the Production portgroup and follow steps 11 through 14 to move vmnic0 and vmnic2 to Standby Adapters. This dedicates vmnic1 to the Virtual Machine Network portgroup unless vmnic1 fails.

Click the VMotion portgroup and follow steps 11 through 14 to move vmnic0 and vmnic1 to Standby Adapters. This dedicates vmnic2 to the VMotion portgroup while still allowing failover to the vmnic0 and vmnic1 adapters if vmnic2 were to fail.

When configured, this solution provides each portgroup with its own dedicated network adapter, effectively isolating it from the network activity of the others. However, it also allows each portgroup to be failed over to the two remaining network adapters if its own network adapter loses connectivity.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESX Server

Related Versions:

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant