Failing Back to the Primary Appliance

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

Making a Backup of the Secondary Appliance

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

1. Using a console, log in to the secondary appliance as the visionems user.

2. Make a backup as follows:
   Enter: shell
   You are brought to the appliance’s OS-level shell.
   Enter the user ID and password for the visionems user.
   Enter: cd /opt/accedian/skylight/scripts
   Enter: ./ems_backup_mysql.sh

3. Note the name of the backup file that is created in the /data/backups directory.

4. Transfer the backup file to the /data/backups directory on the primary appliance.

Disabling Secondary as Metrics Collection Server and SNMP Trap Receiver

1. Using a web browser, log in to the Skylight orchestrator web interface on the secondary appliance.

2. Access the Collection ▶ Server Configuration page in the Skylight orchestrator web interface on the appliance.

3. Uncheck the checkbox labeled as follows:
   Use Skylight orchestrator as default server for metrics collection
   Disabling this setting on the secondary appliance means that the primary appliance will be the default server for performance metrics collection. All Skylight devices will send their metrics data to the primary appliance.

4. Access the SNMP fault receiver configuration in Admin ▶ SNMP page:
   Use Skylight orchestrator as default SNMP trap receiver
   Disabling this setting on the secondary appliance causes all SNMP trap events coming from managed elements to be sent to the primary appliance.

Restoring the Data Store on the Primary Appliance

1. Log in on the console of the primary appliance as the visionems user.

2. Enter: service stop app_server

3. Restore the backup that was transferred to the appliance (during the procedure Making a Backup of the Secondary Appliance.

4. Here is a typical filename for an automatic data store backup file:
   DB_BAK_2021-12-21_14:05:01.tar.gz,

5. Enter the following command: shell
   You are brought to the appliance’s OS-level shell.

6. Enter the username and password for the visionems user.

7. Enter the following commands:
   cd /opt/accedian/skylight/scripts
   ./ems_restoredb_mysql.sh /data/backups/DB_BAK_timestamp.tar.gz

8. Exit.

9. Enter: service start app_server

The application starts on the primary appliance.

Verifying the Switch Back to the Primary Appliance

The final step is to verify that the network inventory is correct and that the Skylight orchestrator web interface is operational on the primary appliance.

1. Using a supported web browser, log in to the Skylight orchestrator web interface on the primary appliance.

2. Click the Skylight orchestrator icon to display the About Skylight orchestrator dialog and check that the BuildVersion is the latest.

3. Select the Devices ▶ Managed Elements page and verify that the total count of devices (in the bottom left corner) is accurate.

4. Click the icon (bottom left corner of page) and verify current alarm count is accurate.

5. Select the Commission ▶ Jobs page and verify pre-existing configuration jobs are present.

6. Select the 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 Appliance

After you have verified that the primary appliance is back in service, wait five minutes and then execute the following steps to put the secondary appliance back in standby mode.

1. Using a console, log in as the visionems user on the secondary appliance.

2. Enter the following command: service stop app_server