The platforms I have used it on it has been correct, but that doesn’t include 
ASR9k.

Scary to think what you have said could happen, but I guess I shouldn’t be 
surprised.

Sent from my iPhone

> On 14 May 2018, at 7:32 pm, Saku Ytti <s...@ytti.fi> 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 different people code
> IOS-XR than ezchip, so I think there is failure mode where one code is
> updated, and another is not, I hope I'm wrong.
> 
> But if I'm right, then the only way to do this, is actually ask the
> microcode 'hey i have this packet, do a lookup for it', or like in
> CAT7600/ELAM, get lookup results for real traffic.
> 
>> On 15 May 2018 at 02:27, Nikolas Geyer <n...@neko.id.au> wrote:
>> Unless it’s changed in newer releases there is no equivalent which is 
>> annoying.
>> 
>> I believe you can drop to the FPC vty and extract the information card by 
>> card similar to the link you shared, but it’s not exactly a workable 
>> solution, nor “officially supported” by Juniper.
>> 
>> The lack of this command is literally my biggest frustration with Juniper.
>> 
>> Sent from my iPhone
>> 
>>> On 11 May 2018, at 4:40 am, James Bensley <jwbens...@gmail.com> wrote:
>>> 
>>> Hi All,
>>> 
>>> Does anyone know of a command like the Cisco CEF "exact-route" command
>>> on Juniper?
>>> 
>>> I've seen this older thread: https://lists.gt.net/nsp/juniper/50645
>>> 
>>> Which links to a post on using JSIM but for DPC cards, but I'm
>>> interested in MPC cards:
>>> http://junosandme.net/article-junos-load-balancing-part-3-troubleshooting-109382234.html
>>> 
>>> Does anyone have any details on using JSIM on MPC cards on MX
>>> platforms? Or is there "another way" ?
>>> 
>>> I'm going to open a JTAC case as well as asking here however, in the
>>> past they have rejected requests to explain PFE commands to me or
>>> provide documentation for them. I have managed it a few times but only
>>> after a couple of weeks of non-stop screaming. So I'm not holding my
>>> breath for that option.
>>> 
>>> Kind regards,
>>> James.
>>> _______________________________________________
>>> 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
> 
> 
> 
> -- 
>  ++ytti
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to