Reset Search
 

 

Article

How to Migrate From HM Classic To ExtremeCloud IQ

« Go Back

Information

 
TitleHow to Migrate From HM Classic To ExtremeCloud IQ
Objective
  • Migration from Hive Manager Classic to Extreme Cloud IQ.
  • Migration between Extreme Cloud IQ Instances
Environment
  • Hive Manager Classic
  • Extreme Cloud IQ
Procedure

Read additional notes below, before initiating the migration process. 

  • Use Firefox during the migration. The exported configuration file can exceed 20 GB in size, and Firefox is capable of handling extremely large files such as this.
  • Verify your licenses and access privileges. Ensure your licenses are valid for the new VHM and that you have full administrator privileges.
  • Ensure your devices are supported. Some very old Extreme Networks devices are not supported by current ExtremeCloud IQ software. Attempting to import unsupported devices can result in ExtremeCloud IQ displaying error messages or other unpredictable behavior, but does not prevent or interrupt the migration.
  • Update devices before you migrate. Update all devices to the latest stable or feature release. This ensures that ExtremeCloud IQ supports the IQ Engine versions of your supported devices. Attempting to migrate supported devices running unsupported software results in ExtremeCloud IQ displaying error messages, but does not prevent or interrupt the migration. However, ExtremeCloud IQ cannot manage a device running unsupported software, so you must upgrade IQ Engine on the affected devices manually.
  1. Create a Destination VHM (Virtual Appliance Only)

To migrate a VHM, you must have a destination VHM. The destination VHM must be running HiveManager 12.8.0.3 or later and—if you are hosting the physical server on which the VHM runs—must meet the minimum hardware requirements listed in the "ExtremeCloud IQ Virtual Appliance QuickStart Guide", to which you can refer for the ExtremeCloud IQ VHM installation instructions.

  1. Export the Configuration from HM Classic

Export Device Running Configurations

  • Navigate to Monitor.
  • Select a device.
  • Click Utilities > Diagnostics > Show Running Config.
  • Copy the resulting text output and paste into a text editor for reference.
Repeat the steps above for each remaining device type within each network policy.

