Configure routing settings for your remote network.
| Where Can I Use
This? | What Do I Need? |
|---|
In order for Prisma Access to route traffic to your remote networks, you must provide
routing information for the subnetworks that you want to secure using Prisma Access.
You can do this in several ways. You can either define a static route to each
subnetwork at the remote network site, or configure BGP between your service
connection locations and Prisma Access, or use a combination of both methods.
If you configure both static routes and enable BGP, the static routes take
precedence. While it might be convenient to use static routes if you have just a few
subnetworks at your remote network locations, in a large deployment with many remote
networks with overlapping subnets, BGP will enable you to scale more easily.
Static Routes—To enable static routes to and from your remote site to
Prisma Access, identify the subnetworks or individual IP addresses at the
remote site that you want Prisma Access to secure (for both inbound and
outbound traffic). The subnetworks at each site must not overlap with each
other, with the IP pools that you designated for Prisma Access for Users, or
with the infrastructure subnet.
BGP—If you want to enable BGP to dynamically route traffic to and from
your remote network, you will need to provide the BGP information for the
eBGP router at your branch:
Branch Router Autonomous System (AS) Number—The AS to which
the eBGP router at the remote network belongs. This is called the
Peer AS.
Router ID—The IP address assigned as the Router ID of the eBGP
router on the remote network. This is called the Peer
Address.
If you configure both static routes and BGP routing, the static routes take
precedence.
Here’s how to configure routing settings for your remote network site.
