HP BladeSystem bc2800 Embedded Web System User Guide for the HP BladeSystem PC - Page 170
Defining Aggregate Policer
View all HP BladeSystem bc2800 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 170 highlights
Configuring Quality of Service Defining Aggregate Policer After a packet is classified, the policing process begins. A policer specifies the bandwidth limit for incoming traffic on the classified flow and actions are defined for packets that exceed the limits. These actions include forwarding packets, dropping packets, or remarking packets with a new DSCP value. Aggregate policers enforce limits on a group of flows. An aggregate policer cannot be deleted if it is being used in a policy map. First delete the aggregate policer from all policy maps by using the no police aggregate command before using the no qos aggregate-policer command. The Aggregate Policer page allows network managers to specify the bandwidth limits and define actions to take on packets that do not meet the requirements. To aggregate policies: 1. Click QoS > Advanced Mode > Aggregate Policer. The Aggregate Policer page opens: Aggregate Policer The Aggregate Policer page contains the following fields: ❏ Aggregate Policer Name-Specifies the aggregate policer name. ❏ Ingress CIR - Defines the CIR in bits per second. ❏ Ingress CBS -Defines the CBS in bytes per second. ❏ Exceed Action - Action assigned to incoming information exceeds the traffic limits. Possible values are: ◆ Drop - Drops packets exceeding the assigned bandwidth limits. ◆ Remark DSCP - Flags and remarks packets exceeding the assigned bandwidth limits DSCP values. ◆ None - Forwards packets exceeding the assigned bandwidth limits. 13-14 www.hp.com Embedded Web System User Guide