Hi
Im having a problem that is doing my absolute head in.
I have two U431F-v6.2-build0281
Ive been following this https://docs.fortinet.com/document/fortiap/7.0.4/fortiwifi-and-fortiap-configuration-guide/124271/co...
Everything is fine up to changing the type, add ssid and passwd then reboot, either via the cli or gui
When I connect via the console to see whats going on .. it seems to have dropped all of its configuration around the profile, so im assuming it will never connect
When i do things like
cw_diag -c mesh
cw_diag -c radio-cfg
all the config is back to default.
Even when checking the date, apparently its 1970 Jan 1
Im fairly new tho this but for the life of me, no matter what I do, I cant even get this to remotely work.
I have to factor reset it, physically plug it back into fortigate and mess around.
Any direction that i could be pointed in would be fantastic.
SCT
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.
Hello REDSCT,
Thank you for using the Community Forum.
I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.
Regards,
Hello,
If I may ask you, I see that the release you are using is 6.2 and the guide is for 7.0.4.
Did you try to upgrade your two FortiAPs?
Regards,
Hi Anthony
I probally should have mentioned all the models
The 2 x APs are FortiAP U431F on version - PU431F-v6.2-build0281
My Fortinet60F is on version FortiOS v7.0.3 build0237 (GA)
I have read both versions of the guide and they seem very similar.
When I line up the support matrix hopefully im on the correct versions. I noticed the U Models dont go past 6.2
The non U models seem to go up to 7.0.2. Im guessing this is the incorrect firmware version for my model.
Thanks
Hi Anthony, any updates? thanks
Hello REDSCT,
Please refer to the below link:
Regards,
Rahul Mittal
Thanks for the link
I've noticed a few things that might affect it. So ill make these changes
I dont have broadcast SSID on, I didnt think it would affect it but will turn it on
I used Radio1 as my mesh, I thought I saw that somewhere in the documentation.
I didnt set an IP via the commandline
Im assuming the : are a typo?
cfg -a MESH_AP_TYPE:=1
cfg -a MESH_AP_SSID:=MESH
cfg -a MESH_AP_PASSWD:= test1234
Ill also udate the fortios and fortiap firmwares to 7.2 fortiOS and 6.2.4 for the U431 AP and see if that helps any
Thanks again
Hi REDSCT,
You can use any radio for the mesh setup, Only thing to make sure is both ap's are able to see each other.
Thanks for highlighting the missed detail:
I have corrected that now.
it should be like below:
cfg -a MESH_AP_TYPE=1
cfg -a MESH_AP_SSID=MESH
cfg -a MESH_AP_PASSWD=test1234
Regards,
Rahul Mittal
Created on 07-19-2022 04:10 PM Edited on 07-20-2022 03:55 AM
Hi
Im not sure what has fixed it, but it seems to be sorted.
Not sure if it was
- Firmware update
- Broadcast SSID is now on
- Separate AP Profile, I was just using the default for both
Whatever it was, it seems to be ok now.
Thanks for the assistance, I might try and isolate it later on.
The broadcast SSID is the more annoying one as I dont want this to pop up on peoples devices, but ill have a play around, its not a big deal.
Thanks again for the help
SCT
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 |
---|---|
1703 | |
1092 | |
752 | |
446 | |
229 |
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.