Description This article describes upgrading FortiSwitch-648F from
factory image v7.2.4_build5166 to 7.4.x or 7.2.x from FSW or FGT(Managed
FSW) GUI fails. Scope FortiSwitch 648F, and FortiSwitch 648FPOE running
the factory image. Solution The issue ...
Description This article describes the troubleshooting steps to check
when IGMP snooping is not working as expected. Scope FortiSwitch v6.4.x
and above. Solution Before beginning, it is important to go through the
below links, it contains important i...
Description This article describes how to restore a FortiSwitch after an
RMA. Scope FortiSwitch v6.4.x and above. Solution Upgrade the
FortiSwitch from the GUI. Depending on the FortiSwitch, there may be a
dedicated management port with an IP address...
Description This article describes what to do when it is not possible to
access FortiSwitch GUI using HTTP or HTTPS. Scope FortiSwitch v7.0.x and
v7.2.x. Solution Follow these steps if it is not possible to access the
FortiSwitch GUI despite the corr...
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...