QoS CIR Support For Aggregate Bandwidth
Table of Contents
4.0.0 Panorama Managed
Expand all | Collapse all
-
- QoS CIR Support For Aggregate Bandwidth
- Prisma Access for Networks Non-Aggregate Bandwidth Licensing
- IPSec Termination Nodes in Prisma
- IPSec Termination Node Logic (Panorama Managed)
- Determine Region Bandwidth Utilization
- Determine IPSec Termination Nodes Method #1
- Determine IPSec Termination Nodes Method #2
- IPSec Termination Node Conventions and Tag Nomenclature
-
- Onboard an ECMP Site
- Additional ECMP Settings
- Onboard a Non-ECMP Site
- Set Additional Information Tag
- Configure BGP
- Assign Interface-Level Tags for Non-ECMP Sites
- Customize Prisma Access Objects Names using CloudBlade Tag
- Prisma Access for Networks Region List
- Prisma Access CloudBlade Tag Information
- Edit Application Policy Network Rules
- Understand Service and Data Center Groups
- Verify Standard VPN Endpoints
- Configure Standard Groups
- Assign Domains to Sites
- Use Groups in Network Policy Rules
- Enable, Pause, Disable, and Uninstall the Integration
-
- Monitor the Prisma Access for Networks (Panorama managed) CloudBlade
- Understand Prisma SD-WAN and Prisma Access Integration
- Correlate Objects between Prisma SD-WAN and Panorama
- View Standard VPNs at a Site Level
- View Alerts and Alarms
- View Activity Charts
- Use the Device Toolkit
- Check Tunnel Status on Panorama
QoS CIR Support For Aggregate Bandwidth
4.0.0 PIC
In Aggregate Bandwidth licensing mode, the bandwidth allocation is done for a compute
location on
Prisma Access
. The number of tunnels terminating within a compute
location and SPN share the aggregate bandwidth allocated. You must configure the CIR
for specific tunnels terminating on an SPN within a compute location to guarantee
the Quality of Service (QoS). Follow these steps to configure Quality of Service (QoS) in Panorama for aggregate
bandwidth, including adding a QoS profile, enabling QoS, and tagging the QoS profile
on the
Prisma SD-WAN
interface.- Add aQoS Profile.You can edit any existing QoS profile, including the default, by clicking the QoS profile name.
- In Panorama, selectandNetworkNetwork ProfilesQoS ProfileAdda new profile.
- Enter a descriptiveProfile Name.
- Set the overall bandwidth limits for the QoS profile rule.
- Enter anEgress Maxvalue to set the overall bandwidth allocation for the QoS profile rule.
- Enter anEgress Guaranteedvalue (bandwidth that is the guaranteed bandwidth for this profile (in Mbps).
Any traffic that exceeds the Egress Guaranteed value is best effort and not guaranteed. Bandwidth that is guaranteed but is unused continues to remain available for all traffic. - In the Classes section,Addone or more classes and specify how to mark up to eight individual QoS classes.
- Add a class to the QoS Profile.
- Select thePriorityfor the class (eitherreal-time,high,medium, orlow).
- Enter theEgress Maxand theEgress Guaranteedfor traffic assigned to each QoS class.
- Enter aClass Bandwidth Typefor the profile.
- ClickOK.
- SelectCommit and Pushto save the changes.
- ForDefault QoS Profiles, enable QoS for your remote network locations that allocate bandwidth by compute location.
- Determine thePrisma Accesslocations where you want to deploy QoS; then find the compute location that corresponds to each location.Each location is allocated bandwidth from its compute location, and you must know the name of the compute location for the locations where you want to allocate QoS. For a list of compute location-to-location mapping, seePrisma Access, or selectand click the gear icon; the mappings display in thePanoramaCloud ServicesConfigurationRemote NetworksAggregate BandwidthCompute LocationandPrisma Access Locationcolumns.
- Select, click the gear to edit the settings, and selectPanoramaCloud ServicesConfigurationRemote NetworksSettingsQoS.
- Enable QoSat a compute location level.Whatever settings you enter apply to all locations that correspond to this compute location.
- In the case of default QoS profiles, you must enter theQoS Profile, and the Guaranteed Bandwidth Ratio.
- SelectCommitandPushto save the changes.The default QoS profile does not require any configuration changes to be done inPrisma SD-WAN.
- Customize QoS per Site.
- In Panorama, go toand select the site that you wish to customize.SettingsQoSIf you do not wish to use the default profile on the sites, the profile can be customized by using Interface/Circuit level tags inPrisma SD-WAN.
- Check theCustomize Per Sitecheckbox and clickOK.
- SelectCommitandPushto save the changes.
- InPrisma SD-WAN, navigate to theand assign interface level tags in the following format.SiteInterfaces/Circuitsprisma_qos:<profile_name>:[0-100]The profile name for QoS will be the same name as the profile created in Step 1.Interface/Circuit level tagging can be done for both ECMP and Non-ECMP enabled sites inPrisma SD-WAN.
- Non-ECMP: Go to the site onPrisma SD-WANwhere you wish to customize QoS and tag the interface or circuit. In the example shown below, the allocated bandwidth is 20%.After you tag the Interface/Circuit, the CloudBlade integration applies these changes on Panorama.
- ECMP: enabled sites allow customizations per ECMP link. You must tag the ECMP links where you want to apply the QoS customization.After the tags are applied, the CloudBlade integration applies these changes on Panorama.