If your license includes remote networks or service connections,
.
Prisma Access uses the infrastructure subnet to create the
network backbone for communication between your branch sites, mobile
users and the Prisma Access security infrastructure, as well as
with the HQ and data center networks you plan to connect to Prisma Access over service connections.
Prisma Access provides you with a default
Infrastructure Subnet of
192.168.255.0/24. If you want to create a custom infrastructure
subnet:
Note: In addition to this Infrastructure Subnet, Prisma Access
provides you a default
Client IP Pool of
100.127.0.0/16. Prisma Access assigns an IP address from this
pool to each GlobalProtect-connected device. We recommend that
the number of IP addresses in this pool is 2 times the number of
mobile user devices that will connect to Prisma Access. If you
want to modify this subnet,
you can do so after
you complete the onboarding workflow.
- Use an RFC 1918-compliant subnet. While the use of non-RFC
1918-compliant (public) IP addresses is supported, we don't
recommend it because of possible conflicts with the internet
public IP address space.
Don’t specify any subnets that overlap with the
169.254.0.0/16 and 100.64.0.0/10 subnet range because Prisma Access reserves those IP addresses and subnets
for its internal use.
This subnetwork is an extension to your existing network and
therefore, can’t overlap with any IP subnets that you use
within your corporate network or with the IP address pools
that you assign for Prisma Access for users or Prisma Access for networks.
Because the service infrastructure requires a large number of
IP addresses, you must designate a /24 subnetwork (for
example, 172.16.55.0/24).
For the BGP AS, enter an RFC 6996-compliant
BGP AS number. This number identifies the routes through which BGP
can send traffic. If you don’t supply an AS number, Prisma Access uses the default AS number (65534).
The BGP Private AS number is the autonomous system (AS)
