Phone Lines icon GFI Support Home

Articles in this section

See more

Exinda | Copying Config or Migrating from different Exinda

Author: Luis Fernandes

Summary

Copy configuration from one Exinda to a different Exinda

Overview

The configuration of an Exinda can be moved between devices, which can be useful in a number of scenarios:
  1. If a client has lost the configuration in one of his Exinda and wants to use another Exinda's config.
  2. If a device is being upgraded or replaced (RMA).
  3. If something is requiring a device to be set to factory defaults or re-manufactured
In these scenarios, it is possible to copy configuration over, with some caveats.
  • Ensure that both devices are on the same firmware version
  • 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 which are exchanging configuration, a text copy of the original Exinda's configuration can be made and imported into the second Exinda. To do so, go to the original Exinda and perform the following:
  1. Go to Configuration > System > Maintenance
  2. On the "Manage Config" tab, find the configuration you wish to export, and
  3. Click on the save icon in the Download column beside it (may take some time to generate)
  • You will be prompted to download a .txt file to your local system.
  • This .txt file contains all the CLI commands to replicate the config, much like a "show run" command.
On the new device, perform the following:
  1. Go to Configuration > System > Maintenance
  2. On the "Import Config" tab, select the "Upload local text file" option and choose the file downloaded from the original Exinda
  3. Click "Upload Configuration"
  • 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.
Note: Binary copies of the configuration only work when the device and hardware is 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.
Go to the original device and perform the following:
  1. Go to Configuration > System > Maintenance
  2. On the "Manage Config" tab, put a check mark in the box beside the configuration you wish to export
  3. Click on the "Download" option to download the config as a binary file.
Once it downloads locally to your system, go to the new device and perform the following:
  1. Go to Configuration > System > Maintenance
  2. On the "Import Config" tab, under the "Upload local binary file" option, select the binary downloaded from the original Exinda
  3. Click "Upload Configuration"
Note: This process can take some time.

Additional Information

  1. There are some caveats and things to note with this process:

    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
  2. The host name of the original device is copied over as well.
  3. 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.
  4. 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.
  5. If error happen with regards to being unable to match bridges or unknown interfaces (for example, a 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 after 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.
  6. 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.


Note: 

  • The online JS compressor tool can help you to optimize your scripts for a faster page loading.
  • If errors persist during import, please contact Customer Support for assistance.

Internal Notes

Recommended/Safer way to Import configuration into RMA devices

>>> Caution: This process is internal and should not be implemented independently by the customer <<<
>>> Caution: The conventional way of downloading and importing the config file is not recommended In the case of RMA <<<

------ Preparation Stage -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Make sure that the customer is aware of below prerequisites since a slight downtime for the network is considered.
  • Ask the customer to download the current configs and save it as a txt file. (it is recommended to download and save the binary file as well)
    > Disable Adblock if download does not start
  • Ensure both devices are on the same firmware version
  • 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 before you start the procedure otherwise it may affect the customer network performance.
  • Console into the new unit before customer starts any re-racking
  • Enable IPMI (Dell iDRAC) as a backdoor to the system if the device model is capable of.
------- Importing the Configuration ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Make sure that these commands are imported and executed chunk by chunk through maintenance>import config. You should see a green bar after each execution. red bars mean some particular commands has not gone through, so you have to react accordingly.
What to be imported from the text file (already downloaded in the previous stage):
  • Network interface configuration (if you are %100 sure all the ports/bridges match with the older unit. if they don't change them accordingly. also mind the static IPs as mentioned in the additional information)
  • Other IP configurations (DNS and etc.)
  • SLA Configurations
  • Routing configuration
  • All the Objects (Network, Schedules, Applications and etc. )
  • Application Groups
  • Optimizer configurations (The biggest Chunk of codes)
  • Reports
  • Policies and Virtual Circuits
  • Acceleration Configurations
Hint: In case you lose access, try to use IPMI port if enabled (applicable on limited Dell server models)
Hint: It is recommended to note every part we skip importing and reconfigure in the future.

-------- Exinda in Production ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  • Check all the network settings
  • Take a look at all the objects defined by the customer
  • Check the system health.
  • Check to see if all the policies are in place.
  • Check all the custom applications, Pre-defined applications, and application groups
  • and check whatever that may impact the Exnida's functionality if missing
  • Unplug the cables from the old one and plug them into the new one. (there would be a downtime for few seconds till the auto bridge bypass triggers)
  • Monitor the real-time traffic and make sure traffic has the flow it is supposed to have
Do not close the case right away! Let the customer monitor the Exinda performance for few days, then follow up and close the case upon the confirmation.

Related articles