Install CCM HA Using Installer

Unable to render {include} The included page could not be found.

The /tmp Alternative

You can download installation files to a directory of your choice. The procedure provided in the CloudCenter documents, recommend using the /tmp folder as the download folder. In some cases, you may not want to use /tmp folder as the temp location as this directory may not allow files to be executed in your environment.

To install CloudCenter on systems where /tmp is set to nosuid or noexec, issue the following command before downloading the component files:

export TEMP_DIR=<any_directory_with_exec_permission>

The /tmp alternative is available for the CCM, CCO, and AMQP components.

Process

CCM Installers are only available for AWS, OpenStack, and VMware clouds.

  1.  MGMTPOSTGRES_MASTER/SLAVE - Run Core Installer and Setup SSH Communication

    MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE – Run Core Installer and Setup SSH Communication

    1. Download package files:

      See Installer Overview to understand the required components.

      See Phase 4 Overview  to understand the various types of software download files.

      1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.

      2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

        • core_installer.bin
        • ccm-installer.jar
        • ccm-response.xml
    2. Run the core installer to setup core system components using the following commands:

      sudo -i
      cd /tmp
      chmod 755 core_installer.bin
      
      #Set the following only if a local package store is setup 
      export CUSTOM_REPO=<http://local_package_store ip>
      
      ./core_installer.bin <ostype> <cloudtype> mgmtpostgres
      

      For example:

      ./core_installer.bin centos7 amazon mgmtpostgres
      

      Syntax:

      <ostype> = centos6, centos7, rhel6, rhel7

      <cloudtype> = amazon, openstack, vmware

    3. Remove the core_installer.bin file.

      rm core_installer.bin 
      
    4. Perform Steps 1 to 4 (a to e) on the MGMTPOSTGRES_SLAVE.

  2.  Exchange SSH Keys between the MGMTPOSTGRES Servers

    Unable to render {include} The included page could not be found.

  3.  MGMTPOSTGRES_MASTER - Configure High Availability Properties

    Unable to render {include} The included page could not be found.

  4.  CCM_SA_PRIMARY/SECONDARY - Run Core Installer and Setup SSH Communication

    CCM_SA_PRIMARY/SECONDARY – Run Core Installer and Setup SSH Communication

    1. Download package files:

      See Installer Overview to understand the required components.

      See Phase 4 Overview  to understand the various types of software download files.

      1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.

      2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

        • core_installer.bin
        • ccm-installer.jar
        • ccm-response.xml
    2. Run the core installer to setup core system components using the following commands:

      sudo -i
      cd /tmp
      chmod 755 core_installer.bin
      
      #Set the following only if a local package store is setup 
      export CUSTOM_REPO=<http://local_package_store ip>
      
      ./core_installer.bin <ostype> <cloudtype> ccm_sa
      

      For example:

      ./core_installer.bin centos7 amazon ccm_sa
      

      Syntax:

      <ostype> = centos6, centos7, rhel6, rhel7

      <cloudtype> = amazon, openstack, vmware

    3. Remove the core_installer.bin file.

      rm core_installer.bin 
      
    4. Log off and log back in as the root user to ensure JAVA Home is set.

      exit
      sudo -i
    5. Exchange the SSH keys between the CCM_SA_PRIMARY and CCM_SA_SECONDARY

      1. On the CCM_SA_PRIMARY, execute the following to generate a new SSH key. 

        su - cliqruser
        ssh-keygen -t rsa
        cd ~/.ssh
        cat id_rsa.pub >> authorized_keys
      2. Copy the id_rsa files (~/.ssh/id_rsa and ~/.ssh/id_rsa.pub) from CCM_SA_PRIMARY to the same location on the CCM_SA_SECONDARY. On the CCM_SA_SECONDARY, if the .ssh directory does not exist, create it using the following commands before copying the files!

        su - cliqruser
        mkdir -p ~/.ssh
        chmod 700 ~/.ssh
      3. On the CCM_SA_SECONDARY, execute the following to add a new SSH key.

        su - cliqruser
        chmod 400 ~/.ssh/id_rsa*
        cat id_rsa.pub >> authorized_keys
        chmod 600 authorized_keys
      4. Verify mutual SSH access between the CCM_SA_PRIMARY and CCM_SA_SECONDARY by running the following command on each VM.

        su - cliqruser
        ssh cliqruser@<CCM_SA_PRIMARY/CCM_SA_SECONDARY>

     

  5.  CCM_SA_PRIMARY - Run Appliance Install

    CCM_SA_PRIMARY – Run Appliance Install  

    To run the appliance install for the CCM_SA_PRIMARY, follow this procedure.

    1. SSH into the VM instance using the key pair that you used to launch the VM.
    2. Change to the /tmp directory and modify the ccm-response.xml file as follows:

      Response File EntryValueNotes
      <entry key="db_host" value="default"/>The db_host IP address depends on the database set up for the CCM:
      • Standalone DB: Use the instance IP address
      • HA DB: Use the VIP address

      Required
    3. Run the appliance installer to setup the CCM.

      java -jar ccm-installer.jar ccm-response.xml
    4. Reboot the CCM VM.

  6.  CCM_SA_SECONDARY - Run Appliance Install

    CCM_SA_SECONDARY – Run Appliance Install  

    To run the appliance install for the CCM_SA_SECONDARY, follow this procedure.

    1. SSH into the VM instance using the key pair that you used to launch the VM.

    2. Change to the /tmp directory and modify the ccm-response.xml file as follows:

      Response File EntryValueNotes
      <entry key="db _enable" value="true "/> Change the value to false.

      In the HA setup, the appliance installer on the secondary instance should not update the database.

      <entry key="db_host" value="default"/>

      The db_host IP address depends on the database set up for the CCM.

      1. Standalone DB:  Use the instance IP address.

      2. HA DB: Use the VIP address

      Required.
    3. Run the appliance installer to setup the CCM.

      java -jar ccm-installer.jar ccm-response.xml
    4. Reboot the CCM VM.

  7.  CCM_SA_PRIMARY - Configure HA Wizard Properties

    Unable to render {include} The included page could not be found.

  8.  CCM_SA_PRIMARY/SECONDARY - Configure CCM Wizard Properties

    Unable to render {include} The included page could not be found.

  9.  CCM_LB

    Unable to render {include} The included page could not be found.

     

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved