Re: Exit-Graceful Restart Condition
Kishore Rao <kishore@IND.ALCATEL.COM> Wed, 25 May 2005 19:02 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 PAA09330 for <ospf-archive@LISTS.IETF.ORG>; Wed, 25 May 2005 15:02:33 -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 <0.0105B5A0@cherry.ease.lsoft.com>; Wed, 25 May 2005 15:02:33 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.3) with spool id 72516787 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 25 May 2005 15:02:28 -0400
Received: from 208.8.0.238 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Wed, 25 May 2005 15:02:28 -0400
Received: from mailhub2.ind.alcatel.com (mailhub2.ind.alcatel.com [198.206.181.70]) by ind.alcatel.com (8.12.9/8.12.9/(postal 2.0 [OUT])) with ESMTP id j4PJ2SMd024594 for <OSPF@peach.ease.lsoft.com>; Wed, 25 May 2005 12:02:28 -0700 (PDT)
X-InterScan: Passed
Received: from mailhub2.ind.alcatel.com (localhost [127.0.0.1]) by mailhub2.ind.alcatel.com (8.12.10/8.12.10/(mailhub2 4.1.4 [HUB2])) with ESMTP id j4PJ2Raw012182 for <OSPF@peach.ease.lsoft.com>; Wed, 25 May 2005 12:02:27 -0700 (PDT)
Received: from omni.ind.alcatel.com ([198.206.181.20]) by mailhub2.ind.alcatel.com (MailFrontier 4.0.2.4693) with ESMTP; Wed, 25 May 2005 12:02:27 -0700
Received: from Kishorepc ([128.251.40.163]) by omni.ind.alcatel.com (8.9.3+Sun/8.9.1 (omni 3.0 [engr-SPOOL])) with SMTP id MAA13946 for <OSPF@peach.ease.lsoft.com>; Wed, 25 May 2005 12:02:27 -0700 (PDT)
References: <000001c56135$9cb892b0$ca04120a@china.huawei.com> <42949392.3060002@cisco.com> <4294A37E.2000000@cisco.com> <4dbb3ecf05052511211a3138e6@mail.gmail.com> <4294C810.4030608@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mlf-Threat: nothreat
X-Mlf-Threat-Detailed: nothreat;none;list_addrbk_domain
Message-ID: <040f01c5615c$7a1cf210$a328fb80@Kishorepc>
Date: Wed, 25 May 2005 13:03:45 -0600
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Kishore Rao <kishore@IND.ALCATEL.COM>
Subject: Re: Exit-Graceful Restart Condition
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
----- Original Message ----- From: "Padma Pillay-Esnault" <ppe@cisco.com> To: <OSPF@peach.ease.lsoft.com> Sent: Wednesday, May 25, 2005 12:46 PM Subject: Re: Exit-Graceful Restart Condition > ashok holla wrote: > > >Hi, > >When myself and Sujay raised this issue, we thought about the > >possibility which Pama and Acee suggested. > >However, this will not work in all cases. > > > >Consider: > > > >TOPO------------------------ DUT---------------------------RTA > > Area0 Area1 > >In this case, DUT will not get his pre-restart router of Area 1 as > >there no other router in the area to give it to him. > >Therefore, this solution fails. > >In this case, suppose DUT had run the spf, he would have seen that the > >type-3 summary lsa he had advertised into area 0, is no longer > >consistent with the topology and then could have exited GR. However, > >this consistensy check can be done only after grace period terminates > >as RTA MAY come up within that time. > >So, for this case, there seems to be no solution. > > > > > You have not taken into account one major premise in thr rfc - > For graceful restart to success you MUST have a helper to enable you to > recover. > In the case above you have > 1. A double failure > 2. No helper in the area > > With 2 - There can be no GR restart in the first place. Optimizing the > detection is not possible if you do not even > have the list of your previous neighbors. If no neighbors are detected after the interface Hello interval, wouldn't exiting GR be advisable instead of waiting for grace timer to expire ? Kishore > > >However, it does seem to be worthwhile to start deadTimers for all > >nbrs listed in the pre-restart router lsa when we get it for the first > >time. (even though we have not received hello pkts from them). When > >any inactivity timer fires on the restarting router, he can quit GR. > >This can be done to impro convergence incase, topology is unstable. > > > > > > > I would put that as an option rather than a "must". > > Padma > > >Is our understanding correct? > > > >regards, > >Ashok/Sujay > > > > > >On 5/25/05, Acee Lindem <acee@cisco.com> wrote: > > > > > >>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 > >>>> > >>>> > >>>> > >>>> > >>>> > > > > > > > >
- Waiting State Question John Smith
- Re: Waiting State Question Anthony Baire
- Re: Waiting State Question Kishore Rao
- Re: Waiting State Question Mukul Goyal
- Re: Waiting State Question Erblichs
- Re: Waiting State Question Kishore Rao
- Re: Waiting State Question Mukul Goyal
- Re: Waiting State Question Kishore Rao
- Re: Waiting State Question Mukul Goyal
- Re: Waiting State Question Kishore Rao
- Re: Waiting State Question Erblichs
- Re: Waiting State Question Kishore Rao
- Re: Waiting State Question John Smith
- Re: Waiting State Question Erblichs
- Re: Waiting State Question Erblichs
- Re: Waiting State Question Mukul Goyal
- Re: Waiting State Question Kishore Rao
- Re: Waiting State Question Erblichs
- Exit-Graceful Restart Condition sujay
- Re: Exit-Graceful Restart Condition Padma Pillay-Esnault
- Re: Exit-Graceful Restart Condition Acee Lindem
- Re: Exit-Graceful Restart Condition Kishore Rao
- Re: Exit-Graceful Restart Condition Padma Pillay-Esnault
- Re: Exit-Graceful Restart Condition ashok holla
- Re: Exit-Graceful Restart Condition Padma Pillay-Esnault
- Re: Exit-Graceful Restart Condition Kishore Rao
- Re: Exit-Graceful Restart Condition Kishore Rao
- Re: Exit-Graceful Restart Condition Padma Pillay-Esnault
- Re: Exit-Graceful Restart Condition sujay
- Re: Exit-Graceful Restart Condition Acee Lindem
- Re: Exit-Graceful Restart Condition Padma Pillay-Esnault