I have configured LACP on one of my hosts connected to a Cisco SG300-20 (firmware 1.4.1.3) in L3 mode. Everything on both sides looks good. However, the virtual machine is not able to ping the default gateway on the SG300 nor is the SG300 able to ping the IP of the virtual machine. I know the IP configuration of the virtual machine is good because when I move it to a standard port group on the same VLAN all is good.
From vCenter 6.0.0 Build 3617395
LAG as seen in dvSwitch topology.
LAG ports on dvSwitch
Virtual machine ports on dvSwitch
On ESXi 6.0.0 Update 3 (build-5050593)
[root@VAPELHhost01:~] esxcli network vswitch dvs vmware list
VA-DvSwitch_for_Everything
Name: VA-DvSwitch_for_Everything
VDS ID: f1 ef 2b 50 9f f3 c2 d7-f1 81 53 04 b7 db 19 86
Class: etherswitch
Num Ports: 4352
Used Ports: 8
Configured Ports: 512
MTU: 1500
CDP Status: both
Beacon Timeout: -1
Uplinks: vmnic3, vmnic2
VMware Branded: true
DVPort:
Client:
DVPortgroup ID: dvportgroup-242
In Use: false
Port ID: 0
Client:
DVPortgroup ID: dvportgroup-242
In Use: false
Port ID: 1
Client: vmnic3
DVPortgroup ID: dvportgroup-242
In Use: true
Port ID: 36
Client: vmnic2
DVPortgroup ID: dvportgroup-242
In Use: true
Port ID: 37
Client: RHEL01.eth0
DVPortgroup ID: dvportgroup-385
In Use: true
Port ID: 28
[root@VAPELHhost01:~] esxcli network vswitch dvs vmware lacp config get
DVS Name LAG Name LAG ID NICs Enabled Mode Load balance
-------------------------- -------- ------ ------------- ------- ------ --------------
VA-DvSwitch_for_Everything lag1 23153 vmnic3,vmnic2 true Active Src and dst ip
[root@VAPELHhost01:~] esxcli network vswitch dvs vmware lacp stats get
DVSwitch LAGID NIC Rx Errors Rx LACPDUs Tx Errors Tx LACPDUs
-------------------------- ----- ------ --------- ---------- --------- ----------
VA-DvSwitch_for_Everything 23153 vmnic2 0 281 0 280
VA-DvSwitch_for_Everything 23153 vmnic3 0 281 0 280
[root@VAPELHhost01:~] esxcli network vswitch dvs vmware lacp status get
VA-DvSwitch_for_Everything
DVSwitch: VA-DvSwitch_for_Everything
Flags: S - Device is sending Slow LACPDUs, F - Device is sending fast LACPDUs, A - Device is in active mode, P - Device is in passive mode
LAGID: 23153
Mode: Active
Nic List:
Local Information:
Admin Key: 9
Flags: SA
Oper Key: 9
Port Number: 32770
Port Priority: 255
Port State: ACT,AGG,SYN,COL,DIST,
Nic: vmnic2
Partner Information:
Age: 00:00:05
Device ID: 1c:de:a7:31:63:f0
Flags: SA
Oper Key: 1000
Port Number: 56
Port Priority: 1
Port State: ACT,AGG,SYN,COL,DIST,
State: Bundled
Local Information:
Admin Key: 9
Flags: SA
Oper Key: 9
Port Number: 32771
Port Priority: 255
Port State: ACT,AGG,SYN,COL,DIST,
Nic: vmnic3
Partner Information:
Age: 00:00:05
Device ID: 1c:de:a7:31:63:f0
Flags: SA
Oper Key: 1000
Port Number: 58
Port Priority: 1
Port State: ACT,AGG,SYN,COL,DIST,
State: Bundled
[root@VAPELHhost01:~]
From Cisco SG300-20 (firmware 1.4.1.3)
LAG Management
LAG Settings
LAG Settings detail
I'm not sure what do next. I don't have any other device capable of LACP to test the switch.
I was able to figure out the problem. In the Cisco switch I had the LAN associated with the LAG instead of the individual switch ports. This was a bit counter intuitive as I figured that because vSphere is sending VLAN tagged traffic to the LAG that the VLAN should be associated with the LAG on the switch. Not so much.
I was able to figure out the problem. In the Cisco switch I had the LAN associated with the LAG instead of the individual switch ports. This was a bit counter intuitive as I figured that because vSphere is sending VLAN tagged traffic to the LAG that the VLAN should be associated with the LAG on the switch. Not so much.