|
|
This chapter describes how to configure Novell Internetwork Packet Exchange (IPX) and provides configuration examples. For a complete description of the IPX commands in this chapter, refer to the "Novell IPX Commands" chapter in the Cisco IOS AppleTalk and Novell IPX Command Reference publication. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
An IPX network address consists of a network number and a node number expressed in the format network.node.
The network number identifies a physical network. It is a 4-byte (32-bit) quantity that must be unique throughout the entire IPX internetwork. The network number is expressed as hexadecimal digits. The maximum number of digits allowed is eight.
The Cisco IOS software does not require that you enter all eight digits; you can omit leading zeros.
The node number identifies a node on the network. It is a 48-bit quantity, represented by dotted triplets of four-digit hexadecimal numbers.
If you do not specify a node number for a router to be used on WAN links, the Cisco IOS software uses the hardware MAC address currently assigned to it as its node address. This is the MAC address of the first Ethernet, Token Ring, or FDDI interface card. If there are no valid IEEE interfaces, then the Cisco IOS software randomly assigns a node number using a number that is based on the system clock.
The following example shows how to configure an IPX network address:
4a.0000.0c00.23fe
In this example, the network number is 4a (more specifically, it is 0000004a), and the node number is 0000.0c00.23fe. All digits in the address are hexadecimal.
To configure IPX routing, perform the tasks in the following sections:
See the "Novell IPX Configuration Examples" section at the end of this chapter for configuration examples.
You configure IPX routing by first enabling it on the router and then configuring it on each interface.
Optionally, you can route IPX on some interfaces and transparently bridge it on other interfaces. You can also route IPX traffic between routed interfaces and bridge groups, or route IPX traffic between bridge groups.
To configure IPX routing, perform the tasks in the following sections. The first two tasks are required; the rest are optional.
In IPX, a default route is the network where all packets for which the route to the destination address is unknown are forwarded.
Original Routing Information Protocol (RIP) implementations allowed the use of network -2 (0xFFFFFFFE) as a regular network number in a network. With the inception of NetWare Link Services Protocol (NLSP), network -2 is reserved as the default route for NLSP and RIP. Both NLSP and RIP routers should treat network -2 as a default route. Therefore, you should implement network -2 as the default route regardless of whether you configure NLSP in your IPX network.
By default, Cisco IOS software treats network -2 as the default route. You should ensure that your IPX network does not use network -2 as a regular network. If, for some reason, you must use network -2 as a regular network, you can disable the default behavior. To do so, see the "Adjusting Default Routes" section later in this chapter.
For more background information on how to handle IPX default routes, refer to the Novell NetWare Link Services Protocol (NLSP) Specification, Revision 1.1 publication.
The first step in enabling IPX routing is to enable it on the router. If you do not specify the node number of the router to be used on WAN links, the Cisco IOS software uses the hardware MAC address currently assigned to it as its node address. This is the MAC address of the first Ethernet, Token Ring, or FDDI interface card. If there are no valid IEEE interfaces, then the Cisco IOS software randomly assigns a node number using a number that is based on the system clock.
To enable IPX routing, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx routing [node] |
For an example of how to enable IPX routing, see the "IPX Routing Examples" section at the end of this chapter.
 |
CautionIf you plan to use DECnet and IPX routing concurrently on the same interface, you should enable DECnet routing first, then enable IPX routing without specifying the optional MAC node number. If you enable IPX before enabling DECnet routing, routing for IPX will be disrupted because DECnet forces a change in the MAC-level node number. |
After you have enabled IPX routing, you enable IPX routing on the individual interfaces by assigning network numbers to those interfaces.
You enable IPX routing on interfaces that support a single network or multiple networks.
When you enable IPX routing on an interface, you can also specify an encapsulation (frame type) to use for packets being sent on that network. Table 8 lists the encapsulation types you can use on IEEE interfaces and shows the correspondence between Cisco naming conventions and Novell naming conventions for the encapsulation types.
| Interface Type | Cisco Name | Novell Name |
|---|---|---|
Ethernet | novell-ether (Cisco IOS default) | Ethernet_802.3 |
Token Ring | sap (Cisco IOS default) | Token-Ring |
FDDI | Fddi_Snap |
The following sections describe how to enable IPX routing on interfaces that support a single network and on those that support multiple networks. You must perform one of the tasks to enable IPX routing on an interface:
A single interface can support a single network or multiple logical networks. For a single network, you can configure any encapsulation type. Of course, it should match the encapsulation type of the servers and clients using that network number.
To assign a network number to an interface that supports a single network, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx network network [encapsulation encapsulation-type] | Enable IPX routing on an interface. |
If you specify an encapsulation type, be sure to choose the one that matches the one used by the servers and clients on that network. See Table 8 for a list of encapsulation types you can use on IEEE interfaces.
For an example of how to enable IPX routing, see the "IPX Routing Examples" section at the end of this chapter.
When assigning network numbers to an interface that supports multiple networks, you must specify a different encapsulation type for each network. Because multiple networks share the physical medium, the Cisco IOS software is allowed to identify the packets that belong to each network. For example, you can configure up to four IPX networks on a single Ethernet cable, because four encapsulation types are supported for Ethernet. Remember, the encapsulation type should match the servers and clients using the same network number. See Table 8 for a list of encapsulation types you can use on IEEE interfaces.
There are two ways to assign network numbers to interfaces that support multiple networks. You can use subinterfaces or primary and secondary networks.
You typically use subinterfaces to assign network numbers to interfaces that support multiple networks.
A subinterface is a mechanism that allows a single physical interface to support multiple logical interfaces or networks. That is, several logical interfaces or networks can be associated with a single hardware interface. Each subinterface must use a distinct encapsulation, and the encapsulation must match that of the clients and servers using the same network number.
 |
