From: Mick Vollmer (mvollmer@xxxxxxxx)
Date: Wed Apr 04 2001 - 15:42:16 GMT-3
Thanks Michael,
This is from a LAB scenario and one of the restrictions is to not use inverse
arp or individual sub-interfaces. I think I figured it out though. If you
look really close you'll read the words "shut down" in the config for S0 on
R2. Sometimes it's hard to see the forrest for the trees.
I really appreciate the help from everyone.
Mick
----- Original Message -----
From: "Michael Herald" <mherald@dyb.com>
To: "'Mick Vollmer'" <mvollmer@visi.net>
Sent: Wednesday, April 04, 2001 2:02 PM
Subject: RE: IPX and RIP
> You are missing the (IPX) route maps from spoke to spoke. I read your post
> to the group about putting all of them in. In the real world you do not
> have to. More than likely inverse arp works properly for you and you are
> allowed to use it. Your frame provider isnt trying to trick you into doing
> (or not doing) things.
>
> Put the spoke to spoke frame maps in and you will be running again.
>
> I would go with IPX EIGRP in the real world (provided you have all Cisco
> equipment) as it will save your frame relay bandwidth.
>
> -----Original Message-----
> From: Mick Vollmer [SMTP:mvollmer@visi.net]
> Sent: Wednesday, April 04, 2001 11:46 AM
> To: mherald@dyb.com
> Subject: Re: IPX and RIP
>
> Again, the idea is to no be using a fully meshed frame, otherwise I would
> stay with RIP.
>
>
> Here they are:
>
> R1 S0/0.1
> IPX Net 2
> DLCI 102 | | DLCI 103
> | |
> | |
> | |
> DLCI 201 | | DLCI 301
> R2 R3
> S0 S0
>
> On R1
> interface Serial0/0.1 multipoint
> ip address 172.16.4.1 255.255.255.0
> no ip directed-broadcast
> ip ospf network point-to-multipoint
> ipx network 2
> no ipx split-horizon eigrp 8
> frame-relay map ip 172.16.4.2 102 broadcast
> frame-relay map ip 172.16.4.3 103 broadcast
> frame-relay map ipx 2.0002.0002.0002 102 broadcast
> frame-relay map ipx 2.0003.0003.0003 103 broadcast
>
> On R2:
> interface Serial0
> ip address 172.16.4.2 255.255.255.0
> encapsulation frame-relay
> ip ospf network point-to-multipoint
> bandwidth 72
> shutdown
> frame-relay map ip 172.16.4.1 201 broadcast
> frame-relay map ipx 2.0001.0001.0001 201 broadcast
> no frame-relay inverse-arp
>
> On R3:
> interface Serial0
> ip address 172.16.4.3 255.255.255.0
> no ip directed-broadcast
> encapsulation frame-relay
> ip ospf network point-to-multipoint
> no ip mroute-cache
> ipx network 2
> frame-relay map ip 172.16.4.1 301 broadcast
> frame-relay map ipx 2.0001.0001.0001 301 broadcast
> no frame-relay inverse-arp
>
>
>
> ----- Original Message -----
> From: "Michael Herald" <mherald@dyb.com>
> To: "'Mick Vollmer'" <mvollmer@visi.net>
> Sent: Wednesday, April 04, 2001 12:24 PM
> Subject: RE: IPX and RIP
>
>
> > Your frame relay map ipx statements. I can send you examples if you need
> them. They are very dependant on your local addressing.
> >
> > Mike
> >
> > -----Original Message-----
> > From: Mick Vollmer [SMTP:mvollmer@visi.net]
> > Sent: Wednesday, April 04, 2001 11:12 AM
> > To: rwebber@callisma.com; ccielab@groupstudy.com
> > Subject: Re: IPX and RIP
> >
> > OK - I followed your advice and I'm seeing IPX routes on R2 from R3 and
> R3
> > from R2. I can ping from R1 to R2 or R3, R2 and R3 to R1 but not from R2
> to
> > R3 or R3 to R2. The routes are there, the pings get to R3 but I'm
> getting
> > the following error on R3:
> >
> > 03:30:14: IPX: local:300.0003.0003.0003->2.0002.0002.0002 ln=100 tc=00
> pt=02
> > ds=
> > 0002 ss=0002, encap failed
> > 03:30:14: IPXECHO: Can't send echo
> >
> >
> > R1 S0/0.1
> > | |
> > | |
> > | |
> > | |
> > R2 R3
> > S0 S0
> >
> > Any ideas?
> >
> > Mick
> >
> >
> > ----- Original Message -----
> > From: "Rob Webber" <rwebber@callisma.com>
> > To: "'Mick Vollmer'" <mvollmer@visi.net>; <ccielab@groupstudy.com>
> > Sent: Wednesday, April 04, 2001 10:18 AM
> > Subject: RE: IPX and RIP
> >
> >
> > > Short of static routes (really ugly), I would recommend enabling EIGRP
> > just
> > > on the frame links (and disabling RIP). Mutual redistribution with
> EIGRP
> > and
> > > RIP is automatic, so you don't have to mess around with any of that
> stuff.
> > >
> > > You could also do EIGRP on the LAN side, but if you have any nodes
> (Novell
> > > servers, etc.) they usually need RIP, so its just as easy to use RIP
> > there.
> > >
> > > If I was given a lab scenario that simply instructed "enable IPX on all
> > > interfaces..." and some of them happened to be FR, I would immediately
> > jump
> > > to EIGRP on the FR. Tunnels might be another (messier) option...
> > >
> > > Rob.
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > > Mick Vollmer
> > > Sent: Wednesday, April 04, 2001 9:38 AM
> > > To: ccielab@groupstudy.com
> > > Subject: IPX and RIP
> > >
> > >
> > > I have a question regarding IPX RIP. I understand the split horizon
> issue
> > > and have read that you can't disable split horizon on RIP. I'm working
> on
> > a
> > > hub and spoke frame config that is not fully meshed and I had to
> disable
> > > inverse ARP. What alternatives do I have for addressing the split
> horizon
> > > issue? Do I have to replace the IGP with EIGRP or just do that over
> the
> > > frame links? Any ideas would be appreciated.
> > >
> > > Mick
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:40 GMT-3