bridge0 and bridge1 not active after reboot

[ixuser]

Hello,

I have a set up of 2 Hyper-V servers and a FreeNAS (11.3-U3.2).

FreeNAS has a 1Gbe 4 ports Intel network card (em0 to em3) set up with Jumbo Frames and iSCSI with multipath.

em0 -> vlan0 (tagged 10, MTU 9000)
em1 -> vlan1 (tagged 10, MTU 9000)
em2 -> vlan2 (tagged 20, MTU 9000)
em3 -> vlan3 (tagged 20, MTU 9000)

vlan0 & vlan1 -> bridge0 (MTU 9000, 192.168.1.1/24)
vlan2 & vlan3 -> bridge1 (MTU 9000, 192.168.2.1/24)


This setup works extremely well but after a server reboot, bridge0 shows UP although doesn't work, and bridge1 neither shows UP nor its IP, and I need to delete both bridge interfaces and recreate them manually for the iSCSI service to go back up.

Has anyone experienced this?

Thank you

 

[Samuel Tai]

I believe you're seeing a race condition between the vlan and bridge interfaces being plumbed on startup. There's no easy fix for this, since the GUI doesn't have any mechanism to set the order at which interfaces come up. For another example with LAGG interfaces, see https://www.ixsystems.com/community/threads/lagg-specify-interfaces-in-different-order.85386/. The only means I know of currently to do what you want is to remove the VLAN and bridge configurations from the GUI, and to script everything as a post-init script in the order you need.

 

[ixuser]

I believe you're seeing a race condition between the vlan and bridge interfaces being plumbed on startup. There's no easy fix for this, since the GUI doesn't have any mechanism to set the order at which interfaces come up. For another example with LAGG interfaces, see https://www.ixsystems.com/community/threads/lagg-specify-interfaces-in-different-order.85386/. The only means I know of currently to do what you want is to remove the VLAN and bridge configurations from the GUI, and to script everything as a post-init script in the order you need.

Will do that, thank you.

 

[ixuser]

Ok, I think I solved the problem. There is a bug when setting up the MTU on the VLAN interfaces that will be used on BRIDGES. I thnk the bug is on the python script that generates the interfaces.

To solve this just add a init script (tunable should work too) to change (in order) the MTU values of the physical adapters, vlan interfaces and bridges.

This is mine:

Code:

ifconfig em0 mtu 9000
ifconfig em1 mtu 9000
ifconfig em2 mtu 9000
ifconfig em3 mtu 9000
ifconfig vlan0 mtu 9000
ifconfig vlan1 mtu 9000
ifconfig vlan2 mtu 9000
ifconfig vlan3 mtu 9000
ifconfig bridge0 mtu 9000
ifconfig bridge1 mtu 9000
ifconfig em0 up
ifconfig em1 up
ifconfig em2 up
ifconfig em3 up
ifconfig vlan0 up
ifconfig vlan1 up
ifconfig vlan2 up
ifconfig vlan3 up
ifconfig bridge0 up
ifconfig bridge1 up