This article provides the steps required for you to migrate the configuration from an Exinda System to another one, make sure to follow all suggestions and read it carefully because an incorrect migration can result in missing applications in your Exinda system
- Access to the Exinda Web UI
- If a client has lost the configuration in one of his Exinda and wants to use another Exinda's config
- If a device is being upgraded or replaced (RMA)
- If something is requiring a device to be set to factory defaults or re-manufactured
- Ensure that both devices are on the same firmware version (If there is a mismatch in between firmware on both systems, this can cause missing applications on the new system)
- Note the bridge names and interfaces on both devices as these may be required to change in the config
- Ensure the new device has a valid license already installed on it
In the former cases, where there are two separate devices that are exchanging configuration, a text copy of the original Exinda's configuration can be made and imported into the second Exinda.
A Text File
- First, you need to download the configuration file from the Exinda system.
- After that, you need to import the configuration file to the new Exinda system.
- This will execute every command line in the file, one at a time, starting from the top
- The config is generated according to the order of Import, however, some errors may still occur (see below for more information)
- The logging of the Exinda will log every CLI command done, so progress can be checked to see where the Exinda is in the process of executing the configuration
- In the latter case, where the device will remain the same but for some reason the configuration will be lost and it is known ahead of time, the device can have its configuration copied in binary form
Binary copies of the configuration only work when the device and hardware are exactly the same, right down to the MAC addresses on the NICs.
- As a result, it can only be done in cases where the device is the exact same
- The advantage is that binary configuration often imports a lot faster than large text configurations, and is less prone to error
- First, you need to download the binary file from the old Exinda system.
- After that, you need to import the binary file to the new Exinda system
- Copying over the config copies over any IP addresses associated with interfaces. This means that if the original device is still on the network, there will be IP conflicts with any new devices. This also means that the IP address for management on the new device might change, so web UI access will be lost until the new IP is used. This also involves terminating the web UI processes and restarting them
- The hostname of the original device is copied over as well
- This will copy the old license over from the original device.
Going to Configuration > System > Setup, and find the "Licenses" tab, there will be a new license below the one for the original unit. It will say "Tied to Host ID: [id] (FAILED)" and there will be a red X in the box. That license is tied to the original device and will not be valid on the new one, so it is safe to remove
- Sensitive things like passwords for SNMP or the Active Directory Integration, or private keys for certificates that have been placed on the Exinda, if enabled, will not be copied over and will need to be recreated once the configuration is imported
- If errors happen with regards to being unable to match bridges or unknown interfaces (for example, 2061 only has eth1-4, but a 6062 has eth1-2, eth10, eth11, etc), those commands can be changed in the configuration file. To edit the configuration file:
- Bridge commands can be found by searching for 'br'. A bridge number starts on the LAN interface (an even number) - so a bridge for eth20-21 will be br20.
- Lines that should not be imported can be commented out by using a hash symbol (#) at the start of a line. This will disregard that line as a command.
- If certain commands have failed through the import, it is possible to redo certain commands by copying and pasting them into the large textbox on the "Import Config" page. This will only import the commands pasted in.
- The optimizer configuration - including circuit sizes and virtual circuits will be copied exactly. If the new device is not licensed for as much as the original unit is, there can be some problems with allocating too much bandwidth to circuits past the licensed limit. Ensure that the new device's license is at least as large as the original one is.