Ok, problem solved...And there is a very important lesson to learn here that
I will get to in a minute...
The eigrp neighbor problem was due to the fact that on the hub, I defined
the neighbors in the eigrp process, where on the spokes I did not. I was
able to pinpoint this as the problem by doing debug eigrp packet and
debug eigrp neighbor. The error messages indicated that the hub was
receiving multicast hellos, where the spokes were receiving unicast hellos.
Both ends were discarding the hello's because they were in a format not
compatible with what they were configured to use. Once I wiped all of the
neighbor definitions altogether, the neighborships formed instantly. Man, I
could kick myself! I did, however go back in my books and look for
something that says you can't do this, and didn't find anything, so I don't
feel quite so stupid.
Ok, now for the very important lesson to learn from all this: This list is
an awesome pool of knowledge to draw from, but is of absolutely no use to
you if you feed it inaccurate information, just as I did with the configs
that I provided from memory (what was my name again, I forget). I failed
to include the neighbor configuration (along with providing incorrect map
statements where interface-dlci statements were actually used), and thus
eliminated any chance of any of the experts on the list helping me figure
this out in less than the 2 hours I wasted on it. So.If you are going
to post information...ESPECIALLY router configsmake sure you give people
a chance by providing them with the WHOLE story, unlike me.
Big thanks to Chuck, cebuano, and the others who attempted to help me.
Kelly Cobean
-Original Message-
From: Kelly Cobean [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 19, 2002 10:43 PM
To: cisco
Subject: FW: EIGRP Neighbor issue
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
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=47112t=47112
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
