User`s guide

Configuring IPX Routing
How the Pipeline performs IPX routing
Pipeline User’s Guide Preliminary January 30, 1998 4-7
Tick Count=12
Connection #=0
Note:
The Pipeline cannot support more than 300 server and route entries. In
order to keep the Pipeline operational with IPX enabled on a large network, the
Pipeline enforces a maximum limit of 300 server and route entries, including
limit checking for both server and route entries. When the Pipeline reaches its
limit of 300, it drops all IPX route and SAP packets containing additional routes
and services. This limit results in an incomplete network map, so you need to
activate a size-limiting feature, such as enabling IPX SAP Proxy or IPX filtering.
(To check the number of current servers and routes, see “Using the terminal
server interface” on page 8-17, specifically note the function of the
show netw
servers
command. For information about how to use the IPX SAP Proxy
parameter, refer to the Reference Guide, and also see “IPX SAP proxy servers”
on page 4-14. For information on setting up IPX filtering, refer to “Managing
IPX SAP filters” on page 4-21.)
IPX SAP filters
You might not want the Pipeline SAP table to include long lists of all servers
available at a remote site. IPX SAP filters let you exclude services from the SAP
table, or explicitly include certain services.
SAP filters can be applied to inbound or outbound SAP packets. Inbound filters
control which services are added to the Pipeline unit’s SAP table from
advertisements on a network link. Outbound filters control which services the
Pipeline advertises on a particular network link. (For more information, see
“Managing IPX SAP filters” on page 4-21.)
Configure IPX SAP filters in Ethernet
>
IPX SAP filters
>
any profile:
Name=optional
Input SAP filters...
Output SAP filters
Valid=Yes
Type=Exclude
Server Type=0004
Server Name=SERVER-1
See “Managing IPX SAP filters” on page 4-21 for details on each parameter.