Upgrading to Legacy orchestrator Docker 24.09

IMPORTANT

Please note that documentation for versions before 24.09 release has been relocated to the Legacy Products and Documentation category.

This Legacy orchestrator Docker Upgrade article includes procedures that will help the personnel of mobile network operators, Cable Multi-Service Operators (MSOs), business service providers, and cloud and data center services upgrade and maintain their performance assurance solutions.

Specifically, this article explains how to upgrade the Legacy orchestrator Docker to version 24.09 from any of the following previously-installed versions. It includes support for both Ubuntu and Red Hat operating systems.

Docker running:

• 23.04 5K profile
• 23.04 15K profile
• 23.04 30K profile
• 23.04 60K profile
• 23.04.1 5K profile
• 23.04.1 15K profile
• 23.04.1 30K profile
• 23.04.1 60K profile
• 23.12 5K profile
• 23.12 15K profile
• 23.12 30K profile
• 23.12 60K profile

---

Note: The Red Hat operating system does not support Skylight orchestrator Docker 23.04.1.

---

Prior installation data and configuration information is retained during the upgrade process.

Pre-Upgrade Requirements and Procedures

This section describes the requirements and procedures that must be followed before performing an upgrade.

The following sections cover the procedures for upgrading a Docker host running Skylight orchestrator 23.04, Skylight orchestrator 23.04.1 or Skylight orchestrator 23.12 software on the Docker host. During the upgrade, the system will be unavailable for approximately 90 minutes.

Before performing the upgrade procedures, you must read through the Release Notes for Legacy orchestrator 24.09.

---

WARNING: If you are using Provider Connectivity Assurance, the Sensor Collector component must be upgraded to the latest release before upgrading to Legacy orchestrator Docker 24.09. Please contact the Provider Connectivity Assurance support team to verify that your Sensor Collector version is compatible with Legacy orchestrator Docker 24.09.

---

Requirements

You must ensure you have the following items before starting the upgrade procedure. If you are missing anything, contact Technical Support.

1. SSH client (such as PuTTY)
2. SCP client (such as WinSCP)
3. The Docker host must have over 25 GiB of free space for Docker images.
4. The Docker host must have 15 GiB of free space for the temporary folder used during the installation.
5. One user must have sudo privileges or root access on the Docker host.
6. The multipath tool (multipath-tools package) must have been installed on the host.
7. To upgrade to version 24.09, you must have access to the following package file:

   Skylight-orchestrator-24.09-GA_4_docker-dist-cisco-24.09-GA-4

8. Check and ensure the current deployment profile matches with resource requirements (vCPU, RAM, disk). Please refer to the Docker Deployment Profile Configuration and Docker Disk Configuration articles for additional information

Pre-Upgrade Procedures

This section explains the procedures that must be performed before upgrading to version 24.09.

The pre-upgrade procedures are:

1. Backing up the Data Store
2. Transferring file to the Docker host that deployed Legacy orchestrator Docker
3. If operating in a Hot Standby configuration, stop the redundancy feature

Backing up the Data Store

A database backup of the system is needed.

Requirement:

Legacy orchestrator services must be started.

To back up the mysql database

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
2. Log in as the skylight user.
3. Create a backup of the data store by entering:

database backup

---

Notes:

On the Non-Hot Standby configuration system, the backup is generated as a tar.gz file in the folder ‘backups’ of the ‘so-mysql’ volume.

On the Hot Standby configuration system:

• The backup must be taken from the active site.
• The backup is generated as a tar.gz file in the folder '/home/skylight/so/mysql-ha/backups'

---

Transferring File to the Docker host which deployed the Legacy orchestrator Docker

This procedure explains how to install the required upgrade script to the appropriate location.

The following upgrade file must be available:

• Skylight-orchestrator-24.09-GA_4_docker-dist-cisco-24.09-GA-4

To transfer file

The procedure must be executed by the skylight user.

1. From your computer, use an SCP client (such as WinSCP) and the skylight user to transfer the required file to the /home/skylight folder.

---

CAUTION: The location of the required file must be /home/skylight.

---

If operating in a Hot Standby configuration, stop the redundancy feature

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
2. Log in as the skylight user.
3. Stop the redundancy feature process by entering:

