Step 1

Download the Cisco ACI Multi-Site Orchestrator Image.

1. Browse to the Software Download link:

   https://software.cisco.com/download/home/285968390/type

2. Click ACI Multi-Site Software.

3. From the left sidebar, choose the Cisco ACI Multi-Site Orchestrator release version.

4. Download the ACI Multi-Site App Image file (Cisco-MSO-<version>.aci) for the release.

Step 2

Copy the Orchestrator image to the Application Services Engine.

# scp <app-local-path> rescue-user@<service-engine-ip>:/tmp/

# scp <app-local-path>.aci -i <pem-file-name>.pem rescue-user@<service-engine-ip>:/tmp/

Step 3

Install the Orchestrator app in your Application Services Engine.

1. Log in to any one of your Services Engine nodes as rescue-user.

   If your Cisco Application Services Engine is deployed in VMware ESX (.ova), Linux KVM (.qcow), or as a physical appliance (.iso), simply SSH in using the following command:

   # ssh rescue-user@<service-engine-ip>

   However, if your Application Services Engine is deployed in AWS and you have not enabled password-based login, you must login using the certificate (.pem file) that you created during the Application Services Engine deployment:

   # ssh -i <pem-file-name>.pem rescue-user@<service-engine-ip>

2. Verify Services Engine health.

   # acidiag health
   All components are healthy

3. Install the Orchestrator.

   In the following command, replace <application-path> with the full path to the application image you copied in the previous step.

   # acidiag app install <application-path>

   For example:

   # acidiag app install /tmp/Cisco-MSO-2.2.3.aci
   Image uploaded succesfully
   check image status using: acidiag image show cisco-mso-2.2.3.aci

   Note

   In certain cases, the Service Engine's app install command may return the following error: HTTPSConnectionPool(host='localhost', port=9090): Max retries exceeded with url: /api/v1/firmware/uploads (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x788b6e1d2f50>: Failed to establish a new connection: [Errno 111] Connection refused'). In this case, wait a couple of minutes and rerun the acidiag app install command again.

4. Verify that the application was loaded.

   Use the following command to check the operState of the application.

   While the application is loading and installing it will go through a number of operational states, which will be reflected in the operState field, for example 'operState': 'Initialize'. This process can take up to 20 minutes and you must ensure that the state changes to Disabled before proceeding to the next step.

   After the application's state changes to Disabled, make a note of the application's id, you will use it in the next step to enable the application.

   # acidiag app show
   [   {   'adminState': 'Disabled',
           'apiEntrypoint': '/query',
           'appID': 'MSO',
           'creationTimestamp': '2020-02-10T20:30:36.195960295Z',
           'description': 'Multi-Site Orchestrator application',
           'displayName': 'ACI Multi-Site Orchestrator',
           'id': 'cisco-mso:2.2.3',
           'name': 'cisco-mso',
           'operStage': 'PostInstall',
           'operState': 'Disabled',
           'schemaversion': '',
           'uiEntrypoint': '/ui/app-start.html',
           'vendorID': 'Cisco',
           'version': '2.2.3'}]

Step 4

Enable the Orchestrator app.

# acidiag app enable <app-id>

# acidiag app enable cisco-mso:2.2.3
Application enabled succesfully

Step 5

Verify that the cluster was deployed successfully.

1. Verify that the application was enabled successfully.

   While the application is being enabled, it will go through multiple operational states. You can use acidiag app show command to check the current state.

   In the following output, ensure that the highlighted fields are Enabled, Enable, and Running respectively.

   ## acidiag app show
   [   {   'adminState': 'Enabled',
           'apiEntrypoint': '/query',
           'appID': 'MSO',
           'creationTimestamp': '2020-02-10T20:30:36.195960295Z',
           'description': 'Multi-Site Orchestrator application',
           'displayName': 'ACI Multi-Site Orchestrator',
           'id': 'cisco-mso:2.2.3',
           'name': 'cisco-mso',
           'operStage': 'Enable',
           'operState': 'Running',
           'schemaversion': '',
           'uiEntrypoint': '/ui/app-start.html',
           'vendorID': 'Cisco',
           'version': '2.2.3'}]

2. Log in to the Cisco ACI Multi-Site Orchestrator GUI.

   Note	After the application is enabled as described in the previous step, it may take up to 20 additional minutes for all the Orchestrator services to start and the GUI to become available.

   After the GUI becomes available, you can access it by browsing to any one of your Application Services Engine nodes' IP addresses. The default log in is admin and the default password is We1come2msc!.

   When you first log in, you will be prompted to change the password.

Step 1

Deploy a brand new Orchestrator cluster in Application Service Engine.

Step 2

Backup existing deployment configuration.

1. Log in to your existing Cisco ACI Multi-Site Orchestrator.

2. From the left navigation pane, select Admin > Backups.

3. In the main window, click New Backup.

   A New Backup window opens.

4. In the Name field, provide the name for the backup file.

   The name can contain up to 10 alphanumeric characters, but no spaces or underscores (_).

5. Choose the Backup Location.

   You can save the backup file locally on the Orchestrator nodes or export it to a remote location.

   If you want to save the backup file locally, choose Local.

   Otherwise, if you want to save the backup file to a remote location, choose Remote and provide the following:

   • From the Remote Location dropdown menu, select the remote location.

   • In the Remote Path, either leave the default target directory or you can choose to append additional subdirectories to the path. However, the directories must be under the default configured path and must have been already created on the remote server.

6. Click Save to create the backup.

Step 3

Copy the Backup file from the existing Orchestrator.

Step 4

Bring down the existing Multi-Site Orchestrator cluster VMs.

Step 5

Import the backup file to your new Orchestrator cluster deployed on the Application Service Engine.

1. Log in to your existing Cisco ACI Multi-Site Orchestrator.

2. From the left navigation menu, select Admin > Backups.

3. In the main window, click Import.

4. In the Import from file window that opens, click Select File and choose the backup file you want to import.

   Importing a backup will add it to the list of the backups displayed the Backups page.

1. Log in to your Cisco ACI Multi-Site Orchestrator.

2. From the left navigation pane, select Admin > Remote Locations.

3. In the top right of the main window, click Add Remote Location.

   An Add New Remote Location screen appears.

4. Provide the same information for the remote location that you used in your old Orchestrator.

5. Click Save to add the remote server.

Step 6

Restore the configuration.

1. From the left navigation menu, select Admin > Backups.

2. In the main window, click the actions () icon next to the backup you want to restore and select Rollback to this backup.

   If the version of the selected backup is different from the running Multi-Site version, the rollback could cause a removal of the features that are not present in the backup version.

3. Click Yes to confirm that you want to restore the backup you selected.

   If you click Yes, the system terminates the current session and the user is logged out.