Skip to main content
Versa Networks

Configure QoS

Versa-logo-release-icon.pngFor supported software information, click here.

When a network experiences congestion and delay, you can use quality of service (QoS), also known as class of service (CoS), to prioritize traffic so that more important traffic is handled with a higher priority. QoS allows you to do the following:

  • Prioritize network and application traffic to ensure high priority for essential traffic and to limit traffic for non-essential activities.
  • Control how to share a link's bandwidth among different classes, subnetworks, and users in the network.
  • Allocate bandwidth to internal and external traffic, and to upload and download traffic.
  • Ensure low latency for network traffic that generates revenue for the enterprise.
  • Implement application traffic profiling to ensure bandwidth usage.

QoS examines and classifies all incoming (ingress) traffic on a Versa Operating SystemTM (VOSTM) device, and then schedules the outgoing (egress) traffic so that it is transmitted out the VOS device's interfaces. QoS classifies all ingress traffic packets based on their importance and places related packets into their own forwarding class. For egress traffic, QoS distributes the forwarding classes across interface queues and schedules the transmission for each queue. For ingress traffic, you define policies that accept or deny Layer 2 and application-specific traffic. For both ingress and egress traffic, you can rewrite the DSCP and 802.1p bits in the packet headers.

To define how QoS handles traffic, you configure the following:

  • QoS profiles—QoS profiles define how to police ingress traffic, they assign the ingress traffic to a forwarding class, and they define whether to rewrite the DSCP or 802.1p header bits. A QoS profile can define a per-user policer, based either on IP address or user ID, to police the traffic for individual users, restrict the total number of concurrent users on the device, and restrict the number of sessions allowed for each user. For example, you can restrict YouTube traffic to 10 concurrent users, with 5 Mbps per user, and you can allow 100 concurrent users for voice traffic, with 100 Mbps and two active sessions for each user. You associate a QoS profile with a QoS policy.
  • Application QoS policies—Application QoS policies define how to process ingress traffic based on the application or URL from which the traffic originates. When you define both QoS and application QoS policies, the QoS policy is applied first and the application QoS policy is applied second. This means that the application QoS policy overwrites the QoS policy.
  • Stateless QoS policies—Stateless QoS policies define how to process ingress traffic, including match parameters and actions to take on matching traffic.

This article describes how to configure QoS profiles, application QoS policies, and stateless QoS policies.

Configure QoS Profiles

You configure a QoS profile to:

  • Create ingress policers, which limit the rate of ingress traffic. Ingress policers prevent ingress traffic from overloading a port or device. Ingress policing uses the following parameters:
    • Peak rate—The maximum transmission rate. The maximum supported policer rate is 4 GB. 
    • Burst size—The number of bytes that are allowed beyond the configured peak rate. You set the burst size to avoid retransmission during bursts of traffic.
  • Associate ingress traffic with a forwarding class and loss priority.
  • Define whether to rewrite the DSCP or 802.1p header bits.

To configure a QoS profile:

  1. In Tenant view, select Configure > Secure SD-WAN > QoS & Traffic Steering > QoS.

    qos-navigation.png

    The following screen displays if there are no exiting QoS profiles.

    qos-profiles-tab-add-option.png
    The following screen displays if there are existing QoS profiles. 

    qos-profiles-main.png
  2. Select the Profiles tab.
  3. Click Add QoS Profile or + Add. The Add QoS Profile screen displays 

    add-qos-profile-configuration-tab.png
  4. Click step 1, Configuration, and enter information for the following fields.
     
    Field Description

    Ingress Policing (Group of Fields) 

     
    • Peak Rate (pps)

    Enter how many data packets to allow, in packets per second (pps). All packets that exceed this value are dropped. Entering a peak rate value enables the policer.

    Range: 1 through 4294967295 pps

    Default: None

    • Peak Rate (Kbps)

    Enter the maximum ingress rate, in kilobits per second (Kbps). For Releases 21.2.2 and later, if you enter a peak rate value, the fields on the Per-User Policer tab display. For more information, see Step 6.

    Range: 64 through 4294967295 Kbps

    Default: None

    • Peak Burst Size

    Enter the packet burst size, in bytes.

    Range: 128 through 4294967295 bytes

    Default: None

    Forwarding Class (Group of Fields)  
    • Forwarding Class (Required)
    Select the forwarding class to associate with the profile.
    • Loss Priority (Required)
    Select the loss priority for the forwarding class.
    • DSCP Rewrite
    Click to change the DSCP value in the header of incoming IP packets. The value can be changed to predefined values.
    • Dot IP Rewrite
    Click to rewrite the IEEE 802.1p value of outgoing Ethernet packets. The value can be changed to predefined values.
  5. Click Next to go to step 2, Permissions. The following screen displays. The permission for each role is selected by default, and you can update it. 

    add-qos-profile-permissions-tab.png
  6. To change the permissions for a role, select or deselect the Read, Update, and Delete fields for the role.
  7. Click Next to go to step 3, Review and Submit. In the General section, enter information for the following fields.

    add-qos-profile-review-submit-tab.png
     
    Field Description

    Name

    Enter a name or the rule.

    Description

    (Optional) Enter a description for the rule.

    Tags

    (Optional) Enter one or more tags. A tag is an alphanumeric text descriptor with no spaces or special characters. You can specify multiple tags added for the same object. The tags are used for searching the objects.
  8. Review the settings you have selected. Click the pencil-icon-blue-on-white-22.png Edit icon to change a setting, as needed.
  9. Click Submit.

