Re: Inconsistent view of routers over a LAN

Acee Lindem <acee@REDBACK.COM> Tue, 10 June 2003 17:15 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 NAA09656 for <ospf-archive@LISTS.IETF.ORG>; Tue, 10 Jun 2003 13:15:56 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <21.00A0A87D@cherry.ease.lsoft.com>; Tue, 10 Jun 2003 13:15:56 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 45185648 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 10 Jun 2003 13:15:55 -0400
Received: from 24.93.67.82 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 10 Jun 2003 13:15:55 -0400
Received: from redback.com (rdu162-240-050.nc.rr.com [24.162.240.50]) by ms-smtp-01.southeast.rr.com (8.12.5/8.12.2) with ESMTP id h5AHAOTp000722 for <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 10 Jun 2003 13:10:24 -0400 (EDT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <3EE5F2DD.9794A0F@alcatel.com> <3EE5FEB3.156FB9E3@alcatel.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3EE61252.5020304@redback.com>
Date: Tue, 10 Jun 2003 13:16:02 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: Inconsistent view of routers over a LAN
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Cheng-Yin Lee wrote:
> Hello,
> Just got some private responses, perhaps I should clarify.
> This is in context of an emulated LAN, and I am not looking for a fix in
> routing protocols.

Hi Cheng-Yin,

What I've recommended in the past for these situations is to force
the routing protocol to view the underlying network as a P2MP
(Point-to-Multi-Point) network. Many vendors support this. For
example, in our implementation you'd simply configure:

   router ospf 1
    area 0
     interface backbone
      network-type point-to-multipoint
               o
               o
          < the rest of the OSPF config>
               o

Good Luck,
Acee


>
> Thanks
> Cheng-Yin
>
> Cheng-Yin Lee wrote:
>
>>Hello,
>>What happens if for some reason Router A can't reach Router B, but
>>Router C can reach A & B (and vice-versa), when Router A,B,C are
>>connected over a broadcast network or LAN.
>>
>>E.g. in the case for (OSPF and IS-IS) where:
>>i) C is the DR
>>ii) B is the DR
>>
>>Thanks
>>Cheng-Yin
>
>


--
Acee