Hardware controller version 5.6.4 problems
Hardware controller version 5.6.4 problems
I recently updated the OC200 hardware controller to version 5.6.4 and the ER7206 router to firmware version 1.2.3. Since the update, the router is not honoring IP reservations and is not issuing valid IP addresses to clients within each vlan. Some clients are being issued IP addresses that are for vlans other than the vlan that client is connected to.
As a result, the entire network is down and I cannot get anything to work. Is there some setting that needs to be changed after the update? Is this a bad firmware update?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @DannyZ,
DannyZ wrote
I recently updated the OC200 hardware controller to version 5.6.4 and the ER7206 router to firmware version 1.2.3. Since the update, the router is not honoring IP reservations and is not issuing valid IP addresses to clients within each vlan. Some clients are being issued IP addresses that are for vlans other than the vlan that client is connected to.
As a result, the entire network is down and I cannot get anything to work. Is there some setting that needs to be changed after the update? Is this a bad firmware update?
To figure out the issue, please allow me to check the information below.
- What's the previous firmware version of your OC200 hardware controller and the ER7206 router?
- Can you describe or draw your network diagram?
- How did you upgrade the firmware, did you change any settings during that? Did you notice the LED status after the update is completed?
- Is your network recovered now and how did you recover the network? If your network is not recovered so far, what's the LED status of your ER7206 router? Are you willing to do further troubleshooting with our support engineer?
- Copy Link
- Report Inappropriate Content
1. Last working firmware for OC200 is 5.5.7 and the last working firmware for ER7206 is 1.2.1. Updating OC200 to 5.6.4 caused some minor issues but updating ER7206 to 1.2.3 caused major DHCP issues.
2. I have ER7206 leading to two TP-Link switches, each of which lead to multiple EAPs. The OC200 is connected to one of the switches and powered by poe.
3. Both updates were done though the Omada cloud and appeared to complete successfully. I was able to access the controller where it became obvious clients and other TP-Link devices (switches, EAPs) were not getting appropriate IPs. LED status lights appeared to be functioning as expected.
4. First, I manually rolled back the OC200 firmware to 5.5.7 (ER7206 firmware remained at 1.2.3) which did not solve the problem. Next, I factory reset the ER7206, then logged into it directly and downgraded the firmware to 1.2.1 before readopting it to the controller. After several hours of working on it, this seems to resolve the problem for the moment. I just completed this so time will tell.
It seems that the problem was caused specifically by ER7206 firmware version 1.2.3, but I do not want to upgrade the OC200 again yet at the risk of bringing down my entire network.
- Copy Link
- Report Inappropriate Content
i am surprised 1.2.1 was working for you. I saw similar issues (I have only 1 vlan mind you) within 3 days upgrading to 1.2.1 but being on OC200 4.4.6. How long ago have you upgraded to 1.2.1?
- Copy Link
- Report Inappropriate Content
Hello, I also updated to version 5.6.4 3 days ago and have exactly the same problem. All IP reservations are no longer honored.
DHCP devices or clients with fixed IPs work, all others have no connection or cannot connect to the WLAN because the DHCP does not respond.
I don't think DannyZ is an single case.
Thorsten
Addition: I'm running an ER7206 with firmware 1.2.3. But this has been the case for a long time, I only updated the hardware controller (OC300) to 5.6.4 over the weekend.
- Copy Link
- Report Inappropriate Content
I wonder if it could be associated with controller appliance version... I have a few Ubuntu VMs on 5.6.3 and ER7206 1.2.3 and no issues with DHCP reservations.
- Copy Link
- Report Inappropriate Content
@DannyZ a few of us had a similar issue with the 605 release 1.2.1 and TP came out with a minor release to resolve that back when I was running 5.5.7
I am running 5.6.4 on the OC200 and still running 1.2.1 patched on the ER605 and to date, nothing obvious to me yet. But...if they do push an upgrade for the ER605 that has to make me wonder...
I have cameras on my vlan 30 that need reserved IP's and I dont need my recorder losing them in the network because of this. I could probably just go into the cameras and set up a static ip below my DHCP range and be done with it...
But that of course is not the point...and this has been a recurring theme with TP-Link and the way they manage DHCP as well as stateful/stateless ACL.
It is interesting though to hear that more folks with the OC200 have these kinds of issues versus those that are running the controller via software.
- Copy Link
- Report Inappropriate Content
i had static ips set for all devices on the network. The router was not honoring them and instead was issuing random ip addresses out of acceptable range. Multiple devices received the same IPs and nothing was working.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
My IP reservations were not honored either. But you are correct in that if I set static IPs on each individual device (not from the controller/router) then those devices would connect.
It's definitely a DHCP server and IP reservation issue likely associated with ER7206 formware version 1.2.3.
- Copy Link
- Report Inappropriate Content
I been using 1.2.1 since it came out. It's been a long time. Probably a couple months if I had to guess.
after downgrading back to 1.2.1, things are back to working again.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 2185
Replies: 18