Prisma Access for Networks CloudBlade Release 3.1.2
Focus
Focus
Prisma SD-WAN

Prisma Access for Networks CloudBlade Release 3.1.2

Table of Contents

Prisma Access for Networks CloudBlade Release 3.1.2

Learn about the Prisma Access CloudBlade integration with Prisma SD-WAN version 3.1.2 release information.
This document contains the Prisma Access for Networks (managed by Panorama) CloudBlade, Version 3.1.2 release notes.
Prisma Access for Networks (managed by Panorama) requires ION devices to run software version 5.1.9 or later. Versions prior to 5.1.9 are not supported.The recommended software version is 5.4.3 or higher and the minimum software version supported is 5.1.9.

Features Introduced in Prisma Access CloudBlade 3.1.2

The new features Prisma Access CloudBlade version 3.1.2 include:
  • Starting with version 3.1.2, you can configure the Prisma Access CloudBlade in non-aggregate bandwidth licensing mode, where the bandwidth is allocated for the remote network through the CloudBlade integration.
  • Migration is now supported between non-aggregate bandwidth model to aggregate bandwidth model. 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 version 2.2.0-h30.
    When the Non Aggregate Bandwidth to Aggregate Bandwidth migration is completed on Panorama, the following changes will be done by the Panorama Integration Container on SDWAN controller:
    • 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.
  • The QoS parameters for Non-Aggregate Bandwidth mode in Prisma Access CloudBlade 3.1.2 can be configured as part of the interface tagging in Panorama Integration Container (PIC) 3.1.2.
  • Migration is now supported between tunnels for on-premise Prisma Access CloudBlade 2.x versions to Panorama Integration Container (PIC) version 3.1.2.

Compatibility of CloudBlade Version 3.1.2 and Prisma Access

The following table lists the minimum required Prisma Access and Prisma Access Cloud Plugin versions with CloudBlade version 3.1.2.
CloudBlade VersionPrisma Access VersionCloud Plugin Version
3.1.23.1
Minimum Cloud Plugin version supported is 3.1.0-H25.
3.0
Minimum Cloud Plugin version supported is 3.0.0-H26.
2.2
Minimum version supported for the Cloud Plugin is 2.2.0-H44 Preferred.

Limitations and Caveats in Release 3.1.2

The limitations and caveats in Release 3.1.2 are:
  • QoS CIR support is not available in Aggregate Bandwidth model for Prisma Access for Networks CloudBlade.
  • When the QoS Profile is present, Non-Aggregate to Aggregate Bandwidth migration is not allowed.
  • Contact the Palo Alto Support team to ensure that the public IP address of Panorama is added to an allow list to configure and use the 3.1.2 CloudBlade.