I suppose you might be right, but I was just wondering if there is a practical way to test if the 2Gbps uplink is actually working. I would enable loopback-detection on your LAG group (on HP, as it is smarter, than easysmart), so I would see, if LAG doesn't work. Trunk is an old name of link aggregation came from cisco firstly, then trunk became 'tagged link', but it is OK, that some vendors still use Trunk as Link Aggregation/Etherchannel. If it didn't work, you would receive loop. I don't see any critical issues that should happen when there's a loop, but I also am not sure if I have the 2Gbps uplink between both switches using this configuration.Īditionally, this is some of the statistics that I could gather from both switches, with a few seconds of delay (~5) between the HPE switch/ports and the statistics in the TP-Link ones: Thei idea is essentially to create a 2Gbps uplink instead of a single 1Gbps uplink, I'm considering expanding it to at least 4Gbps if this works, but how can I be sure it is working?

On the TP-Link I've created a Static LAG (LAG 1) using ports 15 and 17, then on the HPE Procurve I've created a Trunk Membership (Trunk T1) (Aggregation Mode: SMAC XOR DMAC) using ports 16 and 18 port 1516 and port 1718. The TL-SG1024DE switch doesn't seem to have any LACP settings, so that seems to be a dead end, but the Trunk Membership - is it possible that it achieves the same funcionality as Static LAG? While the TL-SG1024DE has the simple Static LAG setting page, the Procurve has other naming schemes that might mean the same thing or not, for example:

I want to create a LAG between both but I am unsure if it can work at all. I have two managed switches, one is a TP-Link TL-SG1024DE, the other is an HPE Procruve J9028B (1800-24G).

I know that this question is a stretch, but if someone could drop a hint I would be very grateful.

Software lag switch 1.0