// removed jquery ui css and js

Upgrade AMQP

AMQP Non-HA

Upgrade AMQP

To upgrade AMQP, follow this procedure.

  1. SSH into the AMQP instance.

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

    • core_upgrade.bin

    • cco-installer.jar

    • conn_broker-response.xml

  3. Run the core upgrade to upgrade AMQP 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> rabbit
  4. Run the appliance installer to upgrade AMQP.

    java -jar cco-installer.jar conn_broker-response.xml

    You have now completed the AMQP upgrade.

AMQP HA

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

Upgrade AMQP_PRIMARY

To upgrade AMQP_PRIMARY, follow this procedure.

  1. SSH into the AMQP_PRIMARY instance.

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

    • core_upgrade.bin

    • cco-installer.jar

    • conn_broker-response.xml

  3. Run the core upgrade to upgrade AMQP_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> rabbit
  4. Run the appliance installer to upgrade AMQP_PRIMARY.

    java -jar cco-installer.jar conn_broker-response.xml

    You have now completed the AMQP_PRIMARY upgrade.

Upgrade AMQP_SECONDARY

To upgrade AMQP_SECONDARY, follow this procedure.

  1. SSH into the AMQP_SECONDARY instance.

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

    • core_upgrade.bin

    • cco-installer.jar

    • conn_broker-response.xml

  3. Run the core upgrade to upgrade AMQP_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> rabbit
  4. Run the appliance installer to upgrade AMQP_SECONDARY.

    java -jar cco-installer.jar conn_broker-response.xml

    You have now completed the AMQP_SECONDARY upgrade.

Check Cluster Status after Upgrade

Run the following command on both AMQP_PRIMARY and AMQP_SECONDARY to verify the cluster status. Both the nodes should display in cluster.

# rabbitmqctl cluster_status

The following is a sample output for this command

In the following output amqp1 and amqp2 are the hostnames of AMQP_PRIMARY and AMQP_SECONDARY.

Restart HAProxy in the AMQP_LB

If you configure a load balancer for any CloudCenter component, be aware that the firewalId is enabled by default and you must explicitly disable it to ensure that the CloudCenter component(s) can communicate with the load balancer. See Firewall Rules Overview for additional context.

Restart HAProxy in the AMQP_LB after upgrading the AMQP_PRIMARY and AMQP_SECONDARY servers.

Note: If you are using your custom Load Balancer, please use their respective options to restart.

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

  2. Run the following commands to restart HAProxy.

    systemctl stop haproxy
    systemctl start haproxy
    systemctl status haproxy


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