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

Cisco CloudCenter 4.8.2 Release Notes

Release Date

December 20, 2017


  • January 5, 2017 – to include a Known Issue and updates to the features bullets.

  • January 18, 2017 – to include a Windows 2016 Known Issue

  • February 22, 2018 – to include the Policy Management APIs

  • March 4, 2018 – to include the Capacity Management APIs

  • May 29, 2018 – to include the Upload File API and deprecate the Upload Logo API.

  • August 1, 2018to add details on the Upgrade Path


CloudCenter 4.8.2 is available as virtual appliances. See Virtual Appliance Overview for additional context.

Upgrade Instructions

You can only upgrade to CloudCenter 4.8.2 from CloudCenter 4.7.0 and later releases.

To upgrade to CloudCenter 4.8.2, see Upgrade Overview for additional context.

  • The Non-HA mode is no longer supported and the Non-HA Standalone mode is being renamed to Non-HA.

  • If using your own certs, replace the certs in the CCM Nginx certs folder in /etc/ssl/certs/ with your certificates after the upgrade to 4.8.2.

Upgrade Path

The recommended upgrade path if you are using CloudCenter 4.8.2 is to upgrade to CloudCenter 4.9.0.

Component Version Matrix

See the Version Matrix for a list of third-party or Open Source application versions used by CloudCenter 4.8.2.


  • Management PostgreSQL Server: 

    • The PostgreSQL instance requires a dedicated server. This is a change!

    • Due to this change, you will no longer see separate documentation instructions for  CCM NON-HA.

    • See CCM (Required) for additional context.

  • Monitor Does Not Require a Dedicated Server: This is a change!

    • The Monitor is now an intrinsic part of the CloudCenter platform (and not a separate service) and continues to perform the same function – but no longer requires a dedicated server!

    • The Dashboard > Cloud Health Status continues to display on the CCM UI dashboard based on the CCO health.

  • Dedicated Log Collector ServerThis is a change!

    • The Log Collector, previously referred to as the ELK stack, requires a dedicated VM that comes without HA support.

    • See Virtual Appliance Overview Log Collector for additional context.

  • Additional Memory Requirements for the CCM Server: This is a change!

    • The CCM server requires additional memory for the changes in the underlying architecture.

    • See Hardware Requirements for additional context. 

  • CCM wizard has fewer configuration options: This is a change!

    • The Mail and Mail_User options that were configurable in the CCM wizard is now configurable in the CCM UI's Tenant Information section or using APIs. See the SMTP Mail Properties or the Mail Properties Management sections below for additional context. 

    • The Config_App_Logo option used by the application profile templates is deprecated.

    • The ESB_Info option is now configurable using a separate wizard. See Enterprise Service Bus (ESB) for additional context.

    • For CCM HA scenarios, the Hazelcast IP and External URL options are deprecated and are derived from the Primary Node Private IP, Secondary Node Private IP, and Management DNS name.

    • Ports 7788 and 7789 are not configurable and required by default by the Connection Broker as described in AMQP Firewall Rules. However, you can no longer change these default port configurations and have been removed from the CCO wizard.

  • Bundle settings in the Repo Virtual Appliance: This is a change!

    • See Repo (Conditional) for additional context.

  • Additional IPv6 Support

    • The CloudCenter platform now has the capability to assign IPv6 addresses to launched VMs .

    • When creating firewall rules, the CloudCenter platform supports IPv6 in addition to IPv4 addresses in the CIDR for source network. This is available at application profiles, tenant level firewalls, and security profiles.

    • This support is restricted to AWS and OpenStack clouds.

    • See IP Allocation Mode for additional details.

  • Using Custom Client Certificates: This is a change!

    • The procedure to use your own client certificates has changed. 

    • See Certificate Authentication > Using Your Own Client Certificates for additional details.

  • The File: This is a change!

    • In older CloudCenter releases, the file was not formally documented and only provided a workaround if the default settings for some features could not be configured using the CCM. Effective CloudCenter 4.8.2, CloudCenter APIs allow you to override these settings.  

    • See the Tenant Properties Management APIs for additional context.

    • This change also changes the procedure for the following settings:


  • Google Cloud:

    • Ability to select the storage type for the root disk. The storage type field is optional and if you don't select one, the CloudCenter platform uses a default storage type.

    • See Multiple Volumes for additional context.

  • OpenStack:

    • The Assign IPv6 Address feature provides an option to assign IPv6 addresses on a per-NIC basis in Default Cloud Settings on Deployment Environment, Simplified Networks, and Cloud Settings during Application Deployments. 

      • Also the platform now supports IPv6 addresses in CIDRs for source networks while defining firewall rules in application profiles, tenants, and security profiles.

      • See IP Allocation Mode > Cloud-Specific Nuances > OpenStack for additional context.

    • Capacity Management:

      • Explained in the Cloud Management section below.

      • See Capacity Management for additional context.

  • VMware:

    • Capacity Management:

      • Explained in the Cloud Management section below.

      • See Capacity Management for additional context.

  • vCD:

    • The CloudCenter platform has the provision to specify disk size while defining instance types. This would attach an additional ephemeral disk to the VM when the instance of corresponding type is launched. Effective CloudCenter 4.8.2, the instance type disk size field is not available for vCD clouds. Any additional disks needs to added through actions defined in action library. This is a change!

    • See Manage Instance Types > Root Disk Size > vCD for additional context.

  • Azure

    • Azure Classic: All references to Azure Classic have been removed from the CloudCenter 4.8.2 documentation in keeping with the earlier announcement in the 4.8.1 > Deprecated release notes.

      • If additional volumes are required for an application to be deployed on Azure Pack, then the additional disk needs to be mapped to BlankDisk:  on the Azure Pack console for deployments to work.

  • AWS:

    • The Assign IPv6 Address feature provides an option to assign IPv6 addresses on a per-NIC basis in Default Cloud Settings for Deployment Environment, Simplified Networks, and Cloud Settings during Application Deployments. 

    • Also the platform now supports IPv6 addresses in CIDRs for source networks while defining firewall rules in application profiles, tenants, and security profiles.

    • See IP Allocation Mode > Cloud-Specific Nuances > AWS for additional context.

  • New Images provided by Cisco:

    • The CloudCenter platform upgraded several older images and instance types. When upgrading from an earlier CloudCenter version to CloudCenter 4.8.2, you must sync images and instance types. See Map Images > Sync Image Mappings for additional context.

