GroupStudy.com GroupStudy.com - A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
RE: EIGRP Neighbor issue [7:47030] posted 06/20/2002
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]


On p2p frame-relay interfaces, you have to set 
an interface DLCI.  That should resolve your neighbor
problem.

HTH

______________________________

Thomas Crowe
Senior Systems Engineer / Senior Architect
EMC Proven Master Architect
CTS Professional Services - Atlanta
______________________________ 

-----Original Message-----
From: nobody@xxxxxxxxxxxxxx [mailto:nobody@xxxxxxxxxxxxxx]
Sent: Thursday, June 20, 2002 12:09 PM
To: cisco@xxxxxxxxxxxxxx
Subject: Re: EIGRP Neighbor issue [7:47030]




My understanding of P2P Frame-Relay is that you do NOT need map statements.
Unless I'm following an olders IOS behavior as outlined in Caslow, please
correct me if I'm wrong.

----- Original Message -----
From: "Kelly Cobean"
To:
Sent: Wednesday, June 19, 2002 11:27 PM
Subject: FW: EIGRP Neighbor issue [7:47030]


> Hey all,
>      I'm probably missing some fairly simple concept here, but for some
> reason, I cannot get two routers to establish a neighborship over a
> frame-relay link without manually specifying each as the other's neighbor
in
> the eigrp configuration on each router.  Both routers have frame-relay
map
> statements that include the "broadcast" keyword.  The spoke router has
> another router connected to it via Ethernet.  It dynamically discovers
this
> other router and establishes adjacency without manual configuration.
>
> Here's the basics of the config:
>
> Hub#
> int s0.300 multipoint
>  ip address 192.168.1.1 255.255.255.0
>  frame-relay map ip 192.168.1.3 301 broadcast
>  frame-relay map ip 192.168.1.2 302 broadcast
>
> router eigrp 100
>  no auto-summary
>  network 192.168.1.0
>
> __________
>
> Spoke#
> int s0.103 point-to-point
>  ip address 192.168.1.3 255.255.255.0
>  frame-relay map ip 192.168.1.1 103 broadcast
>
> router eigrp 100
>  no auto-summary
>  network 192.168.1.0
> __________________________________________________
>
> Unless I add the line "neighbor 192.168.1.3" and "neighbor 192.168.1.1"
to
> each router respectively, the adjacency fails.  My impression of the
> "broadcast" keyword in the frame-relay map statement was that it would
cause
> the interface to pass broad/multicasts.  So what am I missing?  There is
> nothing in my BSCN book about this (unless I'm blind) and I've had a hard
> time finding anything on Cisco's site about it.  Any input is greatly
> appreciated.  Thanks.
>
> Kelly

[GroupStudy.com removed an attachment of type text/x-vcard which had a name
of Thomas Crowe.vcf]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=47094&t=47030
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to abuse@xxxxxxxxxxxxxx