Configure Application QoS Policies

Similar to stateless QoS policies, application QoS policies define how to handle traffic when a network becomes congested. You define rules for processing mission-critical and latency-sensitive application traffic as well as for processing lower-priority traffic. Application QoS policies are based on Layer 7 protocols, and they are enforced on a per-session basis. In an application QoS policy, you associate QoS classes with specific types of Layer 7 applications, and then you define how to classify traffic for treatment when it transits a QoS-enabled interface.

When you configure both stateless QoS and application QoS policies, the stateless QoS policy is evaluated first and then the application QoS policy. Because the application QoS policy evaluation occurs after the stateless QoS policy evaluation, the forwarding class assigned in the application QoS policy overwrites the one assigned in the stateless QoS policy.

Application QoS policies define traffic-handling parameters for specific applications to ensure optimal performance and user experience. To configure an application QoS policy, you first define rules to classify incoming traffic based on match criteria, such as application, source IP address, destination IP address, and incoming zone. Then, you specify the action to take when traffic matches the configured criteria.

The rules in a policy are evaluated starting with the first rule, that is, from top to bottom in the order in which the rules are displayed in the Concerto rules UI. When a packet matches the criteria defined in a rule, that rule is enforced and all subsequent rules in the policy are ignored. Therefore, to enforce the most specific match, place the more specific rules above the more generic rules, and place generic rules that can match any packets, such as wildcard rules, at the end. After you create policy rules, you can re-order them.

Create an Application QoS Policy

You can create an application QoS policy as part of a main template, or you can create it separately and then associate it with a main template. For more information on main templates, see Configure Main Templates.

  • To create a application QoS policy for an existing main template:
    1. In Tenant view, select Configure > SD-WAN > Main Templates.
    2. Select the main template for which you want to configure the policy.
    3. Click step 5, QoS, Traffic Steering, and Traffic Monitoring. The following screen displays.

      edit-main-template-applicaiton-qos.png
    4. Select the Application QoS tab, and then click Add New Application QoS Policy.
    5. Continue to Configure an Application QoS Policy Rule, below.
  • To create an application QoS  policy separately from a main template:
    1. In Tenant view, select Configure > Secure SD-WAN > QoS & Traffic Steering > QoS.

      qos-navigation.png

      The following screen displays with the Policies > Application QoS Policies tab selected by default.

      application-qos-policies-tab1.png

      If there are no existing QoS policy rules, the following screen displays:

      application-qos-policies-add-option.png
    2. Click + Add or Add Application QoS Policy. The Add Application QoS Policy screen displays. 
    3. Continue to Configure an Application QoS Policy Rule, below.

