Add a New Compute Location for a Deployed Prisma Access
Learn about how IP addresses change and how to use a
new compute location for an existing location.
To optimize performance and improve latency,
Prisma Access can introduce new compute locations for
locations you have already deployed as part of a plugin upgrade.
When you upgrade the plugin, the existing compute location-to-location
mapping does not change, but you can choose to take advantage of
the new compute location. If you change the compute location, Prisma
Access changes the gateway and portal IP addresses (for mobile users)
and Service IP addresses (for remote networks and service connections) for
the location or locations to which the new compute location is associated.
If you use allow lists in your network to provide users access to
internet resources such as SaaS applications or publicly accessible
partner applications, you need to add these new IP addresses to
your allow lists.
To upgrade to a new compute location after
it becomes available, complete the following task.
need to allow time to delete and add the existing location and change
your allow lists (for mobile users) or peer IPSec tunnel IP address
(for remote networks and service connections), Palo Alto Networks
recommends that you schedule a compute location change during a
maintenance window or during off-peak hours.
reduce down time for mobile user deployments, use the API to pre-allocate
the new mobile user gateway and portal IP addresses before you perform these
Remote Network deployments only
bandwidth for the new remote network compute locations.
Remote Network deployments that allocate
remote network bandwidth by compute locations only
Click the gear icon in the
Bandwidth Allocation (Mbps)
new compute location.
Wait for the bandwidth to be reflected in the Allocated
Total field at the top of the page; then, click
Delete the Service Connection, Remote Network connection,
or Mobile User location associated with the new compute location.