LACP not working

[winanjaya]

Dear All,

I am running FreeNAS-8.0.4 x64 (10351)
I have 2 onboard NICs and 1 NIC with 4 ports inside..

I want to do LACP for the NIC with 4 ports inside..

I followed the instruction on http://doc.freenas.org/index.php/Link_Aggregations

but still no luck

below what I have done are:

I have created a LAGG virtual interface named lagg0
an Interface created named lagg0 (IP address is: 172.16.0.88/22)
then I created vlan interface named vlan01 and assigned the lagg0 as Parent interface
I setted VLAN tag to 1
then I reboot the system..
but I still unable to ping 172.16.0.88..
could any body please help?

many thanks in advance

Regards
Winanjaya

 

[louisk]

How did you configure your switch?

 

[winanjaya]

Yes, I have configured the switch
and FYI, my switch is TP-Link TL-SG3424

any idea or suggestion?

Thanks & Regards

 

[survive]

Hi winanjaya,

First thing I would do is simplify things by getting the vlan out of the equation.

Clear the config on the filer & reconfigure the interfaces & lagg....do the same on the switch. Does that change the behavior?

-Will

 

[winanjaya]

hmm,
I have reinstall FreeNAS..8.0.4
I do the samething but without creating vlan..
still no luck..
btw, I am using Intel Gigabit VT Quad Port Server Adapter (82575)
and I already put

if_igb_load="YES"

at /boot/loader.conf

any help appreciated..

thanks & regards

 

[winanjaya]

anybody can help me? .. I am stuck ...

thanks

 

[BlastXng]

In your switch are both interfaces set-up for LACP?
If not they both will need to be..

Are you trunking (DOT1Q) to your server?

 

[winanjaya]

yup the ports configured for 802.3ad (LACP)
and no I don't trunking dotq1 (vlan) ..
any suggestion?

 

[BlastXng]

yup the ports configured for 802.3ad (LACP)
and no I don't trunking dotq1 (vlan) ..
any suggestion?

First configure both switch ports for LACP...
Connect only one port..
Verify that it is in LACP mode on both the switch and FreeNAS.. I'm not sure how you'd check this on FreeNAS so I'd default to someone else who might know..
If you see it in LACP mode on the switch, meaning it is talking and negotiating with the server then you'll need to check to see how the switch is configure for use of both interfaces when they are connected.. Also read the FreeNAS document about LACP restrictions that they have. You'll need to align your switch configuration to the LACP that FreeNAS can support..

 

[joz]

Just throwing this out there. I also have been testing the same switch and I have doubts on whether LACP actually functions on it. In LACP mode with my XenServers and FreeNAS the switch would totally lock up after a period of time to the point it would require a power cycle to come back online.
Lockup meaning no port on the switch would work whether using LAG or not. And the admin gui web interface was not accessible.

There is has been a couple firmware releases on it "Improved the LACP function of TL-SG3424."
But others are having issues. [URL]https://forum.pfsense.org/index.php?topic=59328.0

If anyone was able to get that working feedback would be much appreciated.

Update: This was totally my fault, reconfigured switch . I had marked every port as active when really they should have been passive.[/URL]

 

[louisk]

On the FreeNAS side, you should see output that looks similar to the following:
[root@freenas] ~# ifconfig bce0
bce0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c00b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE>
ether 00:22:19:63:18:65
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
[root@freenas] ~# ifconfig bce1
bce1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c00b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE>
ether 00:22:19:63:18:65
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
[root@freenas] ~# ifconfig lagg0
lagg0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c00b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE>
ether 00:22:19:63:18:65
inet 198.18.3.250 netmask 0xffffff00 broadcast 198.18.3.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
status: active
laggproto lacp lagghash l2,l3,l4
laggport: bce1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
laggport: bce0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
[root@freenas] ~#

I don't know what your switch config looks like, but on my Juniper, it looks like the following:
louisk@switch0.cmhome> show configuration interfaces ae1 | display set
set interfaces ae1 description "FreeNAS lagg"
set interfaces ae1 aggregated-ether-options link-speed 1g
set interfaces ae1 aggregated-ether-options lacp passive
set interfaces ae1 aggregated-ether-options lacp periodic slow
set interfaces ae1 unit 0 family ethernet-switching

{master:0}
louisk@switch0.cmhome> show lacp interfaces ae1
Aggregated interface: ae1
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/40 Actor No No Yes Yes Yes Yes Slow Passive
ge-0/0/40 Partner No No Yes Yes Yes Yes Slow Active
ge-0/0/41 Actor No No Yes Yes Yes Yes Slow Passive
ge-0/0/41 Partner No No Yes Yes Yes Yes Slow Active
LACP protocol: Receive State Transmit State Mux State
ge-0/0/40 Current Slow periodic Collecting distributing
ge-0/0/41 Current Slow periodic Collecting distributing

{master:0}
louisk@switch0.cmhome>

Notice that both sides in the equation are showing that they are in a state of "collecting distributing". This means its working.