Features Introduced in Prisma Access CloudBlade 3.1.2

• 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.