User`s guide

Configuring IPX Routing
Working with the RIP and SAP tables
4-18 Preliminary January 30, 1998 Pipeline User’s Guide
This setting specifies that the Pipeline receives the RIP table from the other
IPX router but will not upload its RIP table. To disable IPX RIP, set:
IPX RIP=None
4
Close the Connection profile.
Configuring a static IPX route
Each static IPX route contains all of the information needed to reach one
NetWare server on a remote network. When the Pipeline receives an outbound
packet for that server, it finds the referenced Connection profile and dials the
connection.
Note:
You don’t need to create IPX routes to servers on the local Ethernet.
Most sites configure only a few IPX routes and rely on RIP for most other
connections. If you have servers on both sides of the WAN connection, you
should define a static route to the remote site even if your environment requires
dynamic routes. If you have one static route to a remote site, it should specify a
“master” NetWare server that knows about many other services. NetWare
workstations can then learn about other remote services by connecting to that
remote NetWare server.
Note:
Remember that static IPX routes are manually administered, so they must
be updated if there is a change to a remote server.
To define an IPX Route profile:
1
Open Ethernet > IPX Routes > any profile.
For example:
Server Name=SERVER-1
Active=Yes
Network=ccccfff1
Node=000000000001
Socket=0000
Server Type=0004
Hop Count=2
Tick Count=12
Connection #=1
2
Specify the name of the remote NetWare server.