Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Don Goodspeed (dgoodspeEXCITE.COM)
Date: Sat Nov 24 2001 - 00:31:55 CST
Unfortunately, option 2 (swap ages) would result in
a new sequence # for a MaxAge LSA that has probably
already been flooded and flushed (usually) from
most of the routers already. The other routers
would have to receive, process, install, and flood
an LSA at MaxAge that they had already flushed.
Option 1 can work if the sequence # is incremented
and all of the fields are updated with the new info.
The other routers will use the new infomation, resulting
in an implicit delete of the old LSA and its info.
Of course, it is late and I could be missing something.
My 2 cents,
On Fri, 23 Nov 2001 07:09:11 -0800, Mailing List wrote:
> I had this little problem with Appendix E. Appendix E
> states that if the network mask for the new
> destination longer then that of the old LSAs
> destination then the old LSA should be originated for
> the new destination and the new LSA for the old
> destination with the host bits set. Does this also
> apply if my old database copy is MaxAge and is waiting
> to be deleted from the database. In this case if I
> swap the destinations (while not swapping the ages)
> then the LSA for the new destination gets deleted
> after receiving acknowledgements.
> The two solutions I can think of is I can go ahead
> and ignore the database copy (ie. not apply appendix
> E, and overwrite the new LSA over the old one) and
> originate the new LSA for the new destination. Or I
> can swap the ages of the two LSAs too. I wanted to
> know if I am on the right track. If anyone has a
> better idea, please share it with me.
> Do You Yahoo!?
> Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
Send a friend your Buddy Card and stay in contact always with Excite Messenger