Community discussions

MikroTik App
 
Kpacu
just joined
Topic Author
Posts: 1
Joined: Tue Jun 09, 2020 7:48 pm

Mikrotik and Esxi 6.7 NIC teaming (802.3ad) ISSUE

Tue Jun 09, 2020 8:01 pm

Hello,

I have MikrotTk CRS317-1G-16S+ with License level:6

What kind of license I need to have, so I could make bond (802.3ad) with Esxi 6.7 (HPE ProLiant DL380 gen10) NIC teaming for Load balancing and Failover ?

Where I can find for best practice for bond procedure ?

I tried with layer-2-and-3 but unsuccessful

# model = CRS317-1G-16S+
/interface bonding add mode=802.3ad name=esxi_d slaves=sfp-sfpplus14,sfp-sfpplus13 transmit-hash-policy=layer-2-and-3
/interface bridge port add bridge=bridge1 interface=esxi_d
/interface bridge port add bridge=bridge1 interface=LAN

Image
https://wiki.mikrotik.com/wiki/Manual:Interface/Bonding

This is my configuration on Vmware
Image
I tried without bonding directly to bridge interfaces

/interface bridge port

add bridge=bridge1 interface=sfp-sfpplus15 <--- this is vmnic3
add bridge=bridge1 interface=sfp-sfpplus16 <--- this is vmnic2

but after interrupting on interface sfp-sfpplus15 everything stops

Has anyone had any difficulty with MikroTik ( CRS317-1G-16S+) RouterOS (6.47) and ESXI NIC teaming ?
 
killersoft
Member Candidate
Member Candidate
Posts: 235
Joined: Mon Apr 11, 2011 2:34 pm
Location: Victoria, Australia

Re: Mikrotik and Esxi 6.7 NIC teaming (802.3ad) ISSUE

Thu Jul 16, 2020 12:51 pm

I'm looking to do the same thing very soon, so a tested config( & esxi notes appreciated )
 
User avatar
cdiedrich
Forum Veteran
Forum Veteran
Posts: 997
Joined: Thu Feb 13, 2014 2:03 pm
Location: Basel, Switzerland // Bremen, Germany
Contact:

Re: Mikrotik and Esxi 6.7 NIC teaming (802.3ad) ISSUE

Thu Jul 16, 2020 2:17 pm

The problem is neither the physical switch nor the routerOS license level.
It's in ESX.
Link aggregation is only supported on distributed switches. These are only available from vSphere enterprise license level upwards.
All standard vSwitches in ESXi balance the vm NICs between all uplinks of the vSwitch and take care of failover - which is working very well, BTW (as long as an uplink physically goes down).

If you still are desperately looking for a real link aggegration, I'd suggest the following:

Remove all physical NICs from your current vSwitch.
Create a new port group on that vSwitch and call it "postBond", vlan ID 4095 (which means "trunk")

Create one vSwitch per desired LAG member, add ONE single physical NIC to it.
Create one port group per new vSwitch and call them "preBond-xx", vlan ID 4095.
Enable promiscuous mode on both the vSwitch and the port groups.

Spin up a router OS vm and add as many NICs as you have vSwitches created above.
Connect those NICs to the "preBond" port groups.
Add another single NIC and add it to the "postBond" port group.

In your virtual routerOS, create a 802.3ad bonding with all preBond-NICs as slaves.
Make sure your physical switch is configured the same way.
The Wiki shows you how to do this.

Then create a bridge in your virtual routerOS and add the bonding and the postBond-NIC to it.

Done.
-Chris
 
killersoft
Member Candidate
Member Candidate
Posts: 235
Joined: Mon Apr 11, 2011 2:34 pm
Location: Victoria, Australia

Re: Mikrotik and Esxi 6.7 NIC teaming (802.3ad) ISSUE

Fri Jul 17, 2020 9:40 am

Thanks for the advice on that. Just about to buy Vmware essentials plus kit v7.0..
The problem is neither the physical switch nor the routerOS license level.
It's in ESX.
Link aggregation is only supported on distributed switches. These are only available from vSphere enterprise license level upwards.
All standard vSwitches in ESXi balance the vm NICs between all uplinks of the vSwitch and take care of failover - which is working very well, BTW (as long as an uplink physically goes down).

If you still are desperately looking for a real link aggegration, I'd suggest the following:

Remove all physical NICs from your current vSwitch.
Create a new port group on that vSwitch and call it "postBond", vlan ID 4095 (which means "trunk")

Create one vSwitch per desired LAG member, add ONE single physical NIC to it.
Create one port group per new vSwitch and call them "preBond-xx", vlan ID 4095.
Enable promiscuous mode on both the vSwitch and the port groups.

Spin up a router OS vm and add as many NICs as you have vSwitches created above.
Connect those NICs to the "preBond" port groups.
Add another single NIC and add it to the "postBond" port group.

In your virtual routerOS, create a 802.3ad bonding with all preBond-NICs as slaves.
Make sure your physical switch is configured the same way.
The Wiki shows you how to do this.

Then create a bridge in your virtual routerOS and add the bonding and the postBond-NIC to it.

Done.
-Chris
 
nclmrc
just joined
Posts: 5
Joined: Sat Aug 24, 2019 2:33 am

Re: Mikrotik and Esxi 6.7 NIC teaming (802.3ad) ISSUE

Sun Dec 04, 2022 8:54 pm

this configuration work for me
/interface bridge
add admin-mac=C4:AD:34:07:B2:84 auto-mac=no mtu=1500 name=bridge
/interface ethernet
set [ find default-name=ether1 ] name=ether1-bonding-ESXi-vmnic1
set [ find default-name=ether2 ] name=ether2-bonding-ESXi-vmnic2
set [ find default-name=ether3 ] name=ether3-CAP1-Lucignano
set [ find default-name=ether4 ] name=ether4-CAP2-Lucignano
/interface bonding
add forced-mac-address=C4:AD:34:07:B2:84 mode=balance-xor name=bonding-ESXi slaves=ether1-bonding-ESXi-vmnic1,ether2-bonding-ESXi-vmnic2 \
    transmit-hash-policy=layer-2-and-3
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/interface bridge port
add bridge=bridge interface=bonding-ESXi
add bridge=bridge interface=ether3-CAP1-Lucignano
add bridge=bridge interface=ether4-CAP2-Lucignano
add bridge=bridge interface=ether5
add bridge=bridge interface=sfp1
[admin@Switch-Lucignano] > 
Image

Who is online

Users browsing this forum: rapix61, scoobyn8 and 50 guests