From: Schulz, Dave (DSchulz@dpsciences.com)
Date: Tue May 30 2006 - 23:32:41 ART
Actually, I believe that the explicit frame-relay mapping is needed.
Local policy will not help here, since you telling the router to look
for a route on an already connected interface, which it cannot find.
Dave Schulz, CCDP, CCNP, CCSP
Email: dschulz@dpsciences.com <mailto:dschulz@dpsciences.com%20>
________________________________
From: Jian Gu [mailto:guxiaojian@gmail.com]
Sent: Tuesday, May 30, 2006 5:39 PM
To: Schulz, Dave
Cc: Cisco certification
Subject: Re: Frame - eigrp and split horizon
Since the destination you are trying to ping is directly connected, it
does not matter whether you have ip split horirzon configured or not,
you will have encap failure. In order to ping spoke to spoke, you either
need to configure explicit frame-relay mapping or configure local policy
based routing.
On 5/30/06, Schulz, Dave <DSchulz@dpsciences.com> wrote:
Question on split horizon....
I set up a hub router on a frame with the following configuration.....
interface Serial0/0
ip address 192.168.1.1 255.255.255.0
encapsulation frame-relay
no ip split-horizon eigrp 100
frame-relay map ip 192.168.1.1 102
frame-relay map ip 192.168.1.2 102 broadcast
frame-relay map ip 192.168.1.3 103 broadcast
no frame-relay inverse-arp
!
router eigrp 100
network 192.168.1.0
no auto-summary
There are two remote sites, with the following configuration.....
interface Serial0/0
ip address 192.168.1.2 255.255.255.0
encapsulation frame-relay
no frame-relay inverse-arp IP 203
no frame-relay inverse-arp IP 204
and......
interface Serial0
ip address 192.168.1.3 255.255.255.0
encapsulation frame-relay
no frame-relay inverse-arp IP 302
no frame-relay inverse-arp IP 304
!
Both set up with eigrp 100. They both form the neighbor relationship
with the hub router. However, there is still not connectivity from
spoke to spoke (even though split horizon is disabled). I know that
everything works if I statically map everything, just trying to
understand a little further on the eigrp between multiple routers. I
was thinking that this may be a recursive issue, but I see that we have
the route recursing to the hub router, but not continuing from the hub
to the second spoke.....
R2#sh ip rou 192.168.1.3
Routing entry for 192.168.1.0/24
Known via "connected", distance 0, metric 0 (connected, via interface)
Redistributing via eigrp 100
Routing Descriptor Blocks:
* directly connected, via Serial0/0
Route metric is 0, traffic share count is 1
I may be missing something. Sorry for hitting on some of the more basic
things.
Dave Schulz,
Email: dschulz@dpsciences.com <mailto: dschulz@dpsciences.com >
This archive was generated by hypermail 2.1.4 : Thu Jun 01 2006 - 06:33:22 ART