redundancy control stop

---

Note: Redundancy feature can be stopped on both sites by running above command on a site only.

---

Upgrading Legacy orchestrator Docker

This procedure contains instructions on how to upgrade to Legacy orchestrator Docker 24.09.

---

Note: If you are running a redundant configuration, this procedure must be executed on each virtual appliance of the redundant pair.

---

Removing the Older Version Before Upgrading

---

Notes:

Skip this step if the current Legacy orchestrator Docker is NOT upgraded from any previous version.

The older version must be removed before upgrading to free up disk space on the Docker host.

---

To remove the older version before upgrading

1. Open an SSH terminal session to port 22 of the appliance, log in to the appliance with one user having sudo privileges or root access on the host.

2. Execute the script that removes the older version:

sudo sh /home/skylight/Skylight-orchestrator-24.09-GA_4_docker-dist-cisco-24.09-GA-4 -c

If prompted, provide the password of the user having sudo privileges or root access on the host.

---

Note: Continue to the “Upgrading to the New Software Version” section if the “No previous version of Legacy orchestrator to commit all changes. Exiting.” message is returned.

---

3. When prompted enter:

y

=========================================================================================
Committing all changes of Skylight orchestrator 24.09-GA and cleaning up Skylight orchestrator 23.12-GA
Unable to rollback to Skylight orchestrator 23.12-GA after this action

=========================================================================================
Proceed ? (y/N)
y
Remove Skylight orchestrator images version 23.12-GA

[ . . . ]

Remove origin folder and data of Skylight orchestrator version 23.12-GA
Successfully cleaned up Skylight orchestrator system version 23.12-GA

Upgrading to the New Software Version

This procedure will install the upgraded software.

To upgrade to the new software

1. Open an SSH terminal session to port 22 of the appliance, log in to the appliance with one user having sudo privileges or root access on the host.
2. Execute the script that does the partition upgrade:

sudo sh /home/skylight/Skylight-orchestrator-24.09-GA_4_docker-dist-cisco-24.09-GA-4

If prompted, provide the password of the user having sudo privileges or root access on the host.

3. When prompted enter:

y

Upgrade Skylight orchestrator version 23.12-GA to 24.09-GA
Proceed ? (y/N)
y
Validate mysql disk space for upgrade
Mysql disk space already to backup database
Stop Skylight orchestrator services version 23.12-GA
Backup database
Backup java for rollback

Install Skylight orchestrator version 24.09-GA

=========================================================================================

Installing Skylight orchestrator 24.09-GA (build 1-3934a3d)

=========================================================================================

4. When prompted enter:

y

Proceed ? (y/N)
y

5. Type the temporary installation folder to extract the Docker images or type enter to accept default: /tmp folder

Temporary installation folder? [enter to accept default: /tmp]
/tmp

Checking requirements ...

Requirements are ok.

Extracting installation package to /tmp/so_install ...

Please wait ...

Installation package extracted to /tmp/so_install .

Importing Skylight orchestrator distribution docker images from /tmp/so_install/docker_images.tar ...
b40ed86654e5: Loading layer 75.15MB/75.15MB
8dbe5f6a3a6e: Loading layer 115.9MB/115.9MB
[...]
Loaded image: so-drbd9-focal:24.09-GA

Setup user:group skylight:skylight ...
Found group 'skylight'
skylight:x:2000:

Found user 'skylight'
skylight:x:2000:2000:Skylight orchestrator:/home/skylight:/bin/bash

user:group skylight:skylight are created.

Resetting the main user in Skylight orchestrator containers to host UID and GID

Resetting 'so-mysql' container user to host UID and GID
Sending build context to Docker daemon 8.704kB
[...]
Successfully built c4c94bc55804
Successfully tagged so-ha:23.12-GA
Untagged: so-ha:23.12-GA-distro

Skylight orchestrator images installed
REPOSITORY TAG IMAGE ID CREATED SIZE
so-ha 23.12-GA c4c94bc55804 1 second ago 880MB
so-export 23.12-GA bd25f964c42e 3 seconds ago 252MB
so-core 23.12-GA b8eeefc85955 6 seconds ago 6.19GB
so-med 23.12-GA a24f3cfecd1a 56 seconds ago 4.48GB
so-nbi 23.12-GA e9640d899cd1 About a minute ago 4.48GB
so-mysql 23.12-GA a69b77268f50 2 minutes ago 8.31GB

