[j-nsp] Using QoS to ensure BGP bandwidth

Hello, I've been investigating using QoS to ensure BGP traffic out of our router to the peer gets transmitted even when the line is at full saturation. I was going to use a firewall filter to assign all BGP to a queue with strict-high priority, however it appears that network-control traffic is as

[j-nsp] New_title: vpls over gre config sample

Pasting a working config for vpls over gre between pes. Ce-ce pings/ospf working. MTU on the t1 link adjusted to accommodate 1500 byte pings between ces. Topo is pasted inline and will wrap. Cannot attach to this list. This is part of a larger testscript so much of the topo is not being used. In th

Re: [j-nsp] BGP Origin Issue

Hi, My bad, described behaviour was true back in 2001. In nowadays both cisco and juniper set by default origin for aggregated routes to IGP. Jeff P.S. Sorry for all the mails, bloody outlook :) > -Original Message- > From: Phil Bedard [mailto:[EMAIL PROTECTED] > Sent: vrijdag 20 april

Re: [j-nsp] BGP Origin Issue

Hi, My bad, described behaviour was true back in 2001. In nowadays both cisco and juniper set by default origin for aggregated routes to IGP. Jeff P.S. Sorry for all the mails, bloody outlook :) > -Original Message- > From: Phil Bedard [mailto:[EMAIL PROTECTED] > Sent: vrijdag 20 april

Re: [j-nsp] BGP Origin Issue

Hi, My bad, described behaviour was true back in 2001. In nowadays both cisco and juniper set by default origin for aggregated routes to IGP. Jeff P.S. Sorry for all the mails, bloody outlook :) > -Original Message- > From: Phil Bedard [mailto:[EMAIL PROTECTED] > Sent: vrijdag 20 april

Re: [j-nsp] AS path access list (regexp)

Hi, It would look like: ABCD+ .{0,2} Regards, Jeff > -Original Message- > From: [EMAIL PROTECTED] [mailto:juniper-nsp- > [EMAIL PROTECTED] On Behalf Of Kanagaraj Krishna > Sent: vrijdag 20 april 2007 12:54 > To: juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] AS path access list (rege

Re: [j-nsp] Class of Service implementation over MLPPP link

FAHAD ALI KHAN wrote: > Dear All > > Thanks for you support i also want to start another thread which has ben > questioned alot of time but never answered. > > Carrying MPLS VPN [L2VPN (Kompella) and L2cct (Martini)] traffic over GRE > Tunnel. > > As it has been proposed in Juniper Documentati

Re: [j-nsp] Class of Service implementation over MLPPP link

Dear All Thanks for you support i also want to start another thread which has ben questioned alot of time but never answered. Carrying MPLS VPN [L2VPN (Kompella) and L2cct (Martini)] traffic over GRE Tunnel. As it has been proposed in Juniper Documentation that MPLS over GRE is supported, i

Re: [j-nsp] BGP Origin Issue

Yeah the Cisco is a little strange in those regards, the only time it will not use IGP for the origin code in an aggregate-address is if you are using as-set and one of the contributing routes is incomplete... I second the policy of resetting the origin to IGP to take that out of the possible

Re: [j-nsp] AS path access list (regexp)

For prepend stuff, what about something like: regexp ^1000(_[1-9]+)(\1)*(_[1-9]+)(\2)*$ Assuming 1000 is your peering AS, then the other (up to) two AS's could have the same number repeat itself. Just a thought. Scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED

Re: [j-nsp] AS path access list (regexp)

Hello Kanagaraj, ^.{1,3}$ will allow an AS_PATH which depth is between 1 and 3 AS it will not cater though for either the first, second or third AS doing AS_PATH prepending. Daniel Kanagaraj Krishna wrote: > Hi, > I have this AS path access list to one of my BGP peerings (inbound route

Re: [j-nsp] AS path access list (regexp)

Hello Kanagaraj, ^.{1,3}$ will allow an AS_PATH which depth is between 1 and 3 AS it will not cater though for either the first, second or third AS doing AS_PATH prepending. Daniel Kanagaraj Krishna wrote: > Hi, > I have this AS path access list to one of my BGP peerings (inbound route

Re: [j-nsp] BGP Origin Issue

Hi, Actually there's a situation where you could get hit by differences in "origin" setup. By default Cisco, when aggregates, marks origin as IGP while Juniper does incomplete. If you have got more than 1 BGP sessions with a same peer and they aggregate on the peering routers where 1 is Cisco and

Re: [j-nsp] AS path access list (regexp)

Hi, I have this AS path access list to one of my BGP peerings (inbound route map) which is based on Cisco to set different local pref to: - direct peering AS - direct peering AS + 1st AS hop - direct peering AS + 1st AS hop + 2nd AS hop Based on Cisco --- ip as-path ac

Re: [j-nsp] BGP Origin Issue

Hi, Actually there's a situation where you could get hit by differences in "origin" setup. By default Cisco, when aggregates, marks origin as IGP while Juniper does incomplete. If you have got more than 1 BGP sessions with a same peer and they aggregate on the peering routers where 1 is Cisco and

Re: [j-nsp] BGP Origin Issue

Hi, Actually there's a situation where you could get hit by differences in "origin" setup. By default Cisco, when aggregates, marks origin as IGP while Juniper does incomplete. If you have got more than 1 BGP sessions with a same peer and they aggregate on the peering routers where 1 is Cisco and

Re: [j-nsp] BGP Origin Issue

Hi, Actually there's a situation where you could get hit by differences in "origin" setup. By default Cisco, when aggregates, marks origin as IGP while Juniper does incomplete. If you have got more than 1 BGP sessions with a same peer and they aggregate on the peering routers where 1 is Cisco and

Re: [j-nsp] BGP Origin Issue

Hi, Actually there's a situation where you could get hit by differences in "origin" setup. By default Cisco, when aggregates, marks origin as IGP while Juniper does incomplete. If you have got more than 1 BGP sessions with a same peer and they aggregate on the peering routers where 1 is Cisco and

Re: [j-nsp] BGP Origin Issue

Hi, Actually there's a situation where you could get hit by differences in "origin" setup. By default Cisco, when aggregates, marks origin as IGP while Juniper does incomplete. If you have got more than 1 BGP sessions with a same peer and they aggregate on the peering routers where 1 is Cisco and

Re: [j-nsp] BGP Origin Issue

Hi, Actually there's a situation where you could get hit by differences in "origin" setup. By default Cisco, when aggregates, marks origin as IGP while Juniper does incomplete. If you have got more than 1 BGP sessions with a same peer and they aggregate on the peering routers where 1 is Cisco and

[j-nsp] Multiply Radius servers

Hi, Is it possible on M-series routers use different radius servers for different username regexps? For example users with logins like ppp.* authenticating via one server but users like rrr.* via another? -- R:Em ___ juniper-nsp mailing list juniper-ns

Re: [j-nsp] Class of Service implementation over MLPPP link

Friday, April 20, 2007, 8:48:17 AM, you wrote: FAK> One more question related to Multicalss MLPPP. Suppose if my scenario is FAK> something like following, FAK> PE1 = PE2 PE3 FAK> || FAK> || FAK>