Dell PowerEdge VRTX - Manual (Page 447)

447
FILE LOCATION: C:\Users\gina\Desktop\Checkout_new\Dell Plasma\User
Guide\Plasma_UGQoS.fm
D E L L CO N F I D E N T I A L – P R E L I MI N A RY 4/ 1 8 /1 3 - F O R PR O O F O N LY
Defining Aggregate Policers Using CLI Commands
The following table summarizes the CLI commands for setting the fields in
the Aggregate Policer pages.
The following is an example of the CLI commands:
Single Policers
Single policers are created by:
1 Create a policy in the Police Table pages
2 Configure the policy in the Policy Class Maps pages. Here the policy class
can be designated as containing a single policer, or it can be designated as
containing Aggregate policers.
Policy Table
A policy can consist of one of the following:
• One or more class maps of ACLs that define the traffic flows in the policy.
• One or more aggregate policers that apply the QoS to the traffic flows in
the policy.
Only those policies that are bound to an interface are active (see the Policy
Binding pages).
After a policy has been added, class maps can be added in the Policy Table
pages.
Table 19-14. Aggregate Policer CLI Commands
CLI Command Description
qos aggregate-policer
aggregate-policer-name
committed-rate-kbps excess-
burst-byte[exceed-action
{drop|policed-dscp-transmit}]
no qos aggregate-policer
aggregate-policer-name
Defines the policer parameters that can
be applied to multiple traffic classes
within the same policy map.
Use the no form of this command to
remove an existing aggregate policer.
console(config)# qos aggregate-policer policer1
124000 9600 exceed-action drop