I recently purchase some FortiAP-433G. I connected them to a Cisco 9200L PoE switch. The AP and switch negociate PoE succesfully at 802.3at, and the switch supplies 30W.
This AP, according to the spec sheets can operate at 802.3at (30W) or 802.3bt (60W)
When creating more than 2 SSIDs on the AP, ir begins to constantly reboot it self.
Has anyone experience this issue as well?
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
What AP firmware are you running? Always run the latest AP code irrespective of the Firewall.
If you have SSH access to the AP, log into it and see if there are any crash logs. use the keyword 'crash' or 'kp' (kernel panic).
If there are no crashes and/or the AP firmware is up to date then it might be something related to the CAPWAP daemon on the Firewall perhaps.
Log a support ticket if needed.
Can you check in AP events if any relevant logs are shown before reboot?
What is the power budget usage in the switch? It may be that the AP is connected to a low PoE priority port that gets cut when a high priority PoE device get's connected. Adding SSIDs should not increase the power usage (radio power) or cause reboots.
Switch has 847w available, 59w in used.
Based on the used power budget of the switch, this issue seems not related to PoE consumption. Is the AP connected using both interfaces (RJ45)? Is this AP managed by a FGT or via FortiLAN Cloud?
Since the AP is running in "Low" mode (802.3at), check if the applied AP profile is not configured to use more than 17dBm in Transmit power.
Hi.
The AP si connected on one port only, so only 30W is supplied.
The AP is managed by a Fortigate.
The transmit power is set to auto (10-17dB)
What AP firmware are you running? Always run the latest AP code irrespective of the Firewall.
If you have SSH access to the AP, log into it and see if there are any crash logs. use the keyword 'crash' or 'kp' (kernel panic).
If there are no crashes and/or the AP firmware is up to date then it might be something related to the CAPWAP daemon on the Firewall perhaps.
Log a support ticket if needed.
AP firmware 7.4.2 (build0634).
- KP log output:
- crashlog output:
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1712 | |
1093 | |
752 | |
447 | |
231 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.