Hardware Controller (Built-in Omada SDN Controller V5.15.6.25) Pre-release

Hardware Controller (Built-in Omada SDN Controller V5.15.6.25) Pre-release

Hardware Controller (Built-in Omada SDN Controller V5.15.6.25) Pre-release
Hardware Controller (Built-in Omada SDN Controller V5.15.6.25) Pre-release
Wednesday - last edited Wednesday
Model: OC200   OC300   OC400  
Hardware Version:
Firmware Version:

 

 

This Article Applies to

OC200(UN)_V1_1.33.5_pre-release (Built-in Omada SDN Controller 5.15.6.25)

OC200(UN)_V2_2.18.5_pre-release (Built-in Omada SDN Controller 5.15.6.25)

OC300(UN)_V1_1.27.5_pre-release (Built-in Omada SDN Controller 5.15.6.25)

OC400(UN)_V1_1.5.5_pre-release (Built-in Omada SDN Controller 5.15.6.25)

 

Overview

 

We hope to offer you a chance to experience the new features added in the Controller v5.15.6.25 in advance, and also give us TP-Link the opportunity to fully test the firmware in your real network environment and scenarios before the official release. All feedback is welcome, including letting us know about successful upgrades.

 

Upgrade Note(for OC200 & OC300 with Built-in Controller v5.13 and older)

 

You can use the following 2 methods to upgrade to this version:

1. Upload Firmware v5.15.6 in Global View > System Settings > Hardware Controller Firmware > Manual Upgrade, and upgrade directly.

2. Check for Upgrade in Global View > System Settings > Hardware Controller Firmware; you will get the latest firmware as v5.14.32. After upgrading to Built-in Controller v5.14.32, you can check for upgrade and upgrade to Built-in Controller v5.15.6.

 

Since version 5.14.32, Omada Controller no longer supports upgrades from Controller v4.

 

Release Notes

 

New Features

1. Added support for gateways: DR3650v, ER703WP-4G-Outdoor.

2. Added support for APs: EAP775-Wall, EAP115-Bridge v2.0, EAP211-Bridge v2.0, EAP215-Bridge v2.0.

3. Added support to disable ports in the properties window of device.

4. Added support for batch import and export of Radius users in Site View > Settings > Network Profile > RADIUS Profile > RADIUS Users.

5. Added support for SAML SSO in Global View > Settings on OC300 & OC400. 

6. Added support to configure DSL Gateway features in Site View > Settings > Wired & Wireless Networks > WAN Mode:

  • Virtual WAN
  • VoIP
  • DSL Dialing
  • TP-Link DDNS

 

Enhancements

1. Optimized WLAN Optimization, added support to deploy Channel Width and Channel.

2. Optimized properties window, added support for Loopback Detection in Device > Properties window > Config > Services > Loopback Control.

3. Optimized the following features in the Omada App:

  • Added support for NTP configuration
  • Added support for Static Routing
  • Optimized properties window of device

 

Notes

1. This version of the Controller is fully applied to the Omada APP of version 4.20 or above.

2. Omada SDN Controller can only manage certain devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.

3. Since version 5.14.32, Omada Software Controller no longer supports upgrade from Controller v4.

 

Firmware Download

 

Before the Upgrade

(1) Please be sure you have read the Beta Test Agreement before upgrading the Pre-release firmware!

(2) For the sake of insurance, it's always recommended to save a copy of the controller Backup Config file before upgrading or downgrading.

(3) You may follow the following guide to upgrade your Omada Controller. How to Upgrade or Downgrade Omada SDN Controller.

 

Firmware Download Link

 

  • Direct Download

 

OC200(UN)_V1_1.33.5 (pre-release version) > Built-in Omada SDN Controller 5.15.6.25

OC200(UN)_V2_2.18.5 (pre-release version) > Built-in Omada SDN Controller 5.15.6.25

OC300(UN)_V1_1.27.5 (pre-release version) > Built-in Omada SDN Controller 5.15.6.25

