Description | This article describes a possible cause associated with disconnecting and rebooting FortiAP units and its solution. |
Scope | FortiAP and FortiGate units acting as wireless controllers upgraded from FortiOS 6.2.1 and older to FortiOS 6.2.2 and newer. |
Solution |
When a FortiGate unit acting as a wireless controller is upgraded from FortiOS 6.2.1 or older to FortiOS 6.2.2 or newer, the associated FortiAP units might start to randomly disconnect and eventually reboot. By doing so, log entries with action "ap-leave" and reason "AP fsm stuck" or "AP DTLS peer disconnected" will appear, as shown in the examples below:
And/or:
type="event" subtype="wireless" level="notice" action="ap-leave" msg="AP <AP_NAME> left." logdesc="Physical AP leave" sn="<AP_SERIAL_NUMBER>" ip=<IP_ADDRESS> reason="AP DTLS peer disconnected" profile="<WTP_PROFILE_NAME>"
Starting with FortiOS 6.2.2 and above, newly created FortiAP profiles will enable LLDP by default. However, FortiAP profiles created while running FortiOS 6.2.1 or older versions will have LLDP disabled. When upgrading to FortiOS 6.2.2 or above, the LLDP will continue to be disabled, as shown below:
Related documents: FortiOS 7.6.0 CLI Reference - config wireless-controller wtp-profile |