Community discussions

MikroTik App
  4. RouterOS
  5. General

6.43.8 l2mtu bonding x86

Post Reply
 
Muator
just joined
Topic Author
Posts: 22
Joined: Tue Jun 14, 2011 6:26 pm

6.43.8 l2mtu bonding x86

Sun Jan 20, 2019 4:24 pm

Сервер х86, ether1 - Realtek, ether2 - intel i350, ether2 - intel i350.
Столкнулись со странной проблемой MTU, L2MTU 0.
При создании вланов, использовалась сетевая ether1, позже добавили i350-t2, создали bonding1, изменили на всех вланах интерфейс с ether1 на bonding1.
Удалить влан можно без проблем. Создать влан, можно только на интерфейсе ether1.
Если создать влан, на интерфейсе bonding1, получается ошибка "coldnt create int - cannot change mtu" что то в этом роде.
Если создать влан на ether1 и изменить интерфейс на bonding1 со второго раза получится изменить. Первый раз ошибка.
Если bonding down/up l2mtu то пусто то 65531. Попытки изменить L2MTU MTU из консоли, не привели к успеху.
Получили такие баги.
Пинг и winbox с мира доступен, winbox из локалки, пустые поля все. Не работает nat.
Сервер онлайн, supout готов, могу выслать.
Если ether1 удалить из bonding1, можно создать vlan2 с нормальным MTU L2MTU.

___________________________________________________________________________________________________________

Server x86, ether1-Realtek, ether2 - intel i350, ether2-intel i350.
Faced a strange MTU problem, L2MTU 65531.
When creating plans, have been used ether1, later added i350-t2, created bonding 1, changed at all vlnach interface with ether1 on bonding1.
You can remove the VLAN without problems. You can create a VLAN only on the ether1 interface.
If you create VLANs on the interface bonding 1, you get the error "couldn't create int - cannot change mtu" something like that.
If you create a VLAN on ether1 and change the interface to bonding1 the second time will change. First mistake.
If bonding down / up l2mtu is empty then 65531. Attempts to change the MTU L2MTU from the console, has not led to success.
Got bugs like this. Ping and winbox with world available, winbox from local empty fields all. Nat does not work.
Server online, supout ready, I can send.
If ether1 is removed from bonding1, you can create a vlan2 with a normal l2mtu MTU.
Code: Select all
int pr       
Flags: D - dynamic, X - disabled, R - running, S - slave 
 #     NAME                                TYPE       ACTUAL-MTU L2MTU  MAX-L2MTU MAC-ADDRESS      
 0  R  ether1                             ether            1500             4080            2C:4D:54:
 1  RS ether2                             ether            1500             9014            A0:36:9F:
 2  RS ether3                             ether            1500             9014            A0:36:9F:
 3  R vlan18                              vlan             1500            65531            A0:36:9F:
 4  R  vlan19                             vlan             1500            65531            A0:36:9F:
 5  R  van34                              vlan             1500            65531            A0:36:9F:
 6  R  bonding1                           bond             1500            9014            A0:36:9F:
 8  R  vlan2                                vlan             1500              9010            A0:36:9F:
int pr det

