Lucent Technologies 6000 - Manual (Page 533)

Configuring Packet Bridging
Configuring bridged connections
MAX 6000/3000 Network Configuration Guide 14-13
IPX Frame
The IPX Frame parameter located in the Ethernet > Mod Config > Ether Options profile,
specifies the type of packet frame the MAX routes and spoofs. The setting is based on the type
of IPX frame used by the majority of NetWare servers on Ethernet network (IEEE 802.2 by
default). If some NetWare software transmits IPX in a frame type other than the type specified,
the MAX drops those packets, or if bridging is enabled, it bridges them. If you do not specify
an IPX frame type in the Mod Config > Ether Options profile, you must set the Connections >
Connection profile > IPX Options > Handle IPX parameter to N/A. (If you are not familiar
with the concept of packet frames, see the Novell documentation. Set the Handle IPX
parameter to N/A if an IPX frame type is not specified in the Ethernet profile. For more
information about IPX frame types and how they affect routing and bridging connections, see
Chapter 12, “Configuring IPX Routing.”
Route IPX
The Route IPX parameter in a Connection profile enables or disables the routing of IPX data
packets for the connection. IPX routing must be enabled on both sides of the connection, and
the MAX unit must be configured with an IPX network address and frame type in the Ethernet
Mod Config > Ether Options profile (as discussed in “Enabling IPX routing in the MAX” on
page 12-5. Note that the MAX routes and spoofs only one IPX frame type. Other frame types
are bridged if bridging is enabled. If you set Route IPX to Yes in the Connection profile, the
system sets the IPX Options > Handle IPX parameter to N/A but acts as if the parameter is set
to Server.
Handle IPX
The Handle IPX parameter, located in the Connections > Connection profile > IPX Options
subprofile, specifies IPX server or IPX client bridging. Use IPX server bridging when the local
Ethernet network supports NetWare servers (or a combination of clients and servers) and the
remote network supports NetWare clients only.
Use IPX client bridging when the local Ethernet network supports NetWare clients but no
servers. In an IPX client bridging configuration, you want the local clients to be able to bring
up the WAN connection by querying (broadcasting) for a NetWare server on a remote network.
You also want to filter IPX RIP and SAP updates, so the connections should not remain up
permanently.
Note: If NetWare servers are supported on both sides of the WAN connection, Lucent
strongly recommends that you use an IPX routing configuration instead of bridging IPX. If you
bridge IPX in this type of environment, client-server logins are lost when the MAX brings
down an inactive WAN connection.
If an IPX frame type is not specified in the Ethernet > Mod Config > Ether Options profile, set
the Handle IPX parameter to N/A.
Netware t/o (watchdog spoofing)
NetWare servers send out NCP watchdog packets to monitor client connections. Only clients
that respond to watchdog packets remain logged into the server.
In an IPX server bridging configuration, you want the MAX unit to respond to NCP watchdog
requests on behalf of remote clients, but to bring down inactive connections whenever