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 DNA Center 2.3.5 on AWS Deployment Guide.

• Any manual alterations made to the automated configuration workflow of Cisco DNA 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 Cisco DNA Center on AWS. For more information, see "Create a New Cisco DNA Center VA" in the Cisco DNA Center 2.3.5 on AWS Deployment Guide.

• You can only create one Cisco DNA Center VA per VA pod.

• When configuring a VA pod, the following VPN vendors are not supported:

  • Barracuda

  • Sophos

  • Vyatta

  • Zyxel

• Deleting a VA pod on Cisco Global Launchpad can take approximately 20 to 40 minutes.

The Overview Pane

On the Dashboard pane, the Privacy - Terms link isn't working.

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.

Regions and Availability Zones

• Cisco Global Launchpad must be running Release 1.2.1 or later before you can install Release 1.7.0 and update a region version.

• 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 the following 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.

Amazon Email Subscription, Logs, and Alarms

• Multiple users should not update their email IDs concurrently. If this occurs, the latest updated email ID is used for email notification.

• 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 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.