Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
cjackson_ncl
New Contributor III

FortiAP Firmware to fix bug ID 1060165

Hello,

 

Is there any way of determining whether there will be a FortiAP v 7.4.x release that fixes bug ID 1060165: The FAP-231G/233G/234G 2.4GHz radio would stop SSID beaconing?

 

I know there is a 7.6.2 fix for this, however it requires FortiOS 7.6.3 to ensure compatibility and I'm not confortable to push that FortiOS release out yet to production FortiGates.

 

Thanks,

NSE4
NSE4
1 Solution
atakannatak
Contributor II

Hi @cjackson_ncl ,

 

The release notes confirm that bug 1060165 is fixed only in the 7.6 code line. Fortinet therefore expects FortiGate controllers to run the matching 7.6.3 firmware for full FortiAP support. If a future 7.4.x maintenance build lists 1060165 under resolved issues, that will signal an official back-port. Until then, you have two options:

 

  1. Stay on your current FortiOS version and open a TAC case to request a hot-patch or back-port.
  2. Plan to upgrade both FortiGate and FortiAP to the 7.6.x bundle when feasible.

https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/995071fd-302b-11f0-a9d0-d2b0d2...

 

Beyond the official documents, there is no public source to track this bug’s status. You can open a TAC case for support, but TAC will likely point out that the fix is already available in the specified firmware version and recommend upgrading. Still, it’s worth opening a case—you may at least receive confirmation.

 

Keep in mind that a back-port is not guaranteed—Fortinet may have technical reasons for limiting the fix to 7.6.x.

 

BR.

 

If my answer provided a solution for you, please mark the reply as solved it so that others can get it easily while searching for similar scenarios.

 

CCIE #68781

Atakan Atak

View solution in original post

Atakan Atak
1 REPLY 1
atakannatak
Contributor II

Hi @cjackson_ncl ,

 

The release notes confirm that bug 1060165 is fixed only in the 7.6 code line. Fortinet therefore expects FortiGate controllers to run the matching 7.6.3 firmware for full FortiAP support. If a future 7.4.x maintenance build lists 1060165 under resolved issues, that will signal an official back-port. Until then, you have two options:

 

  1. Stay on your current FortiOS version and open a TAC case to request a hot-patch or back-port.
  2. Plan to upgrade both FortiGate and FortiAP to the 7.6.x bundle when feasible.

https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/995071fd-302b-11f0-a9d0-d2b0d2...

 

Beyond the official documents, there is no public source to track this bug’s status. You can open a TAC case for support, but TAC will likely point out that the fix is already available in the specified firmware version and recommend upgrading. Still, it’s worth opening a case—you may at least receive confirmation.

 

Keep in mind that a back-port is not guaranteed—Fortinet may have technical reasons for limiting the fix to 7.6.x.

 

BR.

 

If my answer provided a solution for you, please mark the reply as solved it so that others can get it easily while searching for similar scenarios.

 

CCIE #68781

Atakan Atak
Atakan Atak
Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors