From: steven.j.nelson@bt.com
Date: Sat Sep 21 2002 - 05:43:46 GMT-3
John
Do you have IPX rip running across the interface and also some IPX networks
on the other end ?
I will post some debug over the weekend so you can see the output.
Thanks
Steve
-----Original Message-----
From: JohnZ [mailto:Johnzaggat@yahoo.com]
Sent: 21 September 2002 05:22
To: Nelson,SJ,Steven,IVNH33 C; CLarson; syv
Cc: ccielab
Subject: Re: Re[2]: IPX network discovery
Well I tried the subs and disable the ipx route-cache on the main interface
and with debug ipx packet I don't get any updates from the ethernet
interface. The only time I get an update is when do shut /no shut on the
router on the other end which will be undoable in a lab. Is there any thing
else I need to do in addition to the steps outlined here.
Thanks
----- Original Message -----
From: <steven.j.nelson@bt.com>
To: <CLarson@usaid.gov>; <syv@911networks.com>
Cc: <ccielab@groupstudy.com>
Sent: Friday, September 20, 2002 8:39 AM
Subject: RE: Re[2]: IPX network discovery
> Chris
>
> I think svy is being a bit naieve if he thinks Cisco will simply let you
use
> CDP and such simple tools in a lab environment.
>
> Anyway stick to the subs it works...
>
> Steve
> CCIE#10055
>
> -----Original Message-----
> From: Larson, Chris [mailto:CLarson@usaid.gov]
> Sent: 20 September 2002 16:36
> To: 'syv'; Nelson,SJ,Steven,IVNH33 C
> Cc: ccielab@groupstudy.com
> Subject: RE: Re[2]: IPX network discovery
>
>
>
> Not necessarily true. This does not show everything you need. If you are
> connected to a switch I do not believe it will give you the IPX network
info
> of the neighboring router. Even if it does, it is possible to turn it off
on
> the router so you cannot get the info. ......
>
> The way described previously with the sub ints and encapsulations will
> definetly work. I do not think Cisco will make it as easy as show cdp
> neighbor even if it will show you the IPX network.
>
>
>
> -----Original Message-----
> From: syv [SMTP:syv@911networks.com]
> Sent: Friday, September 20, 2002 10:50 AM
> To: steven.j.nelson@bt.com
> Cc: ccielab@groupstudy.com
> Subject: Re[2]: IPX network discovery
>
> On Friday, September 20, 2002, steven.j.nelson@bt.com wrote:
>
> The simplest is:
>
> show cdp neighbor
>
> and everything is there.
>
> -----Original Message-----
> sjnbc> Pieter
>
> sjnbc> Create some subinterfaces off the main interface the the ipx
> device you want
> sjnbc> to discover is hanging off.
>
> sjnbc> Make sure each sub interface has a different IPX address and
> encapsulation
> sjnbc> type, also check that the main interface has IPX route-caching
> disabled.
>
> sjnbc> Debug ipx packet, and you will see an error message from the
> interface with
> sjnbc> the correct encapsulation but the incorrect address, the correct
> address
> sjnbc> will be in the debug. Voila' you have found the network and encaps.
>
> sjnbc> Now remove the subs and put the correct details onto the main
> interface and
> sjnbc> you should be working.
>
> sjnbc> Thanks
>
> sjnbc> Steve
> sjnbc> CCIE #10055
>
> sjnbc> -----Original Message-----
> sjnbc> From: Pieter Jordaan [ mailto:pieterj@is.co.za
> <mailto:pieterj@is.co.za> ]
> sjnbc> Sent: 20 September 2002 10:22
> sjnbc> To: ccielab@groupstudy.com
> sjnbc> Subject: IPX network discovery
>
>
> sjnbc> Hi
>
>
>
> sjnbc> My understanding is that nhrp will help me in discovering
> what the IPX
> sjnbc> network number on a wan link is, Is it possible to discover IPX
> networks on
> sjnbc> Ethernet in a similar manner to the way NHRP works, or how would I
go
> about
> sjnbc> doing this.
>
>
>
> sjnbc> Thanks
>
>
>
> sjnbc> Pieter Jordaan
>
> sjnbc> Hosting Engineer
>
> sjnbc> Tel: 27115750313
>
> sjnbc> Email: pieterj@is.co.za < mailto:pieterj@is.co.za
> <mailto:pieterj@is.co.za> >
>
> sjnbc> Web: http://www.is.co.za <http://www.is.co.za> <
> http://www.is.co.za <http://www.is.co.za> >
>
>
>
>
>
>
>
>
>
> sjnbc> "This e-mail may contain confidential information and may be
> legally
> sjnbc> privileged and is intended only for the person to whom it is
> addressed. If
> sjnbc> you are not the intended recipient, you are notified that you may
not
> use,
> sjnbc> distribute or copy this document in any manner whatsoever. Kindly
> also
> sjnbc> notify the sender immediately by telephone, and delete the e-mail.
> When
> sjnbc> addressed to clients of the company from where this e-mail
originates
> ("the
> sjnbc> sending company ") any opinion or advice contained in this e-mail
is
> subject
> sjnbc> to the terms and conditions expressed in any applicable terms of
> business or
> sjnbc> client engagement letter . The sending company does not accept
> liability for
> sjnbc> any damage, loss or expense arising from this e-mail and/or from
the
> sjnbc> accessing of any files attached to this e-mail."
>
>
> Thanks
> ----
> syv@911networks.com
This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:59 GMT-3