Applications and Services

 No updates.

CloudCenter Management

  • Capacity Management:

    • The Capacity Management feature helps make efficient use of system resources and enables the CloudCenter platform to automatically place workloads based on capacity.

    • When you deploy an application with Capacity Management enabled, then the CloudCenter platform is capable of automatically identifying the applicable VMware cluster or OpenStack zone having the most amount of free compute resources (CPU/memory) and deploys the application to the identified cluster or zone.

  • Policy Enhancement:

    • The CloudCenter Aging Policy which controls how deployments are aged (suspended/terminated) now supports Cost-based aging of deployments as well! Earlier only Time-based (runtime) aging was supported.

    • Users can now add the aging policy to deployments at launch time or add/remove the policy after the deployment.

    • Aging policies are now applied for the entire lifecycle of the deployment. In earlier releases it was only applied until the first suspend/resume operation. This is a change!

    • You can also extend the aging policy for pre-defined number of times and get notifications as the period is nearing.

    • See Policies for additional context.

    • You can associate an application deployment tier with a scaling policy by associating system tags with the application deployment or deployment tier (if corresponding system tag matching rules are configured for the policy and rules-based governance  is enabled) or by associating the application deployment with the name of the policy to use (if rules-governance is disabled). See Governance Rules for details.

Administration and Governance

  • SMTP Mail Properties: This is a change!

    • In earlier releases, you could only set the SMTP mail properties in the file. Effective CloudCenter 4.8.2, you can configure the SMTP mail settings using the CloudCenter UI or APIs.

    • The SMTP mail settings in the CCM UI are available as part of the Tenant Information settings and as part of the Mail Properties Management APIs listed in the New APIs section below.

  • ServiceNow Extensions:

    • The ServiceNow approval workflows can now be triggered from CloudCenter by configuring a new type of Extension for ServiceNow. This provides a seamless integration between both the applications.

    • Once the configuration process is complete, customers can choose to invoke approval workflows for application deployment, suspend/resume/terminate a deployment and extend an aging policy.

    • Optionally, you can also choose to update the Configuration Management Database on ServiceNow with the asset information, for the VMs being launched from the CloudCenter platform.


No updates.

End of Life Notices

See End of Support Notices for additional details.


The following features are deprecated effective CloudCenter 4.8.2 as already published in the CloudCenter 4.8.1 release notes:

  • Cisco deprecated support for Microsoft Azure Classic – All instances of Azure Classic have been removed from the documentation and the UI.

  • Cisco deprecated support for Ubuntu 12.04 – Use CentOS6 going forward.

  • Cisco deprecated support for View Policies as the new v2 APIs added in this release provide additional, granular features to view policies. Use the View Aging Policies or View Suspension Policies APIs.

  • Cisco deprecated support for the Upload Logo API API and expanded its scope to all files. Use the Upload File API.


  • New Menu Items:

    • Capacity Management

    • Policy Management

    • Service Now Management

  • Browser Compatibility: Cisco supports the two latest versions of each browser. See Browser Compatibility for a list of compatible browsers.

  • Localization: No updates. See UI Behavior for context.


