F5F Stay Refreshed Power Users Networks Configurer un routeur LACP/LAG pour connecter à un commutateur

Configurer un routeur LACP/LAG pour connecter à un commutateur

Configurer un routeur LACP/LAG pour connecter à un commutateur

Y
yTatsumi
Member
151
11-06-2016, 01:44 PM
#1
Checked online options but didn’t find the exact setup you described. For your GT-AX11000 connecting to a Zyxel GS1900-16 via LAG, you’d need to know if the switch can detect and manage the LAG traffic. If the router could handle it, the switch should be aware of the connection status and bandwidth usage. With a Zyxel GS1900-16, you’d typically see two 1GBPS ports, which can handle the extra bandwidth if configured properly.
Y
yTatsumi
11-06-2016, 01:44 PM #1

Checked online options but didn’t find the exact setup you described. For your GT-AX11000 connecting to a Zyxel GS1900-16 via LAG, you’d need to know if the switch can detect and manage the LAG traffic. If the router could handle it, the switch should be aware of the connection status and bandwidth usage. With a Zyxel GS1900-16, you’d typically see two 1GBPS ports, which can handle the extra bandwidth if configured properly.

R
RulwenJr
Posting Freak
786
11-06-2016, 04:33 PM
#2
LAG or LACP mainly boosts overall bandwidth for every client, not just one. Many implementations offer redundancy too, but some are fixed and remain ineffective if a link fails—this is the opposite of redundancy, similar to RAID0. Second, outside specific NAS models like Synology and QNAP, LAG must be configured identically on both ends; otherwise performance will suffer significantly. The switch is highlighted as a key feature in its documentation, suggesting it might be possible to arrange it correctly.
R
RulwenJr
11-06-2016, 04:33 PM #2

LAG or LACP mainly boosts overall bandwidth for every client, not just one. Many implementations offer redundancy too, but some are fixed and remain ineffective if a link fails—this is the opposite of redundancy, similar to RAID0. Second, outside specific NAS models like Synology and QNAP, LAG must be configured identically on both ends; otherwise performance will suffer significantly. The switch is highlighted as a key feature in its documentation, suggesting it might be possible to arrange it correctly.

W
117
11-06-2016, 05:49 PM
#3
W
whitecastle200
11-06-2016, 05:49 PM #3

O
onmyo
Junior Member
9
11-08-2016, 02:32 AM
#4
The switch ignores the device type on each port. It doesn’t distinguish between a router and a NAS.
O
onmyo
11-08-2016, 02:32 AM #4

The switch ignores the device type on each port. It doesn’t distinguish between a router and a NAS.

A
AboooDy919
Member
207
11-10-2016, 12:33 PM
#5
It seems you haven't provided a clear question to address. Could you clarify what you're asking?
A
AboooDy919
11-10-2016, 12:33 PM #5

It seems you haven't provided a clear question to address. Could you clarify what you're asking?

K
Kaden4y
Member
191
11-10-2016, 01:12 PM
#6
I provided the solution without making it too easy. The switch doesn’t understand what devices are connected or what they do. So, setting up a LAG to the router is a good move—congratulations! Now you gain extra bandwidth between the switch and the router. If that was the main issue (like inter-vlan routing consuming all available bandwidth), LAG can be beneficial. LAG is simply a utility you can apply wherever needed. Just like any tool, it has its moments and places where it’s unnecessary. However, if you’re facing a problem where network traffic between a device and the rest of the network must exceed the capacity of a single link, LAG might be the right choice. Here are some scenarios where it shines:

1. Your internet speed exceeds 1Gb/s and your router already has a 2.5Gb/s port available.
2. You’re managing VLANs and need to handle more than 1Gb/s of combined traffic across VLANs and LAN-to-WAN.
3. Your NAS can process more than 1Gb/s, and there are enough wireless clients connecting to it.

LAG can boost overall bandwidth between devices like the router, switch, NAS, etc., and often adds a layer of redundancy against cable failures. Whether it makes a difference depends on whether there was originally a bottleneck between those devices. If a cable isn’t reaching its full speed, adding another parallel connection won’t help much.
K
Kaden4y
11-10-2016, 01:12 PM #6

I provided the solution without making it too easy. The switch doesn’t understand what devices are connected or what they do. So, setting up a LAG to the router is a good move—congratulations! Now you gain extra bandwidth between the switch and the router. If that was the main issue (like inter-vlan routing consuming all available bandwidth), LAG can be beneficial. LAG is simply a utility you can apply wherever needed. Just like any tool, it has its moments and places where it’s unnecessary. However, if you’re facing a problem where network traffic between a device and the rest of the network must exceed the capacity of a single link, LAG might be the right choice. Here are some scenarios where it shines:

1. Your internet speed exceeds 1Gb/s and your router already has a 2.5Gb/s port available.
2. You’re managing VLANs and need to handle more than 1Gb/s of combined traffic across VLANs and LAN-to-WAN.
3. Your NAS can process more than 1Gb/s, and there are enough wireless clients connecting to it.

LAG can boost overall bandwidth between devices like the router, switch, NAS, etc., and often adds a layer of redundancy against cable failures. Whether it makes a difference depends on whether there was originally a bottleneck between those devices. If a cable isn’t reaching its full speed, adding another parallel connection won’t help much.