From: Marian Jancar <marian.jancar@infonet.cz>
To: linux-kernel@vger.kernel.org
Subject: [zebra 10019] Re: Can't find originating ASBR route
Date: Thu, 16 Aug 2001 15:29:21 +0200 [thread overview]
Message-ID: <3B7BCAB1.9040700@infonet.cz> (raw)
In-Reply-To: <01be01c0f5c4$ccbb5c80$10e27ac3@marshal>
Serge Y. Zhukov wrote:
> Hello
>
> After 2-3 hours jobs ospfd (but not always, some day sometimes works) stops
> correctly to work and produces in log file:
>
> OSPF: Route[External]: Calculate AS-external-LSA to 195.122.226.216/29
> OSPF: Route[External]: Can't find originating ASBR route
>
> And so for all paths. I can give what information when there will occur such
> moment. Four Cisco-router in same network is normal work.
After upgrading Linux kernel from 2.2.16 to 2.2.19 my ospfd has similar
behaviour (a little while after started). The route is droped and usualy after
one or more hellos reinstated. I tried latest cvs, doesnt help. I would like
to correct this, but I dont have enough knowlege about ospf to do it myself,
any help or hints are wellcome.
Marian Jancar
parent reply other threads:[~2001-08-16 13:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <01be01c0f5c4$ccbb5c80$10e27ac3@marshal>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B7BCAB1.9040700@infonet.cz \
--to=marian.jancar@infonet.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox