PDF(193.8 KB) View with Adobe Reader on a variety of devices
ePub(265.7 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(114.3 KB) View on Kindle device or Kindle app on multiple devices
Updated:December 11, 2018
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-550X Switch
The switch uses policies to support per-flow QoS when it is in QoS advanced mode. An aggregate policer applies Quality of Service (QoS) to multiple class maps. 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-550X Switches.
Step 1. Log in to the web configuration utility, and 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 page opens.
Step 3. From the Aggregate Policer Name drop-down list, choose an Aggregate Policer.
Step 4. In the Ingress Committed Information Rate (CIR) field, enter the CIR value. CIR specifies the amount of bandwidth on a frame relay service.
Step 5. In 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 Differentiated Services Code Point (DSCP) values with the new DSCP values based on the Out of Profile DSCP Mapping table for the packets which exceed the CIR limit.