Hello everybody.
I just connected a new host (HP DL360G9, ESXi 6.5 build 5224529, 4xGigabitEthernet) with new Cisco SG500 Switch and trying to configure link aggregation, but something go wrong.
The problem is - no matter what i do, after configuring link aggregation on Cisco (with or without LACP) the connection on vmnic0 is go down, physical link is down too.
I tried to configure almost everything on switch side and ESXi - no luck. Load balance policy ("Ip hash" and "port ID"), reset Cisco config, even vDS with LACP - vmnic0 with management ip going down after ports is aggregated (connection with this IP is still available!).
I tried to team only vmnic1, vmnic2 and vmnic3 - success.
vmnic2 and vmnic3 - success.
vmnic0, vmnic1, vmnic2 and vmnic3 - no good.
vmnic0 and vmnic1 - no good.
I tried to reboot ESXi - physical link is UP, but only until ntg3 (network card) driver is loaded.
I tried to reset ESXi configuration and reboot - all the same, even with default config first link is go down (connection to management IP is NOT available in this case).
What i do wrong?
Yes, i have read already this KBs.
Finally i found the source of problem - it`s a new ntg3 driver. After I do
esxcfg-module -e tg3
esxcfg-module -d ntg3
reboot
everything is good - no more failed uplinks.
Developers of ntg3 should see this post. Am i right, chnb?
Try to follow the procedure described in this KB: NIC teaming using EtherChannel leads to intermittent network connectivity in ESXi (1022751) | VMware...
and set PortFast on the ESXi facing ports STP may cause temporary loss of network connectivity when a failover or failback event occurs (10038...
Yes, i have read already this KBs.
Finally i found the source of problem - it`s a new ntg3 driver. After I do
esxcfg-module -e tg3
esxcfg-module -d ntg3
reboot
everything is good - no more failed uplinks.
Developers of ntg3 should see this post. Am i right, chnb?