Feedback
Table Of Contents
ipx input-network-filter (RIP)
ipx netbios input-access-filter
ipx netbios output-access-filter
ipx netbios-socket-input-checks
ipx output-network-filter (RIP)
ipx pad-process-switched-packets
ipx potential-pseudonode (NLSP)
ipx route-cache inactivity-timeout
ipx route-cache update-timeout
ipx input-network-filter (RIP)
Note
Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx input-network-filter (RIP) command is not supported in Cisco IOS software.
To control which networks are added to the Cisco IOS software routing table, use the ipx input-network-filter command in interface configuration mode. To remove the filter from the interface, use the no form of this command.
ipx input-network-filter {access-list-number | name}
no ipx input-network-filter {access-list-number | name}
Syntax Description
Defaults
No filters are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx input-network-filter command controls which networks are added to the routing table based on the networks learned in incoming IPX routing updates (RIP updates) on the interface.
You can issue only one ipx input-network-filter command on each interface.
Examples
In the following example, access list 876 controls which networks are added to the routing table when IPX routing updates are received on Ethernet interface 1. Routing updates for network 1b will be accepted. Routing updates for all other networks are implicitly denied and are not added to the routing table.
access-list 876 permit 1binterface ethernet 1ipx input-network-filter 876The following example is a variation of the preceding that explicitly denies network 1a and explicitly allows updates for all other networks:
access-list 876 deny 1a access-list 876 permit -1Related Commands
ipx input-sap-filter
Note
To control which services are added to the Cisco IOS software SAP table, use the ipx input-sap-filter command in interface configuration mode. To remove the filter, use the no form of this command.
ipx input-sap-filter {access-list-number | name}
no ipx input-sap-filter {access-list-number | name}
Syntax Description
Defaults
No filters are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx input-sap-filter command filters all incoming service advertisements received by the router. This is done prior to accepting information about a service.
You can issue only one ipx input-sap-filter command on each interface.
When configuring SAP filters for NetWare 3.11 and later servers, use the server's internal network and node number (the node number is always 0000.0000.0001) as its address in the access-list (SAP filtering) command. Do not use the network.node address of the particular interface board.
Examples
The following example denies service advertisements about the server at address 3c.0800.89a1.1527, but accepts information about all other services on all other networks:
access-list 1000 deny 3c.0800.89a1.1527access-list 1000 permit -1!interface ethernet 0ipx input-sap-filter 1000Related Commands
ipx internal-network
Note
To set an internal network number for use by NetWare Link Services Protocol (NLSP) and IPXWAN, use the ipx internal-network command in global configuration mode. To remove an internal network number, use the no form of this command.
ipx internal-network network-number
no ipx internal-network [network-number]
Syntax Description
Defaults
No internal network number is set.
Command Modes
Global configuration
Command History
Usage Guidelines
An internal network number is a network number assigned to the router. This network number must be unique within the internetwork.
You must configure an internal network number on each device on an NLSP-capable network for NLSP to operate.
When you set an internal network number, the Cisco IOS software advertises the specified network out all interfaces. It accepts packets destined to that network at the address internal-network.0000.0000.0001.
Examples
The following example assigns internal network number e001 to the local router:
ipx routingipx internal-network e001Related Commands
ipx router
Specifies the routing protocol to use.
ipx routing
Enables IPX routing.
ipx ipxwan
Note
To enable the IPX wide-area network (IPXWAN) protocol on a serial interface, use the ipx ipxwan command in interface configuration mode. To disable the IPXWAN protocol, use the no form of this command.
ipx ipxwan [local-node {network-number | unnumbered} local-server-name retry-interval retry-limit]
no ipx ipxwan
Syntax Description
Defaults
IPXWAN is disabled.
If you enable IPXWAN, the default is unnumbered.
Command Modes
Interface configuration
Command History
Usage Guidelines
If you omit all optional arguments and keywords, the ipx ipxwan command defaults to ipx ipxwan 0 unnumbered router-name (which is equivalent to ipx ipxwan 0 local-server-name), where router-name is the name of the router as configured with the hostname global configuration command. For this configuration, the show ipx interface command displays
ipx ipxwan 0 0local-server-name.If you enter a value of 0 for the network-number argument, the output of the show running-config EXEC command does not show the 0 but rather reports this value as "unnumbered."
The name of each device on each side of the link must be different.
IPXWAN is a start-up end-to-end options negotiations protocol. When a link comes up, the first IPX packets sent across are IPXWAN packets negotiating the options for the link. When the IPXWAN options have been successfully determined, normal IPX traffic starts. The three options negotiated are the link IPX network number, internal network number, and link delay (ticks) characteristics. The side of the link with the higher local-node number (internal network number) gives the IPX network number and delay to use for the link to the other side. Once IPXWAN finishes, no IPXWAN packets are sent unless link characteristics change or the connection fails. For example, if the IPX delay is changed from the default setting, an IPXWAN restart will be forced.
To enable the IPXWAN protocol on a serial interface, you must not have configured an IPX network number (using the ipx network interface configuration command) on that interface.
To control the delay on a link, use the ipx delay interface configuration command. If you issue this command when the serial link is already up, the state of the link will be reset and renegotiated.
Examples
The following example enables IPXWAN on serial interface 0:
interface serial 0encapsulation pppipx ipxwanThe following example enables IPXWAN on serial interface 1 on device CHICAGO-AS. When the link comes up, CHICAGO-AS will be the master because it has a larger internal network number. It will give the IPX number 100 to NYC-AS to use as the network number for the link. The link delay, in ticks, will be determined by the exchange of packets between the two access servers.
On the local access server (CHICAGO-AS):
interface serial 1no ipx networkencapsulation pppipx ipxwan 6666 100 CHICAGO-ASOn the remote router (NYC-AS):
interface serial 0no ipx networkencapsulation pppipx ipxwan 1000 101 NYC-ASRelated Commands
ipx ipxwan error
Note
To define how to handle IPX wide-area network (IPXWAN) when IPX fails to negotiate properly at link startup, use the ipx ipxwan error command in interface configuration mode. To restore the default, use the no form of this command.
ipx ipxwan error [reset | resume | shutdown]
no ipx ipxwan error [reset | resume | shutdown]
Syntax Description
Defaults
The link is reset.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the ipx ipxwan error command to define what action to take if the IPXWAN startup negotiation fails.
Examples
In the following example, the serial link will be shut down if the IPXWAN startup negotiation fails after three attempts spaced 20 seconds apart:
interface serial 0encapsulation pppipx ipxwanipx ipxwan error shutdownRelated Commands
ipx ipxwan
Enables the IPXWAN protocol on a serial interface.
ipx ipxwan static
Negotiates static routes on a link configured for IPXWAN.
ipx ipxwan static
Note
To negotiate static routes on a link configured for IPX wide-area network (IPXWAN), use the ipx ipxwan static command in interface configuration mode. To disable static route negotiation, use the no form of this command.
ipx ipxwan static
no ipx ipxwan static
Syntax Description
This command has no arguments or keywords.
Defaults
Static routing is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you specify the ipx ipxwan static command, the interface negotiates static routing on the link. If the router at the other side of the link is not configured to negotiate for static routing, the link will not initialize.
Examples
The following example enables static routing with IPXWAN:
interface serial 0encapsulation pppipx ipxwanipx ipxwan staticRelated Commands
ipx ipxwan
Enables the IPXWAN protocol on a serial interface.
ipx ipxwan error
Defines how to handle IPXWAN when IPX fails to negotiate properly at link startup.
ipx link-delay
Note
To specify the link delay, use the ipx link-delay command in interface configuration mode. To return to the default link delay, use the no form of this command.
ipx link-delay microseconds
no ipx link-delay microseconds
Syntax Description
Defaults
No link delay (delay of 0).
Command Modes
Interface configuration
Command History
Usage Guidelines
The link delay you specify replaces the default value or overrides the value measured by IPXWAN when it starts.
Examples
The following example sets the link delay to 20 microseconds:
ipx link-delay 20Related Commands
ipx linkup-request (RIP)
Note
To enable the sending of a general RIP and/or SAP query when an interface comes up, use the ipx linkup-request command in interface configuration mode. To disable the sending of a general RIP and/or SAP query when an interface comes up, use the no form of this command.
ipx linkup-request {rip | sap}
no ipx linkup-request {rip | sap}
Syntax Description
rip
Enables the sending of a general RIP query when an interface comes up.
sap
Enables the sending of a general SAP query when an interface comes up.
Defaults
General RIP and SAP queries are sent.
Command Modes
Interface configuration
Command History
Usage Guidelines
Under normal operation, when using serial or other point-to-point links, the router sends RIP and SAP information twice when an interface comes up. The RIP and SAP information is sent as soon as the link is up and is sent again when the router receives a general RIP query from the other end of the connection. By disabling the ipx linkup-request command, the router sends the RIP and SAP information once, instead of twice.
Examples
The following example configures the router to disable the general query for both RIP and SAP on serial interface 0:
interface serial 0no ipx linkup-request ripno ipx linkup-request sapRelated Commands
ipx update interval
Adjusts the RIP or SAP update interval.
ipx update sap-after-rip
Configures the router to send a SAP update immediately following a RIP broadcast.
ipx maximum-hops (RIP)
Note
To set the maximum hop count allowed for IPX packets, use the ipx maximum-hops command in global configuration mode. To return to the default number of hops, use the no form of this command.
ipx maximum-hops hops
no ipx maximum-hops hops
Syntax Description
Defaults
16 hops
Command Modes
Global configuration
Command History
Usage Guidelines
Packets whose hop count is equal to or greater than that specified by the ipx maximum-hops command are dropped.
In periodic RIP updates, the Cisco IOS software never advertises any network with a hop count greater than 15. However, using protocols other than RIP, the software might learn routes that are farther away than 15 hops. The ipx maximum-hops command defines the maximum number of hops that the software will accept as reachable, as well as the maximum number of hops that an IPX packet can traverse before it is dropped by the software. Also, the software will respond to a specific RIP request for a network that is reachable at a distance of greater than 15 hops.
Examples
The following command configures the software to accept routes that are up to 64 hops away:
ipx maximum-hops 64ipx maximum-paths
Note
To set the maximum number of equal-cost paths that the Cisco IOS software uses when forwarding packets, use the ipx maximum-paths command in global configuration mode. To restore the default value, use the no form of this command.
ipx maximum-paths paths
no ipx maximum-paths
Syntax Description
paths
Maximum number of equal-cost paths which the Cisco IOS software will use. It can be a number from 1 to 512. The default value is 1.
Defaults
1 path
Command Modes
Global configuration
Command History
Usage Guidelines
The ipx maximum-paths command increases throughput by allowing the software to choose among several equal-cost, parallel paths. (Note that when paths have differing costs, the software chooses lower-cost routes in preference to higher-cost routes.)
When per-host load sharing is disabled, IPX performs load sharing on a packet-by-packet basis in round-robin fashion, regardless of whether you are using fast switching or process switching. 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.
Limiting the number of equal-cost paths can save memory on routers with limited memory or with 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.
When you enable per-host load sharing, IPX performs load sharing by transmitting traffic across multiple, equal-cost paths while guaranteeing that packets for a given end host always take the same path. Per-host load sharing decreases the possibility that successive packets to a given end host will arrive out of order.
With per-host load balancing, the number of equal-cost paths set by the ipx maximum-paths command must be greater than one; otherwise, per-host load sharing has no effect.
Examples
In the following example, the software uses up to three parallel paths:
ipx maximum-paths 3Related Commands
ipx delay
Sets the tick count.
ipx per-host-load-share
Enables per-host load sharing.
show ipx route
Displays the contents of the IPX routing table.
ipx nasi-server enable
Note
To enable NetWare Asynchronous Services Interface (NASI) clients to connect to asynchronous devices attached to your router, use the ipx nasi-server enable command in global configuration mode. To prevent NASI clients from connecting to asynchronous devices through a router, use the no form of this command.
ipx nasi-server enable
no ipx nasi-server enable
Syntax Description
This command has no arguments or keywords.
Command Default
NASI is not enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
When you enter this command, NASI clients can connect to any port on the router, other than the console port, to access network resources. When the user on the NASI client uses the Windows or DOS application to connect to the router, a list of available tty and vty lines appear, beginning with tty1. The user can select the desired outgoing tty or vty port.
To to enable a username and password prompt for authentication, authorization, and accounting purposes, you can configure TACACS+ security on the router, after the user on the NASI client selects a tty or vty port.
Examples
The following example shows a minimum configuration to enable NASI clients dial-in access with TACACS+ authentication:
ipx routingipx internal-network ncs001interface ethernet 0ipx network 1ipx nasi-server enable! enable TACACS+ authentication for NASI clients using the list name swamiaaa authentication nasi swami tacacs+line 1 8modem inoutRelated Commands
ipx netbios input-access-filter
Note
To control incoming IPX NetBIOS FindName messages, use the ipx netbios input-access-filter command in interface configuration mode. To remove the filter, use the no form of this command.
ipx netbios input-access-filter {host | bytes} name
no ipx netbios input-access-filter {host | bytes} name
Syntax Description
Defaults
No filters are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can issue only one ipx netbios input-access-filter host and one ipx netbios input-access-filter bytes command on each interface.
These filters apply only to IPX NetBIOS FindName packets. They have no effect on LLC2 NetBIOS packets.
Examples
The following example filters packets arriving on Token Ring interface 1 using the NetBIOS access list named engineering:
netbios access-list host engineering permit eng*netbios access-list host engineering deny manu*interface tokenring 1ipx netbios input-access-filter engineeringRelated Commands
ipx netbios output-access-filter
Note
To control outgoing NetBIOS FindName messages, use the ipx netbios output-access-filter command in interface configuration mode. To remove the filter, use the no form of this command.
ipx netbios output-access-filter {host | bytes} name
no ipx netbios output-access-filter {host | bytes} name
Syntax Description
Defaults
No filters are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can issue only one ipx netbios output-access-filter host and one ipx netbios output-access-filter bytes command on each interface.
These filters apply only to IPX NetBIOS FindName packets. They have no effect on LLC2 NetBIOS packets.
Examples
The following example filters packets leaving Token Ring interface 1 using the NetBIOS access list named engineering:
netbios access-list bytes engineering permit 20 AA**04interface token 1ipx netbios output-access-filter bytes engineeringRelated Commands
ipx netbios-socket-input-checks
Note
To enable additional checks that are performed on Network Basic Input/Output System (NetBIOS) packets that do not conform fully to Novell Type20 NetBIOS packets, use the ipx netbios-socket-input-checks command in global configuration mode. To disable the additional checking, use the no form of this command.
ipx netbios-socket-input-checks
no ipx netbios-socket-input-checks
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
When you use the ipx netbios-socket-input-checks command to enable additional checks on NetBIOS packets that do not fully conform to Novell Type20 NetBIOS packets, the same checks that are performed on Type20 packets to avoid broadcast loops are performed for any packet that does not have the netBIOS socket, even if it is not a Novell Type20 packet.
Note
Examples
The following example enables the additional checks on NetBIOS packets:
ipx netbios-socket-input-checksRelated Commands
ipx network
Note
To enable IPX routing on a particular interface and to optionally select the type of encapsulation (framing), use the ipx network command in interface configuration mode. To disable IPX routing, use the no form of this command.
ipx network network [encapsulation encapsulation-type [secondary]]
no ipx network network [encapsulation encapsulation-type]
Syntax Description
network
Network number. This is an 8-digit hexadecimal number that uniquely identifies a network cable segment. It can be a number in the range 1 to FFFFFFFD.
You do not need to specify leading zeros in the network number. For example, for the network number 000000AA you can enter AA.
encapsulation encapsulation-type
(Optional) Type of encapsulation (framing). For a list of possible encapsulation types, see Table 12.
secondary
(Optional) Indicates an additional (secondary) network configured after the first (primary) network.
Defaults
IPX routing is disabled.
Encapsulation types:
For Ethernet: novell-ether
For Token Ring: sap
For FDDI: snap
For serial: hdlcIf you use NetWare Version 4.0 and Ethernet, you must change the default encapsulation type from novell-ether to sap.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx network command allows you to configure a single logical network on a physical network or more than one logical network on the same physical network (network cable segment). Each network on a given interface must have a different encapsulation type.
Note
The first network you configure on an interface is considered to be the primary network. Any additional networks are considered to be secondary networks; these must include the secondary keyword.
Note
You can configure an IPX network on any supported interface as long as all the networks on the same physical interface use a distinct encapsulation type. For example, you can configure up to four IPX networks on a single Ethernet cable because Ethernet supports four encapsulation types.
The interface processes only packets with the correct encapsulation and the correct network number. IPX networks that use encapsulations can be present on the physical network. The only effect on the router is that it uses some processing time to examine packets to determine whether they have the correct encapsulation.
All logical networks on an interface share the same set of configuration parameters. For example, if you change the IPX RIP update time on an interface, you change it for all networks on that interface.
When you define multiple logical networks on the same physical network, IPX treats each encapsulation as if it were a separate physical network. This means, for example, that IPX sends RIP updates and SAP updates for each logical network.
Caution
The ipx network command is useful when migrating from one type of encapsulation to another. If you are using it for this purpose, you should define the new encapsulation on the primary network.
Note
To delete all networks on an interface, use the following command:
no ipx network
Deleting the primary network with the following command also deletes all networks on that interface. The argument number is the number of the primary network.
no ipx network number
To delete a secondary network on an interface, use one of the following commands. The argument number is the number of a secondary network.
no ipx network number
no ipx network number encapsulation encapsulation-type
Novell's FDDI_RAW encapsulation is common in bridged or switched environments that connect Ethernet-based Novell end hosts via a FDDI backbone. Packets with FDDI_RAW encapsulation are classified as Novell packets and are not automatically bridged when you enable both bridging and IPX routing. Additionally, you cannot configure FDDI_RAW encapsulation on an interface configured for IPX autonomous or silicon switching engine (SSE) switching. Similarly, you cannot enable IPX autonomous or SSE switching on an interface configured with FDDI_RAW encapsulation.
With FDDI_RAW encapsulation, platforms that do not use CBUS architecture support fast switching. Platforms using CBUS architecture support only process switching of novell-fddi packets received on an FDDI interface.
Table 12 describes the types of encapsulation available for specific interfaces.
Examples
The following example uses subinterfaces to create four logical networks on Ethernet interface 0. Each subinterface has a different encapsulation. Any interface configuration parameters that you specify on an individual subinterface are applied to that subinterface only.
ipx routinginterface ethernet 0ipx network 1 encapsulation novell-etherinterface ethernet 0.1ipx network 2 encapsulation snapinterface ethernet 0.2ipx network 3 encapsulation arpainterface ethernet 0ipx network 4 encapsulation sapThe following example uses primary and secondary networks to create the same four logical networks as shown previously in this section. 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.
ipx routingipx network 1 encapsulation novell-etheripx network 2 encapsulation snap secondaryipx network 3 encapsulation arpa secondaryipx network 4 encapsulation sap secondaryThe following example provides information about maximum supported packet sizes described in the "Caution." If the primary network is configured with SAP encapsulation, IPX packets greater than 1497 are dropped because one of the following situations exists:
•
•
The following data compares some maximum sizes of IPX datagrams:
Novell-Ethernet is 1518 - 12 -2 (length) -4 (CRC) = 1500
SAP is 1518 - 12 -2 (length) -3 (SAP header) -4 (CRC) = 1497
SNAP is 1518 - 12 -2 (length) -8 (SNAP header) -4 (CRC) = 1492
ARPA is 1518 -12 -2 (length) -2 (type) -4 (CRC) =1500
Twelve bytes represents the source address and destination address in the Ethernet frame.
The following example enables IPX routing on FDDI interfaces 0.2 and 0.3. On FDDI interface 0.2, the encapsulation type is SNAP. On FDDI interface 0.3, the encapsulation type is Novell's FDDI_RAW.
ipx routinginterface fddi 0.2 enc sde 2ipx network f02 encapsulation snapinterface fddi 0.3 enc sde 3ipx network f03 encapsulation novell-fddiRelated Commands
ipx encapsulation
Sets the Ethernet frame type of the interface to that of the local file server.
ipx routing
Enables IPX routing.
ipx nhrp authentication
Note
To configure the authentication string for an interface using Next Hop Resolution Protocol (NHRP), use the ipx nhrp authentication command in interface configuration mode. To remove the authentication string, use the no form of this command.
ipx nhrp authentication string
no ipx nhrp authentication [string]
Syntax Description
string
Authentication string configured for the source and destination stations that controls whether NHRP stations allow intercommunication. The string can be up to eight characters long.
Defaults
No authentication string is configured; the Cisco IOS software adds no authentication option to NHRP packets it generates.
Command Modes
Interface configuration
Command History
Usage Guidelines
All routers configured with NHRP on a fabric (for an interface) must share the same authentication string.
Examples
In the following example, the authentication string specialxx must be configured in all devices using NHRP on the interface before NHRP communication occurs:
ipx nhrp authentication specialxxipx nhrp holdtime
Note
To change the number of seconds for which Next Hop Resolution Protocol (NHRP) nonbroadcast multiaccess (NBMA) addresses are advertised as valid in authoritative NHRP responses, use the ipx nhrp holdtime command in interface configuration mode. To restore the default value, use the no form of this command.
ipx nhrp holdtime seconds-positive [seconds-negative]
no ipx nhrp holdtime [seconds-positive [seconds-negative]]
Syntax Description
Defaults
7200 seconds (2 hours) for both arguments.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx nhrp holdtime command affects authoritative responses only. The advertised holding time is the length of time for which the Cisco IOS software tells other routers to keep information that it is provided in authoritative NHRP responses. The cached IPX-to-NBMA address mapping entries are discarded after the holding time expires.
The NHRP cache can contain static and dynamic entries. The static entries never expire. Dynamic entries expire regardless of whether they are authoritative or nonauthoritative.
If you want to change the valid time period for negative NHRP responses, you must also include a value for positive NHRP responses, as the arguments are position-dependent.
Examples
The following example advertises NHRP NBMA addresses as valid in positive authoritative NHRP responses for one hour:
ipx nhrp holdtime 3600The following example advertises NHRP NBMA addresses as valid in negative authoritative NHRP responses for one hour and in positive authoritative NHRP responses for two hours:
ipx nhrp holdtime 7200 3600ipx nhrp interest
Note
To control which IPX packets can trigger sending a Next Hop Resolution Protocol (NHRP) request, use the ipx nhrp interest command in interface configuration mode. To restore the default value, use the no form of this command.
ipx nhrp interest access-list-number
no ipx nhrp interest [access-list-number]
Syntax Description
Defaults
All non-NHRP packets can trigger NHRP requests.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command with the access-list command to control which IPX packets trigger NHRP requests.
Examples
In the following example, any NetBIOS traffic can cause NHRP requests to be sent, but no other IPX packets will cause NHRP requests:
ipx nhrp interest 901access-list 901 permit 20Related Commands
access-list (IPX extended)
Defines an extended Novell IPX access list.
access-list (IPX standard)
Defines a standard IPX access list.
ipx nhrp map
Note
To statically configure the IPX-to-NBMA address mapping of IPX destinations connected to a nonbroadcast multiaccess (NBMA) network, use the ipx nhrp map command in interface configuration mode. To remove the static entry from NHRP cache, use the no form of this command.
ipx nhrp map ipx-address nbma-address
no ipx nhrp map ipx-address nbma-address
Syntax Description
Defaults
No static IPX-to-NBMA cache entries exist.
Command Modes
Interface configuration
Command History
Usage Guidelines
You will probably have to configure at least one static mapping in order to reach the Next Hop Server. Repeat this command to statically configure multiple IPX-to-NBMA address mappings.
Examples
The following example statically configures this station in an SMDS network to be served by two Next Hop Servers 1.0000.0c14.59ef and 1.0000.0c14.59d0. The NBMA address for 1.0000.0c14.59ef is statically configured to be c141.0001.0001 and the NBMA address for 1.0000.0c14.59d0 is c141.0001.0002.
interface serial 0ipx nhrp nhs 1.0000.0c14.59efipx nhrp nhs 1.0000.0c14.59d0ipx nhrp map 1.0000.0c14.59ef c141.0001.0001ipx nhrp map 1.0000.0c14.59d0 c141.0001.0002Related Commands
ipx nhrp max-send
Note
To change the maximum frequency at which Next Hop Resolution Protocol (NHRP) packets can be sent, use the ipx nhrp max-send command in interface configuration mode. To restore this frequency to the default value, use the no form of this command.
ipx nhrp max-send pkt-count every interval
no ipx nhrp max-send
Syntax Description
pkt-count
Number of packets for which can be transmitted in the range 1 to 65,535.
every interval
Time (in seconds) in the range 10 to 65,535. Default is 10 seconds.
Defaults
pkt-count = 5 packets
interval = 10 secondsCommand Modes
Interface configuration
Command History
Usage Guidelines
The software maintains a per interface quota of NHRP packets that can be transmitted. NHRP traffic, whether locally generated, or forwarded, cannot be sent at a rate that exceeds this quota. The quota is replenished at the rate specified by the interval argument.
Examples
In the following example, only one NHRP packet can be sent out serial interface 0 each minute:
interface serial 0 ipx nhrp max-send 1 every 60Related Commands
ipx nhrp network-id
Note
To enable the Next Hop Resolution Protocol (NHRP) on an interface, use the ipx nhrp network-id command in interface configuration mode. To disable NHRP on the interface, use the no form of this command.
ipx nhrp network-id number
no ipx nhrp network-id
Syntax Description
number
Globally unique, 32-bit network identifier for a nonbroadcast multiaccess (NBMA) network. The range is 1 to 4,294,967,295.
Defaults
NHRP is disabled on the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
In general, all NHRP stations within a fabric must be configured with the same network identifier.
Examples
The following example enables NHRP on the interface:
ipx nhrp network-id 1ipx nhrp nhs
Note
To specify the address of one or more Next Hop Resolution Protocol (NHRP) Next Hop Servers, use the ipx nhrp nhs command in interface configuration mode. To remove the address, use the no form of this command.
ipx nhrp nhs nhs-address [net-address]
no ipx nhrp nhs nhs-address [net-address]
Syntax Description
nhs-address
Address of the Next Hop Server being specified.
net-address
(Optional) IPX address of a network served by the Next Hop Server.
Defaults
No Next Hop Servers are explicitly configured, so normal network layer routing decisions forward NHRP traffic.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to specify the address of a Next Hop Server and the networks it serves. Normally, NHRP consults the network layer forwarding table to determine how to forward NHRP packets. When Next Hop Servers are configured, the next hop addresses specified with the ipx nhrp nhs command override the forwarding path specified by the network layer forwarding table that would usually be used for NHRP traffic.
For any Next Hop Server that is configured, you can specify multiple networks that it serves by repeating this command with the same nhs-address address, but different net-address IPX network numbers.
Examples
In the following example, the Next Hop Server with address 1.0000.0c00.1234 serves IPX network 2:
ipx nhrp nhs 1.0000.0c00.1234 2ipx nhrp record
Note
To re-enable the use of forward record and reverse record options in Next Hop Resolution Protocol (NHRP) Request and Reply packets, use the ipx nhrp record command in interface configuration mode. To suppress the use of such options, use the no form of this command.
ipx nhrp record
no ipx nhrp record
Syntax Description
This command has no arguments or keywords.
Defaults
Forward record and reverse record options are enabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
Forward record and reverse record options provide loop detection and are used in NHRP Request and Reply packets. Using the no form of this command disables this method of loop detection. For another method of loop detection, see the ipx nhrp responder command.
Examples
The following example suppresses forward record and reverse record options:
no ipx nhrp recordRelated Commands
ipx nhrp responder
Note
To designate which interface's primary IPX address that the Next Hop Server uses in Next Hop Resolution Protocol (NHRP) Reply packets when the NHRP requestor uses the Responder Address option, use the ipx nhrp responder command in interface configuration mode. To remove the designation, use the no form of this command.
ipx nhrp responder type number
no ipx nhrp responder [type] [number]
Syntax Description
Defaults
The Next Hop Server uses the IPX address of the interface where the NHRP Request was received.
Command Modes
Interface configuration
Command History
Usage Guidelines
If an NHRP requestor wants to know which Next Hop Server generates an NHRP Reply packet, it can request that information through the Responder Address option. The Next Hop Server that generates the NHRP Reply packet then complies by inserting its own IPX address in the Responder Address option of the NHRP Reply. The Next Hop Server uses the primary IPX address of the specified interface.
If an NHRP Reply packet being forwarded by a Next Hop Server contains that Next Hop Server's own IPX address, the Next Hop Server generates an Error Indication of type "NHRP Loop Detected" and discards the Reply.
Examples
In the following example, any NHRP requests for the Responder Address will cause this router acting as a Next Hop Server to supply the primary IPX address of interface serial 0 in the NHRP Reply packet:
ipx nhrp responder serial 0ipx nhrp use
Note
To configure the software so that Next Hop Resolution Protocol (NHRP) is deferred until the system has attempted to send data traffic to a particular destination multiple times, use the ipx nhrp use command in interface configuration mode. To restore the default value, use the no form of this command.
ipx nhrp use usage-count
no ipx nhrp use usage-count
Syntax Description
Defaults
The default is usage-count = 1. The first time a data packet is sent to a destination for which the system determines NHRP can be used, an NHRP request is sent.
Command Modes
Interface configuration
Command History
Usage Guidelines
When the software attempts to transmit a data packet to a destination for which it has determined that NHRP address resolution can be used, an NHRP request for that destination is normally transmitted right away. Configuring the usage-count causes the system to wait until that many data packets have been sent to a particular destination before it attempts NHRP. The usage-count for a particular destination is measured over 1-minute intervals (the NHRP cache expiration interval).
The usage-count applies per destination. So if usage-count is configured to be 3, and 4 data packets are sent toward 10.0.0.1 and 1 packet toward 10.0.0.2, then an NHRP request is generated for 10.0.0.1 only.
If the system continues to need to forward data packets to a particular destination, but no NHRP response has been received, retransmission of NHRP requests are performed. This retransmission occurs only if data traffic continues to be sent to a destination.
The ipx nhrp interest command controls which packets cause NHRP address resolution to take place; the ipx nhrp use command controls how readily the system attempts such address resolution.
Examples
In the following example, if in the first minute four packets are sent to one IPX address and five packets are sent to a second IPX address, then a single NHRP request is generated for the second IPX address. If in the second minute the same traffic is generated and no NHRP responses have been received, then the system retransmits its request for the second IPX address.
ipx nhrp use 5Related Commands
ipx nhrp interest
Controls which IPX packets can trigger sending an NHRP Request.
ipx nhrp max-send
Changes the maximum frequency at which NHRP packets can be sent.
ipx nlsp csnp-interval
Note
To configure the NetWare Link-Services Protocol (NLSP) complete sequence number PDU (CSNP) interval, use the ipx nlsp csnp-interval command in interface configuration mode. To restore the default value, use the no form of this command.
ipx nlsp [tag] csnp-interval seconds
no ipx nlsp [tag] csnp-interval seconds
Syntax Description
Defaults
30 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx nlsp csnp-interval command applies only to the designated router for the specified interface only. This is because only designated routers send CSNP packets, which are used to synchronize the database.
CSNP does not apply to serial point-to-point interfaces. However, it does apply to WAN connections if the WAN is viewed as a multiaccess meshed network.
Examples
The following example configures Ethernet interface 0 to transmit CSNPs every 10 seconds:
interface ethernet 0ipx network 101ipx nlsp enableipx nlsp csnp-interval 10Related Commands
ipx nlsp hello-interval
Specifies the hello multiplier used on an interface.
ipx nlsp retransmit-interval
Configures RIP compatibility when NLSP is enabled.
ipx nlsp enable
Note
To enable NetWare Link-Services Protocol (NLSP) routing on the primary network configured on this interface or subinterface, use the ipx nlsp enable command in interface configuration mode. To disable NLSP routing on the primary network configured on this interface or subinterface, use the no form of this command.
ipx nlsp [tag] enable
no ipx nlsp [tag] enable
Syntax Description
Defaults
NLSP is disabled on all interfaces.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you enable NLSP routing, the current settings for RIP and SAP compatibility modes as specified with the ipx nlsp rip and ipx nlsp sap interface configuration commands take effect automatically.
When you specify an NLSP tag, the router enables NLSP on the specified process. An NLSP process is a router's databases working together to manage route information about an area. NLSP version 1.0 routers are always in the same area. Each router has its own adjacencies, link-state, and forwarding databases. These databases operate collectively as a single process to discover, select, and maintain route information about the area. NLSP version 1.1 routers that exist within a single area also use a single process.
NLSP version 1.1 routers that interconnect multiple areas use multiple processes to discover, select, and maintain route information about the areas they interconnect. These routers manage an adjacencies, link-state, and area address database for each area to which they attach. Collectively, these databases are still referred to as a process. The forwarding database is shared among processes within a router. The sharing of entries in the forwarding database is automatic when all processes interconnect NLSP version 1.1 areas.
Configure multiple NLSP processes when a router interconnects multiple NLSP areas.
Note
Examples
The following example enables NLSP routing on Ethernet interface 0:
interface ethernet 0ipx nlsp enableThe following example enables NLSP routing on serial interface 0:
interface serial 0ipx ipxwan 2442 unnumbered local1ipx nlsp enableThe following example enables NLSP routing for process area3 on Ethernet interface 0:
interface ethernet 0ipx nlsp area3 enableRelated Commands
ipx nlsp rip
Configures RIP compatibility when NLSP is enabled.
ipx output-ggs-filter
Configures SAP compatibility when NLSP in enabled.
ipx nlsp hello-interval
Note
To configure the interval between the transmission of hello packets, use the ipx nlsp hello-interval command in interface configuration mode. To restore the default value, use the no form of this command.
ipx nlsp [tag] hello-interval seconds
no ipx nlsp [tag] hello-interval seconds
Syntax Description
Defaults
10 seconds for the designated router.
20 seconds for nondesignated routers.Command Modes
Interface configuration
Command History
Usage Guidelines
The designated router sends hello packets at an interval equal to one-half the configured value.
Use this command to improve the speed at which a failed router or link is detected. A router is declared to be down if a hello has not been received from it for the time determined by the holding time (the hello interval multiplied by the holding time multiplier; by default, 60 seconds for nondesignated routers and 30 seconds for designated routers). You can reduce this time by lowering the hello-interval setting, at the cost of increased traffic overhead.
You may also use this command to reduce link overhead on very slow links by raising the hello interval. This will reduce the traffic on the link at the cost of increasing the time required to detect a failed router or link.
Examples
The following example configures serial interface 0 to transmit hello packets every 30 seconds:
interface serial 0ipx ipxwan 2442 unnumbered local1ipx nlsp enableipx nlsp hello-interval 30Related Commands
ipx nlsp hello-multiplier
Note
To specify the hello multiplier used on an interface, use the ipx nlsp hello-multiplier command in interface configuration mode. To restore the default value, use the no form of this command.
ipx nlsp [tag] hello-multiplier multiplier
no ipx nlsp [tag] hello-multiplier
Syntax Description
Defaults
The default multiplier is 3.
Command Modes
Interface configuration
Command History
Usage Guidelines
You use the hello modifier in conjunction with the hello interval to determine the holding time value sent in a hello packet. The holding time is equal to the hello interval multiplied by the hello multiplier.
The holding time tells the neighboring router how long to wait for another hello packet from the sending router. If the neighboring router does not receive another hello packet in the specified time, then the neighboring router declares that the sending router is down.
You can use this method of determining the holding time when hello packets are lost with some frequency and NLSP adjacencies are failing unnecessarily. You raise the hello multiplier and lower the hello interval correspondingly to make the hello protocol more reliable without increasing the time required to detect a link failure.
Examples
In the following example, serial interface 0 will advertise hello packets every 15 seconds. The multiplier is 5. These values determine that the hello packet holding time is 75 seconds.
interface serial 0ipx nlsp hello-interval 15ipx nlsp hello-multiplier 5Related Commands
ipx nlsp lsp-interval
Note
To configure the time delay between successive NetWare Link-Services Protocol (NLSP) link-state packet (LSP) transmissions, use the ipx nlsp lsp-interval command in interface configuration mode. To restore the default time delay, use the no form of this command.
ipx nlsp [tag] lsp-interval interval
no ipx nlsp [tag] lsp-interval
Syntax Description
Defaults
55 milliseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
This command allows you to control how fast LSPs can be flooded out an interface.
In topologies with a large number of NLSP neighbors and interfaces, a router may have difficulty with the CPU load imposed by LSP transmission and reception. This command allows you to reduce the LSP transmission rate (and by implication the reception rate of other systems).
Examples
The following example causes the system to transmit LSPs every 100 ms (10 packets per second) on Ethernet interface 0:
interface Ethernet 0ipx nlsp lsp-interval 100Related Commands
ipx nlsp metric
Note
To configure the NetWare Link-Services Protocol (NLSP) cost for an interface, use the ipx nlsp metric command in interface configuration mode. To restore the default cost, use the no form of this command.
ipx nlsp [tag] metric metric-number
no ipx nlsp [tag] metric metric-number
Syntax Description
tag
(Optional) Names the NLSP process. The tag can be any combination of printable characters.
metric-number
Metric value for the interface. It can be a number from 0 to 63.
Defaults
The default varies on the basis of the throughput of the link connected to the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the ipx nlsp metric command to cause NLSP to prefer some links over others. A link with a lower metric is more preferable than one with a higher metric.
Typically, it is not necessary to configure the metric; however, it may be desirable in some cases when there are wide differences in link bandwidths. For example, using the default metrics, a single 64-kbps ISDN link will be preferable to two 1544-kbps T1 links.
Examples
The following example configures a metric of 10 on serial interface 0:
interface serial 0ipx network 107ipx nlsp enableipx nlsp metric 10Related Commands
ipx nlsp enable
Configures the interval between the transmission of hello packets.
ipx nlsp multicast
Note
To configure an interface to use multicast addressing, use the ipx nlsp multicast command in interface configuration mode. To configure the interface to use broadcast addressing, use the no form of this command.
ipx nlsp [tag] multicast
no ipx nlsp [tag] multicast
Syntax Description
Defaults
Multicast addressing is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command allows the router interface to use NLSP multicast addressing. If an adjacent neighbor does not support NLSP multicast addressing, the router will revert to using broadcasts on the affected interface.
The router will also revert to using broadcasts if multicast addressing is not supported by the hardware or driver.
Examples
The following example disables multicast addressing on Ethernet interface 0:
interface ethernet 0no ipx nlsp multicastipx nlsp priority
Note
To configure the election priority of the specified interface for designated router election, use the ipx nlsp priority command in interface configuration mode. To restore the default priority, use the no form of this command.
ipx nlsp [tag] priority priority-number
no ipx nlsp [tag] priority priority-number
Syntax Description
Defaults
44
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the ipx nlsp priority command to control which router is elected designated router. The device with the highest priority number is selected as the designated router.
The designated router increases its own priority by 20 in order to keep its state as of the designated router more stable. To have a particular router be selected as the designated router, configure its priority to be at least 65.
Examples
The following example sets the designated router election priority to 65:
interface ethernet 0ipx network 101ipx nlsp enableipx nlsp priority 65ipx nlsp retransmit-interval
Note
To configure the link-state packet (LSP) retransmission interval on WAN links, use the ipx nlsp retransmit-interval command in interface configuration mode. To restore the default interval, use the no form of this command.
ipx nlsp [tag] retransmit-interval seconds
no ipx nlsp [tag] retransmit-interval seconds
Syntax Description
Defaults
5 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
This command sets the maximum amount of time that can pass before an LSP will be sent again (retransmitted) on a WAN link, if no acknowledgment is received.
Reducing the retransmission interval can improve the convergence rate of the network in the face of lost WAN links. The cost of reducing the retransmission interval is the potential increase in link utilization.
Examples
The following example configures the LSP retransmission interval to 2 seconds:
ipx nlsp retransmit-interval 2Related Commands
ipx nlsp csnp-interval
Configures the NLSP CSNP interval.
ipx nlsp hello-interval
Specifies the hello multiplier used on an interface.
ipx nlsp rip
Note
To configure RIP compatibility when NetWare Link-Services Protocol (NLSP) is enabled, use the ipx nlsp rip command in interface configuration mode. To restore the default, use the no form of this command.
ipx nlsp [tag] rip [on | off | auto]
no ipx nlsp [tag] rip [on | off | auto]
Syntax Description
Defaults
RIP periodic traffic is sent only if another router in sending periodic RIP traffic.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx nlsp rip command is meaningful only on networks on which NLSP is enabled. (RIP and SAP are always on by default on other interfaces.) Because the default mode is auto, no action is normally required to fully support RIP compatibility on an NLSP network.
Examples
In the following example, the interface never generates or sends RIP periodic traffic:
interface ethernet 0ipx nlsp rip offRelated Commands
ipx nlsp enable
Configures the interval between the transmission of hello packets.
ipx output-ggs-filter
Configures SAP compatibility when NLSP in enabled.
ipx nlsp sap
Note
To configure SAP compatibility when NetWare Link-Services Protocol (NLSP) in enabled, use the ipx nlsp sap command in interface configuration mode. To restore the default, use the no form of this command.
ipx nlsp [tag] sap [on | off | auto]
no ipx nlsp [tag] sap [on | off | auto]
Syntax Description
Defaults
SAP periodic traffic is sent only if another router in sending periodic SAP traffic.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx nlsp sap command is meaningful only on networks on which NLSP is enabled. Because the default mode is auto, no action is normally required to fully support SAP compatibility on an NLSP network.
Examples
In the following example, the interface never generates or sends SAP periodic traffic:
interface ethernet 0ipx nlsp sap offRelated Commands
ipx nlsp enable
Configures the interval between the transmission of hello packets.
ipx nlsp rip
Configures RIP compatibility when NLSP is enabled.
ipx output-ggs-filter
Note
To control which servers are included in the Get General Service (GGS) responses sent by Cisco IOS software, use the ipx output-ggs-filter command in interface configuration mode. To remove the filter from the interface, use the no form of this command.
ipx output-ggs-filter {access-list-number | name}
no ipx output-ggs-filter {access-list-number | name}
Syntax Description
Defaults
No filters are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can issue only one ipx output-ggs-filter command on each interface.
Note
Examples
The following example excludes the server at address 3c.0800.89a1.1527 from GGS responses sent on Ethernet interface 0, but allows all other servers:
access-list 1000 deny 3c.0800.89a1.1527access-list 1000 permit -1ipx routinginterface ethernet 0ipx network 2Bipx output-ggs-filter 1000Related Commands
ipx output-gns-filter
Note
To control which servers are included in the Get Nearest Server (GNS) responses sent by Cisco IOS software, use the ipx output-gns-filter command in interface configuration mode. To remove the filter from the interface, use the no form of this command.
ipx output-gns-filter {access-list-number | name}
no ipx output-gns-filter {access-list-number | name}
Syntax Description
Defaults
No filters are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can issue only one ipx output-gns-filter command on each interface.
Examples
The following example excludes the server at address 3c.0800.89a1.1527 from GNS responses sent on Ethernet interface 0, but allows all other servers:
access-list 1000 deny 3c.0800.89a1.1527access-list 1000 permit -1ipx routinginterface ethernet 0ipx network 2Bipx output-gns-filter 1000Related Commands
ipx output-network-filter (RIP)
Note
To control the list of networks included in routing updates sent out an interface, use the ipx output-network-filter command in interface configuration mode. To remove the filter from the interface, use the no form of this command.
ipx output-network-filter {access-list-number | name}
no ipx output-network-filter {access-list-number | name}
Syntax Description
Defaults
No filters are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx output-network-filter command controls which networks the Cisco IOS software advertises in its IPX routing updates (RIP updates).
You can issue only one ipx output-network-filter command on each interface.
Examples
In the following example, access list 896 controls which networks are specified in routing updates sent out the serial 1 interface. This configuration causes network 2b to be the only network advertised in Novell routing updates sent on the specified serial interface.
access-list 896 permit 2binterface serial 1ipx output-network-filter 896Related Commands
ipx output-rip-delay
Note
To set the interpacket delay for RIP updates sent on a single interface, use the ipx output-rip-delay command in interface configuration mode. To return to the default value, use the no form of this command.
ipx output-rip-delay delay
no ipx output-rip-delay [delay]
Syntax Description
delay
Delay, in milliseconds (ms), between packets in a multiple-packet RIP update. The default delay is 55 ms. Novell recommends a delay of 55 ms.
Defaults
55 ms
Command Modes
Interface configuration
Command History
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet routing update. The ipx output-rip-delay command sets the interpacket delay for a single interface.
The system uses the interpacket delay specified by the ipx output-rip-delay command for periodic and triggered routing updates when no delay is set for triggered routing updates. When you set a delay for triggered routing updates, the system uses the delay specified by the ipx output-rip-delay command for only the periodic routing updates sent on the interface.
To set a delay for triggered routing updates, see the ipx triggered-rip-delay or ipx default-triggered-rip-delay commands.
You can also set a default RIP interpacket delay for all interfaces. See the ipx default-output-rip-delay command for more information.
Novell recommends a delay of 55 ms for compatibility with older and slower IPX machines. These machines may lose RIP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX machines.
The default delay on a NetWare 3.11 server is about 100 ms.
This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.
Examples
The following example establishes a 55-ms interpacket delay on serial interface 0:
interface serial 0ipx network 106Aipx output-rip-delay 55Related Commands
ipx output-sap-delay
Note
To set the interpacket delay for Service Advertising Protocol (SAP) updates sent on a single interface, use the ipx output-sap-delay command in interface configuration mode. To return to the default delay value, use the no form of this command.
ipx output-sap-delay delay
no ipx output-sap-delay
Syntax Description
delay
Delay, in milliseconds, between packets in a multiple-packet SAP update. The default delay is 55 ms. Novell recommends a delay of 55 ms.
Defaults
55 ms
Command Modes
Interface configuration
Command History
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet SAP update. The ipx output-sap-delay command sets the interpacket delay for a single interface.
The system uses the interpacket delay specified by the ipx output-sap-delay command for periodic and triggered SAP updates when no delay is set for triggered updates. When you set a delay for triggered updates, the system uses the delay specified by the ipx output-sap-delay command only for the periodic updates sent on the interface.
To set a delay for triggered updates, see the ipx triggered-sap-delay or ipx default-triggered-sap-delay commands.
You can also set a default SAP interpacket delay for all interfaces. See the ipx default-output-sap-delay command for more information.
Novell recommends a delay of 55 ms for compatibility with older and slower IPX servers. These servers may lose SAP updates because they process packets more slowly than the router sends them. The delay imposed by the ipx output-sap-delay command forces the router to pace its output to the slower-processing needs of these servers.
The default delay on a NetWare 3.11 server is about 100 ms.
This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.
Examples
The following example establishes a 55-ms delay between packets in multiple-packet SAP updates on Ethernet interface 0:
interface ethernet 0ipx network 106Aipx output-sap-delay 55Related Commands
ipx output-sap-filter
Note
To control which services are included in Service Advertising Protocol (SAP) updates sent by Cisco IOS software, use the ipx output-sap-filter command in interface configuration mode. To remove the filter, use the no form of this command.
ipx output-sap-filter {access-list-number | name}
no ipx output-sap-filter {access-list-number | name}
Syntax Description
Defaults
No filters are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
Cisco IOS software applies output SAP filters prior to sending SAP packets.
You can issue only one ipx output-sap-filter command on each interface.
When configuring SAP filters for NetWare 3.11 and later servers, use the server's internal network and node number (the node number is always 0000.0000.0001) as its address in the SAP access-list command. Do not use the network.node address of the particular interface board.
Examples
The following example denies service advertisements about server 0000.0000.0001 on network aa from being sent on network 4d (via Ethernet interface 1). All other services are advertised via this network. All services, included those from server aa.0000.0000.0001, are advertised via networks 3c and 2b.
access-list 1000 deny aa.0000.0000.0001access-list 1000 permit -1interface ethernet 0ipx network 3cinterface ethernet 1ipx network 4dipx output-sap-filter 1000interface serial 0ipx network 2bRelated Commands
ipx pad-process-switched-packets
Note
To control whether odd-length packets are padded so as to be sent as even-length packets on an interface, use the ipx pad-process-switched-packets command in interface configuration mode. To disable padding, use the no form of this command.
ipx pad-process-switched-packets
no ipx pad-process-switched-packets
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled on Ethernet interfaces.
Disabled on Token Ring, FDDI, and serial interfaces.Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command only under the guidance of a customer engineer or other service representative.
The ipx pad-process-switched-packets command affects process-switched packets only, so you must disable fast switching before the ipx pad-process-switched-packets command has any effect.
Some IPX end hosts reject Ethernet packets that are not padded. Certain topologies can result in such packets being forwarded onto a remote Ethernet network. Under specific conditions, padding on intermediate media can be used as a temporary workaround for this problem.
Examples
The following example configures the Cisco IOS software to pad odd-length packets so that they are sent as even-length packets on FDDI interface 1.
interface fddi 1ipx network 2Ano ipx route-cacheipx pad-process-switched-packetsRelated Commands
ipx per-host-load-share
Note
To enable per-host load sharing, use the ipx per-host-load-share command in global configuration mode. To disable per-host load sharing, use the no form of this command.
ipx per-host-load-share
no ipx per-host-load-share
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enable per-host load sharing. Per-host load sharing transmits traffic across multiple, equal-cost paths while guaranteeing that packets for a given end host always take the same path.
When you do not enable per-host load sharing, the software uses a round-robin algorithm to accomplish load sharing. Round-robin load sharing transmits successive packets over alternate, equal-cost paths, regardless of the destination host. With round-robin load sharing, successive packets destined for the same end host might take different paths. Thus, round-robin load sharing increases the possibility that successive packets to a given end host might arrive out of order or be dropped, but ensures true load balancing of a given workload across multiple links.
In contrast, per-host load sharing decreases the possibility that successive packets to a given end host will arrive out of order; but, there is a potential decrease in true load balancing across multiple links. True load sharing occurs only when different end hosts utilize different paths; equal link utilization cannot be guaranteed.
With per-host load balancing, the number of equal-cost paths set by the ipx maximum-paths command must be greater than one; otherwise, per-host load sharing has no effect.
Examples
The following command globally enables per-host load sharing:
ipx per-host-load shareRelated Commands
ipx maximum-paths
Sets the maximum number of equal-cost paths the Cisco IOS software uses when forwarding packets.
ipx ping-default
Note
To select the ping type that Cisco IOS software transmits, use the ipx ping-default command in global configuration mode. To return to the default ping type, use the no form of this command.
ipx ping-default {cisco | novell | diagnostic}
no ipx ping-default {cisco | novell | diagnostic}
Syntax Description
cisco
Transmits Cisco pings.
novell
Transmits standard Novell pings.
diagnostic
Transmits diagnostic request/response for IPX pings.
Defaults
Cisco pings
Command Modes
Global configuration
Command History
Usage Guidelines
This command can transmit Cisco pings, standard Novell pings as defined in the NLSP specification, and IPX diagnostic pings.
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.
Note
The ipx ping-default command using the diagnostic keyword can be used to conduct a reachability test and should not be used to measure accurate roundtrip delay.
Examples
The following is sample output from the ipx ping-default command when the diagnostic keyword is enabled:
Router# ipx ping-default diagnosticProtocol [ip]: ipxTarget IPX address: 20.0000.0000.0001Verbose [n]: yTimeout in seconds [2]: 1Type escape sequence to abort.Sending 1, 31-byte IPX Diagnostic Echoes to 20.0000.0000.0001, timeout is 1 seconds:Diagnostic Response from 20.0000.0000.0001 in 4 msMajor Version: 1Minor Version: 0SPX Diagnostic Socket: 4002Number of components: 3Component ID: 0 (IPX / SPX)Component ID: 1 (Router Driver)Component ID: 5 (Router)Number of Local Networks: 2Local Network Type: 0 (LAN Board)Network Address1 20Node Address1 0000.0000.0001Local Network Type: 0 (LAN Board)Network Address2 30Node Address2 0060.70cc.bc65
Note
Related Commands
ipx potential-pseudonode (NLSP)
Note
To enable NetWare Link Services Protocol (NLSP) to keep backup router and service information for potential pseudonode, use the ipx potential-pseudonode command in global configuration mode. To disable the feature so that NLSP does not keep backup router and service information for potential pseudonode, use the no form of this command.
ipx potential-pseudonode
no ipx potential-pseudonode
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
The potential pseudonode is NLSP-specified service information that a router keeps in anticipation of possibly becoming a designated router. Designated routers are required to produce an actual pseudonode.
Examples
The following example enables NLSP to keep backup router and service information for potential pseudonode:
ipx potential-pseudonodeipx rip-max-packetsize
Note
To configure the maximum packet size of RIP updates sent out the interface, use the ipx rip-max-packetsize command in interface configuration mode. To restore the default packet size, use the no form of this command.
ipx rip-max-packetsize bytes
no ipx rip-max-packetsize bytes
Syntax Description
bytes
Maximum packet size in bytes. The default is 432 bytes, which allows for 50 routes at 8 bytes each, plus 32 bytes of IPX network and RIP header information.
Defaults
432 bytes
Command Modes
Interface configuration
Command History
Usage Guidelines
The maximum size is for the IPX packet including the IPX network and RIP header information.
Do not allow the maximum packet size to exceed the allowed maximum size of packets for the interface.
Examples
The following example sets the maximum RIP update packet to 832 bytes:
ipx rip-max-packetsize 832Related Commands
ipx sap-max-packetsize
Configures the maximum packet size of SAP updates sent out the interface.
ipx rip-multiplier
Note
To configure the interval at which a network's RIP entry ages out, use the ipx rip-multiplier command in interface configuration mode. To restore the default interval, use the no form of this command.
ipx rip-multiplier multiplier
no ipx rip-multiplier multiplier
Syntax Description
Defaults
Three times the RIP update interval
Command Modes
Interface configuration
Command History
Usage Guidelines
All routers on the same physical cable should use the same multiplier value.
Examples
In the following example, in a configuration where RIP updates are sent once every 2 minutes, the interval at which RIP entries age out is set to 10 minutes:
interface ethernet 0ipx rip-multiplier 5Related Commands
ipx update sap-after-rip
Configures the router to send a SAP update immediately following a RIP broadcast.
ipx rip-queue-maximum
Note
To set an IPX Routing Information Protocol (RIP) queue maximum to control how many RIP packets can be waiting to be processed at any given time, use the ipx rip-queue-maximum command in global configuration mode. To clear a set RIP queue maximum, use the no form of this command.
ipx rip-queue-maximum milliseconds
no ipx rip-queue-maximum milliseconds
Syntax Description
Defaults
No queue limit is set.
Command Modes
Global configuration
Command History
Usage Guidelines
When you use the ipx rip-queue-maximum command to control how many RIP packets can be waiting to be processed at any given time, remember that if the queue limit is reached, the incoming RIP request packets are dropped. Be sure to set a large enough queue limit to handle normal incoming RIP requests on all interfaces, or else the RIP information may time out.
Examples
The following example sets a RIP queue maximum of 500 milliseconds:
ipx rip-queue-maximum 500Related Commands
ipx rip-response-delay
Note
To change the delay when responding to Routing Information Protocol (RIP) requests, use the ipx rip-response-delay command in interface configuration mode. To return to the default delay, use the no form of this command.
ipx rip-response-delay ms
no ipx rip-response-delay
Syntax Description
Defaults
No delay in answering (0 ms).
Command Modes
Interface configuration
Command History
Usage Guidelines
This command slows down the Cisco router and allows another router to answer first and become the router of choice. A delay in responding to RIP requests can be imposed so that, in certain topologies, any local Novell IPX router or any third-party IPX router can respond to the RIP requests before the Cisco router responds.
Optimal delay time is the same as or slightly longer than the time it takes the other router to answer.
Examples
The following example sets the delay in responding to RIP requests to 55 ms (0.055 seconds):
ipx rip-response-delay 55Related Commands
ipx rip-update-queue-maximum
Note
To set an IPX Routing Information Protocol (RIP) queue maximum to control how many incoming RIP update packets can be waiting to be processed at any given time, use the ipx rip-update-queue-maximum command in global configuration mode. To clear a set RIP queue maximum, use the no form of this command.
ipx rip-update-queue-maximum queue-maximum
no ipx rip-update-queue-maximum queue-maximum
Syntax Description
Defaults
No queue limit
Command Modes
Global configuration
Command History
Usage Guidelines
When you use the ipx rip-update-queue-maximum command to control how many incoming RIP update packets can be waiting to be processed at any given time, remember that if the queue limit is reached, the incoming RIP update packets are dropped.
Note
Examples
The following example sets a RIP update queue maximum of 500:
ipx rip-update-queue-maximum 500Related Commands
ipx route
Note
To add a static route or static NetWare Link Services Protocol (NLSP) route summary to the routing table, use the ipx route command in global configuration mode. To remove a route from the routing table, use the no form of this command.
ipx route {network [network-mask] | default} {network.node | interface} [ticks] [hops] [floating-static]
no ipx route
Syntax Description
Defaults
No static routes are predefined.
Command Modes
Global configuration
Command History
Usage Guidelines
The ipx route command forwards packets destined for the specified network (network) via the specified router (network.node) or an interface (interface) on that network regardless of whether that router is sending dynamic routing information.
Floating static routes are static routes that can be overridden by dynamically learned routes. Floating static routes allow you to switch to another path whenever routing information for a destination is lost. One application of floating static routes is to provide back-up routes in topologies where dial-on-demand routing is used.
If you configure a floating static route, the Cisco IOS software checks to see if an entry for the route already exists in its routing table. If a dynamic route already exists, the floating static route is placed in reserve as part of a floating static route table. When the software detects that the dynamic route is no longer available, it replaces the dynamic route with the floating static route for that destination. If the route is later relearned dynamically, the dynamic route replaces the floating static route and the floating static route is again placed in reserve.
If you specify an interface instead of a network node address, the interface must be an IPXWAN unnumbered interface. For IPXWAN interfaces, the network number need not be preassigned; instead, the nodes may negotiate the network number dynamically.
Note that by default, floating static routes are not redistributed into other dynamic protocols.
Examples
In the following example, a router at address 3abc.0000.0c00.1ac9 handles all traffic destined for network 5e:
ipx routing ipx route 5e 3abc.0000.0c00.1ac9The following example defines a static NLSP route summary:
ipx routing ipx route aaaa0000 ffff0000Related Commands
ipx route-cache
Note
To enable IPX fast switching, use the ipx route-cache command in interface configuration mode. To disable fast switching, use the no form of this command.
ipx route-cache
no ipx route-cache
Syntax Description
This command has no arguments or keywords.
Defaults
Fast switching is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Fast switching allows higher throughput by switching packets using a cache created by previous transit packets. Fast switching is enabled by default on all interfaces that support fast switching, including Token Ring, Frame Relay, PPP, Switched Multimegabit Data Service (SMDS), and ATM.
On ciscoBus-2 interface cards, fast switching is done between all encapsulation types. On other interface cards, fast switching is done in all cases except the following: transfer of packets with sap encapsulation from an Ethernet, a Token Ring, or an FDDI network to a standard serial line.
You might want to disable fast switching in two situations. One is if you want to save memory on the interface cards: fast-switching caches require more memory than those used for standard switching. The second situation is to avoid congestion on interface cards when a high-bandwidth interface is writing large amounts of information to a low-bandwidth interface.
Note
Examples
The following example enables fast switching on an interface:
interface ethernet 0ipx route-cacheThe following example disables fast switching on an interface:
interface ethernet 0no ipx route-cacheRelated Commands
ipx route-cache inactivity-timeout
Note
To adjust the period and rate of route cache invalidation because of inactivity, use the ipx route-cache inactivity-timeout command in global configuration mode. To return to the default values, use the no form of this command.
ipx route-cache inactivity-timeout period [rate]
no ipx route-cache inactivity-timeout
Syntax Description
Defaults
The default period is 2 minutes. The default rate is 0 (cache entries do not age).
Command Modes
Global configuration
Command History
Usage Guidelines
IPX fast-switch cache entries that are not in use may be invalidated after a configurable period of time. If no new activity occurs, these entries will be purged from the route cache after one additional minute.
Cache entries that have been uploaded to the switch processor when autonomous switching is configured are always exempt from this treatment.
This command has no effect if silicon switching is configured.
Examples
The following example sets the inactivity period to 5 minutes, and sets a maximum of 10 entries that can be invalidated per minute:
ipx route-cache inactivity-timeout 5 10Related Commands
ipx route-cache max-size
Note
To set a maximum limit on the number of entries in the IPX route cache, use the ipx route-cache max-size command in global configuration mode. To return to the default setting, use the no form of this command.
ipx route-cache max-size size
no ipx route-cache max-size
Syntax Description
Defaults
The default setting is no limit on the number of entries.
Command Modes
Global configuration
Command History
Usage Guidelines
On large networks, 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. If the 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. The ipx route-cache max-size command allows you to set a maximum number of entries for the route cache.
If the route cache already has more entries than the specified limit, the extra entries are not deleted. However, all route cache entries are subject to being removed via the parameter set for route cache aging via the ipx route-cache inactivity-timeout command.
Examples
The following example sets the maximum route cache size to 10,000 entries.
ipx route-cache max-size 10000Related Commands
ipx route-cache update-timeout
Note
To adjust the period and rate of route cache invalidation because of aging, use the ipx route-cache update-timeout command in global configuration mode. To return to the default values, use the no form of this command.
ipx route-cache update-timeout period [rate]
no ipx route-cache update-timeout
Syntax Description
Defaults
The default setting is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
IPX fast-switch cache entries that exceed a minimum age may be invalidated after a configurable period of time. Invalidation occurs unless the cache entry was marked as active during the last minute. Following invalidation, if no new activity occurs, these entries will be purged from the route cache after one additional minute.
This capability is primarily useful when autonomous switching or silicon switching is enabled. In both cases, activity is not recorded for entries in the route cache, because data is being switched by the Switch Processor (SP) or Silicon Switch Processor (SSP). In this case, it may be desirable to periodically invalidate a limited number of older cache entries each minute.
If the end hosts have become inactive, the cache entries will be purged after one additional minute. If the end hosts are still active, the route cache and autonomous or SSP cache entries will be revalidated instead of being purged.
Examples
The following example sets the update timeout period to 5 minutes and sets a maximum of 10 entries that can be invalidated per minute:
ipx route-cache update-timeout 5 10Related Commands
ipx router
Note
To specify the routing protocol to use, use the ipx router command in global configuration mode. To disable a particular routing protocol on the router, use the no form of this command.
ipx router {eigrp autonomous-system-number | nlsp [tag] | rip}
no ipx router {eigrp autonomous-system-number | nlsp [tag] | rip}
Syntax Description
Defaults
RIP is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
You must explicitly disable RIP by issuing the no ipx router rip command if you do not want to use this routing protocol.
You can configure multiple Enhanced IGRP processes on a router. To do so, assign each a different autonomous system number.
Note
When you specify an NLSP tag, you configure the NLSP routing protocol for a particular NLSP process. An NLSP process is a router's databases working together to manage route information about an area. NLSP version 1.0 routers are always in the same area. Each router has its own adjacencies, link-state, and forwarding databases. These databases operate collectively as a single process to discover, select, and maintain route information about the area. NLSP version 1.1 routers that exist within a single area also use a single process.
NLSP version 1.1 routers that interconnect multiple areas use multiple processes to discover, select, and maintain route information about the areas they interconnect. These routers manage an adjacencies, link-state, and area address database for each area to which they attach. Collectively, these databases are still referred to as a process. The forwarding database is shared among processes within a router. The sharing of entries in the forwarding database is automatic when all processes interconnect NLSP version 1.1 areas.
Configure multiple NLSP processes when a router interconnects multiple NLSP areas.
Examples
The following example enables Enhanced IGRP:
ipx router eigrp 4The following example enables NLSP on process area1. This process handles routing for NLSP area 1.
ipx router nlsp area1Related Commands
network
Enables Enhanced IGRP.
redistribute (IPX)
Redistributes from one routing domain into another.
ipx router-filter
Note
To filter the routers from which packets are accepted, use the ipx router-filter command in interface configuration mode. To remove the filter from the interface, use the no form of this command.
ipx router-filter {access-list-number | name}
no ipx router-filter
Syntax Description
Defaults
No filters are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can issue only one ipx router-filter command on each interface.
Examples
In the following example, access list 866 controls the routers from which packets are accepted. For Ethernet interface 0, only packets from the router at 3c.0000.00c0.047d are accepted. All other packets are implicitly denied.
access-list 866 permit 3c.0000.00c0.047dinterface ethernet 0ipx router-filter 866Related Commands
ipx router-sap-filter
Note
To filter Service Advertising Protocol (SAP) messages received from a particular router, use the ipx router-sap-filter command in interface configuration mode. To remove the filter, use the no form of this command.
ipx router-sap-filter {access-list-number | name}
no ipx router-sap-filter {access-list-number | name}
Syntax Description
Defaults
No filters are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can issue only one ipx router-sap-filter command on each interface.
Examples
In the following example, the Cisco IOS software will receive service advertisements only from router aa.0207.0104.0874:
access-list 1000 permit aa.0207.0104.0874access-list 1000 deny -1interface ethernet 0ipx router-sap-filter 1000Related Commands
ipx routing
Note
To enable IPX routing, use the ipx routing command in global configuration mode. To disable IPX routing, use the no form of this command.
ipx routing [node]
no ipx routing
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
ipx internal-network 1
Usage Guidelines
The ipx routing command enables IPX Routing Information Protocol (RIP) and Service Advertising Protocol (SAP) services.
If you omit the argument node and if the MAC address later changes, the IPX node address automatically changes to the new address. However, connectivity may be lost between the time that the MAC address changes and the time that the IPX clients and servers learn the router's new address.
If you plan to use DECnet and IPX routing concurrently on the same interface, you should enable DECnet router 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.
Examples
The following example enables IPX routing:
ipx routingRelated Commands
ipx network
Enables IPX routing on a particular interface and optionally selects the type of encapsulation (framing).
