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

[Jeff Wheeler]

Is anyone using routing-options autonomous-system N loops L on any of
their routers? I am experiencing a problem that I believe is a bug with
this configuration. When using '2' or '1' as the value for L, config
commits cause rpd to choke and restart. The following is syslogged..:

Dec 11 14:47:49  bordercore3.chcgil02 mgd[4630]: UI_COMMIT: User 'root'
performed commit: no comment
Dec 11 14:47:50  bordercore3.chcgil02 rpd[4675]: UI_CONFIGURATION_ERROR:
Process: rpd, path: <none>, statement: <none>, Invalid loop count
configured
Dec 11 14:47:50  bordercore3.chcgil02 rpd[4675]: RPD_EXIT: Exit
rpd[4675] version 6.1R2.2 built by builder on 2003-11-21 23:53:00 UTC,
caller 809f3cb
Dec 11 14:47:50  bordercore3.chcgil02 init: routing (PID 4675) exited
with status=0 Normal Exit
Dec 11 14:47:50  bordercore3.chcgil02 init: routing (PID 4928) started

Obviously the rpd restart causes my routing protocols to restart, which
flaps eBGP peers and causes havoc on the IGP as well. The only cure I've
found was to simply remove the loops statement (which was a challenge in
and of itself, thanks, CLI!). This complicates my configuration, as I
really do want to receive (some) routes over eBGP sessions containing my
own as number one or more times! :-(

-- 
Jeff at Reflected Networks