NoteWhen enabling NLSP and configuring multiple encapsulations on the same physical LAN interface, you must use subinterfaces. You cannot use secondary networks. |
Any interface configuration parameters that you specify on an individual subinterface are applied to that subinterface only.
To configure multiple IPX networks on a physical interface using subinterfaces, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | interface type number.subinterface-number | |
Step2 | ipx network network [encapsulation encapsulation-type] | Enable IPX routing, specifying the first encapsulation type. |
To configure more than one subinterface, repeat these two steps. See Table 8 for a list of encapsulation types you can use on IEEE interfaces.
For examples of configuring multiple IPX networks on an interface, see the "IPX Routing on Multiple Networks Examples" section at the end of this chapter.
When assigning network numbers to interfaces that support multiple networks, you can also configure primary and secondary networks.
The first logical network you configure on an interface is considered the primary network. Any additional networks are considered secondary networks. Again, each network on an interface must use a distinct encapsulation and it should match that of the clients and servers using the same network number.
Any interface configuration parameters that you specify on this interface are applied to all the logical networks. For example, if you set the routing update timer to 120 seconds, this value is used on all four networks.
To use primary and secondary networks to configure multiple IPX networks on an interface, use the following commands in interface configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx network network [encapsulation encapsulation-type] | Enable IPX routing on the primary network. |
Step2 | ipx network network [encapsulation encapsulation-type] [secondary] |
To configure more than one secondary network, repeat as appropriate. See Table 8 for a list of encapsulation types you can use on IEEE interfaces.
|
NoteWhen enabling NLSP and configuring multiple encapsulations on the same physical LAN interface, you must use subinterfaces. You cannot use secondary networks. |
You can route IPX on some interfaces and transparently bridge it on other interfaces simultaneously. To enable this type of routing, you must enable concurrent routing and bridging. To enable concurrent routing and bridging, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
bridge crb | Enable concurrent routing and bridging. |
For more information about configuring integrated routing and bridging, refer to the "Configuring Transparent Bridging" chapter in the Cisco IOS Bridging and IBM Networking Configuration Guide.
Enhanced IGRP is an enhanced version of the Interior Gateway Routing Protocol (IGRP) developed by Cisco. Enhanced IGRP uses the same distance vector algorithm and distance information as IGRP. However, the convergence properties and the operating efficiency of Enhanced IGRP have improved significantly over IGRP.
The convergence technology is based on research conducted at SRI International and employs an algorithm referred to as the Diffusing Update Algorithm (DUAL). This algorithm guarantees loop-free operation at every instant throughout a route computation, and allows all routers involved in a topology change to synchronize at the same time. Routers that are not affected by topology changes are not involved in recomputations. The convergence time with DUAL rivals that of any other existing routing protocol.
Enhanced IGRP offers the following features:
Enhanced IGRP has four basic components discussed in the following sections:
Neighbor discovery/recovery is the process that routers use to dynamically learn of other routers on their directly attached networks. Routers must also discover when their neighbors become unreachable or inoperative. The router achieves neighbor discovery/recovery with low overhead by periodically sending small hello packets. As long as hello packets are received, a router can determine that a neighbor is alive and functioning. Once this status is determined, the neighboring devices can exchange routing information.
The reliable transport protocol is responsible for guaranteed, ordered delivery of Enhanced IGRP packets to all neighbors. It supports intermixed transmission of multicast and unicast packets. Some Enhanced IGRP packets must be sent reliably, and others need not be. For efficiency, reliability is provided only when necessary. For example, on a multiaccess network that has multicast capabilities (such as Ethernet) it is not necessary to send hellos reliably to all neighbors individually. Therefore, Enhanced IGRP sends a single multicast hello with an indication in the packet informing the receivers that the packet need not be acknowledged. Other types of packets (such as updates) require acknowledgment, which is indicated in the packet. The reliable transport has a provision to send multicast packets quickly when there are unacknowledged packets pending. This provision helps ensure that convergence time remains low in the presence of varying speed links.
The DUAL finite-state machine embodies the decision process for all route computations. It tracks all routes advertised by all neighbors. DUAL uses the distance information (known as a metric) to select efficient, loop-free paths. DUAL selects routes to be inserted into a routing table based on feasible successors. A successor is a neighboring router used for packet forwarding that has a least-cost path to a destination that is guaranteed not to be part of a routing loop. When there are no feasible successors but there are neighbors advertising the destination, a recomputation must occur. This is the process whereby a new successor is determined. The amount of time it takes to recompute the route affects the convergence time. Recomputation is processor-intensive. It is advantageous to avoid recomputation if it is not necessary. When a topology change occurs, DUAL will test for feasible successors. If there are feasible successors, it will use any it finds in order to avoid unnecessary recomputation.
The protocol-dependent modules are responsible for network layer protocol-specific tasks. They are also responsible for parsing Enhanced IGRP packets and informing DUAL of the new information received. Enhanced IGRP asks DUAL to make routing decisions, but the results are stored in the IPX routing table. Also, Enhanced IGRP is responsible for redistributing routes learned by other IPX routing protocols.
To enable IPX Enhanced IGRP, perform the tasks in the following sections. Only the first task is required; the remaining tasks are optional.
To create an IPX Enhanced IGRP routing process, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx router eigrp autonomous-system-number | Enable an Enhanced IGRP routing process. |
Step2 | network {network-number | all}
|
To associate multiple networks with an Enhanced IGRP routing process, you can repeat the preceding two steps.
For an example of how to enable Enhanced IGRP, see the "IPX Enhanced IGRP Example" section at the end of this chapter.
You might want to customize the Enhanced IGRP link characteristics. The following sections describe these customization tasks:
By default, Enhanced IGRP packets consume a maximum of 50 percent of the link bandwidth, as configured with the bandwidth interface subcommand. If a different value is desired, use the ipxbandwidth-percent command. This command may be useful if a different level of link utilization is required, or if the configured bandwidth does not match the actual link bandwidth (it may have been configured to influence route metric calculations).
To configure the percentage of bandwidth that may be used by Enhanced IGRP on an interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx bandwidth-percent eigrp as-number percent | Configure the percentage of bandwidth that may be used by Enhanced IGRP on an interface. |
For an example of how to configure the percentage of Enhanced IGRP bandwidth, see the "IPX Enhanced IGRP Bandwidth Configuration Example" section at the end of this chapter.
|
NoteAlthough adjusting the maximum hop count is possible, it is not recommended for Enhanced IGRP. We recommend that you use the default value for the maximum hop count of Enhanced IGRP. |
By default, IPX packets whose hop count exceeds 15 are discarded. In larger internetworks, this maximum hop count may be insufficient. You can increase the hop count to a maximum of 254 hops for Enhanced IGRP. To modify the maximum hop count, use the following command in global configuration mode:
You can adjust the interval between hello packets and the hold time.
Routers periodically send hello packets to each other to dynamically learn of other devices on their directly attached networks. Routers use this information to discover their neighbors and to discover when their neighbors become unreachable or inoperative.
By default, hello packets are sent every 5 seconds. The exception is on low-speed, nonbroadcast multiaccess (NBMA) media, where the default hello interval is 60 seconds. Low speed is considered to be a rate of T1 or slower, as specified with the bandwidth interface configuration command. The default hello interval remains 5 seconds for high-speed NBMA networks.
You can configure the hold time on a specified interface for a particular Enhanced IGRP routing process designated by the autonomous system number. The hold time is advertised in hello packets and indicates to neighbors the length of time they should consider the sender valid. The default hold time is three times the hello interval, or 15 seconds.
On very congested and large networks, 15 seconds may not be sufficient time for all routers to receive hello packets from their neighbors. In this case, you may want to increase the hold time. To increase the hold time, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx hold-time eigrp autonomous-system-number seconds |
To change the interval between hello packets, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx hello-interval eigrp autonomous-system-number seconds |
|
NoteDo not adjust the hold time without consulting with Cisco technical support. |
You might want to customize the exchange of routing and service information. The following sections describe these customization tasks:
By default, the Cisco IOS software redistributes IPX RIP routes into Enhanced IGRP, and vice versa.
To disable route redistribution, use the following command in IPX-router configuration mode:
| Command | Purpose |
|---|---|
no redistribute {connected | eigrp
autonomous-system-number | rip | static}
| Disable redistribution of RIP routes into Enhanced IGRP and Enhanced IGRP routes into RIP. |
For an example of how to enable redistribution of Enhanced IGRP and NLSP, see the "Enhanced IGRP and NLSP Route Redistribution Example" section at the end of this chapter.
Split horizon controls the sending of Enhanced IGRP update and query packets. If split horizon is enabled on an interface, these packets are not sent for destinations if this interface is the next hop to that destination.
By default, split horizon is enabled on all interfaces.
Split horizon blocks information about routes from being advertised by the Cisco IOS software out any interface from which that information originated. This behavior usually optimizes communication among multiple routers, particularly when links are broken. However, with nonbroadcast networks (such as Frame Relay and SMDS), situations can arise for which this behavior is less than ideal. For these situations, you can disable split horizon.
To disable split horizon, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
no ipx split-horizon eigrp autonomous-system-number | Disable split horizon. |
|
NoteSplit horizon cannot be disabled for RIP or SAP, only for Enhanced IGRP. |
To control which devices learn about routes, you can control the advertising of routes in routing updates. To control this advertising, use the following command in router configuration mode:
| Command | Purpose |
|---|---|
distribute-list access-list-number out [interface-name | | Control the advertising of routes in routing updates. |
To control the processing of routes listed in incoming updates, use the following command in router configuration mode:
| Command | Purpose |
|---|---|
distribute-list access-list-number in [interface-name] | Control which incoming route updates are processed. |
If IPX Enhanced IGRP peers are found on an interface, you can configure the Cisco IOS software to send SAP updates either periodically or when a change occurs in the SAP table. When no IPX Enhanced IGRP peer is present on the interface, periodic SAPs are always sent.
On serial lines, by default, if an Enhanced IGRP neighbor is present, the Cisco IOS software sends SAP updates only when the SAP table changes. On Ethernet, Token Ring, and FDDI interfaces, by default, the software sends SAP updates periodically. To reduce the amount of bandwidth required to send SAP updates, you might want to disable the periodic sending of SAP updates on LAN interfaces. This feature should only be disabled when all nodes out of this interface are Enhanced IGRP peers; otherwise, loss of SAP information on the other nodes will result.
To send SAP updates only when a change occurs in the SAP table, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx sap-incremental eigrp autonomous-system-number | Send SAP updates only when a change in the SAP table occurs, and send only the SAP changes. |
To send SAP updates only when a change occurs in the SAP table and to send only the SAP changes, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx sap-incremental eigrp autonomous-system-number rsup-only | Send SAP updates only when a change in the SAP table occurs, and send only the SAP changes. |
When you enable incremental SAP using the ipx sap-incremental eigrp rsup-only command, CiscoIOS software disables the exchange of route information via Enhanced IGRP for that interface.
To send periodic SAP updates, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
no ipx sap-incremental eigrp autonomous-system-number |
For an example of how to configure SAP updates, see the "Enhanced IGRP SAP Update Examples" section at the end of this chapter.
To disable split horizon for incremental SAP, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
no ipx sap-incremental split-horizon | Disable split horizon for SAP. |
|
NoteIPX incremental SAP split horizon is off for WAN interfaces and subinterfaces, and on for LAN interfaces. The global default stays off. The interface setting takes precedence if the interface setting is modified or when both the global and interface settings are unmodified. The global setting is used only when the global setting is modified and the interface setting is unmodified. |
To control which devices learn about services, you can control the advertising of these services in SAP updates. To control this advertising, use the following command in router configuration mode:
| Command | Purpose |
|---|---|
distribute-sap-list access-list-number out [interface-name | routing-process] | Control the advertising of services in SAP updates distributed between routing processes. |
For a configuration example of controlling the advertisement of SAP updates, see the "Advertisement and Processing of SAP Update Examples" section at the end of this chapter.
To control the processing of routes listed in incoming updates, use the following command in router configuration mode:
| Command | Purpose |
|---|---|
distribute-sap-list access-list-number in [interface-name] | Control which incoming SAP updates are processed. |
For a configuration example of controlling the processing of SAP updates, see the "Advertisement and Processing of SAP Update Examples" section at the end of this chapter.
By default, the Cisco IOS software queries its own copy of the backup server table of each Enhanced IGRP neighbor every 60seconds. To change this interval, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx backup-server-query-interval interval | Specify the minimum period of time between successive queries of the backup server table of a neighbor. |
NLSP is a link-state routing protocol based on the Open System Interconnection (OSI) Intermediate System-to-Intermediate System (IS-IS) protocol.
NLSP is designed to be used in a hierarchical routing environment, in which networked systems are grouped into routing areas. Routing areas can then be grouped into routing domains, and domains can be grouped into an internetwork.
Level 1 routers connect networked systems within a given routing area. Areas are connected to each other by Level 2 routers, and domains are connected by Level 3 routers. A Level2 router also acts as a Level 1 router within its own area; likewise, a Level 3 router also acts as a Level2 router within its own domain.
The router at each level of the topology stores complete information for its level. For instance, Level1 routers store complete link-state information about their entire area. This information includes a record of all the routers in the area, the links connecting them, the operational status of the devices and their links, and other related parameters. For each point-to-point link, the database records the end-point devices and the state of the link. For each LAN, the database records which routers are connected to the LAN. Similarly, Level 2 routers would store information about all the areas in the routing domain, and Level 3 routers would store information about all the domains in the internetwork.
Although NLSP is designed for hierarchical routing environments containing Level 1, 2, and 3 routers, only Level 1 routing with area route aggregation and route redistribution has been defined in a specification.
NLSP is a link-state protocol, which means that every router in a routing area maintains an identical copy of the link-state database. This database contains all information about the topology of the area. All routers synchronize their views of the databases among themselves to keep their copies of the link-state databases consistent. NLSP has the following three major databases:
The Cisco implementation of NLSP supports the Novell NLSP specification, version 1.1. Our implementation of NLSP also includes read-only NLSP MIB variables.
To configure NLSP, you must have configured IPX routing on your router, as described previously in this chapter. Then, you must perform the tasks described in the following sections:
You can optionally perform the tasks described in the following sections:
For an example of enabling NLSP, see the "IPX Routing Protocols Examples" section at the end of this chapter.
An internal network number is an IPX network number assigned to the router. For NLSP to operate, you must configure an internal network number for each device.
To enable IPX routing and to define an internal network number, use the following commands in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx routing | Enable IPX routing. |
Step2 | ipx internal-network network-number |
To enable NLSP, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx router nlsp [tag] | Enable NLSP. |
Step2 | area-address address mask | Define a set of network numbers to be part of the current NLSP area. |
You configure NLSP differently on LAN and WAN interfaces, as described in the following sections:
To configure NLSP on a LAN interface, use the following commands in interface configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx network network [encapsulation encapsulation-type] | Enable IPX routing on an interface. |
Step2 | ipx nlsp [tag] enable |
To configure multiple encapsulations on the same physical LAN interfaces, you must configure subinterfaces. Each subinterface must have a different encapsulation type. To configure subinterfaces, use the following commands beginning in global configuration mode:
Repeat these three steps for each subinterface.
|
NoteWhen enabling NLSP and configuring multiple encapsulations on the same physical LAN interface, you must use subinterfaces. You cannot use secondary networks. |
To configure NLSP on a WAN interface, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | interface serial number | |
Step2 | ipx ipxwan [local-node unnumbered local-server-name retry-interval retry-limit] | Enable IPXWAN. |
Step3 | ipx nlsp [tag] enable |
You might want to customize the NLSP link characteristics. The following sections describe these customization tasks:
Cisco IOS supports the use of NLSP multicast addressing for Ethernet, Token Ring, and FDDI router interfaces. This capability is only possible when the underlying Cisco hardware device or driver supports multicast addressing.
With this feature, the router defaults to using multicasts on Ethernet, Token Ring, and FDDI interfaces, instead of broadcasts, to address all NLSP routers on the network. If an adjacent neighbor does not support NLSP multicasting, the router will revert to using broadcasts on the affected interface.
This feature is only available on routers running Cisco IOS software Release 11.3 or later. When routers running prior versions of Cisco IOS software are present on the same network with routers running CiscoIOS Release 11.3 software, broadcasts will be used on any segment shared by the two routers.
The NLSP multicast addressing offers the following benefits:
The following sections describe configuration tasks associated with the NLSP multicast addressing:
By default, NLSP multicast addressing is enabled. You need not configure anything to turn on NLSP multicasting.
Typically, you do not want to substitute broadcast addressing where NLSP multicast addressing is available. NLSP multicast addressing uses network bandwidth more efficiently than broadcast addressing. However, there are circumstances where you might want to disable NLSP multicast addressing.
For example, you might want to disable NLSP multicast addressing in favor of broadcast addressing when one or more devices on a segment do not support NLSP multicast addressing. You might also want to disable it for testing purposes.
If you want to disable NLSP multicast addressing, you can do so for the entire router or for a particular interface.
To disable multicast addressing for the entire router, use the following commands in IPX-router configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx router nlsp | Enter NLSP router configuration mode. |
Step2 | no multicast |
To disable multicast addressing on a particular router interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
no ipx nlsp [tag] multicast |
For examples of how to disable NLSP multicast addressing, see the "NLSP Multicast Addressing Examples" section at the end of this chapter.
NLSP assigns a default link cost (metric) based on the link throughput. If desired, you can set the link cost manually.
Typically, you need not set the link cost manually; however, there are some cases where you might want to. For example, in highly redundant networks, you might want to favor one route over another for certain kinds of traffic. As another example, you might want to ensure load sharing. Changing the metric value can help achieve these design goals.
To set the NLSP link cost for an interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nlsp [tag] metric metric-number |
The delay and throughput of each link are used by NLSP as part of its route calculations. By default, these parameters are set to appropriate values or, in the case of IPXWAN, are dynamically measured.
Typically, you need not change the link delay and throughput; however, there are some cases where you might want to change these parameters. For example, in highly redundant networks, you might want to favor one route over another for certain kinds of traffic. To favor one route over another, you would change the metric on the less-desirable path to be slightly worse by assigning it a higher metric value using the ipx-link-delay command. In this case, traffic is forced to route over the favorable path. As another example, you might want to ensure load sharing. To load share, you would ensure that the metrics on the equal paths are the same.
The link delay and throughput you specify replaces the default value or overrides the value measured by IPXWAN when it starts. The value is also supplied to NLSP for use in metric calculations.
To change the link delay, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx link-delay microseconds |
To change the throughput, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx throughput bits-per-second |
By default, IPX packets whose hop count exceeds 15 are discarded. In larger internetworks, this maximum hop count may be insufficient. You can increase the hop count to a maximum of 127 hops for NLSP.
For example, if you have a network with end nodes separated by more than 15 hops, you can set the maximum number of hops considered to be reachable by non-RIP routing protocols to a value from 16 to 127.
To modify the maximum hop count, use the following command in global configuration mode:
|
NoteIn the context of this discussion, the term designated router can refer to an access server or a router. |
NLSP elects a designated router on each LAN interface. The designated router represents all routers that are connected to the same LAN segment. It creates a virtual router called a pseudonode, which generates routing information on behalf of the LAN and sends it to the remainder of the routing area. The routing information generated includes adjacencies and RIP routes. The use of a designated router substantially reduces the number of entries in the LSP database.
By default, electing a designated router is done automatically. However, you can manually affect the identity of the designated router by changing the priority of the system; the system with the highest priority is elected to be the designated router.
By default, the priority of the system is 44. To change this priority, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nlsp [tag] priority priority-number |
You can configure the hello transmission interval and holding time multiplier, the complete sequence number PDU (CSNP) transmission interval, the LSP transmission interval, and the LSP retransmission interval.
The hello transmission interval and holding time multiplier used together determine how long a neighboring system should wait after a link or system failure (the "holding time") before declaring this system to be unreachable. The holding time is equal to the hello transmission interval multiplied by the holding time multiplier.
To configure the hello transmission interval on an interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nlsp [tag] 3.325 seconds |
To specify the holding time multiplier used on an interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nlsp [tag] hello-multiplier multiplier |
Although not typically necessary, you can configure the CSNP transmission interval. To configure the CSNP interval, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nlsp [tag] csnp-interval seconds |
You can specify how fast LSPs can be flooded out an interface by configuring the LSP transmission interval. To configure the LSP transmission interval, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nlsp [tag] lsp-interval interval | Configure the LSP transmission interval. |
You can set the maximum amount of time that can pass before an LSP will be resent on a WAN link when no acknowledgment is received. To configure this LSP retransmission interval, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nlsp [tag] retransmit-interval seconds |
To modify LSP parameters, use one or more of the following commands in router configuration mode:
| Command | Purpose |
|---|---|
lsp-gen-interval seconds | |
max-lsp-lifetime [hours] value | Set the maximum time the LSP persists. |
lsp-refresh-interval seconds | |
lsp-mtu bytes | |
spf-interval seconds |
You can control how often the Cisco IOS software performs a partial route calculation (PRC). Because the partial route calculation is processor-intensive, it may be useful to limit how often this calculation is done, especially on slower router models. Increasing the PRC interval reduces the processor load of the router, but it also potentially slows down the rate of convergence.
To modify the PRC, use the following command in router configuration mode:
| Command | Purpose |
|---|---|
prc-interval seconds | Set the hold-down period between partial route calculations. |
Prior to Cisco IOS Release 11.1, you could segregate IPX internetworks into distinct NLSP areas only by interconnecting them with IPX RIP. With Release 11.1 or later software, you can easily perform the following tasks:
In this document, these independent capabilities are known collectively as the route aggregation feature. Cisco has designed the route aggregation feature to be compatible with the Novell NetWare Link Services Protocol (NLSP) Specification, Revision 1.1 publication.
|
NoteIn the sections that follow, "NLSP version 1.1 routers" refers to routers that support the route aggregation feature, while "NLSP version 1.0 routers" refers to routers that do not. Additionally, all NLSP instances configured on a router running Release 11.1 are NLSP 1.1 instances. They are all capable of generating and using aggregated routes. However, in the text and examples that follow, an "NLSP 1.0 instance" refers to an instance of NLSP that is in an area that includes NLSP version1.0 routers. |
This section discusses area addresses, route summaries, and aggregated routes. It also describes how area addresses relate to route summaries.
An area address uniquely identifies an NLSP area. The area addresses configured on each router determine the areas to which a router belongs.
An area address consists of a pair of 32-bit hexadecimal numbers that include an area number and a corresponding mask. The mask indicates how much of the area number identifies the area, and how much identifies individual networks in the area. For example, the area address pair 12345600FFFFFF00 describes an area composed of 256 networks in the range 12345600 to 123456FF.
You can configure up to three area addresses per NLSP process on the router. Adjacencies are formed only between routers that share at least one common area address.
A route summary defines a set of explicit routes that the router uses to generate an aggregated route. A route summary tells the router how to summarize the set of explicit routes into a single summarized route.
A route summary is similar in form to an area address. That is, the route summary described by 12345600FFFFFF00 summarizes the 256 networks in the range 12345600 to 123456FF.
An aggregated route is the single, compact data structure that describes many IPX network numbers simultaneously. The aggregated route represents all the explicit routes defined by the route summary. In an LSP, the router expresses an aggregated route as a 1-byte number that gives the length, in bits, of the portion of the 32-bit network number common to all summarized addresses. The aggregated route for 12345600FFFFFF00 is 18 12345600.
When you enable route summarization in Cisco IOS Release 11.1 while running multiple instances of NLSP, the router performs default route summarization based on the area address configured in each NLSP area. That is, explicit routes that match the area address in a given area are not redistributed individually into neighboring NLSP areas. Instead, the router redistributes a single aggregated route that is equivalent to the area address into neighboring areas.
This section describes single versus multiple NLSP areas and discusses the behavior of the router when you mix NLSP versions within a single NLSP area.
NLSP version 1.0 routers support only a single, Level 1 area. Two routers form an adjacency only if they share at least one configured area address in common. The union of routers with adjacencies in common form an area.
Each router within the NLSP area has its own adjacencies, link-state, and forwarding databases. Further, the link-state database of each router is identical. Within the router, these databases operate collectively as a single process or instance to discover, select, and maintain route information about the area. NLSP version 1.0 routers and NLSP version 1.1 routers that exist within a single area use a single NLSP instance.
With NLSP version 1.1 and Cisco IOS Release 11.1, multiple instances of NLSP may exist on a given router. Each instance discovers, selects, and maintains route information for a separate NLSP area. Each instance has its own copy of the NLSP adjacency and link-state database for its area. However, all instances (along with other routing protocols such as RIP and Enhanced IGRP) share a single copy of the forwarding table.
You can have NLSP version 1.1 routers and NLSP version 1.0 routers in the same area. However, NLSP version 1.0 routers do not recognize aggregated routes. For this reason, the default behavior of Cisco IOS Release 11.1 software is to not generate aggregated routes. To prevent routing loops in a mixed environment, packets routed via an aggregated route by an NLSP version 1.1 router are dropped if the next hop is an NLSP version 1.0 router.
|
NoteIn general, you should ensure that all routers in an area are running NLSP version 1.1-capable software before you enable route summarization on any of the routers in an area. |
Because you can configure multiple NLSP areas, you must understand how the router passes route information from one area to another. Passing route information from one area to another, or from one protocol to another, is known as route redistribution. Additionally, you must understand the default route redistribution behavior of the router before configuring route summarization.
This section describes the default route redistribution behavior between multiple NLSP areas, between NLSP and Enhanced IGRP, and between NLSP and RIP.
Regardless of the NLSP version, Cisco IOS Release 11.1 redistributes routes between multiple NLSP areas by default. That is, redistribution between multiple NLSP version 1.1 areas, between multiple NLSP version 1.0 areas, and between NLSP version 1.1 and NLSP version 1.0 areas is enabled by default. All routes are redistributed as individual, explicit routes.
Route redistribution between instances of NLSP (version 1.1 or version 1.0) and Enhanced IGRP is disabled by default. You must explicitly configure this type of redistribution. See the "Redistributing Routing Information" section later in this chapter for information about configuring redistribution between NLSP and Enhanced IGRP.
Route redistribution between instances of NLSP (version 1.1 or version 1.0) and RIP is enabled by default. All routes are redistributed as individual, explicit routes.
Route summarization is disabled by default to avoid the generation of aggregated routes in an area running mixed versions of NLSP. You can explicitly enable route summarization on a router running CiscoIOS Release 11.1. This section describes default route summarization, customized route summarization, and the relationship between filtering and route summarization.
NLSP route summarization provides the following benefits to well-designed IPX networks:
As a result of these benefits, you can build larger IPX networks using route aggregation.
When you explicitly enable route summarization, the default route summarization depends on the following circumstances:
In the case of the first two circumstances, the area address for each NLSP instance is used as the basis for generating aggregated routes. That is, all explicit routes that match a local area address generate a common aggregated route. The router redistributes only the aggregated route into other NLSP areas; explicit routes (and more specific aggregated routes) represented by a particular aggregated route are filtered.
|
NoteThe router continues to redistribute into other areas the explicit routes that do not match the area address. |
You can also customize the route summarization behavior of the router using the redistribute IPX-router subcommand with an access list. The access list specifies in detail which routes to summarize and which routes to redistribute explicitly. In this case, the router ignores area addresses and uses only the access list as a template to control summarization and redistribution. You can use numbered or named access lists to control summarization and redistribution.
In addition, you must use customized route summarization in environments that use either of the following combinations:
Route summarization between Enhanced IGRP and NLSP is controlled by the access list. Route summarization is possible only in the Enhanced IGRP-to-NLSP direction. Routes redistributed from NLSP to Enhanced IGRP are always explicit routes.
Route summarization between RIP and NLSP is also controlled by the access list. Route summarization is possible only in the RIP-to-NLSP direction. Routes redistributed from NLSP to RIP are always explicit routes. Use the default route instead to minimize routing update overhead, yet maximize reachability in a RIP-only area.
|
NoteBefore introducing the default route into a RIP-only area, be sure that all routers and servers in the area are upgraded to understand and use the default route. |
In a well-designed network, within each NLSP area, most external networks are reachable by a few aggregated routes, while all other external networks are reachable either by individual explicit routes or by the default route.
Redistribution of routes and services into and out of an NLSP area may be modified using filters. Filters are available for both input and output directions. Refer to the distribute-list in, distribute-list out, distribute-sap-list in, and distribute-sap-list out commands in the "Novell IPX Commands" chapter in the Cisco IOS AppleTalk and Novell IPX Command Reference publication.
Filtering is independent of route summarization, but may affect it indirectly, because filters are always applied before the aggregation algorithm is applied. It is possible to filter all explicit routes that could generate aggregated routes, making the router unable to generate aggregated routes even though route aggregation is turned on.
The router always accepts service information as long as the network of the service is reachable by an explicit route, an aggregated route, or the default route. When a server for a Get Nearest Server (GNS) response is chosen, the tick value of the route to each eligible server is used as the metric. No distinction is made between explicit and summary routes in this determination. If the tick values are equal, then the hop count is used as a tiebreaker. However, because there is no hop value associated with an aggregated route, services reachable via an explicit route are always preferred over those reachable via only an aggregated route.
An NLSP version 1.1 router always uses the most explicit match to route packets. That is, the router always uses an explicit route if possible. If not, then a matching aggregated route is used. If multiple aggregated routes match, then the most explicit (longest match) is used. If no aggregated route is present, then the default route is used as a last resort.
To configure the route aggregation feature, perform one or more of the task in the following sections:
Redistribution between multiple NLSP 1.1 areas is enabled by default. Because multiple NLSP processes are present on the router, a tag or label identifies each. For each instance, configure an appropriate area address and, optionally, enable route summarization. Enable NLSP on appropriate interfaces. Be sure to use the correct tag (process) identifier to associate that interface with the appropriate NLSP area.
|
NoteNote that the tag used to identify an NLSP instance is meaningful only locally within the router. NLSP adjacencies and areas are determined by the area address and interfaces configured for each instance of NLSP running on each router. There is no need (other than administrative convenience) to ensure that individual tags match between routers. |
The following sections describe how to configure route aggregation for multiple NLSP version 1.1 areas:
To configure the route aggregation feature with the default route summarization behavior, use the following commands for each NLSP process beginning in global configuration mode:
For an example of how to configure this type of route aggregation, see "NLSP Route Aggregation for NLSP Version 1.1 and Version 1.0 Areas Example" section at the end of this chapter.
To configure the route aggregation feature with customized route summarization behavior (using numbered access lists), use the following commands for each NLSP process beginning in global configuration mode:
To configure the route aggregation feature with customized route summarization behavior (using named access lists), use the following commands for each NLSP process beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx router nlsp [tag] | Enable NLSP routing and identify the process with a unique tag. |
Step2 | area-address address mask | From router configuration mode, define up to three area addresses for the process. |
Step3 | route-aggregation | Enable route summarization from router configuration mode. |
Step4 | redistribute nlsp [tag] access-list name | From router configuration mode, use the redistribute command with a named access list. In this case, the tag argument identifies a unique NLSP process. |
Step5 | ipx nlsp [tag] enable | From interface configuration mode, enable NLSP on each network in the area described by the tag argument. |
Step6 | ipx access-list summary name | From global configuration mode, specify a named IPX access list for NLSP route aggregation. |
Step7 | deny network network-mask [ticks ticks] | In access-list configuration mode, specify the redistribution of aggregated routes instead of explicit routes. For each address range you want to summarize, use a deny command. |
Step8 | permit -1 | (Optional) Terminate the access list with a "permit all" statement to redistribute all other routes as explicit routes. |
By default, redistribution is enabled between multiple instances of NLSP. Route summarization, when enabled, is possible in one direction only---from NLSP version 1.0 to NLSP version 1.1.
The following sections describe how to configure route aggregation for NLSP version 1.1 and NLSP version 1.0 areas:
To configure the route aggregation feature with default route summarization behavior, use the following commands for each NLSP process beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx router nlsp [tag] | Enable NLSP routing and identify the process with a unique tag. |
Step2 | area-address address mask | From router configuration mode, define up to three area addresses for the process. |
Step3 | route-aggregation | For NLSP version 1.1 areas, enable route summarization from router configuration mode. Omit this step for NLSP version 1.0 areas. |
Step4 | ipx nlsp [tag] enable | From interface configuration mode, enable NLSP on each network in the area described by the tag argument. |
To configure the route aggregation feature with customized route summarization behavior (using numbered access lists), use the commands in the following two tables.
For the NLSP version 1.1 process, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx router nlsp [tag] | Enable NLSP routing and identify the process with a unique tag. |
Step2 | area-address address mask | From router configuration mode, define up to three area addresses for the process. |
Step3 | route-aggregation | For NLSP version 1.1 areas, enable route summarization from router configuration mode. |
Step4 | redistribute nlsp [tag] access-list access-list-number | (Optional) From router configuration mode, redistribute NLSP version 1.0 into the NLSP version 1.1 area. Include an access list number from 1200 to 1299. |
Step5 | ipx nlsp [tag] enable | From interface configuration mode, enable NLSP on each network in the area described by the tag argument. |
Step6 | access-list access-list-number deny network network-mask [ticks ticks] [area-count area-count] | (Optional) From global configuration mode, define the access list to redistribute an aggregated route instead of explicit routes learned from the NLSP version 1.0 area. For each address range you want to summarize, use the deny keyword. |
Step7 | access-list access-list-number permit -1 | (Optional) Terminate the access list with a "permit all" statement to redistribute all other routes as explicit routes. |
For the NLSP version 1.0 process, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx router nlsp [tag] | Enable NLSP routing and identify the process with a unique tag. |
Step2 | area-address address mask | From router configuration mode, define up to three area addresses for the process. |
Step3 | ipx nlsp [tag] enable | From interface configuration mode, enable NLSP on each network in the area described by the tag argument. |
For an example of how to configure the route aggregation feature with this type of customized route summarization, see the "NLSP Route Aggregation for NLSP Version 1.1 and Version 1.0 Areas Example" section at the end of this chapter.
To configure the route aggregation feature with customized route summarization behavior (using named access lists), use the commands in the following two tables.
For the NLSP version 1.1 process, use the following commands beginning in global configuration mode:
For the NLSP version 1.0 process, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx router nlsp [tag] | Enable NLSP routing and identify the process with a unique tag. |
Step2 | area-address address mask | From router configuration mode, define up to three area addresses for the process. |
Step3 | ipx nlsp [tag] enable | From interface configuration mode, enable NLSP on each network in the area described by the tag argument. |
Redistribution is not enabled by default. Additionally, summarization is possible in the Enhanced IGRP to NLSP direction only.
The following sections describe how to configure route aggregation for Enhanced IGRP and NLSP version 1.1 environments:
For each NLSP version 1.1 process, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx router nlsp [tag] | Enable NLSP routing and identify the process with a unique tag. |
Step2 | area-address address mask | From router configuration mode, define up to three area addresses for the process. |
Step3 | route-aggregation | (Optional) From router configuration mode, enable route summarization. |
Step4 | redistribute {eigrp autonomous-system-number}
[access-list access-list-number]
| (Optional) From router configuration mode, redistribute Enhanced IGRP into the NLSP version 1.1 area. Include an access list number from 1200 to 1299. |
Step5 | ipx nlsp [tag] enable | From interface configuration mode, enable NLSP on each network in the area described by the tag argument. |
Step6 | access-list access-list-number deny network network-mask [ticks ticks] [area-count area-count] | (Optional) From global configuration mode, define the access list to redistribute an aggregated route instead of explicit routes learned from Enhanced IGRP. For each address range you want to summarize, use the deny keyword. |
Step7 | access-list access-list-number permit -1 | (Optional) Terminate the access list with a "permit all" statement to redistribute all other Enhanced IGRP routes as explicit routes. |
For each Enhanced IGRP autonomous system, use the following commands beginning in global configuration mode:
For an example of how to configure this type of route aggregation, see the "NLSP Route Aggregation for NLSP Version 1.1, Enhanced IGRP, and RIP Example" section at the end of this chapter.
For each NLSP version 1.1 process, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx router nlsp [tag] | Enable NLSP routing and identify the process with a unique tag. |
Step2 | area-address address mask | From router configuration mode, define up to three area addresses for the process. |
Step3 | route-aggregation | (Optional) From router configuration mode, enable route summarization. |
Step4 | redistribute {eigrp autonomous-system-number}
access-list name
| (Optional) From router configuration mode, redistribute Enhanced IGRP into the NLSP version 1.1 area. |
Step5 | ipx nlsp [tag] enable | From interface configuration mode, enable NLSP on each network in the area described by the tag argument. |
Step6 | ipx access-list summary name | (Optional) From global configuration mode, specify a named IPX access list for NLSP route aggregation. |
Step7 | deny network network-mask [ticks ticks] | (Optional) From access-list configuration mode, define the access list to redistribute an aggregated route instead of explicit routes learned from Enhanced IGRP. For each address range you want to summarize, use a deny statement. |
Step8 | permit -1 | (Optional) Terminate the access list with a "permit all" statement to redistribute all other Enhanced IGRP routes as explicit routes. |
For each Enhanced IGRP autonomous system, use the following commands beginning in global configuration mode:
Because redistribution between RIP and NLSP is enabled by default, you only need to enable the route summarization, if desired, to configure all the capabilities of the route aggregation feature.
The following sections describe how to configure route aggregation for RIP and NLSP version 1.1 environments:
For each NLSP version 1.1 process, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx router nlsp [tag] | Enable NLSP routing and identify the process with a unique tag. |
Step2 | area-address address mask | From router configuration mode, define up to three area addresses for the process. |
Step3 | route-aggregation | (Optional) From router configuration mode, enable route summarization. |
Step4 | redistribute rip [access-list access-list-number] | (Optional) From router configuration mode, redistribute RIP routes into the NLSP version 1.1 area. Include an access list number from 1200 to 1299. |
Step5 | ipx nlsp [tag] enable | From interface configuration mode, enable NLSP on each network in the area described by the tag argument. |
Step6 | access-list access-list-number deny network network-mask [ticks ticks] [area-count area-count] | (Optional) From global configuration mode, define the access list to redistribute an aggregated route instead of explicit RIP routes. For each address range you want to summarize, use the deny keyword. |
Step7 | access-list access-list-number permit -1 | (Optional) Terminate the access list with a "permit all" statement to redistribute all other RIP routes as explicit routes. |
For an example of how to configure this type of route aggregation, see the "NLSP Route Aggregation for NLSP Version 1.1, Enhanced IGRP, and RIP Example" section at the end of this chapter.
For each NLSP version 1.1 process, use the following commands beginning in global configuration mode:
You might want to customize the exchange of routing information. The following sections describe customization tasks:
RIP and SAP are enabled by default on all interfaces configured for IPX, and these interfaces always respond to RIP and SAP requests. When you also enable NLSP on an interface, the interface, by default, generates and sends RIP and SAP periodic traffic only if another RIP router or SAP service is sending RIP or SAP traffic.
To modify the generation of periodic RIP updates on a network enabled for NLSP, use one of the following commands in interface configuration mode:
To modify the generation of periodic SAP updates on a network enabled for NLSP, use one of the following commands in interface configuration mode:
Automatic redistribution of one routing protocol into another provides a simple and effective means for building IPX networks in a heterogeneous routing protocol environment. Redistribution is usually effective as soon as you enable an IPX routing protocol. One exception is NLSP and Enhanced IGRP. You must configure the redistribution of Enhanced IGRP into NLSP, and vice versa.
Once you enable Enhanced IGRP and NLSP redistribution, the router makes path decisions based on a predefined, nonconfigurable administrative distance, and prevents redistribution feedback loops without filtering via a stored, external hop count.
To enable redistribution of Enhanced IGRP into NLSP, and vice versa, use the following commands beginning in global configuration mode:
For an example of how to enable redistribution of Enhanced IGRP and NLSP, see the "Enhanced IGRP and NLSP Route Redistribution Example" section at the end of this chapter.
Routers, access servers, and hosts can use Next Hop Resolution Protocol (NHRP) to discover the addresses of other routers and hosts connected to an NBMA network. NHRP provides an Address Resolution Protocol (ARP)-like solution that alleviates some NBMA network problems. With NHRP, systems attached to an NBMA network can dynamically learn the NBMA address of the other systems that are part of that network. These systems can then directly communicate without requiring traffic to use an intermediate hop.
For more information on NHRP and the Cisco implementation, refer to the "Configuring IP Addressing" chapter in the Cisco IOS IP and IP Routing Configuration Guide.
To configure NHRP, perform the tasks described in the following sections. The first task is required, the remainder are optional.
For NHRP configuration examples, see the "NHRP Examples" section at the end of this chapter.
.
| Command | Purpose |
|---|---|
ipx nhrp network-id number | Enable NHRP on an interface. |
For an example of enabling NHRP, see the "NHRP Examples" section at the end of this chapter.
To participate in NHRP, a station connected to an NBMA network must be configured with the IPX and NBMA addresses of its Next Hop Servers. The format of the NBMA address depends on the medium you are using. For example, ATM uses a network service access point (NSAP) address, Ethernet uses a MAC address, and SMDS uses an E.164 address.
These Next Hop Servers are most likely the default or peer routers of the station, so their IPX addresses are obtained from the network layer forwarding table of the station.
If the station is attached to several link-layer networks (including logical NBMA networks), the station should also be configured to receive routing information from its Next Hop Servers and peer routers so that it can determine which IPX networks are reachable through which link-layer networks.
| Command | Purpose |
|---|---|
ipx nhrp map ipx-address nbma-address | Configure static IPX-to-NBMA address mapping. |
A Next Hop Server normally uses the network-layer forwarding table to determine where to forward NHRP packets and to find the egress point from an NBMA network. A Next Hop Server may alternately be statically configured with a set of IPX address prefixes that correspond to the IPX addresses of the stations it serves, and their logical NBMA network identifiers.
To statically configure a Next Hop Server, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nhrp nhs nhs-address [net-address] | Statically configure a Next Hop Server. |
To configure multiple networks that the Next Hop Server serves, repeat the ipx nhrp nhs command with the same Next Hop Server address, but different IPX network addresses. To configure additional Next Hop Servers, repeat the ipx nhrp nhs command.
| Command | Purpose |
|---|---|
ipx nhrp authentication string | Specify an authentication string. |
To control when NHRP is initiated, perform one of the tasks in the following sections:
You can specify an IPX access list that is used to decide which IPX packets trigger the sending of NHRP requests. By default, all non-NHRP packets can trigger NHRP requests. To limit which IPX packets trigger NHRP requests, you must define an access list and then apply it to the interface.
To define an access list, use one of the following commands in global configuration mode:
To apply the IPX access list to the interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nhrp interest access-list-number | Specify an IPX access list that controls NHRP requests. |
By default, when the software attempts to send a data packet to a destination for which it has determined that NHRP can be used, it sends an NHRP request for that destination. You can configure the system to wait until a specified number of data packets have been sent to a particular destination before NHRP is attempted. To configure the system in this way, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nhrp use usage-count | Specify how many data packets are sent to a destination before NHRP is attempted. |
By default, the maximum rate at which the software sends NHRP packets is 5 packets per 10seconds. The software maintains a per-interface quota of NHRP packets (whether generated locally or forwarded) that can be sent. To change this maximum rate, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nhrp max-send pkt-count every interval | Change the NHRP packet rate per interface. |
To dynamically detect link-layer filtering in NBMA networks (for example, SMDS address screens), and to provide loop detection and diagnostic capabilities, NHRP incorporates a route record in requests and replies. The route record options contain the network (and link layer) addresses of all intermediate Next Hop Servers between source and destination (in the forward direction) and between destination and source (in the reverse direction).
By default, forward record options and reverse record options are included in NHRP request and reply packets. To suppress the use of these options, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
no ipx nhrp record | Suppress forward and reverse record options. |
If an NHRP requester wants to know which Next Hop Server generates an NHRP reply packet, it can request that information by including the responder address option in its NHRP request packet. The Next Hop Server that generates the NHRP reply packet then complies by inserting its own IPX address in the NHRP reply. The Next Hop Server uses the primary IPX address of the specified interface.
To specify which interface the Next Hop Server uses for the NHRP responder IPX address, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nhrp responder type number | Specify which interface the Next Hop Server uses to determine the NHRP responder address. |
If an NHRP reply packet being forwarded by a Next Hop Server contains the IPX address of that Next Hop Server, the Next Hop Server generates an "NHRP Loop Detected" error indication and discards the reply.
You can change the length of time that NBMA addresses are advertised as valid in positive and negative NHRP responses. In this context, advertised means how long the Cisco IOS software tells other routers to keep the addresses it is providing in NHRP responses. The default length of time for each response is 7200 seconds (2hours). To change the length of time, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx nhrp holdtime seconds-positive [seconds-negative] | Specify the number of seconds that NBMA addresses are advertised as valid in positive or negative NHRP responses. |
You can configure IPX over dial-on-demand routing (DDR), Frame Relay, PPP, SMDS, and X.25 networks. For more information about dial-on-demand routing (DDR) refer to the Cisco IOS Dial Services Configuration Guide: Terminal Services. For more information about Frame Relay, SMDS, and X.25 refer to the Cisco IOS Wide Area Networking Configuration Guide.
When you configure IPX over PPP, address maps are not necessary for this protocol. Also, you can enable IPX header compression over point-to-point links to increase available useful bandwidth of the link and reduce response time for interactive uses of the link.
You can use fast-switching IPX serial interfaces configured for Frame Relay and SMDS, and you can use fast-switching Subnetwork Access Protocol (SNAP)-encapsulated packets over interfaces configured for ATM.
Additionally, you can configure the IPXWAN protocol.
For an example of how to configure IPX over a WAN interface, see the "IPX over a WAN Interface Example" section at the end of this chapter.
IPX sends periodic watchdog keepalive packets from servers to clients after a client session has been idle for approximately 5 minutes. On a DDR link, a call would be made every 5minutes, regardless of whether there were data packets to send. You can prevent these calls from being made by configuring the Cisco IOS software to respond to the watchdog keepalive packets of a server on behalf of a remote client---sometimes referred to as spoofing the server. Spoofing makes a server view a client as always connected, even when it is not, thus reducing the number of available licenses. Users can set the duration of IPX watchdog spoofing and periodically disable it so that Novelle NetWare servers can clean up inactive connections.
When configuring IPX over DDR, you might want to disable the generation of these packets so that a call is not made every 5 minutes. A call made every 5 minutes is not an issue for the other WAN protocols, because they establish dedicated connections rather than establishing connections only as needed.
Use the ipx watchdog-spoof command to enable and set the duration of watchdog spoofing. You can specify the number of consecutive hours spoofing is to stay enabled and the number of minutes spoofing is to stay disabled. The server can clean up inactive connections when spoofing is disabled. Be sure that fast switching and autonomous switching are disabled on the serial interface before using this command.
To enable watchdog spoofing, use the following interface configuration command
:
| Command | Purpose |
|---|---|
ipx watchdog-spoof [enable-time-hours disable-time-minutes] | Enables and sets the duration of watchdog spoofing. |
To keep the serial interface idle when only watchdog packets are being sent, refer to the tasks described in the "Deciding and Preparing to Configure DDR" chapter of the Cisco IOS Dial Services Configuration Guide: Terminal Services. For an example of configuring IPX over DDR, see the "IPX over DDR Example" section at the end of this chapter.
Sequenced Packet Exchange (SPX) sends periodic keepalive packets between clients and servers. Similar to IPX watchdog packets, these are keepalive packets that are sent between servers and clients after the data has stopped being transferred. On pay-per-packet or byte networks, these packets can incur large customer telephone connection charges for idle time. You can prevent these calls from being made by configuring the Cisco IOS software to respond to the keepalive packets on behalf of a remote system.
When configuring SPX over DDR, you might want to disable the generation of these packets so that a call has the opportunity to go idle. Disabling the generation of packets may not be an issue for the other WAN protocols, because they establish dedicated connections rather than establishing connections only as needed.
To keep the serial interface idle when only keepalive packets are being sent, refer to the tasks described in the "Deciding and Preparing to Configure DDR" chapter of the Cisco IOS Dial Services Configuration Guide: Terminal Services.
For an example of how to configure SPX spoofing over DDR, see the "IPX over DDR Example" section at the end of this chapter.
You can configure IPX header compression over point-to-point links. With IPX header compression, a point-to-point link can compress IPX headers only, or the combined IPX and NetWare Core Protocol headers. Currently, point-to-point links must first negotiate IPX header compression via IPXCP or IXPWAN. The Cisco IOS software supports IPX header compression as defined by RFC1553.
For details on configuring IPX header compression, refer to the "Configuring Medial-Independent PPP and Multilink PPP" chapter in the Cisco IOS Dial Services Configuration Guide: Terminal Services.
The Cisco IOS software supports the IPXWAN protocol, as defined in RFC 1634. IPXWAN allows a router that is running IPX routing to connect via a serial link to another router, possibly from another manufacturer, that is also routing IPX and using IPXWAN.
IPXWAN is a connection startup protocol. Once a link has been established, IPXWAN incurs little or no overhead.
You can use the IPXWAN protocol over PPP. You can also use it over HDLC; however, the devices at both ends of the serial link must be Cisco routers.
To configure IPXWAN on a serial interface, use the following commands in interface configuration mode:
To control access to IPX networks, first create access lists and then apply them to individual interfaces using filters.
You can create the following IPX access lists to filter various kinds of traffic:
There are more than 14 different IPX filters that you can define for IPX interfaces. They fall into the following six groups:
Table 9 summarizes the filters, the access lists they use, and the commands used to define the filters in the first five groups. Use the showipx interfaces command to display the filters defined on an interface. For additional information about route aggregation, see the "Configuring Route Aggregation" section earlier in this chapter.
| Filter Type | Access List Used by Filter | Command to Define Filter |
|---|---|---|
| Generic filters |
| |
Filter inbound or outbound packets based on the contents of the IPX network header. | Standard or Extended | ipx access-group {access-list-number | name} [in | out]
|
| Routing table filters | ||
Control which networks are added to the routing table. | Standard or Extended | ipx input-network-filter {access-list-number | name}
|
Control which networks are advertised in routing updates. | Standard or Extended | ipx output-network-filter {access-list-number | name}
|
Control which networks are advertised in the Enhanced IGRP routing updates sent out by the CiscoIOS software. | Standard or Extended | distribute-list {access-list-number | name} out [interface-name | routing-process]
|
Control the routers from which updates are accepted. | Standard or Extended | ipx router-filter {access-list-number | name}
|
| SAP filters | ||
Filter incoming service advertisements. | SAP | ipx input-sap-filter {access-list-number | name}
|
Filter outgoing service advertisements. | SAP | ipx output-sap-filter {access-list-number | name}
|
Control the routers from which SAP updates are accepted. | SAP | ipx router-sap-filter {access-list-number | name}
|
Filter list of servers in GNS response messages. | SAP | ipx output-gns-filter {access-list-number | name}
|
| IPX NetBIOS filters | ||
Filter incoming packets by node name. | IPX NetBIOS | ipx netbios input-access-filter host name |
Filter incoming packets by byte pattern. | IPX NetBIOS | ipx netbios input-access-filter bytes name |
Filter outgoing packets by node name. | IPX NetBIOS | ipx netbios output-access-filter host name |
Filter outgoing packets by byte pattern. | IPX NetBIOS | ipx netbios output-access-filter bytes name |
| Broadcast filters |
| |
Control which broadcast packets are forwarded. | Standard or Extended | ipx helper-list {access-list-number | name}
|
Remember the following information when configuring IPX network access control:
You perform the required tasks in the following sections to control access to IPX networks:
You can create access lists using numbers or names. You can choose which method you prefer. If you use numbers to identify your access lists, you are limited to 100 access lists per filter type. If you use names to identify your access lists, you can have an unlimited number of access lists per filter type.
The following sections describe how to perform these tasks:
To create access lists using numbers, use one or more of the following commands in global configuration mode:
| Command | Purpose |
|---|---|
access-list access-list-number {deny | permit}
source-network [.source-node [source-node-mask]] | Define a standard IPX access list using a number. (Generic, routing, and broadcast filters use this type of access list.) |
access-list access-list-number {deny | permit}
protocol [source-network [.source-node
[source-network-mask.source-node-mask]]
source-socket [destination-network
[.destination-node
[destination-network-mask.destination-node-mask]
destination-socket]
[log] [time-range
time-range-name]
| Define an extended IPX access list using a number. (Generic, routing, and broadcast filters use this type of access list.) Use the log keyword to get access list logging messages, including violations. Specify a time range to restrict when the permit or deny statement is in effect. |
access-list access-list-number {deny | permit}
network [.node] [network-mask.node-mask]
[service-type [server-name]]
| Define a SAP filtering access list using a number. (SAP and GNS response filters use this type of access list). |
Once you have created an access list using numbers, apply it to the appropriate interfaces using filters as described in the "Creating Filters" section later in this chapter. Applying a filter will activate the access list.
IPX named access lists allow you to identify IPX access lists with an alphanumeric string (a name) rather than a number. Using IPX named access lists allows you to maintain security by using a separate and easily identifiable access list for each user or interface. IPX named access lists also remove the limit of 100lists per filter type.You can configure an unlimited number of the following types of IPX named access lists:
If you identify your access list with a name rather than a number, the mode and command syntax are slightly different.
Consider the following information before configuring IPX named access lists:
To configure IPX named access lists for standard, extended, SAP, NLSP route aggregation (summarization), or NetBIOS access lists, perform one or more of the tasks in the following sections:
To create a named standard access list, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx access-list standard name | Define a standard IPX access list using a name. (Generic, routing, and broadcast filters use this type of access list.) |
Step2 | {deny | permit} source-network [.source-node
[source-node-mask]] [destination-network
[.destination-node [destination-node-mask]]]
| In access-list coytnfiguration mode, specify one or more conditions allowed or denied. This determines whether the packet is passed or dropped. |
Step3 | exit | Exit access-list configuration mode. |
For an example of creating a named standard access list, see the "Standard Named Access List Example" section at the end of this chapter.
To create a named extended access list, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx access-list extended name | Define an extended IPX access list using a name. (Generic, routing, and broadcast filters use this type of access list.) |
Step2 | {deny | permit} protocol [source-network]
[[[.source-node] source-node-mask] | [.source-node
source-network-mask.source-node-mask]]
[source-socket] [destination-network]
[[[.destination-node] destination-node-mask] |
[.destination-node
destination-network-mask.destination- | In access-list configuration mode, specify the conditions allowed or denied. Use the log keyword to get access list logging messages, including violations. Specify a time range to restrict when the permit or deny statement is in effect. |
Step3 | exit | Exit access-list configuration mode. |
| Command | Purpose | |
|---|---|---|
Step1 | ipx access-list sap name | Define a SAP filtering access list using a name. (SAP, GNS, and Get General Service (GGS) response filters use this type of access list.) |
Step2 | {deny | permit} network [.node]
[network-mask.node-mask] [service-type
[server-name]]
| In access-list configuration mode, specify the conditions allowed or denied. |
Step3 | exit | Exit access-list configuration mode. |
NLSP route aggregation access lists perform one of the following functions:
| Command | Purpose | |
|---|---|---|
Step1 | ipx access-list summary name | Define an IPX access list for NLSP route aggregation using a name. |
Step2 | {deny | permit} network network-mask [ticks ticks] | In access-list configuration mode, specify the conditions allowed or denied. For each address range you want to redistribute as a single aggregated route, use the deny keyword. For each address that you want to redistribute explicitly, use the permit keyword. |
Step3 | exit | Exit access-list configuration mode. |
For information on how to use named access list when configuring route aggregation, see the tasks listed in the "Configuring Route Aggregation Task List" section earlier in this chapter.
To create a NetBIOS access list, use one or more of the following commands in global configuration mode:
After you initially create an access list, you place any subsequent additions (possibly entered from the terminal) at the end of the list. In other words, you cannot selectively add access list command lines to the middle of a specific access list. However, you can use no permit and no deny commands to remove entries from a named access list.
|
NoteWhen creating access lists, remember that, by default, the end of the access list contains an implicit deny statement for everything if it did not find a match before reaching the end. |
For an example of creating a generic filter, see the "IPX Network Access Examples" section at the end of this chapter.
After creating an access list, you must apply it to the appropriate interface using filters as described in the "Creating Filters" section later in this chapter. Applying a filter will activate the access list.
It is now possible to implement access lists based on the time of day and week using the time-range command. To do so, first define the name of the time range and times of the day and week, then reference the time range by name in an access list to apply the restrictions of the time range to the access list.
Currently, IP and IPX named or numbered extended access lists are the only functions that can use time ranges. The time range allows the network administrator to define when the permit or deny statements in the access list are in effect. Prior to this time range feature, access list statements were always in effect once they were applied. The time-range keyword and argument are referenced in the named and numbered extended access list task tables in the previous sections, "Creating Access Lists Using Numbers" and "Creating Access Lists Using Names." The time-range command is configured in the "Performing Basic System Management" chapter of the Cisco IOS Configuration Fundamentals Configuration Guide. See the "IPX Network Access Examples" section at the end of this chapter for a configuration example of IPX time ranges.
There are many possible benefits of time ranges, such as the following:
Filters allow you to control which traffic is forwarded or blocked at the interfaces of the router. Filters apply specific numbered or named access lists to interfaces.
The following sections describe how to perform the tasks for creating filters:
Generic filters determine which data packets to receive from or send to an interface, based on the source and destination addresses, IPX protocol type, and source and destination socket numbers of the packet.
To create generic filters, first create a standard or an extended access list as described in the "Creating Access Lists" section earlier in this chapter and then apply a filter to an interface.
To apply a generic filter to an interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx access-group {access-list-number | name} |
You can apply only one input filter and one output filter per interface or subinterface. You cannot configure an output filter on an interface where autonomous switching is already configured. Similarly, you cannot configure autonomous switching on an interface where an output filter is already present. You cannot configure an input filter on an interface if autonomous switching is already configured on any interface. Likewise, you cannot configure input filters if autonomous switching is already enabled on any interface.
For an example of creating a generic filter, see the "IPX Network Access Examples" section at the end of this chapter.
Routing table update filters control the entries that the Cisco IOS software accepts for its routing table, and the networks that it advertises in its routing updates.
To create filters to control updating of the routing table, first create a standard or an extended access list as described in the "Creating Access Lists" section earlier in this chapter and then apply one or more routing filters to an interface.
To apply routing table update filters to an interface, use one or more of the following commands in interface configuration mode:
|
NoteThe ipx output-network-filter command applies to the IPX RIP only. To control the advertising of routes when filtering routing updates in Enhanced IGRP, use the distribute-list out command. See the "Controlling the Advertising of Routes in Routing Updates" section earlier in this chapter for more information. |
A common source of traffic on Novell networks is SAP messages, which are generated by NetWare servers and the Cisco IOS software when they broadcast their available services.
To control how SAP messages from network segments or specific servers are routed among IPX networks, first create a SAP filtering access list as described in the "Creating Access Lists" section earlier in this chapter and then apply one or more filters to an interface.
To apply SAP filters to an interface, use one or more of the following commands in interface configuration mode:
You can apply one of each SAP filter to each interface.
For examples of creating and applying SAP filters, see the "SAP Input Filter Example" and "SAP Output Filter Example" sections at the end of this chapter.
To create filters for controlling which servers are included in the GNS responses sent by the CiscoIOS software, first create a SAP filtering access list as described in the "Creating Access Lists" section earlier in this chapter and then apply a GNS filter to an interface.
To apply a GNS filter to an interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx output-gns-filter {access-list-number | name}
|
To create filters for controlling which servers are included in the GGS responses sent by the CiscoIOS software, first create a SAP filtering access list as described in the "Creating Access Lists" section earlier in this chapter and then apply a GGS filter to an interface.
|
NoteBecause GGS SAP response filters are applied ahead of output SAP filters, a SAP entry permitted to pass through the GGS SAP response filter can still be filtered by the output SAP filter. |
To apply a GGS filter to an interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx output-ggs-filter | Filters the list of servers in GGS response messages. |
For an example of creating a GGS SAP response filter, see the "IPX Network Access Examples" section at the end of this chapter.
The Novell IPX NetBIOS allows messages to be exchanged between nodes using alphanumeric names and node addresses. Therefore, the Cisco IOS software lets you filter incoming and outgoing NetBIOS FindName packets by the node name or by an arbitrary byte pattern (such as the node address) in the packet.
|
NoteThese filters apply to IPX NetBIOS FindName packets only. They have no effect on Logic Link Control, type 2 (LLC2) NetBIOS packets. |
Remember the following when configuring IPX NetBIOS access control:
To create filters for controlling IPX NetBIOS access, first create a NetBIOS access list as described in the "Creating Access Lists" section earlier in this chapter and then apply the access list to an interface.
To apply a NetBIOS access list to an interface, use one or more of the following commands in interface configuration mode:
| Command | Purpose |
|---|---|
ipx netbios input-access-filter host name | |
ipx netbios input-access-filter bytes name | |
ipx netbios output-access-filter host name | |
ipx netbios output-access-filter bytes name |
You can apply one of each of these four filters to each interface.
For an example of how to create filters for controlling IPX NetBIOS, see the "IPX NetBIOS Filter Examples" section at the end of this chapter.
Routers normally block all broadcast requests and do not forward them to other network segments, therefore preventing the degradation of performance inherent in broadcast traffic over the entire network. You can define which broadcast messages get forwarded to other networks by applying a broadcast message filter to an interface.
To create filters for controlling broadcast messages, first create a standard or an extended access list as described in the "Creating Access Lists" section earlier in this chapter and then apply a broadcast message filter to an interface.
To apply a broadcast message filter to an interface, use the following commands in interface configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx helper-address network.node | |
Step2 | ipx helper-list {access-list-number | name}
|
|
NoteA broadcast message filter has no effect unless you have issued an ipx helper-address or an ipx type-20-propagation command on the interface to enable and control the forwarding of broadcast messages. These commands are discussed later in this chapter. |
For examples of creating and applying broadcast message filters, see the "Helper Facilities to Control Broadcast Examples" section at the end of this chapter.
You can tune IPX network performance by performing the tasks in one or more of the following sections:
You can control compliance to Novell specifications by performing the tasks in the following sections:
NetBIOS over IPX uses Type 20 propagation broadcast packets flooded to all networks to get information about the named nodes on the network. NetBIOS uses a broadcast mechanism to get this information, because it does not implement a network layer.
Routers normally block all broadcast requests. By enabling Type 20 packet propagation, IPX interfaces on the router may accept and forward Type 20 packets.
When an interface configured for Type 20 propagation receives a Type 20 packet, Cisco IOS software processes the packet according to Novell specifications. Cisco IOS software propagates the packet to the next interface. The Type 20 packet can be propagated for up to eight hop counts.
Before forwarding (flooding) the packets, the router performs loop detection as described by the IPX router specification.
You can configure the Cisco IOS software to apply extra checks to Type 20 propagation packets above and beyond the loop detection described in the IPX specification. These checks are the same ones that are applied to helpered all-nets broadcast packets. They can limit unnecessary duplication of Type 20 broadcast packets. The extra helper checks are as follows:
Although this extra checking increases the robustness of Type 20 propagation packet handling by decreasing the amount of unnecessary packet replication, it has the following two side effects:
You use helper addresses to forward non-Type 20 broadcast packets to other network segments. For information on forwarding other broadcast packets, see the "Using Helper Addresses to Forward Broadcast Packets" section later in this chapter.
You can use helper addresses and Type 20 propagation together in your network. Use helper addresses to forward non-Type 20 broadcast packets and use Type 20 propagation to forward Type20 broadcast packets.
You can enable the forwarding of Type 20 packets on individual interfaces. Additionally, you can restrict the acceptance and forwarding of Type 20 packets. You can also choose to not comply with Novell specifications and forward Type 20 packets using helper addresses rather than using Type 20 propagation. The following sections describe these tasks:
By default, Type 20 propagation packets are dropped by the Cisco IOS software. You can configure the software to receive Type 20 propagation broadcast packets and forward (flood) them to other network segments, subject to loop detection.
To enable the receipt and forwarding of Type 20 packets, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx type-20-propagation | Forward IPX Type 20 propagation packet broadcasts to other network segments. |
When you enable Type 20 propagation, Cisco IOS propagates the broadcast to the next interface up to eight hops.
For incoming Type 20 propagation packets, the Cisco IOS software is configured by default to accept packets on all interfaces enabled to receive Type 20 propagation packets. You can configure the software to accept packets only from the single network that is the primary route back to the source network, which means that similar packets from the same source that are received via other networks will be dropped.
Checking of incoming Type 20 propagation broadcast packets is done only if the interface is configured to receive and forward Type 20 packets.
To impose restrictions on the receipt of incoming Type 20 propagation packets in addition to the checks defined in the IPX specification, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx type-20-input-checks |
For outgoing Type 20 propagation packets, the Cisco IOS software is configured by default to send packets on all interfaces enabled to send Type 20 propagation packets, subject to loop detection. You can configure the software to send these packets only to networks that are not routes back to the source network. (The software uses the current routing table to determine routes.)
Checking of outgoing Type 20 propagation broadcast packets is done only if the interface is configured to receive and forward Type 20 packets.
To impose restrictions on the transmission of Type 20 propagation packets, and to forward these packets to all networks using only the checks defined in the IPX specification, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx type-20-output-checks |
You can also forward Type 20 packets to specific network segments using helper addresses rather than using the Type 20 packet propagation.
You may want to forward Type 20 packets using helper addresses when some routers in your network are running versions of Cisco IOS that do not support Type 20 propagation. When some routers in your network support Type 20 propagation and others do not, you can avoid flooding packets everywhere in the network by using helper addresses to direct packets to certain segments only.
Cisco IOS Release 9.1 and earlier versions do not support Type 20 propagation.
|
NoteForwarding Type 20 packets using helper addresses does not comply with the Novell IPX router specification. |
To forward Type 20 packets addresses using helper addresses, use the following commands beginning in global configuration mode:
The Cisco IOS software forwards Type 20 packets to only those nodes specified by the ipx helper-address command.
|
NoteUsing the ipx type-20-helpered command disables the receipt and forwarding of Type 20 propagation packets as directed by the ipx type-20-propagation command. |
To control interpacket delay, you can use a combination of global configuration and interface configuration commands.
Use one or more of the following commands in global configuration mode:
Use one or more of the following commands in interface configuration mode:
|
NoteWe recommend that you use the ipx output-rip-delay and ipx output-sap-delay commands on slower speed WAN interfaces. The default delay for Cisco IOS Release 11.1 and later versions is 55milliseconds. |
To shut down an IPX network using a Novell-compliant method, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx down network | Administratively shut down an IPX network on an interface. This removes the network from the interface. |
Convergence is faster when you shut down an IPX network using the ipx down command than when using the shutdown command.
To achieve full compliance on each interface configured for IPX, use the following commands in interface configuration mode:
You can also globally set interpacket delays for multiple-packet RIP and SAP updates to achieve full compliance, eliminating the need to set delays on each interface. To set these interpacker delays, use the following commands in global configuration mode:
|
NoteThe default delay for Cisco IOS Release 11.1 and later versions is 55milliseconds. |
You can adjust RIP and SAP information by performing one or more of the optional tasks in the following sections:
IPX uses RIP, Enhanced IGRP, or NLSP to determine the best path when several paths to a destination exist. The routing protocol then dynamically updates the routing table. However, you might want to add static routes to the routing table to explicitly specify paths to certain destinations. Static routes always override any dynamically learned paths.
Be careful when assigning static routes. When links associated with static routes are lost, traffic may stop being forwarded or traffic may be forwarded to a nonexistent destination, even though an alternative path might be available.
To add a static route to the routing table, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx route {network [network-mask] | default}
{network.node | interface}[ticks] [hops]
|
You can configure static routes that can be overridden by dynamically learned routes. These routes are referred to as floating static routes. You can use a floating static route to create a path of last resort that is used only when no dynamic routing information is available.
|
NoteBy default, floating static routes are not redistributed into other dynamic protocols. |
To add a floating static route to the routing table, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx route {network [network-mask] | default}
{network.node | interface}[ticks] [hops]
[floating-static]
|
By default, all LAN interfaces have a RIP delay of 1 and all WAN interfaces have a RIP delay of 6. Leaving the delay at its default value is sufficient for most interfaces. However, you can adjust the RIP delay field by setting the tick count. To set the tick count, use the following command in interface configuration mode:
| Command | Purpose |
ipx delay tick | Set the tick count, which is used in the IPX RIP delay field. |
To control responses to RIP requests, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx rip-response-delay ms | Set the delay when responding to RIP requests. |
You can set the interval between IPX RIP updates on a per-interface basis. You can also specify the delay between the packets of a multiple-packet RIP update on a per-interface or global basis. Additionally, you can specify the delay between packets of a multiple-packet triggered RIP update on a per-interface or global basis.
You can set RIP update timers only in a configuration in which all routers are Cisco routers, or in which the IPX routers allow configurable timers. The timers should be the same for all devices connected to the same cable segment. The update value you choose affects internal IPX timers as follows:
You might want to set a delay between the packets in a multiple-packet update if there are some slower PCs on the network or on slower-speed interfaces.
To adjust RIP update timers on a per-interface basis, use one or all of the following commands in interface configuration mode:
To adjust RIP update timers on a global basis, use one or both of the following commands in global configuration mode:
By default, the RIP entry for a network or server ages out at an interval equal to three times the RIP timer. To configure the multiplier that controls the interval, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx rip-multiplier multiplier | Configure the interval at which a network RIP entry ages out. |
By default, the maximum size of RIP updates sent out an interface is 432 bytes. This size allows for 50 routes at 8 bytes each, plus a 32-byte IPX RIP header. To modify the maximum packet size, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx rip-max-packetsize bytes | Configure the maximum packet size of RIP updates sent out an interface. |
Servers use SAP to advertise their services via broadcast packets. The Cisco IOS software stores this information in the SAP table, also known as the Server Information Table. This table is updated dynamically. You might want to explicitly add an entry to the Server Information Table so that clients always use the services of a particular server. Static SAP assignments always override any identical entries in the SAP table that are learned dynamically, regardless of hop count. If a dynamic route that is associated with a static SAP entry is lost or deleted, the software will not announce the static SAP entry until it relearns the route.
To add a static entry to the SAP table, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx sap service-type name network.node socket hop-count |
The Cisco IOS software maintains a list of SAP requests to process, including all pending GNS queries from clients attempting to reach servers. When the network is restarted following a power failure or other unexpected event, the router can be inundated with hundreds of requests for servers. Typically, many of these are repeated requests from the same clients. You can configure the maximum length allowed for the pending SAP requests queue. SAP requests received when the queue is full are dropped, and the client must resend them.
To set the queue length for SAP requests, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx sap-queue-maximum number |
You can adjust the interval at which SAP updates are sent. You can also set the delay between packets of a multiple-packet SAP update on a per-interface or global basis. Additionally, you can specify the delay between packets of a multiple-packet triggered SAP update on a per-interface or global basis.
Changing the interval at which SAP updates are sent is most useful on limited-bandwidth, point-to-point links such as slower-speed interfaces. You should ensure that all IPX servers and routers on a given network have the same SAP interval. Otherwise, they might decide that a server is down when it is really up.
It is not possible to change the interval at which SAP updates are sent on most PC-based servers. Therefore, you should never change the interval for an Ethernet or Token Ring network that has servers on it.
You can set the router to send an update only when changes have occurred. Using the changes-only keyword specifies the sending of a SAP update only when the link comes up, when the link is downed administratively, or when the databases change. The changes-only keyword causes the router to do the following:
To modify the SAP update timers on a per-interface basis, use one or all of the following commands in interface configuration mode:
To adjust SAP update timers on a global basis (eliminating the need to configure delays on a per-interface basis), use one or both of the following commands in global configuration mode:
By default, the SAP entry of a network or server ages out at an interval equal to three times the SAP update interval. To configure the multiplier that controls the interval, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx sap-multiplier multiplier | Configure the interval at which the SAP entry of a network or server ages out. |
By default, the maximum size of SAP updates sent out on an interface is 480 bytes. This size allows for seven servers (64 bytes each), plus a 32-byte IPX SAP header. To modify the maximum packet size, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx sap-max-packetsize bytes | Configure the maximum packet size of SAP updates sent out an interface. |
The IPX SAP-after-RIP feature links SAP updates to RIP updates so that SAP broadcast and unicast updates automatically occur immediately after the completion of the corresponding RIP update. This feature ensures that a remote router does not reject service information because it lacks a valid route to the service. As a result of this feature, periodic SAP updates are sent at the same interval as RIP updates.
The default behavior of the router is to send RIP and SAP periodic updates with each using its own update interval, depending on the configuration. In addition, RIP and SAP periodic updates are jittered slightly, such that they tend to diverge from each other over time. This feature synchronizes SAP and RIP updates.
Sending all SAP and RIP information in a single update reduces bandwidth demands and eliminates erroneous rejections of SAP broadcasts.
Linking SAP and RIP updates populates the service table of the remote router more quickly, because services will not be rejected due to the lack of a route to the service. Populating the service table more quickly can be especially useful on WAN circuits where the update intervals have been greatly increased to reduce the overall level of periodic update traffic on the link.
To configure the router to send a SAP update following a RIP broadcast, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx update sap-after-rip | Configure the router to send a SAP broadcast immediately following a RIP broadcast. |
You can disable the sending of general RIP or SAP queries on a link when it first comes up to reduce traffic and save bandwidth.
RIP and SAP general queries are normally sent by remote routers when a circuit first comes up. On WAN circuits, two full updates of each kind are often sent across the link. The first update is a full broadcast update, triggered locally by the link-up event. The second update is a specific (unicast) reply triggered by the general query received from the remote router. If you disable the sending of general queries when the link first comes up, it is possible to reduce traffic to a single update, and save bandwidth.
To disable the sending of a general RIP or SAP query when an interface comes up, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
no ipx linkup-request {rip |
sap}
| Disable the sending of a general RIP or SAP Query when an interface comes up. |
To reenable the sending of a general RIP or SAP query, use the positive form of the command.
You can set the method in which the router responds to SAP GNS requests, you can set the delay time in responding to these requests, or you can disable the sending of responses to these requests altogether.
By default, the router responds to GNS requests if appropriate. For example, if a local server with a better metric exists, then the router does not respond to the GNS request on that segment.
The default method of responding to GNS requests is to respond with the server whose availability was learned most recently.
To control responses to GNS requests, use one or both of the following commands in global configuration mode:
| Command | Purpose |
|---|---|
ipx gns-round-robin | Respond to GNS requests using a round-robin selection method. |
ipx gns-response-delay [milliseconds] |
|
NoteThe ipx gns-response-delay command is also supported as an interface configuration command. To override the global delay value for a specific interface, use the ipxgns-response-delay command in interface configuration mode. |
To disable GNS queries on a per-interface basis, use the following command in interface configuration mode:
| Command | Purpose |
ipx gns-reply-disable |
You can configure IPX to perform round-robin or per-host load sharing, as described in the following sections:
You can set the maximum number of equal-cost, parallel paths to a destination. (Note that when paths have differing costs, the Cisco IOS software chooses lower-cost routes in preference to higher-cost routes.) The software then distributes output on a packet-by-packet basis in round-robin fashion. That is, the first packet is sent along the first path, the second packet along the second path, and so on. When the final path is reached, the next packet is sent to the first path, the next to the second path, and so on. This round-robin scheme is used regardless of whether fast switching is enabled.
Limiting the number of equal-cost paths can save memory on routers with limited memory or very large configurations. Additionally, in networks with a large number of multiple paths and systems with limited ability to cache out-of-sequence packets, performance might suffer when traffic is split between many paths.
To set the maximum number of paths, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx maximum-paths paths | Set the maximum number of equal-cost paths to a destination. |
Round-robin load sharing is the default behavior when you configure ipx maximum-paths to a value greater than 1. Round-robin load sharing works by sending data packets over successive equal cost paths without regard to individual end hosts or user sessions. Path utilization increases transmission speed, but, because packets destined for a given end host may take different paths, they might arrive out of order.
You can address the possibility of packets arriving out of order by enabling per-host load sharing. With per-host load sharing, the router still uses multiple, equal-cost paths to achieve load sharing; however, packets for a given end host are guaranteed to take the same path, even if multiple, equal-cost paths are available. Traffic for different end hosts tend to take different paths, but true load balancing is not guaranteed. The exact degree of load balancing achieved depends on the exact nature of the workload.
To enable per-host load sharing, use the following commands in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | ipx maximum-paths paths | Set the maximum number of equal cost paths to a destination to a value greater than 1. |
Step2 | ipx per-host-load-share | Enable per-host load sharing. |
You can specify the use of broadcast messages as described in the following sections:
Routers normally block all broadcast requests and do not forward them to other network segments, therefore preventing the degradation of performance over the entire network. However, you can enable the router to forward broadcast packets to helper addresses on other network segments.
Helper addresses specify the network and node on another segment that can receive unrecognized broadcast packets. Unrecognized broadcast packets are non-RIP and non-SAP packets that are not addressed to the local network.
When the interface configured with helper addresses receives an unrecognized broadcast packet, CiscoIOS software changes the broadcast packet to a unicast and sends the packet to the specified network and node on the other network segment. Unrecognized broadcast packets are not flooded everywhere in your network.
With helper addresses, there is no limit on the number of hops that the broadcast packet can make.
Cisco IOS supports fast switching of helpered broadcast packets.
You use helper addresses when you want to forward broadcast packets (except Type 20 packets) to other network segments.
Forwarding broadcast packets to helper addresses is sometimes useful when a network segment does not have an end-host capable of servicing a particular type of broadcast request. You can specify the address of a server, network, or networks that can process the broadcast packet.
You use Type 20 packet propagation to forward Type 20 packets to other network segments. For information on forwarding Type20 packets, see the "Controlling the Forwarding of Type 20 Packets" section earlier in this chapter.
You can use helper addresses and Type 20 propagation together in your network. Use helper addresses to forward non-Type 20 broadcast packets and use Type 20 propagation to forward Type20 broadcast packets.
Using helper addresses is not Novell-compliant. However, it does allow routers to forward broadcast packets to network segments that can process them without flooding the network. It also allows routers running versions of Cisco IOS that do not support Type 20 propagation to forward Type 20 packets.
The Cisco IOS software supports all-networks flooded broadcasts (sometimes referred to as all-netsflooding). These are broadcast messages that are forwarded to all networks. Use all-nets flooding carefully and only when necessary, because the receiving networks may be overwhelmed to the point that no other traffic can traverse them.
Use the ipx helper-list command, described earlier in this chapter, to define access lists that control which broadcast packets get forwarded.
To specify a helper address for forwarding broadcast packets, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx helper-address network.node |
You can specify multiple helper addresses on an interface.
For an example of using helper addresses to forward broadcast messages, see the "Helper Facilities to Control Broadcast Examples" section at the end of this chapter.
By default, Cisco IOS software switches packets that have been helpered to the broadcast address. To enable fast switching of these IPX-directed broadcast packets, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx broadcast-fastswitching |
By default, fast switching is enabled on all interfaces that support fast switching.
Fast switching allows higher throughput by switching a packet using a cache created by previous packets. Fast switching is enabled by default on all interfaces that support fast switching.
Packet transfer performance is generally better when fast switching is enabled. However, you might want to disable fast switching in order to save memory space on interface cards and to help avoid congestion when high-bandwidth interfaces are writing large amounts of information to low-bandwidth interfaces.
|
CautionTurning off fast switching increases system overhead. |
To disable IPX fast switching, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
no ipx route-cache |
Adjusting the route cache allows you to control the size of the route cache, reduce memory consumption, and improve router performance. You accomplish these tasks by controlling the route cache size and invalidation. The following sections describe these optional tasks:
You can limit the number of entries stored in the IPX route cache to free up router memory and aid router processing.
Storing too many entries in the route cache can use a significant amount of router memory, causing router processing to slow. This situation is most common on large networks that run network management applications for NetWare.
For example, if a network management station is responsible for managing all clients and servers in a very large (greater than 50,000 nodes) Novell network, the routers on the local segment can become inundated with route cache entries. You can set a maximum number of route cache entries on these routers to free up router memory and aid router processing.
To set a maximum limit on the number of entries in the IPX route cache, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx route-cache max-size size | Set a maximum limit on the number of entries in the IPX route cache. |
If the route cache has more entries than the specified limit, the extra entries are not deleted. However, they may be removed if route cache invalidation is in use. See the "Controlling Route Cache Invalidation" section later in this chapter for more information on invalidating route cache entries.
You can configure the router to invalidate fast-switch cache entries that are inactive. If these entries remain invalidated for 1 minute, the router purges the entries from the route cache.
Purging invalidated entries reduces the size of the route cache, reduces memory consumption, and improves router performance. Also, purging entries helps ensure accurate route cache information.
You specify the period of time that valid fast-switch cache entries must be inactive before the router invalidates them. You can also specify the number of cache entries that the router can invalidate per minute.
To configure the router to invalidate fast-switch cache entries that are inactive, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx route-cache inactivity-timeout period [rate] | Invalidate fast-switch cache entries that are inactive. |
When you use the ipx route-cache inactivity-timeout command with the ipx route-cache max-size command, you can ensure a small route cache with fresh entries.
You can adjust the use of default routes in your IPX network. You can turn off the use of network number -2 as the default route. You can also specify that the router advertise only default RIP routes out an interface. The following sections describe these optional tasks:
The default route is used when a route to any destination network is unknown. All packets for which a route to the destination address is unknown are forwarded to the default route. By default, IPX treats network number -2 (0xFFFFFFFE) as the default route.
For an introduction to default routes, see the "IPX Default Routes" section earlier in this chapter. For more background information on how to handle IPX default routes, refer to the Novell NetWare Link Services Protocol (NLSP) Specification, Revision 1.1 publication.
By default, Cisco IOS software treats network -2 as the default route. You can disable this default behavior and use network -2 as a regular network number in your network.
To disable the use of network number -2 as the default route, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
no ipx default-route |
Unless configured otherwise, all known RIP routes are advertised out each interface. However, you can choose to advertise only the default RIP route if it is known, therefore greatly reducing the CPU overhead when routing tables are large.
To advertise only the default route via an interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx advertise-default-route-only network |
Some IPX end hosts accept only even-length Ethernet packets. If the length of a packet is odd, the packet must be padded with an extra byte so that end host can receive it. By default, Cisco IOS pads odd-length Ethernet packets.
However, there are cases in certain topologies where nonpadded Ethernet packets are forwarded onto a remote Ethernet network. Under specific conditions, you can enable padding on intermediate media as a temporary workaround for this problem. Note that you should perform this task only under the guidance of a customer engineer or other service representative.
To enable the padding of odd-length packets, use the following commands in interface configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | no ipx route-cache | Disable fast switching. |
Step2 | ipx pad-process-switched-packets |
You can administratively shut down an IPX network in two ways. In the first way, the network still exists in the configuration, but is not active. When shutting down, the network sends out update packets informing its neighbors that it is shutting down, therefore allowing the neighboring systems to update their routing, SAP, and other tables without needing to wait for routes and services learned via this network to time out.
To shut down an IPX network such that the network still exists in the configuration, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
ipx down network | Shut down an IPX network, but have the network still exist in the configuration. |
To shut down an IPX network and remove it from the configuration, use one of the following commands in interface configuration mode:
When multiple networks are configured on an interface and you want to shut down one of the secondary networks and remove it from the interface, use the second command in the previous table specifying the network number of one of the secondary networks.
For an example of shutting down an IPX network, see the "IPX Routing Examples" section at the end of this chapter.
IPX accounting enables you to collect information about IPX packets and the number of bytes that are switched through the Cisco IOS software. You collect information based on the source and destination IPX address. IPX accounting tracks only IPX traffic that is routed out an interface on which IPX accounting is configured; it does not track traffic generated by or terminated at the router itself.
The Cisco IOS software maintains two accounting databases: an active database and a checkpoint database. The active database contains accounting data tracked until the database is cleared. When the active database is cleared, its contents are copied to the checkpoint database. Using these two databases together enables you to monitor both current traffic and traffic that has previously traversed the router.
Process and fast switching support IPX accounting statistics. Autonomous and silicon switching engine (SSE) switching do not support IPX accounting statistics.
IPX access lists support IPX accounting statistics.
You can configure IPX accounting by performing the tasks in the following sections. The first task is required. The remaining tasks are optional.
To enable IPX accounting, use the following command in interface configuration mode:
| Command | Purpose |
ipc accounting |
To customize IPX accounting, use one or more of the following commands in global configuration mode:
Transit entries are entries in the database that do not match any of the networks specified by the ipx accounting-list commands.
If you enable IPX accounting on an interface but do not specify an accounting list, IPX accounting tracks all traffic through the interface (all transit entries) up to the accounting threshold limit.
For an example of how to configure IPX accounting, see the "IPX Accounting Example" section at the end of this chapter.
Cisco IOS software supports routing IPX between Ethernet-emulated LANs and Token Ring-emulated LANs. For more information on emulated LANs and routing IPX between them, refer to the "Configuring LAN Emulation" chapter of the Cisco IOS Switching Services Configuration Guide.
Cisco IOS software supports routing IPX between VLANs. Users with Novell NetWare environments can configure any one of the four IPX Ethernet encapsulations to be routed using the Inter-Switch Link (ISL) encapsulation across VLAN boundaries. For more information on VLANs and routing IPX between them over ISL, refer to the "Configuring Routing Between VLANs with ISL Encapsulation" chapter of the Cisco IOS Switching Services Configuration Guide.
Cisco IOS software supports IPX Multilayer Switching (MLS). For more information on IPX MLS, refer to the "Multilayer Switching" chapter of the Cisco IOS Switching Services Configuration Guide.
You can monitor and maintain your IPX network by performing the optional tasks described in the following sections:
You can perform one or more of these general monitoring and maintaining tasks as described in the following sections:
To monitor and maintain caches, tables, interfaces, or statistics in a Novell IPX network, use one or more of the following commands in EXEC mode:
| Command | Purpose |
|---|---|
clear ipx cache | |
clear ipx route [network | *] | |
clear ipx traffic | Clear IPX traffic counters. |
show ipx cache | |
show ipx interface [type number] | Display the status of the IPX interfaces configured in the router and the parameters configured on each interface. |
show ipx route [network] [default] [detailed] | |
show ipx servers [unsorted | sorted [name | net | type]] | |
show ipx traffic [since {bootup | show}]
| Display information about the number and type of IPX packets sent and received. |
show sse summary | Display a summary of SSE statistics. |
The Cisco IOS software can send Cisco pings and standard Novell pings as defined in the NLSP specification or diagnostic request packets. By default, the software generates Cisco pings. To choose the ping type, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
ipx ping-default {cisco | novell | diagnostic}
|
The IPX diagnostic ping feature addresses diagnostic related issues by accepting and processing unicast or broadcast diagnostic packets. It makes enhancements to the current IPX ping command to ping other stations using the diagnostic packets and display the configuration information in the response packet.
|
NoteWhen a ping is sent from one station to another, the response is expected to come back immediately; when the ipx ping-default command is set to diagnostics, the response could consist of more than one packet and each node is expected to respond within 0.5 seconds of receipt of the request. Due to the absence of an end-of-message flag, there is a delay and the requester must wait for all responses to arrive. Therefore, in verbose mode there may be a brief delay of 0.5 seconds before the response data is displayed. The ipx ping command using the diagnostic keyword can be used to conduct a reachability test and should not be used to measure accurate round-trip delay. |
To initiate a ping, use one of the following commands in EXEC mode:
| Command | Purpose |
|---|---|
ping ipx network.node | Diagnose basic IPX network connectivity (user-level command). |
ping [ipx] [network.node] | Diagnose basic IPX network connectivity (privileged command). |
To trace the IPX destination and measure roundtrip delays, use the following command in either user or privileged EXEC mode:
| Command | Purpose |
|---|---|
trace [protocol] [destination] | Trace packet routes through the network (user or privileged). |
|
NoteIn user EXEC mode, you are not allowed to change the trace route timeout interval, probe count, minimum and maximum time to live, and verbose mode. To do so, use the trace command in privileged EXEC mode. |
To monitor and maintain Enhanced IGRP on an IPX network, use one or more of the following commands in EXEC mode:
You can enable the logging of neighbor adjacency changes to monitor the stability of the routing system and to help you detect problems. By default, adjacency changes are not logged.
To enable logging of Enhanced IGRP neighbor adjacency changes, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
log-neighbor-changes |
To monitor and maintain NLSP on an IPX network, use one or more of the following commands in EXEC mode
:
You can allow NLSP to generate a log message when an NLSP adjacency changes state (up or down). Generating a log message may be very useful when monitoring large networks. Messages are logged using the system error message facility. Messages are of the following form:
%CLNS-5-ADJCHANGE: NLSP: Adjacency to 0000.0000.0034 (Serial0) Up, new adjacency
%CLNS-5-ADJCHANGE: NLSP: Adjacency to 0000.0000.0034 (Serial0) Down, hold time expired
To generate log messages when an NLSP adjacency changes state, use the following command in router configuration mode:
| Command | Purpose |
|---|---|
log-adjacency-changes | Log NLSP adjacency state changes. |
To monitor the NHRP cache or traffic, use either of the following commands in EXEC mode:
| Command | Purpose |
|---|---|
show ipx nhrp [dynamic | static] [type number] | Display the IPX NHRP cache, optionally limited to dynamic or static cache entries for a specific interface. |
show ipx nhrp traffic | Display NHRP traffic statistics. |
The NHRP cache can contain static entries caused by statically configured addresses and dynamic entries caused by the Cisco IOS software learning addresses from NHRP packets. To clear static entries, use the no ipx nhrp map command. To clear the NHRP cache of dynamic entries, use the following command in EXEC mode:
| Command | Purpose |
|---|---|
clear ipx nhrp | Clear the IPX NHRP cache of dynamic entries. |
To monitor and maintain IPX accounting in your IPX network, use the following commands in EXEC mode:
Posted: Mon Jul 17 13:01:20 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.