CloudCenter 4.6.0 introduces v2 APIs, where applicable. If a new API is introduced for the first time, it continues to use v1 as it is still the first version of that particular API. The following list differentiates between the New and Updated APIs for CloudCenter 4.8.2.


Service Now Management – explained in several section above.


This section lists the documentation changes implemented in CloudCenter 4.8.2.

  • CloudCenter 4.8.2 Changes: See the links provided in this section for additional context on documentation for this release.

  • The following bullets identify the documentation changes implemented in CloudCenter 4.8.2:

    • CloudCenter 4.8.2 documentation is available at CloudCenter Documentation 4.8.2x and 4.9. All links default to relevant pages for this release.

    • To view documentation for an earlier release, select the applicable release from the dropdown list as shown in the following screenshot.

Known Issues

CloudCenter 4.8.2 has the following known issues:

  • After upgrading to CloudCenter 4.8.2, you must reconfigure deployment schedules that were configured in earlier releases as these older schedules will no longer be usable.

  • Whenever a deployment is submitted for approval, and the user stays on the same page while the deployment is approved by ServiceNow, the Deployment Pending Approval banner does not go away. To workaround this issue, perform a hard refresh of the page.

  • Dynamic bootstrapping does not work in AWS for Linux AMIs that do not have python accessible on the PATH. Make sure that python is present in the PATH environment variable for the root user of a VM launched from this AMI.

  • Job submissions to a phase having a VM plan are not checked for the quota limits of the user's VM plan at the time of job submission.

  • While deploying to a phase within a project, deployment environment owners quotas are checked instead of users plan itself.

  • Parent CCM's initial request to create a Federated link to subordinate CCM for root tenant fails when the root tenant is given a tenant short name in the same session. To workaround this issue, log out on the parent CCM and login, the initial link request from the parent CCM succeeds.

  • Push AgentLite action fails, unable to download the This is observed when the VMs network interface uses an MTU size other than standard MTU -1500 octets. To workaround this issue, execute the following iptable rule to fix the issue:
    iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu

  • Users will not be able to download the logs for deployments that were done before upgrade. The download of logs for deployment done post upgrade continues to work.

  • VMs deployed post upgrading to 4.8.2 may not get listed in the Virtual Machines page.

  • This could be because the time on CCM is not synced with UTC. Sync the time / system clock on your CCM with the UTC time.

  • CloudCenter 4.8.2 fails to deploy a Windows VM based out of a Snapshot on VMWare cloud. Template based VM deployments continue to work.

  • Users will not be able to open a Remote Desktop session for application VMs that were launched using Windows 2016 images, from Job details page.

Resolved Issues

