[j-nsp] Rewriting ToS on the edge
Richmond, Jeff (ELI)
jeff_richmond at eli.net
Mon Dec 13 10:54:10 EST 2004
Jerome, you would want something along these lines I believe (I am using EXP
here, but you just need to substitute for DSCP or Precedence). I believe
this worked fine last time I tested it, but it has been a while. Basically,
I am taking anything marked 010 or 011 and rewriting it to 010, and 000 I am
leaving at 000.
class-of-service {
classifiers {
exp TEST-EXP-CLASSIFIER {
forwarding-class HIGH-PRIORITY {
loss-priority low code-points 010;
loss-priority high code-points 011;
}
forwarding-class BEST-EFFORT {
loss-priority low code-points 000;
}
}
}
interfaces {
so-* {
unit 0 {
scheduler-map TEST-SCHED-MAP;
classifiers {
exp TEST-EXP-CLASSIFIER;
}
rewrite-rules {
exp TEST-EXP-REWRITE;
}
}
}
}
rewrite-rules {
exp TEST-EXP-REWRITE {
forwarding-class HIGH-PRIORITY {
loss-priority low code-point 010;
}
forwarding-class BEST-EFFORT {
loss-priority low code-point 000;
}
}
}
-Jeff
-----Original Message-----
From: Jerome Fleury [mailto:jeje at jeje.org]
Sent: Monday, December 13, 2004 6:54 AM
To: juniper-nsp at puck.nether.net
Subject: [j-nsp] Rewriting ToS on the edge
Hi there,
I'm looking for a simple way to rewrite the ToS of every incoming packet on
an interface (edge
interface) to 0. As I understand the Juniper philosophy, I should mark it on
the incoming
interface, and rewrite the ToS on each output interface.
This looks a bit tricky for such a simple task. Is there any shortcut for
that ?
Thanks.
Jerome Fleury.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list