Created on
07-24-2025
02:24 AM
Edited on
07-24-2025
02:27 AM
By
Jean-Philippe_P
| Description | This article describes the reason for the 'ED' flag on the MCLAG-ICL interface when MCLAG-ICL peers' FortiSwitches are root Bridges. |
| Scope | FortiSwitch version 7.x and above. |
| Solution |
In a multi-tier MC-LAG ICL topology, where Tier-1 FortiSwitch MC-LAG peers act as the STP root bridge, it is observed that the ICL interface shows the 'ED' (Edge) flag, even though the edge port is disabled by default.
Consider the following CLI output:
show switch interface "_FlInK1_ICL0_" end
Despite the edge port being explicitly disabled, the interface '_FlInK1_ICL0_' still shows the ED flag in the STP diagnostic output.
diagnose stp instance list
MST Instance 0 (Common Spanning Tree):
Instance ID 0 (CST) Root MAC 7818ecb9xxxx, Priority 20480, Path Cost 0 Regional Root MAC 7818ecb9xxxx, Priority 20480, Path Cost 0 Port Speed Cost Priority Role State HelloTime Flags
MST Instance 15 (VLAN 4094):
Instance ID 15 Regional Root MAC 7818ecb9xxxx, Priority 20480, Path Cost 0 Port Speed Cost Priority Role State Flags
Explanation of Flags:
Although 'edge-port' is not enabled manually, FortiSwitch’s STP implementation dynamically marks the ICL port as an edge port in some scenarios.
Reasons:
This behaviour is commonly seen when the MC-LAG ICL peers are the STP root bridges.
Related articles: Troubleshooting Tip: MCLAG-ICL interface in STP discarding state |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.