Export Device Inventory

  • Navigate to Manage > Managed Devices, and then click the select all check box to select all devices. (The select all check box does not have a label, but is located in the column header above the selection check box column. If you have more than one page of devices an option appears in the center of the page to ensure you can select all devices.
  • Click Device Inventory > Export.
  • When HM Classic generates the .csv file and makes it available to you, download it for reference.

Export HM Classic Backup File

Export from HM Classic Cloud
  • Navigate to Home > Administration > HiveManager Operations > Back Up Database
  • Select Configuration backup only
  • Click on Back Up.
This process can take some time (greater than 30 minutes) depending on the number of and the size of the maps in the planning tool.

Export from HM Classic Virtual Appliance

  • Navigate to Manage > Update > Advanced > Upload and Activate IQ Engine Firmware.
User-added image
  • Select Add/Remove, select the check boxes of all firmware files by file name, and click Remove.
The exported file contains the firmware files, so this step ensures that the exported configuration file is as small as possible, and also ensures that the exported file is compatible with the new ExtremeCloud IQ VHM. Be sure to remove all the firmware files.
  • Navigate to Home > HiveManager Operations > Back Up Database, select Configuration backup only, and then click Back Up.
User-added image

This process can take more than 30 minutes, depending on number and size of the maps in the planning tool.
  1. Import the Configuration File to the Destination VHM
  • Log in to ExtremeCloud IQ using an account with Administrator or Operator privileges
  • Navigate to Global Settings > VHM Management, and then click Import VHM. In the VHM Import dialog box, select Import VHM from HM Classic.
  • Click Choose, and then choose the file you want to import.
  • In the Optional Settings, enter 60 minutes in the Timeout text box, and select Continue the import operation.
In rare occasions, such as when there is a low available bandwidth, the process can exceed the default timeout of 30 minutes. Increasing the timeout to 60 minutes increases the success rate without the need to re-import the file.
  • Click Import Now.
  1. Remove Devices in Hive Manager Classic

If you are moving your VHM from HM Classic Online to IQ Virtual Appliance, ensure that you have your virtual appliance running, and that you have a DNS A record entry for it.

  • Navigate to Manage > Managed Devices, and then click the select all check box to select all devices. (The select all check box does not have a label, but is located in the column header above the selection check box column.) If you have more than one page of devices an option appears beneath the column header row to ensure you can select all devices.

User-added image

  • Click Device Inventory and then select Remove.
  • If you are migrating from HM Classic Online to HM Classic Cloud, select Keep existing device configurations in the Remove Selected Devices dialog, otherwise select Reset device configurations to their default or bootstrap settings.
  • In the Remove Selected Devices dialog box, select Keep existing device configurations.
  • Click Yes.
If you are migrating from HM Classic Appliance or HM Classic Virtual Appliance to ExtremeCloud IQ Cloud, then wait approximately 10 minutes, shut down the HM Classic instance, and then remove the DNS record for your virtual appliance.
 
  1. Add Devices to the ExtremeCloud IQ Destination VHM

Depending on whether the new ExtremeCloud IQ VHM is now in the cloud or running on a virtual machine there are two procedures.

Add Devices to a IQ Virtual Appliance

To prepare to add devices to your IQ Virtual Appliance, check your DNS A record and note the FQDN and IP address of your current virtual appliance. You can use this information to ensure that your new VHM is properly allocated during the migration.

  • Open ExtremeCloud IQ by entering the URL of your new ExtremeCloud IQ VHM, designating port 3000.
User-added image
 
  • Change the IP address and the host name (in this case, the host name field contains the FQDN of the instance, such as hivemanager.yourdomain.com) to match those of the old HM Classic instance.
  • Click Submit to apply the settings and reboot the system. After a short time, the devices begin to appear in ExtremeCloud IQ on the Managed Devices page.
  • The devices do not normally appear right away; rather, they appear incrementally over the course of five to ten minutes.
  • Continue with Step 6 below.

Add Devices to ExtremeCloud IQ

Newly-imported devices are initially marked as unmanaged. You must explicitly change these devices to managed. ExtremeCloud IQ automatically populates device mapping in the global redirector and invokes the device discovery process as each device calls the global redirector to be redirected.
  • Navigate to Manage > Devices, click Add, and then add the devices.
  • Select the check boxes of the imported (added) devices, and then select Actions > Change Management Status > Manage Devices.
 
  1. Deploy Policies to Managed Devices
  • Navigate to Manage > Devices and ensure that your devices appear as managed devices in the Managed column of the device table. If the Managed column does not appear, click the column picker and select Managed from the list of available columns.
  • Select the newly managed devices to which you want to assign a particular network policy, click Actions > Assign Network Policy, and then choose the policy. Repeat for all remaining devices, as required.
  • In the Device Update dialog box, select Complete Configuration Update, and then click Perform Update.

Because this is a first-time device configuration upload from this ExtremeCloud IQ, all updated devices reboot after receiving the new configuration.

 

 









 


 

Additional notes

To begin, there are important considerations you must understand before initiating a migration:

  • HM Classic configuration elements are not preserved. When you export your HM Classic VHM, the configuration parameters are preserved in the exported file, but the configuration elements (such as network policies) are not preserved. This means that you need to create the configuration elements in the new VHM before importing the configuration file.
  • ExtremeCloud IQ configuration elements are preserved. When moving your VHM from one ExtremeCloud IQ instance to another ExtremeCloud IQ instance, the process is much easier because all the configuration elements are present in the export file and preserved during the move.
  • Licenses might not transfer. Because licenses might not transfer, you need to contact your sales representative to ensure that you possess a valid license for the new ExtremeCloud IQ instance before migrating.

 

 

    Feedback

     

    Was this article helpful?


       

    Feedback

    Please tell us how we can make this article more useful.

    Characters Remaining: 255