Setup Skylight orchestrator configuration ...

Skylight orchestrator configuration is setup.

Installing Skylight orchestrator files and folders ...

Skylight orchestrator files and folders are created.

Setup Skylight orchestrator docker volumes...
Setup so-config volume...
so-config
so-config

Skylight orchestrator docker volumes are setup.

Setup the network for Skylight orchestrator docker containers...
Found network 'so-network'

[
  {
   "Name": "so-network",
   "Id": "3fe5c18c48cfd9aa3afdb445f861cd0f76e84720c36dfa53ad3eb1840c06a304",
   "Created": "2022-07-19T08:23:13.970164575Z",
   "Scope": "local",
   "Driver": "bridge",
   "EnableIPv6": true,
   "IPAM": {
      "Driver": "default",
       "Options": {},
       "Config": [
          {
            "Subnet": "172.18.0.0/24",
            "Gateway": "172.18.0.1"
          },
          {
           "Subnet": "fd00:1::/80",
           "Gateway": "fd00:1::1"
          }
       ]
    },
    "Internal": false,
    "Attachable": false,
    "Ingress": false,
    "ConfigFrom": {
       "Network": ""
    },
    "ConfigOnly": false,
    "Containers": {},
    "Options": {},
    "Labels": {}
   }
]

Starting HA docker container by default...

Creating so-ha-24.09-GA ... done

HA docker container started.

Removing the temporary installation folder /tmp/so_install ...

=================================================================================================================

The installation of Skylight orchestrator 24.09-GA (build 1-3934a3d) is complete.

To manage Skylight orchestrator, run:

/usr/bin/socli.sh

=================================================================================================================

Import data upgrade version 24.09-GA
Upgrade database schema for Skylight orchestrator version 24.09-GA
Creating so-mysql-24.09-GA ... done
Successfully upgraded the database schema
Stopping so-mysql-24.09-GA ... done
Removing so-mysql-24.09-GA ... done
Going to remove so-mysql-23.12-GA
Import 'skylight' certificate into the keystore for Skylight orchestrator version 24.09-GA

=========================================================================================

Skylight orchestrator version 24.09-GA upgrade process was successful

=========================================================================================

Post-Installation Procedures

This section explains the procedures applicable after your upgrade.

The post-installation procedures are:

1. Reconfiguring the med-ip(s)
2. Configuring Mediation Volumes
3. Restarting the Legacy orchestrator services
4. Post-Upgrade Checks

Reconfiguring the med-ip(s)

---

Notes: Skip this procedure if upgrading from Skylight orchestrator Docker 23.12.

This procedure to reconfigure the med-ip(s) is before upgrading. This procedure can be skipped if the user does not want a specific configuration.

---

Reconfigure the med-ip(s) for a Hot Standby configuration

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.

3. Reconfigure the med-ip(s) for the Legacy orchestrator Docker:

config set network med-ip mediation <Y> <Z>

Where:

• Y is a mediation number from 1-6.
• Z is the IP address in IPv4 or IPv6 format (the IPs must exist on the Docker host).

Example:

Skylight: config set network med-ip mediation 2 10.220.199.234
Removing existing Skylight orchestrator containers ...
IP address has been set to: [10.220.199.234]

4. Verify med-ip configuration by entering:

config show

Example:

Skylight: config show 

network subnet = ["172.18.0.0/24" "fd00:1::/80" ] - ipv6enabled = "true"
network core-ip = 
network core-http-port = 80
network core-https-port = 443
network medn1-ip = 10.220.199.234
network medn2-ip = 10.220.199.234
network medn3-ip = 10.220.199.234
network medn4-ip = 10.220.199.234
network medn5-ip = 10.220.199.234
network medn6-ip = 10.220.199.234
network med-snmp-port = 1163
volume-location so-config = /home/skylight/so/config
volume-location so-mysql = /home/skylight/so/mysql
volume-location so-data = /home/additional-disk/sdb/mediation1
volume-location so-logs = /home/skylight/so/logs
volume-location so-data-medn2instance = /home/additional-disk/sdc/mediation2
volume-location so-data-medn3instance = /home/additional-disk/sdc/mediation3
volume-location so-data-medn4instance = /home/additional-disk/sdd/mediation4
volume-location so-data-medn5instance = /home/additional-disk/sde/mediation5
volume-location so-data-medn6instance = /home/additional-disk/sde/mediation6

