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

VxRail vSAN hosts running Intel X710 nic card go into not responding state (60439)

Last Updated: 11/23/2020Categories: TroubleshootingTotal Views: 10498Language:
Chinese (Simplified)JapaneseEnglish

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

VxRail vSAN hosts running Intel X710 NIC goes into not responding state randomly in the cluster.

You may see the following errors related to NICS Ethernet Controller X710 for 10GbE SFP+  ( ex. vmnic1 and vmnic0 in below logs ) in the vmkernel logs during which time the issue occurred with the host -:

2018-10-20T01:04:55.604Z cpu21:140896553)NetPort: 1662: enabled port 0x4000011 with mac 00:50:56:af:77:df
2018-10-20T01:05:15.214Z cpu42:678436159)WARNING: NetPort: 1934: failed to disable port 0x4000028 on DvsPortset-0: Busy
2018-10-20T01:05:15.214Z cpu42:678436159)netschedHClk: NetSchedHClkPortQuiesce:4918: vmnic1: received a force quiesce for port 0x4000028
2018-10-20T01:05:15.214Z cpu42:678436159)netschedHClk: NetSchedHClkPortQuiesce:4918: vmnic0: received a force quiesce for port 0x4000028
2018-10-20T01:05:15.214Z cpu42:678436159)netschedHClk: NetSchedHClkHashQuiesceHierarchyIter:396: vmnic0: dropped 506 pkts from queue netsched.pools.vm.67108904 while quiescing port 0x4000028
2018-10-20T01:05:15.215Z cpu42:678436159)Vmxnet3: 15916: There is still packet not transmitted when the device isdisabled, port:0x4000028, queue: 2
2018-10-20T01:05:15.215Z cpu42:678436159)NetPort: 1881: disabled port 0x4000028
2018-10-20T01:05:15.227Z cpu42:678436159)Vmxnet3: 17293: Disable Rx queuing; queue size 1024 is larger than Vmxnet3RxQueueLimit limit of 64.
2018-10-20T01:05:15.227Z cpu42:678436159)Vmxnet3: 17651: Using default queue delivery for vmxnet3 for port 0x4000028
2018-10-20T01:05:15.227Z cpu42:678436159)NetPort: 3208: resuming traffic on DV port 28679
2018-10-20T01:05:15.227Z cpu42:678436159)Team.etherswitch: TeamESPolicySet:5942: Port 0x4000028 frp numUplinks 2 active 2(max 2) standby 0
2018-10-20T01:05:15.227Z cpu42:678436159)Team.etherswitch: TeamESPolicySet:5950: Update: Port 0x4000028 frp numUplinks 2 active 2(max 2) standby 0
2018-10-20T01:05:15.227Z cpu42:678436159)NetPort: 1662: enabled port 0x4000028 with mac 00:50:56:af:f0:14
2018-10-20T01:05:15.228Z cpu42:678436159)NetPort: 1881: disabled port 0x4000028
2018-10-20T01:05:15.259Z cpu42:678436159)Vmxnet3: 17293: Disable Rx queuing; queue size 1024 is larger than Vmxnet3RxQueueLimit limit of 64.
2018-10-20T01:05:15.259Z cpu42:678436159)Vmxnet3: 17651: Using default queue delivery for vmxnet3 for port 0x4000028
2018-10-20T01:05:15.259Z cpu42:678436159)NetPort: 3208: resuming traffic on DV port 28679
2018-10-20T01:05:15.259Z cpu42:678436159)Team.etherswitch: TeamESPolicySet:5942: Port 0x4000028 frp numUplinks 2 active 2(max 2) standby 0
2018-10-20T01:05:15.259Z cpu42:678436159)Team.etherswitch: TeamESPolicySet:5950: Update: Port 0x4000028 frp numUplinks 2 active 2(max 2) standby 0

--------------------------------------------------------------------------------------------------------------------------------------------------------
vmkernel.0:2018-10-30T02:51:47.141Z cpu58:672058372)netschedHClk: NetSchedHClkHashQuiesceHierarchyIter:396: vmnic0: dropped 8 pkts from queue netsched.pools.persist.default while quiescing port 0x300003f
vmkernel.0:2018-10-30T02:51:47.141Z cpu58:672058372)netschedHClk: NetSchedHClkHashQuiesceHierarchyIter:396: vmnic0: dropped 503 pkts from queue netsched.pools.vm.50331711 while quiescing port 0x300003f
vmkernel.0:2018-10-30T02:51:52.066Z cpu53:74667289)netschedHClk: NetSchedHClkPortQuiesce:4918: vmnic0: received a force quiesce for port 0x3000012

--------------------------------------------------------------------------------------------------------------------------------------------------------
vmkernel.0:2018-10-30T02:51:47.140Z cpu58:672058372)netschedHClk: NetSchedHClkPortQuiesce:4918: vmnic1: received a force quiesce for port 0x300003f
vmkernel.0:2018-10-30T02:51:52.066Z cpu53:74667289)netschedHClk: NetSchedHClkPortQuiesce:4918: vmnic1: received a force quiesce for port 0x3000012

--------------------------------------------------------------------------------------------------------------------------------------------------------
2018-10-30T02:51:47.141Z cpu58:672058372)netschedHClk: NetSchedHClkHashQuiesceHierarchyIter:396: vmnic0: dropped 8 pkts from queue netsched.pools.persist.default while quiescing port 0x300003f
2018-10-30T02:51:47.141Z cpu58:672058372)netschedHClk: NetSchedHClkHashQuiesceHierarchyIter:396: vmnic0: dropped 503 pkts from queue netsched.pools.vm.50331711 while quiescing port 0x300003f

--------------------------------------------------------------------------------------------------------------------------------------------------------
grep  "while quiescing port" vmkernel.* | wc
1128   15792  228683
--------------------------------------------------------------------------------------------------------------------------------------------------------
grep "time since last heartbeat" vpxd-*.log
vpxd-681.log:2018-10-30T02:38:32.961Z info vpxd[7F086F66C700] [Originator@6876 sub=HostCnx opID=CheckforMissingHeartbeats-7460ee5a] [VpxdHostCnx] No heartbeats received from host; cnx: 52dce226-1083-fa13-d11c-99cb60f68547, h: host-115, time since last heartbeat: 63271ms

Purpose

This is a known issue with Intel X710 NIC confirmed by Intel and VMware. Refer to public articles below,

https://communities.vmware.com/thread/552470
https://communities.intel.com/thread/124544

Cause

Outdated drivers and firmware running on Intel X710 NIC as per VMware HCL. Please install the latest supported drivers and firmware.

Resolution

Upgrade NIC driver and firmware of intel X710 NIC for 6.5 update 2 as per VMware HCL.

http://partnerweb.vmware.com/comp_guide2/detail.php?deviceCategory=io&productid=38742&releaseid=338&deviceCategory=io&details=1&VID=8086&DID=1572&SVID=1028&SSID=1f9c&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc

Recommended Driver -: i40en version 1.7.11

Recommended firmware -: 18.5.0

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)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.6.x

Take Our Survey

Support Assistant