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)

12345

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

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

  @Vincent-TP 

 

 

Something sinister happened here.

I thought I'd lost access to everything.

The OC200 V1 suddenly got the IP address 192.168.0.100 after I tried to disable a feature on port 3, because the profile I had configured for VLANs no longer works the same way it did before.

I need to understand this better.

After I regained access, I changed it to a different IP address, but it just saved.
Suggestion: When saving this configuration, prompt the user to reboot for it to take effect through a warning.

 

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

Hi  @Artur.Aragao 

 

Thanks for the feedback. Generally, we don't need to reboot controller to make any feature to take effective. To understand the situation better, could you please give us more details? such as, port3 is for from which device? what settings did you try to to save/change?

Artur.Aragao wrote

  @Vincent-TP 

 

 

Something sinister happened here.

I thought I'd lost access to everything.

The OC200 V1 suddenly got the IP address 192.168.0.100 after I tried to disable a feature on port 3, because the profile I had configured for VLANs no longer works the same way it did before.

I need to understand this better.

After I regained access, I changed it to a different IP address, but it just saved.
Suggestion: When saving this configuration, prompt the user to reboot for it to take effect through a warning.

 

 

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

  @Vincent-TP 

 

Vincent-TP wrote

Hi  @Artur.Aragao 

 

Thanks for the feedback. Generally, we don't need to reboot controller to make any feature to take effective. To understand the situation better, could you please give us more details? such as, port3 is for from which device? what settings did you try to to save/change?

Artur.Aragao wrote

  @Vincent-TP 

 

 

Something sinister happened here.

I thought I'd lost access to everything.

The OC200 V1 suddenly got the IP address 192.168.0.100 after I tried to disable a feature on port 3, because the profile I had configured for VLANs no longer works the same way it did before.

I need to understand this better.

After I regained access, I changed it to a different IP address, but it just saved.
Suggestion: When saving this configuration, prompt the user to reboot for it to take effect through a warning.

 

 


 

Well.

I tried disabling a port profile. It seems to have changed how it works. I decided to disable it. However, something went wrong during the process, and I ended up losing access to the controller.

I reset the AP and the Switch to confirm what was happening. And, even with the devices re-adopted, I still couldn't access it.
I had to remove the network cable from port 3, where the port profile was applied.
I plugged it into the router port, and then I was able to access it. I changed the port profile to activate it as it was before. I removed it, put the connections back in as before, and when I tried to access it again, I couldn't.

At that point, I thought there was a more serious problem. But then I did some troubleshooting and realized that the IP had changed to the default IP, with the final octet 100.

It was at this point that when I tried to change it, I noticed that it saved, but it didn't reboot. I saved it again, and it just said it had been saved. Nothing more. So, I decided to reboot, because since it was a pre-release firmware, there could be implementation issues.

After restarting the controller, everything went back to normal.

Look, I really want to thank you for what you did with this firmware. I see in some comments that there's still room for improvement and provisioning more features to be enabled. What you did here was great. It's a shame that the OC200 can't achieve better performance, but the improvements you made in this version 6 are really good. I notice more controlled loading and a few things that are faster.

I'd like an overview of which features were removed and which were changed and added. Especially those that were modified, as I noticed this port profile issue and need to better understand this change and its best use.

A page showing a table with the before and after would be great. So we can delve deeper into this.

Thank you.

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

  @Vincent-TP

 

I almost forgot something I consider very important.

I had reported the Load Balancing feature's functionality in version 5, and at the time, it was reported that it could be a problem with the provider.

 

I noticed a bug report in the release notes for Load Balancing that appears to have been fixed. However, I believe there are still issues with online detection.

 

I'm using this configuration as a test.

In "Load Balancing Weight," I've already tried 1:1 and am now testing 1:10.

However, looking at the next image, we can see that the link is being indicated as offline. This validation algorithm needs improvement. It's not satisfactory.

I need to make a small observation: both links are now offline. The detection timeout is 3 minutes. This is really not good. I hope you can improve this.

 

The link on WAN1 went down and didn't go through to WAN2 after some time, due to the offline detection indication.

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

  @Vincent-TP 

 

