// removed jquery ui css and js

Upgrade CCO

CCO Non-HA

Upgrade CCO

To upgrade CCO, follow this procedure.

  1. SSH into the CCO instance.

  2. Download the following files in /tmp folder of CCO.

    • core_upgrade.bin

    • cco-installer.jar

    • cco-response.xml

  3. Run the core upgrade to upgrade CCO system components using the following commands.

    sudo -i
    cd /tmp
    chmod 755 core_upgrade.bin
     
    #Set the following only if a local store is setup
    export CUSTOM_REPO=<http://local_package_store IP>
     
    ./core_upgrade.bin <ostype> <cloud> cco
  4. Run the appliance installer to upgrade CCO.

    java -jar cco-installer.jar cco-response.xml
  5. Update the agent bundle URL in the CCO.

    This step is conditional and is required only when the local bundle server or REPO is used in the setup.

    1. SSH into CCO instance.

    2. Run the cco_config_wizard.

      sudo -i
      /usr/local/cliqr/bin/cco_config_wizard
    3. Set the Agent bundle URL.

      #Agent bundle URL
      http://your_HTTP_server/release-<version>/bundle/
    4. Exit the CCO wizard

You have now completed the CCO upgrade.

CCO HA

Run the core_upgrade and appliance files one after the other – do not run them in parallel!

If you are upgrading from a CloudCenter 4.7.x environment, perform the following steps before upgrading the CCO

  1. SSH into the CCO_PRIMARY server.
  2. Run the following commands:

    sudo -i
    touch /usr/local/osmosix/etc/cco_ha_info
    echo "prim_ip=<CCO_PRIMARY_IP>" >  /usr/local/osmosix/etc/cco_ha_info
    echo "sec_ip=<CCO_SECONDARY_IP>" >>  /usr/local/osmosix/etc/cco_ha_info
    echo "ter_ip=<CCO_TERTIARY_IP>" >>  /usr/local/osmosix/etc/cco_ha_info
    chown cliqruser:cliqruser /usr/local/osmosix/etc/cco_ha_info
  3. Continue with the following procedure.


Upgrade CCO_PRIMARY

To upgrade CCO_PRIMARY, follow this procedure.

  1. SSH into the CCO_PRIMARY instance.

  2. Download the following files in /tmp folder of CCO.

    • core_upgrade.bin

    • cco-installer.jar

    • cco-response.xml

  3. Run the core upgrade to upgrade CCO_PRIMARY system components using the following commands.

    sudo -i
    cd /tmp
    chmod 755 core_upgrade.bin
     
    #Set the following only if a local store is setup
    export CUSTOM_REPO=<http://local_package_store IP>
     
    ./core_upgrade.bin <ostype> <cloud> cco
  4. Run the appliance installer to upgrade CCO_PRIMARY.

    java -jar cco-installer.jar cco-response.xml
  5. Update the agent bundle URL in the CCO.

    This step is conditional and is required only when the local bundle server or REPO is used in the setup.


    1. SSH into CCO instance.

    2. Run the cco_config_wizard.

      sudo -i
      /usr/local/cliqr/bin/cco_config_wizard
    3. Set the Agent bundle URL.

      #Agent bundle URL
      http://your_HTTP_server/release-<version>/bundle/
    4. Exit the CCO wizard

You have now completed the CCO_PRIMARY upgrade.

Upgrade CCO_SECONDARY

To upgrade CCO_SECONDARY, follow this procedure.

follow this procedure.

  1. SSH into the CCO_SECONDARY instance.

  2. Download the following files in /tmp folder of CCO.

    • core_upgrade.bin

    • cco-installer.jar

    • cco-response.xml
  3. Run the core upgrade to upgrade CCO_SECONDARY system components using the following commands.

    sudo -i
    cd /tmp
    chmod 755 core_upgrade.bin
     
    #Set the following only if a local store is setup
    export CUSTOM_REPO=<http://local_package_store IP>
     
    ./core_upgrade.bin <ostype> <cloud> cco
  4. Run the appliance installer to upgrade CCO_SECONDARY.

    java -jar cco-installer.jar cco-response.xml
  5. Update the agent bundle URL in the CCO.

    This step is conditional and is required only when the local bundle server or REPO is used in the setup.

    1. SSH into CCO instance.

    2. Run the cco_config_wizard.

      sudo -i
      /usr/local/cliqr/bin/cco_config_wizard
    3. Set the Agent bundle URL.

      #Agent bundle URL
      http://your_HTTP_server/release-<version>/bundle/
    4. Exit the CCO wizard

You have now completed the CCO_SECONDARY upgrade.

Upgrade CCO_TERTIARY

To upgrade CCO_TERTIARY, follow this procedure.

  1. SSH into the CCO_TERTIARY instance.

  2. Download the following files in /tmp folder of CCO.

    • core_upgrade.bin

    • cco-installer.jar

    • cco-response.xml
  3. Run the core upgrade to upgrade CCO_TERTIARY system components using the following commands.

    sudo -i
    cd /tmp
    chmod 755 core_upgrade.bin
     
    #Set the following only if a local store is setup
    export CUSTOM_REPO=<http://local_package_store IP>
     
    ./core_upgrade.bin <ostype> <cloud> cco
  4. Run the appliance installer to upgrade CCO_TERTIARY.

    java -jar cco-installer.jar cco-response.xml
  5. Update the agent bundle URL in the CCO.

    This step is conditional and is required only when the local bundle server  or REPO is used in the setup.

    1. SSH into CCO instance.

    2. Run the cco_config_wizard.

      sudo -i
      /usr/local/cliqr/bin/cco_config_wizard
    3. Set the Agent bundle URL.

      #Agent bundle URL
      http://your_HTTP_server/release-<version>/bundle/
    4. Exit the CCO wizard

You have now completed the CCO_TERTIARY upgrade.

Check the MongoDB Status after Upgrade

Run the following command on the CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY to verify the MongoDB status. All nodes should display the Mongo replica set.

Connect to Mongo shell on each of the three CCO instances and run the following command.

mongo
> rs.status()

The following is a sample output for this command.

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