Focus

Validate the AWS Transit Gateway Integration CloudBlade

Table of Contents

Filter

Expand All | Collapse All

Prisma SD-WAN Docs

Administration
Deployment
Incidents & Alerts
CloudBlades
Version
- AWS Transit Gateway
- Azure vWAN
- Azure vWAN with vION
- ChatBot for MS Teams
- ChatBot for Slack
- CloudBlades Integration with Prisma Access
- GCP NCC
- Service Now
- Zoom QSS
- Zscaler Internet Access
Reference
Release Notes
Version
- ION 5.2
- ION 5.3
- ION 5.4
- ION 5.5
- ION 5.6
- ION 6.0
- ION 6.1
- ION 6.2
- ION 6.3
- ION 6.4
- New Features Guide
- On-Premises Controller
- Prisma Access CloudBlade Cloud Managed
- Prisma Access CloudBlade Panorama Managed
- Prisma SD-WAN CloudBlades

Configure and Install the AWS Transit Gateway Integration CloudBlade

Setup Application Path Policy Rules

Validate the AWS Transit Gateway Integration CloudBlade

Lets see how to validate the AWS transit gateway integration cloudblade in Prisma SD-WAN.

The Prisma SD-WAN AWS Transit Gateway Integration CloudBlade automatically provisions a pair of vIONs in an AWS Connect VPC. The AWS route tables for the DC IONs are updated to establish a GRE tunnel between the AWS DC vIONs and the Transit Gateway Connect peers. BGP core peering will be established over the GRE tunnel.

The AWS transit gateway ASN number should not match with the Prisma SD-WAN default ASN value of 64512.

The following steps can be used to validate if the CloudBlade is working as intended:

Check the status indicator on the CloudBlade window. Once enabled and deployed correctly, the status indicator should turn green.

If the access credentials are invalid, the status indicator will throw an “Invalid AWS credentials error message”
Check if the Prisma SD-WAN Datacenter site has been created in the AWS cloud and if the vION HA pair has been assigned to this site.
Go to the Active ION’s Interface configuration window and check if the GRE VPN has been created.
1. Click on the interface to check the IP address configuration.
2. Go to the 2nd ION’s interface configuration window and check the GRE tunnel interface configuration.
Check if the core BGP peering between each vION and the Transit Gateway Connect peer is UP.
Check if both the vIONs have learned the prefixes from the Application VPC behind the AWS Transit Gateway and the active ION has learned and advertised the routes.