ER605 v2 2.1.0 Build 20221230 May Lead into Adopting - Provisioning Loop [Case Closed]

ER605 v2 2.1.0 Build 20221230 May Lead into Adopting - Provisioning Loop [Case Closed]

ER605 v2 2.1.0 Build 20221230 May Lead into Adopting - Provisioning Loop [Case Closed]
ER605 v2 2.1.0 Build 20221230 May Lead into Adopting - Provisioning Loop [Case Closed]
2023-01-16 08:21:50 - last edited 2023-01-31 02:56:20

Updated on Jan 30th 2023:

 

The official firmware 2.1.1 has been released to fix the issue mentioned in this post. 

If you still have the adopting issue with the official firmware 2.1.1, it might be a different case, please don't hesitate to Start a New Thread from HERE. 

To get better assistance from Community, you may check Tips For Efficiently Reporting an Issue In The Community.

 

 

Updated on Jan 18th 2023:

Add the Beta firmware ER605_v2_2.1.0.

Add some notes for the firmware.

Here is the Release note.

 

This Article Applies to:

Omada Controller v5.7 or below

ER605_v2

with FW 2.1.0 Build 20221230

 

 

Issue Description/Phenomenon:

 

Recently we received feedback that after upgrading to ER605 2.1.0 Build 20221230, ER605 will get caught in the loop of adopting- provisioning- configuring under below conditions*, resulting in unstable issue on the network. And this cannot be resolved by rebooting.

 

*Note that the issue above will only occur when both of the following conditions are satisfied:

  • Omada Controller v5.7 or below manage ER605 v2

  • The WAN connection type is PPPOE

 

After further investigation and tests, the TP-Link team located the problem is that when the WAN connection type is PPPoE, the newly added MRU function is not adapted to the controller version (v5.7 and below).

 

Available Solutions:

Case 1:

If you are not satisfied the following conditions, please refer to the Case 2 directly.

  • You can still access the Internet.
  • When Controller and the ER605 are on the same site, you can perform the following steps when you are on site.

 

 

1. Please go to the official website to download the firmware version ER605_V2_2.0.1 Build 20220223.

2. Please change the WAN Connection Type from PPPOE to Dynamic IP on the controller.

Note:  After modification, the network will be disconnected for a period of time, you need to ensure that the controller and router on the same site.

3. After the Controller and Gateway Keep in a stable Connected state, you can downgrade the firmware version of ER605 to 2.0.1 on the Controller, and modify the WAN Connection Type back to PPPoE after the downgrading.

 

Case 2:

If you are no longer able to access the Internet, please follow the steps below:

 

1. Please hardware reset the ER605.

2. You can use the default IP address 192.168.0.1 to login the management page in Standalone mode, and now you can do the Basic Network settings like WAN Connection Type (PPPOE).

Note: If the LAN Network you used previously is not 192.168.0.0/24, it is recommended that you can modify it to original subnet in this moment.

For example: The original LAN network you used is 192.168.10.0/24, we suggest you modify the LAN to 192.168.10.0/24 either in Standalone mode, it will be very helpful to restore the network.

 

3. Please go to the official website to download the firmware version ER605_V2_2.0.1 Build 20220223, and downgrade it in standalone mode.

4. Now you can login the controller, and adopt the ER605.

Note: If the controller’s IP address is obtained from ER605 automatically, it is recommended that you unplug and plug the Ethernet cable between controller and Router/Switch to trigger the DHCP, try to adopt the ER605 after the controller obtained the original IP address(like 192.168.10.X) . Then the adoption process will be easier.

 

 

Updated on Jan 30th 2023:

 

The official firmware 2.1.1 has been released to fix the issue mentioned in this post. 

 

If you still have the adopting issue with the official firmware 2.1.1, it might be a different case, please don't hesitate to Start a New Thread from HERE. 

To get better assistance from Community, you may check Tips For Efficiently Reporting an Issue In The Community.

 

 

Feedback:

 

If your WAN Connection Type is not PPPOE and still have the same issues with the latest firmware above, it might be a different case, please don't hesitate to comment below for further assistance.

 

If this was helpful, welcome to give us Kudos by clicking the upward triangle below.

If there is anything unclear in this solution post, please feel free to comment below.

  13      
  13      
#1
Options
1 Accepted Solution
Re:ER605 v2 2.1.0 Build 20221230 May Lead into Adopting - Provisioning Loop [Case Closed]-Solution
2023-01-30 11:08:52 - last edited 2023-01-30 11:17:12

Updated on Jan 30th 2023:

 

The official firmware 2.1.1 has been released to fix the issue mentioned in this post. 

If you still have the adopting issue with the official firmware 2.1.1, it might be a different case, please don't hesitate to Start a New Thread from HERE. 

To get better assistance from Community, you may check Tips For Efficiently Reporting an Issue In The Community.

Recommended Solution
  0  
  0  
#21
Options
20 Reply
Re:ER605 v2 – New Firmware 2.1.0 May Lead ER605 into Adopting - Provisioning Loop with Controller v5.7
2023-01-16 15:30:18 - last edited 2023-01-16 15:39:27
Hello,
since the update to 2.1.0 the ER605 no longer starts. Even a reset and downgrade to 2.0.1 didn't help.

Only when you disconnect the ER605 from the power supply and after about 1 minute press the reset button does it start up.


I have 3 systems and all the same.

