Re: IPX Troubleshooting

From: Larry Roberts (lroberts22@xxxxxxxxxx)
Date: Sat Feb 24 2001 - 23:17:15 GMT-3


   
Hello all,

Henry, I would check into configuring IPXWAN on my serial links, IPXWAN
speeds up the protocol negotiation process on serial links. From interface
configuration mode on both serial interfaces enter the following command:
ipx ipxwan
Here's a link to CCO for more info:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/cs/csprtn2
/csipx.htm#xtocid2835247

Hope this helps,
Larry R.

----- Original Message -----
From: "Henry Dziewa" <henryd31@home.com>
To: <smorris@mentortech.com>; <ccielab@groupstudy.com>
Sent: Saturday, February 24, 2001 6:35 PM
Subject: RE: IPX Troubleshooting

> Thanks Scott, but the MTU (1500) and for that matter everything else
> is set the same way on both of the routers. This is really killing
> me here. Makes no sense whatsoever, tried swapping IOS as well and didn't
> accomplish anything new.
>
>
> -----Original Message-----
> From: Scott Morris [mailto:smorris@mentortech.com]
> Sent: Saturday, February 24, 2001 8:29 PM
> To: 'Henry Dziewa'; ccielab@groupstudy.com
> Subject: RE: IPX Troubleshooting
>
>
> Try an extended IPX ping and choose the option "sweep sizes".
>
> Without understanding any of the specifics of your configuration, off the
> top of my head, one important thing to note would be MTU sizes...
Remember
> that IPX can NOT be fragmented. This means if you have an IPX packet on
one
> side (LAN?) of your network that's too big, then your router tries to put
it
> out the other side (WAN?) with a smaller MTU. If a packet is too big it
> won't work.
>
> Other things like RIP updates, EIGRP, SAP, etc. will work fine, because
> they're set as a small packet specifically for this reason.
>
> Anyway, something worth looking into since everything else seems to work
> just fine. Check your MTU's, and use the extended ping to sweep sizes and
> see what works and what doesn't.
>
> Hope this helps!
>
> Scott
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Henry Dziewa
> Sent: Saturday, February 24, 2001 8:01 PM
> To: ccielab@groupstudy.com
> Subject: IPX Troubleshooting
>
>
> Hello group,
>
> Here is a problem I've been faced with. I have very simple
> network for a small client. The config is like this, r1 connects
> to r2 over dedicated T1. 6 DS0's of this T1 are split at the CSU/DSU
> and go to a "PBX", so I'm left with 18 DS0's for data.
> There is IP and IPX involved. There are Novell servers on each of these
> two sites. Routing protocol is EIGRP for IP, EIGRP IPX on the WAN, and
> obviously IPX RIP on the LAN. The problem is that I loose IPX packets
> going thru the WAN link. I tested all over the place, I was placing loops
> everywhere possible on either side. I worked with Telco, they don't see
> any errors on the line. The strangest thing is that with IP there is no
> problem at all. Only when using extened IPX pings, even between the
> Serial interfaces, I keep on loosing packets. The problem to the
> end stations is that the Novell mapped drives are very slow, the documents
> being opened are hanging the systems, and more of such nightmares :(
>
> I even tried testing with different routers and still no go. It would seem
> that I have a problem with the Telco. However, like I said, there is no
> problem
> with IP traffic at all !!! I don't get any errors on the interfaces, the
> only errors
> that come up sometimes are CRC's - yes I verified/played with the timing
as
> well - when I do extended IPX pings but not when I do IP extended pings.
> With loopbacks, everything works great until I go out to the Telco,
> once the line is crossed to the telco, I get the errors - but again only
> with IPX.
>
> Any ideas to this problem would be appreciated..
>



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:00 GMT-3