From: MADMAN (dmadlan@xxxxxxxxx)
Date: Thu Apr 11 2002 - 18:27:59 GMT-3
I sure thought I had done this before so I had to try it and yes it
does work!!!!
C2620A#sh ipx ro
Codes: C - Connected primary network, c - Connected secondary network
S - Static, F - Floating static, L - Local (internal), W - IPXWAN
R - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregate
s - seconds, u - uses, U - Per-user static
1 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.
No default route known.
C DEAD (NOVELL-ETHER), Fa0/0
C2620A#
1w5d: IPX: Fa0/0:BEEF.0030.94ff.7250->BEEF.ffff.ffff.ffff ln= 40 tc=00
pt=01 ds=
0453 ss=0453, rcvd
1w5d: IPX: Fa0/0:BEEF.0030.94ff.7250->BEEF.ffff.ffff.ffff ln= 40 tc=00
pt=01 ds=
0453 ss=0453, bad pkt
1w5d: IPX: Fa0/0:BEEF.0030.94ff.7250->BEEF.ffff.ffff.ffff ln= 34 tc=00
pt=04 ds=
0452 ss=0452, rcvd
1w5d: IPX: Fa0/0:BEEF.0030.94ff.7250->BEEF.ffff.ffff.ffff ln= 34 tc=00
pt=04 ds=
0452 ss=0452, bad pkt
C2620A#sh ipx ro
I configured ipx network DEAD on the 2620 and BEEF on an adjacent
3660, did a debug IPX packet and wallah it complains about BEEF
Jon O'Nan wrote:
>
> Tried it...
>
> r1#xi bri
> Interface IPX Network Encapsulation Status IPX
> State
> Ethernet0 100 SNAP up [up]
> Serial0 unassigned not config'd administratively down n/a
> Serial1 unassigned not config'd up n/a
> r1#
> r1#
> r1#
> r1#
> 4d04h: IPXRIP: positing full update to 100.ffff.ffff.ffff via Ethernet0
> (broadcast)
> 4d04h: -Traceback= 36CAA3A 36BEDA8 36C937C 36C9534
> 4d04h: IPX: Sched upd for Et0 (RIP)(FULL): gap = 55, holddown = 5
> 4d04h: IPXRIP: Update for Ethernet0:100 (FULL)(RESET PH)
> 4d04h: ?: 100 via 100:Et0 (FULL:BCAST) (SHRZ) NO
> 4d04h: IPXRIP: suppressing null update to 100.ffff.ffff.ffff (Ethernet0),
> sent 0 packet(s)(IDLE)
> 4d04h: IPXSAP: positing update to 100.ffff.ffff.ffff via Ethernet0
> (broadcast) (full)
> 4d04h: -Traceback= 36CA634 36BEE52 36C93F2 36C9534
> 4d04h: IPX: Sched upd for Et0 (SAP)(FULL) (NONE)
> 4d04h: IPXRIP: positing full update to 100.ffff.ffff.ffff via Ethernet0
> (broadcast)
> 4d04h: -Traceback= 36CAA3A 36BEDA8 36C937C 36C9534
> 4d04h: IPX: Sched upd for Et0 (RIP)(FULL): gap = 55, holddown = 5
> 4d04h: IPXRIP: Update for Ethernet0:100 (FULL)(RESET PH)
> 4d04h: ?: 100 via 100:Et0 (FULL:BCAST) (SHRZ) NO
> 4d04h: IPXRIP: suppressing null update to 100.ffff.ffff.ffff (Ethernet0),
> sent 0 packet(s)(IDLE)
> 4d04h: IPXSAP: positing update to 100.ffff.ffff.ffff via Ethernet0
> (broadcast) (full)
> 4d04h: -Traceback= 36CA634 36BEE52 36C93F2 36C9534
> 4d04h: IPX: Sched upd for Et0 (SAP)(FULL) (NONE)
>
> ----------------------------------------------------------------------------
> ----------------------------
>
> r2#xi brie
> Interface IPX Network Encapsulation Status IPX
> State
> Ethernet0 2000 NOVELL-ETHER up [up]
> Serial0 unassigned not config'd administratively down n/a
> Serial1 unassigned not config'd up n/a
> TokenRing0 unassigned not config'd administratively down n/a
> r2#
> ----- Original Message -----
> From: "Lupi, Guy" <Guy.Lupi@eurekaggn.com>
> To: "'MADMAN'" <dmadlan@qwest.com>; "Jon O'Nan" <jononan@columbus.rr.com>
> Cc: <ccielab@groupstudy.com>
> Sent: Thursday, April 11, 2002 3:59 PM
> Subject: RE: IPX Question
>
> > Does this also work for encapsulation mismatches? I can't test it right
> > now, thanks.
> >
> > -----Original Message-----
> > From: MADMAN [mailto:dmadlan@qwest.com]
> > Sent: Thursday, April 11, 2002 3:48 PM
> > To: Jon O'Nan
> > Cc: ccielab@groupstudy.com
> > Subject: Re: IPX Question
> >
> >
> > Give the interface an IPX network number and then debug IPX. You
> > should see the conflict.
> >
> > Dave
> >
> > Jon O'Nan wrote:
> > >
> > > If I had a router connected to an IPX network and did not know the
> > > network number. How would I discover the network on my router?
> > >
> > > Help Please!!!
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:05 GMT-3