Re: Clarification in changing the router id dynamically!!

"Naidu, Venkata" <Venkata.Naidu@MARCONI.COM> Mon, 07 July 2003 14:51 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 KAA28273 for <ospf-archive@LISTS.IETF.ORG>; Mon, 7 Jul 2003 10:51:00 -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 <1.00A544A5@cherry.ease.lsoft.com>; Mon, 7 Jul 2003 10:50:59 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 47678669 for OSPF@PEACH.EASE.LSOFT.COM; Mon, 7 Jul 2003 10:50:58 -0400
Received: from 169.144.68.6 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Mon, 7 Jul 2003 10:50:58 -0400
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA25053 for <OSPF@PEACH.EASE.LSOFT.COM>; Mon, 7 Jul 2003 10:50:56 -0400 (EDT)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA15395 for <OSPF@PEACH.EASE.LSOFT.COM>; Mon, 7 Jul 2003 10:50:57 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19) id <NJ804KBD>; Mon, 7 Jul 2003 10:50:57 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <39469E08BD83D411A3D900204840EC55FB6F45@vie-msgusr-01.dc.fore.com>
Date: Mon, 07 Jul 2003 10:50:56 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: "Naidu, Venkata" <Venkata.Naidu@MARCONI.COM>
Subject: Re: Clarification in changing the router id dynamically!!
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

-> This case isn't explicitly handled by RFC 2328 and there is
-> some variance
-> between implementations. At a minimum, the DR must recognize
-> the change
-> in router ID and originate a new network LSA. I found that
-> one popular
-> implementation required the router with the router ID change
-> to bring its
-> adjacencies down (by sending a hello w/o any neighbor IDs)
-> in order to interoperate.

  RFC2328 recommends this approach. Page 47 reads:
  . . .
                                                          If a
        router's OSPF Router ID is changed, the router's OSPF software
        should be restarted before the new Router ID takes effect.
  . . .

  Restarting OSPF software is nothing but bringing up adjacencies
  afresh.

Venkata.