245v3 firmware 5.0.3 failing and getting disconnected
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi
I have 4 EAP245 v3 that got upgraded to 5.0.3. My controller is version 4.4.3. For some reason the devices get disconnected and after resetting and try to adopt them doesn't seem to work for all of them, always one fails. I tried to reboot them and them one disappeared and 2 got disconnected. Now I have just one as connected.
I tried to check for version 5.0.3 at the download site and I didn't find it.
Not sure what to do next?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
You could try downgrading them again to 5.0.2 and see if the issue disappears?
Could be a new issue in that firmware, however I have upgraded also and not experienced this on the 245s I manage
Also when you reset them, did you forget the device from the controller? Has the controller been rebooted recently?
- Copy Link
- Report Inappropriate Content
I also have 3 EAP's that got upgraded to 5.0.3 yesterday afternoon and can't find any information on it. What is fixed in this version ?
I am running 4.4.3 of the software based SDN.
I don't know if it's related but last night I started experiencing "IP Address failures" when devices were trying to connect to two my of VLANS. Nothing had been changed and the configs looked fine. I checked the devices on the controller and many had "---" for an IP address. Forcing a reconnect and rebooting the EAP's, switch and router did nothing. One device that had an IP address showed it as being "255.255.255.2" and another on the same vlan showed "169.254.136.34" on a vlan subnet of 192.168.50.1/24.
I ended up having to restore an SDN backup to resolve the issue.
I also have the TL-SG2008P switch running : 1.0.1 Build 20210407 Rel.54710 and the TL-R605 router running : 1.1.1 Build 20210723 Rel.64608
- Copy Link
- Report Inappropriate Content
So,
I tried to forget the ones that were disconnected but they failed.
Now, although I have reset them using the button on the device, they are not appearing back.
It looks like they are somehow in the database and getting adopted but not showing up. The led on the device seems normal green not yellowish green.
I'll try to restore a backup and see what happens. Any other idea is welcome
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Try manually logging into the AP while its not adopted and do the downgrade from there.
I have seen that warning before when downgrading via the controller and that was how i got by it
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
My controller auto-upgraded one AP and left the other at 5.0.2, so I found the following release notes:
====
This firmware fully adapts the Omada SDN platform but only compatible with Omada Controller v4.1.5 or above.
New Feature/Enhancement:
1. Add automatic Tx Power deployment function.
2. Add the feature that when using Migration moving EAP to a invalid IP address of Omada Controller, the EAP will roll back.
3. Add support for displaying CPU utilization, memory utilization, and bandwidth-related configuration in the Standalone mode of the Omada APP.
4. Optimize the problem that sometimes EAP resets with an unstable power supply.
Bug fixed:
1. Fixed the bug that sometimes EAP doesn't send broadcast packets when working with some printers.
2. Fixed the bug that after changing the bandwidth of the 5G band, the acquired channel list remains unchanged in the Standalone mode of the Omada APP.
3. Fixed the bug that the client list and block list cannot display icons of Huawei, Samsung or some other Android phones in the Standalone mode of the Omada APP.
Notes
1. For EAP245 v3 only.
2. This version of firmware is applied to the Omada APP of version 3.2.3x or above.
- Copy Link
- Report Inappropriate Content
dcmleung wrote
My controller auto-upgraded one AP and left the other at 5.0.2, so I found the following release notes:
====
This firmware fully adapts the Omada SDN platform but only compatible with Omada Controller v4.1.5 or above.
New Feature/Enhancement:
1. Add automatic Tx Power deployment function.
2. Add the feature that when using Migration moving EAP to a invalid IP address of Omada Controller, the EAP will roll back.
3. Add support for displaying CPU utilization, memory utilization, and bandwidth-related configuration in the Standalone mode of the Omada APP.
4. Optimize the problem that sometimes EAP resets with an unstable power supply.
Bug fixed:
1. Fixed the bug that sometimes EAP doesn't send broadcast packets when working with some printers.
2. Fixed the bug that after changing the bandwidth of the 5G band, the acquired channel list remains unchanged in the Standalone mode of the Omada APP.
3. Fixed the bug that the client list and block list cannot display icons of Huawei, Samsung or some other Android phones in the Standalone mode of the Omada APP.
Notes
1. For EAP245 v3 only.
2. This version of firmware is applied to the Omada APP of version 3.2.3x or above.
I've seen when I got it in the first time. Strange it hasn't appeared to the download site yet, it has been days already. Also, the auto tx power didn't show on the AP for me. It all besides the problems I had after rebooting the AP led to the conclusion it is not 100% ready for u
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1431
Replies: 9
Voters 0
No one has voted for it yet.