Troubleshooting Tip: Unable to establish LAG between FortiSwitch/FortiGate and Meraki
| Description | This article describes a potential issue that may be faced when attempting to create a LAG between a FortiSwitch and Meraki where the Meraki device blocks the ports upon attempting to establish a LAG. This document may also be applicable between FortiGate devices and Meraki devices. |
| Scope | FortiSwitch, FortiGate. |
| Solution | With the default configuration, Meraki does not establish the LAG group if it receives a negotiated PDU with priority greater than itself, and places the ports in a blocking state.
The Meraki unit may log the event: 'LACP has disabled this port'.
By default, Meraki sends an LACP PDU with priority of 32678:
Meraki will not establish the LAG group if it receives a negotiated PDU with priority greater than itself, and will place the ports in blocking state.
This issue may be seen with certain Fortinet devices (e.g., FortiGate 80F) but not others (such as FortiGate 70F) due to hardware and platform-specific LACP negotiation behaviour differences.
Resolution: In the Meraki port or aggregation group settings, change the 'Enforce LACP' setting on the Meraki port side and set the value to 'Disabled'.
Note that this option is typically not available by default and requires Meraki tech support to enable it first.
Related article: |