0  R  name="ether1" default-name="ether1" type="ether" mtu=1500 actual-mtu=1500 l2mtu=4080 mac-address=2C:4D:54: 
       last-link-up-time=jan/20/2019 11:08:37 link-downs=0 

 1  RS name="ether2" default-name="ether2" type="ether" mtu=1500 actual-mtu=1500 l2mtu=9014 mac-address=A0:36:9F: 
       last-link-up-time=jan/20/2019 11:08:38 link-downs=0 

 2  RS name="ether3" default-name="ether3" type="ether" mtu=1500 actual-mtu=1500 l2mtu=9014 mac-address=A0:36:9F: 
       last-link-up-time=jan/20/2019 11:08:39 link-downs=0 

 3  R  name="vlan18" type="vlan" mtu=1500 actual-mtu=1500 l2mtu=65531 mac-address=A0:36:9F: last-link-down-time=jan/20/2019 11:25:38 
       last-link-up-time=jan/20/2019 11:25:45 link-downs=2 

 4  R  name="vlan19" type="vlan" mtu=1500 actual-mtu=1500 l2mtu=65531 mac-address=A0:36:9F: last-link-down-time=jan/20/2019 11:25:38 
       last-link-up-time=jan/20/2019 11:25:45 link-downs=2 

 5  R  name="vlan34" type="vlan" mtu=1500 actual-mtu=1500 l2mtu=65531 mac-address=A0:36:9F: last-link-down-time=jan/20/2019 11:25:38 
       last-link-up-time=jan/20/2019 11:25:45 link-downs=2 

 6  R  name="bonding1" type="bond" mtu=1500 actual-mtu=1500 l2mtu=9014 mac-address=A0:36:9F: last-link-down-time=jan/20/2019 11:25:38 
       last-link-up-time=jan/20/2019 11:25:45 link-downs=4
       
 8    R  name="vlan2" type="vlan" mtu=1500 actual-mtu=1500 l2mtu=9010 mac-address=A0:36:9F: last-link-down-time=jan/20/2019 11:25:38 
       last-link-up-time=jan/20/2019 11:25:45 link-downs=3
Last edited by Muator on Thu Jan 24, 2019 10:35 pm, edited 1 time in total.
Top
 
Muator
just joined
Topic Author
Posts: 22
Joined: Tue Jun 14, 2011 6:26 pm

Re: 6.43.8 l2mtu bonding x86

Thu Jan 24, 2019 10:49 am

Делал ресет систем, после этого создавал bonding, создаю влан, получаю ошибку - cold not set MTU (6).
Прошиваю 6.34.2 вланы на bonding работают без проблем. Проверял на архитектуре х86 и x86_64.

_______________________________________________________________________________________

I made a reset of systems, after that I created a bonding, I create a vlan, I get an error - cold not set MTU (6).
I sew 6.34.2 of the vlan on the bonding work without problems. Checked on the x86 and x86_64 architecture.
Top
 
Muator
just joined
Topic Author
Posts: 22
Joined: Tue Jun 14, 2011 6:26 pm

Re: 6.43.8 l2mtu bonding x86

Thu Jan 24, 2019 10:58 am

viewtopic.php?f=2&hilit=bonding&p=70032 ... e7e141927b
Аналогичная проблема.
Все кто обратил внимание, на х86_64 и считают что проблема в этом, ошибаются.
Изменял архитектуру на просто х86, проблема актуальна.

_____________________________________________________________________

Similar problem.
All who paid attention to x86_64 and believe that the problem is this, is wrong.
Changed the architecture to just x86, the problem is relevant.
Top
 
Muator
just joined
Topic Author
Posts: 22
Joined: Tue Jun 14, 2011 6:26 pm

Re: 6.43.8 l2mtu bonding x86

Thu Jan 24, 2019 6:57 pm

Повышая версию прошивки, 6.35,6.36,6.37.
Выяснилось, что на 6.36 уже есть проблема с l2mtu, автоматически оно устанавливается в значение 1496, если выключить-включить vlan.
Флаг интерфейса vlan, при этом значении mtu пустой.
При этом vlan создаются на интерфейсе bonding, успешно.
На 6.37 vlan создается, но уже с ошибкой - cold not set MTU (6).
Если изменить интерфейс vlan*, с bonding на ether, получим ошибку - Couldn't change interface <vlan*> - device does not exist any more!(8)

__________________________________________________________________________________

