Migrating the AirWave Server
Important Information for Migration
The following are the requirements and guidelines for the migration process:
Only online migration is supported currently. Ensure both the AirWave system which is being migrated and the Aruba Central system which is the target are reachable on the network. Ensure that the TCPTransmission Control Protocol. TCP is a communication protocol that defines the standards for establishing and maintaining network connection for applications to exchange data. port 443 is open to migrate to Aruba Central (on-premises).
The AirWave system must be running a minimum AirWave version of 8.2.8.2 for the migration to proceed. If the AirWave system is running an earlier version, refer to the AirWave documentation to upgrade the version to 8.2.8.2.
Only those APs, controllers, and switches that are supported in Aruba Central (on-premises) are migrated. For information on supported hardware, see Supported Platforms section.
As part of migration, Visual RFRadio Frequency. RF refers to the electromagnetic wave frequencies within a range of 3 kHz to 300 GHz, including the frequencies used for communications or Radar signals. and the device inventory for CAPs, IAPs, controllers, and Aruba/HPE switches are migrated.
For controllers, the device credentials for SNMPSimple Network Management Protocol. SNMP is a TCP/IP standard protocol for managing devices on IP networks. Devices that typically support SNMP include routers, switches, servers, workstations, printers, modem racks, and more. It is used mostly in network management systems to monitor network-attached devices for conditions that warrant administrative attention. and HTTPSHypertext Transfer Protocol Secure. HTTPS is a variant of the HTTP that adds a layer of security on the data in transit through a secure socket layer or transport layer security protocol connection. profiles are mapped.
Migration of multiple AirWave systems to a single Aruba Central (on-premises) server is supported. That is, you can migrate multiple AirWave systems to Aruba Central (on-premises) by adding the IP addresses of each AirWave system individually.
All the historical data including data related to reports, monitoring, and stats are not migrated from Airwave to Aruba Central (on-premises) during the migration process.
Templates are not migrated from Airwave to Aruba Central (on-premises) during the migration process. You must manually create a new template in Aruba Central (on-premises) based on the requirement.
All data related to VisualRF is migrated from Airwave to Aruba Central (on-premises) during the migration process.
Accessing the Migration Page
To access the migration page, perform the following procedure:
1. Log in to your Aruba Central (on-premises) account as an administrator.
2. Click the page icon.
The Account Home page is displayed.
3. Click >
4. Click the tab.
The migration page is displayed.
|
|
During the migration process, a new AMPAirWave Management Platform. AMP is a network management system for configuring, monitoring, and upgrading wired and wireless devices on your network. back up is created in AirWave and transferred to the Aruba Central (on-premises). The scheduled nightly backup is independent of the backup operation performed as a part of the migration process. |
Following table lists the tab details:
|
Name |
Description |
|
|
FQDNFully Qualified Domain Name. FQDN is a complete domain name that identifies a computer or host on the Internet. or IP address of the AMP. |
|
|
Indicates if the migration is ongoing, failed, or successful. For more information, see Migration Status and Migration Descriptions. |
|
|
Displays the ongoing step in the migration process. For example, the Description column provides information |
|
|
Provides a summary of the migration activity occurring during migration. Following are some of the messages displayed: Number of devices existing on Aruba Central (on-premises) Number of devices on AirWave 8.x Number of devices to migrate Number of devices successfully migrated Number of devices failed to migrate |
|
|
Allows you to restart the migration process by clicking the restart |
icon. You can also delete an AMP from the migration table by clicking the delete 
icon.5. Click the tab at the top right corner of the table to add a new migration task. For more information, see Performing the Migration.
Performing the Migration
In the migration page, perform the following steps:
1. Enter the following details in the migration page:
—Enter the IP address of the AirWave Management Platform (AMP).
—Enter the user name for any administrative user.
—Enter the password associated with the administrative account.
—Re-enter the password.
2. Click to begin the migration process.
3. You can add multiple IP addresses to migrate from multiple AirWave servers to one Aruba Central (on-premises) server. In this case, each AMP will be migrated sequentially one after another.
Figure 1 Add Migration Using Host Name
Figure 2 Add Migration Using IP Address
|
|
All system operations are disabled until the active system operation is complete. The migration, backup and restore, high availability processes, and the upgrade operations are the system operations in Aruba Central (on-premises). |
Validating the Migration Process
After you click on the migration window, the migration process starts. If multiple AMPs are added, each AMP will be migrated sequentially one after another.
Figure 3 Screen Capture of a successful Migration.
|
|
The default time out period for the backup process during the migration is . |
During the migration process, a fresh AMP back up is created in Airwave 8.x and transferred to the Aruba Central (on-premises). The scheduled nightly backup is not performed as a part of the migration process.
Logs
The table displays all the logs related to the migrations that are either complete or failed. Click to create the log files.
The log files that are generated contains the cumulative data of all the AMP migrations.
Figure 4 Log File
The table displays the following columns:
|
Name |
Description |
|
|
The name of the log file that is generated. |
|
|
The date and time when the log file is created. |
| Indicates the status of the logs that are generated. The status indicated is , , , or | |
|
|
Enables you to perform the following actions: Downloading the generated log files by clicking the download icon. The files are then saved to the local drive as a TAR file. Deleting the log file by clicking the delete icon. |
Migration Status
Following is a list of migration status displayed in the Airwave Migration table:
Waiting to start migration
Migration Stopped
Migration Started
AW8.X generating migration dump
AW8.X migration dump is ready
COP migration is in progress
Migration Success
Migration Failed
Labels assigned successfully
Migration needs to be done before applying labels
Labels cannot be applied for the failed migration
Labels cannot be applied while migration is in progress
Migration Descriptions
Following is a list of migration status descriptions that are displayed during the migration process under the description heading of the migration table:
Migration of AMP not started
Starting migration of AMP to COP
Connecting to AMP
Could not establish connection to AMP
Could not prepare backup on AMP
Waiting for AMP backup to be prepared
AMP backup not prepared after 2 hrs, please check AMP logs
AMP backup is ready for download from AMP
AMP backup is being downloaded to COP
AMP backup download failed AMP backup downloaded successfully
Restoring AMP backup in COP
AMP version not supported for migration
Migrating devices to COP Migrating profiles to COP
Checking for VRFVisualRF. VRF is an AirWave Management Platform (AMP) module that provides a real-time, network-wide views of your entire Radio Frequency environment along with floor plan editing capabilities. VRF also includes overlays on client health to help diagnose issues related to clients, floor plan, or a specific location. data to migrate VRF migration in progress
Migration of VRF data failed VRF
Migration did not complete after 2 hrs, please check the VRF logs
Migration of AMP completed successfully, VRF data not found
Migration was terminated abruptly, please retry migration
Migration of AMP completed successfully
Exception occurred during migration, please check the logs
Another system operation is active, retry after sometime
