From: Earl Aboytes (earl@xxxxxxxxxxxx)
Date: Mon Jun 05 2000 - 19:29:13 GMT-3
I tried this in the lab and it worked like a charm!!!!!!!!!!!!!!!!!!!!!!!!
Check this out. Here are my four interfaces hanging off the Ethernet
interface Ethernet0.1
ipx network 11
!
interface Ethernet0.2
ipx network 12 encapsulation SAP
!
interface Ethernet0.3
ipx network 13 encapsulation ARPA
!
interface Ethernet0.4
ipx network 14 encapsulation SNAP
Here is my debug! Debug ipx sap events, debug ipx packet, debug ipx sap
activity.
IPXSAP: positing update to 13.ffff.ffff.ffff via Ethernet0.3 (broadcast)
(full)
IPXSAP: positing update to 11.ffff.ffff.ffff via Ethernet0.1 (broadcast)
(full)
IPX: Et0.3:12345.0050.0f01.1c60->12345.ffff.ffff.ffff ln= 96 tc=00, rcvd
IPX: Et0.3:12345.0050.0f01.1c60->12345.ffff.ffff.ffff ln= 96 tc=00, bad pkt
IPX: Et0.3:12345.0050.0f01.1c60->12345.ffff.ffff.ffff ln= 40 tc=00, rcvd
IPX: Et0.3:12345.0050.0f01.1c60->12345.ffff.ffff.ffff ln= 40 tc=00, bad pkt
IPXSAP: positing update to 14.ffff.ffff.ffff via Ethernet0.4 (broadcast)
(full)
IPXSAP: positing update to 12.ffff.ffff.ffff via Ethernet0.2 (broadcast)
(full)
IPXSAP: positing update to 13.ffff.ffff.ffff via Ethernet0.3
dcaend )
Look at e0.3. It has an error message with a network number of 12345. That
is the mystery network that I had my wife put in an adjacent router. Thank
you Ron, for the idea. If you look at my config, e0.3 has an encapsulation
of arpa. I deleted the subinterfaces and created a main interface that had
an encap of arpa. I then saw my saps come through the debug.
IPXSAP: positing update to 12345.ffff.ffff.ffff via Ethernet0 (broadcast)
(full)
IPXSAP: suppressing null update to 12345.ffff.ffff.ffff
IPXSAP: Response (in) type 0x2 len 96 src:12345.0050.0f01.1c60
dest:12345.ffff.ffff.ffff(452)
type 0x4, "surf", 10.0010.0010.0010(451), 3 hops
The whole process took less than 10 minutes! Wooohooo!
7 days 'til San Jose
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Earl Aboytes
Senior Technical Conultant
GTE Managed Solutions
805-381-8817
earl.aboytes@telops.gte.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of Aaron
DuShey
Sent: Monday, May 15, 2000 2:37 PM
To: 'Jay Rose'; 'Brad Ellis'; 'Asbjorn Hojmark'; ccielab@groupstudy.com
Subject: RE: Finding IPX network and encap
where in the debug did you see the encap? I can't seem to find it?
Aaron DuShey
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Jay Rose
Sent: Sunday, May 14, 2000 5:19 PM
To: Brad Ellis; Asbjorn Hojmark; ccielab@groupstudy.com
Subject: RE: Finding IPX network and encap
What about "show ipx interface brief"
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Brad Ellis
Sent: Monday, 15 May 2000 9:04 AM
To: Asbjorn Hojmark; ccielab@groupstudy.com
Subject: Re: Finding IPX network and encap
Asbjorn,
I know what you're getting at, but I wasn't able to figure out another way
of doing it. It's a pain in the butt and it definitely takes a bit of time
(and patience) to get the right IPX encapsulation and network #.
-B
----- Original Message -----
From: "Asbjorn Hojmark" <Asbjorn@Hojmark.ORG>
To: <ccielab@groupstudy.com>
Sent: Sunday, May 14, 2000 6:02 PM
Subject: Finding IPX network and encap
> Can anyone think of a time-efficient way of finding the correct
> IPX network and encapsulation for an interface when this isn't
> given?
>
> The only way, I can think of, is configuring a network and doing
> 'debug ipx packet'. That way you'll see incoming IPX traffic and
> get the network number. But you'll still have to test all the
> different encapsulations.
>
> TIA,
> -A
> --
> Heroes: Vint Cerf & Bob Kahn, Leonard Kleinrock, Robert Metcalfe
> Links : http://www.hojmark.org/networking/
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:40 GMT-3