From: Manny Gonzalez (gonzalu@xxxxxxx)
Date: Tue Apr 02 2002 - 13:36:05 GMT-3
Dan, one wrinkle which may stump others as it stumped me...
MAKE SURE you have some other interface setup with IPX on the side
sending the updates... If you do as I did:
r1e0------>e0r2
and only configure IPX on that link you will NEVER get an update :-)) I
spend two days on and off trying to figure out why... hahaha... as soon
as I turned up a loopback It started to speak across the link BAM!
lo0R1e0----->e0R2
DAN DORTON wrote:
>
> If you have to automatically discover encapsulation type & network
> numbers on a link do this.
>
> Create subinterfaces on the link & put different bogus IPX numbers on
> each of them & specify a different encapsulation on each of them.
>
> Do a debug ipx packet detail & do a no shut on the interface.
>
> You will see a bad packet response coming from the subinterface with
> the proper encapsulation on it & it will come from the correct network
> number!
>
> Dan
>
> >>> "Frank Jimenez" <franjime@cisco.com> 04/01/02 08:26PM >>>
> Guy,
> Not just specific to the lab, but I find that in 'the real world',
> many customers still have problems with the whole concept of IPX
> encapsulation types as they apply to routing. Be sure to have those
> down.
>
> Frank Jimenez, CCIE #5738
> franjime@cisco.com
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> Lupi, Guy
> Sent: Monday, April 01, 2002 12:10 PM
> To: 'ccielab@groupstudy.com'
> Subject: IPX stuff
>
> Does anyone have a list of IPX gotcha's that they wouldn't mind
> sharing?
> I am ok with all the basic protocols and stuff, but I don't really
> have
> a list of "watch out for this". Thanks.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:51 GMT-3