Business Community > Controllers > Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
< Controllers

Early Access Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)

1456

Early Access Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)

55 Reply
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
Yesterday

  @Artur.Aragao 

 

The key changes in V6 compared to V5 are outlined in the Release Notes. Due to the extensive content, this is currently just a high-level overview. Our teams are progressively releasing supporting materials including: An FAQ list (covering 16 major/impactful features like VLAN, Switch Port, and Air Capture), Video tutorials and Updated User Guides
 Please stay tuned for official updates on our website.

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  2  
  2  
#57
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
Yesterday - last edited 21 hours ago

  @Vincent-TP 

 

Dear friend,

Thank you for always being attentive to our needs.

To explain the situation, the link is indeed not being detected, despite it being active.

What I could confirm was that I first tried disconnecting and reconnecting it through the controller itself in the visual tab, as shown in the image above. However, the connection status, even after some time, remains offline for both WAN1 and WAN2.

I tried turning the network operator routers off and on again, but the status was the same for both WANs. Now, I've tried unplugging and replugging the cable in both network operator routers. Both remain offline.

I'm always waiting for the detection times. As I mentioned, this isn't working satisfactorily in version 6. In version 5, I noticed a similar issue with WAN2. However, disconnecting and reconnecting the cable returned the link to WAN2. However, after a while, it went offline again.

So, clearly, when the connection goes down, I don't have identification and forwarding to the WAN2 link. WAN1 remains active.

With a simple Linux solution, you can get this working perfectly. I hope TP-Link finally manages to fix this properly on the ER605 V2. My firmware is 2.3.0 Build 20250826 Rel.41004.

 

UPDATE
 

I was concerned about the recent tests I performed.

Load balancing isn't working. That's super strange.
I ran a few more tests to check both load balancing and failover. However, neither test worked with my router from the other provider. And in version 5, it worked correctly, despite some errors in online detection.

I think this needs to be thoroughly reviewed.
I ran a small test by changing the ports, and the behavior was the same. I thought at the time that my router might have a DNS issue, but that wasn't the case. Testing with a laptop, I was able to properly measure its performance.

I'll wait for more information.

Later, I'll try to run some more tests, as I've seen reports that this detection could take up to 6 minutes. I consider that time to be extremely long.

 

 

 

  

  0  
  0  
#58
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
23 hours ago

  @Vincent-TP

 

Taking advantage of a detail I noticed, the update search for new beta, release candidate, and stable firmware updates, despite querying TP-Link's database, seems to be finding nothing in the database for the last two months. At least, that's what I noticed when I checked firmware updates that were several weeks old and didn't see any updates identified by the controller as options.

I'd like to understand more details about this here:
To ensure the proper functioning of new device features, please make sure that TCP port 29817 is open and accessible on your network.

  0  
  0  
#59
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
21 hours ago

  @Vincent-TP

 

Other issues I detected:

1- The serial number of the ER605 V2 device is not displayed.

2- Clients appear to still be connected, when they are actually not. This is very strange.

NOTE: And, even stranger is seeing that it indicates a wired connection, when there is only a wireless connection in this case.

 

3- I initially thought it was the latest firmware for the EAP670V1 US (although version EAP670v1_1.3.50_[20250819-rel57463] clearly has signal performance and internet bandwidth issues), but the disconnections don't seem to be caused by this.

Two smartphones are experiencing the same issue. I need to do more testing to better assess this, but I don't recall my smartphone exhibiting this behavior before the update to v6 on the OC200 controller.

I hope I helped.

  0  
  0  
#60
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
18 hours ago - last edited 18 hours ago

  @Vincent-TP 

 

Management scale is Cluster mode - 

 

I have upgraded the controller to FW version V6.0.0 and configured the cluster on the OC300. Under the cluster settings, the following message is displayed:
"Due to performance restrictions of OC300, the management scale will be reduced by half in Hot-Standby Backup mode."

 

However, when we review the Controller Capacity under the controller settings after configuring the cluster, the capacities remain unchanged and reflect the original values, which are:

  • Gateway Capacity: 100

  • Switch Capacity: 100

  • OLT Capacity: 5

  • EAP Capacity: 500

 

Could you kindly clarify the exact meaning of this message? Specifically, we would like to understand in which scenario the management scale will actually be reduced to half. 

 

Your guidance on this matter will help us ensure accurate planning and deployment of the solution.

 

 

 

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