Re: Exit-Graceful Restart Condition

Acee Lindem <acee@CISCO.COM> Wed, 25 May 2005 16:11 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 MAA24515 for <ospf-archive@LISTS.IETF.ORG>; Wed, 25 May 2005 12:11:22 -0400 (EDT)
Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <11.0105B0D6@cherry.ease.lsoft.com>; Wed, 25 May 2005 12:11:22 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.3) with spool id 72503258 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 25 May 2005 12:11:14 -0400
Received: from 64.102.122.149 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Wed, 25 May 2005 12:11:11 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 25 May 2005 12:11:11 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j4PGB252023143 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 25 May 2005 12:11:09 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 25 May 2005 12:10:41 -0400
Received: from [10.82.224.4] ([10.82.224.4]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 25 May 2005 12:10:41 -0400
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <000001c56135$9cb892b0$ca04120a@china.huawei.com> <42949392.3060002@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 May 2005 16:10:41.0143 (UTC) FILETIME=[4C0BA870:01C56144]
Message-ID: <4294A37E.2000000@cisco.com>
Date: Wed, 25 May 2005 12:10:38 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@CISCO.COM>
Subject: Re: Exit-Graceful Restart Condition
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <42949392.3060002@cisco.com>
Precedence: list
Content-Transfer-Encoding: 7bit

Padma Pillay-Esnault wrote:

> sujay wrote:
>
>> Hi All,
>>
>> Considering RFC3623, Graceful Restart for OSPF V2 I have a problem;
>>
>> Ex:
>>
>>  (network)---- DUT ---- RTA
>>
>> (All in the same area)
>>
>> Assume DUT undergoes a Graceful-Restart, it sends out grace LSA's to
>> RTA and other routers in the 'network'
>>
>> At the instant RTA recvs the Grace-LSA it also goes down.
>>
>> Is there a way in the RFC 3623 specified as to how DUT could Detect 
>> this topology change and Exit GR *before* grace period expiry??
>>  
>>
> I do not think the RFC covers this case. You are in a double failure 
> situation.
>
> I can think of a simple solution. When DUT reacquires its router-lsa. 
> It can determine its previous
> neighbors. It can then decide that if within DeadRouterInterval that 
> neighbor did not  respond
> to hellos to abort GR. This would be equivalent to the normal 
> situation when a router goes down and its
> neigbors takes DeadInterval to bring down their adjacency

I agree completely with Padma. One point, if RTA comes back up and 
originates a new router LSA
then the DUT will detect the inconsistency (as specified in RFC 3623) 
with it's pre-restart LSA and
terminate graceful restart. 


>
> Padma.
>
>> For other routers in the network RTA is still reachable and traffic 
>> Will be eventually dropped.
>>
>> Kindly correct me,
>>
>> Regds,
>> Ashok/Sujay
>>
>>  
>>
>