Re: Clarification in changing the router id dynamically!!

"Jeyanath Minto J - CTD, Chennai." <jeyananthj@CTD.HCLTECH.COM> Fri, 04 July 2003 06:04 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09153 for <ospf-archive@LISTS.IETF.ORG>; Fri, 4 Jul 2003 02:04:02 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <20.00A4BA58@cherry.ease.lsoft.com>; Fri, 4 Jul 2003 2:03:51 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 47540305 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 4 Jul 2003 02:03:49 -0400
Received: from 202.54.64.2 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Fri, 4 Jul 2003 02:03:48 -0400
Received: by GANESH with Internet Mail Service (5.5.2653.19) id <3BLWFG69>; Fri, 4 Jul 2003 11:33:43 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <AB9CCBF59B42604EB08449C1B0BFC81A5C9EC4@HARITHA.ctd.hcltech.com>
Date: Fri, 04 Jul 2003 11:34:03 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: "Jeyanath Minto J - CTD, Chennai." <jeyananthj@CTD.HCLTECH.COM>
Subject: Re: Clarification in changing the router id dynamically!!
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

hi Kamatchi,
        old neighbour down event trigger the new lsa origination. ofcourse,
its very late origination.
u can detect it earlier and originate as soon as possible .This is
implementation dependent.

Cheers
Minto Mascarenhas


-----Original Message-----
From: kamatchi soundaram [mailto:kamatchi@TDD.SJ.NEC.COM]
Sent: Friday, July 04, 2003 1:14 AM
To: OSPF@PEACH.EASE.LSOFT.COM
Subject: Clarification in changing the router id dynamically!!


Hi,

  If the router id of the router R1 is changed on the fly (dynamically),
what factor triggers the adjacent router R2 connected to R1 via point to
point link, to generate the new Router LSA???

 From the RFC i could infer that R1 will flush all his self originated lsas
when it's router lsa has been changed.
  But i couldn't find, how the R2 triggered to generate the new router lsa
with the changed router id as is neighbor id in its router lsa??

Thanks in advance,
Kamatchi.