[j-nsp] bfd = busted failure detection :)
Ross Vandegrift
ross at kallisti.us
Fri Dec 11 14:50:51 EST 2009
On Wed, Dec 09, 2009 at 05:21:21PM -0600, Richard A Steenbergen wrote:
> I've personally never had any luck reproducing it in the lab, so I
> understand Juniper's frustration. It seems to require a complexity of
> routes, ports, and/or protocols which we simply don't have the time or
> money to reproduce in the lab, but I can reproduce it in the field (with
> undesired customer impact of course) nearly every time I reboot a
> router. Maybe we just need to help provide them with an example
> configuration that they can try to reproduce themselves.
Hmmm, I may have just reproduced something like this in the lab. I
had two static routes for 10.57.55.0/24 and realized I hadn't applied
a per-packet load balancing policy to the forwarding table export. So
I wrote a policy and applied it to the forwarding-table export. This
has been stuck in the KRT queue for over four hours now.
This is different than the indirect next-hop change, but I wonder if
its related. Note that interesting error "EPERM -- Jtree walk in
progress".
Ross
{master:0}
rvandegrift at lab-4200> show route 10.57.55.0 extensive
inet.0: 8 destinations, 8 routes (7 active, 0 holddown, 1 hidden)
10.57.55.0/24 (1 entry, 1 announced)
TSI:
KRT queued (deferred) change
10.57.55.0/24 -> {172.16.23.2}=>{172.16.23.2, 172.16.23.3}
in-kernel 10.57.55.0/24 -> {172.16.23.2}
*Static Preference: 5
Next hop type: Router
Next-hop reference count: 2
Next hop: 172.16.23.2 via me0.0, selected
Next hop: 172.16.23.3 via me0.0
State: <Active Int Ext>
Age: 8:49
Task: RT
Announcement bits (1): 0-KRT
AS path: I
{master:0}
rvandegrift at lab-4200> show krt queue
Routing table add queue: 0 queued
Interface add/delete/change queue: 0 queued
Indirect next hop add/change: 0 queued
MPLS add queue: 0 queued
Indirect next hop delete: 0 queued
High-priority deletion queue: 0 queued
High-priority change queue: 0 queued
High-priority add queue: 0 queued
Normal-priority indirect next hop queue: 0 queued
Normal-priority deletion queue: 0 queued
Normal-priority composite next hop deletion queue: 0 queued
Normal-priority change queue: 1 queued
CHANGE FROM gf 1 inst id 0 10.57.55.0/24 nexthop
172.16.23.2, me0.0
(15)
error 'EPERM -- Jtree walk in progress'
TO gf 1 inst id 0 10.57.55.0/24 nexthops
172.16.23.2, me0.0
172.16.23.3, me0.0
(15)
error 'EPERM -- Jtree walk in progress'
Normal-priority add queue: 0 queued
Routing table delete queue: 0 queued
--
Ross Vandegrift
ross at kallisti.us
"If the fight gets hot, the songs get hotter. If the going gets tough,
the songs get tougher."
--Woody Guthrie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20091211/82e7afa2/attachment.bin>
More information about the juniper-nsp
mailing list