Migrate Windows Controller 5.14.20.9 to OC200 5.13.30.20

Migrate Windows Controller 5.14.20.9 to OC200 5.13.30.20

Migrate Windows Controller 5.14.20.9 to OC200 5.13.30.20
Migrate Windows Controller 5.14.20.9 to OC200 5.13.30.20
2024-07-30 02:12:43 - last edited 2024-07-31 08:04:31
Hardware Version: V1
Firmware Version: 5.13.30.20

I have a Windows controller that I want to migrate to a OC200. The guides I've found say the two controllers need to be on the same version. What is the best approach in my case?

 

Thanks

  0      
  0      
#1
Options
1 Accepted Solution
Re:Migrate Windows Controller 5.14.20.9 to OC200 5.13.30.20-Solution
2024-07-31 08:04:19 - last edited 2024-07-31 08:04:31

  @millsusaf 

Update the software controller to V5.14.26.1 and the OC200 firmware to V1_1.31, which includes the built-in Software Controller (v5.14.26.23).
Then you can migrate them.
 

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  0  
  0  
#3
Options
6 Reply
Re:Migrate Windows Controller 5.14.20.9 to OC200 5.13.30.20-Solution
2024-07-31 08:04:19 - last edited 2024-07-31 08:04:31

  @millsusaf 

Update the software controller to V5.14.26.1 and the OC200 firmware to V1_1.31, which includes the built-in Software Controller (v5.14.26.23).
Then you can migrate them.
 

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  0  
  0  
#3
Options
Re:Migrate Windows Controller 5.14.20.9 to OC200 5.13.30.20
2024-07-31 20:55:13

Hank21 wrote

  @millsusaf 

Update the software controller to V5.14.26.1 and the OC200 firmware to V1_1.31, which includes the built-in Software Controller (v5.14.26.23).
Then you can migrate them.
 

  @Hank21 

 

Thank you for that info. I have the firmware downloaded however the guide/release notes are not accurate/current.  When I navigate to Settings>System Settings>Hardware Controller all I'm presented with is the "Check for Upgrade" box. When clicked it says I'm running the latest verion, which is 1.29.4. How can I force it to manually upgrade to your recommended 1.31?

  0  
  0  
#4
Options
Re:Migrate Windows Controller 5.14.20.9 to OC200 5.13.30.20
2024-08-01 01:48:36

  @millsusaf 

You are unable to directly upgrade to the most recent firmware, since it hasn't uploaded to the cloud. It would soon be updated, though. To manually upgrade the firmware, follow this link.How to upgrade or downgrade the firmware of Omada Controller

Firmware Download

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#5
Options
Re:Migrate Windows Controller 5.14.20.9 to OC200 5.13.30.20
2024-08-01 02:15:02

Hank21 wrote

  @millsusaf 

You are unable to directly upgrade to the most recent firmware, since it hasn't uploaded to the cloud. It would soon be updated, though. To manually upgrade the firmware, follow this link.How to upgrade or downgrade the firmware of Omada Controller

Firmware Download

  @Hank21 

 

I guess I will have to wait then as the option for a manual upload isn't avaliable. The documents are outdated/incorrect.

 

Its unfortunate the manual update option was removed.

 

 

  0  
  0  
#6
Options
Re:Migrate Windows Controller 5.14.20.9 to OC200 5.13.30.20
2024-08-01 02:19:16

  @millsusaf 

It is not outdated. You should update it locally. That means logging in using the OC200's IP address rather than the Cloud.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#7
Options
Re:Migrate Windows Controller 5.14.20.9 to OC200 5.13.30.20
2024-08-01 12:25:57

Hank21 wrote

  @millsusaf 

It is not outdated. You should update it locally. That means logging in using the OC200's IP address rather than the Cloud.

  @Hank21 

 

I see, that worked. Thank you.

 

I also see 1.31 is now avaliable for auto-upgraded. Thanks

  1  
  1  
#8
Options