>
    Upgrade Considerations for Panorama Managed Prisma Access (4.1 Preferred)
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma Access
    3. Panorama Support for Prisma Access 4.1 Preferred
    4. Upgrade Considerations for Panorama Managed Prisma Access (4.1 Preferred)
    Download PDF
    Prisma Access

    Upgrade Considerations for Panorama Managed Prisma Access (4.1 Preferred)

    Table of Contents

    Upgrade Considerations for Panorama Managed Prisma Access (4.1 Preferred)

    If you're using Panorama to manage Prisma Access, here's what to consider when upgrading to Prisma Access 4.0.
    An infrastructure and dataplane upgrade is required for all upgrades from an existing Panorama Managed Prisma Access version to 4.1 Preferred, including if you are upgrading from any Prisma Access Innovation version to 4.1 Preferred. After you download and install the Cloud Services plugin 4.1, you receive all supported features in Prisma Access to date, including 4.1 features and all previous Innovation and Preferred features.
    The Cloud Services plugin version 4.1 supports 10.0.8 and 10.1.3-based Prisma Access dataplane versions; however, not all new features in the plugin are supported until your dataplane has been upgraded to PAN-OS version 10.2.4.
    To upgrade your Cloud Services plugin to Prisma Access 4.1 Preferred, use one of the following upgrade paths. To find your current plugin version in Panorama, select PanoramaCloud ServicesConfigurationService Setup and check the plugin version in the Plugin Alert area.
    Be sure to follow the minimum Panorama versions for each plugin version during the upgrade.
    Installed Cloud Services Plugin VersionTargeted VersionPlugin Upgrade Path
    4.0 Preferred4.1 Preferred
    Upgrade your plugin to Prisma Access 4.1 and commit and push your changes.
    3.0, 3.1, and 3.2 Preferred4.1 Preferred
    1. (3.0 plugins only) Upgrade your plugin to Prisma Access 3.1 and commit and push your changes.
    2. (3.1 plugins only) Upgrade your plugin to either Prisma Access 3.2 or 3.2.1 and commit and push your changes.
    3. Upgrade your plugin to either Prisma Access 3.2 or 3.2.1 and commit and push your changes.
    4. Upgrade your plugin to Prisma Access 4.0 and commit and push your changes.
    5. Upgrade your plugin to Prisma Access 4.1 and commit and push your changes.
    2.2 Preferred4.1 Preferred
    1. Upgrade your plugin to Prisma Access 3.0 and commit and push your changes.
    2. Upgrade your plugin to Prisma Access 3.1 and commit and push your changes.
    3. Upgrade your plugin to either Prisma Access 3.2 or 3.2.1 and commit and push your changes.
    4. Upgrade your plugin to Prisma Access 4.0 and commit and push your changes.
    5. Upgrade your plugin to Prisma Access 4.1 and commit and push your changes.
    Releases earlier than 2.2 Preferred4.1 Preferred
    1. Upgrade your plugin to Prisma Access 2.2 and commit and push your changes.
      If your deployment is on a version of Prisma Access that is earlier than 2.2 Preferred, you must first upgrade to 2.2 before you can upgrade to 3.2. Upgrades from 2.0 or 2.1 versions of Prisma Access are not supported.
    2. Upgrade your plugin to Prisma Access 3.0 and commit and push your changes.
    3. Upgrade your plugin to Prisma Access 3.1 and commit and push your changes.
    4. Upgrade your plugin to either Prisma Access 3.2 or 3.2.1 and commit and push your changes.
    5. Upgrade your plugin to Prisma Access 4.0 and commit and push your changes.
    6. Upgrade your plugin to Prisma Access 4.1 and commit and push your changes.

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