Adding Satellite Managers to the mesh

This topic describes how to add Satellite Managers to the Multi-Manager mesh.

Before you begin

Make sure that the following prerequisites are met:

• Make sure that you have configured the Content Manager.
• Make sure that the Manager software is installed on the target Satellite Managers as described in Installing-the-Manager-software-in-a-Multi-Manager-configuration.

To add Satellite Managers to the mesh

1. Log on to a server that you have designated as a Satellite Manager in your environment.
2. Open the /app/clarity/dmanager/etc/mesh.conf file in a text editor.

3. Add the following lines:
   manager_type=member
   mega_manager=Content_Manager_host_name
   nodenum=node_number
   
    The Content_Manager_host_name should be the fully qualified hostname of the Content Manager. The node_number should be a unique number other than 1 (1 is reserved for the Content Manager).

   Note

   For megamesh to work correctly, the /home/clarity directory must exist and be owned by the clarity user.

4. Save the /app/clarity/dmanager/etc/mesh.conf file.

5. (Only if you are installing on Red Hat Enterprise Linux (RHEL) 7.5 with PostgreSQL server 9.6.x) Link the PostgreSQL files from the /usr/pgsql-9.6/bin directory:

   ln -snf /usr/pgsql-9.6/bin/* /usr/bin/

6. (Only if you are installing on RHEL 6 or RHEL 7 with PostgreSQL server 11.x) Link the PostgreSQL files from the /usr/pgsql-11/bin directory:

   ln -snf /usr/pgsql-11/bin/* /usr/bin/

7. Run the configure_megamesh script:
   /app/clarity/manager_scripts/bin/configure_megamesh
   
    The first time this command is run on a Satellite Manager, an SSH key is generated in the
   /app/clarity/dmanager/etc/id_rsa.pub file. A message informs you of this and exits immediately afterward.

   Note

   The public and private keys on the Satellite Manager are owned by the clarity (Satellite Manager) account.

8. Append the contents of the id_rsa.pub file to the /home/megamesh/.ssh/authorized_keys directory on the Content Manager.

   Note

   If the /home/megamesh/.ssh directory does not exist on the Content Manager, create it, ensure that it has a change mode value of 0700 and is owned by the megamesh user. The authorized_keys file inside this directory should have a change mode value of 0600 and also be owned by the megamesh user.

9. To verify that you have completed the previous step successfully, log on as root and run the following on the Satellite (where <Content Manager hostname> is rh5-mm007-01.gridapp-dev.com, for example). This command attempts to ssh to the content manager and run the date command. If the current date and time are returned, the previous step has been completed successfully:
   su clarity -c 'ssh -i /app/clarity/dmanager/etc/id_rsa -o StrictHostKeyChecking=no -o UserKnownHostsFile=/app/clarity/dmanager/etc/ssh_known_hosts -l megamesh <Content Manager hostname> date'

   Note

   If this command is successful, but the following error message appears: “Could not create directory '/home/clarity/.ssh'”, run the following two commands and proceed with the rest of the configuration steps:
   mkdir /home/clarity
   chown clarity -R /home/clarity.

10. Run the configure_megamesh script again:
    {{code language="none"}}
    /app/clarity/manager_scripts/bin/configure_megamesh
    
    {{/code}}

    Note

    These are passwords that you used when you configured the Content Manager.

11. Open the /app/clarity/dmanager/etc/dmanager.conf file in a text editor.
12. Add the following lines:
    megamanager=Content_Manager_host_name
    service=static MegaManagerCommunicator "-t 1 -i 120 -f
    /app/clarity/dmanager/var/megamesh_failures"
     The Content_Manager_host_name should be the fully qualified hostname of the Content Manager.
13. Save the /app/clarity/dmanager/etc/dmanager.conf file.
14. Restart the dmanager service:
    service dmanager restart
15. Restart the Multi-Manager service on the Satellite Manager:
    service megamesh restart
16. Repeat steps 1 through 13 for the other Satellite Managers in the mesh.