How to migrate the configuration files from Omada Software Controller into OC200?

Configuration Guide
Updated 04-10-2019 06:02:37 AM
Ten artykuł dotyczy: 

The Omada Cloud Controller (OC200) is the management device which is pre-installed with the Omada Software Controller 3.0.2 or above. Therefore, you can migrate the configuration file from the Omada Software Controller into the OC200 using the Restore function. Then you can conveniently change your management tool from Omada Software Controller to the OC200 without data lost. Note that Backup&Restore is available only for local logged-in users.

Follow the steps below to migrate the configurations from Omada Software Controller into the OC200.

  • Backup your configuration files on your Omada Controller Software.
  1. Launch the Omada Software Controller.
  2. Go to Controller Settings > Backup&Restore. Select the length of time in days that data will be backed up in the Retained Data Backup drop-down list. For example, with 7days selected, the data only in recent 7days will be backed up.

  1. Click Backup to save the backup file.
  • Migrate the configurations into the OC200
  1. Launch a web browser and type the IP address of the OC200 in the address bar, then press Enter (Windows) or Return (Mac). Go to Controller Settings > Backup&Restore.
  2. Click Browse to locate and choose the backup file. Then click Restore to migrate the configurations.

Due to the limited capacity and unsupported features of the OC200, some parameters below will be inevitably changed or discarded after the migration is completed. You need to configure again.

  • If the backup time interval is set as All Time in the backup file from the Omada Software Controller, the backup time interval will be set as 365 days after restoration. Because the OC200 does not support backing up data all the time.
  • The site privileges of the cloud users whose roles are Operator or Observers will be cleared.  You should go to the Cloud Access page to configure site privileges again.
  • For the limited data capacity of the OC200 device, only part of the data entries will be retained as the following rules.

Access Points

OC200 can manage 100 EAPs at most. When the number of the EAPs managed by Omada Software Controller is more than 100, only 100 EAPs which are last seen by the controller will be restored to the OC200.

Recent Activities

OC200 can keep 100000 entries of Recent Activities. When the number of the Recent Activities of Omada Software Controller is more than 100000, only 100000 entries in the recent time will be restored to the OC200.

Client Statistics

OC200 can keep a record of 40000 clients at most. When the number of the client entries is more than 40000, only 40000 clients which are last seen by the controller will be restored to the OC200.

Guest Statistics

OC200 can keep a record of 40000 guests at most. When the number of the guests entries is more than 40000, only 40000 guests which are last seen by the controller will be restored to the OC200.

Client History

OC200 can keep 200000 entries of Client History. When the number of the Client History of Omada Software Controller is more than 200000, only 200000 entries in the recent time will be restored to the OC200.

Logs

OC200 can keep 10000 entries of logs. When the number of logs of Omada Software Controller is more than 10000, only 10000 entries in the recent time will be restored to the OC200.

Picture Files

OC200 can keep the picture files within 128MB. When the size of pictures in the configuration file of Omada Software Controller is bigger than 128MB, the pictures cannot be restored to the OC200. The map and portal which use the picture will revert to the default pictures.