Prisma SD-WAN
IPSec Termination Nodes Within Prisma (Cloud Managed CloudBlade)
Table of Contents
Expand All
|
Collapse All
Prisma SD-WAN Docs
-
-
-
- CloudBlade Integrations
- CloudBlades Integration with Prisma Access
-
-
-
-
- 6.5
- 6.4
- 6.3
- 6.2
- 6.1
- 5.6
- New Features Guide
- On-Premises Controller
- Prisma SD-WAN CloudBlades
- Prisma Access CloudBlade Cloud Managed
- Prisma Access CloudBlade Panorama Managed
IPSec Termination Nodes Within Prisma (Cloud Managed CloudBlade)
Select IPSec termination nodes within Prisma Access in the aggregate licensing model
for Cloud Managed CloudBlade.
The IPSec Termination Node logic for Prisma Access for Networks (Cloud
Managed) CloudBlade, in the Aggregate Bandwidth model, involves assigning bandwidth to a
compute region within Prisma Access.
Go to ConfigurationNGFW and Prisma AccessRemote NetworksBandwidth Management and view the which Prisma Access, regions are configured to allocate
bandwidth for that region.

If looking at two locations, namely US East, and US Central, you can see the respective
bandwidth allocated for each region as shown below.

With Prisma Access for Networks utilizing the Aggregate Bandwidth model, for every
500 Mbps of bandwidth allocation, a compute instance will be added to support the
throughput requirements.
The compute instances behind a region are referred to as the IPSec Termination Nodes and
are visible when configuring a Remote Network onboarding.
Determine Region Bandwidth Utilization
Prior to deploying on any previous
IPSec termination nodes, a utilization of the current region bandwidth if there are
preexisting VPN tunnels should be analyzed. To view the utilization, navigate to ConfigurationNGFW and Prisma AccessRemote Networks.
Select the site where you want to view the performance data. For the given region,
any data if present, will show in a graph, with options to choose for different time
ranges.