[Top] [Prev] [Next] [Bottom]

Using the IPX Protocol

This document provides information on the Nx Networks implementation of the Internetwork Packet Exchange` (IPX` ) protocol. It introduces you to IPX, IPX WAN, and NLSP` and includes the following topics:

Implementation of IPX

Broadcast and IPX WAN Circuits

IPX WAN

NLSP

Configuring IPX

Configuring NLSP

Performing Optional Configuration Tasks

IPX Filtering

IPX Commands

NLSP Configuration Commands

Implementation of IPX

 The Nx Networks implementation of IPX allows the router to function as a Novell" NetWare" internetwork router. It works with all previous Novell NetWare version environments and it supports:

IPX Addressing

 The IPX Network-layer address has three parts:

Network Numbers

 You assign a unique network number to each broadcast circuit. Network numbers allow communication between two entities on different networks. They guide routing decisions.

Note: IPX WAN circuits can have no network number, that is, a network number of zero.

Node Numbers

 The node number identifies a specific system attached to the network.

Ethernet, Token Ring, and FDDI interfaces use their hardware MAC address as their node number, and you cannot change them.

Since a serial line has no hardware MAC address, its node address is either automatically derived from the internal network number, or you can set it manually.

Socket Number

The socket number identifies a higher-layer entity, such as an application or protocol, within a system.

Broadcast and IPX WAN Circuits

IPX runs over circuits. When you configure IPX, you must choose the type of IPX circuit over which you want IPX to run and you must add circuits. There are two kinds of IPX circuits:

A broadcast circuit can broadcast a packet to all other routers on the circuit. It is used for LANs, such as Ethernet, Token Ring, and FDDI. Use the IPX add bcastcircuit command to define broadcast circuits.

An IPX WAN circuit means there is a point-to-point WAN connection with a router on each end. Additionally, IPX WAN circuits always send IPX WAN messages to negotiate certain IPX features before the router sends any IPX data over the circuit. Use the IPX add ipxwancircuit command to define IPX WAN circuits.

In addition to the more obvious differences between broadcast circuits and IPX WAN circuits, note the following important differences in their features, especially in regard to NLSP:

IPX WAN

 IPX WAN is a point-to-point concept. It is the Novell standard way of running the Novell IPX protocol over various WAN media. It interoperates with any router that supports the IPX WAN Novell standard.

Note: You do not have to use IPX WAN over your WANs. You can still run the broadcast circuit method over your WANs, if you wish. However, IPX WAN is the preferred method. NLSP was designed to run very efficiently over IPX WAN.

OpenROUTE software supports IPX WAN Version 2 (IW2) over PPP, Frame Relay, X.25, and IP Relay. For Frame Relay and X.25, the unit of IPX forwarding is an individual circuit.

One of the most important things that IPX WAN does is to set the routing protocol used over the WAN connection. The possible routing protocols are

IP Relay

 You can define an IPX WAN circuit to run over a Novell IP Relay circuit, which you implement using the well-known UDP port number 213 (decimal).

You identify the Novell IP Relay circuit involved by specifying the IP address at the endpoint of the IP tunnel. You can do this in either of the following two ways:

Source IP Address

 When configuring IPX WAN over IP Relay, you must determine the source IP address that the router uses when it sends IPX WAN packets over IP Relay. You determine the source IP address in the following order:

1. If the router has an internal IP address, this address is the source IP address.

2. If the router has a Router ID IP address, this address is the source IP address.

3. If the router has neither an internal IP address nor a Router ID IP address, the source IP address is the IP address of the lowest numbered interface.

Internal IP Address

 To ensure a fixed, consistent IP address as the endpoint of the IPX WAN IP Relay circuit, Nx Networks recommends that you define and always use the other router's internal IP address.

Choosing an IPX WAN or a Broadcast Circuit

The following table summarizes the possible combinations of broadcast circuits and IPX WAN circuits.
WAN Type IPX WAN Circuit Supported Broadcast Circuit Supported Both Supported Simultaneously
PPP

 Yes*

 Yes

 No

IP Relay

 Yes**

 No

 No

Frame Relay

 Yes**

 Yes

 Yes***

X.25

 Yes**

 Yes

 No

* In releases before OpenROUTE 2.2 (Release 16.2), you could only define an IPX WAN circuit on PPP.

** You can define more than one IPX WAN circuit, each mapping to an individual circuit on the network.

*** The Frame Relay broadcast circuit consists of those circuits not defined as IPX WAN circuits.
________________________________________________________

As a general rule, an IPX WAN circuit is always preferable to a broadcast circuit for the following reasons:

As a general rule, you should use a broadcast circuit only for backwards compatibility when interoperating with a router running a release before OpenROUTE 2.2, or for compatibility with other vendors' routers.

Certainly, for PPP, the general rules apply.

For Frame Relay and X.25 networks, Nx Networks prefers the IPX WAN circuit. However, for these networks, there may be some cases where a broadcast circuit could be the better choice. For example, when there is a large number of routers on the same Frame Relay network. In this case, the configuration of a single broadcast circuit may be simpler and easier than configuring a number of separate IPX WAN circuits. The inverse ARP and ARP mechanisms work very well for a broadcast circuit on a Frame Relay network.

Note: All releases before OpenROUTE 2.2 only support a broadcast circuit on Frame Relay and X.25 networks.

It is difficult to say what constitutes a large number of IPX WAN circuits; it depends upon the application traffic load and the bandwidth of the WAN. At this time, Nx Networks considers 20 IPX WAN circuits to be a large number.

Notes:

NLSP

 NLSP provides link state routing for IPX networks. Routing accomplishes two objectives:

A router attaches to two or more disjoint segments and forwards data traffic as needed from one segment to another. It exchanges information with other routers to acquire sufficient information to make the best forwarding choices.

NLSP is essentially a protocol for information exchange among routers geared to the needs of large IPX internetworks.

End Station RIP and SAP Support

With NLSP, the routing protocol can be different between routers, but any NLSP router continues to support the existing RIP and SAP protocols between the end station and the router.

Interoperability With Existing RIP Routers

With NLSP, the router is still capable of routing the RIP protocol to interoperate with non-NLSP routers running RIP.

Adjacencies

One of the most basic and critical NLSP functions is to always keep a list of adjacencies, that is, a list of all other NLSP routers that reside on the same interfaces as itself. These routers are called neighbors and use the NLSP Hello protocol to do this. The NLSP Hello protocol and Hello packet layouts are a little different for broadcast and point-to-point (IPX WAN) circuits.

There are configuration parameters you can adjust and to tune the adjacency part of the NLSP Hello protocol.

NLSP Designated Router

Another basic and critical NLSP function is to elect only one router, out of all the routers on a broadcast circuit as the designated router. Use the NLSP Hello packet protocol to do this.

The designated router is the router that is responsible for generating the NLSP pseudonode Link State Packet (LSP) for the network. It is also the router responsible for sending a Complete Sequence Number Packet (CSNP) to ensure the replicated routing databases are synchronized among the routers.

There are configuration parameters for you to adjust the designated router part of the NLSP Hello protocol.

Propagation and Synchronization of the NLSP
Routing Database

The routing database is propagated using NLSP LSPs.

Synchronization of the replicated routing database is done using NLSP, CSNP, and Partial Sequence Number Packet (PSNP) packets.

There are configuration parameters for you to adjust the process of the NLSP LSP, CSNP, and PSNP protocols.

Decision Process for NLSP Routing

Using all the information about the network kept in its NLSP link state database, NLSP chooses its routes for the routing table based upon the following ordered criteria:

1. End-to-end path with the lowest NLSP cost.

See Table 1.

2. End-to-end path providing the highest network NLSP throughput.

3. End-to-end path providing the lowest total NLSP delay.

4. End-to-end path supporting the largest MTU size.

5. First hop node with the lowest System ID.

6. Circuit with the lowest local circuit ID on the local router.

7. Neighbor with the lowest LAN MAC address on the remote router.

Note: Because cost, throughput, and delay are critical factors in the NLSP routing algorithm, you can manually override them when necessary.

Table 1 Default Costs

Throughput* Default Cost Typical Media
At least

 Strictly less than

0 K

 16 K

 61

16 K

 32 K

 55

32 K

 48 K

 55

48 K

 64 K

 45

 ISDN (U.S.)

64 K

 128 K

 45

 ISDN (European)

128 K

 256 K

 40

256 K

 512 K

 35

512 K

 1 M

 30

1 M

 2 M

 27

 T1 (1.5 M),
Corvus Omninet (1 M)

At least

 Strictly less than

2 M

 4 M

 26

 E1 (2 M), ARCnet (2.5 M)

4 M

 8 M

 25

 Token Ring (4 M)
Corvus Omninet (4 M)

8 M

 10 M

 23

10 M

 16 M

 20

 Ethernet

16 M

 32 M

 19

 Token Ring (16 M)

32 M

 64 M

 15

64 M

 128 M

 14

 FDDI (100 M)
CDDI (100 M)

128 M

 256 M

 9

256 M

 512 M

 9

512 M

1 G

 6

1 G

2 G

 6

2 G

 4 G

 6

4 G

8 G

 3

8 G

16 G

 3

16 G

 32 G

 3

* K = 103 bits/second
M = 106 bits/second
G = 109 bits/second

Note: The lower the cost, the higher the priority.

Configuring IPX

This section describes how to initially configure IPX and IPX WAN circuits.

1. At the Config> prompt, display the IPX configuration prompt. 

Config>protocol ipx
IPX config>
2. Enable IPX on the router. 

IPX config>enable ipx
3. Assign a unique internal network number.

Nx Networks recommends that you use an internal network number. An internal network number is necessary to use IPX WAN circuits. It also serves as a useful IPX Ping target.

The internal network number must be unique among all the other IPX networks in your internet. 

IPX Config>set internal-net-number
Internal network number, or 0 for none (00000000-FFFFFFFD) [0]?
4. Define a broadcast circuit for each Ethernet, Token Ring, or FDDI circuit over which you want to run IPX.

You identify the interface by supplying the interface number. The only critical piece of information is the IPX network number for the circuit, which must be unique among all the other IPX networks in your internet and set to the same value that any other routers and servers are using on the circuit. 

IPX Config>add bcastcircuit
Which interface [0]? 0
IPX enabled on this circuit (y/n) [y]? y
IPX network number (00000001-FFFFFFFD) [0]? 176
Continue with expert config questions?(Yes or [No]): no
5. (Optional) Set the encapsulation type for the Ethernet, Token Ring, or FDDI media with the frame command.

This is usually not necessary since the default frame type is already set to the most popular encapsulation setting for the LAN media. 

IPX Config>frame ethernet_8023
Which interface [0]?
6. Define IPX WAN circuits for your WAN interfaces.

You identify the interface by supplying the interface number. If the interface is a Frame Relay, X.25, or IP Relay network, you must also enter a circuit name to identify which circuit.

The software prompts you for the kind of routing that the network allows on the IPX WAN circuits. The default value (Yes) for unnumbered RIP and RIP usually works very well. You may also want to specify an IPX network number if you think the IPX WAN circuit may end up negotiating RIP as the protocol for the IPX WAN circuit. 

IPX config>add ipxwan
prompting for the involved circuit...
Enter interface number, or 9999 for IP Relay [0]? 4


IPX enabled on this circuit (y/n) [y]? 
Use client-router routing (y/n) [n]? 
Use static routing (y/n) [n]? 
Unnumbered RIP routing acceptable (y/n) [y]?
RIP routing acceptable (y/n) [y]? 
IPX network number (00000001-FFFFFFFD) [0]?

Continue with expert config questions?(Yes or [No]):
7. Define a broadcast circuit on any WAN interfaces that you want to operate as a broadcast circuit.

Although the intention of Novell for the broadcast circuit was for LAN media, a broadcast circuit over a WAN may be useful in the following cases: 

IPX Config>add bcastcircuit
Which interface [0]?
8. If you want your router to run NLSP, enable NLSP. 

IPX Config>enable nlsp
You have finished configuring IPX.

Configuring NLSP

This section describes how to configure NLSP.

1. To access the NLSP Config> prompt, at the IPX Config> prompt, type nlsp. 

IPX Config> nlsp
NLSP (NetWare Link Services Protocol) configuration
NLSP Config>
2. Enable NLSP from either of the following prompts: 

NLSP Config> enable nlsp


IPX Config> enable nlsp

Performing Optional Configuration Tasks

 The following are optional settings that you can adjust:

The following sections provide information on these settings.

Notes:

Memory Allocation Settings

 Set memory allocation with the set memory command that controls the sizes of all the IPX tables: remote and local fast path cache, routing table, and SAP table.

Global Routing Options

Set the global routing options with the set maximum command that controls the maximum number of hops allowed and the number of equal-cost paths to keep.

Keepalive Spoofing and Serialization Packet Filtering

You can configure IPX to prevent keepalive and serialization packets from continually activating a dial-on-demand link or to minimize traffic over a dial-on-demand link. This implementation of IPX keepalive and serialization packet filtering works only in configurations where there is a router running OpenROUTE software at each end of the link.

If a Novell client logs into a Novell server and then is inactive, the server sends periodic keepalive requests to the client and the client replies with keepalive replies.

When a Novell server detects other Novell servers on the network, it sends out periodic IPX serialization packets to all other servers on the network. The serialization packet contains the NetWare license number of the server. Novell servers use these packets to detect duplicate copies of NetWare running on the network.

Set keepalive spoofing/serialization packet filtering on a circuit basis using the expert questions under the following commands:

How Keepalive and Serialization Packet Filtering Work

 In Figure 1, keepalive filtering causes the routers to enter the first keepalive request/reply into their keepalive tables and then forward the request/reply. After that, the routers do not forward keepalive traffic for that client-server connection over the WAN link. Instead, Router A replies to keepalive requests it receives from the Novell server and Router B sends keepalive requests once every minute to the Novell client.

Figure 1 Keepalive Filtering

Serialization packet filtering prevents the routers from forwarding NetWare serialization packets over the WAN link.

RIP Protocol Settings

Set RIP settings on a circuit basis using the expert questions under the set bcastcircuit or set ipxwancircuit command.

SAP Protocol Settings

Set SAP settings on a circuit basis using the expert questions under the set bcastcircuit or set ipxwancircuit command.

NetBIOS Forwarding

You can turn NetBIOS forwarding on or off and set it on a circuit basis using the expert questions under the set bcastcircuit or set ipxwancircuit command.

Split-horizon Routing

You can turn split horizon on or off and set it on a broadcast circuit basis using the expert questions under the set bcastcircuit command.

Split horizon is a method of routing that avoids broadcasting RIP and SAP updates to the router from which they were learned.

As the default, split horizon is enabled. Nx Networks recommends that you do not disable split horizon, except on partially-meshed Frame Relay networks or on X.25 networks.

In a partially-meshed Frame Relay network, as shown in Figure 2, the routers at the branches cannot communicate with each other unless the router at headquarters broadcasts all routing information to all other routers. In this case, disable split horizon on the Frame Relay broadcast circuit at headquarters and enable it at each of the branches to keep them from generating unnecessary traffic.

Figure 2 Partially-meshed Frame Relay Network

NLSP Global Settings

You can set NLSP global settings using the NLSP config>set globals command.

NLSP Parameters

You can set NLSP parameters on a circuit basis by using the expert questions under the set bcastcircuit or set ipxwancircuit command.

IPX Performance Tuning

This implementation of IPX supports a fast path routing concept that splits the forwarding path into a fast path and a slower path to route traffic more efficiently.

The fast path forwards only data packets, while a slower path handles administration packets, such as RIP and SAP packets. Fast path uses an address cache that enables the router to forward a packet quickly.

The router performs slower routing table lookups only during the creation of a cache entry. The cache has an aging mechanism that allows it to deal intelligently with overflows.

The IPX fast path cache includes two entries: local and remote. Each entry can handle the requirements of that type of addressing.

Use the set memory command to set a limit on the maximum number of entries the cache allows. When the cache is full, the router purges the least frequently used entries.

IPX Filtering

There are two types of IPX filters:

You cannot use both a global filter and a circuit filter to filter the same type of traffic.

There are two types of global filters and four types of circuit filters. Table 2 describes the global filters and Table 3 describes the circuit filters.

Table 2 IPX Global Filters

Filter Type Filters based on the . . . Use this filter to . . .
SAP Maximum hop count for a service or group of services.

 Reduce SAP traffic on WANs by controlling the extent to which the router broadcasts information about services.

IPX (Access Controls) IPX source and destination addresses.

 Provide security or stop the forwarding of packets beyond the area of interest.

Table 3 IPX Circuit Filters

Filter Type Filters based on the . . . Use this filter to . . .
RIP Router Address of RIP response packets.

 Group IPX networks into distinct IPX internets and to provide network security by ensuring that only authorized routers communicate routing information.

RIP Network entries of RIP response packets.

 Control the extent to which the circuit broadcasts routing information about selected networks.

SAP Maximum hop count for a service or group of services.

 Reduce SAP traffic on WANs by controlling the extent to which the router broadcasts information about services.

IPX Hop count, IPX packet type, and source and destination addresses.

 Provide security by controlling the extent to which selected servers and end stations can communicate with each other.

Generally, RIP filters deal with internetworking between all stations on a set of networks; SAP filters control which workstations can reach which servers throughout the internetwork; and IPX filters deal with internetworking between individual workstations or individual applications on individual workstation.

The following section describes global filters. Using IPX Circuit Filters describes circuit filters.

Global Filters

This section describes IPX (access controls) and SAP global filters.

IPX Access Controls

IPX access controls prevent the router from forwarding packets based on IPX addresses. You can use access controls to provide security or to stop the forwarding of packets from applications beyond the area of interest.

Access controls are based on the IPX source and destination addresses. Intermediate hop addresses are not important.

An IPX address for access controls consists of an IPX network number, an IPX host number, and a range of IPX socket numbers that you specify in hexadecimal. You can specify the network number and host number as 0, which is a wildcard that matches all network and host numbers. A range of 0 to FFFF is a wildcard for sockets.

When creating IPX access control lists, consider the following:

How Access Controls Work

 The access control list is an ordered list of entries. You can configure each access control entry as inclusive or exclusive. The router compares IPX packets that it receives to see if they match an entry in the access control list. It applies the first match; therefore, the order of access controls is critical.

The router examines IPX packets for the following criteria:

The result of the following example is to forward only those IPX packets sourced from any client on IPX net 1871 destined for the NCP application on the Novell File Server 0000C93A0912 on network 18730. The router drops all other traffic.

IPX config>add access control
Enter type [E]? i
Destination network number (in hex) [ ]? 18730
Destination host number (in hex) [ ]? 0000C93A0912
Starting destination socket number (in hex) [ ]? 0451
Ending destination socket number (in hex) [ ]? 0451
Source network number (in hex) [ ]? 1871
Source host number (in hex) [ ]? 0
Starting source socket number (in hex) [ ]? 4000
Ending source socket number (in hex) [ ]? 7FFF

IPX config>set access-control on

SAP Filters

 IPX SAP filters are a way of preventing service advertising information from being propagated through the router. There are three primary reasons to use SAP filters:

Note: None of these reasons explicitly mentions security. SAP filters cannot protect a service. All that SAP does is provide a name-to-address translation for services. If a potential intruder knows the address of the service, blocking its advertisement via SAP filters does not protect the service.

 The SAP filter is based on a maximum hop count for a particular service, or group of services. The router accepts into the SAP table only service advertisements it receives with the specified hop count (or less). The router uses and re-advertises only those services in the SAP database.

Note: The router allows you to enter service names in seven-bit ASCII only. Some service names use binary data in violation of Novell SAP specifications. You cannot filter those services by name.

A SAP filter can apply to all services of a type. Novell assigns four-digit hexadecimal type numbers for each type of service. Alternately, a SAP filter can apply to one particular service of a type. You do this by specifying the name of the service.

A SAP type can only have several filters for a specific name, or one (wildcard) filter for all names.

Creating SAP Filters

Follow these steps to configure SAP filters:

1. Enter add sap-filter at the IPX Config> prompt. You must specify several key entries that you normally find in the SAP broadcasts:

The following example shows the creation of a SAP filter against a specific print server. 

IPX config>add sap-filter
Enter maximum number of hops allowed [1]? 2
Enter service type [0]? 0047
Enter Service Name [ ]? rem-ptr1

This SAP filter causes the router to ignore SAP advertisements from any print server (service type 0047) named rem-ptr1 that is more than two hops away. The filter prevents the router from propagating advertisements that match these criteria.

2. Enter enable sap-filter at the IPX Config> prompt to enable the filter. 

IPX config> enable sap-filter

Determining the Service Type for a SAP Filter

 To determine the SAP type for a filter you want to establish, follow these steps.

1. At the * prompt, enter monitor. Then, at the Monitor> prompt, enter protocol ipx.

At the IPX> prompt enter slist all. Note the entry for the service(s) you want to filter. 

SAP entries:  active: 1   pre-allocated: 4000   in-use: 3
State Typ Service Name         Hops   Age        Net /   Node     / Sock
SAP 0004 SABRE2                 1    0:30    2CBF1D4E/000000000001/0451
2. At the * prompt, enter config. Then, at the Config> prompt, enter protocol ipx. Add the appropriate SAP filter and the appropriate hop count for the service you want to filter.

3. After creating the filter, restart the router.

4. If you have successfully filtered a service, the router no longer lists it. Enter slist at the IPX> prompt to check that the service is not listed.

IPX Commands

 Table 4 lists and defines the IPX configuration and monitoring commands.

Press Space twice after you type a command to display the available parameters for each command. Enter help for information about using the command line interface.

[C] means the command is available at the IPX Config> prompt.

[M] means the command is available at the IPX> prompt.

Table 4 IPX Commands

Command Function
Add [C] Adds access control for IPX packets and filters, broadcast and IPX WAN circuits, static RIP routes, SAP filters and static entries, and X.25 call destinations.

Access-controls [M] Lists the status of IPX access controls and a count of how many times the router follows each control statement.

Clear-config [C] Deletes all definitions of a certain category so that you do not have to remove them individually.

Clear-counters [M] Clears the IPX counters.

Delete [C] [M] At the configuration prompt, deletes individual parameters. At the monitoring prompt, deletes entries from the keepalive table.

Disable [C] [M] At the configuration prompt, globally disables access controls, IPX, static routes, and SAP filters. At the monitoring prompt, globally disables IPX and disables specific IPX circuits, IPX over PPP, and keepalive filtering.

Dump [M] Displays the contents of the current IPX RIP routing tables.

Enable [C] [M] At the configuration prompt, enables access controls, IPX, static routes, and SAP filters. At the monitoring prompt, globally enables IPX and enables specific IPX circuits, IPX over PPP, and keepalive filtering.

Filter-lists [C] [M] Displays the prompts that allow you to configure and monitor IPX circuit-based filters.

Frame [C] Specifies the data link format for Ethernet, Token Ring, and FDDI interfaces.

Ipxwan [M] Lists configuration information about IPX running over a WAN interface using PPP.

Keepalive [M] Shows status of keepalive filtering on each circuit and displays the status of each active client-server connection.

List [C] [M] Displays the current IPX configuration.

Move [C] Changes the line numbers set when adding access control.

Nlsp [C] Provides access to the NLSP Config> prompt where you can enter configuration settings for NLSP.

Nlsp-list [M] Displays NLSP area addresses, neighbors, and all or part of the link state database.

Ping [M] Sends ping packets to test reachability and routing.

Route [M] Displays information on how a router routes to a given IPX network.

SAP-filters [M] Lists the current SAP filters and the state of each filter.

Set [C] Sets global routing parameters, memory sizes, router name, and internal network number.

Shutdown [M] Carries out a Novell-style shutdown of IPX.

Slist [M] Displays the entire SAP routing table or part of it.

Add [C]

Adds access controls, broadcast and IPX WAN circuits, static routes, global IPX SAP filters, static SAP entries, and X.25 call destinations to your IPX configuration.

Syntax: add

access-control
bcastcircuit
ipxwancircuit
route-static
sap-filter
sap-static
x25calldestination

access-control

 Adds access control lists to your IPX configuration. The access control list is an ordered set of entries that the router uses to filter packets. Each entry is inclusive or exclusive and has source and destination network numbers, host addresses, and socket ranges.

When the router receives a packet for the IPX protocol, and you enable IPX access controls, the router checks the packet against network/address/socket pairs in the access control list. If there is no match, the router drops the packet. If there is a match, and the entry is inclusive, the router receives the packet and, if it matches the rest of the criteria, forwards the packet. If the matching entry is exclusive, the router drops the packet.

After you use the add access-control command to create an access control list, enable the access controls by entering enable access-controls. Use the move command to change the order of the access-control list.

Note: If you do not enable reception of RIP (socket 453 hexadecimal) or SAP (socket 452 hexadecimal) packets, the IPX forwarder does not function.

Example: add access-control

Enter type [E]? i
Destination network number (in hex) [0]? 0
Destination host number (in hex) []? 0
Starting destination socket number in hex [0]? 0
Ending destination socket number in hex [0]? FFF
Source network number in hex [0]? 0
Source host number (in hex) []? 0
Starting source socket number in hex [0]? 452
Ending source socket number in hex [452]? 453
Type

 Identifies whether the router receives or drops packets. Enter I for include. This causes the router to receive the packet and to forward it if it matches the defined access control entry.

Enter E for exclude. This causes the router to discard the packets.

Destination network number

 Network number of the destination in hexadecimal. Zero (0) means all networks.

Destination host number

 Host number on the destination network in hexadecimal. Zero (0) means all hosts on the network.

Starting and Ending destination socket number

 Two hexadecimal numbers between 0 (zero) and FFFF that specify an inclusive range of destinations.

Source network number

Network number of the source. Enter the network number in hexadecimal. Zero (0) means all networks.

Source host number

 Host number of the source network. Enter the host number in hexadecimal. Zero (0) means all hosts on the network.

Starting and Ending source socket number

 Two hexadecimal numbers between zero (0) and FFFF that specify an inclusive range of sources.

bcastcircuit

Defines and sets the configurable items for an IPX broadcast circuit. You can define a broadcast circuit over interfaces in which the underlying media provide a broadcast capability to all the other IPX nodes on the circuit.

You can define IPX broadcast circuits to run over LAN interfaces, such as Ethernet, Token Ring, and FDDI.

You can also define an IPX broadcast circuit to run over PPP, Frame Relay, and X.25. For purposes of interoperability with earlier releases of OpenROUTE software, you can use an IPX broadcast circuit over PPP, Frame Relay, and X.25 to connect to routers that are not running IPX WAN.

Notes:

Example: add bcastcircuit

Which interface [0]?
IPX enabled on this circuit (y/n) [y]?
IPX network number (00000001-FFFFFFFD) [0]? 1

Continue with expert config questions?(Yes or [No]): y
Enter new value, or <ENTER> to accept current value,
On most numeric questions, enter 0 to set back to standard IPX default.

NLSP Priority for becoming designated router (1-127) [64]?
NLSP Cost default override, 0 = no override (1-63) [0]?
NLSP MTU, in bytes, 0 = circuit default maximum (576-4200) [0]?
NLSP maximum packets per second (1-100) [18]?
NLSP Hello interval, in secs, 0 = use globals default (1-600) [0]?
NLSP Hello HoldTimeMultiplier, 0 = use globals default (2-20) [0]?
NLSP multicast address usage (y/n) [y]?
NLSP enabled (y/n) [y]?
RIP routing options, 1=off, 2=on, 3=auto (1-3) [3]?
RIP interpacket gap, in milliseconds (10-10000) [55]?
RIP periodic update interval, in minutes (1-1440) [1]?
RIP aging multiplier (2-10000) [4]?
RIP maximum packet size (40-4032) [432]?
RIP ticks default override, 0 = no override (1-20000) [0]?
SAP routing options, 1=off, 2=on, 3=auto (1-3) [3]?
SAP interpacket gap, in milliseconds (10-10000) [55]?
SAP periodic update interval, in minutes (1-1440) [1]?
SAP aging multiplier (2-10000) [4]?
SAP maximum packet size (96-4128) [480]?
DISABLE SAP reply to get nearest server (y/n) [n]?
  The purpose of this value is to allow the adjustment of the
  split-horizon behavior of IPX on non-IPXWAN Frame Relay interfaces,
as needed.  Otherwise, it is recommended to not adjust this value.
Split-horizon, 0=heuristic, 1=enabled, 2=disabled (0-2) [1]?           
NetBIOS forwarding enabled (y/n) [y]?
Split-horizon, 0=heuristic, 1=enabled, 2=disabled (0-2) [1]?
Enable keepalive filtering (y/n) [n]?
NetBIOS forwarding enabled (y/n) [y]?
IPX enabled on this circuit

 Specifies whether or not the IPX circuit is enabled. Allows you to quickly turn off and on an IPX broadcast circuit definition, eliminating the need to fully delete and add the definition.

IPX network number

 You must specify a nonzero IPX network number for the broadcast circuit. It should be unique among the other IPX network numbers in your internet.

All IPX routers and servers on this IPX broadcast circuit must have the IPX network number for the circuit set to the same value.

Continue with expert questions

 Normally, you answer No here and you are finished. If you answer Yes, the software asks you many advanced configuration questions, but rarely do you need to adjust these items.

Enter a new value, press Enter to accept the current value, or enter 0 (zero) to set the item back to its default value.

NLSP priority for becoming designated router

 The priority of this router to become the NLSP designated router on this broadcast circuit.

To force this router to always become and remain the designated router, set the NLSP priority to a large value and keep other routers at the default of 64. Nx Networks recommends setting a value of 100 for the designated router.

When an NLSP router elects itself designated router, it raises its priority by 20.

NLSP cost default override values

 Usually, you should enter 0 (zero), which causes the NLSP cost to default according to the default cost table that assigns a number from 1 to 63 based on the throughput of the circuit. See Table 1.

You can override the default NLSP cost, which is the most important factor in NLSP routing. You would do this to force NLSP to route in a way that the default cost for the circuit does not do. Reasons you would override the cost would be to

  • Force two paths to equal costs so that parallel load-sharing routing is done over them.

  • Force a path to be less cost than another so that one path is essentially a backup for the other.

This item is for expert fine tuning of routing, and you should not use it unless the network is already up and running. A change of this nature probably involves a coordinated change across several routers.

NLSP MTU

 The maximum size, in bytes, that the router supports locally on this circuit for NLSP Hello frames. Includes the IPX header, but not the data-link header or trailer.

The default automatically tries to use the maximum MTU that the underlying circuit supports. The software automatically negotiates the value downward among the routers on the broadcast circuit.

There should not be any reason to change this parameter except for an interoperability or workaround situation.

NLSP maximum packets

 The maximum rate, in packets per second, at which the router can send consecutive NLSP LSP packets or consecutive CSNP packets on this circuit. You may want to adjust this value to be lower if the rate is too fast for the receiving routers or is consuming too much of the circuit throughput.

The router uses the lower value in packets per second, and the calculation of circuit throughput/10000 bps, as the packet rate for sending consecutive LSP or CSNP packets. Since there is already an automatic adjustment in the rate for low throughput circuits, it may not be necessary to manually lower this value.

NLSP Hello interval

 The interval, in seconds, between NLSP Hello packets on this circuit. If 0, use the global default value that BcastHelloInt specifies under the set globals command at the NLSP config> prompt.

NLSP Hello HoldTimeMultiplier

 A number constant used in calculating the holding time in the Hello packet. The holding time is calculated as the HoldTimeMultiplier times the value of the NLSP Hello interval. The holding time is the length of time after which the receiving router considers the sending router as no longer present, assuming it receives no more Hello packets.

If 0, use the global default value HoldTimeMultiplier specifies under the set globals command at the NLSP Config> prompt.

NLSP multicast address

 When NLSP sends to all routers on the broadcast circuit, this value specifies if NLSP uses a multicast MAC address or the broadcast address.

Always specify Yes to multicast because multicast is more efficient than broadcast. Additionally, NLSP routers automatically negotiate back to using the broadcast address if one of the other routers does not have multicast capabilities.

If you select No, this router only uses the broadcast address. This can be used as a workaround to interoperate with another NLSP router with a multicast problem.

NLSP enabled

 Normally, you want to enable NLSP. The default strategy of the broadcast circuit running NLSP, combined with the ability to automatically turn on RIP if the software detects any RIP routers on the broadcast circuit, works very well.

However, there may be situations where you enable NLSP globally, but you want to make sure a certain broadcast circuit only runs RIP and never sends or receives any NLSP packets.

One example where this may be useful is when you are trying to minimize traffic on an IPX broadcast circuit over a WAN interface. By not sending NLSP packets, you save bandwidth, and a dial-on-demand circuit can come down more often.

RIP routing options

 RIP routing indicates whether or not the router sends and receives RIP routing information over this circuit.

  • Off means do not run RIP.

  • On means run RIP.

  • Auto (automatic) is the default and best choice.

RIP does not run unless there are other RIP routers on the broadcast circuit that need RIP. Auto RIP routing is initially off and the router does not send periodic RIP packets unless it first detects another RIP router on the circuit. If the RIP routers are down or removed, RIP automatically stops.

The router always responds to end-station RIP requests regardless of the RIP routing setting.

RIP interpacket gap

 The gap, in milliseconds, between RIP packets. The default is the Novell default of 55. The router's timing capabilities limit the accuracy of the gap.

Changing the gap to a larger value reduces the

  • overall rate of circuit bandwidth consumption during a sequence of RIP packets.

  • rate of RIP packets for the convenience of the other IPX routers on the circuit.

RIP periodic update interval

 The RIP periodic update interval, in minutes. Changing the update interval to a higher value reduces the amount of periodic RIP packet traffic from the circuit.

As a general rule, you should configure all IPX routers on the circuit in the same way.

RIP aging multiplier

 The holding multiplier controls how the router ages out information it receives in RIP packets. Usually, the aging multiplier is the value 3 or 4 on an IPX router. Calculate the RIP age-out time as

RIP periodic update interval x the RIP aging multiplier = RIP age-out time

One reason for changing the aging multiplier to a higher value is to provide a higher age-out time if your RIP routes are prematurely aging out too fast.

RIP maximum packet size

 The size, in bytes, of RIP packets sent on this circuit. Calculate the standard value as

32 + (50 RIP entries x 8 bytes per entry) = 432

Do not change this value (either higher or lower) unless there is a very special reason related to circuit bandwidth. Other vendor's routers may not support values higher than the standard value.

The maximum MTU size the underlying circuit supports automatically limits the RIP packet size.

RIP ticks default override

 Normally, you want the default of 0 (zero), which allows IPX to perform the standard calculation of ticks for this circuit automatically.

If set to nonzero, the automatically calculated tick value for this circuit is overridden by the nonzero value. Two reasons for overriding the default value for the ticks are to force

  • Two RIP paths to equal ticks so that parallel load-sharing routing is done over them.

  • One RIP path to be less cost than another.

This item is for expert fine tuning of routing and should not be attempted unless the network is already up and running. Any change to the default setting probably involves a coordinated change across several routers.

SAP routing options

 SAP routing indicates whether the router sends or receives SAP routing information over this circuit.

  • Off means do not run SAP.

  • On means run SAP.

  • Auto (automatic) is the default and best choice.

SAP is not run unless there are other SAP routers on the broadcast circuit that need SAP. SAP routing is initially Off and the router does not send periodic SAP packets unless it first detects another SAP router on the circuit. If the SAP routers are down or removed, SAP stops automatically.

The router always responds to end-station SAP requests regardless of the SAP routing setting.

Auto SAP detection is tied to auto RIP detection; that is, auto SAP is on as long as auto RIP is on.

SAP interpacket gap

 Similar to RIP interpacket gap, but for SAP packets.

SAP periodic update interval

 Similar to RIP periodic update interval, but for SAP packets.

SAP aging multiplier

 Similar to RIP aging multiplier, but for SAP packets.

SAP maximum packet size

 The size, in bytes, of SAP packets the router sends on this circuit. Calculate the standard value as

32 + (7 SAP entries x 64 bytes per entry) = 480.

Do not change this value (either higher or lower) unless there is a very special reason related to circuit bandwidth. Other vendor's routers may not support higher than the standard value.

The maximum MTU size the underlying circuit supports automatically limits the SAP packet size.

Disable SAP reply to get nearest server

 Specifies whether or not the router responds to get-nearest-server requests on this circuit.

This parameter lets you adjust the split-horizon behavior of IPX on non-IPX WAN Frame Relay interfaces as needed. Otherwise, Nx Networks does not recommend that you adjust this value.

Split-horizon

 Specifies whether or not to use the split-horizon rule for RIP and SAP routing broadcasts.

NetBIOS forwarding enabled

 Although the default is Yes, you may disable the handling of NetBIOS packets, also referred to as Type 20 packets, on this circuit. If No, the router does not receive or send NetBIOS packets on this circuit.

A reason for disabling NETBIOS forwarding is that you may want to stop NetBIOS packets from going over a circuit and using unnecessary circuit bandwidth if you know that this part of the IPX internet does not require NetBIOS capabilities.

ipxwancircuit

Prompts you for configurable items for an IPX WAN circuit. An IPX WAN circuit defines a point-to-point WAN connection that has an IPX router on each end of the WAN connection.

Figure 3 IPX WAN Circuit

The IPX WAN circuit can physically map to an interface running PPP, an individual Frame Relay DLCI, an X.25 PVC or SVC, or an IP Relay circuit.

The IPX WAN circuit, which adheres to the Novell standard for WANs, performs an IPX WAN negotiation before the router can forward any IPX data traffic on the circuit. The key items negotiated by IPX WAN are

Example: add ipxwancircuit

prompting for the involved circuit...
Enter interface number, or 9999 for IP Relay [0]?
 Note: A circuit name is required to further identify
 the individual Frame Relay, X.25, or IP Relay IPXWAN circuit.
  For Frame Relay, this name is defined under FR Config>add perm.
  For X.25, this name is defined under IPX Config>add X25CallDestination.
  For IP Relay, this name is defined under IP Config>add hostname.

Circuit name []? ipxwan
IPX enabled on this circuit (y/n) [y]?
Use client-router routing (y/n) [n]?
Use static routing (y/n) [n]?
NLSP routing acceptable (y/n) [y]?
Unnumbered RIP routing acceptable (y/n) [y]?
RIP routing acceptable (y/n) [y]?
IPX network number (00000001-FFFFFFFD) [0]? 1

Continue with expert config questions?(Yes or [No]):y
Enter new value, or <ENTER> to accept current value,
On most numeric questions, enter 0 to set back to standard IPX default.

NLSP Cost default override, 0 = no override (1-63) [0]?
NLSP IPXWAN delay default override, in milliseconds,
  0 = use IPXWAN calculated default (1-1000) [0]?
NLSP IPXWAN throughput default override, in bits per sec,
  0 = use IPXWAN calculated default (1-100000000) [0]?
NLSP MTU, in bytes, 0 = circuit default maximum (576-4200) [0]?
NLSP maximum packets per second (1-100) [18]?
NLSP Hello interval, in secs, 0 = use globals default (1-20000) [0]?
NLSP Hello HoldTimeMultiplier, 0 = use globals default (2-20) [0]?
RIP interpacket gap, in milliseconds (10-10000) [55]?
RIP periodic update interval, in minutes (1-1440) [1]?
RIP aging multiplier (2-10000) [4]?
RIP maximum packet size (40-4032) [432]?
RIP ticks default override, 0 = no override (1-20000) [0]?
SAP interpacket gap, in milliseconds (10-10000) [55]?
SAP periodic update interval, in minutes (1-1440) [1]?
SAP aging multiplier (2-10000) [4]?
SAP maximum packet size (96-4128) [480]?
DISABLE SAP reply to get nearest server (y/n) [n]?
Enable keepalive filtering (y/n) [n]?
NetBIOS forwarding enabled (y/n) [y]?
Circuit name

 If the router requires a circuit name, the prompt for the circuit name appears. The router requires a circuit name to further identify the individual Frame Relay, X.25, or IP Relay IPX WAN circuit.

You define this name in

  • Frame Relay using add permanent at the FRMGR Config <WAN> prompt.

  • X.25 using add X25calldestination at the X.25 Config> prompt.

  • IP Relay using add hostname at the IP Config> prompt.

The circuit name is limited to 23 characters.

IPX enabled on this circuit

 Specifies whether or not you want to enable the IPX circuit. It conveniently lets you quickly turn off and on an IPX broadcast circuit definition, eliminating the need to fully delete and add the definition.

Client-router routing

 The default is No. Answer Yes if client-routing is acceptable. If Yes, this means that the IPX machine on the other end of the IPX WAN circuit must be a client and not a router. If Yes, none of the other routing questions are relevant and the software skips them.

Static routing

 The default is No. Answer Yes if static routing is acceptable. If Yes, this means that you want no routing protocol at all to run over the IPX WAN circuit, that is, no RIP or SAP. If Yes, none of the other routing questions are relevant and the software skips them.

NLSP routing

 The default is Yes. Answer Yes if NLSP routing is acceptable during IPX WAN negotiation.

Even if this value is Yes, it is ignored and is always treated as if it is No unless you enable it globally. This is done so that, in general, the only thing you need to do to switch back and forth from RIP routing and NLSP routing is to enable or disable NLSP globally.

During negotiation, if there is a choice, the router gives priority to NLSP over unnumbered RIP and numbered RIP.

Unnumbered RIP routing

 The default is Yes. Answer Yes if unnumbered RIP is acceptable during IPX WAN negotiation.

During negotiation, if there is a choice, the router gives priority to unnumbered RIP over numbered RIP.

RIP routing acceptable

 The default is Yes. Answer Yes if numbered RIP is acceptable during IPX WAN negotiation.

IPX network number

 The default is 0 (zero). The only reason to assign an IPX network number is to run numbered RIP and nothing else. Otherwise, you can let the other router assign the network number. If the routers negotiate unnumbered RIP, the number is always 0 (zero) anyway.

If you selected client-router routing, you must enter a network number.

Expert config questions

 Usually, you answer No here and you are done. If you answer Yes, the software asks you many advanced configuration questions, but rarely do these items need adjusting.

NLSP cost default override

 See NLSP cost default override values.

This item is for expert fine tuning of routing and you should not use it unless the network is already up and running. Any change of this nature probably involves a coordinated change across several routers.

NLSP IPXWAN throughput default override

 The default is 0 (zero), which means NLSP uses the IPX WAN calculated throughput value. You can override this value if necessary. Throughput is the second most important criteria in NLSP routing after NLSP cost.

This item is for expert fine tuning of routing and you should not use it unless the network is already up and running. Any change of this nature probably involves a coordinated change across several routers.

NLSP IPXWAN delay default override

 The default is 0 (zero), which means NLSP uses the IPX WAN calculated delay value. You can override this value if necessary. Delay is the third most important criteria in NLSP routing, after NLSP cost and throughput.

This item is for expert fine tuning of routing and you should not use it unless the network is already up and running. Any change of this nature probably involves a coordinated change across several routers.

NLSP MTU

 See NLSP MTU.

NLSP maximum packets

 See NLSP maximum packets.

NLSP Hello interval

 The interval, in seconds, between NLSP Hello packets on this circuit. If 0 (zero), use the global default value that nonBcastHelloInt specifies under the set globals command at the NLSP Config> prompt.

You can adjust the Hello timer value to fairly high values to reduce the possibility of dial-on-demand circuits unnecessarily coming up.

NLSP HoldTimeMultiplier

 A number constant used in calculating the holding time sent in the Hello packet. The holding time is the length of time after which the receiving router considers the sending router as no longer present, assuming it receives no more Hello packets. The holding time is calculated as this number times the value of the NLSP Hello Interval.

If 0 (zero), the router uses the global default value specified under the set globals command.

The defaults should always work; however, HelloTimer and HoldTimeMultiplier give complete control, if needed, of the Hello protocol on a per circuit basis.

Disable SAP reply

 See Disable SAP reply to get nearest server.

Enable keepalive filtering

 The default is No. If Yes, you enable keepalive filtering.

NetBIOS forwarding enabled

 See NetBIOS forwarding enabled.

If you specify either numbered RIP or unnumbered RIP as an allowed protocol, the software also asks the following questions. See the discussion of these options under the add bcastcircuit command. 

RIP interpacket gap, in milliseconds (10-10000)[55]?
RIP periodic update interval, in minutes (1-1440) [1]?
RIP aging multiplier (2-10000) [4]?
RIP maximum packet size (40-4032) [432]?
RIP ticks default override, 0 = no override (1-20000) [0]?
SAP interpacket gap, in milliseconds (10-10000)[55]?
SAP periodic update interval, in minutes (1-1440) [1]?
SAP aging multiplier (2-10000) [3]?
SAP maximum packet size (96-4128) [480]?

route-static

 Defines an IPX static RIP routing entry.

Example: add route-static

IPX net address: (00000001-FFFFFFFE) [0]?
<prompting for the involved circuit...>

IPX node address, in hex: [000000000001]?
Ticks: (0-30000) [0]?
Hops: (0-14) [0]?
IPX net address

 Enter the IPX network number for which you wish to define a static route. Use the special value of 0xFFFFFFFE to mean the default route.

Circuit

 Enter the circuit over which the IPX network is reachable.

IPX node address

 Enter the IPX node address of the next hop router, residing on the circuit indicated above, through which the IPX network is reachable.

For IPX WAN circuits, the IPX node address of the next hop router is irrelevant and you may enter any value. Nx Networks suggests that you use 0x000000000001.

Ticks

 The static route competes among other routes on the traditional IPX best-path basis that uses ticks as the main criterion. Therefore, if you want this route to always be present, use 0 (zero) ticks. If you want the route to be secondary to a dynamically learned route, use a larger value such as 1000.

Hops

 Enter a value that approximates the actual number of hops to the IPX network; otherwise, just use 0 (zero).

sap-filter

Enables you to determine the number of hops that are reasonable for a service. You can configure IPX SAP filters to ignore certain entries in SAP advertisements. This limits the size of the SAP database, which could be necessary due to size limitations in older versions of NetWare file servers. It also limits the amount of SAP data sent across WAN links.

SAP filters are a global ordered list of filter entries. Each filter entry has a maximum hop count, a service type, and an optional service name. When the router receives a SAP packet, it compares each SAP entry with the filter list. If the SAP entry matches an entry in the filter list, the router does not enter it into the local SAP database. If there is no match, the router accepts the SAP entry.

The following example displays any SAP advertisements for the Lotus Notes server, NOTES-CHICAGO, at more than two hops.

After you add filters, you need to enable them by entering enable sap-filters.

Example: add sap-filter

Maximum number of hops allowed [1]? 2
Service type in hex [4]? 039B
Optional service name []? NOTES-CHICAGO
Hops

 Maximum number of hops permitted for the service. The range is 0 to FFFF.

Service type

 Numeric service class. Enter a two-byte number. Enter slist at the IPX> prompt to see a list of service types.

Service name

 Identifies a particular function that the server provides. In general, you do not need to enter anything in this field. If you do specify a value, enter a name of up to 48-characters.

sap-static

Defines an IPX static SAP entry.

Example: add sap-static

Sap type: (00000000-0000FFFF) [0]?
SAP name []?

<prompting for the involved circuit...>

SAP details:
IPX net address: (00000001-FFFFFFFE) [0]?
IPX node address, in hex: [000000000001]? 
IPX socket: (00000000-0000FFFF) [0]?

Hops: (0-14) [0]?
SAP type

 Type of the SAP for which you wish to define a static route.

SAP name

 Name of the SAP for which you wish to define a static route. This name is case-sensitive.

Circuit

 Circuit over which the SAP is reachable.

SAP details

 The Novell location of the SAP, that is, its IPX network, node, and socket numbers.

Hops

 The hop value for the SAP route. The static route competes among other routes on the traditional IPX best-path basis that uses hops as the main criterion. Therefore, if you want this route to always be present, use 0 (zero) hops. If you want the route to be secondary to a dynamically learned route, use a larger value, such as 8.

x25calldestination

Creates X25CallDestination definitions. You must create an X25CallDestination for each IPX WAN X.25 circuit to further define what type of X.25 circuit is involved and its associated DTE address.

Example: add X25calldestination

X.25 circuit name []?
IPX X25 circuit type (PVC/INSVC/OUTSVC) [PVC]?
IPX DTE Address []?
X.25 circuit name

 Must match the circuit name used in the corresponding IPXWANCircuit definition under the add ipxwancircuit command.

IPX X.25 circuit type

 One of the following X.25 circuit types:

PVC— A Permanent Virtual Circuit (PVC) that remains active whenever the interface is active.
INSVC— A Switched Virtual Circuit (SVC) that listens for an incoming call-request.
OUTSVC— A Switched Virtual Circuit that initiates an outbound call-request.
You must choose either INSVC or OUTSVC. The SVC cannot do both at the same time. If you need both, you must define two separate IPXWANCircuit and X25CallDestination definitions.

IPX DTE address

 An X.121 DTE address, from 1 to 15 digits of 0-9, to identify the specific destination DTE.

PVC— Must match a configured PVC under X.25 Config>.
OUTSVC— Remote DTE address with which you want to establish a call connection.
INSVC— Remote DTE from which you want to receive an incoming call request.

The following are helpful hints for definitions that you must make at the X.25 Config> prompt:

Access-controls [M]

 Displays the access controls. These are the older-style access controls that effectively serve as an IPX header input filter mechanism. You may only configure the access controls globally and apply them to all incoming IPX packets on all circuits.

Syntax: access-controls

Example: access-controls

Access Control currently disabled
Access Control list is empty.

Clear-config [C]

 Deletes all static routes or SAP static entries.

Syntax: clear-config

route-static
sap-static

route-static

 Deletes all static routes.

Example: clear-config route-static

sap-static

Deletes all SAP static entries.

Example: clear-config sap-static

Clear-counters [M]

Zeroes all IPX counters, which include all those listed under the list counters command. This can be useful when analyzing a problem or performance.

Syntax: clear-counters

Example: clear-counters

Delete [C] [M]

You can use delete at both the configuration and monitoring prompts, as described in the next sections.

Delete [C]

Deletes selected items.

Note: This command's options are the same as those for the add command.

Syntax: delete

access-control
bcastcircuit
ipxwancircuit
route-static
sap-filter
sap-static
x25calldestinastion

access-control

 Discards the access control statement that matches the line number you enter. To display the current line numbers, enter the list access-controls command.

Example: delete access-control

Enter index of access control to be deleted [1]? 1
  # T Dest Net         Host  Sck  Sck   Src Net         Host  Sck  Sck
  1 I        0 000000000000    0  FFF         0 000000000000  452  453
Are you sure this is the record you want to delete(Yes or [No]): yes
Deleted

bcastcircuit

 Removes the selected broadcast circuit definition.

Example: delete bcastcircuit

Which interface [0]? 
Entry deleted

ipxwancircuit

 Removes the selected IPXWANCircuit definition.

Example: delete ipxwancircuit

<prompting for the involved circuit...>
Entry deleted

route-static

 Removes the static route definition.

Example: delete route-static

IPX net address: (00000001-FFFFFFFE) [0]? 111
<prompting for the involved circuit...>
IPX node address, in hex: [000000000001]?
Entry deleted

sap-filter

 Discards the specified SAP filter. Before you delete a SAP filter enter list sap-filter to display the filter. You can then use the information to select the prompts under the delete sap-filter command.

Example: delete sap-filter

Maximum number of hops allowed [1]? 2 
Service type in hex []? 039B
Optional service name []? NOTES-CHICAGO 
Are you sure(Yes or [No]): yes
Deleted

sap-static

 Removes the SAP static route definition.

Example: delete sap-static

Sap type: (00000000-0000FFFF) [0]? 4
SAP name []? SABRE2
<prompting for the involved circuit...>
Entry deleted

x25calldestination

 Removes an X25CallDestination definition.

Example: delete x25calldestination

X.25 circuit name []? openroutepvc
Entry deleted

Delete [M]

 Allows you to clear a keepalive connection.

Syntax: delete

keepalive
Example: delete keepalive

Which Keepalive connection? [0]?
No such connection

Disable [C] [M]

 You can use disable for both configuring and monitoring as described in the next sections.

Disable [C]

At the IPX config> prompt, disables the selected item.

Syntax: disable

access controls
ipx
nlsp
route-static
sap-filter
sap-static

access-controls

 Globally disables access controls.

Example: disable access-controls

ipx

Globally disables the IPX forwarder.

Example: disable ipx

nlsp

Globally disables the NLSP protocol.

This is an extremely important command because it lets you quickly change the router from an NLSP router to a RIP router with one simple command.

Example: disable nlsp

route-static

Globally disables the static routes.

Example: disable route-static

sap-filter

Globally disables SAP filters.

Example: disable sap-filter

sap-static

Globally disables the SAP static routes.

Example: disable sap-static

Disable [M]

At the IPX> prompt, disables the circuit, static route, or static SAP route.

Syntax: disable

circuit
route-static
sap-static

circuit

 Dynamically brings down an IPX circuit so that IPX is no longer running over the circuit.

Example: disable circuit

<prompting for the involved circuit...>
Disabling circuit

route-static

 Dynamically disables static routes and removes any static routes currently in the routing table.

Example: disable route-static

<prompting for the involved route-static...>
Disabling route-static

sap-static

 Dynamically disables any SAP static routes and removes any SAP static routes currently in the SAP routing table.

Example: disable sap-static

<prompting for the involved sap-static...>
Disabling sap-static

Dump [M]

 Displays the contents of the current IPX routing tables.

Syntax: dump

all
direct
range
static

all

 Displays all the routing tables for IPX with the direct routes listed first, followed by all other routes in ascending network order.

Example: dump all

Routing entries:  active: 4   pre-allocated: 128   in-use: 4
Type Dest net Hops Ticks Age(M:S) Next Hop              Circuit
Dir  56785678 0    1        0:00  56785678/000000000001 internal
Dir  00111111 0    1        0:00  00111111/00009318C41E 2(Eth/2)
Dir  00222222 0    1        0:00  00222222/00009318C49E 3(Eth/3)
RIP  34343434 1    2        0:30  00111111/0000E8C411A3 2(Eth/2)
NLSP 34343434 1    2        0:30  00222222/000093843808 3(Eth/3)
Routing entries

 Summarizes how many routing table entries are active, how many have been pre-allocated, and how many are in-use.

Active— The routing entry is valid. The router is actively using the entry for routing.
Pre-allocated— The number of routing table entries exclusively reserved for the table at initialization.
In-use— The number of routing entries that the router is using. Usually the same as active.
Except for active, this is the same information that may also appear under the list memory configuration command.

Type

Dir— A direct route. There should be one of these for each directly attached IPX circuit that is ready to forward IPX traffic.
RIP— A route that the router has learned from the RIP protocol.
Stat— A statically configured route.
XRIP— A route that was learned from an NLSP Xroute. This means that NLSP learned this route from RIP originally.
L2— A route that was learned from a level-2 router. The concept of a level-2 router is obsolete. Novell is phasing it out, but it is still part of Novell certification tests.
NLSP— A route that was learned directly from an NLSP router.
dXXXX— Where XXXX is one of the above routes. Indicates that the route is in the process of being deleted and may briefly appear in the display.
" " — Used to repeat another line to show an additional parallel path to the same destination network.
Dest net

 Network destination of the route.

Hops

 The number of hops to the destination network.

Ticks

 The number of ticks to the destination network.

Age

 The time, in minutes and seconds, since this route entry was last updated or refreshed.

Next Hop

 An IPX network and node address. The meaning depends on the type of route.

  • For direct routes, it is the IPX network and node address of the directly attached circuit. Some direct routes have a network number of 0 (zero), which means that the direct route is an unnumbered network and has not been assigned a network number. Direct routes with a network number of 0 are not actually in the routing table because network 0 is not a legal routable destination; the software displays such networks for completeness so that you can clearly see all of the router's directly attached circuits in one convenient display.

  • For other routes, it is the IPX network and node address of the next hop router to which a router forwards a packet.

Circuit

 The circuit display name of an IPX circuit. The meaning depends on the type of route.

  • For direct routes, this is the circuit display name of the directly attached circuit.

  • For other routes, this is the circuit display name of the next hop router to which a router forwards a packet.

direct

Displays only the direct routes portion of the routing table.

Example: dump direct

Type Dest net Hops Ticks Age(M:S) Next Hop              Circuit
Dir  56785678 0    1        0:00  56785678/000000000001 internal
Dir  00222222 0    1        0:00  00222222/00009318C49E 3(Eth/3)
Dir  00333333 0    1        0:00  00333333/00009318C45E 4(Eth/4)
Dir  00111111 0    1        0:00  00111111/00009318C41E 2(Eth/2)
See the dump all command for detailed information.

range

Displays a subsection of the routing table based on a range of network addresses. This is an important capability when a router has a large routing table and listing the entire table is too tedious.

The following example shows the routing table for the networks from A0009-A000B.

Example: dump range

First IPX net: (00000000-FFFFFFFF) [0]? A0009
Last IPX net: (000A0009-FFFFFFFF) [A0009]? A000B
Type Dest net Hops Ticks Age(M:S) Next Hop              Circuit
RIP  000A0009 10   100      1:00  00111111/0000E8C411A3 2(Eth/2)
RIP  000A000A 1    10       1:00  00111111/0000E8C411A3 2(Eth/2)
RIP  000A000B 2    20       1:00  00111111/0000E8C411A3 2(Eth/2)
See the dump all command for detailed information.

static

Displays the static routes defined in the routing table.

Example: dump static

Type Dest net Hops Ticks Age(M:S) Next Hop              Circuit
Stat 00205333 0    1        0:00  00205333/000000000001 internal
Stat 00333444 0    1        0:00  00333444/0000C90103A8 5(TKR/1)
Stat 00000000 0    13       0:00  00000000/002053330000 2(X25/0):x25circ-in
Stat 00000000 0    13       0:00  00000000/002053330000 2(X25/0):x25circ-out
Stat 00000000 0    7        0:00  00000000/002053330000 1(PPP/0):<none>
See the dump all command for detailed information.

Enable [C] [M]

You can use enable for both configuring and monitoring as described in the next sections.

Enable [C]

Enables the selected item.

Syntax: enable

access-controls
ipx
nlsp
route-static
sap-filter
sap-static

access-controls

 Globally enables access controls.

Example: enable access-controls

ipx

Globally enables the IPX forwarder.

Example: enable ipx

nlsp

Globally enables the NLSP protocol.

This is an extremely important command because lets you quickly change the router from a RIP router to an NLSP router with one simple command.

Example: enable nlsp

route-static

Globally enables the static routes.

Example: enable route-static

sap-filter

Globally enables SAP filters.

Example: enable sap-filter

sap-static

Globally enables the SAP static routes.

Example: enable sap-static

Enable [M]

Interactively enables IPX on a circuit or enables a static route or a static SAP entry.

Syntax: enable

circuit
route-static
sap-static

circuit

 Dynamically brings up an IPX circuit so that IPX is running over it.

Example: enable circuit

<prompting for the involved circuit...>
Reread config memory for latest circuit values?(Yes or [No]):
Enabling circuit
The software asks whether or not you want the router to reread the configuration memory to obtain the latest circuit configuration for this circuit. If you allow this, you can dynamically change almost all circuit parameters, without restarting the router. Follow these steps:

1. Disable the circuit.

2. Change the circuit's configuration.

3. Enable the circuit.

It is possible that when you bring up the circuit, it may fail to initialize. This is usually due to configuration errors. If the circuit does not come up, display the IPX ELS messages to find the reason. Some possible reasons:

route-static

 Dynamically enables static routes. The router submits any static routes defined in configuration memory to the routing table. The static route becomes part of the routing table if it is a better route.

Example: enable route-static

sap-static

Dynamically enables SAP static entries.

Example: enable sap-static

Filter-lists [C] [M]

You can use filter-lists for both configuring and monitoring as described in the next sections.

Note: Since OpenROUTE 2.2, a filter now applies to an IPX circuit instead of strictly to an interface.

Filter-lists [C]

 Displays the prompts that let you configure IPX circuit filters. See IPX Filter Commands, for information on the commands available at these prompts.

Syntax: filter-lists

ipx
rip
router
sap

ipx

 Displays the prompt that lets you configure IPX circuit filters.

Example: filter-lists ipx

IPX IPX-List Config>

rip

 Displays the prompt that lets you configure RIP circuit filters.

Example: filter-lists rip

IPX RIP-List Config>

router

 Displays the prompt that lets you configure RIP Router circuit filters.

Example: filter-lists router

IPX Router-List Config>

sap

 Displays the prompt that lets you configure SAP circuit filters.

Example: filter-lists sap

IPX SAP-List Config>

Filter-lists [M]

 Displays the prompts that let you monitor IPX circuit filters. See IPX Filter Commands, for information on the commands available at these prompts.

Syntax: filter-lists

ipx
rip
router
sap

ipx

 Displays the prompt that lets you monitor IPX circuit filters.

Example: filter-lists ipx

IPX IPX-Lists>

rip

 Displays the prompt that lets you monitor RIP circuit filters.

Example: filter-lists rip

IPX RIP-Lists>

router

 Displays the prompt that lets you monitor RIP Router circuit filters.

Example: filter-lists router

IPX Router-Lists>

sap

 Displays the prompt that lets you monitor SAP circuit filters.

Example: filter-lists sap

IPX SAP-Lists>

Frame [C]

Specifies the packet format for IPX interfaces.

The default encapsulation formats are

Note: When there are incorrect or invalid configuration records, the router uses the default frame values.

 Syntax: frame

ethernet_II
ethernet_8022
ethernet_8023
ethernet_snap
token-ring
token-ring_snap
fddi
fddi_snap
Example: frame token-ring msb

Which interface [0]?
Ethernet_II

 Default of NetWare 4.0 and greater. Uses Ethernet version 2.0 protocol 81-37.

Ethernet_8022

 Uses Ethernet 802.3 with 802.2 SAP E0.

Ethernet_8023

 Default of pre-NetWare 4.0. Uses Ethernet 802.3 without any 802.2 header.

Ethernet_SNAP

 Nx Networks does not recommend using this encapsulation. Ethernet_SNAP encapsulation is not architecturally valid and it violates IEEE 802.1 (that is, Bridging Ethernet in IEEE 802 environment). There is no route caching performed on this encapsulation.

Token Ring MSB

 Standard 802.2 IPX header in MSB (Most Significant Bit) or noncanonical address bit ordering. The router builds outgoing packets with a three-byte 802.2 header, (0xE0,0xE0,0x03).

Token Ring LSB

 Same as Token Ring MSB except the router sends addresses in LSB (Least Significant Bit) format or canonical format.

Token Ring_SNAP MSB

 The router builds outgoing packets with an eight-byte 802.2/SNAP header, (0xAA,0xAA,0x03,0x00,0x00,0x00,0x81,0x37). The router sends source and destination addresses in MSB format or noncanonical format.

Token Ring_SNAP LSB

 Same as Token Ring_SNAP MSB except that the router sends addresses in LSB or canonical format.

FDDI

 Uses the standard 802.2 DSAP/SSAP of E0 for IPX.

FDDI_SNAP

 Uses the 802.2 with SNAP header for IPX.

Ipxwan [M]

Lists information for IPX WAN circuits.

Syntax: ipxwan

detailed
summary

detailed

 Lists detailed information about a specific IPX WAN circuit. If the IPX WAN circuit completed IPX WAN negotiation, details about the critical pieces of information, which IPX WAN has negotiated or calculated, appear.

Example: ipxwan detailed

prompting for the involved circuit...
Is the circuit based upon a normal router interface? [Yes]:
Which interface [0]? 2
 Note: A circuit name is only required if one needs to identify
 an individual IPXWAN circuit on a circuit-based network such as Frame
 Relay.
Circuit name of the circuit []? raleigh

Detailed information for IPXWAN circuit 1:raleigh
  State:                   Master
  Neighbor Name:           rbx250-1
  Negotiated Routing Type: Unnumbered RIP
  Network Number:          0
  RIP Link Delay:          990ms
  NLSP delay
    calculated:            66660us
    used:                  66660us
  NLSP throughput
    calculated:            62205b/s
    used:                  62205b/s
State

 Master, Slave, Negotiating, or Down. If the state is Master or Slave, the details of the negotiation appear. Otherwise, no information appears.

Neighbor Name

 The router name on the other end of the circuit.

Negotiated Routing Type

 One of four possible routing protocols for the IPX WAN circuit: RIP, unnumbered RIP, NLSP, static routing, or client routing.

Network Number

 The negotiated IPX network number for the IPX WAN circuit. If the negotiated routing protocol is unnumbered RIP, NLSP, or static routing, the negotiated network number is always 0 (zero).

RIP Link Delay

 The dynamically measured RIP delay in milliseconds. This number is important because the router uses it to calculate the ticks value for the circuit.

NLSP delay

 Only calculated and displayed if the negotiated protocol is NLSP. The IPX WAN calculated and used delay values, in microseconds, appear. The used value is the same as the calculated value unless the NLSP delay was manually configured; in this case, the used value is the manually configured value.

NLSP throughput

 Only calculated and displayed if the negotiated protocol is NLSP. The IPX WAN calculated and used values appear. The used value is the same as the calculated value unless the NLSP throughput was manually configured; in this case, the used value is the manually configured value.

summary

Lists a brief summary display of all IPX WAN circuits.

Example: ipxwan summary

Neighbor Name     State        Circuit
----------------  -----------  ----------------
rbx250-250333     Master       5(X25/0):x25circ-out
rbx250-250333     Master       5(X25/0):x25circ-in
<none>            Down         6(PPP/0):<none>
<none>            Negotiating  5(X25/0):x25pvc
.
N