FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
kaurm
Staff
Staff
Article Id 401513
Description

This article describes how to resolve a scenario where the FortiSwitch 2048F is upgraded to 7.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 the firmware version 7.6.0 to 7.6.2.
  • The FortiGate may be on 7.4.7 or 7.4.8.
  • The topology mapping does not show for the FortiSwitches, but the list view shows all of the connections.


Picture1.png

 

The above image shows the FortiSwitch segregated from the topology.

 

Picture2.png

 

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 the 7.4.8.

 

This issue has been resolved in in FortiOS 7.4.9 and FortiSwitch 7.4.8.

See Technical Tip: Managed FortiSwitch onboarding Troubleshooting Guide.