Both ends are configured manually
A static LAG treats a set of links as one logical interface without LACP or PAgP. Cisco calls this on mode. Both ends need to put the correct physical links in a matching logical bundle and agree on what the bundle carries, such as the VLANs on a trunk.
The local switch can observe a member’s physical link failure. Static aggregation does not negotiate the remote system or member group. A miswired member can look healthy locally even though the far side does not treat it as part of the same bundle. That can cause loss or a forwarding loop.
Try it in a lab
- In a two-switch lab, configure the same two links as a static bundle at both ends. Verify the member list on each switch and send test traffic across the logical link.
- Disconnect one member. Confirm that both ends remove it from forwarding and test connectivity over the remaining member. Compare the verification with an LACP bundle, which also reports partner information.