Skip to main content
Jannik
Visitor III
August 24, 2026
Solved

ForitAP - AP_MGMT_VLAN_ID variable missing

  • August 24, 2026
  • 4 replies
  • 92 views

I have a strange case with some fortiAPs right now. 1x FAP 231G and 1x431F both on 7.6.4. I want to set a VLAN ID to have the management tagged but the variable is missing when typing cfg -s. Then i connected to the HTTPS GUI and the field is also missing. I typed in the command cfg -a AP_MGMT_VLAN_ID=200 on the CLI and I got no error. cfg -c for commit to flash. Nothing happened. Reboot and still no change, the AP won't take the VLAN ID. I have 100 more 231G on this site and also 20x431F and they all have the variable and it works fine. How is this possible? Anyone else encountering this problem?

    Best answer by ebilcari

    It seems like this is the same post as: 

    Did you check the response? If MESH_AP_TYPE appears as 2, try manually setting it to 0:

    # cfg -a MESH_AP_TYPE=0

     

    4 replies

    ebilcari
    Staff
    ebilcariAnswer
    Staff
    August 24, 2026

    It seems like this is the same post as: 

    Did you check the response? If MESH_AP_TYPE appears as 2, try manually setting it to 0:

    # cfg -a MESH_AP_TYPE=0

     

    Emirjon
    Jannik
    JannikAuthor
    Visitor III
    August 24, 2026

    Interessting. I posted this question on reddit 2 days ago. Apparently someone exactly copied it to the Fortinet community before I posted it here. 

     

    I'll check the variable.

    Jannik
    JannikAuthor
    Visitor III
    August 24, 2026

    Hi, this worked. Thank you very much! What still concerns me is that I never changed anything about that parameter. According to the FortiAP CLI documentation mode 2 is the default value. However all my APs are on 0 since day 1 and I never changed anything about that parameter. It was those 2 APs that were set to 2 without me doing anything. Strange!

    ebilcari
    Staff
    Staff
    August 24, 2026

    Thank you for your feedback. I'm glad to hear that it is working now. This is a misbehavior starting from firmware 7.6.3 and is planned to be fixed in a future release.

    Emirjon