So, I was trying to use all address-based algorithms (L2/L3/L3_L4) with and without LACP.
With no success, unfortunately.
Here is my CORE1 mlag peer config (not full, of course):
configure snmp sysName "CORE1"
configure snmp sysLocation "some location"
configure snmp sysContact "some contact"
configure slot 1 module X670G2-48x-4q
configure sys-recovery-level slot 1 reset
configure slot 2 module X460G2-48t-10G4
configure sys-recovery-level slot 2 reset
create vlan "isc"
configure vlan isc tag 1001
enable sharing 1:13 grouping 1:13 algorithm address-based L3_L4 lacp
configure vlan isc ipaddress 192.168.101.1 255.255.255.0
create mlag peer "isc_core"
configure mlag peer "isc_core" ipaddress 192.168.101.2 vr VR-Default
enable mlag port 1:13 peer "isc_core" id 13
and CORE2 mlag peer config:
configure snmp sysName "CORE2"
configure snmp sysLocation "some location"
configure snmp sysContact "some contact"
configure slot 1 module X670G2-48x-4q
configure sys-recovery-level slot 1 reset
configure slot 2 module X460G2-48t-10G4
configure sys-recovery-level slot 2 reset
create vlan "isc"
configure vlan isc tag 1001
enable sharing 1:13 grouping 1:13 algorithm address-based L3_L4 lacp
configure vlan isc ipaddress 192.168.101.2 255.255.255.0
create mlag peer "isc_core"
configure mlag peer "isc_core" ipaddress 192.168.101.1 vr VR-Default
enable mlag port 1:13 peer "isc_core" id 13
Whenever I changed to "lacp" on sharing, I changed respectively the NIC setting on server side to "lacp" as well. But it gave nothing...
When I change to sharing within single core (not through MLAG, all NIC-Team adapters on the same core), the lag started working (?).
I have expected the lag to run over MLAG as if it was on single core.
Anyone have successfully connected Windows Server 2012 NIC-Team through MLAG ?
Regards
Robert