Aggregate Policer Settings on ESW2-350G Switches

Available Languages

Download Options

  • PDF     (217.5 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (257.6 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (120.1 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:December 11, 2018
Document ID:SMB4171

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Aggregate Policer Settings on ESW2-350G Switches

Objective

The switch uses policies to support per-flow QoS when it is in QoS advanced mode. An aggregate policer applies QoS to multiple class maps, therefore having one or more flows. It supports class maps from different policies and applies QoS to each of its flows in aggregation, hence the name Aggregate Policer. 

This article explains how to set up an aggregate policer on a ESW2-350G Switches.

Note: QoS must be in advanced mode. For more information refer to the article entitled Quality of Service (QoS) Properties on ESW2-350G Switches.

Applicable Devices

• ESW2-350G
• ESW2-350G-DC

Software Version

• 1.3.0.62

Aggregate Policer

Step 1. Log in to the web configuration utility to choose Quality of Service > QoS Advanced Mode > Aggregate Policer. The Aggregate Policer page opens:

Step 2. Click Add to add a policy. The Add Aggregate Policer window appears.

Step 3. At the Aggregate Policer Name field, enter a name for the Aggregate Policer.

Step 4. At the Ingress Committed Information Rate (CIR) field, enter the CIR value. It specifies the amount of bandwidth on a frame relay service.

Step 5. At the Ingress Committed Burst Size (CBS) field, enter the maximum burst size (even if it goes beyond the CIR) in bytes. Committed burst size is the amount of data that a network accepts in a given committed rate measurement interval (Tc). Tc is defined as ratio of CBS to CIR.

Step 6. Click the appropriate radio button in the Exceed Action field to define what action has to be taken when the packets exceed the CIR limit. The possible values are as follows:

• Forward — Forwards the packets which exceed the CIR limit.

• Drop — Drops the packets which exceed the CIR limit.

• Out of Profile DSCP — This replaces the old DSCP values with the new DSCP values based on the Out of Profile DSCP Mapping table for the packets which exceed the CIR limit.

Note: For more information on the Out of Profile DSCP Mapping table, refer to the article entitled Configuration of Out of Profile DSCP Mapping on ESW2-350G Switches.

Step 7. Click Apply to save the changes. 

Step 8. (Optional) To edit the aggregate policer, check the particular aggregate policer and click Edit and follow Steps 3-7.

Step 9. (Optional) To delete the aggregate policer, check the particular aggregate policer and click Delete.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco