Perle Systems IOLINK-520 - Manual (Page 30)

Applications
2.10 — IOLINK-520 & IOLINK-PRO Installation & Applications Guide
Once the WAN connections have been established to the remote partner IOLINK
routers, the IPX router portion of the IOLINK routers will begin to build their routing
tables according to the IPX frames they receive from the network. Manual entries
may be made in the routing tables by adding static IPX routes.
2.1.3.2 - Novell Servers in One Location Only
Some Novell LAN installations require that a remote LAN that consists of only Novell IPX
clients be connected to a central LAN that contains the Novell servers and some more
clients. In this configuration, the IOLINK router IPX router located at the remote site
must be configured with the appropriate IPX network numbers. The IPX network number
must be configured manually because there is no Novell server at the remote site. The
IOLINK router must act as a Novell server to supply the proper IPX network number to
the clients on the remote site LAN.
In the following diagram, the IOLINK router connected to LAN #2 must be configured
with IPX network number 1500 (or any other valid, unique IPX network number) using the
appropriate frame type. The clients connected to LAN #2 must also be running with the
same frame type as defined on the IOLINK router. After the IOLINK routers have
established the WAN connection, the IPX routing procedures will cause the names of the
services located on LAN #1 to be stored in the services table on the IOLINK router on
LAN #2. When one of the clients on LAN #2 starts up, it will look for a server on the local
LAN and the IOLINK router will respond with the list of servers that are located on LAN
#1.
Figure 2 -4 IPX Routed Local Area Networks (Servers on one side)
WAN connection
Novell Server Novell IPX Client Novell IPX Client Novell IPX Client
LAN #1
IPX Network Address
1512
IPX Network Address
1500 - defined on router
LAN #2