From: Chuck Larrieu (chuck@xxxxxxxxxxxxx)
Date: Mon Apr 09 2001 - 12:41:44 GMT-3
Two things.
Given the configs below, there is no ipx routing on the tunnels. Therefore
the tunnel source and destination are irrelevant to this discussion. Also,
you, Jim, are correct that with IPX RIP there is no way to disable split
horizon. This is per the Novell spec, and Cisco's conformance to it.
Chuck
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Jim
Graves
Sent: Monday, April 09, 2001 7:51 AM
To: fwells12; ccielab@groupstudy.com
Subject: Re: More IPX tunnels over sub-interfaces.
I thought that was only when using point-to-point subinterfaces. I could
be deeply confused, but I think split-horizon is still enabled on
multipoint subinterfaces.
At 07:19 AM 4/9/2001 -0700, fwells12 wrote:
>Isn't Split-Horizon disabled by default for sub-interfaces, why would this
>be the problem?
>
>
>----- Original Message -----
>From: Jim Graves <jtg@lucent.com>
>To: fwells12 <fwells12@hotmail.com>; <ccielab@groupstudy.com>
>Sent: Monday, April 09, 2001 5:33 AM
>Subject: Re: More IPX tunnels over sub-interfaces.
>
>
> > If you're running IPX RIP, then split-horizon is your problem. The
> > split-horizon problem occurs in both EIGRP and RIP over hub-and-spoke
> > parital mesh; but you can only turn off split-horizon using IPX
> > EIGRP. There's no knob to turn it off in IPX RIP.
> >
> > At 11:19 PM 4/8/2001 -0700, fwells12 wrote:
> > >Can anyone explain why I am able to see all IPX networks from the hub
>(r5) but
> > >I am unable to see IPX network 34 on r3 from r2 and likewise, IPX
network
>12
> > >on r2 from r3? The spoke routers are r2 and r3, the hub router is r5.
I
>can
> > >ipx ping the spokes from each other. I am not running IPX EIGRP over
the
> > >cloud in case your thinking split-horizon.
> > >
> > >Here are the relevant parts of the configs. TIA.
> > >
> > >interface Tunnel25
> > > no ip address
> > > tunnel source Serial0
> > > tunnel destination 133.6.10.22
> > >!
> > >interface Tunnel35
> > > no ip address
> > > tunnel source Serial0
> > > tunnel destination 133.6.10.23
> > >!
> > >interface Ethernet0
> > > mac-address 0005.0005.0032
> > > ip address 133.6.100.5 255.255.255.0
> > > ipx network 32
> > >!
> > >interface Serial0
> > > no ip address
> > > no ip directed-broadcast
> > > encapsulation frame-relay
> > > no ip mroute-cache
> > > no frame-relay inverse-arp
> > > frame-relay lmi-type ansi
> > >!
> > >interface Serial0.1 multipoint
> > > ip address 133.6.10.25 255.255.255.240
> > > ipx network 35
> > > frame-relay map ip 133.6.10.22 102 broadcast
> > > frame-relay map ip 133.6.10.23 103 broadcast
> > >
> > >r2
> > >interface Tunnel25
> > > no ip address
> > > tunnel source Serial0
> > > tunnel destination 133.6.10.25
> > >!
> > >interface Serial0
> > > ip address 133.6.10.22 255.255.255.240
> > > ipx network 35
> > >!
> > >interface Serial1
> > > ipx network 12
> > >
> > >r3
> > >interface Tunnel35
> > > no ip address
> > > tunnel source Serial0
> > > tunnel destination 133.6.10.25
> > >!
> > >interface Serial0
> > > ip address 133.6.10.23 255.255.255.240
> > > ipx network 35
> > >!
> > >interface Ethernet0
> > > mac-address 0003.0003.0034
> > > ipx network 34
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:43 GMT-3