>
    Strata Copilot
    Prisma Access for Networks CloudBlade Release 3.1.3
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma SD-WAN
    3. Prisma Access CloudBlade Integration Release Notes (Panorama Managed)
    4. Prisma Access for Networks CloudBlade Release 3.1.3
    Download PDF
    Prisma SD-WAN

    Prisma Access for Networks CloudBlade Release 3.1.3

    Table of Contents

    Prisma Access for Networks CloudBlade Release 3.1.3

    Learn about the Prisma Access CloudBlade integration with Prisma SD-WAN version 3.1.3 release information.
    This document contains the Prisma Access for Networks (Panorama Managed) CloudBlade, version 3.1.3 release notes.
    Prisma Access for Networks (Panorama Managed) 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.3

    Starting with version 3.1.3, you must generate the Panorama Authorization Key in the Panorama console using the browser XML API for Prisma SD-WAN integration. This key must then be entered in the Prisma Access for Networks (managed by Panorma) CloudBlade configuration page on Prisma SD-WAN.

    Addressed Issues in Prisma Access CloudBlade 3.1.3

    The following table lists the issues addressed in Prisma Access for Networks (managed by Panorama) Release 3.1.3.
    ISSUE IDDESCRIPTION
    CGCBL-969Resolved an issue where Prisma Access Endpoint Liveliness Probes maybe set to 8.8.8.8 instead of the Infrastructure IP.
    CGCBL-959Resolved an issue when using the “prisma_ha_primary” tag on the Active ION could cause the site to fail on-boarding to Prisma Access.
    CGCBL-1001Resolved an issue where removing ECMP Bundle from the Prisma SD-WAN site tag configuration does not delete the Remote Network resources in Prisma Access.
    CGCBL-1052Resolved an issue where during migration of Prisma Access (Panorama managed) CloudBlade from version 2.0.3 to version 3.1.3 with ECMP tunnels without tags at the interface level or circuit level, the tunnels are lost.
    CGCBL-1055Resolved an issue for Non Aggregate to Aggregate Bandwidth migration, where the ECMP Bundles were created only using site level tag (no tags on interfaces). The CloudBlade was unable to recognise the correct tunnels, and hence was removing these tunnels during first run, post migration.

    Upgrade or Downgrade Considerations in Release 3.1.3

    Make sure you understand the following version specific scenarios for release Prisma Access for Networks (managed by Panorama) CloudBlade version 3.1.3.
    • When using Panorama Integration Container version 3.1.2, no additional action is required if you are using h44 version of the plugin and version 3.1.2 is enabled on the CloudBlade configuration page in Prisma SD-WAN.
    • If the deployment is Prisma SD-WAN with Prisma Access using the On-Prem container, the authorization key field in the Cloudblade configuration is not applicable. This only applies to the Cloud Container deployment and once migrated, you are required to configure this field.

    Compatibility of CloudBlade Version 3.1.3 and Prisma Access

    The following table lists the minimum required Prisma Access and Prisma Access Cloud Plugin versions with CloudBlade version 3.1.3.
    CloudBlade VersionPrisma Access VersionCloud Plugin Version
    3.1.33.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.

    © 2026 Palo Alto Networks, Inc. All rights reserved.