Configure an Application QoS Policy Rule

  1. In the Add Application QoS Policy screen, click Add Application QoS Rule.

    add-application-qos-policy-rules-tab.png

    The screen displays the workflow to create a rule, beginning with step 1, Applications and URLs.

    create-application-qos-rule-tabs.png
  2. By default, all applications, URLs, and reputations are included in the match criteria. You can include or exclude specific applications, application groups, application categories, URL categories and URL reputations. 

    To specify traffic for application groups, specific applications, application categories, and URL categories and reputations for the rule:
    1. Select the Applications > Application Groups tab.

      applications1.png
    2. To select specific application groups to include or exclude in the rule, click User Defined Application Groups, Predefined Application Groups, or both. Then select the application groups for the rule to match. You can use the Search bar to find specific application groups.
      • To create an Application Group object, click + Add Application Group.
    3. Select the Applications > Applications tab.

      applications2.png
    4. To select specific applications, click User Defined Applications, Predefined Applications, or both. Then select the applications for the rule to match. You can use the Search bar to find specific applications.
    5. Select the Applications > Application Category tab.

      applications3.png
    6. Select one or more user-defined and predefined application categories for the rule to match. You can use the Search bar to find specific application categories.
      • To create an Application Category object, click + Add Application Category. See the See Application Categories section in Configure Reusable Objects.
    7. Select the URLs and Reputations tab. 

      applications4.png
    8. In the URL Categories field, click the down arrow, and then select one or more URL categories for the rule to match.
    9. In the Reputations field, click the down arrow, and then select one or more reputations to include in the rule:
      • High risk
      • Low risk
      • Moderate risk
      • Suspicious
      • Trustworthy
      • Undefined
  3. Click Next or select step 2, Users & User Groups.
  4. By default, all users and user groups are included in the match criteria. To customize which traffic to include or exclude from users & user groups:
    1. Click to select the user type for which you want to apply the rule:
      • All Users—Apply rule for all matched users. This is the default.
      • Selected Users—Apply rule for selected users. 
      • Known Users—Apply rule for all known (authenticated) users. 
      • Unknown Users—Apply rule only for users that are not authenticated. 

        users-match-all.png
    2. If you select the Selected Users option, the following screen displays. 

      users-match-selected-update.png
    3. Click the User and Device Authentication Profile field to select a user authentication profile for the matched users and groups.
    4. On the User Groups tab, click the checkbox for each user group to include. You can search for specific user groups, or click Select All to include all user groups.
    5. Click the Users tab, and then click the checkbox for each user to include. You can search for specific users, or click Select All to include all users. 
  5. Click Next or select step 3, Source & Destination Traffic.
  6. By default, traffic from all source and destination addresses and zones, and all sites, are included in the match criteria. You can include or exclude specific source and destination traffic to match the rule.   

    To match traffic from specific source and destination addresses, zones, and sites:
    1. Select the Source Addresses tab.

      src-dest-traffic-1.png
    2. Select a source address group or address object for the rule to match, or use the search box to find a source address group or object. To exclude the source address or addresses, click Negate Source Address.
      • To create an Address Group object, click the + icon. For more information, see Add Address Group.
      • To create an Address Object, click the + icon. For more information, see Add Address Object in Configure Reusable Objects.
    3. To match on IP range, subnet, or wildcard, enter one or more values in the IP Range, Subnet, or Wildcard fields. 
    4. Select the Destination Addresses tab.

      src-dest-traffic-2.png
    5. Select a destination address group or object for the rule to match, or use the search box to find a source address or object. To exclude the destination address or addresses, click Negate Source Address.
    6. To match on IP range, subnet, or wildcard, enter one or more values in the IP Range, Subnet, or Wildcard fields. 
    7. Click the Enable Match Anycast Address to enable match on an anycast IP address, which is a shared default gateway IP address. 
    8. Select the Source Zones & Sites tab to specify source zones to include in the match criteria. Select one or more source zones or source sites from the lists. You can also select an ingress routing instance.

      src-dest-traffic-3.png
    9. Select the Destination Zones & Sites tab to specify destination zones to include in the match criteria. Select one or more destination zones or destination sites from the lists. You can also select an egress routing instance.

      src-dest-traffic-4.png
  7. Click Next to go to step 4, Source and Destination Geolocation.
  8. Geolocation uses IP addresses to identify the location of connected devices. By default, source and destination traffic from all locations are included in the match criteria. You can specify the source and destination traffic to include or exclude in the match criteria based on geographic location.

    To specify the geographic locations to include or exclude:
     
    1. On the Source Geo Location tab, click the Country drop-down list to select a geographic category to search. 
    2. In the next field, type the name of the country, state, or city. When a match is found, it is added to the Selected list.
    3. To remove a country from the list, click the X next to the country name. To remove all selections, click Clear All.
    4. To exclude the selected geographic locations from the match criteria, click Negate Selection.
    5. Click the Destination Geo Location tab, and repeat steps 8a through 8d.

      geolocation.png
  9. Click Next to go to step 5, Services & DSCP.
  10. By default, all services, service groups, and DSCPs are included in the match criteria. You can specify the services, service groups, and Differentiated Services Code Points (DSCPs) for the rule to match.

    To specify services, service groups, and DSCP to include:
    1. Select the Services tab.

      services-update.png
    2. Select the services to include in the match criteria. To filter the list, click All Services, and select Predefined or User Defined. You can also search by service name.
    3. Select the Service Groups tab.

      service-groups-update.png
    4. Select the service groups to include in the match criteria. You can search by service group name.
      • To create a service group object, click the + icon. For more information, see Add a Service Group in Configure Reusable Objects.
    5. Select the DSCP tab. By default, all DSCP decimal values are included in the match criteria. You can specify which DSCP decimal values to include.

      services-dscp3.png
    6. Select one or more DSCP decimal values. The value range is 0 to 63. You can use the search bar to locate values.
  11. Click Next to go to step 6, QoS Profile.

    create-application-qos-rule-qos-profile-tab.png
  12. In the QoS Profile field, select an existing QoS profile to associate with the rule, or click + Create New to create a new profile. For more information, see Configure QoS Profiles, above.
  13. Click Next to go to step 7, Review and Submit.
  14. In the General section, enter information for the following fields.

    review-submit-rules.png
     
    Field Description
    General (Group of Fields)  
    • Name
    Enter a name or the rule.
    • Description
    (Optional) Enter a description for the rule.
    • Tags
    (Optional) Enter one or more tags. A tag is an alphanumeric text descriptor with no spaces or special characters. You can specify multiple tags added for the same object. The tags are used for searching the objects.
    • Schedule
    Select a schedule to set the time and frequency at which the rule is in effect.
    • Rule Enabled
    Click to disable the rule once it is saved. By default, the rule is enabled.
    • Logging Disabled
    Click to the slider bar to enable logging for the rule. By default, logging is disabled.
  15. Review the remaining sections. Click the pencil-icon-blue-on-white-22.png Edit icon in any section to make changes, as needed.
  16. Click Save Traffic Steering Rule. The Add Application QoS Policy screen displays the saved rule. 

    add-application-qos-policy-rules-added1.png
  17. To add another rule, click + Add in the horizontal menu. You can also select an existing rule and perform the following operations: 
    • Filter—Click the filter-action.pngFilter icon to filter on matching IP address or subnet in any address range. You can also filter on service port number. In the drop-down list, select one of the following:
      • Select IP Address and enter an IP address or IP subnet, and then click Apply.
      • Select Service Port and enter a service port number, and then click Apply.
      • Select IP Address and enter an IP address or IP subnet, and select Service Port and enter a service port number, and then click Apply.
    • Clone—Creates a copy of the rule. You can change the default name of the cloned rule, if desired. The cloned rule then appears in the list of traffic steering rules.
    • Reorder—Reorder the selected policy rule. 
    • Delete—Delete the selected policy rule. 
  18. Continue to Configure Permissions, Review and Submit the Application QoS Policy, below. 

