From: Mingzhou Nie (mnie@xxxxxxxxx)
Date: Tue Aug 20 2002 - 22:39:15 GMT-3
Fred,
Do you have sample configs for nlsp on WAN w/o ipxwan? I couldn't get
it work.
r131
interface Serial2/0
no ip address
ipx network 7878
ipx nlsp enable
!
ipx router nlsp
!
!
ipx router rip
no network 7878
--- Fred Ingham <fingham@cox.net> wrote:
> The IPXWAN network number is only used in the ipxwan packet exchanges
> and
> does not get propagated. The network number can be different on
> either end
> . The router that is the master will dictate the actual network
> number used
> in the exchange.
>
> For instance, R1 is configured as ipx ipxwan a1 14 R1, R4 is
> configured as
> ipx ipxwan a4 144 R4, NLSP is enabled, RIP/SAP are disabled. R4 with
> the
> higher internal address (a4 vs. a1) will become the master and will
> dictate
> that 144 is the network number to be used in ipxwan packets. In the
> R1 ipx
> route table, 144 is the W network. From R1 an IPX ping to
> 144.0000.00a4.0000 works as does a ping to 144.0000.00a1.0000 in the
> other
> direction. Use sh ipx interface to see the addresses and the
> master-slave
> relationship.
>
> R3 is another NLSP router and does not see either 14 or 144 as you
> observed
> in your original note. This is normal.
>
> Debug below captured on r4.
>
> 1w0d: IPXWAN: Rcv TIMER_REQ on Serial0.14/A4:144, NodeID A1, Seq 0
> 1w0d: IPXWAN: Send TIMER_REQ [seq 1] out Serial0.14/A4:144
> 1w0d: IPXWAN: offer TIMER_REQ routing options NLSP
> 1w0d: IPXWAN: Rcv TIMER_RSP on Serial0.14/A4:144, NodeID A1, Seq 1,
> Del 38
> 1w0d: IPXWAN: Rcv TIMER_RSP accept as MASTER NLSP on Serial0.14
> 1w0d: IPXWAN: state (Sending Timer Requests -> Master: Sent
> Throughput)
> [Serial0
> .14/A4:144 (Received Timer Response as master)]
> 1w0d: IPXWAN: Send NLSP THROUGHPUT [seq 0] out Serial0.14/A4:144
> 1w0d: IPXWAN: Rcv THROUGHPUT response from Serial0.14/A4:144, NodeID
> A1, Seq
> 0
> 1w0d: IPXWAN: Send NLSP THROUGHPUT [seq 1] out Serial0.14/A4:144
> 1w0d: IPXWAN: Throughput size 576 delta 64000
> 1w0d: IPXWAN: Rcv THROUGHPUT response from Serial0.14/A4:144, NodeID
> A1, Seq
> 1
> 1w0d: IPXWAN: state (Master: Sent Throughput -> Master: Sent Delay)
> [Serial0.14/
> A4:144 (Received Second Throughput Response )]
> 1w0d: IPXWAN: Throughput size 576 delta 64000
> 1w0d: IPXWAN: Send NLSP DELAY [seq 0] out Serial0.14/A4:144
> 1w0d: IPXWAN: Rcv DELAY_RSP from Serial0.14/A4:144, NodeID A1, Seq 0
> 1w0d: IPXWAN: Send NLSP DELAY [seq 0] out Serial0.14/A4:144
> 1w0d: IPXWAN: Rcv DELAY_RSP from Serial0.14/A4:144, NodeID A1, Seq 0
> 1w0d: IPXWAN: Rcv DELAY_RSP Delay1 384, Delay2 372, thru 72000
> 1w0d: IPXWAN: state (Master: Sent Delay -> Master: Sent Router Info)
> [Serial0.14
> /A4:144 (Received Second Delay Response)]
> 1w0d: IPXWAN: Send ROUTING_INFO_REQ [seq 0] out Serial0.14/A4:144
> 1w0d: IPXWAN: NLSP delay 1000000, throughput 72000
> 1w0d: IPXWAN: Rcv ROUTING_INFO_RSP from Serial0.14/A4:144, NodeID A1,
> Seq 0
> 1w0d: IPXWAN: NLSP delay 1000000, throughput 72000
> 1w0d: IPXWAN: state (Master: Sent Router Info -> Master: Connect)
> [Serial0.14/A4
> :144 (Received Router Info Rsp as Master)]
>
> This follows the diagram on p.447 of Chappell, Novell's Guide to
> LAN/WAN
> Analysis: IPX/SPX
>
> Hope this answers your original question.
> Fred
> ----- Original Message -----
> From: "ccie candidate" <ccie1@lycos.com>
> To: "ccie candidate" <ccie1@lycos.com>; <ccielab@groupstudy.com>;
> "Fred
> Ingham" <fingham@cox.net>
> Sent: Tuesday, August 20, 2002 12:29 AM
> Subject: Re: NLSP and IPXWAN
>
>
> > ok i would do the same .
> > however my question was about the network assigned by the IPXWAN
> command
> >
> > ipx ipxwan 0 16 R1
> >
> > where 16 is the assigned network for the link by the command ( or i
> understand it like that )
> >
> > this network shows in the routing table as "W" however it dont
> propagate
> with NLSP
> >
> > any comments
> >
> >
> >
> > --
> >
> > On Mon, 19 Aug 2002 23:08:54
> > Fred Ingham wrote:
> > >The configuration guides still have ipxwan as a configuration step
> in
> > >enabling ipx nlsp over a point-to-point serial interface. It
> works
> without
> > >the ipxwan but the costs are different when configuring with
> ipxwan and
> when
> > >just using ipx enable nlsp. If asked to configure it I would use
> ipxwan.
> > >When using ipxwan there is no network number assigned to the
> interface.
> > >
> > >Fred
> > >----- Original Message -----
> > >From: "ccie candidate" <ccie1@lycos.com>
> > >To: <ccielab@groupstudy.com>
> > >Sent: Monday, August 19, 2002 11:40 AM
> > >Subject: NLSP and IPXWAN
> > >
> > >
> > >> folks;
> > >> when running nlsp over wan (serial ) one must use ipxwan
> ...right ??
> > >>
> > >> i read this somewhere multiple times ...i beleive it is right
> unless
> > >someone has different opinion .
> > >>
> > >>
> > >> when i config ipxwan i noticed that the network of the ipxwan
> link
> didnt
> > >show up in the far end routers ..is this normal ???
> > >>
> > >>
> > >> say
> > >> R1-----R2------R3
> > >>
> > >> R1R2 connection is serial running ipxwan ,while R2R3 is
> ethernet.
> > >>
> > >> on r1
> > >> int ser 0
> > >> ipx ipxwan aa 12 r1
> > >> !
> > >> on r2
> > >> int ser 0
> > >> ipx ipxwan bb 12 r2
> > >> !
> > >>
> > >> now NLSP is running for R1 ,R2,R3
> > >>
> > >>
> > >> on R3 , the network 12 didnt show up ..however the internal
> network AA
> and
> > >BB showed normally ...
> > >>
> > >>
> > >> is this normal ?
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:31 GMT-3