Re: [j-nsp] MX punting packets to RE - why?

2016-02-01 Thread Michael Hare
Ross- Change 'fpc0' to 'afeb0' in your failed command. I got goose eggs, but this lab chassis isn't doing multicast which may play a part. $user@mx104-lab-re0> request pfe execute target afeb0 command "show nhdb mcast resolve" SENT: Ukern command: show nhdb mcast resolve GOT: GOT: Nexthop Inf

Re: [j-nsp] MX punting packets to RE - why?

2016-02-01 Thread Saku Ytti
On 1 February 2016 at 22:37, Ross Halliday wrote: Hey, > If I am understanding what you guys are saying correctly, this would cause > everything to get punted to the CPU until a new hardware shortcut is created, > and in the meantime - since our entire channel lineup is in there - this > woul

Re: [j-nsp] MX punting packets to RE - why?

2016-02-01 Thread Ross Halliday
Hi Saku and Dragan, Thank you for the responses, and apologies for the ambiguity. The EXes are our video source switches. PIM RP is shared with MSDP to an anycast address. The MXes connect to the EXes at L3 via BGP - MX1/EX1 link is de-prioritized with a metric. Most of our receivers ride off o