Dell Force10 S25N-S50N FTOS Command Line Reference Guide FTOS 8.4.2.7 E-Series - Page 1197

policy-aggregate c e s Allow an aggregate method of configuring per-port QoS via policy maps. An aggregate QoS policy is part of the policy map (input/output) applied on an interface. Syntax policy-aggregate qos-policy-name To remove a policy aggregate configuration, use no policy-aggregate qos-policy-name command. Parameters qos-policy-name Enter the name of the policy map in character format (32 characters maximum) Defaults No default behavior or values Command Modes CONFIGURATION (policy-map-input and policy-map-output) Command History Version 8.2.1.0 Version 7.6.1.0 Version 7.5.1.0 pre-Version 6.1.1.1 Policy name character limit increased from 16 to 32. Introduced on S-Series Introduced on C-Series Introduced on E-Series Usage Information C-Series and S-Series Aggregate input/output QoS policy applies to all the port ingoing/outgoing traffic. Aggregate input/ output QoS policy can co-exist with per queue input/output QoS policies. 1. If only aggregate input QoS policy exists, input traffic conditioning configurations (rate-police) will apply. Any marking configurations in aggregate input QoS policy will be ignored. 2. If aggregate input QoS policy and per class input QoS policy co-exist, then aggregate input QoS policy will preempt per class input QoS policy on input traffic conditioning (rate-police). In other words, if rate police configuration exists in aggregate QoS policy, the rate police configurations in per class QoS are ignored. Marking configurations in per class input QoS policy still apply to each queue. E-Series Aggregate input/output QoS policy applies to all the port ingoing/outgoing traffic. Aggregate input/ output QoS policy can co-exist with per queue input/output QoS policies. 1. If only an aggregate input QoS policy exists, input traffic conditioning configurations (rate-police) will apply. Any marking configurations in the aggregate input QoS policy will be ignored. 2. If an aggregate input QoS policy and a per-class input QoS policy co-exist, then the aggregate input QoS policy will preempt the per-class input QoS policy on input traffic conditioning (rate-police). In other words, if a rate police configuration exists in the aggregate QoS policy, the rate police configurations in the per-class QoS are ignored. Marking configurations in the per-class input QoS policy still apply to each queue. 3. If only an aggregate output QoS policy exists, egress traffic conditioning configurations (rate-limit and rate-shape) in the aggregate output QoS policy will apply. Scheduling and queuing configurations in the aggregate output QoS policy (if existing) are ignored. Each queue will use default scheduling and queuing configuration (Weighted Random Early Detection (WRED) and Bandwidth). 4. If the aggregate output QoS policy and per-queue output QoS policy co-exist, the aggregate output QoS policy will preempt a per-queue output QoS policy on egress traffic conditioning (rate-limit). In other words, if a rate limit configuration exists in the aggregate output QoS policy, the rate limit Quality of Service (QoS) | 1197