Today I decided to delete the backup files that are listed under Global View, Settings, Maintenence, Backup Files List.  Unfortunately, I have been lazy and have not been deleting older files on a regular basis.  Now the list is long and there is no way to batch delete them.  They have to be deleted one by one.

 

I recommend that a Batch Delete function be added similar to that for the log files.

 

1x ER706W 1x OC300 4x SG2008 1x EAP610 2x EAP650
  1  
  1  
#51
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
12 hours ago

  @Vincent-TP 

 

Hi,

 

Are you going to release it for the ER7212PC v1 too ? 

 

Thanks

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

  @Vincent-TP 

37. Added support for overriding default LAN DHCP settings during adoption in Network Config > Network Settings > LAN > Default.

Does this mean that when adopting a router you can leave its DHCP settings (incl. subnet definitions) alone? I.e. You can first set up DHCP in the standalone controller. Then adopt it later and keep its DHCP settings intact?

This would be great to prevent the chicken and egg run-around when cascading routers!

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

Hi  @Artur.Aragao 

Thanks for the feedback.

From the screenshots, the Internet for the two WANs is not affected, only their detection status was abnormally displaying as Offline, is this correct?

 

The link on WAN1 went down and didn't go through to WAN2 after some time, due to the offline detection indication.

>>> How did the link of WAN1 went down? Did you unplug WAN1 for a test? or what else? (I see the link backup was disabled)

Artur.Aragao wrote

  @Vincent-TP

 

I almost forgot something I consider very important.

I had reported the Load Balancing feature's functionality in version 5, and at the time, it was reported that it could be a problem with the provider.

 

I noticed a bug report in the release notes for Load Balancing that appears to have been fixed. However, I believe there are still issues with online detection.

 

I'm using this configuration as a test.

In "Load Balancing Weight," I've already tried 1:1 and am now testing 1:10.

However, looking at the next image, we can see that the link is being indicated as offline. This validation algorithm needs improvement. It's not satisfactory.

I need to make a small observation: both links are now offline. The detection timeout is 3 minutes. This is really not good. I hope you can improve this.

 

The link on WAN1 went down and didn't go through to WAN2 after some time, due to the offline detection indication.

 

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

Hi  @Artur.Aragao 

 

Thank you for your kind words. Listing the changes between V6 and V5 is indeed a good suggestion, but it will take some time. I'll try to work on this.

 

To verify, is this situation similar to what @GRL  shared below:

https://community.tp-link.com/en/business/forum/topic/841724?replyId=1612334

 

Artur.Aragao wrote

  @Vincent-TP 

 

Vincent-TP wrote

Hi  @Artur.Aragao 

 

Thanks for the feedback. Generally, we don't need to reboot controller to make any feature to take effective. To understand the situation better, could you please give us more details? such as, port3 is for from which device? what settings did you try to to save/change?

Artur.Aragao wrote

 

Well.

I tried disabling a port profile. It seems to have changed how it works. I decided to disable it. However, something went wrong during the process, and I ended up losing access to the controller.

I reset the AP and the Switch to confirm what was happening. And, even with the devices re-adopted, I still couldn't access it.
I had to remove the network cable from port 3, where the port profile was applied.
I plugged it into the router port, and then I was able to access it. I changed the port profile to activate it as it was before. I removed it, put the connections back in as before, and when I tried to access it again, I couldn't.

At that point, I thought there was a more serious problem. But then I did some troubleshooting and realized that the IP had changed to the default IP, with the final octet 100.

It was at this point that when I tried to change it, I noticed that it saved, but it didn't reboot. I saved it again, and it just said it had been saved. Nothing more. So, I decided to reboot, because since it was a pre-release firmware, there could be implementation issues.

After restarting the controller, everything went back to normal.

Look, I really want to thank you for what you did with this firmware. I see in some comments that there's still room for improvement and provisioning more features to be enabled. What you did here was great. It's a shame that the OC200 can't achieve better performance, but the improvements you made in this version 6 are really good. I notice more controlled loading and a few things that are faster.

I'd like an overview of which features were removed and which were changed and added. Especially those that were modified, as I noticed this port profile issue and need to better understand this change and its best use.

A page showing a table with the before and after would be great. So we can delve deeper into this.

Thank you.

 

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#55
Options
12345
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.