LACP Help required

[aribs]

I am using ASRock C2750D4I which has 3 Ethernet port out which 1 is for ipmi and the other 2 can be used to configure link aggregation. I also have a switch which supports lacp.

The problem is i can get lacp to configure properly on Freenas. I have looked at some of the videos and referred to many forums and I can't get it to work. One of the forum suggested that you run into a lot problems if you only 2 nics. So far i have tried the following:

NIC 1
192.168.1.100/24 primary nic. lacp0 was created and then nic 2 was added as a member of lacp0

NIC 2
192.168.2.101/24 this nic was being used for configuring with static ip configuration. once lacp0 was created and nic 2 became the member i even restarted freenas and it would not take static ip even if it is manually configured it would be unreachable.

I have used the following video as a guide
https://www.youtube.com/watch?v=4d_-JZyvdgw

I also tried to use a video posted by Freenas team Titled something like "link aggregation & vlan" it was ok until the part of lacp but when he talked about vlan he lost me.

Could someone please help me setup LACP on freenas with only 2 nic. and also how to test it after to make sure it working. Please remember that even though i have some knowledge of networking protocols but I still consider myself a beginner.

Thanks in advance!!!

 

[pirateghost]

Let's start with the basics.

Does your switch support LACP? That's going to be important.

Do you actually have enough clients connecting concurrently to benefit from LACP?

The best way to configure LACP is from the console of the FreeNAS. In your case you can just use the ipmi console. Delete all the network addresses and configure your LACP from there.

 

[depasseg]

When you use LACP, the 2 interfaces share an address. You cannot have them in separate network subnets. You can't add an interface to a LAGG and then give it a separate IP address.

Do you have more than 5 heavy duty clients locally and constantly connecting to the FreeNAS. If not, then don't bother with LACP.

 

[aribs]

I do have a compatible switch (GS724T) also I have multiple client who connect to NAS to stream media. I have some jails running like transmission, btsync, Plex and some other that also requires bandwidth.

I have tried configuring from the console in the past and I get the same error on my freenas. This time the ip of freenas is actually timing out in the past it was unreachable.

This is the error I am getting on my freenas

Please advise.

 

[pirateghost]

Is 192.168.3.x a real subnet in your network? You've listed 3 different IP subnets in this one thread.

 

[aribs]

When you use LACP, the 2 interfaces share an address. You cannot have them in separate network subnets. You can't add an interface to a LAGG and then give it a separate IP address.

Do you have more than 5 heavy duty clients locally and constantly connecting to the FreeNAS. If not, then don't bother with LACP.

the reason different ip were used is to configure via web gui. Once the lagg0 was configured the other nic was also deleted and became the member of lagg0. At the end both interfaces were member of lagg0 with only 1 ip. thanks

 

[aribs]

Is 192.168.3.x a real subnet in your network? You've listed 3 different IP subnets in this one thread.

Yes it is, previous ones were just examples. this is my actual network.

 

[pirateghost]

Go to console. Delete any IP addresses and NIC mappings you may have.

Reboot.

Configure the LAGG only and give it an IP address

 

[aribs]

Go to console. Delete any IP addresses and NIC mappings you may have.

Reboot.

Configure the LAGG only and give it an IP address

I believe that is what I did but I'll try it again

 

[aribs]

I believe that is what I did but I'll try it again

Here is what I did
Deleted lagg0 config then rebooted
configured a new lagg0 with 2 available nics then assigned a static ip 192.168.3.140/24
rebooted again
configured switch ports 23 and 24 to be a member of the lagg0

the ping to nas ip still timing out and getting the same error as above I am not sure where I am going wrong I tried this before too many times.

Any other idea??? thanks

 

[pirateghost]

It sounds like your switch doesn't support LACP

 

[aribs]

Go to console. Delete any IP addresses and NIC mappings you may have.

Reboot.

Configure the LAGG only and give it an IP address

Here is what I did
Deleted lagg0 config then rebooted
configured a new lagg0 with 2 available nics then assigned a static ip 192.168.3.140/24
rebooted again
configured switch ports 23 and 24 to be a member of the lagg0

the ping to nas ip still timing out and getting the same error as above I am not sure where I am going wrong I tried this before too many times.

Any other idea??? thanks

 

[aribs]

It sounds like your switch doesn't support LACP

I know that the switch support LACP because I can setup lacp with the switch and I know other users who have used the same switch and configured lacp.

The only thing I can think of now is try adding a new nic and use that to configure. I remember reading somewhere on the forum that there can be issues configuring lacp with only 2 nics.

 

[pirateghost]

I've never had issues with only 2 NICs, but be aware that there are multiple revisions of your switch and some of them do not support LACP and some of them don't support multicast either (found that out the hard way).

Honestly, I have a sneaky suspicion that you will not actually gain anything here. Most people don't and they don't realize that LACP doesn't allow their few clients to pull any more bandwidth.