02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

• You cannot apply an input Layer 2 QoS policy on an interface you also configure with vlan-stack<br />

access.<br />

• If you apply a service policy that contains an ACL to more than one interface, <strong>FTOS</strong> uses ACL<br />

optimization to conserves CAM space. The ACL Optimization behavior detects when an ACL already<br />

exists in <strong>the</strong> CAM and ra<strong>the</strong>r than writing it to <strong>the</strong> CAM multiple times.<br />

Create Output Policy Maps<br />

Create Output Policy Maps is supported only on plat<strong>for</strong>m e<br />

1. Create an ouput policy map using <strong>the</strong> command policy-map-output from CONFIGURATION mode.<br />

2. Once you create an output policy map, do one or more of <strong>the</strong> following:<br />

• Apply an output QoS policy to a queue<br />

• Specify an aggregate QoS policy<br />

• Apply an output policy map to an interface<br />

3. Apply <strong>the</strong> policy map to an interface. See page 573.<br />

Apply an output QoS policy to a queue<br />

Apply an output QoS policy to queues using <strong>the</strong> command service-queue from INTERFACE mode.<br />

Specify an aggregate QoS policy<br />

Specify an aggregate QoS policy using <strong>the</strong> command policy-aggregate from POLICY-MAP-OUT mode.<br />

Apply an output policy map to an interface<br />

Apply an input policy map to an interface using <strong>the</strong> command service-policy output from INTERFACE<br />

mode. You can apply <strong>the</strong> same policy map to multiple interfaces, and you can modify a policy map after<br />

you apply it.<br />

Weighted Random Early Detection<br />

Weighted Random Early Detection is supported only on plat<strong>for</strong>m e<br />

Weighted Random Early Detection (WRED) congestion avoidance mechanism that drops packets to<br />

prevent buffering resources from being consumed.<br />

Traffic is a mixture of various kinds of packets. The rate at which some types of packets arrive might be<br />

greater than o<strong>the</strong>rs. In this case, <strong>the</strong> space on <strong>the</strong> BTM (ingress or egress) can be consumed by only one or<br />

a few types of traffic, leaving no space <strong>for</strong> o<strong>the</strong>r types. A WRED profile can be applied to a policy-map so<br />

that specified traffic can be prevented from consuming too much of <strong>the</strong> BTM resources.<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 573

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!