Simplified Configuration-Only Migration from a 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 Hot Standby (21.08 or later version) to Cisco Crosswork Assurance Sensor Management Docker Hot Standby (25.07.1-LTS)

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

• The new Target Installation Docker Hot Standby system must possess a unique MAC address and a valid Hot Standby license for operation. Refer to Introduction to Hot Standby Redundancy.
• Ensure the hostname, IP address, NTP server, timezone, and deployment profiles are consistent between the Target and Source Installations.

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

The installation of these new Target Installation Dockers 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 must be assigned to the Docker host.

After setting up Docker, assigning IP addresses, selecting the deployment profile, and configuring networking rules, the high-level migration process involves 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 for Skylight orchestrator Virtual Machine Hot Standby

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. Back up the database by entering:

/opt/accedian/skylight/scripts/ems_backup_mysql.sh

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

4. Rename the database backup file to migrate.tar.gz and transfer it to both sites of the new Legacy Orchestrator Docker Hot Standby to the /tmp directory.

Stopping the Hot Standby process

To stop the Hot Standby process

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

redundancy control stop

Target Installation Procedures

The following procedures guide you through the database import and rebalancing process to be executed on the 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 Docker Deployment articles for more information.

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

Stopping Hot Standby Process on the Active Site

Note: If the redundant systems are stopped, skip this step.

Active Site

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

redundancy control stop

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.

Note: These steps must be run on the target installation virtual appliance you have designated to be the preferred or active site.

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 Application for Hot Standby Configuration

1. Open an SSH terminal session to the Target Installation designated as the preferred active site on port 2200.
2. Log in as the skylight user.
3. Configure the preferred site, the site which transferred the files at 'To back up and transfer the data store' steps, enter:

redundancy config preferred {site-a | site-b}

4. Start the Hot Standby process by entering:

redundancy control start

5. Verify redundancy status, enter:

redundancy show status

(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:

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

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

Note: This procedure must run on the preferred or active site.

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 the Hot Standby process by entering:

redundancy control stop

8. Configure the preferred site, the site which changed the so.env file:

redundancy config preferred {site-a | site-b}

9. Start the Hot Standby process by entering:

redundancy control start

10. Verify redundancy status, enter:

redundancy show status

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 Hot Standby Process and Target Installation Services on Hot Standby Configuration

Active Site

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

redundancy control stop

Source Installation Procedure

This procedure will start the application.

Starting the application for Hot Standby configuration

1. Open an SSH terminal session to the Skylight orchestrator designated as the preferred active site on port 2200.
2. Log in as the visionems user.
3. Configure the preferred site to the last active site by entering:

redundancy config preferred {site-a | site-b}

4. Start the Hot Standby process by entering:

redundancy control start

5. Verify redundancy status by entering:

redundancy show status