A Socket deployment using Link Aggregation (LAG) with an internal switch may experience high latency and packet loss if the link isn't configured correctly. This issue may be more visible with applications sensitive to latency variations.
- Cato LAG implementation.
- Internal switch not supporting Static LAG or LAG isn't configured.
In LAG implementations, Cato only supports Static LAG as explained in Configuring Link Aggregation for a Socket. LACP is currently not supported.
A LAG misconfiguration can be identified by running the following steps:
Note: Network Analytics will not show latency/packet loss caused by LAG misconfigurations.
- Run a ping test from a device on the LAN to the Socket's LAN IP address. The Socket's IP address is the 'Local IP' of the Native range configured in the Socket's networks page.
- Optionally, the ping test can be run from the Socket's WebUI routing it via the LAN to the switch IP or a host behind the switch.
- If the ping test shows intermittent high latency and/or packet loss, the LAG link may be misconfigured.
- Confirm that both the Cato Socket and the internal switch include the same number of LAG members and the correct ports. All LAG members must be in UP state.
- Confirm that the switch has the LAG feature configured as static LAG. Active or passive LACP isn't supported when connecting to the Cato Socket.
If the switch connected to the Cato Socket supports Link Aggregation, configure LAG in static mode.
If static LAG isn't supported by the switch (e.g. only LACP is supported), then remove LAG configurations from both the switch and the Socket. In this scenario, only one port can be configured for the LAN.