At 05:57 PM 6/25/01, Michael L. Williams wrote:
>It seems interested to note that no one has mentioned that IPX not only
>performs addressing and path determination (layer 3) but can also act as
>it's own conectionless transport too (layer 4) like UDP......
The IPX layer identifies a source and destination socket in addition to
source and destination layer-3 addresses, but it is still a layer-3
protocol in my opinion. AppleTalk DDP also identifies sockets, but it's
layer 3 also. IPX and DDP have the same job as IP. IP identifies the next
layer up also. It has its protocol type field.
IPX RIP does path determination.
> IPX does HAVE
>to use SPX for transport.....
Not sure if that was a typo, but IPX does NOT have to use SPX for
transport. Most packets in an IPX network do not have an SPX header.
>so IPX is really a Layer3 & 4 protocol
Perhaps what you are getting at is the extra glue between NetWare Core
Protocol and IPX that does things like sequencing and acknowledging.
Protocol analyzers, such as Sniffer and EtherPeek, decode this as part of
NCP. Novell documentation does not put it with IPX. (I have the IPX
functional specification but not any formal NCP documentation). Perhaps
some books put it with IPX. Here's an EtherPeek packet to help you
understand my point:
802.3 Header
Destination: 00:80:5F:05:77:29
Source: 00:01:83:A0:28:CD
Length: 40
IPX - NetWare Protocol
Checksum: 0xFFFF
Length: 39
Transport Control:
Reserved: %0000
Hop Count: %0000
Packet Type: 17 NCP - Netware Core Protocol
Destination Network: 0x00094301
Destination Node: 00:00:00:00:00:01
Destination Socket: 0x0451 NetWare Core Protocol
Source Network: 0x00000001
Source Node: 00:01:83:A0:28:CD
Source Socket: 0x4003 IPX Ephemeral
NCP - Netware Core Protocol
Request Type: 0x2222 Request
Sequence number: 203
Connection number low: 123
Task number: 20
Connection number high: 0
Function Code: 62 Alt Dir Search Parameters
Alt Dir Search Parameters Request
Directory handle: 45
File Name:
Extra bytes (Padding):
v.....v 76 0C 14 00 18 00 76
Frame Check Sequence: 0x04004A00
Priscilla
>Mike W.
>
>"Priscilla Oppenheimer" wrote in message
>[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > At 12:11 PM 6/25/01, Jack Nalbandian wrote:
> >
> > >Thank you veery much for clarifying that.
> > >
> > >Pardon my ignorance on Novell stuff, but does this mean, then, that the
> > >ODI "wrap" and IPX "share" the layer 2 functions?
> >
> > No. IPX does layer-3 functions.
> >
> > ODI is just an Ethernet driver. It allows a NIC to be used to carry data
> > for different protocols. For example, ODI allows a computer with a single
> > NIC to be simultaneously connected to both an IPX and an IP network. So,
> > IPX interfaces to ODI. It's a layered architecture.
> >
> > >Also, what is the NWLINK equivalent of ARP?
> >
> > NWLINK is NetBIOS running on top of IPX/SPX. It's just generic IPX. It
has
> > nothing to do with ARP which is an IP function to map IP addresses to MAC
> > addresses.
> >
> > These basic questions belong on the CCNA study list, not this one. Also,
> > find yourself a good protocol chart. Every so often someone sends around
a
> > link to one.
> >
> > Priscilla
> >
> >
> > >-----Original Message-----
> > >From: Priscilla Oppenheimer
> > >[mailto:[EMAIL PROTECTED]]
> > >Sent: Monday, June 25, 2001 11:51 AM
> > >To: [EMAIL PROTECTED]
> > >Subject: RE: why there are so many IPX traffic in my network [7:9045]
> > >
> > >IPX runs at layer 3. There's no question of that.
> > >
> > >Perhaps the confusing thing is that IPX layer-3 addresses consist of
> > >network.MAC. The node part of the address is the same as the layer-2 NIC
> > >address, also known as MAC or hardware address.
> > >
> > >This means that IPX doesn't need an ARP. If you know the Layer-3
address,
> > >you know the Layer-2 address also.
> > >
> > >Above IPX, the most common Novell protocol is NetWare Core Protocol
(NCP)
> > >used by file servers. Print servers use SPX. It's a myth that NCP uses
>SPX.
> > >It doesn't.
> > >
> > >Priscilla
> > >
> > >At 12:57 PM 6/25/01, Jack Nalbandian wrote:
> > > >I thought IPX was layer 2 in the IPX/SPX stack.
> > > >
> > > >-----Original Message-----
> > > >From: Charles Manafa
> > > [mailto:[EMAIL PROTECTED]]
> > > >Sent: Wednesday, June 20, 2001 7:25 AM
> > > >To: [EMAIL PROTECTED]
> > > >Subject: RE: why there are so many IPX traffic in my network [7:9045]
> > > >
> > > >
> > > >IPX is layer 3
> > > >Switches operate at layer 2
> > > >
> > > >CM
> > > >
> > > >-----Original Message-----
> > > >From: Sim, CT (Chee Tong)
> > > >To: [EMAIL PROTECTED]
> > > >Sent: 20/06/01 08:14
> > > >Subject: RE: why there are so many IPX traffic in my network [7:9045]
> > > >
> > > >Thanks! I found the setting in the printer to disable the IPX.
>However
> > > >Can
> > > >we filter the IPX traffic on our 2900 IOS switches, and set based 5500
> > > >switches. IF yes.. what is the command to disable transmission of IPX
> > > >traffic in the switches.
> > > >
> > > >
> > > >
> > > >-----Original Message-----
> > > >From: Jim Dixon
> > > [mailto:[EMAIL PROTECTED]]
> > > >Sent: Tuesday, June 19, 2001 9:40 PM
> > > >To: Sim, CT (Chee Tong)
> > > >Subject: RE: why there are so many IPX traffic in my network [7:9045]
> > > >
> > > >
> > > >It may be an HP JetDirect card.
> > > >
> > > >Get rid of it by assigning your JetDirect and or Printer an IP Address
> > > >(whichever you need to do)
> > > >Turn IPX off on the JetDirect Print Server.
> > > >
> > > >OR
> > > >
> > > >Filter IPX at your router and see if you can still print.
> > > >Then
> > > >RE_check for your IPX.. Is it still there? Did printer stop working?
> > > >If so
> > > >then you may want to keep IPX till you can switch to IP.
> > > >
> > > >-----Original Message-----
> > > >From: Sim, CT (Chee Tong)
> > > [mailto:[EMAIL PROTECTED]]
> > > >Sent: Tuesday, June 19, 2001 8:12 AM
> > > >To: [EMAIL PROTECTED]
> > > >Subject: why there are so many IPX traffic in my network [7:9045]
> > > >
> > > >
> > > >Hi.
> > > >
> > > >I use the fluke meter and ethereal software to check the health of our
> > > >network and I found there are a lot of IPX traffic in our network.
But
> > > >we
> > > >have no Novell server here and where is the IPX traffic coming from?
> > > >
> > > >In the ethereal output I saw a lot of statement like
> > > >source destination Protocol Info
> > > >0.0008c7280106 0.ffffffffffff IPX SAP Nearest Query
> > > >0.0008c7280106 0.ffffffffffff IPX SAP General Query
> > > >0.0008c7280106 0.ffffffffffff IPX SAP General Response
> > > >0.0008c7280106 0.ffffffffffff NBIPX Find name "our
> > > >domain
> > > >name"
> > > >0.0008c7280106 0.ffffffffffff BROWSER Host Announcement
> > > >"workstation name" workstation, server, print queue server, NT
> > > >workstation,
> > > >NT server, Potential browser.
> > > >
> > > >In fluke meter, I saw these IPX are mostly by printer and printer
> > > >server?
> > > >Why printer got something to do with IPX .
> > > >
> > > >How to get rid of this?
> > > >
> > > >Please advice
> > > >Thanks
> > > >
> > > >
> > > >
> > > >-----Original Message-----
> > > >From: jason douglas
> > > [mailto:[EMAIL PROTECTED]]
> > > >Sent: Tuesday, June 19, 2001 8:38 PM
> > > >To: [EMAIL PROTECTED]
> > > >Subject: Re: what about ccie-pre-qualification test in boson cisco [7:
> > > >9041]
> > > >
> > > >
> > > >I thought it was similar.
> > > >
> > > >frank wrote:
> > > > >
> > > > > compared with 350-001,easier or much the same?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > frank
> > > >--
> > > >Jason Douglas
> > > >Lucent World Wide Services
> > > >Pager 888-451-0755
> > > >==================================================================
> > > >De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
> > > >is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
> > > >onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en
> > > >de afzender direct te informeren door het bericht te retourneren.
> > > >==================================================================
> > > >The information contained in this message may be confidential
> > > >and is intended to be exclusively for the addressee. Should you
> > > >receive this message unintentionally, please do not use the contents
> > > >herein and notify the sender immediately by return e-mail.
> > > >
> > > >
> > > >==================================================================
> > > >==================================================================
> > > >De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
> > > >is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
> > > >onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en
> > > >de afzender direct te informeren door het bericht te retourneren.
> > > >==================================================================
> > > >The information contained in this message may be confidential
> > > >and is intended to be exclusively for the addressee. Should you
> > > >receive this message unintentionally, please do not use the contents
> > > >herein and notify the sender immediately by return e-mail.
> > > >
> > > >
> > > >==================================================================
> > >________________________
> > >
> > >Priscilla Oppenheimer
> > >http://www.priscilla.com
> > ________________________
> >
> > Priscilla Oppenheimer
> > http://www.priscilla.com
________________________
Priscilla Oppenheimer
http://www.priscilla.com
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=9868&t=9045
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
