loss of network connection on reboot

[Henning Kessler]

Hello,

I am running a FreeNAS Mini with 11.1-U5 and tried to update 11.1-U6. After the reboot the machine lost its network connectivity (fixed IP, both NICs linked via LACP) I managed to login via Console and deleted the link aggregation interface "lagg0" created it again and then configured the interface as before. After this the network worked fine. I thought the issue maybe could be a problem with the update and booted back to 11.1-U5. On reboot the network connectivity was lost again.

Any idea what is happening here? could this be a problem with an VNET configiured iocage jail that I started to use under 11.1-U5?

here is the current working output of ifconfig

Code:

igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

	options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>

	ether d0:50:99:c3:11:a3

	hwaddr d0:50:99:c3:11:a3

	nd6 options=9<PERFORMNUD,IFDISABLED>

	media: Ethernet autoselect (1000baseT <full-duplex>)

	status: active

igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

	options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>

	ether d0:50:99:c3:11:a3

	hwaddr d0:50:99:c3:11:a4

	nd6 options=9<PERFORMNUD,IFDISABLED>

	media: Ethernet autoselect (1000baseT <full-duplex>)

	status: active

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

	options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>

	inet6 ::1 prefixlen 128

	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3

	inet 127.0.0.1 netmask 0xff000000

	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

	groups: lo

bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

	ether 02:d7:a0:8d:34:00

	nd6 options=9<PERFORMNUD,IFDISABLED>

	groups: bridge

	id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15

	maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200

	root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0

	member: vnet0:2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>

			ifmaxaddr 0 port 6 priority 128 path cost 2000

lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

	options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>

	ether d0:50:99:c3:11:a3

	inet 10.99.10.33 netmask 0xffffff00 broadcast 10.99.10.255

	inet 10.99.10.35 netmask 0xffffff00 broadcast 10.99.10.255

	nd6 options=9<PERFORMNUD,IFDISABLED>

	media: Ethernet autoselect

	status: active

	groups: lagg

	laggproto lacp lagghash l2,l3,l4

	laggport: igb0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>

	laggport: igb1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>

vnet0:2: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

	description: associated with jail: dc01

	options=8<VLAN_MTU>

	ether 02:ff:60:8a:5c:39

	hwaddr 02:26:90:00:06:0a

	nd6 options=1<PERFORMNUD>

	media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)

	status: active

	groups: epair

any help or hint would great.

Henning

 

[Chris Moore]

What is your reason for using LACP? If you don't have a lot of clients accessing the NAS simultaneously, there is no reason to have this configured and it is causing problems. Just use a single network interface.

 

[Henning Kessler]

Hi Chris,

thanks for your suggestion but that Mini actually is in use by a couple of graphic designers. At least 2-3 of them are using it concurrently. It would be great if I could keep up with link-aggregated interfaces ;-).

Regards

Henning

 

[Henning Kessler]

changed the type of link aggregation from LACP to load balance did not help so it seams to be a general link aggregation problem...

 

[Henning Kessler]

okay the problem indeed is solved by deleting the link aggregation and using only a single interface.

But giving up the link aggregation make me sad. I know I could get a 10Gbit Interface but then I would need to get new switches as well and even then link aggregation still make sense when used as failover solution on some stacked switches....

isn't there a different solution?

 

[Chris Moore]

Any idea what is happening here? could this be a problem with an VNET configiured iocage jail that I started to use under 11.1-U5?

You could submit a bug report explaining the details of the situation, perhaps it would prompt the developers to work on this problem.

 

[Henning Kessler]

Hi Chris, I guess you are right. I have converted the VNET jail to a "normal" jail (vnet="off") and deleted the two tunables

Code:

cloned_interfaces="bridge0"
ifconfig_bridge="addm lagg0 up"

and now there are no more network issues after the restart.

 

[Chris Moore]

Hi Chris, I guess you are right. I have converted the VNET jail to a "normal" jail (vnet="off") and deleted the two tunables

Code:

cloned_interfaces="bridge0"
ifconfig_bridge="addm lagg0 up"

and now there are no more network issues after the restart.

There have been problems with using LAG and VNET since 9.3 (or earlier) and I know I was right, that is why I said it.
I tried doing it years ago, had problems getting reliable functionality and I remember looking through the forums for advice at the time. Some things have not been fixed and might never get fixed. If I recall, it is a fault that is inherited from the upstream OS, so if you really wanted it fixed, you would probably need to file a bug report with the FreeBSD project instead of filing one with the FreeNAS team.