---

Note: These steps must be run on both sites of the redundant pairs.

---

Reconfigure the med-ip(s) for a Non-Hot Standby configuration

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.

3. Reconfigure the med-ip(s) for the Legacy orchestrator Docker:

config set network med-ip mediation <Y> <Z>

Where:

• Y is a mediation number from 1-6.
• Z is the IP address in IPv4 or IPv6 format (the IPs must exist on the Docker host).

Example:

Skylight: config set network med-ip mediation 2 10.220.199.234
Removing existing Skylight orchestrator containers ...
IP address has been set to: [10.220.199.234]

4. Verify med-ip configuration by entering:

config show

Example:

Skylight: config show 

network subnet = ["172.18.0.0/24" "fd00:1::/80" ] - ipv6enabled = "true"
network core-ip = 
network core-http-port = 80
network core-https-port = 443
network medn1-ip = 10.220.199.234
network medn2-ip = 10.220.199.234
network medn3-ip = 10.220.199.234
network medn4-ip = 10.220.199.234
network medn5-ip = 10.220.199.234
network medn6-ip = 10.220.199.234
network med-snmp-port = 1163
volume-location so-config = /home/skylight/so/config
volume-location so-mysql = /home/skylight/so/mysql
volume-location so-data = /home/additional-disk/sdb/mediation1
volume-location so-logs = /home/skylight/so/logs
volume-location so-data-medn2instance = /home/additional-disk/sdc/mediation2
volume-location so-data-medn3instance = /home/additional-disk/sdc/mediation3
volume-location so-data-medn4instance = /home/additional-disk/sdd/mediation4
volume-location so-data-medn5instance = /home/additional-disk/sde/mediation5
volume-location so-data-medn6instance = /home/additional-disk/sde/mediation6

Configuring Mediation Volumes

From release 23.12, the structure folder of mediations has been changed. Therefore, the mediation volumes must be configured after upgrading.

---

Note: Skip this section if the deployment profile is a single mediation instance (5K profile) or upgrading from Skylight orchestrator Docker 23.12.

---

Mediation(s) volumes configuration must be followed per the table below:

Profile Name	Total Mediation(s) / Additional Disk(s)	Mapping Mediation(s) per Additional Disk(s)
5K	1 mediation / 0 disk	Mediation 1 on OS of Docker host disk
15K	2 mediations / 1 disk	Mediation 1 and 2 on additional disk 1
30K	3 mediations / 2 disks	Mediation 1 on additional disk 1 Mediation 2 and 3 on additional disk 2
60K	6 mediations / 4 disks	Mediation 1 on additional disk 1 Mediation 2 and 3 on additional disk 2 Mediation 4 on additional disk 3 Mediation 5 and 6 on additional disk 4

Configure mediation volumes for a Hot Standby configuration

For Mediation 1

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.

3. Configure volume data for new mediation by entering:

config set volume-location data so-data <X>

Where:

• X is an absolute path for the location created for data volume.

Example:

config set volume-location data so-data /home/additional-disk/sdb/mediation1

---

Note: These steps must be run on both sites of the redundant pairs.

---

For other mediations

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
2. Log in as the skylight user.
3. Configure volume data for new mediation by entering:

config set volume-location data mediation <Y> <Z>

Where:

• Y is a mediation number from 2-6.
• Z is an absolute path for the location created for data volume.

Example:

config set volume-location data mediation 2 /home/additional-disk/sdc/mediation2
config set volume-location data mediation 3 /home/additional-disk/sdc/mediation3
config set volume-location data mediation 4 /home/additional-disk/sdd/mediation4
config set volume-location data mediation 5 /home/additional-disk/sde/mediation5
config set volume-location data mediation 6 /home/additional-disk/sde/mediation6

---

Note: These steps must be run on both sites of the redundant pairs.

---

