21.03.2013 Views

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper 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.

Junos ®<br />

<strong>OS</strong> 12.3 <strong>Ethernet</strong> <strong>Interfaces</strong> <strong>Configuration</strong> Guide<br />

Forwarding Untagged<br />

Layer2 Control Packets<br />

348<br />

to Queue 3<br />

Related<br />

Documentation<br />

queue 1 af-low8;<br />

queue 2 af-high;<br />

queue 3 ef;<br />

queue 4 ops_control;<br />

queue 5 net_control;<br />

queue 6 af-low10_12;<br />

}<br />

restricted-queues {<br />

forwarding-class ef queue-num 0;<br />

forwarding-class af-low8 queue-num 1;<br />

forwarding-class af-low10_12 queue-num 1;<br />

forwarding-class af-high queue-num 2;<br />

forwarding-class be queue-num 3;<br />

}<br />

With this configuration, the FC associated with queue 0 is "ef" (based on the<br />

forwarding-class statement configuration). "ef" maps to restricted-queue number 0<br />

(based on the restricted-queue statement configuration). Hence, with this particular<br />

configuration, untagged ARP, IS-IS, and other untagged Layer 2 control packets would<br />

go to ingress queue 0.<br />

For tagged ARP, IS-IS, or Layer2 control packets, users should configure an explicit<br />

dot1p/dot1ad classifier to make sure these packets are directed to the correct queue.<br />

Without an explicit dot1p/dot1ad classifier, tagged ARP, IS-IS, or Layer 2 control packets<br />

will go to the restricted-queue corresponding to the forwarding class associated with<br />

queue 0.<br />

•<br />

[edit chassis]<br />

forwarding-classes {<br />

queue 0 ef;

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

Saved successfully!

Ooh no, something went wrong!