Transferring the Deployment Configuration from the First MHO-200 in Gaia Clish

Complete the First Time Configuration Wizard on all additional Orchestrators and reboot them.

After you configure the first Orchestrator, all additional Orchestrators in the deployment must join it.

You can join additional Orchestrators in Gaia Portal (see Step 2: Run the First Time Configuration Wizard on Each Additional Orchestrator MHO-200) or in Gaia Clish (with the command join maestro deployment).

  1. On the first Orchestrator, export the deployment configuration:
    1. Connect to the command line on the first Orchestrator.
    2. Log in.
    3. Export the deployment configuration: 
      export maestro deployment to-file /home/admin/<filename>
      Note:

      1. The export wizard automatically appends the file extension .enc to the filename you specify.

      2. The export wizard automatically encrypts the exported configuration file and shows the Deployment Security Key (6-word passphrase) on the screen.

        Warning:

        • Treat this Deployment Security Key and the exported configuration file as sensitive credentials. The file is encrypted, but the key required to use it should be stored securely and shared only with authorized personnel performing the deployment.

        • This Deployment Security Key (passphrase) appears only one time. It is not possible to show it again later.

      3. The export wizard automatically MD5 checksum for the exported file.
  2. On each additional Orchestrator, import the deployment configuration:
    1. Copy the exported configuration file to each additional Orchestrator.
      Note:

      To copy a file to an Orchestrator over the SCP, you must connect with a user, whose default shell is /bin/bash.

      1. Connect to the command line on each additional Orchestrator.

      2. Log in to Gaia Clish.

      3. Configure the default shell /bin/bash for the user admin:

        set user admin shell /bin/bash

      4. On the first Orchestrator, copy the file to each additional Orchestrator:

        scp /home/admin/<filename>.enc admin@<IPv4 Address of Mgmt Interface>:/home/admin/

      5. On each additional Orchestrator, configure the default shell /etc/cli.sh:

        set user admin shell /etc/cli.sh
    2. Connect to the command line on each Orchestrator.
    3. Log in to Gaia Clish.
    4. Join the first Orchestrator: 
      join maestro deployment from-file /home/admin/<filename>.enc

      The wizard:

      1. Prompts for the Deployment Security Key generated during the export.

      2. Shows a warning that the import will overwrite all existing deployment configuration on this Orchestrator.

      3. Asks for the Member ID to assign to this Orchestrator.

    5. When prompted to reboot and apply the changes, enter y.