Ipx Servers; Important Considerations - 3Com corebuilder 3500 Implementation Manual

434 C 15: IPX R
HAPTER

IPX Servers

Important
Considerations
OUTING
Your system creates and maintains a server information table that lists all
the servers that reside on other IPX networks. You can:
Use SAP to exchange server information dynamically.
Make static entries in the server table.
Consider the following guidelines when you set up an IPX server:
The first line in the output (status line) indicates whether:
IPX forwarding is enabled.
IPX RIP mode is active.
IPX RIP mode triggered updates are enabled.
IPX SAP mode is active.
IPX SAP triggered updates are enabled.
The secondary route/server option is enabled on the system.
The route table display shows the range for the server table primary
entries in the format n-m, where n is the current number of entries
and m is the maximum number of entries.
Static servers remain in the table until you:
Remove them.
Remove the corresponding interface.
Remove the route to the corresponding network address.
A static server must have an IPX network address that corresponds to
a configured interface or to a static route. If an interface goes down,
any static servers on that interface are permanently removed from the
server table until the interface comes back up.
Static servers take precedence over dynamically learned servers to the
same destination. You can have a maximum of 32 static servers.
Before you define static servers on the system, first define at least one
IPX interface.
When you use the ipx server remove option to remove a server, that
server is immediately removed from the Server Information Table.
When you use the
dynamically learned servers, all dynamically learned servers are
immediately removed from the Server Information Table.
ipx server flush
command to remove all