Re: FortiAP 7.0.6 tunnel mode SSID sometimes canno...

COA · 07-18-2023

I am using Fortigate-100F(Fortios 7.0.12), but appear below logs every day:Failed to connect FortiManager 173.243.132.61 Central Management connectivity is inactiveTunnel to FortiManager is down Central Management connectivity is inactiveConnected to...

COA · 04-25-2023

FortiOS 7.0.11 (Fortigate 201F HA A-P, SD-WAN with dual WAN)FortiAP 7.0.6 SSID1: Bridge mode, get IP from Windows DHCP Server.SSID2: Tunnel mode, get IP from tunnel interface.SSID3: Tunnel mode, get IP from tunnel interface. After I completed the con...

COA · 08-03-2023

Thank you for the information.Yes, I can see the FortiManager is enabled by default. Regards,Gavin

COA · 08-03-2023

Thank you for the information. Gavin

COA · 08-03-2023

System Event log from Memory:

COA · 07-27-2023

I don't know what is this IP, and I haven't configured central management:

COA · 05-01-2023

Thanks for the update.The end-user using 7.0.4, and it seems to work fine.So they will keep this version at this moment. Thank you again.Gavin

User Statistics

User Activity

After Fortios 7.0, why appear "Failed to connect FortiManager 173.243.132.61" event log in memory?

FortiAP 7.0.6 tunnel mode SSID sometimes cannot get the IP.

Re: After Fortios 7.0, why appear "Failed to connect FortiManager 173.243.132.61" even log

Re: After Fortios 7.0, why appear "Failed to connect FortiManager 173.243.132.61" event lo

Re: After Fortios 7.0, why appear "Failed to connect FortiManager 173.243.132.61" even log

Re: After Fortios 7.0, why appear "Failed to connect FortiManager 173.243.132.61" even log

Re: FortiAP 7.0.6 tunnel mode SSID sometimes cannot get the IP.

Re: FortiAP 7.0.6 tunnel mode SSID sometimes canno...

Re: After Fortios 7.0, why appear "Failed to conne...