RE: OSPF neighbors not becoming adjacent over frame relay

From: Todd, Douglas M. (DTODD@PARTNERS.ORG)
Date: Mon Sep 10 2007 - 17:40:17 ART


Hi Andy:

Some hopefully good thoughts for you:

1) I am assuming that in your example that s0/0 is actually s0/0.125
multipoint?
2) You are changing the ospf network type on both routers and forcing them to
be
non-broadcast. Thus you must use the neighbor command on both a router.

Your options:
Make sure ospf multicast frames can traverse your frame-relay (using debug ip
packet or debug ip ospf adj, debug ip os event, or ping 224.0.0.5). This
could
involve you using a frame-relay map on Router A s0/0.125 vs the interface
dlci.

Change the network type of both interfaces to broadcast and force the router
to
broadcast the frames on a non-broadcast network. This would assume the above
(multicast frames can traverse your frame-relay)

Timers should not be an issue since both networks are non-broadcast by
default
H30/D120. You are forcing the neighbor relationship with the neighbor and not
changing your timers. Thus your timers are ok (including ospf interface type)
(which makes it work). S0/0 on Router B is a multipoint and s0/0.125 is a
multipoint on Router A, thus your timers should be as stated above.

Douglas

The information transmitted in this electronic communication is intended only
for the person or entity to whom it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or other
use of or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you received this
information in error, please contact the Compliance HelpLine at 800-856-1983
and properly dispose of this information.
x-mimeole: Produced By Microsoft Exchange V6.5
Received: from PHSXCON1.partners.org ([132.183.130.40]) by
  PHSXMB24.partners.org with Microsoft SMTPSVC(6.0.3790.1830); Mon, 10
  Sep 2007 16:19:22 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Received: from phsmgmx9.partners.org ([155.52.251.100]) by
  PHSXCON1.partners.org with Microsoft SMTPSVC(6.0.3790.1830); Mon, 10
  Sep 2007 16:19:21 -0400
Received: from lists.groupstudy.com ([207.44.210.9]) by
  phsmgmx9.partners.org with ESMTP; 10 Sep 2007 16:19:22 -0400
Received: (from sympa@localhost) by lists.groupstudy.com
  (8.12.11.20060308/8.11.6) id l8AKFaCn028749; Mon, 10 Sep 2007 16:15:36
  -0400
Received: from groupstudy.com (www.groupstudy.com [209.51.144.7]) by
  lists.groupstudy.com (8.12.11.20060308/8.11.6) with ESMTP id
  l8AKEHcA028737 for <ccielab@lists.groupstudy.com>; Mon, 10 Sep 2007
  16:14:17 -0400
Received: from groupstudy.com (groupstudy.com [127.0.0.1]) by
  groupstudy.com (8.12.11.20060308/8.12.11) with ESMTP id l8AKEUiL006486
  GroupStudy Mailer; Mon, 10 Sep 2007 16:14:30 -0400
Received: (from listserver@localhost) by groupstudy.com
  (8.12.11.20060308/8.12.11/Submit) id l8AKEUaV006484 for
  ccielabxhiddenx; Mon, 10 Sep 2007 16:14:30 -0400
Received: from voltage-out.foremostfarms.com
  (voltage-out.foremostfarms.com [64.73.41.25]) by groupstudy.com
  (8.12.11.20060308/8.12.11) with ESMTP id l8AKEO2f006447 GroupStudy
  Mailer; Mon, 10 Sep 2007 16:14:24 -0400
Received: from ff001m15.foremost.com (ff001m15.foremost.com
  [192.168.1.79]) by voltage-out.foremostfarms.com (8.13.1/8.13.1) with
  ESMTP id l8AKEB7G018135; Mon, 10 Sep 2007 15:14:11 -0500
Received: from FF001M10VS.foremost.com ([192.168.1.171]) by
  ff001m15.foremost.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 10
  Sep 2007 15:14:12 -0500
Content-class: urn:content-classes:message
Subject: RE: OSPF neighbors not becoming adjacent over frame relay
Date: Mon, 10 Sep 2007 16:14:11 -0400
Message-ID: <4BFE4C97AE5C1A42BEA84BBB3C98E85303D0851E@FF001M10VS.foremost.com>
In-Reply-To: <BAY136-F37AC57248B4C9816EA3B9AE4C00@phx.gbl>
Thread-Topic: OSPF neighbors not becoming adjacent over frame relay
Thread-Index: Acfz5syIJAGbnYB0TI2Eerl7rnGcEgAACp6w
List-Help: <mailto:sympa@groupstudy.com?subject=help>
List-Subscribe: <mailto:sympa@groupstudy.com?subject=subscribe%20ccielab>
List-Unsubscribe: <mailto:sympa@groupstudy.com?subject=unsubscribe%20ccielab>
From: "Andy Cole" <Andy.Cole@foremostfarms.com>
Sender: <nobody@groupstudy.com>
To: "Carlos Trujillo Jimenez" <nergal888@hotmail.com>
Cc: <ccielab@groupstudy.com>
Reply-To: "Andy Cole" <Andy.Cole@foremostfarms.com>

 sh ospf interface,
Check the timers, if they don't match, change one side to match the
other

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Carlos Trujillo Jimenez
Sent: Monday, September 10, 2007 3:06 PM
To: ccielab@groupstudy.com
Subject: OSPF neighbors not becoming adjacent over frame relay

I Have the followinf scenario in which Router A and RouterB are directly
connected each other over a NBMA frame relay cloud. Ospf is configured
in each router advertising its frame relay interface, Im trying to
establish adjacency between each other but, seems its not working with
the following
restrictions:

Restrictions:
Do not user neighbor command on any router.
Do not use interface level commands in router B.

Router A :
interface Serial0/0.125 multipoint
ip address 173.1.125.5 255.255.255.0
frame-relay interface-dlci 502

router ospf 1
log-adjacency-changes
network 173.1.125.5 0.0.0.0 area 0

Router B :
interface Serial0/0
ip address 255.255.255.0
encapsulation frame-relay
frame-relay map ip 173.1.125.5 205 broadcast

router ospf 1
log-adjacency-changes
network 173.1.125.2 0.0.0.0 area 0

In router A I configured the following, making it work, and both routers
become fully adjacent, but Im violating the restriction about "to not
use he neighbor command"

int ser 0/0
ip ospf network non-broadcast
ip ospf priority 255

routr ospf 1
neighbor 173.1.125.2

Any ideas about where should I go, or follow??
Remember it must work without the "neighbor" command in both routers.



This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:10 ART