Focus

Prisma SD-WAN

Prisma Access CloudBlade Integration Release 3.1.5

Table of Contents

Filter

Expand All | Collapse All

Activation & Onboarding
Administration
CloudBlades
Select a Document
- CloudBlade Integrations
- CloudBlades Integration with Prisma Access
Deployment
Incidents & Alerts
Reference
Release Notes
Select a Document
- 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

Learn about the Prisma Access CloudBlade Integration release 3.1 5 release information.

This document contains the Prisma Access for Networks (Cloud managed) CloudBlade, version 3.1.5 release notes.

Features Introduced in Prisma Access CloudBlade 3.1.5

The new features introduced in Prisma Access CloudBlade version 3.1.5 are:

Configure Quality of Service (QoS) in Prisma Access (Cloud managed) for aggregate bandwidth, including creating a QoS profile, editing a QoS profile, and tagging the QoS profile on the Prisma SD-WAN web interface.
Prisma Access deployment can be managed by both Panorama and Cloud Management interfaces. Prisma Access allows Panorama to Cloud Management migration where existing customers can use the in-product workflow to migrate their Prisma Access configuration.
When a new license is purchased which has both Prisma Access and Prisma SD-WAN for a specific tenant, a TSG ID is generated automatically as part of the license. The Prisma Access CloudBlade integrates the Prisma SD-WAN tenant with the Prisma Access tenant under the same TSG ID.

The following caveat is applicable for Release 3.1.5:

When migrating from CloudBlade version 3.1.1 to version 3.1.5 in Non-Aggregate Licensing mode in Prisma Access, tunnels may be rebuilt on sites that use ECMP tagging. The 3.1.5 CloudBlade version now considers all available ports for tunnel formation, rather than just the tagged ones. In such scenarios, you could experience some downtime for such sites. It is recommended to enable the dry run option to identify possible changes during migration to 3.1.5.