Make sure that the OSPF router ID is not an IP associated with one
of the circuits that might bounce. It's always a good idea to create
a loopback that'll be selected as the router id or with 12.x explicitly
specify an "ip ospf route-id a.b.c.d".
George
> From cisco-nsp-request@puck.nether.net Tue May 1 00:53:16 2001
> Resent-Date: Tue, 1 May 2001 00:53:10 -0400
> Received-Date: Tue, 1 May 2001 00:51:09 -0400
> Date: Tue, 1 May 2001 00:40:23 -0400 (EDT)
> From: Tatsuya Kawasaki <tatsuya@kivex.com>
> X-Sender: tatsuya@kds1
> To: cisco-nsp@puck.nether.net
> Subject: [nsp] ospf and boucing circuit.
> Resent-From: cisco-nsp@puck.nether.net
> X-Mailing-List: <cisco-nsp@puck.nether.net> archive/latest/6226
> X-Loop: cisco-nsp@puck.nether.net
> Precedence: list
> Resent-Sender: cisco-nsp-request@puck.nether.net
>
> Hi you all,
>
> Does any of you have problems with OSPF protocol and bouncing circuit?
> It appeared that when DS3 bounces, sometimes we lose OSPF update..
> I had not had a chance to take a close look that what part of OSPF is
> failing. Version of cisco we are currently running is 12.0x
> So in order to solve that problem, we need to restart OSFP process.
> Does anyone have simlar problem?
> Interesting thing is that it start having problem almost 1 hour after
> circuit bounces.
>
> Tatsuya
>
>
> /_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> Tatsuya Kawasaki
> Allegiance Telecom
> Unlock the Power of the Internet
> http://www.kivex.com
> Phone 301.215.6777 Fax 301.215.5991
> Affiliation given for identification not representation
> /_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:36 EDT