Configuration Incompatiblity

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Configuration Incompatiblity

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Configuration Incompatiblity
Configuration Incompatiblity
2023-05-01 14:41:45 - last edited 2023-05-01 19:56:46
Model: OC200  
Hardware Version: V5
Firmware Version: Version:5.7.6 Build:1.21.7 Build 20221206 Rel.58608

I wanted to move from my software controller, running on Ubuntu 18 to a OC200 hardware controller.
I backed up the configuration from the former to a local file on my laptop:
 

omada_backup_5.9.31_30days_2023-05-01_08-10-37.cfg
(I note that this file is not in plain text ascii.)
 

I shut down the software controller, attached the new hardware OC200, connected to it via the iPhone APP using the device key, and was able to use the web interface to login. When I tried a restore I got an incompatibility message. I updated to software on the OC200 to the most recent version:
 

Version: 5.7.6
Build: 1.21.7 Build 20221206 Rel.58608
 

I tried to restore again as the configuration is version 5.9.31, there was still a compatibility issue. See the attached file.
 

This is a bad situation where one can't migrate from a software controller to a hardware one. The configuration should have a backward compatibility mode etc.

Frustrated.

Russell Sutherland russ@quist.ca
  0      
  0      
#1
Options
1 Accepted Solution
Re:Configuration Incompatiblity-Solution
2023-05-01 17:00:28 - last edited 2023-05-01 19:56:46
Thanks!!! Very helpful. I will try another OC200 upgrade and then the restore. I've got everything back now in terms of config. with the new controller, but I would like to get the logs back as well.
Russell Sutherland russ@quist.ca
Recommended Solution
  0  
  0  
#3
Options
6 Reply
Re:Configuration Incompatiblity
2023-05-01 15:43:45

  @Quist 

 

Hi, seems to be a known issue.  Yes, the backup file is at least compressed, if not encrypted...XML might have been fixable.

 

I suggested here to try a 'Site' migration from like to like, instead of a Controller migration.

 

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

 

It seemed to work (this was in the opposite direction though). 

 

In your case there is new firmware to take the OC200 to 5.9.32 on the forums. 

https://community.tp-link.com/en/business/forum/topic/605964

 

So do that and try again.  If that fails, try a site migration between the OC200 and Ubuntu (you should probably create a new temporary LAN/subnet for the OC200 as you don't want it fighting for control with the existing Ubuntu controller.

 

 

<< Paying it forward, one juicy problem at a time... >>
  3  
  3  
#2
Options
Re:Configuration Incompatiblity-Solution
2023-05-01 17:00:28 - last edited 2023-05-01 19:56:46
Thanks!!! Very helpful. I will try another OC200 upgrade and then the restore. I've got everything back now in terms of config. with the new controller, but I would like to get the logs back as well.
Russell Sutherland russ@quist.ca
Recommended Solution
  0  
  0  
#3
Options
Re:Configuration Incompatiblity
2023-05-01 19:57:05
This method worked. Thanks very much.
Russell Sutherland russ@quist.ca
  0  
  0  
#4
Options
Re:Configuration Incompatiblity
2023-05-01 20:17:33
That's great news Russ! Glad you're up on the OC200. For those that might come later, can you take a second to describe which parts of the suggestion you used, ie was site-site migration needed, or were you able to get controller 5.9 to sync with controller 5.9? Did you use the temp subnet during the migration?
<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#5
Options
Re:Configuration Incompatiblity
2023-05-01 20:24:32
Sure. I had the OC200 running with connections to my 3 TP-Link APs as well as 1 TP-Link switch. I had known the credentials from my Ubuntu controller. I wanted though to move over the logs. I had the version 5.9 logs, but they were incompatible with the 5.7 version which was the "update" version from TP-Link. So I saved the 5.7 configuration, devices, users + logs, updated the software to 5.9 using the links you gave me, and then I was able to restore from the initial Ubuntu 5.9 based configuration file. All went well. I made a few small changes to the Controller name and Site name, but all else worked fine. Russell
Russell Sutherland russ@quist.ca
  1  
  1  
#6
Options
Re:Configuration Incompatiblity
2023-05-01 20:28:08

  @Quist 

 

Thanks, good to know that 5.9 backup files are compatible between hardware controller and the software controller.  

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#7
Options