[j-nsp] bgp soft clear and metric minimum-igp, bug?

Jeff Wheeler jeff at reflected.net
Wed Jan 21 01:33:40 EST 2004


On Tue, 2004-01-20 at 21:39, Richard A Steenbergen wrote:
> Of course this begs the question, exactly how long will it stay this way
> (forever?) and what happens if you make a permanent routing change which
> takes away the lowest cost route? Would you have to clear it in order for
> the updates to be processed, and if so would a soft clear out do the
> trick? Also, in the event of a sustained outage of the normal lower cost

This is what I was trying to indicate in my original post. A soft clear
won't do. A session flap is necessary to effect the change. While your
time limit notion would be useful, perhaps it would be less involved to
implement a command to simply "forget" all the minimum-igp values for a
particular route and re-evaluate its advertised MED for a session or
sessions, or all routes on a specified session. As another example, if
you were to increase the med advertised to a peer from, minimum-igp 50
to minimum-igp 500, that change would not take effect until the routes
were withdrawn from BGP and the local rpd "lost" their state, or until
the affected session flapped / was fully cleared.

> At any rate, if you don't want the minimum igp cost, leave off the 
> "minimum-" part. :)

Indeed. :-)

-- 
Jeff at Reflected Networks



More information about the juniper-nsp mailing list