Solved LAGG interface on 10.1, "Host is down"

S

SmileyBone

I'm having some issues getting a lagg(4) interface (LACP) working on 10.1-RELEASE.
I confirmed that each network card was working independently. I also have a FreeNAS box on same network that has LACP configured, and the switch configuration is the same (as far as I can tell).
I deleted aliases, took network cards down, then followed the instructions listed in https://www.freebsd.org/doc/handbook/network-aggregation.html
But the NICs aren't marked as "ACTIVE", and a lagg ID is not assigned.

ifconfig -v
Code: 
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
   ether XX:XX:XX:XX:XX:a5
   nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
   media: Ethernet autoselect (1000baseT <full-duplex>)
   status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
   ether XX:XX:XX:XX:XX:a5
   nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
   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>
pflog0: flags=100<PROMISC> metric 0 mtu 33160
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
   ether XX:XX:XX:XX:XX:a5
   inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
   nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
   media: Ethernet autoselect
   status: active
   groups: lagg
   laggproto lacp lagghash l2,l3,l4
   lag id: [(0000,00-00-00-00-00-00,0000,0000,0000),
      (0000,00-00-00-00-00-00,0000,0000,0000)]
   laggport: em1 flags=0<> state=4D
     [(8000,XX-XX-XX-XX-XX-A5,00AB,8000,0002),
      (FFFF,00-00-00-00-00-00,0000,FFFF,0000)]
   laggport: em0 flags=0<> state=4D
     [(8000,XX-XX-XX-XX-XX-A5,00AB,8000,0001),
      (FFFF,00-00-00-00-00-00,0000,FFFF,0000)]
And when testing connection:
ping 192.168.1.1
Code: 
PING 192.168.1.1 (192.168.1.1): 56 data bytes
ping: sendto: Host is down
 
Woo! Fixed. Set up lagg(4) group on switch, and tried a different cable. Problem seems to be resolved. Weird though that the cable worked in a single ethernet config but not aggregated.

EDIT: It was the switch
 
Last edited by a moderator:
SmileyBone said:
Woo! Fixed. Set up lagg(4) group on switch, and tried a different cable. Problem seems to be resolved. Weird though that the cable worked in a single ethernet config but not aggregated.

EDIT: It was the switch
Click to expand...

When you say it was the switch, do you mean it was malfunctioning, not compatible, not setup correctly or its programming limitations prevented you from configuring it as needed?

I'm trying to setup a lagg(4) on 9.3_stable using Broadcom 5720's and a Netgear GS724T.v3 and not having any luck. I'm thinking the Netgear may not be configurable enough to make it work. Your thoughts?
 
You must log in or register to reply here.
Back
Top