PDF(48.3 KB) View with Adobe Reader on a variety of devices
ePub(91.6 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(155.2 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.
Add Aggregate Policer in QoS Advanced Mode on Sx500 Series Stackable Switches
In QoS advanced mode, the switch uses policies to support per-flow QoS. An aggregate policer is one type of QoS policy where it applies the QoS to one or more class maps, and therefore it has one or more flows. It can support class maps from different policies and will apply the QoS to each of its flows in aggregation, regardless of policies and ports. It actually creates a QoS Action for each flow that sends all matching frames to the same policer (aggregate policer).
This document explains how to set up an aggregate policer on a Sx500 Series Stackable Switch.
• Sx500 Series Stackable Switches
Add Aggregate Policers
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. Enter a name for the Aggregate Policer in the Aggregate Policer Name field.
Step 4. Enter the guaranteed amount of data that can be received from the ingress interface on average, measured in bits per second, in the Ingress Committed Information Rate (CIR) field. Internet Service Provider (ISP) provides this rate based on the subscription.
Step 5. ISP provides Committed Burst Size (CBS) which describes the maximum allowable bandwidth that can be reached. Enter the maximum burst size in bytes in the Ingress Committed Burst Size (CBS) field.
Note: If the bandwidth requirement exceeds the CBS, subscription for a higher CIR is recommended.
Step 6. At the Exceed Action field, click the action to be performed on incoming packets that exceed the CIR. The possible values are as follows:
• Forward — Forwards the packet that exceeds the defined CIR value.
• Drop — Drops the packet that exceeds the defined CIR value.
• Out of Profile DSCP — Remap the DSCP values of packets that exceed the defined CIR value to a value based on the Out Of Profile DSCP Mapping Table.
Step 7. Click Apply. The running configuration file is updated.
Step 8. (Optional) To edit a policer, check the check box of the policer you want to edit, and click Edit.
Step 9. (Optional) To delete a policer, check the check box of the policer you want to delete, and click Edit.