This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
It seems that your goal in setting up LACP is to improve the read/write speeds between PCs, am I right? It seems your concern is similar to this forum link I found online. Kindly access and read it.
Doing an iPerf test would help. Here are the links I found online that you could use as a guide to perform an iPerf test.
but what is the best practice? 1º each switch to router or 2º each switch, in cascade by LAG sw1 ---LAG 2 wired-- sw2 ---LAG 2 wired SW3 -- LAG 2 wired SW4 -- (DC,SQL SERVER 2012,DICOM PACS are in sw 1.
Referring on the diagram below, I believe this is the setup that you wanted to implement wherein Switch A is connected to the firewall router. Then switch B is connected via a LAG connection to Switch A. Then Switch C is connected via a LAG connection to Switch B. Am I right?
If ever I am right, this setup is possible and you may refer on the article I have provided previously on how to set up LAG.
I just want to follow-up on this. Were you able to implement the network set up you wanted that involves LAG configuration? If yes, what are the results?
If you restore the switch to factory defaults, the IP address of it will default back into 192.168.0.239. However, be reminded that DHCP is enabled by default so if you will perform a factory reset while the switch is connected to the existing network, it might get assigned an IP Address from the DHCP server.
For me, it would be best to disconnect the switch from the existing network before doing a factory reset on it then assign a static IP address to it before connecting it back to the existing network.
It seems that you have set up LAG properly between Switches A and B. Based from the screenshots, it would be best if you change the LAG Type from Static to LACP.
Advantages of LACP over Static LAG:
1. Even if one physical links fails, it will detect if the point-to-point connection is using a media converter, so that the link status at the switching port remains up. Because LACPDUs (Link Aggregation Control Protocol Data Units) do not form a component of this connection, the link will be removed from the link aggregate. This ensures that packets will not be lost due to the failed link.
2. Both of the devices can mutually confirm the LAG configuration. With static link aggregation, errors in the configuration or wiring will often not be detected as quickly.
For more details about LAG and the basics of LACP, kindly access this link
We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance.
If your issue is now resolved we encourage you to mark the appropriate reply as the “Accepted Solution” so others can be confident in benefiting from the solution. The Netgear community looks forward to hearing from you and being a helpful resource in the future!
It seems that your goal in setting up LACP is to improve the read/write speeds between PCs, am I right? It seems your concern is similar to this forum link I found online. Kindly access and read it.
Doing an iPerf test would help. Here are the links I found online that you could use as a guide to perform an iPerf test.