Increasing the firmware version, 6.35,6.36,6.37.
it turned out that at 6.36 there is already a problem with l2mtu, it is automatically set to 1496 if you turn off-turn on vlan.
The vlan interface flag empty, with this mtu 1496.
In this case, vlan are created on the bonding interface, successfully.
On 6.37 vlan is created, but with an error — cold not set MTU (6).
If you change the vlan*, interface from bonding to ether, we get an error - Couldn't change interface <vlan*> - device does not exist any more!(8)
Code: Select all
int pr
Flags: D - dynamic, X - disabled, R - running, S - slave 
 #     NAME                                TYPE       ACTUAL-MTU L2MTU  MAX-L2MTU MAC-ADDRESS      
 0  R  Rezerv                              ether            1500  4080            2C:4D:54:
 1  RS ether1                              ether            1500                  A0:36:9F:**:**:19
 2  RS ether2                              ether            1500                  A0:36:9F:**:**:1A
 3  RS ether3                              ether            1500                  A0:36:9F:**:**:1B
 4  RS ether4                              ether            1500                  A0:36:9F:**:**:18
 5  R  bonding1                            bond             1500  1500            A0:36:9F:**:**:19
 6     vlan1                               vlan             1500  1496            A0:36:9F:**:**:19
 7  R  vlan2                               vlan             1500                  A0:36:9F:**:**:19
 8     vlan3                               vlan             1500  1496            A0:36:9F:**:**:19
Last edited by Muator on Thu Jan 24, 2019 7:07 pm, edited 1 time in total.
Top
 
Muator
just joined
Topic Author
Posts: 22
Joined: Tue Jun 14, 2011 6:26 pm

Re: 6.43.8 l2mtu bonding x86

Thu Jan 24, 2019 7:05 pm

Проверил какое l2mtu будет на "железном" микротике 6.42.9.
______________________________________________________

Checked what l2mtu will be on the "iron" mikrotik 6.42.9.
Code: Select all
/interface bonding
add link-monitoring=none mode=802.3ad name=bonding1 slaves=ether3,ether2
/interface vlan
add interface=bonding1 name=vlan17 vlan-id=17
Code: Select all
 
Flags: D - dynamic, X - disabled, R - running, S - slave 
 #     NAME                                TYPE       ACTUAL-MTU L2MTU  MAX-L2MTU MAC-ADDRESS      
 0     ether1                              ether            1500  1598       4074 CC:2D:E0:**:**:9B
 1   S ether2                              ether            1500  1598       4074 CC:2D:E0:**:**:9D
 2   S ether3                              ether            1500  1598       4074 CC:2D:E0:**:**:9D
 3     ether4                              ether            1500  1598       4074 CC:2D:E0:**:**:9E
 4  R  ether5                              ether            1500  1598       4074 CC:2D:E0:**:**:9F
 5     sfp1                                ether            1500  1600       4076 CC:2D:E0:
 6     bonding1                            bond             1500  1598            CC:2D:E0:**:**:9D
10     vlan17                              vlan             1500  1594            CC:2D:E0:**:**:9D
Top
 
Muator
just joined
Topic Author
Posts: 22
Joined: Tue Jun 14, 2011 6:26 pm

Re: 6.43.8 l2mtu bonding x86

Thu Jan 24, 2019 9:57 pm

Perhaps the reason is as follows:
Mikrotik can not recognize the l2mtu network card.
The same situation with the 10G cards Intel 82599EB, l2mtu set parameter 0.
____________________________________________
Возможно причина в следующем:
Mikrotik не может узнать l2mtu сетевой карты.
Такая же ситуация с 10Г картами интел 82599EB, l2mtu установленный параметр 0.

ether1-4 intel i350-t4
ether5-6 intel 82571EB
bonding1 ether5 and ether6 - no problem, it works correctly.
Code: Select all
int print                        
Flags: D - dynamic, X - disabled, R - running, S - slave 
 #     NAME                                TYPE       ACTUAL-MTU L2MTU  MAX-L2MTU MAC-ADDRESS      
 0  R  ether1                              ether            1500                  A0:36:9F:**:**:18
 1  R  ether2                              ether            1500                  A0:36:9F:**:**:19
 2  R  ether3                              ether            1500                  A0:36:9F:**:**:1A
 3  R  ether4                              ether            1500                  A0:36:9F:**:**:1B
 4  RS ether5                              ether            1500  9014            00:15:17:**:**:A6
 5  RS ether6                              ether            1500  9014            00:15:17:**:**:A6
 6  R  bonding1                            bond             1500  9014            00:15:17:**:**:A6
 7  R  vlan1                               vlan             1500  9010            00:15:17:**:**:A6
 8  R  vlan2                               vlan             1500  9010            00:15:17:**:**:A6
 9  R  vlan3                               vlan             1500  9010            00:15:17:**:**:A6
