Routing for Service Connection Traffic
How Prisma Access routes its service connection traffic
from mobile users and remote network connections, and the different
modes you can use.
Prisma Access uses BGP for dynamic routing,
and uses BGP path selection to install routes in the route table.
When Prisma Access routes traffic to your headquarters or data center
using service connections, it uses routing methods that direct that
traffic effectively. Prisma Access uses a default routing model
that was designed to fit the majority of network deployments; however,
not all organization’s networks are the same. To fit a wider range
of deployments, Prisma Access allows you choose another mode for
service connection routing.
Changing the Prisma Access service connection
routing method requires a thorough understanding of your organization’s
topology and routing devices, along with an understanding of how
Prisma Access routing works as described in this section. Read this
section carefully before changing the routing method from the default
setting.
Prisma Access supports static routing and dynamic routing using
BGP for service connections and remote network connections; this
section assumes that you use BGP routing for your Prisma Access deployments.
When you select BGP routing, your organization’s network learns
BGP information from Prisma Access.
You can choose from the following routing modes with Prisma Access:
Default routing—This
is the default routing model that Prisma Access uses.
Use
this routing mode if you want Prisma Access to use BGP best path-selection
mechanisms without adjusting any of the BGP attributes. In this
mode, Prisma Access will honor any attribute advertised by the customer
premises equipment (CPE).
Hot Potato routing—Prisma
Access hands off the traffic as quickly as it can to your organization’s
network.
Use this routing method if you want your organization’s
network to perform the majority of routing decisions.
