IETF Logo Mail Archive

[OSPF] OSPF GR query

"Khan Amir-G20247" <amirkhan@motorola.com> Fri, 10 November 2006 09:52 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiT45-0002Ng-Vo; Fri, 10 Nov 2006 04:52:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiT44-0002Nb-Rz for ospf@ietf.org; Fri, 10 Nov 2006 04:52:48 -0500
Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GiT41-00050G-B3 for ospf@ietf.org; Fri, 10 Nov 2006 04:52:46 -0500
X-VirusChecked: Checked
X-Env-Sender: amirkhan@motorola.com
X-Msg-Ref: server-10.tower-128.messagelabs.com!1163152355!7394858!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.7]
Received: (qmail 27284 invoked from network); 10 Nov 2006 09:52:35 -0000
Received: from motgate7.mot.com (HELO motgate7.mot.com) (129.188.136.7) by server-10.tower-128.messagelabs.com with SMTP; 10 Nov 2006 09:52:35 -0000
Received: from az33exr02.mot.com ([10.64.251.232]) by motgate7.mot.com (8.12.11/Motorola) with ESMTP id kAA9qXng001664 for <ospf@ietf.org>; Fri, 10 Nov 2006 02:52:35 -0700 (MST)
Received: from ZMY16EXM66.ds.mot.com (zmy16exm66.ap.mot.com [10.179.4.26]) by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id kAA9qVxJ016242 for <ospf@ietf.org>; Fri, 10 Nov 2006 03:52:32 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: [OSPF] OSPF GR query
Date: Fri, 10 Nov 2006 17:52:17 +0800
Message-ID: <988EE2C769AC284ABAE9328BFC10703F01383B23@ZMY16EXM66.ds.mot.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: [OSPF] OSPF GR query
Thread-Index: Acbofzo03VIFl44LRamn1tmNckH5FgcK/YXw
From: Khan Amir-G20247 <amirkhan@motorola.com>
To: ospf@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: a1f9797ba297220533cb8c3f4bc709a8
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0523372143=="
Errors-To: ospf-bounces@ietf.org

Hi 

I have query related to OSPF Graceful Restart. 

 

 Consider this scenario: 

 

- Three Routers R1, R2 and R3 connected via Broadcast networks. 

 

 

 

- Where R1 is a DR on both the segments, where as R2 and R3 are in
DR-other
- Now R1 wants to perform GR, R2 and R3 agrees to be its Helpers. 
- Now after restart R1 will try to form adjacency with both R2 and R3. 
- Lets say R1 and R2  had become FULL, while R1 and R3 had reached
Exstart state. Now at this time(when R1 and R3 are in transition state)
the adjacency between R1 and  R2  goes down for some reson.  
 
 Considering above scenario, my doubts are: 

-  As the adjacency between R1 and R2 has gone down(which is a Topology
change) and R1 is still in GR mode, can R1 quit GR ? In general can a
NBR which was FULL and then later gone down can be treated as one of the
conditions for quiting GR ? 
 

 

Regards 
Aamir 

 


_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf

v2.23.0 | Report a Bug | By Email