Header Only - DO NOT REMOVE - Extreme Networks

Facing Challange on Configuring LACP ???


Am facing difficulties while configuring LACP on Summit X450 :-
Command which I used in SW :

enable sharing 1 grouping 1-4 algorithm address-based L2 lacp

My question is , Is that mandatory to configure LACP on my Dell Server ? (If yes, How ? )

After entering the lacp commands, i am getting request timeout on my continuous ping( to server).....
Kindly help me out in this as early as possible !!!!!!

15 replies

Userlevel 1
I don't know how you configure LACP on your dell switch but you don't have to configure LACP on the x450. Just leave "LACP" out of the command on the x450 and it will be static.
Yes, you must also build a LAG on your Dell Server as well. How, depends on your OS and/or the NIC drivers on how to do that.
Brad wrote:

Yes, you must also build a LAG on your Dell Server as well. How, depends on your OS and/or the NIC drivers on how to do that.


Actually My X450 is connected to a Storage server ( 4 interface is Active & 4 interface are Passive - all 4 interface have Unique IP address)
Then my storage device is connected to the Server & its works on windows server 2012)
Now, If i try to configure LACP on my switch, I will loose my connectivity & I need your support to eliminate this !!!!!!
Userlevel 6
You can check the link below for setting up NIC teaming.

http://www.netdavidic.com/2013/09/how-to-create-nic-teaming-on-windows.html
Stephen Williams wrote:

You can check the link below for setting up NIC teaming.

http://www.netdavidic.com/2013/09/how-to-create-nic-teaming-on-windows.html

Its really nice & helps me..!!!
Actually My X450 is connected to a Storage server ( 4 interface is Active & 4 interface are Passive - all 4 interface have Unique IP address)
Then my storage device is connected to the Server & its works on windows server 2012)
Now, If i try to configure LACP on my switch, I will loose my connectivity & I need your support to eliminate this !!!!!!
Userlevel 6
Hi Boopathy,

Sharing/Link aggregation using LACP or Static mode should work if configured with one of the options below:
  1. LACP configured on BOTH switch and Server
  2. Static configured on BOTH switch and Server
The mode (LACP or Static) must match on both sides. However, since link aggregation works on outbound you can mix the algorithms like L2, L3, L3_L4 and so on. Even so, its recommended to use the same algorithm for a consistent traffic distribution.

If you enable LACP in the switch, the ports will work only if LACP is enabled on the other side (Server). If LACP does not work you might see a "b" flag in the port stating no traffic is passing through it.

Can you please share the link aggregation (Static or LACP) command used in your Server and also which ports belong to that group?
Henrique wrote:

Hi Boopathy,

Sharing/Link aggregation using LACP or Static mode should work if configured with one of the options below:

  1. LACP configured on BOTH switch and Server
  2. Static configured on BOTH switch and Server
The mode (LACP or Static) must match on both sides. However, since link aggregation works on outbound you can mix the algorithms like L2, L3, L3_L4 and so on. Even so, its recommended to use the same algorithm for a consistent traffic distribution.

If you enable LACP in the switch, the ports will work only if LACP is enabled on the other side (Server). If LACP does not work you might see a "b" flag in the port stating no traffic is passing through it.

Can you please share the link aggregation (Static or LACP) command used in your Server and also which ports belong to that group?

Its really superb..!!! perfect explanation !!!
thanks a lot for your valuable response Mr.Henrique.!!!!
Henrique wrote:

Hi Boopathy,

Sharing/Link aggregation using LACP or Static mode should work if configured with one of the options below:

  1. LACP configured on BOTH switch and Server
  2. Static configured on BOTH switch and Server
The mode (LACP or Static) must match on both sides. However, since link aggregation works on outbound you can mix the algorithms like L2, L3, L3_L4 and so on. Even so, its recommended to use the same algorithm for a consistent traffic distribution.

If you enable LACP in the switch, the ports will work only if LACP is enabled on the other side (Server). If LACP does not work you might see a "b" flag in the port stating no traffic is passing through it.

Can you please share the link aggregation (Static or LACP) command used in your Server and also which ports belong to that group?

Henrique wrote:

Hi Boopathy,

Sharing/Link aggregation using LACP or Static mode should work if configured with one of the options below:

  1. LACP configured on BOTH switch and Server
  2. Static configured on BOTH switch and Server
