Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

Intel NICs flapping with ixgben driver 1.7.10 or later (76251)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 32252Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Intel NIC use the driver ixgben async driver version 1.7.10 or later.

When the last VM of a VLAN was power off,all NICs with "ixgben" driver in the same host will flap  once.

It is also triggered by removing a vmkernel NIC(vmk) if  it occupied the last active port in the VLAN.

The logs in ESXi host show similar to below

vmkernel.log will show error similar to
2018-11-09T07:05:20.524Z cpu146:33194)Net: 3654: disconnected client from port 0x3000008

vobd.log will show similar to

2018-11-09T09:02:21.422Z: [netCorrelator] 75780034230us: [vob.net.pg.uplink.transition.down] Uplink: vmnic7 is down. Affected portgroup: Management Network. 1 uplinks up. Failed criteria: 128
2018-11-09T09:02:21.422Z: [netCorrelator] 75780034373us: [vob.net.pg.uplink.transition.down] Uplink: vmnic4 is down. Affected portgroup: SRV-101. 0 uplinks up. Failed criteria: 128
2018-11-09T09:02:21.422Z: [netCorrelator] 75780034376us: [vob.net.pg.uplink.transition.down] Uplink: vmnic4 is down. Affected portgroup: Management Network. 0 uplinks up. Failed criteria: 128

This is not seen with vmklinux based driver ixgbe and also with Inbox driver

For more information refer to VMware KB : When remove port ID by power off a VM , the VLAN bitmap of the uplink will be reset to all zero

Note:The preceding log excerpts are only examples. Date,time and environmental variables may vary depending on your environment.

Cause

The driver "ixgben" triggers a "fake flapping"  to the ESXi and VLAN connection is  recovered after link flapping.

Impact / Risks

No Impact

Resolution

A new parameter was added to disable the workaround in  ixgben driver version 1.7.20
It provided a method to disable the behavior of NIC link flapping.

In the release note of "ixgben 1.7.20" below is noted

"- Link flapping after powering off the VM or during vMotion.
Workaround: use module parameter to disable the driver workaround for a kernel issue
(lost VLAN connectivity once the last VM in a port group has been shut down).
The kernel bug has been fixed in ESXi 6.5 U1 (and later releases), in which case the workaround can be safely disabled."

To download the 1.7.20 version of driver go to Customer Connect

If ESXi  is running on  ESXi 6.0 P07 or  ESXi6.5U1  and later, it's recommended to install ixgben 1.7.20  or above.
Then disable the "link flapping" workaround.

# esxcli system module parameters set -m ixgben -a -p "VlanRemoveWorkaround=0,0"

In above example,there were 2 network adapters using ixgben driver.

Workaround

1. To workaround on environment which is not running on ESXi 6.0 P07 or  ESXi6.5U1 or later, install the driver version 1.7.20 and keep the parameter "VlanRemoveWorkaround" at default enable status.

2. Alternatively you can use the VMware Inbox driver or the vmklinux based ixgbe driver.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
vSphere Authentication Proxy (vmcam) を使用して Active Directory ドメインにホストを追加すると、エラー コード 41737 で断続的に失敗する (76543)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESXi

Related Versions:

Take Our Survey

Support Assistant