At least two (often more)

Prisma Access

locations that are geographically near each other are grouped in to compute locations. This is the level at which you allocate bandwidth, instead of allocating bandwidth for individual

Prisma Access

locations or for specific remote network sites. It means that

Prisma Access

can dynamically allocate bandwidth to sites in a compute location based on load or demand.

For example, you need to onboard four branch offices using remote networks in the Singapore, Thailand, and Vietnam locations. All these locations map to the Asia Southeast compute location. If you allocate 200 Mbps bandwidth to the Asia Southeast compute location,

Prisma Access

divides the 200 Mbps of bandwidth between the four branch offices you onboarded in that location. If you also add a location in Hong Kong, you note that Hong Kong maps to the Hong Kong compute location, and you would need to add bandwidth to that compute location. Specify a minimum bandwidth of 50 Mbps per compute location.

Prisma Access

dynamically allocates the bandwidth based on load or demand per location. Using the previous example where the four sites collectively use up to 200 Mbps, if one or more sites are not using as much bandwidth as the other sites,

Prisma Access

provides more bandwidth for the locations that are more in demand, giving you a more efficient use of allocated bandwidth. In addition, if one of the sites goes down,

Prisma Access

reallocates the bandwidth between the other sites that are still up in that compute location.

To get started, go to

Manage

Service Setup

Remote Networks

Bandwidth Management

.

To help you determine how much bandwidth a specific site needs, consider the bandwidth available from your ISP at each location. When calculating the amount of bandwidth you need at a site, consider that the bandwidth usage includes both egress and ingress traffic for the remote network connection.