CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Upgrade Overview

To Upgrade CloudCenter

Verify the versions being used to upgrade your CloudCenter platform and ensure that the applicable scenario is supported!

From CloudCenterTo CloudCenterUse the procedure provided in this section?
Any lower 4.8.xAny higher 4.8.x


If you are upgrading from CloudCenter 4.8.2 to, you do not need to run the core_upgrade.bin command. See Upgrade Overview (4.8.2 and later) for additional context.





You must first upgrade to CloudCenter 4.7x.

See CloudCenter 4.6/4.7 Upgrade for additional context.

4.5.x and any lower version4.8.x


You must first upgrade to CloudCenter 4.6x.

See CloudCenter 4.6/4.7 Upgrade for additional context.

Is the core_upgrade.bin File Required?

The core_upgrade.bin file has a different purpose depending on the following factors:

  • What is your current and target release?
  • On which component will you run this file? For example, running the 4.8.0 version of this file on the CCO automatically installs the Docker enhancement.
  • From which release did you obtain this file? Be sure to use the file provided for the applicable release.

Your environment, your combination of releases and components, and when you obtained this file determine if and when to use this file.

While the upgrade procedure provided in this section includes instructions to run the core_upgrade.bin file, be aware that this file is ONLY required for specific versions and is specific to each component as identified in the following table.

FromToIs core_upgrade.bin Required?
Any lower 4.8.xAny higher 4.8.xNot required.
4.7.x and later4.8.x

Required, for the following components:

  • CCM: core_upgrade.bin osType cloudType java
  • CCO: 
    • core_upgrade.bin osType cloudType java
    • core_upgrade.bin osType cloudType docker
  • AMQP: core_upgrade.bin osType cloudType java
  • Monitor: core_upgrade.bin osType cloudType java
  • Guacamole: core_upgrade.bin osType cloudType java
  • External Script Executor: core_upgrade.bin osType cloudType docker

Same Component Versions

All CloudCenter components must all run the same CloudCenter version—they cannot run different CloudCenter versions.

Component Upgrade Sequence

Follow this sequence when upgrading CloudCenter components:

  1. Bundle Store Upgrade (considered a new installation)

  2. CCM-Database Upgrade (HA or Non-HA)

  3. CCO Upgrade (HA or Non HA)

  4. AMQP Upgrade (HA or Non-HA)

  5. Health Monitor Upgrade (HA or Non-HA)

  6. Docker Image Upgrade (HA or Non-HA)

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