Description This article describes how the FortiLinkd process works on
FortiSwitch and forms the automatic FortiLink inter-switch link trunks.
Scope FortiSwitches 7.2.x and above are Managed by FortiGate. Solution
By default when two Managed FortiSwi...
Description This article describes the Capwap discovery process on a
FortiSwitch managed by FortiGate. Scope Managed FortiSwitch version 7.x
and above. Solution FortiSwitch discovers the FortiGate using CapWap
port 5246 and the Capwap process name re...
Description This article describes the default interface configuration
of the inter-switch link trunk, mclag-icl fortilink trunk and the
FortiGate Fortilink trunk that the FortiSwitch forms automatically in a
Managed FortiSwitch Network. Scope Manage...
Description This article describes the steps to take when an
inter-switch link shows STP discarding, but the expected behavior is the
link should be in a 'forwarding state'. Scope FortiGate and Managed
FortiSwitches version 7.x and above. Solution Re...
Description This article describes steps to take if the DHCPRD process
is high on FortiSwitch. Scope FortiSwitch version 7.2.x and above.
Solution In some cases, the DHCP relay process may spike up to 99.9%
when DHCP snooping is enabled on the VLAN. ...
Hi Dan, it will create STP loops and inconsistency in the network if you
do not configure auto-isl-port-group (as per design). Yes, names should
be the same on both MCLAG-ICL peers. This setting instructs the switches
to group ports from MCLAG peers ...
Hi Dan, We configure auto-isl-port-group when we configure multi tier
mclag setup. For eg. in tier1 and tier2 mclag, we will configure
auto-isl-port-group on tier1 mclag FSWs. In the auto-isl-port-group, we
will add the ports as member that are conne...
Hi, On the tier1 MCLAG ICL FSWs pair, create auto-isl-port-group. We
recommend a criss-cross connection between tier1 and tier2. For example
on tier1 ports used are port1 port2, then config on both tier1 FSWs
should be config switch auto-isl-port-gro...