User`s guide

Configuring IPX Routing
How the Pipeline performs IPX routing
4-6 Preliminary January 30, 1998 Pipeline User’s Guide
end. However, it does respond to RIP and SAP queries received from dial-in
clients.
IPX Route profiles
Static IPX routes are specified in IPX Route profiles. When the Pipeline unit’s
RIP and SAP tables are cleared due to a reset or power-cycle, the static routes are
added when the unit initializes. Each static route contains the information needed
to reach one server.
When the Pipeline is connecting to another Pipeline, you can choose not to
configure a static route. Instead, you can use the DO menu to manually dial the
initial connection to that site following a power-cycle or reset. Once connected,
the Pipeline downloads the RIP table from the remote site and maintains the
routes as static until the next power-cycle or reset.
Static routes need manual updating whenever the specified server is removed or
has an address change. However, static routes are a way to ensure that the
Pipeline can bring up the appropriate connection in response to clients’ SAP
requests and to prevent timeouts when a client takes a long time to locate a server
on the WAN. (For more information, see “Configuring a static IPX route” on
page 4-18.)
You can also specify a route to a destination IPX network without defining an
IPX server in the IPX Routes profile. You can reach an IPX network by entering
the Network number (for example, Network=00123456) without specifying the
Server Name and Server Type.
To configure IPX routes, open Ethernet
>
IPX Routes
>
any profile
For example:
Server Name=server-name
Active=Yes
Network=CC1234FF
Node=000000000001
Socket=0000
Server Type=0004
Hop Count=2