How to Migrate to the Aggregate Bandwidth (RN) when there is no option from the UI
11678
Created On 03/23/23 13:15 PM - Last Modified 07/11/25 20:10 PM
Objective
Starting with Prisma 1.8 deployments, bandwidth is allocated at an aggregate level per compute location, commonly referred to as Aggregate Bandwidth licensing. Aggregate bandwidth can be enabled on 1.8 and 2.0 Prisma releases.
Each location has a corresponding compute location for which bandwidth is allocated, and all sites you onboard in a compute location share that allocated bandwidth. For example, you want to onboard four branch offices using remote networks in the Singapore, Hong Kong, Thailand, and Vietnam locations. All these locations map to the Asia Southeast compute location.
If 200 Mbps of bandwidth is allocated to the Asia Southeast compute location, all four branch offices will share the 200 Mbps of bandwidth. If one or more sites are not using a large amount of bandwidth, Prisma Access makes the remaining bandwidth available to other sites in that compute location.
Environment
Prisma Access
Procedure
Caveat
The migration to the aggregate bandwidth model is permanent and not reversible. Before you migrate, review the pre-migration checklist. You must Commit and Push your changes for them to take effect.
If you have QoS Profiles with a Class Bandwidth Type of Mbps, Prisma Access notifies you that you should plan to change these profiles to a Class Bandwidth Type of Percentage.
Please note, that when migrating the existing RN's there will be a downtime.
Kindly note that the process can take time in case of re-deployment which can result in new Service IP Address.
1. Login to Panorama CLI
2. Move to Configure Mode
> Configure
3. Check for whether aggregate bandwidth is enabled
'show plugins cloud_services remote-networks agg-bandwidth'
4. Start enabling aggregate bandwidth
'set plugins cloud_services remote-networks agg-bandwidth enabled yes'
5. Commit the changes
6. You should now be able to see the widget in the GUI