QoS CIR Support For Aggregate Bandwidth
Focus
Focus
Prisma SD-WAN

QoS CIR Support For Aggregate Bandwidth

Table of Contents

QoS CIR Support For Aggregate Bandwidth

Use QoS CIR support for bandwidth allocation for a compute location in Prisma Access.
Where Can I Use This?What Do I Need?
  • Prisma Access CloudBlade (Panorama Managed).
  • Prisma Access CloudBlade (Cloud Managed).
  • Prisma SD-WAN License.
  • Prisma Access for Networks Subscription.
  • Supported Cloud Plugin Versions.
  • Prisma Access CloudBlade (Cloud Managed) version 3.x.x.
  • Prisma Access CloudBlade (Panorama Managed) versions 3.x.x and 4.x.x.
In Aggregate Bandwidth licensing mode, the bandwidth allocation is done for a compute location on Prisma Access. To use QoS with remote networks, you enable or disable QoS and specify the guaranteed bandwidth at the compute location level. 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).

QoS CIR Support for Aggregate Bandwidth (Panorama Managed CloudBlade)

Create or use an existing QoS CIR to define QoS support for aggregate bandwidth (Panorama Managed CloudBlade).
You use QoS Profiles to shape the traffic at egress point by defining QoS classes and assigning a bandwidth to them. Select either an existing QoS profile or create a new QoS Profile when you enable QoS for Prisma Access.
  1. Add a QoS Profile.
    You can edit any existing QoS profile, including the default, by clicking the QoS Profile name.
    1. In Panorama, select NetworkNetwork ProfilesQoS Profile and Add a new profile.
    2. Enter a descriptive Profile Name.
    3. 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. Unused guaranteed bandwidth continues to remain available for all traffic.
    4. In the Classes section, Add one or more classes and specify how to mark up to eight individual QoS classes.
      • 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.
      • The guaranteed bandwidth assigned to a class isn't reserved for that class; any unused bandwidth remains available for all traffic. If a class of traffic exceeds the egress-guaranteed bandwidth, Prisma Access handles that traffic on a best-effort basis.
      • Enter a Class Bandwidth Type for the profile.
    5. Click OK.
    6. Click OKto save the changes.
  2. For Default QoS Profiles, enable QoS for your remote network locations that allocate bandwidth by compute location.
    1. 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, or select PanoramaCloud ServicesConfigurationRemote NetworksAggregate Bandwidth and click the gear icon; the mappings display in the Compute Location and Prisma Access Location columns.
    2. Select PanoramaCloud ServicesConfigurationRemote NetworksSettings, click the gear to edit the settings, and select QoS.
    3. Enable QoS at a compute location level.
      Whatever settings you enter apply to all locations that correspond to this compute location.
    4. In the case of default QoS Profiles, you must enter the QoS Profile, and the Guaranteed Bandwidth Ratio.
    5. Select Save and Commit your changes.
      The default QoS Profile does not require any configuration changes in Prisma SD-WAN.
  3. Customize QoS per Site.
    1. In Panorama, go to SettingsQoS and select the site that you wish to customize.
      If you don't wish to use the default profile on the sites, the profile can be customized by using Interface or Circuit level tags in Prisma SD-WAN.
    2. Check the Customize Per Site check box and click OK.
    3. Select Commit and Push to save the changes.
  4. 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 or 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 applying the tags, the CloudBlade integration applies these changes on Panorama.

QoS CIR Support for Aggregate Bandwidth (Cloud Managed CloudBlade)

Create or use an existing QoS CIR to define QoS support for aggregate bandwidth (Cloud Managed CloudBlade).
Use QoS to prioritize the critical traffic in your remote networks, and to set maximum and guaranteed bandwidths for remote network sites in a compute location.
  1. Enable QoS for your remote network locations.
    1. Select ManageService SetupRemote NetworksBandwidth Management.
    2. Determine the Prisma Access locations where you want to deploy QoS; then find the compute location that corresponds to each Prisma Access location.
      Each Prisma Access 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.
    3. Enable QoS at a compute location level in the QoS column.
      Any changes in settings apply to all locations corresponding to this compute location.
  2. Edit the QoS settings for the compute location.
    1. Select the guaranteed bandwidth ratio, which is a ratio based on the entire allocated bandwidth for the compute location.
      For example, if you have allocated bandwidth of 1,001 Mbps for the US Southwest compute location, and you enter a guaranteed bandwidth ratio of 82%, the guaranteed bandwidth for that compute location is 820.82 Mbps.
      By default, each remote network is given a percentage equal to the number of connections. For example, given four connections in a compute location and a total guaranteed bandwidth of 820.82 Mbps, each location receives 25% of that bandwidth, which is 205.2 Mbps.
    2. Create New QoS Profile or Manage to edit an existing QoS profile.
    3. Customize QoS settings for remote network sites in a compute location. If you have multiple remote networks per compute location and want to change either the bandwidth ratio or QoS Profile for each remote network, select Customize and change the bandwidth allocation ratio, QoS Profile, or both.
    4. Select Save and Push your changes.
  3. In Prisma SD-WAN, navigate to the SiteInterfaces/Circuits and assign interface or circuit level tags in the following format.
    Format:
    <profile_name>:<qos_bandwidth>
    Example:
    prisma_qos:qos_test:20
    The tags can be both ECMP and Non-ECMP. For 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 40%.
    In ECMP, enabled sites allow customizations per ECMP link. You must tag the ECMP links where you want to apply the QoS customization.
    After applying the tags, the CloudBlade integration applies these changes on the Prisma Access Cloud Management interface.