Re: Extended Hitless OSPF Restart

"Manral, Vishwas" <VishwasM@NETPLANE.COM> Thu, 27 June 2002 04:34 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 AAA22568 for <ospf-archive@LISTS.IETF.ORG>; Thu, 27 Jun 2002 00:34:08 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <1.0066B7B1@cherry.ease.lsoft.com>; Thu, 27 Jun 2002 0:34:41 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 8176 for OSPF@DISCUSS.MICROSOFT.COM; Thu, 27 Jun 2002 00:34:41 -0400
Received: from 198.62.10.2 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Thu, 27 Jun 2002 00:34:41 -0400
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19) id <KG6F0T3Y>; Thu, 27 Jun 2002 00:30:07 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328291F82@india_exch.hyderabad.mindspeed.com>
Date: Thu, 27 Jun 2002 00:37:06 -0400
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: "Manral, Vishwas" <VishwasM@NETPLANE.COM>
Subject: Re: Extended Hitless OSPF Restart
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list

Acee,

I agree to your point, however I guess the draft
http://www.ietf.org/internet-drafts/draft-nguyen-ospf-oob-resync-00.txt
though not a working group item does allow Out of Band resynch, something
like the functionality you talk about below.

Thanks,
Vishwas

-----Original Message-----
From: Acee Lindem [mailto:acee@REDBACK.COM]
Sent: Thursday, June 27, 2002 3:40 AM
To: OSPF@DISCUSS.MICROSOFT.COM
Subject: Re: Extended Hitless OSPF Restart


Daniel Gryniewicz wrote:
>
> Isn't the whole point of a grace period that you want to exceed a router
dead
> interval?  If you are not going to exceed it, you can just do an ISIS
restart,
> which does not need a grace period at all.

The main differenence is that without graceful restart, OSPF offers no
mechanism
for learning the link state database without transitioning out of full state
and
re-originating router/neighbors LSAs, etc.


>
> Daniel
>
> On Wed, 26 Jun 2002 14:14:27 -0700
> Acee Lindem <acee@REDBACK.COM> wrote:
>
> > Daniel Gryniewicz wrote:
> > >
> > > Hi.
> > >
> > > Could someone please explain to me why this is necessary?  My reading
of
> > > draft-ietf-ospf-hitless-restart-02 indicates that an implementation
should
> > > *not* exit helper status because a router dead interval expired.
Please
> > > enlighten me.
> >
> > This not what I've implemented. A router acting as a helper will exit
> > helper mode when:
> >
> >     1. The inactivity timer expires.
> >     2. The interface goes down (which will also cause an LSA change).
> However,>        I've made it a configurable option whether or not a given
> router acting>        as a helper exits graceful restart when there is a
> change to an LSA which>        will be flooded to the restarting router.
> >     3. Certain sequence mismatch conditions (but not the obvious ones
that
> occur>        naturally during graceful restart).
> >
> > I'd be interested in what others have implemented.
> >
> > Thanks,
> > Acee
> >
> >
> > >
> > > Daniel
> > >
> > > On Tue, 25 Jun 2002 19:51:32 -0700
> > > Acee Lindem <acee@REDBACK.COM> wrote:
> > >
> > > > FYI - Ultimately, this would be an informational RFC or better yet
> > > > folded into the base "OSPF Hitless Restart" specification (although
> > > > this has not been discussed as of yet).
> > > >
> > > > Thanks,
> > > > Acee