Business Community > Controllers > ER7212PC V1 (Built-in Omada SDN Controller 6.0) Pre-release (Released on 22nd Jan, 2026)
< Controllers

Early Access ER7212PC V1 (Built-in Omada SDN Controller 6.0) Pre-release (Released on 22nd Jan, 2026)

1234

Early Access ER7212PC V1 (Built-in Omada SDN Controller 6.0) Pre-release (Released on 22nd Jan, 2026)

38 Reply
Re:ER7212PC V1 (Built-in Omada SDN Controller 6.0) Pre-release (Released on 22nd Jan, 2026)
2 weeks ago

  @Vincent-TP 

 

I'm now having more significant issues, as the SG2008P switch on fw version 3.20.17 Build 20260121 Rel.53429 is not controllable by the ER7212PC's controller and, after a reset, cannot be set up properly at all (doesn't recognise VLANs outside of the default Mgt VLAN, etc) - clients on the switch are given IP addresses from the Mgt VLAN pool rather than their DHCP-reserved ones in the correct VLAN, etc.

 

The release note for the firmware version of the SG2008P switch (version 3.20.17 Build 20260121 Rel.53429) advises that controller version 6.1 be used, but the controller version in ER7212PC firmware version 1.4.1 Build 20260205 Rel.41033 is only 6.0.0.39 - could this be an issue?

  0  
  0  
#33
Options
Re:ER7212PC V1 (Built-in Omada SDN Controller 6.0) Pre-release (Released on 22nd Jan, 2026)
a week ago

  @Vincent-TP Is there a timeline for the release of Controller 6.1 for ER7212PC v1?

  0  
  0  
#34
Options
Re:ER7212PC V1 (Built-in Omada SDN Controller 6.0) Pre-release (Released on 22nd Jan, 2026)
a week ago - last edited a week ago

Hi  @Type17 

Thanks for the feedback.

As you posted two weeks ago, the switches worked well after a reset and re-adopt.

To confirm, when did the new issue first occur? Before it occurs, did you change any settings?

Type17 wrote

  @Vincent-TP 

 

I'm now having more significant issues, as the SG2008P switch on fw version 3.20.17 Build 20260121 Rel.53429 is not controllable by the ER7212PC's controller and, after a reset, cannot be set up properly at all (doesn't recognise VLANs outside of the default Mgt VLAN, etc) - clients on the switch are given IP addresses from the Mgt VLAN pool rather than their DHCP-reserved ones in the correct VLAN, etc.

 

The release note for the firmware version of the SG2008P switch (version 3.20.17 Build 20260121 Rel.53429) advises that controller version 6.1 be used, but the controller version in ER7212PC firmware version 1.4.1 Build 20260205 Rel.41033 is only 6.0.0.39 - could this be an issue?

 

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#35
Options
Re:ER7212PC V1 (Built-in Omada SDN Controller 6.0) Pre-release (Released on 22nd Jan, 2026)
a week ago

  @dragon16z 

Regarding information such as firmware release plans, feature addition schedules, and product lifecycles for various models, unfortunately, the community team does not have access to specific plans in advance. Compared to the official website, we can only learn about whether a firmware version is scheduled for community pre-release about 1-2 weeks earlier. Beyond that, we have no further information. For more detailed updates, we recommend keeping an eye on the official website. I appreciate your understanding.

dragon16z wrote

  @Vincent-TP Is there a timeline for the release of Controller 6.1 for ER7212PC v1?

 

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#36
Options
Re:ER7212PC V1 (Built-in Omada SDN Controller 6.0) Pre-release (Released on 22nd Jan, 2026)
Yesterday

  @Vincent-TP Apologies for the delayed reply, but in the end I ordered and installed an SG2210P to replace the SG2008P, as I also needed more PoE ports for some extra CCTV cameras. (plus, having SFPs on both the router and switch now mean an extra available Ethernet port on both devices)

I had similar issues with the new switch issuing Mgt VLAN IP addresses to any clients plugged into it, or not allowing any DHCP issuing or routing if the ports were changed to one of the non-Mgt VLANs.

A forced provisioning of the Router (ER7212PC, so built-in controller) finally fixed this after a lot of playing about and experimentation - the migration to Controller V6 has not been smooth for me, although the new GUI is a great improvement.

I'm not yet sure about the SG2008P's firmware level, and whether it works with controller version 6.0.0.39, as I have taken it offline for now, and I'm not in the mood to alter anything after the last few days' hassles.

  1  
  1  
#37
Options
Re:ER7212PC V1 (Built-in Omada SDN Controller 6.0) Pre-release (Released on 22nd Jan, 2026)
Yesterday - last edited Yesterday

  @Type17 Despite my post above, I was curious, so I plugged in and adopted the SG2008P, and it failed on all 24 configuration aspects, all with the same error "Device failed to apply configurations. (ErrorCode: switch_100)".

 

In answer to your question in post #35 about what was changed, I first upgraded the Router/Controller to Controller v6.0.0.39 and the switch wasn't behaving well (can't remember the exact issues at this stage). It now looks like if I had forced a re-provision of the Router at that stage, things might have been ok, but it didn't seem logical that forcing a provision on the router would improve the switch's behaviour.

 

To address the switch's issues, I upgraded it to the latest f/w version, but forgot to check whether the exact version of controller v6 was compatible - it looks like the ER7212P's v6.0.0.39 is not compatible with fw version SG2008P(UN)_V3.20_3.20.17 Build 20260121 (it does recommend controller v6.1), as the "Device failed to apply configurations. (ErrorCode: switch_100)" errors are still happening when trying to adopt the SG2008P, despite fixing the issues with the new SG2210P switch by force-provisioning the router/controller.

 

I can't roll back the firmware on the SG2008P (controller can't control it properly), so if I want to use this switch with my current Omada setup, I'll have to wait until the ER7212P's controller version is upgraded to v6.1+

 

PS: The new switch is a h/w version 5.20, loaded with f/w version 5.20.6 Build 20250117 Rel.60471, which only needs controller version 5.14, so it works fine.

  0  
  0  
#38
Options
Re:ER7212PC V1 (Built-in Omada SDN Controller 6.0) Pre-release (Released on 22nd Jan, 2026)
Yesterday - last edited Yesterday

Hi  @Type17 

 

Thanks for the update.

 

Your assumption is correct—such error messages may appear when using newer switch firmware updates on controller 6.0.0.39. However, you should still be able to successfully adopt the device. May I ask if you have successfully adopted the SG2008P in the end?

 

as the "Device failed to apply configurations. (ErrorCode: switch_100)" errors are still happening when trying to adopt the SG2008P, 

>>>Do you have the screenshots of the errors? 

 

Before you trying to adopt the switch this time, did you factory reset the switch SG2008P?

How does it plugged to the ER7212PC?

Type17 wrote

  @Type17 Despite my post above, I was curious, so I plugged in and adopted the SG2008P, and it failed on all 24 configuration aspects, all with the same error "Device failed to apply configurations. (ErrorCode: switch_100)".

 

In answer to your question in post #35 about what was changed, I first upgraded the Router/Controller to Controller v6.0.0.39 and the switch wasn't behaving well (can't remember the exact issues at this stage). It now looks like if I had forced a re-provision of the Router at that stage, things might have been ok, but it didn't seem logical that forcing a provision on the router would improve the switch's behaviour.

 

To address the switch's issues, I upgraded it to the latest f/w version, but forgot to check whether the exact version of controller v6 was compatible - it looks like the ER7212P's v6.0.0.39 is not compatible with fw version SG2008P(UN)_V3.20_3.20.17 Build 20260121 (it does recommend controller v6.1), as the "Device failed to apply configurations. (ErrorCode: switch_100)" errors are still happening when trying to adopt the SG2008P, despite fixing the issues with the new SG2210P switch by force-provisioning the router/controller.

 

I can't roll back the firmware on the SG2008P (controller can't control it properly), so if I want to use this switch with my current Omada setup, I'll have to wait until the ER7212P's controller version is upgraded to v6.1+

 

PS: The new switch is a h/w version 5.20, loaded with f/w version 5.20.6 Build 20250117 Rel.60471, which only needs controller version 5.14, so it works fine.

 

 

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#39
Options
Re:ER7212PC V1 (Built-in Omada SDN Controller 6.0) Pre-release (Released on 22nd Jan, 2026)
Yesterday

  @Vincent-TP Yes, the SG2008P was adopted successfully, despite the configuration result errors but I forgot it/removed it from the network, as the new SG2210P is more suitable for client requirements (40 clients, including 7 PoE ones, 4 EAPs). It will return to service if the network expands further.

 

I did factory reset it, and had also successfully set it running it in standalone mode, although that wasn't going to be suitable as there would have been a lot of additional configuration required.

It was connected to the ER7212PC with a known-good Ethernet cable, and the devices recognized each other and assigned the ports as an uplink.

Before the update to Controller v6, the ER7212PC and SG2008P had worked together flawlessly for a few years.

 

Here's a screenshot of the failed configuration result, although it was adopted:

  0  
  0  
#40
Options
1234
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.