On Tue, May 15, 2018 at 02:32:07AM +0300, Saku Ytti wrote:
> Have you found cef exact-route to be correct?
>
> Last time I used this (ASR9000), it was giving wrong results to me. I
> think there is entirely separate piece of code for LAG result in
> software code and the CSCO EZChip microcode, and
On Fri, Dec 16, 2016 at 02:45:14PM -0600, Aaron wrote:
> Ah, thanks Jesper... you know how much those 7280's cost ? (just ballpark)
No idea, sorry.
/Jesper
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo
On Fri, Dec 16, 2016 at 02:21:22PM -0600, Aaron wrote:
> I was thinking about the ptx1000 as a supercore fast mpls swapping p-box. I
> understand it can have (24) 100 gig !
>
> I've seen the PTX1000 referred to as a supercore router , and I understand it
> has MPLS LSR functions (someone told m
On Mon, Aug 01, 2016 at 01:03:59PM +0300, Saku Ytti wrote:
> On 1 August 2016 at 11:02, Adam Vitkovsky wrote:
>
> > So essentially you're suggesting holding up BGP updates to peers until the
> > router has it's FIB fully populated right?
>
> Yes.
>
> > I think that might be easier said than don
> On 01 Jun 2016, at 21:29, Vincent Bernat wrote:
>
> The other benefit would be the ability for rpd to make use of more CPU
> registers and to be faster. On average, one could expect a 20% speedup
> when recompiling for x86-64. I have absolutely no idea if such number
> would apply to rpd.
The
On Tue, Mar 29, 2016 at 03:46:07PM +0300, Saku Ytti wrote:
> On 29 March 2016 at 15:05, chip wrote:
> > Juniper has a "This Week" book freely available that discussess, in detail,
> > the path of a packet through an MX. It's quite an informative read.
> >
> > http://www.juniper.net/us/en/training
> On 05 Mar 2016, at 16:41, Saku Ytti wrote:
>
> On 5 March 2016 at 15:22, Adam Vitkovsky wrote:
>>> (b) Are there any noticeable behavioral differences between SPRING and
>>> LDP implementations?
>>>
>> Yes instead of label swap routers do label pop
>
> This is not really a behavioural chang
On Mon, Nov 02, 2015 at 06:30:00PM +, Adam Vitkovsky wrote:
> -Original Message-
> > From: Jesper Skriver [mailto:jes...@skriver.dk]
> > Sent: Monday, November 02, 2015 5:14 PM
> >
> >
> > Right, on those types of platforms it can be done - assuming the
On Tue, Nov 03, 2015 at 01:22:49AM +0200, Saku Ytti wrote:
> On 2 November 2015 at 19:14, Jesper Skriver wrote:
> > Right, on those types of platforms it can be done - assuming there
> > are spare bits in the meta data that goes with the packet, enough
> > free instruction sp
On Mon, Nov 02, 2015 at 06:47:06PM +0200, Saku Ytti wrote:
> On 2 November 2015 at 18:09, Jesper Skriver wrote:
> > I am not sayint that it doesn't make sense - I am saying that it
> > doesn't appear practical given the architecture of the average
> > router. What
On Mon, Nov 02, 2015 at 03:04:22PM +, Adam Vitkovsky wrote:
> > Saku,
> >
> > The point is that the incoming ethertype is only used to determine how to
> > interprete the header (IPv4, IPv6, MPLS etc) and to select what L3 table to
> > lookup in. After that it is gone, and never used again.
> >
On Sun, Nov 01, 2015 at 05:06:22PM +0200, Saku Ytti wrote:
> On 1 November 2015 at 12:08, Jesper Skriver wrote:
>
> > To do what you suggest, one either has to replicate the MPLS
> > table, so that we can handle the same label values for each of the
> > suggested MPLS-
Saku,
On Fri, Oct 30, 2015 at 10:47:48PM +0200, Saku Ytti wrote:
> On 30 October 2015 at 12:35, Jesper Skriver wrote:
>
> > That would not be practical to implement for a router, implementations
> > typically have the L2 header cached and the L3 forwarding
> > constructs
On Fri, Oct 30, 2015 at 02:44:44AM +0200, Saku Ytti wrote:
> On 30 October 2015 at 00:54, Cydon Satyr wrote:
>
> > Adam I believe that is correct. If I remember this, if it's something other
> > than 0x4/0x6 Trio chip looks at bits after first 12 bytes; if it's
> > 0x0800/0x86dd it still load bal
On 09 May 2015, at 10:44, Saku Ytti wrote:
> On (2015-05-09 09:40 +0300), Jesper Skriver wrote:
>
>
>>>> On (2015-05-08 20:16 +0200), Mark Tinka wrote:
>>>>
>>>> IOS XE uses multiple cores in the data plane, but now that I think about
>>&
> On 08 May 2015, at 23:34, Saku Ytti wrote:
>
>> On (2015-05-08 20:16 +0200), Mark Tinka wrote:
>>
>> IOS XE uses multiple cores in the data plane, but now that I think about
>> it, I haven't delved into what their strategy for the RP is. I should ask.
>
> iosd uses several kernel threads, s
> > 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
/Jesper
On Mon, Sep 12, 2011 at 11:19:54AM +0300, medrees wrote:
> Dear Experts
>
>
>
> I'm confusing why all vendors chooses OSPF backbone area to be
> area 0
It is the standard.
http://tools.ietf.org/html/rfc2328#page-27
> and I'm asking if there is method to change this number to any ot
27; and 10.1.1.2/27 configured on B towards 'Juniper'
/Jesper
>
> Scott
>
> -Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jesper Skriver
> Sent: Thursday, July 17, 2008 7:24 AM
> To: Farhan Jaffer
> Cc: Juniper Puck;
like thing? or any other problem.
>
> Thanks very much in advance.
>
> -FJ
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
/Jesper
--
Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456
One
; ___________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
/Jesper
--
Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456
One Unix to rule them all, One Resolver to find them,
One IP to
gt; > send to ISP #2, #3, #10 and #20 so that those ISPs use your routes to
> > get back to you directly, but they won't readvertise your routes to
> > their upstreams and peers.
> > ___
> > juniper-nsp mailing list juniper-n
22 matches
Mail list logo
