Re: [j-nsp] CoS Marking/Rewrite Theory
On Monday 06 October 2008 14:34:43 Pekka Savola wrote: > FWIW, > > "I do not want packets that already have a DSCP bit > assigned to be rewritten" appears to be a sentiment that > Juniper isn't very committed to. In earlier M-series, you > could rewrite DSCP's on some forwarding classes only. On > T-series and M320, if you haven't configured a rewrite > rule on all the forwarding classes, the router ends up > clearing DSCPs for the other forwarding classes, with no > possibility to preserve the DSCP. > > http://www.juniper.net/techpubs/software/junos/junos92/sw >config-cos/assigning-the-rewrite-rules-configuration-to-th >e-output-logicalinterface.html > > Pretty annoying. Too bad these kinds of issues seem to > crop up more and more, usually after you've already > bought the box or a new kind of interface :-/ So I was following up with our SE on this earlier in the week, and he has raised an ER for this with the developers - but it's just that one, I think. We'd need to get more requests in for it to become a consideration. If any of you have a sizeable deal going through with Juniper, and need this, this could move things forward quickly if it was a dependence. In the interim, my SE had a discussion with their team and it is possible to remark the DSCP values for individual flows based on the inbound interface it came on - and the remark is universal for all outbound interfaces, whether upstream to the core or to other customers on the same router, as it's done in the PFE and not on the outbound interface. Until the ER becomes a feature, we'll have to use this as we deploy more Juniper boxes where we've traditionally run Cisco. Cheers, Mark. signature.asc Description: This is a digitally signed message part. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] bgp as-path
On Nov 14, 2008, at 8:38 PM, SunnyDay wrote: but what if i have 4509:65001:4356:65444 will it remove both private or only 65001 and when it checks the next (4356) stops and does not remove 65444 remove-private will only remove leading (left-hand) private ASNs, so in your example, 65001 -and- 65444 will not be removed. --Daniel. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] bgp as-path
but what if i have 4509:65001:4356:65444 will it remove both private or only 65001 and when it checks the next (4356) stops and does not remove 65444 Hyunseog Ryu wrote: "remove private-as" will remove private ASNs from AS-Path, so only ASes with public AS range will be survive after this filtering. So it works for AS-PATHs with both public/private ASN combinations. -Original Message- From: SunnyDay [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2008 12:43 PM To: Hyunseog Ryu Cc: SunnyDay; juniper-Nsp Subject: Re: [j-nsp] bgp as-path yes i know but whta if the AS-PATH contains both ublic and private. what will happen then. i read that the OS will consider it a config error? Hyunseog Ryu wrote: >From bgp options, you can find 'remove-private-as' or something like that. Sent from my Windows Mobile(r) phone. -Original Message- From: SunnyDay <[EMAIL PROTECTED]> Sent: Friday, November 14, 2008 12:35 PM To: juniper-Nsp Subject: [j-nsp] bgp as-path hello i want to know what will the behavior be if AS-PATH contains both public and private ASN and is possible to remove all private ?? Thanks ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] bgp as-path
neighbor remove-private-as Removes private AS numbers in updates sent to external peers. Private AS numbers are only in the range 64,512-65,535. Regards, Masood -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of SunnyDay Sent: Friday, November 14, 2008 11:43 PM To: Hyunseog Ryu Cc: juniper-Nsp Subject: Re: [j-nsp] bgp as-path yes i know but whta if the AS-PATH contains both ublic and private. what will happen then. i read that the OS will consider it a config error? Hyunseog Ryu wrote: > >From bgp options, you can find 'remove-private-as' or something like that. > > > > Sent from my Windows MobileR phone. > > -Original Message- > From: SunnyDay <[EMAIL PROTECTED]> > Sent: Friday, November 14, 2008 12:35 PM > To: juniper-Nsp > Subject: [j-nsp] bgp as-path > > > hello > i want to know what will the behavior be if AS-PATH contains both public and private ASN > and is possible to remove all private ?? > Thanks > > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] bgp as-path
yes i know but whta if the AS-PATH contains both ublic and private. what will happen then. i read that the OS will consider it a config error? Hyunseog Ryu wrote: >From bgp options, you can find 'remove-private-as' or something like that. Sent from my Windows Mobile® phone. -Original Message- From: SunnyDay <[EMAIL PROTECTED]> Sent: Friday, November 14, 2008 12:35 PM To: juniper-Nsp Subject: [j-nsp] bgp as-path hello i want to know what will the behavior be if AS-PATH contains both public and private ASN and is possible to remove all private ?? Thanks ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] bgp as-path
hello i want to know what will the behavior be if AS-PATH contains both public and private ASN and is possible to remove all private ?? Thanks ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] junos policy
https://www.juniper.net/techpubs/software/junos/junos92/swconfig-policy/example-configuring-bgp-flap-damping.html
Please refer to the URL, there're actually a couple of examples out
there, a good reference on JUNOS would be CYMRU's. Not sure if it's
updated yet.
Here's a sample.
--raymondh
policy-statement damping-policy {
term 1 {
from {
route-filter 0.0.0.0/0 prefix-length-range /24-/32 {
damping high-damp;
accept;
}
route-filter 0.0.0.0/0 prefix-length-range /22-/23 {
damping medium-damp;
accept;
}
route-filter 0.0.0.0/0 orlonger {
damping normal-damp;
accept;
}
}
}
}
damping high-damp {
half-life 30;
reuse 820;
suppress 3000;
max-suppress 60;
}
damping medium-damp {
half-life 15;
reuse 750;
suppress 3000;
max-suppress 45;
}
damping normal-damp {
half-life 10;
reuse 1500;
suppress 3000;
max-suppress 30;
}
damping no-damp {
disable;
}
On Nov 14, 2008, at 8:28 PM, Andrew Jimmy wrote:
How do you guys do else in JUNOS policy.. like what if I want
116.203.0/16
orlonger damping high and rest normal. How you are going to use it.
Damping: high
Damping: normal
policy-statement damp {
term 1 {
from {
route-filter 116.203.0.0/16 orlonger damping high;
}
}
Else normal
}
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] junos policy
How do you guys do else in JUNOS policy.. like what if I want 116.203.0/16
orlonger damping high and rest normal. How you are going to use it.
Damping: high
Damping: normal
policy-statement damp {
term 1 {
from {
route-filter 116.203.0.0/16 orlonger damping high;
}
}
Else normal
}
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
