From: Mick Vollmer (mvollmer@xxxxxxxx)
Date: Wed Apr 04 2001 - 14:16:26 GMT-3
I thought about this but what then is the use of having a routing protocol?
It seems odd to have to manually enter a route to every possible location
within the cloud. . . I'll give it a try.
Thanks,
Mick
----- Original Message -----
From: "Rob Webber" <rwebber@callisma.com>
To: "'Mick Vollmer'" <mvollmer@visi.net>; <ccielab@groupstudy.com>
Sent: Wednesday, April 04, 2001 1:12 PM
Subject: RE: IPX and RIP
> You probably don't have a Frame Relay map on R2 for R3 and vice versa. So
on
> R2 you would need:
>
> serial 0
> frame-relay map ipx 100.0003.0003.0003 105 broadcast
>
> where 100.0003.0003.0003 is the IPX address of the Frame-relay interface
on
> R3 and 105 is the DLCI on R2. Note - you can find the IPX address on R3 by
> entering "show ipx int." However you can also make it easy (as above) by
> entering the global command on R3:
>
> ipx routing 3.3.3
>
> Rob.
>
> P.S. If you place a map on R2 for R3, its also a good idea to place a map
> for R1 on R2 as well (and the same for R3). Depending on the IOS, you
might
> otherwise lose connectivity to R1 after a reboot.
>
> -----Original Message-----
> From: Mick Vollmer [mailto:mvollmer@visi.net]
> Sent: Wednesday, April 04, 2001 12:12 PM
> 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