How to setup sharing in MLAG for Windows Server NIC Teaming ?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-08-2018 03:08 PM
Hello,
What is the best sharing algorithm for connecting Windows Server 2012 NIC teaming ?
We have a MLAG disign at the core and NIC teaming mode on Windows is switch independent.
I guess LACP is not good choice here (?).
REGARDS
What is the best sharing algorithm for connecting Windows Server 2012 NIC teaming ?
We have a MLAG disign at the core and NIC teaming mode on Windows is switch independent.
I guess LACP is not good choice here (?).
REGARDS
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-14-2018 01:28 PM
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
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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-14-2018 01:28 PM
Sure, I have all my user and server vlans tagged on the ISC link (which is 2 x 10Gb sharing port).
One thing I forgot to mention: when I check the MLAG status at EMC maps, all working MLAGS are shown as "up", but the one for server is "protecting" (don't know exactly what does it mean: have read EXOS 22.x user guide, but found no word about MLAG possible states).
One thing I forgot to mention: when I check the MLAG status at EMC maps, all working MLAGS are shown as "up", but the one for server is "protecting" (don't know exactly what does it mean: have read EXOS 22.x user guide, but found no word about MLAG possible states).
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-14-2018 01:28 PM
Sorry, just re-read your original post and you mentioned that. Just didn't see it in the config. Just checking, is your server vlan tagged on the ISC links?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-14-2018 01:28 PM
Hello Brian !
Each time I was changing the sharing lacp options, I disabled the mlag on both peers, then disabled sharing, enabled sharing with new options and enabled mlag again.
Each time I was changing the sharing lacp options, I disabled the mlag on both peers, then disabled sharing, enabled sharing with new options and enabled mlag again.
