Plan for IP Address Changes for Mobile Users, Remote Networks, and Service Connections
Table of Contents
Plan for IP Address Changes for Mobile Users, Remote Networks,
and Service Connections
After you set up your Prisma Access deployment, it is
useful to know when IP addresses change so that you can pro-actively
plan your infrastructure and add required IP addresses to allow
lists accordingly. The IP address changes can be the result of changes
you made (for example, adding another mobile users location) or
changes that Prisma Access performs automatically (for example,
a large number of mobile users accesses a single Prisma Access gateway).
The following sections describe how IP addresses can change:
IP Address Allocation For Mobile Users
After you deploy Prisma Access for users for the first
time, Prisma Access adds two for each location you onboard. These
IP addresses are unique, not shared, and dedicated to your Prisma
Access deployment. If you have a multitenant setup, Prisma Access
adds dedicated IP addresses for each tenant.
Since the public IP address is the source IP address used by
Prisma Access for requests made to an internet-based source, you
need to know what the public IP address are and add them to an allow
list in your network to provide your users access to resources such
as SaaS applications or publicly-accessible partner applications.
Because Prisma Access adds more public IP addresses when you
add a gateway, and can add more public IP addresses after a scaling
event, you should add an IP Change Event
Notification URL, or use the API to retrieve mobile user
addresses, to be notified of IP address changes in your Prisma Access
infrastructure. You can then add any added or changed addresses
to an allow list.
Public IP Address Scaling Examples for Mobile Users
The following examples illustrate the mobile user public
IP address allocation process that Prisma Access uses during a scaling
event or when you add a new location.
In the following example, you specified two locations in the
Asia Pacific region for a new mobile user deployment: Sydney and
Seoul. Each location is given two gateway IP addresses.
Then a large number of users log in to the Seoul location. To
accommodate these extra users, Prisma Access adds a second gateway
for the Seoul location, takes one of the gateway addresses from
the first Seoul gateway (51.1.1.4) and assigns it to the second
Seoul gateway. It then adds two additional IP addresses (51.1.1.5
and 51.1.1.6 in this example) and adds them to the two Seoul gateways.
Then you add another location, Tokyo, in the Asia Pacific region.
Prisma Access creates two new IP addresses for the new gateway (51.1.1.7
and 51.1.1.8).
Each time you add a location or have a scaling event, you should retrieve the new egress
and gateway IP addresses that Prisma Access assigned and
add them to an allow list in your network. Prisma Access keeps two sets
of IP addresses at all times for all active gateways in each location.
IP Address Changes For Remote Network Connections That Allocate
Bandwidth by Location
This section applies if you have a legacy Prisma Access
deployment that allocates bandwidth
by location. Any new deployments allocate bandwidth by compute
location; to learn about how Prisma Access allocates those IP addresses,
see IPSec Termination Nodes and Service IP Addresses.
IP addresses for remote network connections are unique, not shared,
and dedicated to your Prisma Access deployment. These IP addresses
do not change after Prisma Access creates them as part of remote
network onboarding, and the IP addresses persist after an upgrade.
However, take care when increasing the bandwidth of an existing
connection, because the IP address of a remote network can change
if that increase causes the bandwidth in a location to exceed 500
Mbps.
In addition, egress IP addresses can change if Prisma Access
creates a new compute location and
you decide to use this new compute location with locations you have
already onboarded. See Mobile User, Remote Network, and Service Connection IP Allocation Changes After a Compute Location Change for details.
These bandwidth guidelines apply only when you upgrade an existing
connection. A single remote network connection, even a 1000 Mbps
(Preview) connection, always receives a single
Service
IP Address
, regardless of its size.The 1000 Mbps bandwidth option is in preview mode. The
throughput during preview is delivered on a best-effort basis and
the actual performance will vary depending upon the traffic mix.
The following example shows three remote network connections
in the same location, each with a bandwidth of 150 Mbps. Since the
total bandwidth is 500 Mbps, Prisma Access assigns a single IP address
for all connections in the location.
The following example shows the bandwidth of remote network connection
A being increased from 150 Mbps to 300 Mbps. Since the total bandwidth
of all connections is now more than 500 Mbps, Prisma Access assigns
a new service IP address for the connection with the additional
bandwidth. The other service IP addresses remain unchanged.
Conversely, given four remote networks with a bandwidth of 100
Mbps, if you increase the bandwidth of one of the remote networks
to 100 Mbps, the Service IP address of that remote network does
not change because the total bandwidth is now 500 Mbps.
If you reduce the bandwidth of a remote network connection,
the Service IP address does not change.
To find the service IP addresses in Panorama, select tab and
click the
Remote Networks
radio button to
display the Service IP Address
for the remote
networks, or use the API script.IPSec Termination Nodes and Service IP Addresses
All new deployments starting with Prisma Access 1.8
allocate remote network bandwidth by compute location instead
of by Prisma Access location. You can also upgrade your current
deployment to allocate bandwidth by compute location.
When you onboard a remote network,
you associate it with an
IPSec Termination Node
, and each
IPSec termination node has a Service IP Address
associated
with it. You use the Service IP Address
as
the peer IP address when you set up the IPSec tunnel for the remote network
connection. Each termination node can provide you up to 500 Mbps
of bandwidth. Associating more than 500 Mbps of bandwidth to a compute
location provides you with more than one Service IP Address
.
When you onboard a remote network in an Ireland compute location,
you are given a choice of two IPSec termination nodes, because the
total bandwidth is more than 500 Mbps.
Each IPSec termination node has its own Service IP address, as
can be seen in .
Mobile User, Remote Network, and Service Connection IP Allocation
Changes After a Compute Location Change
To optimize performance and improve latency, Prisma
Access can introduce new compute locations for
existing remote network locations as part of a plugin upgrade. When
you upgrade the plugin, you can choose to take advantage of the
new compute location. If you change the compute region, Prisma Access
changes the gateway and portal IP addresses (for mobile users) and
Service IP addresses (for remote networks) 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.
Since you 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 network deployments), Palo Alto Networks
recommends that you schedule a compute location change during a
maintenance window or during off-peak hours.
To reduce down time for mobile user deployments,
you can use the API to pre-allocate the
new mobile user gateway and portal IP addresses before you perform
these steps.
- Add bandwidth for the new remote network compute locations.
- ((Remote Network deployments that allocate remote network bandwidth by compute locations only) Select .
- Click the gear icon in theBandwidth Allocationarea and addBandwidth Allocation (Mbps)for the new compute location.
- Wait for the bandwidth to be reflected in the Allocated Total field at the top of the page; then, clickOK.
- Delete the Service Connection, Remote Network connection, or Mobile User location associated with the new compute location.
- Commit and push your changes.
- Re-add the locations you just deleted.
- Commit and push your changes.
- (Mobile User deployments only) Retrieve the new gateway and portal IP addresses using the API script and add them to your allow lists.
- (Remote Network and Service Connection deployments only) Change your CPE to point to the new IP addresses for the IPSec tunnel for the remote network connection or service connection.For remote network connections, select , make a note of theService IP Address, and configure the new Service IP Address as the peer address for the remote network IPSec tunnel on your CPE.For service connections, select , make a note of theService IP Address, and configure the new Service IP Address as the peer address for the service connection IPSec tunnel on your CPE.
- Select , make a note of theService IP Address, and configure the newService IP Addressas the peer address for the remote network IPSec tunnel on your CPE.When you delete and re-add a remote network connection, the IP address of the IPSec tunnel on the Prisma Access side changes.
Loopback IP Address Allocation for Mobile Users
Loopback IP addresses can change for mobile users
during an infrastructure or dataplane upgrade.
Loopback IP addresses do not change for service connections
or remote network connections during an infrastructure or dataplane
upgrade; only mobile user loopback IP addresses can change.
Prisma Access allocates the loopback IP addresses from the infrastructure
subnet that you specify when you enable the Prisma
Access infrastructure. You can add the entire infrastructure
subnet to an allow list and avoid planning for mobile user loopback
IP changes during an infrastructure or dataplane upgrade. To find
the infrastructure subnet, select and
view the
Infrastructure Subnet
.Retrieve these addresses using the Retrieve Public, Loopback, and Egress IP Addresses used to retrieve
public IP and loopback IP addresses.
The following example shows a Prisma Access deployment that has
an infrastructure subnet of 172.16.0.0/16. Prisma Access has assigned
loopback IP addresses 172.16.0.1 and 172.16.0.3 for mobile users
from the infrastructure subnet.
After in infrastructure or dataplane upgrade (for example, to
prepare for a new release of the Cloud Services plugin), Prisma
Access assigns two different IP addresses for mobile users from
the infrastructure subnet (172.16.0.1 is changed to 172.16.0.2 and
172.16.0.3 is changed to 172.16.0.4).