Configure mediation volumes for a Non-Hot Standby configuration

For Mediation 1

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.

3. Configure volume data for new mediation by entering:

config set volume-location data so-data <X>

Where:

• X is an absolute path for the location created for data volume.

Example:

config set volume-location data so-data /home/additional-disk/sdb/mediation1

For other mediations

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.

3. Configure volume data for new mediation by entering:

config set volume-location data mediation <Y> <Z>

Where:

• Y is a mediation number from 2-6.
• Z is an absolute path for the location created for data volume.

Example:

config set volume-location data mediation 2 /home/additional-disk/sdc/mediation2
config set volume-location data mediation 3 /home/additional-disk/sdc/mediation3
config set volume-location data mediation 4 /home/additional-disk/sdd/mediation4
config set volume-location data mediation 5 /home/additional-disk/sde/mediation5
config set volume-location data mediation 6 /home/additional-disk/sde/mediation6

Restarting the Legacy orchestrator services

This procedure will start the upgraded software.

Restarting the Legacy orchestrator services for Hot Standby configuration

1. Open an SSH terminal session to the Legacy orchestrator CLI designated as the preferred active site on port 2200.

2. Log in as the skylight user.

3. Configure the preferred site to last active site, enter:

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

Restarting the Legacy orchestrator services for a Non-Hot Standby configuration

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.

3. Start services by entering:

services start

4. When prompted enter:

y

---

Note: It may take up to 10 minutes for the Legacy orchestrator services to be healthy.

---

Verifying the Startup Status

To verify the startup status

1. Enter:

services status

A list of services that are currently running is displayed.
Ensure that the state of all services is shown as healthy.

2. Close the terminal session to port 2200 by entering:

exit

Post-Upgrade Checks

The final step of the upgrade is to check the network inventory and ensure that Legacy orchestrator Docker is operational. The following steps constitute a basic verification of the state of Skylight orchestrator.

To verify network inventory and check Legacy orchestrator functionality

1. Log in to the Legacy orchestrator web application in a supported web browser.

2. Click the Cisco icon to display the About window.
   The Build Version should indicate version 24.09.

3. Access the Device ▶ Managed Elements tab and verify that the total count of network elements at the bottom-left corner is accurate.

4. Click the icon at the bottom-right corner and verify that the current alarm count is accurate.

5. Access the Commission ▶ Jobs tab and verify that any pre-existing configuration jobs are still present.

6. Access the Collection ▶ Reporting Status tab and verify the following:

   • The list of performance elements with a pm collect agent.
   • The CSV time and Transfer time have both recently been updated for all elements with streaming enabled.

7. Check your session status by accessing Sessions tab.

Rollback Procedure

This section explains how to roll back to the original operating system partition and restore the system to its initial state.

If you must roll back a cluster deployment, you must repeat the procedure on all appliances on which the upgrade was performed (successfully or unsuccessfully).

Rollback for Legacy orchestrator Procedure

This procedure explains how to roll Legacy orchestrator back to the previous release.

You would only need to perform the rollback procedure if problems occur during the appliance upgrade procedure, such as:

• An error message occurs during the upgrade process that prevents you from proceeding.
• The upgrade process terminates unexpectedly.
• The application does not function as expected after the upgrade.

Procedure Requirements

The following requirement applies to the procedure:

1. This procedure must be executed with one user having sudo privileges or root access on the host.

If operating in a Hot Standby configuration, stop the redundancy feature

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.

3. Stop the Hot Standby process by entering:

redundancy control stop

---

Note: Redundancy feature can be stopped on both sites by running above command on a site only.

---

Rolling back the upgrade

Repeat this procedure on all appliances that were upgraded.

To roll back the upgrade

1. Using an SSH terminal session to port 22 of the appliance, log in to the appliance with one user having sudo privileges or root access on the host.

2. Execute the script that does the partition upgrade:

sudo sh /home/skylight/Skylight-orchestrator-24.09-GA_4_docker-dist-cisco-24.09-GA-4 -r

If prompted, provide the password of the user having sudo privileges or root access on the host.

3. When prompted enter:

y

