Hello Nicolas,
If for example you considered ftp traffic critical and wanted to mark
it "010" at the ingress router so you could give it special priority at
the bottleneck in your network, you would configure:
filter set-prec {
term a {
from {
source-port ftp;
}
then {
output-queue 2;
accept;
}
}
}
and:
output {
interfaces {
ge-1/0/0 {
unit 0 {
precedence-rewrite {
output-queue 2 {
plp-clear rewrite-bits 010;
plp-set rewrite-bits 010;
}
}
}
}
}
}
under the firewall filter and the class of service hierarchies
respectively on the ingress router.
no policers for what want.
Thanks
Sean
On Wed, 8 Aug 2001, Nicolas FEVRIER wrote:
> Hi,
>
> we have ethernet users connected a juniper box and I'm trying
> to configure the JunOS to tag data flows (well-known UDP/TCP
> ports) with IP precedence field in order to use CoS at bottleneck
> points.
> I want to assign IP Prec to
> - "signaling" traffic : Prec 110 (which is default value for
> routing data)
> - "real-time" traffic : Prec 101
> - "application critical" traffic : Prec 010
> - "best effort" traffic : Prec 000
>
> In the JunOS documentation (Sean Capshaw Application Note, ...)
> the incoming traffic has been tagged by others means, but it
> seems difficult to classify traffic and tag it correctly (something
> quite easy to configure in a Cisco box).
>
> The only "solution" I found is to use a firewall filter policer to
> identify
> layer 4 traffic and assign this traffic to an output-queue.
> Then, to use the precedence-rewrite to tag the output-queue traffic.
> Not sure it will work...
>
> Does anybody know how to do it ?
>
> Thanxx all,
>
> Nicolas.
>
>
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:36 EDT