background image
Introduction to Novell IPX
415
furnish. All servers receiving the SAP broadcast incorporate the information
into their own SAP tables; they then rebroadcast the SAP entries in their own
SAP updates. Because SAP information is shared among all servers, all
servers eventually become aware of all available services and are thereby
equipped to respond to client GNS requests. As new services are introduced,
they're added to SAP tables on local servers and are rebroadcast until every
server knows they exist and knows where to get them.
So how does a Cisco router fit in here? Well, as far as SAP is concerned,
the Cisco router acts just like another NetWare server. By default, an SAP
broadcast won't cross a Cisco router. A Cisco router catalogs all SAPs heard
on any of its IPX-enabled interfaces into its SAP table; unless you change the
settings, the router then broadcasts the whole table from each of those inter-
faces at 60-second intervals (just as a NetWare server does). This is an
important point, especially with WAN links. The router isolates SAP broad-
casts to individual segments and passes along only the summarized informa-
tion to each segment. Let's take a look at an SAP broadcast with the
Etherpeek analyzer.
Flags: 0x00
Status: 0x00
Packet Length:306
Timestamp: 23:48:36.362000 06/28/1998
Ethernet Header
Destination
: ff:ff:ff:ff:ff:ff Ethernet Brdcast
Source
: 00:80:5f:ad:14:e4
Protocol Type:81-37 NetWare
IPX - NetWare Protocol
Checksum
: 0xffff
Length
: 288
Transport Control:
Reserved
: %0000
Hop Count
: %0000
Packet Type
: 4
PEP
Destination Network: 0xcc715b00
Destination Node
: ff:ff:ff:ff:ff:ff Ethernet
Brdcast
Destination Socket
: 0x0452 Service Advertising
Protocol
Copyright ©2002 SYBEX, Inc., Alameda, CA
www.sybex.com