Focus

Prisma Access

Changes to Default Behavior for Prisma Access 6.0 and 6.0.1

Table of Contents

Filter

Expand All | Collapse All

Prisma Access Docs

Release Notes
Select a Document
- 6.0 Preferred and Innovation
- 5.2 Preferred and Innovation
- 5.1 Preferred and Innovation
- 5.0 Preferred and Innovation
- 4.2 Preferred
- 4.1 Preferred
- 4.0 Preferred
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
Activation & Onboarding
Administration
Select a Document
- 4.0 & Later
- Prisma Access China
Integrations
Incidents & Alerts

New Features in Prisma Access 6.0 and 6.0.1

Prisma Access Known Issues

Changes to Default Behavior for `Prisma Access` 6.0 and 6.0.1

Where Can I Use This?	What Do I Need?
Prisma Access (Managed by Strata Cloud Manager) Prisma Access (Managed by Panorama)	Prisma Access license Minimum Prisma Access 6.0 version required.

The following table details the changes in default behavior for Prisma Access version 6.0.1.

Component	Change
Remapped Mexico West Location	To better optimize the performance of Prisma Access, the The Mexico West location is remapped to the Mexico West compute location. New deployments have the new remapping applied automatically. If you have an existing Prisma Access deployment that uses one of these locations and you want to take advantage of the remapped compute location, follow the procedure to add a new compute location to a deployed Prisma Access location.

Component

Change

Remapped Mexico West Location

To better optimize the performance of Prisma Access, the The Mexico West location is remapped to the Mexico West compute location.

New deployments have the new remapping applied automatically. If you have an existing Prisma Access deployment that uses one of these locations and you want to take advantage of the remapped compute location, follow the procedure to add a new compute location to a deployed Prisma Access location.

The following table details the changes in default behavior for Prisma Access version 6.0.

Component	Change
Remapped Mexico Central Location	To better optimize the performance of Prisma Access, the Mexico Central location is remapped to the Mexico City, Mexico compute location. New deployments have the new remapping applied automatically. If you have an existing Prisma Access deployment that uses one of these locations and you want to take advantage of the remapped compute location, follow the procedure to add a new compute location to a deployed Prisma Access location. Please note these restrictions for the Mexico Central location and site-based remote networks: X-Large sites are not supported. The maximum bandwidth per service IP will be limited to 2 Gbps instead of 3 Gbps, regardless of whether the selected license type is 2.5 Gbps or if the total of selected licenses falls between 2 Gbps and 3 Gbps. Colo-Connect is not supported.
IP Optimization Migrations Do not Support Automatic Restoration of VPN Connection Timeout Values Longer than 30 Minutes	If you have an existing deployment and upgrade to IP Optimization, and if you have configured an Automatic Restoration of VPN Connection Timeout value in the GlobalProtect portal for greater than 30 minutes, a commit validation is seen after the upgrade to Prisma Access 6.0. To work around this issue, revert your commit, change the Automatic Restoration of VPN Connection Timeout to a value lower than 30 minutes, and redo the Commit and Push operation.

Component

Change

Remapped Mexico Central Location

To better optimize the performance of Prisma Access, the Mexico Central location is remapped to the Mexico City, Mexico compute location.

Please note these restrictions for the Mexico Central location and site-based remote networks:

X-Large sites are not supported.
The maximum bandwidth per service IP will be limited to 2 Gbps instead of 3 Gbps, regardless of whether the selected license type is 2.5 Gbps or if the total of selected licenses falls between 2 Gbps and 3 Gbps.
Colo-Connect is not supported.

IP Optimization Migrations Do not Support Automatic Restoration of VPN Connection Timeout Values Longer than 30 Minutes

If you have an existing deployment and upgrade to IP Optimization, and if you have configured an Automatic Restoration of VPN Connection Timeout value in the GlobalProtect portal for greater than 30 minutes, a commit validation is seen after the upgrade to Prisma Access 6.0.

To work around this issue, revert your commit, change the Automatic Restoration of VPN Connection Timeout to a value lower than 30 minutes, and redo the Commit and Push operation.

New Features in Prisma Access 6.0 and 6.0.1

Prisma Access Known Issues

Prisma Access Docs

Changes to Default Behavior for Prisma Access 6.0 and 6.0.1

Prisma Access Docs

Changes to Default Behavior for `Prisma Access` 6.0 and 6.0.1

Activation & Onboarding

SASE

Cloud-Delivered Security Services

Network Security

Endpoints

Visibility & Monitoring

Best Practices

Experts Corner

Translated Documents