Skip to main content
Ahslan
Ahslan
New Member
May 1, 2017
Question

Experience with 5.4.2 firmware on FortiAPs?

  • May 1, 2017
  • 1 reply
  • 10667 views

Curious to see if other people are having a poor experience using the latest 5.4.2 firmware for their FortiAPs. I'm currently running this on FAP-320Cs and it's been a mess for me...clients sometimes can't connect, or if they do, the connection to the internet is horrid. I've actually gone ahead and physically replaced some of the AP's running 5.4.2 with spares that I have on 5.2.4 and they seem to be running better (although definitely too early to tell yet). Curious to see who else is out there running the latest firmware on their APs

    1 reply

    wanglei_FTNT
    Staff
    wanglei_FTNT
    Staff
    May 1, 2017

    1) Actually you can change firmware on the FAP. If you need access to earlier versions, you might need to contact support to get access to that

    2) for the issue you saw on 5.4.2, can you paste wireless related configuration and also a brief description about your deployment?

     

    The whole configuration might contain sensitive info. You can paste output from

    show wireless-controller wtp-profile <the one you use>

    show wireless-controller vap <all the VAPs you use>

     

    Also, you can install a Inssider which comes with free version to quickly assess RF environment

    Ahslan
    AhslanAuthor
    New Member
    May 8, 2017

    1) "5.4.2 does not support downgrading to previous firmware versions" according to the 5.4.2 release notes. Support is currently following up with their devs to find out if there is a way of rolling back but so far, I'm not holding my breath.

     

    2)

    config wireless-controller wtp-profile edit "FAP320C" config platform set type 320C end set ap-country US config radio-1 set band 802.11n,g-only set short-guard-interval enable set auto-power-level enable set auto-power-high 20 set auto-power-low 14 set darrp enable set frequency-handoff enable set vap-all disable set vaps "X" "Y" "Z" set channel "1" "6" "11" end config radio-2 set band 802.11ac set short-guard-interval enable set channel-bonding 80MHz set darrp enable set frequency-handoff enable set vap-all disable set vaps "W" "X" "Y" "Z" set channel "36" "44" "52" "60" "100" "108" "149" "157" end next end

     

    And here are the configurations for each of the SSIDs we use (replaced names and encrypted passphrases):

     

    FW # show wireless-controller vap X config wireless-controller vap edit "X" set vdom "root" set ssid "X" set intra-vap-privacy enable set schedule "7AM-10PM" set passphrase ENC xxxxxxx next end FW # show wireless-controller vap Y config wireless-controller vap edit "Y" set vdom "root" set ssid "Y" set schedule "always" set passphrase ENC xxxxxxx next end FW # show wireless-controller vap W config wireless-controller vap edit "W" set vdom "root" set ssid "W" set broadcast-ssid disable set schedule "always" set passphrase xxxxxxx next end FW # show wireless-controller vap Z config wireless-controller vap edit "Z" set vdom "root" set ssid "Z" set security wpa2-only-enterprise set auth radius set radius-server "radius server" set schedule "always" next end

    tanr
    tanr
    New Member
    May 8, 2017

    My experience with 5.4.2 on the FAP's has been mixed.  I'm running it on a FAP 320C and a 221C.  

     

    Both work well for a while (usually about a month) but then one or the other will have a problem.

     

    The problem manifests as the FAP getting into an odd mode where it is no longer broadcasting any of its SSID's, existing connections slow to a crawl, and it immediately drops any new connections, but reports itself as just fine to the FGT.  A reboot has it working again.

     

    Terms & ConditionsAccessibility statement