The following issues were resolved/addressed in CloudCenter 4.8.2:

  • Issue: The Docker container launched for the external script executor may have intermittent network failures. To work around this issue, restart the Docker service. This was listed as a Known Issue in  
    Resolution: This issue is listed in the resolved section as it was no longer observed during test cycles for the CloudCenter platform.

  • Issue: When logging into the CCM for the first time through SSO the user is notified that the video they are trying to access is private. 
    Resolution: The video is deprecated and the link was removed from the UI.

  • Issue: Image mappings are missing for AWS region EU-West-2.
    Resolution: Image details have been added and necessary changes were uploaded to the repository. The image mappings are available when you sync image mappings.

  • Issue: Both Windows 2012 AMI's for location EU-West2 (London) are identical.
    Resolution: Proper image ids has been updated and necessary changes were uploaded to the repository.

  • Issue: When the repo appliance is used for setting up a repository and offline installation of CCM is tried, it fails with package dependency issues for glibc packages.
    Resolution: The repository has been updated with the latest packages and all package dependency issues should be fixed.

  • Issue: The Subtenant Logo does not show up on the CloudCenter login page.
    Resolution: A fix for this was provided. Additionally, the user must specify the subtenant URL in the "Tenant Domain Name" field in the “Tenant Information” page. This will be visible only when the property is set in the CCM. In the 4.8.2 CCM, one should add this entry in the /etc/sysconfig/mgmtserver.conf file: export R53_DOMAIN_NAME=<domain_url>

  • Issue: Cannot check details of a scheduled deployment. The “Scheduled Deployments” page only gives the names of the scheduled deployments.
    Resolution:  CloudCenter now shows the scheduled deployments in the deployment list page. Details related to the schedule can be checked by visiting the job details page.

  • Issue: The CloudCenter installer doesn't throw any error on windows worker image for wrong or empty argument for the cloudtype variable. Installation will proceed without any interruption and give a success message even if cloudtype is wrong or empty.
    Resolution: Validation is added to check if the cloudtype parameter is empty.

  • Issue: Modifying tenant information after creation does not update the file.
    Resolution:   The '' file no longer exist in 4.8.2. All the vendor specific properties are moved to the database and changed properties will now persist.

  • Issue: Passwords used for ACI extensions are in clear text in the CCM database and exporting the database content will reveal them.
    Resolution: All passwords are stored encrypted in the database and existing passwords will be migrated to encrypted ones.

  • Issue: IE 10 Failing to Properly load CloudCenter UI.
    Resolution:  CloudCenter no longer supports IE 10. User must upgrade to IE 11 or Microsoft Edge browsers.

  • Issue: Deployment of AzureRM Data Science Windows 2016 VM fails.

  • ResolutionCloudCenter 4.8.2 now supports bootstrapping of Windows 2016 VMs on AzureRM.

  • Issue: When using managed disk in AzureRM, the OS disk is always created in 'Standard LRS' disk type. Customer would like the option to use Premium (Managed) disk for the OS disk as well as additional disks.

    ResolutionFor clouds like AWS, Google and AzureRM that support setting root disk storage type, user will be able to choose the storage type for the OS/root disk.

  • Issue: Cannot install AgentLite on Windows in AzureRM.
    : User must enable the SMB1 protocol on the Windows server where you are installing AgentLite per the updated documentation.

  • Issue:User set timeouts for scripts running inside docker container are being ignored and the default timeout of 10 minutes is being used.
    Resolution:  Fixed bug which prevented user set timeouts from overriding the default timeout of 10 minutes. Now the user can run a task that take more than 10 minutes to complete by overriding default timeout, without the task being abruptly terminated.

  • Issue: Azure boot diagnostic extension fails to be provisioned on Windows virtual machines.
    Resolution: CloudCenter and 4.8.2 include a fix to ensure that the boot diagnostic extension is provisioned as designed on Windows VMs.

  • Issue: Ability to extend an aging policy.
    Resolution:  This functionality has been added in 4.8.2.

  • Issue: The policy API calls do not return any context about the policy such as time duration or schedule.
    Resolution:  The new policy API calls return all of the required information in the response.

  • Issue: OpenStack: optimize token retrieval, use expiry time.
    Resolution: Modified OpenStack client 
    to reuse the token for node creation and monitoring.

  • Issue: MongoDB version of 2.6 is outdated.
    Resolution:  Mongo is updated to 3.4.10 in the current build.

  • Issue: Allow hyphens in the cloud name when adding a new cloud.

  • Resolution: The existing behavior will not be changed as users will not be able to sync instance types from AWS if the cloud name includes a hyphen. 

  • Issue: Order of clouds on the deployment page should be in alphabetic order.

  • Resolution: The clouds available during deployment will now be shown in alphabetical order.

  • Issue: UI gets stuck when editing OpenStack image mappings for image with no name.
    Resolution: Checks have been added to handle empty image names and UI will no longer get stuck.

  • Issue: HA AMQP Failing to Start After Rebooting.
    Resolution:  This was a result of restrictive umask setting of 077 that was done in previous release. umask is now restored to 022 and AMQP is able to survive multiple reboots.

  • Issue: While modelling an application, cloning a service alters the input value in the fields that refer to files in the repository.
    Resolution:  Application modelling flow has been fixed so that cloning a service does not alter the inputs of the original service.

  • Issue: When terminating a single node inside a multi-node or scaled deployment, the node does not initiate ipamDealloc.
    Resolution:  Added the warning message in Job Details, VM List and Server Details pages when user attempts to terminate a node (or a bunch of nodes multi-selected in the VM List page) that the lifecycle actions such as IPAM De-allocation will not be executed.. The warning message doesn't show up for unmanaged nodes.

  • Issue:   Multiple dbmaster/dbslave IPs entries are placed in /etc/hosts file when the DB wizard is run more than once..
    Resolution:  Checks have been added so that duplicate entries are not added to /etc/hosts file for the dbmaster/ dbslave IPs even when DB Configuration wizard is run multiple times.

  • Issue: Schedule Benchmark Submit option doesn't work.
    Resolution:  In 4.8.2 a new schedule deploy and schedule benchmark option is available to users.

  • Issue:  User is unable to deploy an application that uses external services.
    Resolution:  The deployment flow has been fixed so that users can now deploy an application that uses external services.

  • Issue: More detail in agent installation process.
    Resolution: Earlier, the only way to obtain the installation procedure was to contact the Cisco Support team. These details are now included with the installation procedures for the other CloudCenter components. See Worker (Conditional) for additional context.

  • Issue: When you model an application using the NFS service and then deploy this application, the access link does not work.
    Resolution: In this case, the customer launched the NFS application to the instance VM using a deployment environment that did not persist the private SSH key – the SSH private key is required by both the NFS service and the CCM to authenticate each other.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks