On Fri, Apr 29, 2011 at 11:05 AM, Stuart Henderson <[email protected]> wrote: > Yes. You sometimes get nasty cloned host routes if ospfd bounces, > but this mostly works pretty well. My usual setup is like this: > > $ cat /etc/hostname.lo1 > inet 192.0.2.5/32 > > $ grep lo1 /etc/ospfd.conf > interface lo1 { passive } > > $ grep 192.0.2.5 /etc/bgpd.conf > router-id 192.0.2.5 > local-address 192.0.2.5
Thanks, my issue was not having local-address defined, came right up after that. Any more details you can share about the routing issue if ospfd bounces, and if it bounced on its own or was done by someone manually? Does the issue happen only on the box where ospfd bounced?