OC400(UN)_V1_1.5.5 (pre-release version) > Built-in Omada SDN Controller 5.15.6.25

 

Additional Information

If somehow you encounter an issue during or after the controller upgrade, it's suggested to contact us with the following info:

  • Omada Controller version (previous and current)
  • Device Model(s), Hardware and Firmware versions
  • (if possible) A copy of the Log file and Backup Config file

 

If you decide to downgrade the controller before reporting the issue to TP-Link, it's suggested to save a copy of the current Log file and Backup Config file before you do that, which could help to investigate and address the issue quickly.

 

>> How to get the Log file and Backup Config file for Omada SDN Controller:

  • If your Windows software controller failed to get launched, please locate the controller installation path for the Log file.

  • If it's not a launch issue, you can export the Log file and Backup Config file in the local network.

    • For Omada Controller v5.8 or later version,

      In the Global View, go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file. On the same page, scroll down for Export for Support, click Export Running Logs for desensitized Log file.

    • For Omada Controller v5.6 or v5.7, 

      Go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export  for the Backup Config file. On the same page, scroll down for Export for Support, click Export Running Logs for desensitized Log file.

    • For Omada Controller v5.5 or previous version,

      Go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file . Go to Settings > Services > Export Data > Running Log to export the Log file.

 

Update Log

 

Dec 18th, 2024:

 

Provide the following controller firmware for early access.

  • OC200(UN)_V1_1.33.5 (pre-release version) > Built-in Omada SDN Controller 5.15.6.25

    OC200(UN)_V2_2.18.5 (pre-release version)  > Built-in Omada SDN Controller 5.15.6.25

    OC300(UN)_V1_1.27.5 (pre-release version) > Built-in Omada SDN Controller 5.15.6.25

    OC400(UN)_V1_1.5.5 (pre-release version) > Built-in Omada SDN Controller 5.15.6.25
     

 

Recommended Threads

 

TP-Link Early Access Program Is Now Available!

Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates

Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!

Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates

  1      
  1      
#1
Options
5 Reply
Re:Hardware Controller (Built-in Omada SDN Controller V5.15.6.25) Pre-release
Wednesday

Upgraded my OC200 V2 and one of my sites and all is working... so far.  

I can not teach anyone anything - I can only make them think - Socrates
  1  
  1  
#2
Options
Re:Hardware Controller (Built-in Omada SDN Controller V5.15.6.25) Pre-release
Wednesday - last edited Wednesday

  @Vincent-TP Just a suggestion. Can you also include the ability to change the color scheme? Green is the default in the new UI but some people may want another color that is pleasing to the eyes. Thank you.

  1  
  1  
#3
Options
Re:Hardware Controller (Built-in Omada SDN Controller V5.15.6.25) Pre-release
Yesterday

Hi  @ceejaybassist 

 

You are welcome to start a vote.

 

How to Submit Requests & Suggestions Effectively

  0  
  0  
#4
Options
Re:Hardware Controller (Built-in Omada SDN Controller V5.15.6.25) Pre-release
Yesterday

  @Vincent-TP Hi Vincent, i've just updated my OC300 without issue and all ok so far. I like the new layout but not 100% sold on the new green colour scheme (i'm sure it will grow on me...) and an option to either go back to Black and white or pick your own colour might have been good to have from the onset....

Lee...

OC300 ER8411 T1600G-52TS V1 TL-SG1218MPE V5 TL-SG608E V6 TL-SG605E V5 EAP225 V3 (x3) EAP225-Outdoor V1 (x2) EAP235-Wall V1 (x2)
  0  
  0  
#5
Options
Re:Hardware Controller (Built-in Omada SDN Controller V5.15.6.25) Pre-release
Yesterday

I'm experiencing one issue...

 

I Updated my OC200 v2 and when you go to 'reconnect' multiple clients the OC200 freezes for 3-4 minutes and can't be managed. 

 

I have many clients that seem to want to connect to FAR AWAY AP's, even with RSSI thresholds enabled, and I have to manually reconnect them until they get decent signal.

  0  
  0  
#6
Options