QoS policing is 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). If there is an aggregate policer attached to that traffic class, then the QoS policy of the aggregate policer acts on the traffic class. Traffic that meets the conditions of the class map of an aggregate policer and falls within the rate limit of the policer will show 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 shows as Out-of-Profile Bytes. Out-of-profile traffic may be dropped, modified, or left alone as determined by 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 Sx500 Series Stackable Switches.
• Sx500 Series Stackable Switches
• 1.3.0.62
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. A new window appears.
Note: Aggregate policer statistics are not tracked unless a request for statistics is setup.
Step 3. Choose the name of the aggregate policer for which statistics are to be tracked from the Aggregate Policer Name drop-down list.
Step 4. Click Apply to begin tracking statistics for the chosen aggregate policer.
Each aggregate policer that has a request for statistics to be tracked displays the following information:
• Aggregate Policer Name — The name of the aggregate policer for which statistics are being tracked.
• 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) Check the check box for an entry and click Delete to delete the entire entry.
Step 6. (Optional) Click Clear Counters to reset In-Profile bytes and Out-of-Profile bytes statistics to zero.
Revision | Publish Date | Comments |
---|---|---|
1.0 |
13-Dec-2018 |
Initial Release |