Simplified Configuration-Only Migration from a Non-Hot Standby Virtual Machine to Docker

Preparing to Migrate

This procedure provides instructions on how to migrate from one of the following releases by migrating the database only:

• Skylight orchestrator virtual machine (21.08 or later version) to Cisco Crosswork Assurance Sensor Management Docker (25.07.1-LTS)

Migration involves setting up a new Target Installation Docker that will be used to import the database configuration of the Skylight orchestrator virtual machine installation (Source Installation). This requires, at a minimum:

• A new Target Installation for Non-Hot Standby
• Ensure the hostname, IP address, NTP server, timezone, and deployment profiles are consistent between the target and source installations.

These procedures are written assuming the target installation will be hosted in a new environment with new net IP addresses. It is expected that new firewall implementations will be required to ensure the application can connect to the network and that end users can access the application interfaces.

The installation of these new Target Installation Docker is beyond the scope of this article. These procedures are already captured in the Target Installation Sensor Management Docker Deployment article and should be used when preparing for your migrating activity. The deployment profile is important to consider when installing your Target Installation Docker.

The software ships with four deployment profiles:

• 5K profile (default)
• 15K profile
• 30K profile
• 60K profile.

The profiles reference the number of network elements the system can manage. Larger profiles have larger memory, CPU, and disk requirements. The selection of the profile is dictated by the current number of network elements in your source installation.

Consult your Cisco sales engineer if you need guidance on the profile to choose for your Target Installation Docker. The deployment profile can be changed (during a maintenance window) at any time, but when doing so, adequate memory, CPU, and disk resources need to be assigned to the Docker host.

Once the Target Installation Docker is in place, with IP addresses assigned, deployment profile selected, and networking rules in place, the high-level process of migrating entails the following tasks:

1. Taking a database backup of your source installation
2. Stopping the software on your source installation
3. Importing the database backup into the target installation
4. Starting up the software on your target installation.

Migration Procedure

Source Installation Procedures

Backing up the Data Store

To rehome, a database backup of the source installation is required.

To back up and transfer the data store

1. Open an SSH terminal session to Skylight orchestrator on port 22.
2. Log in as the visionems user.
3. Change to the scripts directory by entering:

cd /opt/accedian/skylight/scripts

4. Create a backup of the data store by entering:

./ems_backup_mysql.sh -d

The backup is created and saved in the /opt/accedian/backups directory.

5. Rename the database backup file to migrate.tar.gz and transfer it to the new Legacy Orchestrator Docker (target installation) under the /tmp directory.

Stopping the Application

It is best to stop the application on the source installation while performing the migrating procedure.

To stop the application

1. Open an SSH terminal session to the Skylight orchestrator on port 2200.
2. Log in as the visionems user.
3. Stop the application by entering:

service stop app_server

Target Installation Procedures

The following procedures guide you through the database import and rebalancing process to be executed on Target Installation Docker.

Requirements

To ensure all devices are reachable on the Target Installation Docker, manually configure all settings related to the network, interface, NTP server, Hamon, and timezone (highly recommended) to match the configurations on the source virtual appliances. Refer to the Sensor Management Docker Deployment articles for more information.

Ensure the data volume(s) is configured to store all performance session data and performance metrics data.

Stopping the Target Installation Docker Services

1. Open an SSH terminal session to the Target Installation Docker CLI on port 2200.
2. Log in as the skylight user.
3. Stop services by entering:

services stop

Note: If the services are stopped, skip this step.

Importing the Database

Ensure the user 'skylight' has read access to the archive that was copied in the /tmp folder. The backup file that must be restored must be placed on the appliance file system in the /tmp directory.

To import the database

1. Open an SSH terminal session to the Target Installation CLI on port 2200.
2. Log in as the skylight user.
3. Restore the backup by entering:

database migrate <filename_of_the_backup_archive>

Note: You must only provide the filename of the archive, not the path which is assumed to be /tmp.

Starting the Target Installation Services

This procedure will start the application.

1. Open an SSH terminal session to the Target Installation CLI on port 2200.
2. Log in as the skylight user.
3. Start services by entering:

services start

(Optional) Using the Target Installation with Cisco Branding

If migrating from one of the following releases that uses the Accedian branding and want to switch to Cisco branding after completing the migration.

This procedure supports changing the Target Installation Web GUI to Cisco branding.

1. Open an SSH terminal session to the Target Installation CLI on port 22.
2. Log in as the skylight user.
3. Enter the command below:

nano docker/so.env

4. Find the PRODUCT_INFO line in the file and change it to Cisco as below:

PRODUCT_INFO=Cisco

5. Save and exit.
6. Access smcli via port 2200.
7. Stop services by entering:

services stop

8. Start services by entering:

services start

Rollback Procedure

The migrating operation can be rolled back by stopping the application on the target installation and restarting the application on the source installation.

Target Installation Procedure

This procedure will stop the application.

Stopping Target Installation Services on Non-Hot Standby Configuration

1. Open an SSH terminal session to the Target Installation CLI on port 2200.
2. Log in as the skylight user.
3. Stop services by entering:

services stop

Source Installation Procedure

This procedure will start the application.

Starting the application for Non-Hot Standby configuration

1. Open an SSH terminal session to the Legacy Orchestrator on port 2200.
2. Log in as the visionems user.
3. Start the application by entering:

service start app_server