PDF(226.9 KB) View with Adobe Reader on a variety of devices
ePub(298.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(130.4 KB) View on Kindle device or Kindle app on multiple devices
Updated:December 10, 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.
View Quality of Service (QoS) Aggregate Policer Statistics on 300 Series Managed Switches
QoS policies are used to limit traffic flow. An aggregate policer applies a QoS policy to one or more class maps. The aggregate policer applies the QoS policy over multiple flows of traffic. Incoming traffic is selected with an access list (ACL) and if there is an aggregate policer attached to that traffic class, then it is acted on by the QoS policy of the aggregate policer. Traffic that meets the conditions of the class map of an aggregate policer and falls within the rate limit of the policer will show up as In-Profile Bytes if an entry has been added to monitor that aggregate policer under the Aggregate Policer Statistics page. Matched traffic that exceeds the rate limit defined by the aggregate policer will show up as Out-of-Profile Bytes. Out-of-profile traffic may be dropped, modified, or left alone which depends on how the policy is configured.
A request to track statistics for an aggregate policer must be made before any statistics are recorded and available for viewing.
This article explains how to view aggregate policer statistics on the 300 Series Managed Switches.
Note: Policer configurations are available only in Layer 2 mode of the SG/SF 300 Series Managed Switches. For more information about general policer configurations, refer to the article QoS Advanced Mode Configuration on 300 Series Managed Switches.
• SF/SG 300 Series Managed Switches
Track Aggregate Policer Statistics
Step 1. Log in to the web configuration utility and choose Quality of Service > QoS Statistics > Aggregate Policer Statistics. The Aggregate Policer Statistics page opens:
Step 2. Click Add to create a request for statistics to be tracked on an aggregate policer. The Add Aggregate Policer Statistic window appears.
Step 3. Choose from the Aggregate Policer Name drop-down list the aggregate policer you wish to keep a statistic record.
Step 4. Click Apply to save your configuration.
The picture below depicts the changes after your configuration.
The Aggregate Policer Statistic Table provide the the next information:
• Aggregate Policer Name — The name of the aggregate policer that statistics are being tracked on.
• In-Profile Bytes — The number of bytes that meet the conditions defined by the class maps of the aggregate policer and fall within the specified rate limit of the policer.
• Out-of-Profile Bytes — The number of bytes that meet the conditions defined by the class maps of the aggregate policer and exceed the specified rate limit of the policer.
Step 5. (Optional) To delete an entry in the Aggregate Policer Statistic Table, check the check box of the entry you wish to delete and click Delete.
Step 6. (Optional) To clear the counters of an entry in the Aggregate Policer Statistic Table, check the check box of the entry you wish to clear the counters and click Clear Counters.