Failing Back to the Legacy Orchestrator Primary Site

After maintenance or repair is done on the Legacy Orchestrator primary site, you may want to put it back into service. The following procedures explain how to put the Legacy Orchestrator primary site back in service.

Procedure Requirements

A. Certain procedures in this section require SSH access to the Legacy Orchestrator primary and secondary sites. To execute these procedures, you must know the skylight account credentials.

B. Other procedures require access to the Legacy Orchestrator primary and secondary sites through their web user interfaces. To execute these procedures, you must know the account credentials with an admin role to log in to the web interface.

Making a Backup of the Legacy Orchestrator Secondary Site

The data store on the Legacy Orchestrator secondary site must be backed up so that the primary site can be restored to the most current state before putting it back in service.

1. Open an SSH terminal session to the Legacy Orchestrator secondary site CLI on port 2200.

2. Log in as the skylight user.

3. Enter:

   database backup
   

   Example output:

   Skylight: database backup 
   
   Please wait ... This could take several minutes.
   Xtrabackup operating ...
   Preparing files ...
   Synchronised.
   Verifying if there is enough space...
   Compressing the backup folder ...
   Archived in DB_BAK_2026-04-22_07-51-14.tar.gz
   
   *** DATABASE BACKUP LOCAL END TIME 2026-04-22_07:51:30 ***
   

4. Note the name of the backup file that is created in the /home/skylight/so/mysql/backups directory.

5. Transfer the backup file to the /tmp directory on the primary site.

Disabling the Secondary Site as the Metrics Collection Server and SNMP Trap Receiver

1. Use a web browser to log in to the Legacy Orchestrator web interface on the secondary site.

2. Navigate to Collection → Server Configuration page.

3. Uncheck the checkbox labeled as follows:

   [ ]Use Crosswork Active Probing as default server for metrics collection

   Disabling this setting on the secondary site means that the primary site will be the default server for performance metrics collection. All Skylight devices will send their metrics data to the primary site.

4. Select Apply to apply the change.

5. Navigate to Admin → SNMP page and uncheck the following checkbox:

   [ ]Use Crosswork Active Probing as default SNMP trap receiver

   Disabling this setting on the secondary site causes all SNMP trap events coming from managed elements to be sent to the primary site.

6. Select Apply to apply the change.

Restoring the Data Store on the Legacy Orchestrator Primary Site

1. Open an SSH terminal session to the Legacy Orchestrator primary site CLI on port 2200.

2. Log in as the skylight user.

3. Stop Legacy Orchestrator software:

   services stop
   

4. Restore the latest backup database that was transferred to this site (during the procedure "Making a Backup of the Legacy Orchestrator Secondary Site" above):

   database restore <latest-backup-file-name>
   

   Example:

   database restore DB_BAK_2026-04-20_04-00-00.tar.gz
   

5. Start the Legacy Orchestrator software on the primary site:

   services start
   

Expected result: Legacy Orchestrator software is now running on the primary site.

Verifying the Switch Back to the Legacy Orchestrator Primary Site

The final step is to verify that the network inventory is correct and that the Legacy Orchestrator web interface is operational on the primary site.

1. Use a supported web browser to log in to the Legacy Orchestrator web interface on the primary site.
2. Click the logo (upper left corner of the page) to display the About Legacy Orchestrator dialog and verify the Legacy Orchestrator version.
3. Navigate to Devices > Managed Elements page and verify that the total count of Skylight devices (bottom left corner of page) is accurate.
4. Click the alarm icon (in bottom left corner) and verify that the current alarm count is accurate.
5. Navigate to Commission > Jobs page and verify that pre-existing configuration jobs are present.
6. Navigate to Collection > Reporting Status page and verify that:
   • The complete list of managed devices is displayed.
   • CSV time and Transfer time are both updated for all devices with performance data streaming enabled.

Stopping the Secondary Site

After verifying that the primary site is back in service, wait five minutes and then execute the following steps to put the secondary site back in standby mode.

Note: The wait period of five minutes allows the Metrics Collection feature to create and transmit any remaining CSV files and ensure that all PM data is available.

1. Open an SSH terminal session to the Legacy Orchestrator secondary site CLI on port 2200.

2. Log in as the skylight user.

3. Stop Legacy Orchestrator software:

   services stop