From: Lopez, James (james.lopez@xxxxxxxxxxxxxx)
Date: Thu Apr 11 2002 - 18:06:28 GMT-3
Don't forget to try different encapsulations :-) (arpa, sap, snap ....)
-----Original Message-----
From: sanjay [mailto:ccienxtyear@hotmail.com]
Sent: Thursday, April 11, 2002 3:47 PM
To: Jon O'Nan; Lupi, Guy; 'MADMAN'
Cc: ccielab@groupstudy.com
Subject: Re: IPX Question
There needs to be some broadcast traffic comming from that router. Try
setting up a static SAP and you will be able to see the sap and Network
number in the IPX debug
-Sanjay
----- Original Message -----
From: "Jon O'Nan" <jononan@columbus.rr.com>
To: "Lupi, Guy" <Guy.Lupi@eurekaggn.com>; "'MADMAN'" <dmadlan@qwest.com>
Cc: <ccielab@groupstudy.com>
Sent: Thursday, April 11, 2002 1:11 PM
Subject: Re: IPX Question
> 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