Migrate from Hot Standby VM to Sensor Management Docker

Preparing to Migrate

This procedure provides instructions on how to migrate from one of the following releases while preserving session data:

• Skylight orchestrator virtual machine Hot Standby (23.12 or prior version) to the same version of Legacy Orchestrator Docker Hot Standby
• Skylight orchestrator virtual machine Hot Standby (23.12 or 23.12.1 version) to Legacy Orchestrator Docker Hot Standby (24.09 or 24.09.1)
• Skylight orchestrator virtual machine Hot Standby (23.12.3 or 23.12.4 version) to Cisco Crosswork Assurance Sensor Management Docker Hot Standby (25.07.1-LTS)

Terminology

Throughout this document, the following terms are used:

• Source Installation: The existing Skylight orchestrator virtual machine deployment from which data, configuration, and system settings are migrated.

• Target Installation: The destination Docker-based deployment to which the migration is performed. Depending on the migration path, the target installation may refer to:

  • Legacy Orchestrator Docker (24.09 or 24.09.1)
  • Cisco Crosswork Assurance Sensor Management Docker (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 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. Transferring all resync DAT files on each mediation folder to your target installation
4. Transferring the performance session data to your target installation
5. Importing the database backup into the target installation
6. Starting up the software on your target installation.

Before starting the migration process, follow the steps below to ensure there is no offline data (all Resync DAT files) on the source installation.

To ensure there is no offline data on the source installation:

1. Open an SSH terminal session to Skylight orchestrator on port 22.
2. Log in as the visionems user.
3. Run the following command:

find /data/medn*instance/s*/ -type f -name "*RESYNC*" | wc -l

If the output is 0, it indicates there is no offline data.

Otherwise, offline data exists in the virtual machine. In this case, you must wait for the virtual machine to process all offline data by generating the CSV file and sending all CSV files to the SFTP/Rsync destination. If this step is not completed, the offline data will be lost during the migration.

Note: Once the migration is complete, the Legacy Orchestrator Docker 24.09 or later application will continue to generate and handle live and offline data files correctly, even without any old offline data files.

Migration Procedure

Source Installation Procedures

Precondition

Before performing the migration process, add the Internal License Server key to the source installation.

To import an Internal License Server key

Note: From release 23.04, all activation keys are preinstalled by default. Skip this procedure if using Skylight orchestrator 23.04.

1. Obtain the appropriate key file from Technical Support.
2. Save the key file on the local file system (for example, on the desktop) and extract this file.
3. Access the Admin ▶ Feature Activation page.
4. Click the Choose File button.
5. Select the Internal License Server key file on your local file system from the file selector dialog.
6. Click the Import button.

Backing up the Data Store

In order 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. Backup 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 the /tmp directory on both sites of the new Target Installation Docker Hot Standby.

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

Transferring All Resync DAT Files

When migrating from the Skylight orchestrator virtual machine (version 23.12 or prior) to Docker of the same version, follow these steps to ensure the historical performance monitoring data is preserved and transferred to the target installation.

Note: The destination for transferring all resync DAT files should be a preferred site.

To transfer Resync DAT files

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

For Virtual Machine version 23.04.1 or prior

cd /data
rsync -R -v medn1instance/datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation1>

cd /data/medn2instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation2>

cd /data/medn3instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation3>

cd /data/medn4instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation4>

cd /data/medn5instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation5>

cd /data/medn6instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation6>

cd /data/medn7instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation7>

cd /data/medn8instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation8>

cd /data/medn9instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation9>

cd /data/medn10instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation10>

cd /data/medn11instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation11>

cd /data/medn12instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation12>

Transferring the Performance Session Data

To preserve the historical performance session data, it must be transferred over to the target installation by following these steps.

Note: The destination for Performance Session Data files should be a preferred site.

To transfer performance session data

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

rsync -av /data/sdmm skylight@x.x.x.x:/<directory>

Where x.x.x.x is the IP address of the target installation.

Where < directory > is the bizn1instance directory under so-data volume.

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, timezone (highly recommended), etc., 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. If migrating from Skylight orchestrator virtual machine (23.12 or prior version) to the Legacy Orchestrator Docker of the same version, restore the backup by entering:

database restore <filename_of_the_backup_archive>

OR

3. If migrating from the Skylight orchestrator virtual machine (23.12 or 23.12.1 version) to the Legacy Orchestrator Docker 24.09 or 24.09.1 version, restore the backup by entering:

database migrate <filename_of_the_backup_archive>

OR

3. If migrating from the Skylight orchestrator virtual machine (23.12.3 or 23.12.4 version) to the Cisco Crosswork Assurance Sensor Management Docker 25.07.1-LTS version, 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 'Transferring All Resync DAT Files' and 'Transferring the Performance Session Data' 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 (23.12 or prior version) to the same version of Docker
• Skylight orchestrator virtual machine Hot Standby (23.12 or 23.12.1 version) to Legacy Orchestrator Docker Hot Standby (24.09 or 24.09.1)
• Skylight orchestrator virtual machine Hot Standby (23.12.3 or 23.12.4 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 where you 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