Unable to establish 802.3ad Dynamic Link between Synology DS918+ and Netgear GS324T Pro Switch

Swapped out my trusty Cisco SG200-8 for a Netgear GS324T and it all went smoothly! However, I have been unable to re-establish the 802.3ad Dynamic Link between my Synology DS918+ and the Netgear GS324T.

I’ve set up LACP on the switch following the steps from the manual and then tried enabling the Dynamic Link on my DS918+ which as I understand it tries to do a “handshake” with the switch – but this fails… (screenshots below) Any ideas what I might have missed?

Thanks in advance, Peter

Model Name: GS324T

Boot Version: B1.0.0.5

Software Version: 1.0.0.27

peterwbaker1100
Sep 03, 2020
First of all “hats off” to Netgear for offering 90 days free support with such a reasonable price switch as the GS324T, had a very useful conversation with them that later led me to the solution! I had not noticed before the DS was going “off air” as soon as I configured the LAG, I’d only notice it was gone after I configured 802.3ad on Synology DSM!

Updated the firmware from V1.0.0.27 to V1.0.0.30, No change in behaviour…

The following worked, at least for me!

Set the GS324T LAG with:
Hash Mode set to “6. Src/Dest IP and TCP/UDP Port Fields” (default is 3)
Leave LAG Type as “Static” (default)
Set “LACP System Priority” to 1 (default is 65535)
Enable 802.3ad network connection in the DS (DSM reports back “Failed to establish IEEE 802.3ad connection”. In red!).

Change the GS324T LAG Type to “LACP”

Return to the DS to find it has established the IEEE 802.3ad connection.

Rebooted everything just to make sure it was not a fluke and for now all is good!

Hope that helps someone else… Peter

6 Replies

schumaku
Guru - Experienced User
Aug 24, 2020
In a 10 seconds check, the LACP LAG config looks OK as far it's visible.

Both GbE links are coming up, the link LEDs become active?

Plugged the ports configured to the LAG? The UI an be confusing because it does show RJ45s for all ports.
- peterwbaker1100
  Tutor
  Aug 24, 2020
  In a 10 seconds check, the LACP LAG config looks OK as far it's visible. <<<Thanks for looking:-)
  
  Both GbE links are coming up, the link LEDs become active? <<< Yes, green lights on Switch and both ports show "active" on the switch web interface and the DS918+, in fact it all works fine I am just trying to get the 802.3ad group working so when my home backups kick off it can use the full 2GB capacity.
  
  Plugged the ports configured to the LAG? The UI an be confusing because it does show RJ45s for all ports. <<<Yes that is a bit confusing but ports 23 & 24 are the ones configure & connected. See attached image.
  
  Something is happening as after try to apply the 802.3ad configuration on the DS918 it fails and then "dissappears" from the network and only way I can get it back is to remove ports 23 & 24 from the LAG configuration and then the DS will revert back to a working Adaptive Load Balancing connection... It is as if the DS trying to establish connection with the Switch is confusing it!
  
  Regards, Peter
  - schumaku
    Guru - Experienced User
    Aug 24, 2020
    Try to configure the LAG with just one port (might have to edit the Syno config manually). This will leave you a backdoor on the second interface just in case to check from the N AS Linux console, e..g (taken from a QNAP, similar on all Linux systems):
    
    [~] # cat /proc/net/bonding/bond*
    Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
    Bonding Mode: IEEE 802.3ad Dynamic link aggregation
    Transmit Hash Policy: layer2+3 (2)
    MII Status: up
    MII Polling Interval (ms): 100
    Up Delay (ms): 0
    Down Delay (ms): 0
    802.3ad info
    LACP rate: slow
    Min links: 0
    Aggregator selection policy (ad_select): stable
    System priority: 65535
    System MAC address: <snip>
    Active Aggregator Info:
    Aggregator ID: 4
    Number of ports: 4
    Actor Key: 9
    Partner Key: 1000
    Partner Mac Address: 10:da:43:<snip>
    Slave Interface: eth0
    MII Status: up
    Speed: 1000 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: <snip>
    Slave queue ID: 0
    Aggregator ID: 4
    Actor Churn State: none
    Partner Churn State: none
    Actor Churned Count: 0
    Partner Churned Count: 0
    details actor lacp pdu:
    system priority: 65535
    system mac address: <snip>
    port key: 9
    port priority: 255
    port number: 1
    port state: 61
    details partner lacp pdu:
    system priority: 32768
    system mac address: <snip>
    oper key: 1000
    port priority: 128
    port number: 1
    port state: 61
    ....