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

LACP NICs down after ESXi host reboot (75048)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 6807Language:
English

13 like this article

Subscribe to get an email
newsletter with new updates

13 people found this helpful Please provide article feedback:

Symptoms

LACP NICs are down after reboot ESXi host running ESXi 6.7 U2

LACP ports on physical switch are blocked

Hosts using LAG for management cannot be managed anymore after host reboot.

Ports used for LACP are blocked on physical switch:

Example of port status of physical switch after host reboot:

1/1 Active Trk55 Up Yes Success 0 616
1/2 Active Trk55 Up Yes Success 0 616
1/3 Active Trk55 Up Yes Success 0 616
1/7 Active Trk54 Up Yes Success 0 615
...
2/11 Active Trk56 Blocked Yes Failure 0 617
2/12 Active Trk56 Blocked Yes Failure 0 617
...
2/1 Active Trk55 Up Yes Success 0 616
2/2 Active Trk55 Up Yes Success 0 616
2/3 Active Trk55 Up Yes Success 0 616
...

Example of NIC status after host reboot:

esxcli network nic list

vmnic0 0000:01:00.0 Down 1000 Full 1500 igbn 0.1.1.0 0x80000ec5 90:1b:0e:ec:be:6b 8086 1521 1734 11ce Intel Corporation I350 Gigabit Network Connection
vmnic1 0000:01:00.1 Down 0 Half 1500 igbn 0.1.1.0 0x80000ec5 90:1b:0e:ec:be:6c 8086 1521 1734 11ce Intel Corporation I350 Gigabit Network Connection
vmnic2 0000:3d:00.0 Down 0 Half 1500 i40en 1.3.1 3.33 0x800010ef 255.65535.255 4c:52:62:03:41:d5 8086 37d1 1734 1230 Intel(R) Ethernet Connection X722 for 1GbE
vmnic3 0000:3d:00.1 Up 1000 Full 1500 i40en 1.3.1 3.33 0x800010ef 255.65535.255 4c:52:62:03:41:d6 8086 37d1 1734 1230 Intel(R) Ethernet Connection X722 for 1GbE
vmnic4 0000:3d:00.2 Up 1000 Full 1500 i40en 1.3.1 3.33 0x800010ef 255.65535.255 4c:52:62:03:41:d7 8086 37d1 1734 1230 Intel(R) Ethernet Connection X722 for 1GbE
vmnic5 0000:3d:00.3 Down 0 Half 1500 i40en 1.3.1 3.33 0x800010ef 255.65535.255 4c:52:62:03:41:d8 8086 37d1 1734 1230 Intel(R) Ethernet Connection X722 for 1GbE
vmnic6 0000:18:00.0 Down 0 Half 1500 igbn 0.1.1.0 0x80000ee3 b4:96:91:32:1b:90 8086 1521 8086 00a1 Intel Corporation Ethernet Server Adapter I350-T4
vmnic7 0000:18:00.1 Up 1000 Full 1500 igbn 0.1.1.0 0x80000ee3 b4:96:91:32:1b:91 8086 1521 8086 00a1 Intel Corporation Ethernet Server Adapter I350-T4
vmnic8 0000:18:00.2 Down 0 Half 1500 igbn 0.1.1.0 0x80000ee3 b4:96:91:32:1b:92 8086 1521 8086 00a1 Intel Corporation Ethernet Server Adapter I350-T4
vmnic9 0000:18:00.3 Up 1000 Full 1500 igbn 0.1.1.0 0x80000ee3 b4:96:91:32:1b:93 8086 1521 8086 00a1 Intel Corporation Ethernet Server Adapter I350-T4
vmnic10 0000:d8:00.0 Down 0 Half 1500 igbn 0.1.1.0 0x80000f06 b4:96:91:37:86:94 8086 1521 8086 00a2 Intel Corporation Ethernet Server Adapter I350-T2
vmnic11 0000:d8:00.1 Down 0 Half 1500 igbn 0.1.1.0 0x80000f06 b4:96:91:37:86:95 8086 1521 8086 00a2 Intel Corporation Ethernet Server Adapter I350-T2

esxcli network vswitch dvs vmware lacp config get

dvSwitchProd  lag1      232217653  vmnic2,vmnic1,vmnic8,vmnic6,vmnic5,vmnic0  true     Active  Src and dst ip

esxcli network vswitch dvs vmware lacp stats get

DVSwitch        LAG ID         NIC     Rx Errors  Rx LACPDUs  Tx Errors  Tx LACPDUs
-----------------------------------------------------------------------------
dvSwitchProd  232217653  vmnic8          0           4          0           5
dvSwitchProd  232217653  vmnic1          0           4          0           5
dvSwitchProd  232217653  vmnic6          0           3          0           5
dvSwitchProd  232217653  vmnic2          0           4          0           5
dvSwitchProd  232217653  vmnic5          0           3          0           5
dvSwitchProd  232217653  vmnic0          0          12          0          13

Cause

This issue is caused due to LACPDU without SYNC flags.

Resolution

This issue has been fixed in VMware ESXi 6.7 P02 , release name ESXi670-20200400

Workaround

To workaround this issue re-enable all affected NICs on the ESXi host.

Example:
esxcli network nic down -n vmnic0
esxcli network nic up -n vmnic0

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
利用持有者令牌 - 检索用户信息：包含用户数据的已解码 base64 持有者令牌中存在不一致问题 (75137)

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

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 vSphere ESXi

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.7

Take Our Survey

Support Assistant