Troubleshooting Tip: FortiSwitches not showing in topology view on FortiGate

[kaurm]

Description	This article describes how to resolve a scenario where the FortiSwitch 2048F is upgraded to v7.6.2, but the topology map is not working on the FortiGate.
Scope	FortiSwitch 2048F and FortiGate 900G.
Solution	In this scenario: The FortiSwitch 2048F was upgraded from firmware versions 7.6.0 to 7.6.2. The FortiGate may be on v7.4.7 or v7.4.8. The topology mapping does not show for the FortiSwitches, but the list view shows all of the connections. The above image shows the FortiSwitch segregated from the topology. Verified from the CLI, the switches can be seen as 'up' upon running the following command: execute switch-controller get-conn-status Sxxxxxxxxxxxx Fortilink interface ... OK LAG enabled DHCP server ... OK LAG enabled WARNING : NTP service for DHCP entry should be set to local mode  NTP server ... OK LAG enabled NTP server sync ... OK Connection: Connected (capwap) A similar scenario was seen once the FortiGate was upgraded to v7.4.8. This issue has been resolved in FortiOS v7.4.9, v7.6.4, and v8.0.,0 and FortiSwitch v7.4.8, v7.6.4. Remember to check the compatibility of FortiSwitch and FortiGate while upgrading.   See this article: Technical Tip: Managed FortiSwitch onboarding Troubleshooting Guide.