- FortiAP's Profile: The Country on the FortiAP profile should match the region code on FortiAP.
To find the FortiAP region code:
PU231FTH22xxxxxx# fap-get-status
Version: FortiAP-U231F v7.0.4,build0132,240625 (GA)
Serial-Number: PU231FTH2xxxxxxxx
BIOS version: 00000001
System Part-Number: P25813-03
Regcode: E <-----
Base MAC: 84:39:8f:xx:xx:xx
Hostname: PU231FTHxxxxxxxx
Branch point: 0132
Release Version Information: GA
Power-type: PoE 802.3at
FIPS-CC mode: Disabled
To find the region code of countries:
# cw_diag -c all-countries
- Broadcast the SSID to be enabled in SSID configuration:
- The FortiAP profile needs to have a Dedicated scan enabled and SSIDs to be included in the Manual option on each radio.
- Enable Radio 3 as a Dedicated Monitor on the FortiAP profile.
- Check the SSID interface is up on FortiAP CLI:
#vcfg
- Check the SSID's ESSID is in RUN state on FortiAP CLI:
#iwconfig
Here, ESSID 'test222 is in RUN state on interface 'wlan01':
- Check if FortiAP beacons are increasing for the respective SSID on FortiAP CLI:
##apstats -v -i wlan00
#apstats -v -i wlan00 | grep Beacon
(wlan00 is the interface for the SSID as seen in step. 5 via FortiAP CLI command '#iwconfig ').
For example:
FAP # apstats -v -i wlan01 | grep Beacon
Beacon success = 517543
Beacon failed = 21494
IE Overflow count for Tx/Non-Tx VAP Beacon resource overflow = 0
FAP #apstats -v -i wlan01 | grep Beacon
Beacon success = 517898
Beacon failed = 21496
IE Overflow count for Tx/Non-Tx VAP Beacon resource overflow = 0
FAP #apstats -v -i wlan01 | grep Beacon
Beacon success = 518271
Beacon failed = 21501
IE Overflow count for Tx/Non-Tx VAP Beacon resource overflow = 0
FAP#apstats -v -i wlan01 | grep Beacon
Beacon success = 518588
Beacon failed = 21511
IE Overflow count for Tx/Non-Tx VAP Beacon resource overflow = 0
FAP #apstats -v -i wlan01 | grep Beacon
Beacon success = 518949
Beacon failed = 21513
IE Overflow count for Tx/Non-Tx VAP Beacon resource overflow = 0
FAP #
- Check if the FortiAP is getting sufficient power on the CLI :
FAP # wcfg
WTP Configuration
name : FAP
loc : N/A
region map :
pos-x : 0
pos-y : 0
ap mode : thin AP
fmvap : FGT40FTK2309AV7B,(cb1dcdde,baccf395,1),1800,0
atf mode : disabled
VWTP ac conf : dual-5g disabled ddscan disabled
VWTP wtp oper : dual-5g disabled ddscan disabled
poe mode : full(auto)
poe mode oper : full
usb port : enabled
led mode : normal
If the power status appears 'low', as indicated in the output below, check whether the AP is receiving the appropriate power supply according to its FortiAP model requirements (802.3bt / 802.3at / 802.3af).
FAP231F # cw_diag power
Power Detection Data: dc=0 ps1=1 af1=1 at1=0 psv1=0 bt1=0 ps2=0 af2=0 at2=0 psv2=0 bt2=0
Budget lldp 0,0 poe 13,0 (dc=99 af=13 at=25 psv=60 bt=50 full=45.0 low=24.9)
Current Power Mode: low (4) Oper Power Mode: low (4)
Radio 1: MaxTxpower 50 TxChainMask 0x01 RxChainMask 0x01
Radio 2: MaxTxpower 50 TxChainMask 0x10 RxChainMask 0x10
Radio 3: MaxTxpower 0 TxChainMask 0x01 RxChainMask 0x01
USB: disabled
full:usb,txpower full,chain 4; high:txpower 17,chain 4; low:disable all radios
Once the AP receives the required power, the power level should be displayed as 'full', as shown below:
FAP231F # cw_diag power
Power Detection Data: dc=0 ps1=1 af1=1 at1=0 psv1=0 bt1=0 ps2=0 af2=0 at2=0 psv2=0 bt2=0
Budget lldp 25,0 poe 13,0 (dc=99 af=13 at=25 psv=60 bt=50 full=24.9 low=24.9)
Current Power Mode: full (2) Oper Power Mode: full (2)
Radio 1: MaxTxpower 15 TxChainMask 0x03 RxChainMask 0x03
Radio 2: MaxTxpower 21 TxChainMask 0x03 RxChainMask 0x03
Radio 3: MaxTxpower 15 TxChainMask 0x03 RxChainMask 0x03
USB: enabled
full:usb,txpower full; low:txpower 17,disable radio-3
- If the issue persists, then open a TAC ticket with Fortinet technical support.
Related article:
Technical Tip: FortiAPs with external antennas |
