Re: Highly Available OSPF Router.

Dave Katz <dkatz@JUNIPER.NET> Mon, 16 February 2004 07:19 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 CAA00285 for <ospf-archive@LISTS.IETF.ORG>; Mon, 16 Feb 2004 02:19:29 -0500 (EST)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <22.00CE1454@cherry.ease.lsoft.com>; Mon, 16 Feb 2004 2:19:27 -0500
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 2380357 for OSPF@PEACH.EASE.LSOFT.COM; Mon, 16 Feb 2004 02:19:26 -0500
Received: from 207.17.137.57 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Mon, 16 Feb 2004 02:19:26 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id i1G7JPl19726 for <OSPF@PEACH.EASE.LSOFT.COM>; Sun, 15 Feb 2004 23:19:25 -0800 (PST) (envelope-from dkatz@juniper.net)
Received: from juniper.net (nimbus-sc.juniper.net [172.16.12.13]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i1G7JKo12489 for <OSPF@PEACH.EASE.LSOFT.COM>; Sun, 15 Feb 2004 23:19:20 -0800 (PST) (envelope-from dkatz@juniper.net)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v553)
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
Message-ID: <700342AF-6050-11D8-BA5D-000A95A55D88@juniper.net>
Date: Sun, 15 Feb 2004 23:19:20 -0800
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Dave Katz <dkatz@JUNIPER.NET>
Subject: Re: Highly Available OSPF Router.
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <8D260779A766FB4A9C1739A476F84FA42ABEA0@daebe009.americas.nokia.com>
Precedence: list
Content-Transfer-Encoding: 7bit

I suspect a number of folks are working on things like this.

However, the way you describe it says that it in fact is not subject to
standardization, since it does what it does without the neighbors
realizing (nothing outside the "black box.")  Therefore it is only an
implementation trick, not something to be standardized.

--Dave

On Sunday, Feb 15, 2004, at 23:03 US/Pacific, Mukesh.Gupta@NOKIA.COM
wrote:

> Has anyone implemented an OSPF HA where two or more OSPF routers
> appear as one OSPF router to the OSPF neighbors. One of the routers
> (the Master) talks to the external world (OSPF neighbors) and the
> others (the Backups) keep all the dynamic OSPF state (neighbors,
> database etc) in sync with the Master. When the Master dies, one of
> the backup router takes over immediately without the neighbors
> realizing any change in the network ?
>
> If anyone has implemented any such thing, I would like to hear about
> how they do it. I would also like to know if the WG would be interested
> in standardizing such a mechanism ? At least I think that it will be
> a useful thing !!
>
> Regards
> Mukesh
>