[j-nsp] Strange latency when using traceroute.

[Stephen Fulton]

Hi all,

I've noticed that when traceroute passes through our J6350 (using 
8.3R15), that the returned latency is considerably higher from the 
router.  Pinging the router or devices past it are fine, but this is one 
of those things I know I'll be asked about, and I haven't been able to 
figure out.  Here's the redacted output from a sample traceroute:

[sfulton at optics ~]$ traceroute 192.168.254.2
traceroute to 192.168.254.2 (192.168.254.2), 64 hops max, 40 byte packets
  1  router1 (192.168.110.74)  0.337 ms  0.143 ms  0.494 ms
  2  j6350 (192.168.98.65)  25.119 ms  28.051 ms  29.982 ms
  3  router3 (192.168.254.2)  1.079 ms  0.743 ms  0.962 ms
[sfulton at optics ~]$

Now there are filters protecting the routing engine, but I've removed 
all others for the purpose of testing.  CPU load is practically zero, 
and the J6350 is running OSPF and BGP.

Any ideas?

-- Stephen.