Suite Admin 5.0.1 Release Notes

Release Date

First published: April 6, 2019


  • April 9, 2019: Updated the Documentation section to include a list of pages that were updated.

  • April 10, 2019: Added a Tip to the Upgrade Path section in this release notes.

  • April 16, 2019: Updated the Documentation section to highlight SaaS nuances.

  • April 30, 2019:

    • Added a note to the Upgrade section on the need to updated one module at a time.

    • Updated the Documentation section to add a similar note in the related sections.

  • May 15, 2019: Updated the Documentation section to include a list of pages that were updated.


CloudCenter Suite 5.0.1 is available as installer files for ALL components for all supported clouds. Contact the CloudCenter Suite Support team for additional details.

Upgrade Path

While you cannot upgrade the Kubernetes cluster for this release, you can update any module available in CloudCenter Suite5.0.1.

  • If CloudCenter Suite 5.0.0 is not installed, then follow the process specified in the Installer section.

  • If CloudCenter Suite 5.0.0 is already installed, then you can only upgrade a module from CloudCenter Suite 5.0.0 to CloudCenter Suite 5.0.1 as listed in Update Module.

    Upgrading the Suite Admin takes approximately 5-10 minutes. During this time you will:

    • See an interruption in CCS service until the PODs restart and regain the Running status.

    • See a few error messages being displayed, they are temporary.

    • Be logged out – try logging in after a few minutes.

    • You must update the Suite Admin module first, before you update any other CloudCenter Suite module.

      • Before updating any module, verify that you have un-allocated CPU/Memory in your cluster to ensure that your environment has free CPU/Memory – a module-update scenario requires additional resources for the old pod to continue running until the new pod initializes and takes over. This additional resource requirement is temporary and only required while a module update is in Progress. After the module is updated, the additional resources are no longer needed.

      • You must update the Suite Admin module before you update any other CloudCenter Suite module. 

      • Update only one module at at time. If you simultaneously update more than one module, your update process may fail due to limited resource availability. See Prepare Infrastructure for additional context.

      • You may see one or more error messages during the update process. Be aware that these messages will not affect the update itself.

    • When a module upgrade becomes available the module card includes an Update button as displayed in the following image.

    • Click Update to view the available module versions. The available versions are listed in descending order with the latest version at the start of the list which includes all available versions that are higher than the currently installed version.


Effective CloudCenter Suite5.0.1, the time of all worker and master nodes are synced with the primary master nodes.

  • The primary master node is the instance used to launch the CloudCenter Suite – the link that takes you to the Suite Admin UI contains the IP address of the primary master as displayed in the following screenshot.
  • See Prepare Infrastructure > NTP Requirements for additional details.


No updates


No updates

Module Management

No updates

Smart Software Licensing

No updates

User Tenant Management

No updates

Cluster Management

No updates

Security Management

  • Effective CloudCenter Suite 5.0.1, Cisco provides CSRF protection for all API calls.

  • When an API call is made by you or the CloudCenter Suite, be aware that a CSRF token is required for the following scenarios:

    • If the request method is POST, PUT, or DELETE

    • If the request Content-Type is not application/json

  • See CSRF Token Protection for additional details.

Suite UI

No updates


The following Suite Admin API calls were added in CloudCenter Suite 5.0.1.

The following Suite Admin Authentication Service API Calls 5.0.1 APIs were enhanced in CloudCenter Suite 5.0.1 to include the csrfToken variable.

  • Generate Integration Token

    • API call: GET /suite-auth/api/v1/integration_token

    • Description: The Integration Token is used in /integration_token_login/{integrationToken} for authentication purposes.

  • Refresh JWT Token

    • API call: GET /suite-auth/api/v1/token 

    • Description: Token will be both set in the cookie and returned in the response

  • Authenticate endpoint for a first-time admin user

    • API call: GET /suite-auth/init_login

    • Description: The user will have SUITE_OUTOFBOX_USER role that will be limited to update the user profile and password.

  • Successful authentication

    • API call: POST /suite-auth/login Login

    • Description: Token will be both set to cookie and returned in response

  • Authentication endpoint to use the password reset token

    • API call: GET /suite-auth/reset_token_login/{resetToken} .

    • Description: The user is assigned a SUITE_RESET_PASSWORD role that limits this user to using the new password. 


The CloudCenter Suite Installer allowed the use of specific instance types when setting up clusters in EKS and Azure instances. Effective CloudCenter Suite 5.0.1, the following instance types are no longer available as they use variable CPU settings which sometimes results in depleted resources.


The following documentation changes were implemented in CloudCenter Suite 5.0.1:

Known Issues

No updates

Resolved Issues

No updates

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks