Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

How to migrate from hive manager to Extreme Cloud IQ and between Cloud IQ instances

« Go Back

Information

 
TitleHow to migrate from hive manager to Extreme Cloud IQ and between Cloud IQ instances
Objective
Migration from Hive Manager Classic to Extreme Cloud IQ.
Migration between Extreme CLoud IQ Instances
Environment
  • Hive Manager Classic
  • Extreme Cloud IQ
Procedure

Overview

Migrating your network from one ExtremeCloud IQ architecture to another can be a daunting prospect, but it does not need to be difficult. This document provides a conceptual overview of the process, followed by the stepwise process itself. Taken together, the overview and the explicit steps ease the migration process.

Migration vs. Move

In this document, a migration refers to the process of transferring a VHM from a HM Classic instance to a ExtremeCloud IQ instance. A move refers to the process of transferring a VHM between ExtremeCloud IQinstances.

Scope

This document describes how to migrate HM Classic VHMs to ExtremeCloud IQ, and how to move ExtremeCloud IQ VHMs between different ExtremeCloud IQ instances, such as from a virtual appliance to the public cloud. This document does not address migrations in which HM Classic is the destination; HM Classic cannot be the destination platform.

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.

The Process

The process of migrating from HM Classic to ExtremeCloud IQ consists of six steps. (There are fewer steps if HM Classic is not involved.)

First, you must prepare for the migration by setting up a destination VHM and collecting all the information you need to migrate successfully. When you are performing this step, ensure that you have considered all the prerequisites. Omitting information or steps can result in an unsuccessful migration.

Second, export the VHM from your source platform. If you are migrating from HM Classic, remember that configuration elements are not preserved in the migration, so you need to take inventory of your network elements in HM Classic so that you can recreate them within the destination ExtremeCloud IQ instance. The export process differs slightly depending on the specific platform from which you are exporting.

Third, import the VHM into ExtremeCloud IQ. For this step to be successful, you must have the network elements recreated in ExtremeCloud IQ if you are migrating from HM Classic. If you are simply moving your VHM between ExtremeCloud IQ instances, then you do not need to recreate the elements.

Another thing to consider is that, for IQ Virtual Appliance-to-IQ Virtual Appliance migrations, this step requires that both the source and destination VHMs be live on the network at the same time. A simple way to manage this potentially problematic situation is to name your destination VHM “HM” temporarily so that there are no namespace conflicts, and to ensure that you have not assigned it the same IP address as the source VHM. In a later step, you merge your new VHM into your network.

Fourth, unmanage or remove all devices from the source VHM. The goal of this step is to liberate the devices from being managed by your source VHM so that they can be managed by the destination VHM. If the devices are not unmanaged or removed from the source VHM, then your destination VHM cannot manage them after the migration and a call to Support is necessary.

Fifth, manage the devices from within the new destination VHM. When this is done, you can safely shut down the source VHM (which frees its name and IP address for use), and then change the name and IP address of your destination VHM to match the name and IP address of the source VHM. When you do this, your network devices—already configured with the name and IP address of ExtremeCloud IQ —automatically connect to your new VHM seamlessly.

Finally, apply your network policies from within ExtremeCloud IQ. This step initiates a complete configuration update on the devices and forces them to reboot to ensure that a clean and current configuration is present on all devices after the migration is complete.

 

Prerequisites

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.

 

MIGRATE FROM HM CLASSIC TO EXTREME CLOUD IQ

Step 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.


Step 2: Export the Configuration from HM Classic
 

There are three things that you must export:

• Device running configurations

• Device inventory

• VHM backup file

Export Device Running Configurations

In HM Classic, create a file that contains the running configuration settings for the devices that you will be bringing into ExtremeCloud IQ. To build this file in HM Classic, it is best to capture the running configuration from the network policy for each device type (APs, switches, and branch routers). This allows you to see configuration elements within the menu structure that might otherwise be missed, and to identify and remove duplicate elements.

To export a device running configuration, do the following:

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

Exporting the running configurations for your devices can be a long process, especially when there is a large inventory of devices. Furthermore, device configurations can be quite large, and ensuring that the destination network configuration accurately matches your source network configuration can be lengthy process. Whereas this process is an optional step in the migration, it can be helpful as a planning, migration, and troubleshooting reference throughout the migration process.

Export Device Inventory

The device inventory provides you with a list of your devices, along with several of the device parameters. Exporting the device inventory is optional, but you can use the resulting information to verify that the devices are properly imported and present in ExtremeCloud IQ after the migration is complete.

To export the device inventory, do the following:

  1. 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.

  1. Click Device Inventory > Export.
  2. When HM Classic generates the .csv file and makes it available to you, download it for reference.

Export HM Classic Backup File

The workflow for this process differs slightly, depending on whether your source VHM is HM Classic Cloud or HM Classic Appliance.

Export from HM Classic Cloud

To export the VHM backup file from HM Classic Cloud, navigate to Home > Administration > HiveManager Operations > Back Up Database, select Configuration backup only, and then click 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

To export the VHM backup file from HM Classic Virtual Appliance, do the following:

  1. Navigate to Manage > Update > Advanced > Upload and Activate IQ Engine Firmware.
User-added image
 
  1. 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.
  1. 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.


Step 3: Import the Configuration File to the Destination VHM

To import the backup configuration file, do the following:

  1. Log in to ExtremeCloud IQ using an account with Administrator or Operator privileges, navigate to Global Settings > VHM Management, and then click Import VHM.
  2. In the VHM Import dialog box, select Import VHM from HM Classic.
  3. Click Choose, and then choose the file you want to import.
  4. 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.
  1. Click Import Now.

Step 4: Remove Devices in Hive Manager Classic

Before you can manage your devices in the new VHM, you must unmanage them in HM Classic. To unmanage your HM Classic devices, do the following:

  1. 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.
  2. 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
      3. Click Device Inventory and then select Remove.

      4. 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.
      5. In the Remove Selected Devices dialog box, select Keep existing device configurations.
      6. Click Yes.
      7. 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 A record for your virtual appliance.
 

Step 5: 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.

To add your devices to the new IQ Virtual Appliance VHM, do the following:

  1. Open ExtremeCloud IQ by entering the URL of your new ExtremeCloud IQ VHM, designating port 3000.
User-added image
 
  1. 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.
  2. 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.
  1. 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.

To add your devices to the new ExtremeCloud IQ Cloud VHM, do the following:

  1. Navigate to Manage > Devices, click Add, and then add the devices.
  2. Select the check boxes of the imported (added) devices, and then select Actions > Change Management Status > Manage Devices.

Step 6: Deploy Policies to Managed Devices
 

To deploy your network policies to the devices, do the following:

  1. 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.
  2. 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.
  3. 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.

 

MIOVE A VHM BETWEEN EXTREME CLOUD IQ INSTANCES
 

Moving a VHM from one instance of ExtremeCloud IQ to another is a six-step process:

Step 1: Create a Destination VHM

To migrate a VHM, you must have a destination VHM. The destination VHM must be running ExtremeCloud IQ 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.

Step 2: Export the Source VHM to a Configuration File
 

The configuration file that you export from a ExtremeCloud IQ VHM contains all network policies, configuration parameters, and device settings, which simplifies the transfer of information during the move process. To export the VHM, you must possess Administrator or Operator privileges if you are using ExtremeCloud IQ, or Administrator privileges if you are using Hierarchical ExtremeCloud IQ.

  1. Log in to ExtremeCloud IQ using an account with the appropriate privileges, navigate to Global Settings > VHM Management, and then click Export VHM. ExtremeCloud IQ opens the VHM Export dialog as a new tab.
  2. In Optional Settings, enter 60 minutes in the Export Timeout text box.
  • In rare occasions, such as when there is a low available bandwidth, the process exceeds the default timeout of 30 minutes. Increasing the timeout to 60 minutes increases the success rate without the need to re-import the file.
  1. Click Export Now. ExtremeCloud IQ suspends the VHM during the export operation and displays a status progress report. When the export process completes successfully, ExtremeCloud IQ closes the VHM Export dialog tab.
  2. Navigate to Global Settings > VHM Management to reopen the VHM Export dialog in a new tab, and then click the link to download the configuration file to your local machine in .tar.gz (compressed tarball) format. After you download the file, you can safely close the VHM Export dialog tab.


Step 3: Import the File into a HiveManager
 

To import the configuration file into your destination VHM, do the following:

  1. Log in to ExtremeCloud IQ using an account with Administrator or Operator privileges, navigate to Global Settings > VHM Management, and click Import VHM.
  2. In the VHM Import dialog, select Import VHM from ExtremeCloud IQ.
  3. In the Optional Settings, enter 60 minutes in the Import Timeout text box.
  • In rare occasions, such as when there is a low available bandwidth, the process exceeds the default timeout of 30 minutes. Increasing the timeout to 60 minutes increases the success rate without the need to re-import the file.
  1. In the VHM Import dialog box in the Optional Settings section, select Continue the operation as the course of action to take if an error occurs while importing a VHM.
  2. Click Choose, choose the configuration file you want to import, and then click Import Now.

Step 4: Remove Devices from the Source VHM
 

One—and only one—ExtremeCloud IQ VHM can manage a particular device. The determination of which VHM manages which device is made on the global redirector, where a database tracks this relationship. Exporting or importing configuration files does not affect the management information on the global redirector. As a result, even after importing the configuration file—with all the devices—to the destination VHM, each device is still considered to be managed by the source VHM until explicitly removed. Removing a device removes the device mapping on the redirector, removes the CAPWAP settings on the device, and thereby forces the device to begin the device discovery process.

To remove your devices from your source VHM, do the following:

  1. If you are moving your VHM from ExtremeCloud IQ Cloud to IQ Virtual Appliance, ensure that you have your virtual appliance running, and that you have a DNS A record entry for it.
  2. Navigate to Manage > Devices, select the devices you want to remove, and then click .
  • If you have more than one page of devices an option appears beneath the column header row to ensure you can select all devices.
  1. If you are moving your VHM from IQ Virtual Appliance to ExtremeCloud IQ Cloud, remove the DNS A record for your virtual appliance.

Step 5: Import Devices to the Destination VHM
 

When devices are added to a VHM, they are initially marked as unmanaged. You must explicitly change these devices to managed within ExtremeCloud IQ. ExtremeCloud IQ automatically populates device mapping in the global redirector and invokes the device discovery process, in which each device contacts global redirector for its mapping, and then is redirected by the global redirector to the new device management platform—the destination VHM.

To import your devices, navigate to Manage > Devices, select the check box for all devices, and then click Actions > Change Management Status > Manage Devices.

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


Step 6: Deploy Policies to Managed Devices
 

ExtremeCloud IQ-to-ExtremeCloud IQ migrations import all configurations, network policies, and other assignments for the devices. To upload the network policies to the devices, do the following:

  1. Navigate to Manage > Devices and ensure that your devices appear as Managed Devices.
  2. Select the check boxes for the newly managed devices, click Actions > Assign Network Policy, and then select the appropriate policy. Repeat for all remaining devices.
User-added image
  1. 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

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255