10  R  vlan4                               vlan             1500  9010            00:15:17:**:**:A6
Code: Select all
system resource pci print detail 
 0 device="03:00.1" name="82571EB Gigabit Ethernet Controller (rev: 6)" vendor="Intel Corporation" category="Ethernet controller" vendor-id="0x8086" 
   device-id="0x105e" irq=10 memory=0xF7E20000-0xF7E3FFFF,0xF7E00000-0xF7EFFFFF io=0xE000-0xEFFF 

 1 device="03:00.0" name="82571EB Gigabit Ethernet Controller (rev: 6)" vendor="Intel Corporation" category="Ethernet controller" vendor-id="0x8086" 
   device-id="0x105e" irq=11 memory=0xF7E60000-0xF7E7FFFF,0xF7E40000-0xF7E5FFFF io=0xE020-0xE03F 

 2 device="01:00.3" name="unknown device (rev: 1)" vendor="Intel Corporation" category="Ethernet controller" vendor-id="0x8086" device-id="0x1521" irq=11 
   memory=0xF7900000-0xF7DFFFFF,0xF7D80000-0xF7D83FFF 

 3 device="01:00.2" name="unknown device (rev: 1)" vendor="Intel Corporation" category="Ethernet controller" vendor-id="0x8086" device-id="0x1521" irq=11 
   memory=0xF7A00000-0xF7AFFFFF,0xF7D84000-0xF7D87FFF 

 4 device="01:00.1" name="unknown device (rev: 1)" vendor="Intel Corporation" category="Ethernet controller" vendor-id="0x8086" device-id="0x1521" irq=10 
   memory=0xF7B00000-0xF7BFFFFF,0xF7D88000-0xF7D8BFFF 

 5 device="01:00.0" name="unknown device (rev: 1)" vendor="Intel Corporation" category="Ethernet controller" vendor-id="0x8086" device-id="0x1521" irq=11 
   memory=0xF7C00000-0xF7CFFFFF,0xF7D8C000-0xF7D8FFFF
Top
 
Muator
just joined
Topic Author
Posts: 22
Joined: Tue Jun 14, 2011 6:26 pm

Re: 6.43.8 l2mtu bonding x86

Wed Jan 30, 2019 10:34 pm

support mikrotik answered:
x86 machine drivers not always support L2MTU option in RouterOS.
To overcome your experienced issue, you should set 1504 byte MTU on ethernet interface, then create bonding with no MTU changes and create VLAN interface on bonding with 1500 byte MTU.

The question turns out to be very simply solved.
You must specify mtu on the 1504 ethernet interface.
Checked on the values ​​1504 and 9014.
I installed a new mtu ethernet interfaces, created a bonding, created a vlan on a bonding, l2mtu became -4 from ethernet.
Enable, disable, bonding, vlan, work fine.
Please indicate in the topic title that the issue is resolved.
Thank you very much for the support of the mikrotik.

___________________________________________________________________________
Вопрос оказывается очень просто решается.
Необходимо указать mtu на ethernet интерфейсе 1504.
Проверил, на значениях 1504 и 9014.
Установил новое mtu ethernet интерфейсов, создал бондинг, создал вланы на бондинге, l2mtu стало -4 от ethernet.
Выключал, включал, bonding, vlan, l2mtu четко -4 от ethernet.
Пожалуйста укажите в названии темы что вопрос решен.
Спасибо большое, поддержке микротика.
Top
Post Reply

Who is online

Users browsing this forum: Aska, GoogleOther [Bot], Semrush [Bot] and 202 guests
  4. RouterOS
  5. General