Omada 5.7.6 and 5.7.4

 

  0  
  0  
#2
Options
Re:ER605 v2 – New Firmware 2.1.0 May Lead ER605 into Adopting - Provisioning Loop with Controller v5.7
2023-01-16 22:04:46 - last edited 2023-01-16 22:06:45

  @Hank21 When will be there an newer version of the Omada Controller for Linux?

 

  2  
  2  
#3
Options
Re:ER605 v2 – New Firmware 2.1.0 May Lead ER605 into Adopting - Provisioning Loop with Controller v5.7
2023-01-17 01:52:03

  @Hank21 

 

An event called Router was connected occurs several times a day.

 

This Alert is OC200's Problem? or ER605?

 

OC200

5.7.6

2.7.7 Build 20221206 Rel.58608

ER605 ER605 v2.0 2.1.0 Build 20221230 Rel.55248

 

 

ROUTER was connected.

1月 17, 2023 07:17:52  午前

ROUTER was connected.

1月 17, 2023 07:16:36  午前

ROUTER was connected.

1月 17, 2023 06:13:00  午前

ROUTER was connected.

1月 17, 2023 04:35:52  午前

ROUTER was connected.

1月 17, 2023 03:56:58  午前

ROUTER was connected.

1月 17, 2023 12:48:32  午前

ROUTER was connected.

1月 17, 2023 12:14:32  午前

ROUTER was connected.

1月 17, 2023 12:09:34  午前

 

 

Thank you

 

 

 

  2  
  2  
#4
Options
Re:ER605 v2 – New Firmware 2.1.0 May Lead ER605 into Adopting - Provisioning Loop with Controller v5.7
2023-01-17 04:20:40
Thank you for the solution. But would greatly appreciate for the TP Link business development team to not let this kind of buggy updates be released to business users prior complete and through testing.( scrutinize ) This has shaken my confidence in TP link products as now a series of erroneous update release seems to be a norm Starting with DHCP issues , controller issues and now this. I maintain multiple sites with HW controller on every site and it is very disruptive to the end users (1200 plus) due to down time and also damaging to MSP providers (OUR) reputations and costs us reliability loss and face in the market. I sincerely hope to see this issue non existent in the coming future and continue to Enjoy TP-Link products , services and solutions to our business. Thank you and Kind Regards
  4  
  4  
#5
Options
Re:ER605 v2 – New Firmware 2.1.0 May Lead ER605 into Adopting - Provisioning Loop with Controller v5.7
2023-01-17 04:26:02

  @Kash01976 Be careful, I was banned for calling out TP-Link on this stuff as well.  I didn't break any rules and I wasn't disrespectful.  Don't be surprised if you can't login in a day or two.

  2  
  2  
#6
Options
Re:ER605 v2 – New Firmware 2.1.0 May Lead ER605 into Adopting - Provisioning Loop with Controller v5.7
2023-01-17 04:27:15
Also Please start a beta testing program and if there is one i would love to be a part of it. As i maintain a lab and always procure the latest HW from TP-LINK business line. For Example the new ER7212. i got 5 weeks ago upon launch in DXB. This will help beta testers to provide beneficial feed backs in multiple scenarios. Thank you and Regards
  1  
  1  
#7
Options
Re:ER605 v2 – New Firmware 2.1.0 May Lead ER605 into Adopting - Provisioning Loop with Controller v5.7
2023-01-17 04:31:58

  @Kash01976 Great idea!  I'd totally enroll in a beta program as well to help things progress.

  1  
  1  
#8
Options
Re:ER605 v2 – New Firmware 2.1.0 May Lead ER605 into Adopting - Provisioning Loop with Controller v5.7
2023-01-17 05:57:48

I am currently in the provisioning loop.

WAN is not set to PPPOE. Client had disconnects every 10-15 minutes today. I updated switch firmware and OC200 firmware, and now the constant provisioning is happening. Client is not on-site to see if the internet is working or not.

 

Are we supposed to use the same instructions to fix the issue if it is not PPPOE?

  0  
  0  
#9
Options
Re:ER605 v2 – New Firmware 2.1.0 May Lead ER605 into Adopting - Provisioning Loop with Controller v5.7
2023-01-17 07:20:53

  @Kash01976 @@unhappycust0mer 

I am very sorry, but we all are already on a beta test-platform. With the new firmware you always hope, omada will get better and fix old problems.

They should better make a stable final release-platform!

Guys from techsupport tries their best, but in many cases there is no solution for a long time, we have to live with, or just look for another solution.

 

  4  
  4  
#10
Options
Re:ER605 v2 – New Firmware 2.1.0 May Lead ER605 into Adopting - Provisioning Loop with Controller v5.7
2023-01-17 10:25:40

@Hank21

Thank you! The downgrade of my ER605 v2 to firmware version ER605(UN)_V2_2.0.1 Build 20220223 just worked fine! Looking forward for the next flawless firmware update with all these issues fixed and with mDNS support for the ER605 - hopefully soon wink.

Even if the firmware 2.1.0 Build 20221230 is not available at the support page anymore it gets pulled and proposed by the controller. It might be worth it to have a look on that.

 

@DDI 

It took a good ten minutes or so until the "After the Controller and Gateway Keep in a stable Connected state"-state was reached.

 

 

  1  
  1  
#11
Options

Information

Helpful: 13

Views: 6377

Replies: 20