Release Notes for Cisco Global Launchpad, Release 2.0.x
Available Languages
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- US/Canada 800-553-2447
- Worldwide Support Phone Numbers
- All Tools
Feedback
Feedback
Cisco Global Launchpad, Release 2.0.x
Cisco Global Launchpad, Release 2.0.x
Cisco Global Launchpad is a deployment tool that configures and deploys Cisco Catalyst Center on Amazon Web Services (AWS). It also provides centralized management of Catalyst Center virtual appliances (VAs) and associated operational resources.
This document describes the features, limitations, and bugs for Cisco Global Launchpad, Release 2.0.x.
Note: Cisco DNA Center has been rebranded as Catalyst Center, and Cisco DNA Center VA Launchpad has been rebranded as Cisco Global Launchpad. During the rebranding process, you will see the former and rebranded names used in different collaterals. However, Cisco DNA Center and Catalyst Center refer to the same product, and Cisco DNA Center VA Launchpad and Cisco Global Launchpad refer to the same product.
Table 1. Change history to this document since its initial release
| Date |
Change |
Location |
| 2025-08-19 |
Updated the supported upgrade paths information. |
|
| 2025-01-22 |
Added information about Catalyst Center Amazon Machine Images (AMIs). |
|
| 2025-01-21 |
Added new and changed features for Cisco Global Launchpad, Release 2.0.1. |
|
| Added resolved issues for Cisco Global Launchpad, Release 2.0.1. |
||
| 2024-12-20 |
Noted that in the Configure Catalyst Center page, you can choose an available Catalyst Center version. |
|
| 2024-09-24 |
Initial release |
_ |
Cisco Global Launchpad
Table 2. New and changed features in Cisco Global Launchpad, Release 2.0.1
| Product impact |
Feature |
Description |
| Base functionality |
Ability to configure the customer CIDR |
While creating a Catalyst Center VA, you can add the customer CIDR to access the Catalyst Center VA. |
| Password policy update |
The CLI login password requirements for a Catalyst Center VA have been updated. |
Table 3. New and changed features in Cisco Global Launchpad, Release 2.0.0
| Product impact |
Feature |
Description |
| Base functionality |
Ability to specify a version |
In the Configure Catalyst Center page, you can choose an available version from the Catalyst Center version drop-down list. |
| Direct-connect prerequisite |
While creating a new VA pod, when you select the existing TGW option and existing attachment scenario, the drop-down lists all the existing attachments, including any direct connect option. However, to view the direct connect gateway name in the drop-down list, you must log in to Cisco Global Launchpad with an administrator account to grant the required permissions. |
|
| Ease of use |
Network connectivity wait-time message |
On the Network Connectivity Check page, a message now indicates the wait time to create an IPsec tunnel: Waiting for <n> seconds for the IPsec tunnel creation. A message alerts you to any connectivity delay: <Gateway name> in <region> is taking longer than usual to create a tunnel connection. Make sure that the firewall/router settings are correct. |
| Updated cards on the VA pod dashboard |
On the VA Pod Dashboard page, the cards now display the Catalyst Center version. |
|
| New error messages to help in troubleshooting |
●
The transit gateway attachment for this VA pod is in “modifying” state: If you see this error while creating a new pod, it means that the transit gateway attachment was modified manually on the AWS portal. You must wait for the state to change to
Complete before you can continue creating the VA pod.
●
The transit gateway attachment for this VA pod is not found: If you see this error, it means that the transit gateway attachment was manually deleted. You must delete this VA pod and create a new one with the transit gateway attachment.
|
You can use the Cisco Bug Search Tool to search for a specific bug or to search for all resolved bugs in this release.
You can use the Cisco Bug Search Tool to search for a specific bug or to search for all open bugs in this release.
To search for a documented Cisco product issue, type in the browser: <bug_number> site:cisco.com
Table 4. Guidelines and limitations for Cisco Global Launchpad, Release 2.0.x
| Bug ID |
Description |
| Guidelines |
|
| Client system |
We recommend that the client systems you use to log in to Cisco Global Launchpad be equipped with 64-bit operating systems and browsers. |
| Limitations |
|
| Amazon alarms |
● The Amazon CloudWatch alarms for lambda functions remain in the insufficient data state unless a failure occurs in the corresponding lambda function execution. When a lambda function fails, Amazon CloudWatch gathers the metrics and triggers the alarm. The threshold for all lambda alarms is one, so Amazon CloudWatch can capture alerts if there are any failures.
● For some alarms, like S3, the metrics are only reported once per day at midnight in Greenwich Mean Time (GMT) or 00:00 UTC. So, it can take 24 to 48 hours for the dashboard metrics to be updated, which is an expected behavior.
|
| Amazon email subscriptions |
Multiple users should not update their email IDs concurrently. If this occurs, the latest updated email ID is used for email notification. |
| Amazon S3 buckets and objects |
Amazon S3 buckets are automatically created to store objects, such as logs and data. When an object is marked for expiration, the Amazon S3 Lifecycle Policy automatically deletes it from the bucket. However, because the Amazon S3 Lifecycle Policy operates asynchronously, the deletion might take some time. It's important to note that when an object is marked for expiration, you aren't billed for this object anymore even though it might still be visible in the bucket. Because this is an Amazon function and policy, refer to the following Amazon AWS website for the latest information: https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html. |
| Automated deployment workflow |
● The configuration for the Existing Transit Gateway (TGW) and Existing Customer Gateway (CGW) scenario is not available in the automated deployment method. You must manually configure this routing as discussed in the
Cisco Catalyst Center on AWS Deployment Guide.
● Any manual alterations made to the automated configuration workflow of Catalyst Center on AWS can cause conflict with the automated deployment. We recommend against making manual changes with Cisco Global Launchpad through the AWS console, because it can lead to issues that Cisco Global Launchpad cannot resolve.
● A valid Enterprise DNS is mandatory to deploy Catalyst Center on AWS. For more information, see "Create a new Catalyst Center VA" in the
Cisco Catalyst Center on AWS Deployment Guide.
● The DNS server cannot be updated through Cisco Global Launchpad after deploying Catalyst Center on AWS. However, you can update the DNS server using the AWS console. For more information, see "Update the DNS server on a Catalyst Center VA using the AWS console" in the
Cisco Catalyst Center on AWS Deployment Guide.
● You can create only one Catalyst Center VA per VA pod.
● When configuring a VA pod, these VPN vendors are not supported:
◦ Barracuda ◦ Sophos ◦ Vyatta ◦ Zyxel
● Deleting a VA pod on Cisco Global Launchpad can take approximately 20 to 40 minutes.
|
| Catalyst Center AMIs |
Backup Catalyst Center Amazon Machine Images (AMIs) are dynamically generated from AWS Marketplace. |
| Hosted Cisco Global Launchpad |
When you refresh any pane on hosted Cisco Global Launchpad pane from your browser, such as the Create/Manage Cisco Catalyst Center(s) pane, you are redirected to the Dashboard pane. During the refresh, the URL loses the query parameters that contain information about the selected region. |
| Privacy terms |
The privacy terms link is currently inactive and does not lead to any pop-up window or page. |
| Region and availability zones |
● Because the sa-east-1 region is not supported, VA pods and resources created in this region need to be removed manually through the AWS console.
● Cisco Global Launchpad does not support local zones and wavelength zones. It supports only AWS availability zones for regions.
● You cannot create a VA pod in these availability zones because the minimum instance size (r5a.8xlarge) is not supported in these zones:
◦ The us-east-1e availability zone in the us-east-1 region ◦ The ap-northeast-2b and ap-northeast-2d availability zones in the ap-northeast-2 region ◦ The ca-central-1d availability zone in the ca-central-1 region |
| Root Cause Analysis |
Due to an update to the Root Cause Analysis (RCA) folder structure for Amazon S3 Lifecycle, an RCA triggered in Cisco Global Launchpad, Release 1.2.x and earlier can't be displayed in Cisco Global Launchpad, Release 1.3.0 and later. |
Compatible browsers
Cisco Global Launchpad is compatible with these HTTPS-enabled browsers:
● Google Chrome: Version 93 or later.
● Mozilla Firefox: Version 92 or later.
● Apple Safari: Version 16.1 or later.
When upgrading to the latest release of Cisco Global Launchpad, familiarize yourself with this upgrade information:
● You cannot upgrade from a previous release of Cisco Global Launchpad to Cisco Global Launchpad Release 2.0.x. You must reinstall Docker Community Edition (CE) and then install Cisco Global Launchpad Release 2.0.x.
● To enable access to the new regions added in Release 2.0.x, your admin user must log in to Cisco Global Launchpad after the Cisco Global Launchpad Release 2.0.x has been installed. After the admin user has logged in, access to all regions is enabled for all other users.
● All the AWS resources created in the current release of Cisco Global Launchpad aren't supported in earlier releases.
Supported Catalyst Center releases on AWS
Cisco Global Launchpad, Release 2.0.x supports the configuration of new Catalyst Center 2.3.7.x on AWS deployments.
See Cisco Catalyst Center Documentation for additional documents relating to Catalyst Center.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2025 Cisco Systems, Inc. All rights reserved.