[j-nsp] autonomous-system N loops L / local-as N loops L

[Phil Rosenthal]

I agree.

There have been quite a few times that I've made changes to a peer 
(like putting it in it's own rib-group, or changing the import or 
export polices), and it had to flap the peer, whereas there were other 
times that similar changes were made, and it did not result in similar 
flapping.


On Dec 11, 2003, at 9:17 PM, Richard A Steenbergen wrote:

> On Thu, Dec 11, 2003 at 07:36:51PM -0500, Jeff Wheeler wrote:
>> Further complicating my trouble-shooting process was that rpd would 
>> not
>> restart on *every* configuration commit. On some occassions I could 
>> make
>> large changes without trouble, and in other instances, the simple act 
>> of
>> issuing "commit" after making no changes at all, or simple changes 
>> such
>> as adding routing-options static routes, would cause an rpd restart.
>
>> From the "wouldn't it be nice" department:
>
> Sometimes it is not easy to predict when committing a complicated set 
> of
> changes will result in the automatic reset of a BGP session, or the
> automatic soft clearing of a BGP session, or even the automatic 
> restart of
> rpd (renames, inserts, group changes, any of a multitude of knobs). It
> would be nice if there was a way to get a little warning as to how bad
> your flapping is going to be, perhaps with a command to test the 
> proposed
> configuration similar to commit check?
>
> Just a thought. :)
>
> -- 
> Richard A Steenbergen <ras at e-gerbil.net>       
> http://www.e-gerbil.net/ras
> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 
> 2CBC)
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
--Phil Rosenthal
ISPrime, Inc.