|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Alex Zinin (azinin
NEXSI.COM)Date: Tue Sep 04 2001 - 18:38:34 CDT
alex,
You should not flush and reoriginate the Summary LSA
every time Dijkstra is calculated. A summary LSA should
be flushed only if the prefix it describes became
unreachable, and should be reoriginated (as as result
of Dijkstra) if the cost has changed.
If the destination is not reachable, it is removed
from the routing table. Other details are implementation-
specific.
-- Alex ZininFriday, August 10, 2001, 4:38:00 AM, alex lerin wrote:
> Hi > According to RFC if any router LSA has changed > the routing table is to be calculated right from the > scratch. > If this is to happen what abt the summary LSAs > that were generated previously.Should all those > summary LSAs be flushed or only those LSAs with > unreachable destinations are to be flushed.If that is > the case how to find which LSAs has a destination > unreachable.
> It would be better if someone can tell me what all has > to be done when a router LSA has changed
> Thanks > alex
> __________________________________________________ > Do You Yahoo!? > Make international calls for as low as $.04/minute with Yahoo! Messenger > http://phonecard.yahoo.com/
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]