Configure Permissions, Review, and Submit the Application QoS Policy

  1. In the Add Application QoS Policy screen, click Step 2, Permissions. The following screen displays. 
  2. The permission for each role is selected by default, and you can update it.

    qos-permissions-roles.png
  3. To change the permissions for a role, select Read, Update, or Delete in the Permissions column.
  4. Click Next to go to step 3, Review and Submit.
  5. In the General section, enter a name for the application QoS policy. You can also enter a text description for the policy and one or more tags. A tag is an alphanumeric text descriptor with no spaces or special characters. You can specify multiple tags added for the same object. The tags are used for searching the objects.

    review-submit-basic.png
  6. Review the settings you have selected. Click the pencil-icon-blue-on-white-22.png Edit icon to change a setting, as needed.
  7. Click Submit.

Configure Stateless QoS Policies

A stateless QoS policy classifies and prioritizes packets individually, without maintaining any session or flow state information.

To configure a stateless QoS policy, you first create rules to classify incoming traffic based on match criteria, such as source IP address, destination IP address, services, and Layer 2 parameters. Then, you specify the action to take when traffic matches the configured criteria.

Create a Stateless QoS Policy

You can create a stateless QoS policy as part of a main template, or you can create it separately and then associate it with a main template. For more information on main templates, see Configure Main Templates.

  • To create a stateless QoS policy for an existing main template:
    1. In Tenant view, select Configure > SD-WAN > Main Templates.
    2. Select the main template for which you want to configure the policy.
    3. Click step 5, QoS, Traffic Steering, and Traffic Monitoring.

      edit-main-template-stateless-qos-tab.png
    4. Select the Stateless QoS tab, and then click Add New Stateless QoS Policy.
    5. Continue to Configure Stateless QoS Policy Rules below.
  • To create a stateless QoS policy separately from a main template:
    1. In Tenant view, select Configure > Secure SD-WAN > QoS & Traffic Steering > QoS.

      qos-navigation.png
    2. In the Stateless QoS Policies screen, select the Stateless QoS Policies tab.

      application-qos-stateless-policies-tab1.png
    3. Click + Add. The Add Application QoS Policy screen displays. 
    4. Continue to Configure Stateless QoS Policy Rules below.

Configure Stateless QoS Policy Rules

  1. In the Add Stateless QoS Policy screen, click Add Stateless QoS Rules.

    add-stateless-qos-policy-rules-tab.png

    The screen displays the workflow to create a rule, beginning with step 1, Source and Destination Traffic.

    create-stateless-qos-rules-tabs.png
  2. By default, traffic from all source and destination addresses and zones, and all sites, are included in the match criteria. You can include or exclude specific source and destination traffic to match the rule. 

    To match traffic from specific source and destination addresses, zones, and sites:  
    1. Select the Source Addresses tab.

      src-dest-traffic-1.png
    2. Select a source address group or address object for the rule to match, or use the search box to find a source address group or object. To exclude the source address or addresses, click Negate Source Address.
    3. To match on IP range, subnet, or wildcard, enter one or more values in the IP Range, Subnet, or Wildcard fields. 
    4. Select the Destination Addresses tab.

      src-dest-traffic-2.png
    5. Select a destination address group or object for the rule to match, or use the search box to find a source address or object. To exclude the destination address or addresses, click Negate Source Address.
    6. To match on IP range, subnet, or wildcard, enter one or more values in the IP Range, Subnet, or Wildcard fields. 
    7. Click the Enable Match Anycast Address to enable match on an anycast IP address, which is a shared default gateway IP address. 
    8. Select the Source Zones & Sites tab to specify source zones to include in the match criteria. Select one or more source zones or source sites from the lists. You can also select an ingress routing instance.

      src-dest-traffic-3.png
    9. Select the Destination Zones & Sites tab to specify destination zones to include in the match criteria. Select one or more destination zones or destination sites from the lists. You can also select an egress routing instance.

      src-dest-traffic-4.png
  3. Click Next to go to step 2, Services & DSCP.
  4. By default, all services, service groups, and DSCPs are included in the match criteria. You can specify the services, service groups, and Differentiated Services Code Points (DSCPs) for the rule to match.

    To specify services, service groups, and DSCP to include:
    1. Select the Services tab.

      services-dscp1.png
    2. Select the services to include in the match criteria. To filter the list, click All Services, and select Predefined or User Defined. You can also search by service name.
      • To create a services object, click + Add User Defined. <link here>
    3. Select the Service Groups tab.

      services-dscp2.png
    4. Select the service groups to include in the match criteria. You can search by service group name.
      • To create a service group object, click + Add User Defined. <link here>
    5. Select the DSCP tab. By default, all DSCP decimal values are included in the match criteria. You can specify which DSCP decimal values to include.

      services-dscp3.png
    6. Select one or more DSCP decimal values. The value range is 0 to 63. You can use the search bar to locate values.
  5. Click Next to go to step 3, Layer 2.
  6. To classify packets that an interface receives based on Layer 2 fields, enter information for the following fields.

    create-stateless-qos-rules-layer2-tab.png
     
    Field Description

    MAC Address Type

    Select the MAC address type to match:

    • Broadcast
    • Multicast

    Ether Type (Group of Fields)

     
    • None
    Select if you do not want to classify incoming packets based on Ether type.
    • Ether Type

    Select to match by name, and then select the Ether type of incoming packets:

    • ARP
    • IPv4
    • IPv6

     

    ether-type-option.png

    • Ether Type Value

    Select to match by value, and then enter a numeric value between 1536 through 65535.
     

    ether-type-value-option.png

    IEEE 802.1p Priority Values Enter a value (0 through 7) for the IEEE 802.1p Priority Code Point (PCP) in the VLAN tag at Layer 2 to specify the frame priority for QoS handling in Ethernet networks. 
  7. Click Next to go to step 4, QoS Profile.
  8. Enter information for the following fields.

    create-stateless-qos-rules-qos-profile-tab.png
     
    Field Description

    Action 

    Click the action to take on traffic that matches the rule:

    • Allow—Permit traffic that matches the rule.
    • Deny—Do not permit traffic that matches the rule.
    • Bypass Service—Route traffic that matches the rule, but do not perform any service-related processing or create a session for the traffic.
    QoS Profile Select an existing QoS profile to associate with the rule or click + Create New to create a new QoS profile. For more information, see Configure QoS Profiles above.
    Permit Existing Flow

    Select how to apply the rule to an existing flow for TCP sessions created by a non-SYN TCP packet:

    • Allow—Select to allow the existing TCP flows with minimal services.
    • Validate—Select to allow the existing TCP flows with all services applicable in the service chain.
  9. Click Next to go to step 5, Review and Submit.
  10. In the General section, enter information for the following fields.

    review-submit-rules.png
     
    Field Description
    General (Group of Fields)
    • Name
    Enter a name or the rule.
    • Description
    (Optional) Enter a description for the rule.
    • Tags
    (Optional) Enter one or more tags. A tag is an alphanumeric text descriptor with no spaces or special characters. You can specify multiple tags added for the same object. The tags are used for searching the objects.
    • Schedule
    Select a schedule to set the time and frequency at which the rule is in effect.
    • Rule Enabled
    Click to disable the rule once it is saved. By default, the rule is enabled.
    • Logging Disabled
    Click to the slider bar to enable logging for the rule. By default, logging is disabled.
  11. Review the remaining sections. Click the pencil-icon-blue-on-white-22.png Edit icon in any section to make changes, as needed.
  12. Click Save Traffic Steering Rule. The Add Stateless QoS Policy screen displays the saved rule. 

    add-stateless-qos-policy-rules-added1.png
  13. To add another rule, click + Add in the horizontal menu. You can also select an existing rule and perform the following operations: 
    • Filter—Click the filter-action.pngFilter icon to filter on matching IP address or subnet in any address range. You can also filter on service port number. In the drop-down list, select one of the following:
      • Select IP Address and enter an IP address or IP subnet, and then click Apply.
      • Select Service Port and enter a service port number, and then click Apply.
      • Select IP Address and enter an IP address or IP subnet, and select Service Port and enter a service port number, and then click Apply.
    • Clone—Creates a copy of the rule. You can change the default name of the cloned rule, if desired. The cloned rule then appears in the list of traffic steering rules.
    • Reorder—Reorder the selected policy rule. 
    • Delete—Delete the selected policy rule. 
  14. Continue to Configure Permissions, Review and Submit the Stateless QoS Policy. 

