|
When there are MCLAG peers on standalone, and to connect a LAG interface to third-party devices (LACP or static LAG), it is necessary to take into consideration some things:
- The LAG interface should have the same name in both MCLAG peers. This is really important because MCLAG peers are going to identify the trunk in the partner FortiSwitch via trunk name.
- Add the command 'set mclag enable' on the LAG interface (trunk), both FortiSwitch. This command enables the synchronization with the MCLAG peers through the ICL trunk. This command is not visible on the GUI interface:
Configuration of 'FSW1':
config switch trunk
edit SWTierdParty
set mode lacp-active
set mclag enable
Configuration of 'FSW2':
config switch trunk
edit SWTierdParty
set mode lacp-active
set mclag enable
It is possible to validate the trunk synchronization between MCLAG peers with the command 'diagnose switch mclag peer-consistency-check'.
diagnose switch mclag peer-consistency-check
Running diagnostic, it may take sometime...
** Comparing "switch.global.mclag-split-brain-detect" config ....OK
** Comparing "switch.global.mclag-split-brain-all-ports-down" config ....OK
mclag-trunk-name peer-config lacp-state stp-state local-ports remote-ports
__________________ ___________ __________ _________ _____________ _____________
SWTierdParty * OK UP OK port23 port24 port23 port24
|