The mode (LACP or Static) must match on both sides. However, since link aggregation works on outbound you can mix the algorithms like L2, L3, L3_L4 and so on. Even so, its recommended to use the same algorithm for a consistent traffic distribution.

If you enable LACP in the switch, the ports will work only if LACP is enabled on the other side (Server). If LACP does not work you might see a "b" flag in the port stating no traffic is passing through it.

Can you please share the link aggregation (Static or LACP) command used in your Server and also which ports belong to that group?

So , Here we are using storage server on other side.
We are still facing challenge while configuring LACP on Storage side..
Because there is no option like LACP or Teaming in the Storage side.!!!
How to fix this scenario ????
Userlevel 5
Hello Boopathy,

Link aggregation is fairly mature technology. Most any server/storage station have aggregation capabilities of some sort - either static or protocol driven - setup for interop can be a little tricky but most of the function is recognizable even in a product you haven't seen before.
Making this go should not be as difficult as it seems in your case.
Maybe there's something else at work.

(making a few assumptions - then tossing in speculation...) If the 4 active links on your server each have independent IP addresses, aggregating the links doesn't seem to me to be a fit.
It may be that this design doesn't lend itself to link aggregation without more planning.
Mike D wrote:


Hello Boopathy,

Link aggregation is fairly mature technology. Most any server/storage station have aggregation capabilities of some sort - either static or protocol driven - setup for interop can be a little tricky but most of the function is recognizable even in a product you haven't seen before.
Making this go should not be as difficult as it seems in your case.
Maybe there's something else at work.

(making a few assumptions - then tossing in speculation...) If the 4 active links on your server each have independent IP addresses, aggregating the links doesn't seem to me to be a fit.
It may be that this design doesn't lend itself to link aggregation without more planning.

Thanks for your suggestion Mike..!!!
Userlevel 1
Boopathy, It might be helpful to know what type of Dell Storage you have.
Userlevel 6
Hi Boopathy, first thing here is to check which Link Aggregation type (Static or LACP/802.3ad) is supported by your Dell Server / NIC model:
  • If that supports only Static, then you should use EXOS command without "lacp" word.
  • If that supports only LACP/802.3ad, then you should use EXOS command "lacp".
  • if that supports both, I would recommend to try LACP first, then static.
Another important point is related to the # of ports with sharing enabled. Based on the diagram you have 8 ports for X450 and 8 ports (4 active + 4 passive) for Dell Storage. I'm not sure how those active/passive ports work on Dell Server but I would check the following:
  • If those 8 EXOS ports and 8 Dell Storage Server ports (even being active/passive) belong to the same VLAN/LAG, then those 8 ports should be included in the same LAG:
For EXOS: enable sharing 1 grouping 1-8 algorithm address-based L2 lacp

For Dell Storage Server: Please check any information like Sharing Group, LAG, LACP, 802.3ad and so on and create the group accordingly.

After configuring the sharing on both EXOS and Server you can use the command show ports sharing and check if there is an "Y" in the "Agg Mbr" column to check if the sharing for that particular port is working.

If possible, as already requested by Darren, please share the Dell Storage Server / NIC model you have in that solution.
Henrique wrote:

Hi Boopathy, first thing here is to check which Link Aggregation type (Static or LACP/802.3ad) is supported by your Dell Server / NIC model:

  • If that supports only Static, then you should use EXOS command without "lacp" word.
  • If that supports only LACP/802.3ad, then you should use EXOS command "lacp".
  • if that supports both, I would recommend to try LACP first, then static.
Another important point is related to the # of ports with sharing enabled. Based on the diagram you have 8 ports for X450 and 8 ports (4 active + 4 passive) for Dell Storage. I'm not sure how those active/passive ports work on Dell Server but I would check the following:
  • If those 8 EXOS ports and 8 Dell Storage Server ports (even being active/passive) belong to the same VLAN/LAG, then those 8 ports should be included in the same LAG:
For EXOS: enable sharing 1 grouping 1-8 algorithm address-based L2 lacp

For Dell Storage Server: Please check any information like Sharing Group, LAG, LACP, 802.3ad and so on and create the group accordingly.

After configuring the sharing on both EXOS and Server you can use the command show ports sharing and check if there is an "Y" in the "Agg Mbr" column to check if the sharing for that particular port is working.

If possible, as already requested by Darren, please share the Dell Storage Server / NIC model you have in that solution.

Thanks Henrique, Its really helps me..!!!

Reply