Prisma Access for Networks Non-Aggregate Bandwidth Licensing
Table of Contents
Expand all | Collapse all
-
- QoS CIR Support For Aggregate Bandwidth
- Prisma Access for Networks Non-Aggregate Bandwidth Licensing
- IPSec Termination Nodes in Prisma
- IPSec Termination Node Logic (Panorama Managed)
- Determine Region Bandwidth Utilization
- Determine IPSec Termination Nodes Method #1 (Remote Networking On-Boarding)
- Determine IPSec Termination Nodes Method #2 (Panorama API Method)
- IPSec Termination Node Conventions and Tag Nomenclature
-
- Onboard a Non-ECMP Site
- Set Additional Information Tag
- Configure BGP
- Assign Interface-Level Tags for Non-ECMP Sites
- Customize Prisma Access Objects Names using CloudBlade Tag
- Prisma Access for Networks Region List
- Prisma Access CloudBlade Tag Information
- Edit Application Policy Network Rules
- Understand Service and Data Center Groups
- Verify Standard VPN Endpoints
- Configure Standard Groups
- Assign Domains to Sites
- Use Groups in Network Policy Rules
- Enable, Pause, Disable, and Uninstall the Integration
-
- Monitor the Prisma Access for Networks (Panorama Managed) CloudBlade
- Understand Prisma SD-WAN and Prisma Access for Networks Integration
- Correlate Objects between Prisma SD-WAN and Panorama
- View Standard VPNs at a Site Level
- View Alerts and Alarms
- View Activity Charts
- Use the Device Toolkit
- Check Tunnel Status on Panorama
- Change Existing Panorama Serial Number Post CloudBlade Integration
Prisma Access for Networks Non-Aggregate Bandwidth Licensing
Prisma Access
for Networks Non-Aggregate Bandwidth Licensing316 PIC
Configure the
Prisma Access
CloudBlade
in the non-aggregate bandwidth licensing mode, where the bandwidth
is allocated for the remote network through the CloudBlade integration. Non-Aggregate to Aggregate Bandwidth Migration
In
Prisma Access
, the aggregate bandwidth model is available for all
new deployments. If you have an existing deployment that allocates
bandwidth by location (non-aggregate bandwidth model), you can migrate from allocating
bandwidth per location to allocating bandwidth per compute location (aggregate
bandwidth model). This migration feature is enabled from Prisma
Access release version2.2.0-H30
2.2.0-H35
onwards.You can
verify the completion of the non-aggregate to aggregate migration tasks
in the Panorama system logs.
![](/content/dam/techdocs/en_US/dita/_graphics/uv/prisma/prisma-sd-wan/cloudblades/migration-nonagg-agg1.png)
When
the Non-Aggregate Bandwidth to Aggregate Bandwidth migration is complete
on Panorama, the
Prisma SD-WAN
interface tags are updated to the Aggregate
Bandwidth form, and the following changes are done by the Panorama Integration
Container (PIC) on the SD-WAN controller:![](/content/dam/techdocs/en_US/dita/_graphics/uv/prisma/prisma-sd-wan/cloudblades/migration-nonagg-agg2.png)
The CloudBlade will not allow any new
changes made to the sites until the above process is complete. It
will display the following message
Non Aggregate to Aggregate
Bandwidth Migration is in progress
in the CloudBlade Messages
tab.- If a circuit tag exists, the circuit tag is updated with the SPN Name: if an interface tag exists, the interface tag is updated with the corresponding SPN Name for the Remote Network.
- If a circuit tag exists and no interface tagging exists: Circuit Tag is updated with the SPN Name and the Interface tag will be updated if the corresponding Remote Network ends on a different SPN Name than the circuit tagged SPN Name.
This capability
is not supported for remote networks if you use the Aggregate Bandwidth
mode.
QoS for Non-Aggregate Bandwidth
The QoS parameters for Non-Aggregate
Bandwidth mode in
Prisma Access
CloudBlade can be configured as
part of the interface tagging in Panorama Integration Container
(PIC). Following is the format in which the interface tag is specified.Format: prisma_qos:<QoSProfileName>
Example: PRISMA_QOS: test_profile
This
capability is not supported for remote networks if you use the Aggregate
Bandwidth mode.