QoS CIR Support For Aggregate Bandwidth
Table of Contents
3.1.5 Panorama Managed
Expand all | Collapse all
-
- QoS CIR Support For Aggregate Bandwidth
- Prisma Access for Networks Non-Aggregate Bandwidth Licensing
- IPSec Termination Nodes Within Prisma
- IPSec Termination Node Logic (Panorama Managed)
- Determine Region Bandwidth Utilization
- Determine IPSec Termination Nodes Method #1 (Remote Networking On-Boarding)
- Determine IPSec Termination Nodes Method #2 (Panorama API Method)
- IPSec Termination Node Conventions and Tag Nomenclature
-
- Onboard a Non-ECMP Enabled Site
- Set Additional Information Tag
- Configure BGP
- Assign Interface-Level Tags for Non-ECMP Sites
- 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
-
- Understand Prisma SD-WAN and Prisma Access for Networks 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
- Change Existing Panorama Serial Number Post CloudBlade Integration
QoS CIR Support For Aggregate Bandwidth
315 PA
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.
The
minimum Prisma Access cloud plugin version for the QoS CIR feature
is 3.0.0-H24.
- Add
a QoS Profile. You can edit any existing QoS profile, including the default, by clicking the QoS profile name.
- In Panorama, select NetworkNetwork ProfilesQoS Profile and Add a new profile.
- Enter a descriptive Profile Name.
- Set the overall bandwidth limits for the QoS profile rule.
- Enter an Egress Max value to set the overall bandwidth allocation for the QoS profile rule.
- Enter an Egress Guaranteed value (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, Add one
or more classes and specify how to mark up to eight individual QoS
classes.
- Add a class to the QoS Profile.
- Select the Priority for the class (either real-time, high, medium, or low).
- Enter the Egress Max and the Egress Guaranteed for traffic assigned to each QoS class.
- Enter a Class Bandwidth Type for the profile.
- Click OK.
- Select Commit and Push to save the changes.
- For Default QoS Profiles, enable
QoS for your remote network locations that allocate bandwidth by
compute location.
- Determine the Prisma Access locations 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, see Prisma Access Locations by Compute Location, or select PanoramaCloud ServicesConfigurationRemote NetworksAggregate Bandwidth and click the gear icon; the mappings display in the Compute Location and Prisma Access Location columns.
- Select PanoramaCloud ServicesConfigurationRemote NetworksSettings, click the gear to edit the settings, and select QoS.
- Enable QoS at 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 the QoS Profile, and the Guaranteed Bandwidth Ratio.
- Select Commit and Push to
save the changes.The default QoS profile does not require any configuration changes to be done in Prisma SD-WAN.
- Determine the Prisma Access locations where
you want to deploy QoS; then find the compute location that corresponds
to each location.
- Customize QoS per Site.
- In Panorama, go to SettingsQoS and select the site that
you wish to customize.If you do not wish to use the default profile on the sites, the profile can be customized by using Interface/Circuit level tags in Prisma SD-WAN.
- Check the Customize Per Site checkbox and click OK.
- Select Commit and Push to save the changes.
- In Panorama, go to SettingsQoS and select the site that
you wish to customize.
- In Prisma SD-WAN, navigate to the SiteInterfaces/Circuits and assign
interface level tags in the following format.prisma_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 in Prisma SD-WAN.
- Non-ECMP: Go to the site on Prisma SD-WAN where 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.