Configure Permissions, Review, and Submit the Stateless QoS Policy

  1. In the Add Stateless QoS Policy screen, click step 2, Permissions. The following screen displays.

  2. The permission for each role is selected by default, and you can update it. To change permissions for a role, select or deselect the Create, Read, Update, and Delete fields for the role.

    permissions.png
  3. To change the permissions for a role, select Edit, Hide, or Read in the Permissions column.
  4. Click Next to go to step 3, Review and Submit.
  5. In the General section, enter a name for the stateless QoS policy. You can also enter a text description for the policy and one or more tags. A tag is an alphanumeric text descriptor with no spaces or special characters. You can specify multiple tags added for the same object. The tags are used for searching the objects.

    review-submit-basic.png
  6. Review the settings you have selected. Click the pencil-icon-blue-on-white-22.png Edit icon to change a setting, as needed.
  7. Click Submit.

Manage Application and Stateless QoS Policies

You can perform the following actions on application and stateless QoS policies:

  • Filter
  • Edit
  • Clone
  • Delete
  • View references
  • Propagate
  • Compare versions
  • View the audit log
  • Enable and disable auto delete

For information about these actions, see Manage SD-WAN Policies and Profiles.

Supported Software Information

Releases 13.1.1 and later support all content described in this article.

Additional Information

Manage SD-WAN Policies and Profiles