Proceed ? (y/N)
y
Stop Skylight orchestrator version 24.09-GA
Removing image so-mysql:24.09-GA ...
Untagged: so-mysql:24.09-GA
Deleted: sha256:106f366acdfcc01ab086a4c16082deee7e4b38b1fd797cf8d6e44c17c1b8909a
Deleted: sha256:01e3bb19ce4fce80d8b2ceecf74d022e0edcb3832fe827351f05046d09f3d9dd
Deleted: sha256:b04590d7f551c4962e26031415b13b1e5f823926163e41c932be70eb5482c164
[...]

=========================================================================================

Skylight orchestrator rollback process was successful.

=========================================================================================

4. Configure mediation volumes. From Skylight orchestrator 23.12, the structure folder of mediations has been changed. Therefore, the mediation volumes must be configured after rollback.

   ---

   Note: Skip this section if the deployment profile is a single mediation instance (5K profile) or upgrading from Skylight orchestrator Docker 23.12.

   ---

Mediation(s) volumes configuration must be followed per the table below:

Profile Name	Total Mediation(s) / Additional Disk(s)	Mapping Mediation(s) per Additional Disk(s)
5K	1 mediation / 0 disk	Mediation 1 on OS of Docker host disk
15K	3 mediations / 1 disk	Mediation 1, 2 and 3 on additional disk 1
30K	6 mediations / 2 disks	Mediation 1, 2 and 3 on additional disk 1 Mediation 4, 5 and 6 on additional disk 2
60K	12 mediations / 4 disks	Mediation 1, 2 and 3 on additional disk 1 Mediation 4, 5 and 6 on additional disk 2 Mediation 7, 8 and 9 on additional disk 3 Mediation 10, 11 and 12 on additional disk 4

Configure mediation volumes for a Hot Standby configuration

For Mediation 1

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.

3. Configure volume data for new mediation by entering:

config set volume-location data so-data <X>

Where:

• X is an absolute path for the location created for data volume.

Example:

config set volume-location data so-data /home/additional-disk/sdb/mediation1

---

Note: These steps must be run on both sites of the redundant pairs.

---

For other mediations

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
2. Log in as the skylight user.
3. Configure volume data for new mediation by entering:

config set volume-location data mediation <Y> <Z>

Where:

• Y is a mediation number from 2-12.
• Z is an absolute path for the location created for data volume.

Example:

config set volume-location data mediation 2 /home/additional-disk/sdb/mediation2
config set volume-location data mediation 3 /home/additional-disk/sdb/mediation3
config set volume-location data mediation 4 /home/additional-disk/sdc/mediation4
config set volume-location data mediation 5 /home/additional-disk/sdc/mediation5
config set volume-location data mediation 6 /home/additional-disk/sdc/mediation6

---

Note: These steps must be run on both sites of the redundant pairs.

---

Configure mediation volumes for a Non-Hot Standby configuration

For Mediation 1

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.

3. Configure volume data for new mediation by entering:

config set volume-location data so-data <X>

Where:

• X is an absolute path for the location created for data volume.

Example:

config set volume-location data so-data /home/additional-disk/sdb/mediation1

For other mediations

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.

3. Configure volume data for new mediation by entering:

config set volume-location data mediation <Y> <Z>

Where:

• Y is a mediation number from 2-12.
• Z is an absolute path for the location created for data volume.

Example:

config set volume-location data mediation 2 /home/additional-disk/sdb/mediation2
config set volume-location data mediation 3 /home/additional-disk/sdb/mediation3
config set volume-location data mediation 4 /home/additional-disk/sdc/mediation4
config set volume-location data mediation 5 /home/additional-disk/sdc/mediation5
config set volume-location data mediation 6 /home/additional-disk/sdc/mediation6

Restarting the Legacy orchestrator services

This procedure will start the upgraded software.

Restarting the Legacy orchestrator services for Hot Standby configuration

1. Open an SSH terminal session to the Legacy orchestrator CLI designated as the preferred active site on port 2200.

2. Log in as the skylight user.

3. Configure the preferred site to last active site, enter:

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

Restarting the Legacy orchestrator services for a Non-Hot Standby configuration

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.

3. Start services by entering:

services start

4. When prompted enter:

y 

---

Note: It may take up to 10 minutes for the Legacy orchestrator services to be healthy.

---