Re: Exit-Graceful Restart Condition

Kishore Rao <kishore@IND.ALCATEL.COM> Wed, 25 May 2005 18:53 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 OAA08528 for <ospf-archive@LISTS.IETF.ORG>; Wed, 25 May 2005 14:53:11 -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 <2.0105B4C1@cherry.ease.lsoft.com>; Wed, 25 May 2005 14:53:10 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.3) with spool id 72516152 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 25 May 2005 14:53:09 -0400
Received: from 208.8.0.237 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Wed, 25 May 2005 14:53:09 -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/(postal1 2.1 [OUT])) with ESMTP id j4PIr8PG022836 for <OSPF@peach.ease.lsoft.com>; Wed, 25 May 2005 11:53:08 -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 j4PIr6aw011253 for <OSPF@peach.ease.lsoft.com>; Wed, 25 May 2005 11:53:06 -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 11:53:06 -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 LAA13556 for <OSPF@peach.ease.lsoft.com>; Wed, 25 May 2005 11:53:06 -0700 (PDT)
References: <000001c56135$9cb892b0$ca04120a@china.huawei.com> <42949392.3060002@cisco.com> <4294A37E.2000000@cisco.com> <03e201c56152$44214210$a328fb80@Kishorepc> <4294BBCC.5010607@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: <03fc01c5615b$2bcde840$a328fb80@Kishorepc>
Date: Wed, 25 May 2005 12:54:25 -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 11:54 AM
Subject: Re: Exit-Graceful Restart Condition


> Kishore Rao wrote:
>
> >----- Original Message ----- 
> >From: "Acee Lindem" <acee@cisco.com>
> >To: <OSPF@peach.ease.lsoft.com>
> >Sent: Wednesday, May 25, 2005 10:10 AM
> >Subject: Re: Exit-Graceful Restart Condition
> >
> >
> >
> >
> >>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.
> >>
> >>
> >
> >Acee,
> >
> >Will this work ?
> >In case there is another router RTB, scan the Hello from RTB for all
> >neighbors on the network and then make sure Hello from RTA has been
received
> >within a Hello interval + 2 (say) . If not, exit GR.
> >
> >
> It is not clear to me. Do you mean that RTB has the same neighbors as
> DUT and is on the same network link ?

Yes.


>
> Padma
>
> >This would be faster than using the reacquired Router and Network LSAs to
> >determine the neighbors, isnt it ?
> >
> >Kishore
> >
> >
> >
> >
> >>
> >>
> >>>Padma.
> >>>
> >>>
> >>>
> >>>>For other routers in the network RTA is still reachable and traffic
> >>>>Will be eventually dropped.
> >>>>
> >>>>Kindly correct me,
> >>>>
> >>>>Regds,
> >>>>Ashok/Sujay
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >
> >
> >