[SOLVED] analysing LAGG

[sobakorova]

Hi,

I'm using v21.7 on a Qotom with a link aggregation to a Synology NAS. I tend to believe that things don't work smoothly as the throughput does not match my expectations. (I'm aware of the single line constraint per client.) I'm now scratching my head how to analyze a LAG - I can't find any tools in the web GUI. Is there some way to inspect what's going on within a bond like the real-time traffic reporting? I've set both sides to 802.3ad.

Thanks!

[ajm]

I'd use tcpdump -i <if> from inside the host, and/or a switch span port and Wireshark.

[lilsense]

Link Aggregation has multiple ways to be configured. This is an Advanced feature when one can select. which one are we trying to troubleshoot?

====
failover
Sends and receives traffic only through the master port. If the master port becomes unavailable, the next active port is used. The first interface added is the master port; any interfaces added after that are used as failover devices.
fec
Supports Cisco EtherChannel. This is a static setup and does not negotiate aggregation with the peer or exchange frames to monitor the link.
lacp
Supports the IEEE 802.3ad Link Aggregation Control Protocol (LACP) and the Marker Protocol. LACP will negotiate a set of aggregable links with the peer in to one or more Link Aggregated Groups. Each LAG is composed of ports of the same speed, set to full-duplex operation. The traffic will be balanced across the ports in the LAG with the greatest total speed, in most cases there will only be one LAG which contains all ports. In the event of changes in physical connectivity, Link Aggregation will quickly converge to a new configuration.
loadbalance
Balances outgoing traffic across the active ports based on hashed protocol header information and accepts incoming traffic from any active port. This is a static setup and does not negotiate aggregation with the peer or exchange frames to monitor the link. The hash includes the Ethernet source and destination address, and, if available, the VLAN tag, and the IP source and destination address.
roundrobin
Distributes outgoing traffic using a round-robin scheduler through all active ports and accepts incoming traffic from any active port.
none
This protocol is intended to do nothing: It disables any traffic without disabling the lagg interface itself.

[sobakorova]

Thanks a lot for your replies, I will give Wireshark a try. (I'm using 802.3ad.)