Table Of Contents
access-list (NLSP route aggregation summarization)
deny (NLSP route aggregation summarization)
ipx advertise-default-route-only (RIP)
ipx backup-server-query-interval (EIGRP)
ipx default-triggered-rip-delay
ipx default-triggered-sap-delay
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 route-cache inactivity-timeout
ipx route-cache update-timeout
ipx sap-incremental split-horizon
ipx server-split-horizon-on-server-paths
permit (NLSP route aggregation summarization)
Novell IPX Commands
Novell Internet Packet Exchange (IPX) is derived from the Xerox Network Systems (XNS) Internet Datagram Protocol (IDP). One major difference between IPX and XNS is that they do not always use the same Ethernet encapsulation format. A second difference is that IPX uses Novell's proprietary Service Advertising Protocol (SAP) to advertise special network services.
Our implementation of Novell's IPX protocol has been certified as providing full IPX router functionality.
Use the commands in this chapter to configure and monitor Novell IPX networks. For IPX configuration information and examples, refer to the "Configuring Novell IPX" chapter in the Network Protocols Configuration Guide, Part 2.
Note
For all commands that previously used the keyword novell, this keyword has been changed to ipx. You can still use the keyword novell in all commands.
access-list (IPX extended)
To define an extended Novell IPX access list, use the extended version of the access-list global configuration command. To remove an extended access list, use the no form of this command.
access-list access-list-number {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-node-mask]] [destination-socket] [log]
no access-list access-list-number {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-node-mask]] [destination-socket] [log]
Syntax Description
access-list-number
Number of the access list. This is a number from 900 to 999.
deny
Denies access if the conditions are matched.
permit
Permits access if the conditions are matched.
protocol
Name or number of an IPX protocol type. This is sometimes referred to as the packet type. Table 293 in the "Usage Guidelines" section lists some IPX protocol names and numbers.
source-network
(Optional) Number of the network from which the packet is being sent. This is an eight-digit hexadecimal number that uniquely identifies a network cable segment. It can be a number in the range 1 to FFFFFFFE. A network number of 0 matches the local network. A network number of -1 matches all networks.
You do not need to specify leading zeros in the network number; for example, for the network number 000000AA, you can enter AA.
.source-node
(Optional) Node on source-network from which the packet is being sent. This is a 48-bit value represented by a dotted triplet of four-digit hexadecimal numbers (xxxx.xxxx.xxxx).
source-node-mask
(Optional) Mask to be applied to source-node. This is a 48-bit value represented as a dotted triplet of four-digit hexadecimal numbers (xxxx.xxxx.xxxx). Place ones in the bit positions you want to mask.
source-network-mask.
(Optional) Mask to be applied to source-network. This is an eight-digit hexadecimal mask. Place ones in the bit positions you want to mask.
The mask must immediately be followed by a period, which must in turn immediately be followed by source-node-mask.
source-socket
(Optional) Socket name or number (hexadecimal) from which the packet is being sent. Table 294 in the "Usage Guidelines" section lists some IPX socket names and numbers.
destination.network
(Optional) Number of the network to which the packet is being sent. This is an eight-digit hexadecimal number that uniquely identifies a network cable segment. It can be a number in the range 1 to FFFFFFFE. A network number of 0 matches the local network. A network number of -1 matches all networks.
You do not need to specify leading zeros in the network number. For example, for the network number 000000AA, you can enter AA.
.destination-node
(Optional) Node on destination-network to which the packet is being sent. This is a 48-bit value represented by a dotted triplet of four-digit hexadecimal numbers (xxxx.xxxx.xxxx).
destination-node-mask
(Optional) Mask to be applied to destination-node. This is a 48-bit value represented as a dotted triplet of four-digit hexadecimal numbers (xxxx.xxxx.xxxx). Place ones in the bit positions you want to mask.
destination-network-mask.
(Optional) Mask to be applied to destination-network. This is an eight-digit hexadecimal mask. Place ones in the bit positions you want to mask.
The mask must immediately be followed by a period, which must in turn immediately be followed by destination-node-mask.
destination-socket
(Optional) Socket name or number (hexadecimal) to which the packet is being sent. Table 294 in the "Usage Guidelines" section lists some IPX socket names and numbers.
log
(Optional) Logs IPX access control list violations whenever a packet matches a particular access list entry. The information logged includes source address, destination address, source socket, destination socket, protocol type, and action taken (permit/deny).
Defaults
No access lists are predefined.
Command Modes
Global configuration
Command History
Usage Guidelines
Extended IPX access lists filter on protocol type. All other parameters are optional.
If a network mask is used, all other fields are required.
Use the ipx access-group command to assign an access list to an interface. You can apply only one extended or one standard access list to an interface. The access list filters all outgoing packets on the interface.
Note
Table 293 lists some IPX protocol names and numbers. Table 294 lists some IPX socket names and numbers. For additional information about IPX protocol numbers and socket numbers, contact Novell.
To delete an extended access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:
no access-list access-list-number
To delete the access list for a specific protocol, use the following command:
no access-list access-list-number {deny | permit} protocol
Examples
The following example denies access to all RIP packets from the RIP process socket on source network 1 that are destined for the RIP process socket on network 2. It permits all other traffic. This example uses protocol and socket names rather than hexadecimal numbers.
access-list 900 deny -1 1 rip 2 rip access-list 900 permit -1The following example permits type 2 packets from any socket from host 10.0000.0C01.5234 to access any sockets on any node on networks 1000 through 100F. It denies all other traffic (with an implicit deny all):
Note
access-list 910 permit 2 10.0000.0C01.5234 0000.0000.0000 0 1000.0000.0000.0000 F.FFFF.FFFF.FFFF 0Related Commands
access-list (IPX standard)
To define a standard IPX access list, use the standard version of the access-list global configuration command. To remove a standard access list, use the no form of this command.
access-list access-list-number {deny | permit} source-network[.source-node[source-node-mask]] [destination-network[.destination-node [destination-node-mask]]]
no access-list access-list-number {deny | permit} source-network[.source-node[source-node-mask]] [destination-network[.destination-node [destination-node-mask]]]
Syntax Description
Defaults
No access lists are predefined.
Command Modes
Global configuration
Command History
Usage Guidelines
Standard IPX access lists filter on the source network. All other parameters are optional.
Use the ipx access-group command to assign an access list to an interface. You can apply only one extended or one standard access list to an interface. The access list filters all outgoing packets on the interface.
To delete a standard access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:
no access-list access-list-number
To delete the access list for a specific network, use the following command:
no access-list access-list-number {deny | permit} source-network
Examples
The following example denies access to traffic from all IPX networks (-1) to destination network 2:
access-list 800 deny -1 2The following example denies access to all traffic from IPX address 1.0000.0c00.1111:
access-list 800 deny 1.0000.0c00.1111The following example denies access from all nodes on network 1 that have a source address beginning with 0000.0c:
access-list 800 deny 1.0000.0c00.0000 0000.00ff.ffffThe following example denies access from source address 1111.1111.1111 on network 1 to destination address 2222.2222.2222 on network 2:
access-list 800 deny 1.1111.1111.1111 0000.0000.0000 2.2222.2222.2222 0000.0000.0000or
access-list 800 deny 1.1111.1111.1111 2.2222.2222.2222Related Commands
access-list (NLSP route aggregation summarization)
To define an access list that denies or permits area addresses that summarize routes, use the NLSP route aggregation version of the access-list global configuration command. To remove an NLSP route aggregation access list, use the no form of this command.
access-list access-list-number {deny | permit} network network-mask [interface] [ticks ticks]
[area-count area-count]no access-list access-list-number {deny | permit} network network-mask [interface] [ticks ticks]
[area-count area-count]Syntax Description
Defaults
No access lists are predefined.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the NLSP route aggregation access list in the following situations:
•
Use the access list to instruct the router to redistribute an aggregated route instead of the explicit route. The access list also contains a "permit all" statement that instructs the router to redistribute explicit routes that are not subsumed by a route summary.
•
–
–
Note
Examples
The following example uses NLSP route aggregation access lists to redistribute routes learned from RIP to NLSP area1. Routes learned via RIP are redistributed into NLSP area1. Any routes learned via RIP that are subsumed by aaaa0000 ffff0000 are not redistributed. An address summary is generated instead.
ipx routingipx internal-network 2000interface ethernet 1ipx network 1001ipx nlsp area1 enableinterface ethernet 2ipx network 2001access-list 1200 deny aaaa0000 ffff0000access-list 1200 permit -1ipx router nlsp areaarea-address 1000 fffff000route-aggregationredistribute rip access-list 1200Related Commands
access-list (SAP filtering)
To define an access list for filtering Service Advertising Protocol (SAP) requests, use the SAP filtering form of the access-list global configuration command. To remove the access list, use the no form of this command.
access-list access-list-number {deny | permit} network[.node] [network-mask.node-mask]
[service-type [server-name]]no access-list access-list-number {deny | permit} network[.node] [network-mask.node-mask]
[service-type [server-name]]Syntax Description
access-list-number
Number of the SAP access list. This is a number from 1000 to 1099.
deny
Denies access if the conditions are matched.
permit
Permits access if the conditions are matched.
network
Network number. This is an eight-digit hexadecimal number that uniquely identifies a network cable segment. It can be a number in the range 1 to FFFFFFFE. A network number of 0 matches the local network. A network number of -1 matches all networks.
You do not need to specify leading zeros in the network number. For example, for the network number 000000AA, you can enter AA.
.node
(Optional) Node on network. This is a 48-bit value represented by a dotted triplet of four-digit hexadecimal numbers (xxxx.xxxx.xxxx).
network-mask.node-mask
(Optional) Mask to be applied to network and node. Place ones in the bit positions to be masked.
service-type
(Optional) Service type on which to filter. This is a hexadecimal number. A value of 0 means all services.
Table 295 in the "Usage Guidelines" section lists examples of service types.
server-name
(Optional) Name of the server providing the specified service type. This can be any contiguous string of printable ASCII characters. Use double quotation marks (" ") to enclose strings containing embedded spaces. You can use an asterisk (*) at the end of the name as a wildcard to match one or more trailing characters.
Defaults
No access lists are predefined.
Command Modes
Global configuration
Command History
Usage Guidelines
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 command. Do not use the network.node address of the particular interface board.
Table 295 lists some sample IPX SAP types. For more information about SAP types, contact Novell. Note that in the filter (specified by the service-type argument), we define a value of 0 to filter all SAP services. If, however, you receive a SAP packet with a SAP type of 0, this indicates an unknown service.
To delete a SAP access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:
no access-list access-list-number
To delete the access list for a specific network, use the following command:
no access-list access-list-number {deny | permit} network
Examples
The following access list blocks all access to a file server (service Type 4) on the directly attached network by resources on other Novell networks, but allows access to all other available services on the interface:
access-list 1001 deny -1 4access-list 1001 permit -1Related Commands
area-address (NLSP)
To define a set of network numbers to be part of the current NLSP area, use the area-address router configuration command. To remove a set of network numbers from the current NLSP area, use the no form of this command.
area-address address mask
no area-address address mask
Syntax Description
address
Network number prefix. This is a 32-bit hexadecimal number.
mask
Mask that defines the length of the network number prefix. This is a 32-bit hexadecimal number.
Defaults
No area address is defined by default.
Command Modes
Router configuration
Command History
Usage Guidelines
You must configure at least one area address before NLSP will operate.
The area-address command defines a prefix that includes all networks in the area. This prefix allows a single route to an area address to substitute for a longer list of networks.
All networks on which NLSP is enabled must fall under the area address prefix. This configuration is for future compatibility. When Level 2 NLSP becomes available, the only route advertised for the area will be the area address prefix (the prefix represents all networks within the area).
All routers in an NLSP area must be configured with a common area address, or they will form separate areas. You can configure up to three area addresses on the router.
The area address must have zero bits in all bit positions where the mask has zero bits. The mask must consist of only left-justified contiguous one bits.
Examples
The following example defines an area address that includes networks AAAABBC0 through AAAABBDF:
area-address AAAABBC0 FFFFFFE0The following example defines an area address that includes all networks:
area-address 0 0Related Commands
clear ipx accounting
To delete all entries in the accounting database when IPX accounting is enabled, use the clear ipx accounting EXEC command.
clear ipx accounting [checkpoint]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Specifying the clear ipx accounting command with no keywords copies the active database to the checkpoint database and clears all entries in the active database. When cleared, active database entries and static entries, such as those set by the ipx accounting-list command, are reset to zero. Dynamically found entries are deleted.
Any traffic that traverses the router after you issue the clear ipx accounting command is saved in the active database. Accounting information in the checkpoint database at that time reflects traffic prior to the most recent clear ipx accounting command.
You can also delete all entries in the active and checkpoint database by issuing the clear ipx accounting command twice in succession.
Examples
The following example first displays the contents of the active database before the contents are cleared. Then, the clear ipx accounting command clears all entries in the active database. As a result, the show ipx accounting command shows that there is no accounting information in the active database. Lastly, the show ipx accounting checkpoint command shows that the contents of the active database were copied to the checkpoint database when the clear ipx accounting command was issued.
Router# show ipx accountingSource Destination Packets Bytes0000C003.0000.0c05.6030 0000C003.0260.8c9b.4e33 72 28800000C001.0260.8c8d.da75 0000C003.0260.8c9b.4e33 14 6240000C003.0260.8c9b.4e33 0000C001.0260.8c8d.da75 62 31100000C001.0260.8c8d.e7c6 0000C003.0260.8c9b.4e33 20 14700000C003.0260.8c9b.4e33 0000C001.0260.8c8d.e7c6 20 1470Accounting data age is 6Router# clear ipx accountingRouter# show ipx accountingSource Destination Packets BytesAccounting data age is 0Router# show ipx accounting checkpointSource Destination Packets Bytes0000C003.0000.0c05.6030 0000C003.0260.8c9b.4e33 72 28800000C001.0260.8c8d.da75 0000C003.0260.8c9b.4e33 14 6240000C003.0260.8c9b.4e33 0000C001.0260.8c8d.da75 62 31100000C001.0260.8c8d.e7c6 0000C003.0260.8c9b.4e33 20 14700000C003.0260.8c9b.4e33 0000C001.0260.8c8d.e7c6 20 1470Accounting data age is 6Related Commands
clear ipx cache
To delete entries from the IPX fast-switching cache, use the clear ipx cache EXEC command.
clear ipx cache
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
The clear ipx cache command clears entries used for fast switching and autonomous switching.
Examples
The following example deletes all entries from the IPX fast-switching cache:
clear ipx cacheRelated Commands
Enables IPX fast switching.
Displays the contents of the IPX fast-switching cache.
clear ipx nhrp
To clear all dynamic entries from the Next Hop Resolution Protocol (NHRP) cache, use the clear ipx nhrp EXEC command.
clear ipx nhrp
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
This command does not clear any static (configured) IPX-to-NBMA address mappings from the NHRP cache.
Examples
The following example clears all dynamic entries from the NHRP cache for the interface:
clear ipx nhrpRelated Commands
clear ipx nlsp neighbors
To delete all NetWare Link Services Protocol (NLSP) adjacencies from the Cisco IOS software's adjacency database, use the clear ipx nlsp neighbors EXEC command.
clear ipx nlsp [tag] neighbors
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Deleting all entries from the adjacency database forces all routers in the area to perform the shortest path first (SPF) calculation.
When you specify an NLSP tag, the router clears all NLSP adjacencies discovered by that 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.
Note
Examples
The following example deletes all NLSP adjacencies from the adjacency database:
clear ipx nlsp neighborsThe following example deletes the NLSP adjacencies for process area2:
clear ipx nlsp area2 neighborsRelated Commands
Specifies the routing protocol to use.
Controls how often the Cisco IOS software performs the SPF calculation.
clear ipx route
To delete routes from the IPX routing table, use the clear ipx route EXEC command.
clear ipx route {network [network-mask] | default | *}
Syntax Description
Command Modes
EXEC
Command History
10.0
This command was introduced.
11.1
The following keyword and argument were added:
•
•
Usage Guidelines
After you use the clear ipx route command, RIP/SAP general requests are issued on all IPX interfaces.
For routers configured for NLSP route aggregation, use this command to clear an aggregated route from the routing table.
Examples
The following example clears the entry for network 3 from the IPX routing table:
clear ipx route 3The following example clears a route summary entry from the IPX routing table:
clear ipx route ccc00000 fff00000Related Commands
deny (extended)
To set conditions for a named IPX extended access list, use the deny access-list configuration command. To remove a deny condition from an access list, use the no form of this command.
deny 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-node-mask]] [destination-socket] [log]
no deny 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-node-mask]] [destination-socket] [log]
Syntax Description
Defaults
No access lists are defined.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to specify conditions under which a packet cannot pass the named access list.
For additional information on IPX protocol names and numbers, and IPX socket names and numbers, see the access-list (IPX extended) command.
Examples
The following example creates an extended access list named sal that denies all SPX packets:
ipx access-list extended saldeny spx any all any all logpermit anyRelated Commands
deny (NLSP route aggregation summarization)
To filter explicit routes and generate an aggregated route for a named NLSP route aggregation access list, use the deny access-list configuration command. To remove a deny condition from an access list, use the no form of this command.
deny network network-mask [ticks ticks] [area-count area-count]
no deny network network-mask [ticks ticks] [area-count area-count]
Syntax Description
Defaults
No access lists are defined.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to prevent the redistribution of explicit networks that are denied by the access list entry and, instead, generate an appropriate aggregated (summary) route.
For additional information on creating access lists that deny or permit area addresses that summarize routes, see the access-list (NLSP route aggregation summarization) command.
Examples
The following example from a configuration file defines the access list named finance for NLSP route aggregation. This access list prevents redistribution of explicit routes in the range 12345600 to 123456FF and, instead, summarizes these routes into a single aggregated route. The access list allows explicit route redistribution of all other routes.
ipx access-list summary financedeny 12345600 ffffff00permit -1Related Commands
deny (SAP filtering)
To set conditions for a named IPX SAP filtering access list, use the deny access-list configuration command. To remove a deny condition from an access list, use the no form of this command.
deny network[.node] [network-mask.node-mask] [service-type [server-name]]
no deny network[.node] [network-mask.node-mask] [service-type [server-name]]
Syntax Description
Defaults
No access lists are defined.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to specify conditions under which a packet cannot pass the named access list.
For additional information on IPX SAP service types, see the access-list (SAP filtering) command.
Examples
The following example creates a SAP access list named MyServer that denies MyServer to be sent in SAP advertisements:
ipx access-list sap MyServerdeny 1234 4 MyServerRelated Commands
deny (standard)
To set conditions for a named IPX access list, use the deny access-list configuration command. To remove a deny condition from an access list, use the no form of this command.
deny source-network[.source-node [source-node-mask]] [destination-network[.destination-node [destination-node-mask]]]
no deny source-network[.source-node [source-node-mask]] [destination-network[.destination-node [destination-node-mask]]]
Syntax Description
Defaults
No access lists are defined.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to specify conditions under which a packet cannot pass the named access list.
For additional information on creating IPX access lists, see the access-list (IPX standard) command.
Examples
The following example creates a standard access list named fred. It denies communication with only IPX network number 5678.
ipx access-list standard freddeny 5678 anypermit anyRelated Commands
distribute-list in (IPX)
To filter networks received in updates, use the distribute-list in router configuration command. To change or cancel the filter, use the no form of this command.
distribute-list {access-list-number | name} in [interface-name]
no distribute-list {access-list-number | name} in [interface-name]
Syntax Description
Defaults
Disabled
Command Modes
Router configuration
Command History
Examples
The following example causes only two networks—network 2 and network 3—to be accepted by an Enhanced IGRP routing process:
access-list 800 permit 2access-list 800 permit 3access-list 800 deny -1!ipx router eigrp 100network 3distribute-list 800 inRelated Commands
distribute-list out (IPX)
To suppress networks from being advertised in updates, use the distribute-list out router configuration command. To cancel this function, use the no form of this command.
distribute-list {access-list-number | name} out [interface-name | routing-process]
no distribute-list {access-list-number | name} out [interface-name | routing-process]
Syntax Description
Defaults
Disabled
Command Modes
Router configuration
Command History
Usage Guidelines
When redistributing networks, a routing process name can be specified as an optional trailing argument to the distribute-list out command. This causes the access list to be applied to only those routes derived from the specified routing process. After the process-specific access list is applied, any access list specified by a distribute-list out command without a process name argument is applied. Addresses not specified in the distribute-list out command are not advertised in outgoing routing updates.
Examples
The following example causes only one network—network 3—to be advertised by an Enhanced IGRP routing process:
access-list 800 permit 3access-list 800 deny -1!ipx router eigrp 100network 3distribute-list 800 outRelated Commands
distribute-sap-list in
To filter services received in updates, use the distribute-sap-list in router configuration command. To change or cancel the filter, use the no form of this command.
distribute-sap-list {access-list-number | name} in [interface-name]
no distribute-sap-list {access-list-number | name} in [interface-name]
Syntax Description
Defaults
Disabled
Command Modes
Router configuration
Command History
Examples
In the following example, the router redistributes Enhanced IGRP into NLSP area1. Only services for network 2 and 3 are accepted by the NLSP routing process.
access-list 1000 permit 2access-list 1000 permit 3access-list 1000 deny -1!ipx router nlsp area1redistribute eigrpdistribute-sap-list 1000 inRelated Commands
distribute-sap-list out
To suppress services from being advertised in SAP updates, use the distribute-sap-list out router configuration command. To cancel this function, use the no form of this command.
distribute-sap-list {access-list-number | name} out [interface-name | routing-process]
no distribute-sap-list {access-list-number | name} out [interface-name | routing-process]
Syntax Description
Defaults
Disabled
Command Modes
Router configuration
Command History
Usage Guidelines
When redistributing networks, a routing process name can be specified as an optional trailing argument to the distribute-sap-list out command. This causes the access list to be applied to only those routes derived from the specified routing process. After the process-specific access list is applied, any access list specified by a distribute-sap-list out command without a process name argument is applied. Addresses not specified in the distribute-sap-list out command are not advertised in outgoing routing updates.
Examples
The following example causes only services from network 3 to be advertised by an Enhanced IGRP routing process:
access-list 1010 permit 3access-list 1010 deny -1!ipx router eigrp 100network 3distribute-sap-list 1010 outRelated Commands
ipx access-group
To apply generic input and output filters to an interface, use the ipx access-group interface configuration command. To remove filters, use the no form of this command.
ipx access-group {access-list-number | name} [in | out]
no ipx access-group {access-list-number | name} [in | out]
Syntax Description
Defaults
No filters are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
Generic filters control which data packets an interface receives or sends out based on the packet's source and destination addresses, IPX protocol type, and source and destination socket numbers. You use the standard access-list and extended access-list commands to specify the filtering conditions.
You can apply only one input filter and one output filter per interface or subinterface.
When you do not specify an input (in) or output (out) filter in the command line, the default is an output filter.
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.
Examples
The following example applies access list 801 to Ethernet interface 1. Because the command line does not specify an input filter or output filter with the keywords in or out, the software assumes that it is an output filter.
interface ethernet 1ipx access-group 801The following example applies access list 901 to Ethernet interface 0. The access list is an input filter access list as specified by the keyword in.
interface ethernet 0ipx access-group 901 inTo remove the input access list filter in the previous example, you must specify the in keyword when you use the no form of the command. The following example correctly removes the access list:
interface ethernet 0no ipx access-group 901 inRelated Commands
ipx access-list
To define an IPX access list by name, use the ipx access-list global configuration command. To remove a named IPX access list, use the no form of this command.
ipx access-list {standard | extended | sap | summary} name
no ipx access-list {standard | extended | sap | summary} name
Caution
Syntax Description
Defaults
There is no default named IPX access list.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to configure a named IPX access list as opposed to a numbered IPX access list. This command will take you into access-list configuration mode, where you must define the denied or permitted access conditions with the deny and permit commands.
Specifying standard, extended, sap, or summary with the ipx access-list command determines the prompt you get when you enter access-list configuration mode.
Named access lists are not compatible with Cisco IOS releases prior to Release 11.3.
Examples
The following example creates a standard access list named fred. It permits communication with only IPX network number 5678.
ipx access-list standard fredpermit 5678 anydeny anyThe following example creates an extended access list named sal that denies all SPX packets:
ipx access-list extended saldeny spx any all any all logpermit anyThe following example creates a SAP access list named MyServer that allows only MyServer to be sent in SAP advertisements:
ipx access-list sap MyServerpermit 1234 4 MyServerThe following example creates a summary access list named finance that allows the redistribution of all explicit routes every 64 ticks:
ipx access-list summary financepermit -1 ticks 64Related Commands
ipx accounting
To enable IPX accounting, use the ipx accounting interface configuration command. To disable IPX accounting, use the no form of this command.
ipx accounting
no ipx accounting
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
IPX accounting allows 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 allows you to monitor both current traffic and traffic that has previously traversed the router.
IPX accounting statistics will be accurate even if IPX access lists are being used or if IPX fast switching is enabled. Enabling IPX accounting significantly decreases performance of a fast switched interface.
IPX accounting does not keep statistics if autonomous switching is enabled. In fact, IPX accounting is disabled if autonomous or SSE switching is enabled.
Examples
The following example enables IPX accounting on Ethernet interface 0:
interface ethernet 0ipx accountingRelated Commands
ipx accounting-list
To filter networks for which IPX accounting information is kept, use the ipx accounting-list global configuration command. To remove the filter, use the no form of this command.
ipx accounting-list number mask
no ipx accounting-list number mask
Syntax Description
Defaults
No filters are predefined.
Command Modes
Global configuration
Command History
Usage Guidelines
The source and destination addresses of each IPX packet traversing the router are compared with the network numbers in the filter. If there is a match, accounting information about the IPX packet is entered into the active accounting database. If there is no match, the IPX packet is considered to be a transit packet and may be counted, depending on the setting of the ipx accounting-transits global configuration command.
Examples
The following example adds all networks with IPX network numbers beginning with 1 to the list of networks for which accounting information is kept:
ipx accounting-list 1 0000.0000.0000Related Commands
ipx accounting-threshold
To set the maximum number of accounting database entries, use the ipx accounting-threshold global configuration command. To restore the default, use the no form of this command.
ipx accounting-threshold threshold
no ipx accounting-threshold threshold
Syntax Description
threshold
Maximum number of entries (source and destination address pairs) that the Cisco IOS software can accumulate.
Defaults
512 entries
Command Modes
Global configuration
Command History
Usage Guidelines
The accounting threshold defines the maximum number of entries (source and destination address pairs) that the software accumulates. The threshold is designed to prevent IPX accounting from consuming all available free memory. This level of memory consumption could occur in a router that is switching traffic for many hosts. To determine whether overflows have occurred, use the show ipx accounting EXEC command.
Examples
The following example sets the IPX accounting database threshold to 500 entries:
ipx accounting-threshold 500Related Commands
ipx accounting-transits
To set the maximum number of transit entries that will be stored in the IPX accounting database, use the ipx accounting-transits global configuration command. To disable this function, use the no form of this command.
ipx accounting-transits count
no ipx accounting-transits
Syntax Description
Defaults
0 entries
Command Modes
Global configuration
Command History
Usage Guidelines
Transit entries are those that do not match any of the networks specified by ipx accounting-list global configuration commands. If you have not defined networks with ipx accounting-list commands, IPX accounting tracks all traffic through the interface (all transit entries) up to the accounting threshold limit.
Examples
The following example specifies a maximum of 100 transit records to be stored in the IPX accounting database:
ipx accounting-transits 100Related Commands
ipx advertise-default-route-only (RIP)
To advertise only the default RIP route via the specified network, use the ipx advertise-default-route-only interface configuration command. To advertise all known RIP routes out the interface, use the no form of this command.
ipx advertise-default-route-only network
no ipx advertise-default-route-only network
Syntax Description
Defaults
All known routes are advertised out the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
If you specify the ipx advertise-default-route-only command, only a known default RIP route is advertised out the interface; no other networks will be advertised. If you have a large number of routes in the routing table, for example, on the order of 1000 routes, none of them will be advertised out the interface. However, if the default route is known, it will be advertised. Nodes on the interface can still reach any of the 1000 networks via the default route.
Specifying the ipx advertise-default-route-only command results in a significant reduction in CPU processing overhead when there are many routes and many interfaces. It also reduces the load on downstream routers.
This command applies only to RIP. NLSP and Enhanced IGRP are not affected when you enable this command. They continue to advertise all routes that they know about.
Note
Examples
The following example enables the advertising of the default route only:
interface ethernet 1ipx network 1234ipx advertise-default-route-only 1234Related Commands
Forwards to the default network all packets for which a route to the destination network is unknown.
ipx backup-server-query-interval (EIGRP)
To change the time between successive queries of each Enhanced IGRP neighbor's backup server table, use the ipx backup-server-query-interval global configuration command. To restore the default time, use the no form of this command.
ipx backup-server-query-interval interval
no ipx backup-server-query-interval
Syntax Description
interval
Minimum time, in seconds, between successive queries of each Enhanced IGRP neighbor's backup server table. The default is 15 seconds.
Defaults
15 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
A lower interval may use more CPU resources, but may cause lost server information to be retrieved from other servers' tables sooner.
Examples
The following example changes the server query time to 5 seconds:
ipx backup-server-query-interval 5ipx bandwidth-percent eigrp
To configure the percentage of bandwidth that may be used by Enhanced IGRP on an interface, use the ipx bandwidth-percent eigrp interface configuration command. To restore the default value, use the no form of this command.
ipx bandwidth-percent eigrp as-number percent
no ipx bandwidth-percent eigrp as-number
Syntax Description
Defaults
50 percent
Command Modes
Interface configuration
Command History
Usage Guidelines
Enhanced IGRP will use up to 50 percent of the bandwidth of a link, as defined by the bandwidth interface configuration command. This command may be used if some other fraction of the bandwidth is desired. Note that values greater than 100 percent may be configured; this may be useful if the bandwidth is set artificially low for other reasons.
Examples
The following example allows Enhanced IGRP to use up to 75 percent (42 kbps) of a 56-kbps serial link in autonomous system 209:
interface serial 0bandwidth 56ipx bandwidth-percent eigrp 209 75Related Commands
bandwidth
Sets a bandwidth value for an interface.
Specifies the routing protocol to use.
ipx broadcast-fastswitching
To enable the router to fast switch IPX directed broadcast packets, use the ipx broadcast-fastswitching global configuration command. To disable fast switching of IPX directed broadcast packets, use the no form of the command.
ipx broadcast-fastswitching
no ipx broadcast-fastswitching
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
The default behavior is to process-switch directed broadcast packets.
Command Modes
Global configuration
Command History
Usage Guidelines
A directed broadcast is one with a network layer destination address of the form net.ffff.ffff.ffff. The ipx broadcast-fastswitching command permits the router to fast switch IPX directed broadcast packets. This may be useful in certain broadcast-based applications that rely on helpering.
Note that the router never uses autonomous switching for eligible directed broadcast packets, even if autonomous switching is enabled on the output interface. Also note that routing and service updates are always exempt from this treatment.
Examples
The following example enables the router to fast switch IPX directed broadcast packets:
ipx broadcast-fastswitchingRelated Commands
ipx default-output-rip-delay
To set the default interpacket delay for RIP updates sent on all interfaces, use the ipx default-output-rip-delay global configuration command. To return to the initial default delay value, use the no form of this command.
ipx default-output-rip-delay delay
no ipx default-output-rip-delay
Syntax Description
delay
Delay, in milliseconds, 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
Global configuration
Command History
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet routing update. The ipx default-output-rip-delay command sets a default interpacket delay for all interfaces.
The system uses the delay specified by the ipx default-output-rip-delay command for periodic and triggered routing updates when no delay is set for periodic and triggered routing updates on an interface. When you set a delay for triggered routing updates, the system uses the delay specified by the ipx default-output-rip-delay command for only the periodic routing updates sent on all interfaces.
To set a delay for triggered routing updates, see the ipx triggered-rip-delay or ipx default-triggered-rip-delay commands.
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 sets a default interpacket delay of 55 ms for RIP updates sent on all interfaces:
ipx default-output-rip-delay 55Related Commands
ipx default-output-sap-delay
To set a default interpacket delay for SAP updates sent on all interfaces, use the ipx default-output-sap-delay global configuration command. To return to the initial default
delay value, use the no form of this command.ipx default-output-sap-delay delay
no ipx default-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
Global configuration
Command History
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet SAP update. The ipx default-output-sap-delay command sets a default interpacket delay for all interfaces.
The system uses the delay specified by the ipx default-output-sap-delay command for periodic and triggered SAP updates when no delay is set for periodic and triggered updates on an interface. When you set a delay for triggered updates, the system uses the delay specified by the ipx default-output-sap-delay command only for the periodic SAP updates sent on all interfaces.
To set a delay for triggered updates, see the ipx triggered-sap-delay or ipx default-triggered-sap-delay commands.
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 this 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 interfaces.
Examples
The following example sets a default interpacket delay of 55 ms for SAP updates sent on all interfaces:
ipx default-output-sap-delay 55Related Commands
ipx default-route
To forward to the default network all packets for which a route to the destination network is unknown, use the ipx default-route global configuration command. To disable the use of the default network, use the no form of this command.
ipx default-route
no ipx default-route
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled: All packets for which a route to the destination is unknown are forwarded to the default network, which is -2 (0xFFFFFFFE).
Command Modes
Global configuration
Command History
Usage Guidelines
When you use the no ipx default-route command, Cisco IOS software no longer uses -2 as the default network. Instead, the software interprets -2 as a regular network and packets for which a route to the destination network is unknown are dropped.
Examples
The following example disables the forwarding of packets towards the default network:
no ipx default-routeRelated Commands
ipx default-triggered-rip-delay
To set the default interpacket delay for triggered RIP updates sent on all interfaces, use the ipx default-triggered-rip-delay global configuration command. To return to the system default delay, use the no form of this command.
ipx default-triggered-rip-delay delay
no ipx default-triggered-rip-delay [delay]
Syntax Description
delay
Delay, in milliseconds, 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
Global configuration
Command History
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet routing update. A triggered routing update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.
The ipx default-triggered-rip-delay command sets the default interpacket delay for triggered routing updates sent on all interfaces. On a single interface, you can override this global default delay for triggered routing updates using the ipx triggered-rip-delay interface command.
The global default delay for triggered routing updates overrides the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered routing updates.
If the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command is high, then we strongly recommend a low delay value for triggered routing updates so that updates triggered by special events are sent in a more timely manner than periodic routing updates.
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 approximately 100 ms.
When you do not set the interpacket delay for triggered routing updates, the system uses the delay specified by the ipx output-rip-delay or ipx default-output-rip-delay command for both periodic and triggered routing updates.
When you use the no form of the ipx default-triggered-rip-delay command, the system uses the delay set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered RIP updates, if set. Otherwise, the system uses the initial default delay as described in the "Defaults" section.
This command is also useful on limited bandwidth point-to-point links, or X.25 and Frame Relay multipoint interfaces.
Examples
The following example sets an interpacket delay of 55 ms for triggered routing updates sent on all interfaces:
ipx default-triggered-rip-delay 55Related Commands
ipx default-triggered-sap-delay
To set the default interpacket delay for triggered SAP updates sent on all interfaces, use the ipx default-triggered-sap-delay global configuration command. To return to the system default delay, use the no form of this command.
ipx default-triggered-sap-delay delay
no ipx default-triggered-sap-delay [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
Global configuration
Command History
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet SAP update. A triggered SAP update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.
The ipx default-triggered-sap-delay command sets the default interpacket delay for triggered SAP updates sent on all interfaces. On a single interface, you can override this global default delay for triggered updates using the ipx triggered-sap-delay interface command.
The global default delay for triggered updates overrides the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered updates.
If the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command is high, then we strongly recommend a low delay value for triggered updates so that updates triggered by special events are sent in a more timely manner than periodic updates.
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 this command forces the router to pace its output to the slower-processing needs of these IPX servers.
The default delay on a NetWare 3.11 server is approximately 100 ms.
When you do not set the interpacket delay for triggered SAP updates, the system uses the delay specified by the ipx output-sap-delay or ipx default-output-sap-delay command for both periodic and triggered SAP updates.
When you use the no form of the ipx default-triggered-sap-delay command, the system uses the delay set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered SAP updates, if set. Otherwise, the system uses the initial default delay as described in the "Defaults" section.
This command is also useful on limited bandwidth point-to-point links, or X.25 and Frame Relay multipoint interfaces.
Examples
The following example sets an interpacket delay of 55 ms for triggered SAP updates sent on all interfaces:
ipx default-triggered-sap-delay 55Related Commands
ipx delay
To set the tick count, use the ipx delay interface configuration command. To reset the default increment in the delay field, use the no form of this command.
ipx delay ticks
no ipx delay
Syntax Description
ticks
Number of IBM clock ticks of delay to use. One clock tick is 1/18 of a second (approximately 55 ms).
Defaults
The default delay is determined from the delay configured on the interface with the delay command. It is (interface delay + 333) / 334. Therefore, unless you change the delay by a value greater than 334, you will not notice a difference.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx delay command sets the count used in the IPX RIP delay field, which is also known as the ticks field.
IPXWAN links determine their delay dynamically. If you do not specify the ipx delay command on an interface and you have not changed the interface delays with the interface delay interface configuration command, all LAN interfaces have a delay of 1 and all WAN interfaces have a delay of 6. The preferred method of adjusting delays is to use the ipx delay command, not the interface delay command. The show ipx interface EXEC command display only the delay value configured with the ipx delay command.
With IPXWAN, if you change the interface delay with the interface delay command, the ipx delay command uses that delay when calculating a delay to use. Also, when changing delays with IPXWAN, the changes affect only the link's calculated delay on the side considered to be the master.
Leaving the delay at its default value is sufficient for most interfaces.
Examples
The following example changes the delay for serial interface 0 to 10 ticks:
interface serial 0 ipx delay 10Related Commands
ipx down
To administratively shut down an IPX network, use the ipx down interface configuration command. To restart the network, use the no form of this command.
ipx down network
no ipx down
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx down command administratively shuts down the specified network. 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. This allows the neighboring systems to update their routing, SAP, and other tables without having to wait for routes and services learned via this network to time out.
To shut down an interface in a manner that is considerate of one's neighbor, use ipx down before using the shutdown command.
Examples
The following example administratively shuts down network AA on Ethernet interface 0:
interface ethernet 0 ipx down AAipx eigrp-sap-split-horizon
To configure Enhanced IGRP SAP split horizon, use the ipx eigrp-sap-split-horizon global configuration command. To revert to default, use the no form of this command.
ipx eigrp-sap-split-horizon
no ipx eigrp-sap-split-horizon
Syntax Description
This command has no argument or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
When split horizon is enabled, Enhanced IGRP SAP update and packets are not sent back to the same interface where the SAP is received from. This reduces the number of Enhanced IGRP packets on the network.
Split horizon blocks information about SAPs from being advertised by a router about any interface from which that information originated. Typically, this behavior 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 may wish to disable split horizon.
Note
Examples
The following example disables split horizon on the router:
no ipx eigrp-sap-split-horizonRelated Commands
Configures incremental SAP split horizon.
Configures split horizon.
Displays the neighbors discovered by Enhanced IGRP.
ipx gns-reply-disable
To disable the sending of replies to IPX Get Nearest Server (GNS) queries, use the ipx gns-reply-disable interface configuration command. To return to the default, use the no form of this command.
ipx gns-reply-disable
no ipx gns-reply-disable
Syntax Description
This command has no arguments or keywords.
Defaults
Replies are sent to IPX GNS queries.
Command Modes
Interface configuration
Command History
Examples
The following example disables the sending of replies to GNS queries on Ethernet interface 0:
interface ethernet 0ipx gns-reply-disableRelated Commands
ipx gns-response-delay
To change the delay when responding to Get Nearest Server (GNS) requests, use the ipx gns-response-delay global or interface configuration command. To return to the default delay, use the no form of this command.
ipx gns-response-delay [milliseconds]
no ipx gns-response-delay
Syntax Description
Defaults
0 (no delay)
Command Modes
Global configuration (globally changes the delay for the router). Interface configuration (overrides the globally configured delay for an interface)
Command History
Usage Guidelines
This command can be used in two modes: global configuration or interface configuration. In both modes, the command syntax is the same. A delay in responding to GNS requests might be imposed so that, in certain topologies, any local Novell IPX servers respond to the GNS requests before our software does. It is desirable to have these end-host server systems get their reply to the client before the router does because the client typically takes the first response, not the best response. In this case the best response is the one from the local server.
NetWare 2.x has a problem with dual-connected servers in parallel with a router. If you are using this version of NetWare, you should set a GNS delay. A value of 500 ms is recommended.
In situations in which servers are always located across routers from their clients, there is no need for a delay to be imposed.
Examples
The following example sets the delay in responding to GNS requests to 500 ms (0.5 seconds):
ipx gns-response-delay 500Related Commands
Disables the sending of replies to IPX GNS queries.
Changes the delay when responding to RIP requests.
ipx gns-round-robin
To rotate using a round-robin selection method through a set of eligible servers when responding to Get Nearest Server (GNS) requests, use the ipx gns-round-robin global configuration command. To use the most recently learned server, use the no form of this command.
ipx gns-round-robin
no ipx gns-round-robin
Syntax Description
The command has no arguments or keywords.
Defaults
The most recently learned, eligible server is used.
Command Modes
Global configuration
Command History
Usage Guidelines
In the normal server selection process, requests for service are responded to with the most recently learned, closest server. If you enable the round-robin method, the Cisco IOS software maintains a list of the nearest servers eligible to provide specific services. It uses this list when responding to GNS requests. Responses to requests are distributed in a round-robin fashion across all active IPX interfaces on the router.
Eligible servers are those that satisfy the "nearest" requirement for a given request and that are not filtered either by a SAP filter or by a GNS filter.
Examples
The following example responds to GNS requests using a round-robin selection method from a list of eligible nearest servers:
ipx gns-round-robinRelated Commands
Controls which servers are included in the GNS responses sent by the Cisco IOS software.
Sets the interpacket delay for SAP updates sent on a single interface.
ipx hello-interval eigrp
To configure the interval between Enhanced IGRP hello packets, use the ipx hello-interval eigrp interface configuration command. To restore the default interval, use the no form of this command.
ipx hello-interval eigrp autonomous-system-number seconds
no ipx hello-interval eigrp autonomous-system-number seconds
Syntax Description
Defaults
For low-speed NBMA networks: 60 seconds
For all other networks: 5 secondsCommand Modes
Interface configuration
Command History
Usage Guidelines
The default of 60 seconds applies only to low-speed, nonbroadcast, multiaccess (NBMA) media. Low speed is considered to be a rate of T1 or slower, as specified with the bandwidth interface configuration command. Note that for purposes of Enhanced IGRP, Frame Relay and SMDS networks may or may not be considered to be NBMA. These networks are considered NBMA if the interface has not been configured to use physical multicasting; otherwise they are considered not to be NBMA.
Examples
The following example changes the hello interval to 10 seconds:
interface ethernet 0ipx network 10ipx hello-interval eigrp 4 10Related Commands
Specifies the length of time a lost Enhanced IGRP route is placed in the hold-down state.
ipx helper-address
To forward broadcast packets to a specified server, use the ipx helper-address interface configuration command. To disable this function, use the no form of this command.
ipx helper-address network.node
no ipx helper-address network.node
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Routers normally block all broadcast requests and do not forward them to other network segments. This is done to prevent the degradation of performance over the entire network. The ipx helper-address command allows broadcasts to be forwarded to other networks. This is useful when a network segment does not have an end-host capable of servicing a particular type of broadcast request. This command lets you forward the broadcasts to a server, network, or networks that can process them. Incoming unrecognized broadcast packets that match the access list created with the ipx helper-list command, if it is present, are forwarded.
You can specify multiple ipx helper-address commands on a given interface.
The Cisco IOS software supports all-networks flooded broadcasts (sometimes referred to as all-nets flooding). These are broadcast messages that are forwarded to all networks. To configure the all-nets flooding, define the IPX helper address for an interface as follows:
ipx helper-address -1.FFFF.FFFF.FFFFOn systems configured for IPX routing, this helper address is displayed as follows (via the show ipx interface command):
FFFFFFFF.FFFF.FFFF.FFFFAlthough our software takes care to keep broadcast traffic to a minimum, some duplication is unavoidable. When loops exist, all-nets flooding can propagate bursts of excess traffic that will eventually age out when the hop count reaches its limit (16 hops). Use all-nets flooding carefully and only when necessary. Note that you can apply additional restrictions by defining a helper list.
To forward type 20 packets to only those nodes specified by the ipx helper-address command, use the ipx helper-address command in conjunction with the ipx type-20-helpered global configuration command.
To forward type 20 packets to all nodes on the network, use the ipx type-20-propagation command. See the ipx type-20-propagation command for more information.
Examples
The following example forwards all-nets broadcasts on Ethernet interface 0 (except type 20 propagation packets) are forwarded to IPX server 00b4.23cd.110a on network bb:
interface ethernet 0 ipx helper-address bb.00b4.23cd.110aRelated Commands
ipx helper-list
To assign an access list to an interface to control broadcast traffic (including type 20 propagation packets), use the ipx helper-list interface configuration command. To remove the access list from an interface, use the no form of this command.
ipx helper-list {access-list-number | name}
no ipx helper-list {access-list-number | name}
Syntax Description
Defaults
No access list is preassigned.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx helper-list command specifies an access list to use in forwarding broadcast packets. One use of this command is to prevent client nodes from discovering services they should not use.
Because the destination address of a broadcast packet is by definition the broadcast address, this command is useful only for filtering based on the source address of the broadcast packet.
The helper list, if present, is applied to both all-nets broadcast packets and type 20 propagation packets.
The helper list on the input interface is applied to packets before they are output via either the helper address or type 20 propagation packet mechanism.
Examples
The following example assigns access list 900 to Ethernet interface 0 to control broadcast traffic:
interface ethernet 0ipx helper-list 900Related Commands
ipx hold-down eigrp
To specify the length of time a lost Enhanced IGRP route is placed in the hold-down state, use the ipx hold-down eigrp interface configuration command. To restore the default time, use the no form of this command.
ipx hold-down eigrp autonomous-system-number seconds
no ipx hold-down eigrp autonomous-system-number seconds
Syntax Description
autonomous-system-number
Enhanced IGRP autonomous system number. It can be a number from 1 to 65535.
seconds
Hold-down time, in seconds. The default hold time is 5 seconds.
Defaults
5 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
When an Enhanced IGRP route is lost, it is placed into a hold-down state for a period of time. The purpose of the hold-down state is to ensure the validity of any new routes for the same destination.
The amount of time a lost Enhanced IGRP route is placed in the hold-down state is configurable. Set the amount of time to a value longer than the default of 5 seconds if your network requires a longer time for the unreachable route information to propagate.
Examples
The following example changes the hold-down time for autonomous system from 4 to 45 seconds:
interface ethernet 0ipx network 10ipx hold-down eigrp 4 45ipx hold-time eigrp
To specify the length of time a neighbor should consider Enhanced IGRP hello packets valid, use the ipx hold-time eigrp interface configuration command. To restore the default time, use the no form of this command.
ipx hold-time eigrp autonomous-system-number seconds
no ipx hold-time eigrp autonomous-system-number seconds
Syntax Description
Defaults
For low-speed NBMA networks: 180 seconds
For all other networks: 15 secondsCommand Modes
Interface configuration
Command History
Usage Guidelines
If the current value for the hold time is less than two times the interval between hello packets, the hold time will be reset to three times the hello interval.
If a router does not receive a hello packet within the specified hold time, routes through the router are considered available.
Increasing the hold time delays route convergence across the network.
The default of 180 seconds applies only to low-speed, nonbroadcast, multiaccess (NBMA) media. Low speed is considered to be a rate of T1 or slower, as specified with the bandwidth interface configuration command.
Examples
The following example changes the hold time to 45 seconds:
interface ethernet 0ipx network 10ipx hold-time eigrp 4 45Related Commands
ipx input-network-filter (RIP)
To control which networks are added to the Cisco IOS software's routing table, use the ipx input-network-filter interface configuration command. 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
To control which services are added to the Cisco IOS software's SAP table, use the ipx input-sap-filter interface configuration command. 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
To set an internal network number for use by NLSP and IPXWAN, use the ipx internal-network global configuration command. 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 ipxwan
To enable the IPXWAN protocol on a serial interface, use the ipx ipxwan interface configuration command. 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
local-node
(Optional) Primary network number of the router. This is an IPX network number that is unique across the entire internetwork. On NetWare 3.x servers, the primary network number is called the internal network number. The device with the higher number is determined to be the link master. A value of 0 causes the Cisco IOS software to use the configured internal network number.
network-number
(Optional) IPX network number to be used for the link if this router is the one determined to be the link master. The number is an eight-digit hexadecimal number that uniquely identifies a network cable segment. It can be a number in the range 0 to FFFFFFFD. A value 0 is equivalent to specifying the keyword unnumbered.
You do not need to specify leading zeros in the network number. For example, for the network number 000000AA, you can enter AA.
unnumbered
(Optional) Specifies that no IPX network number is defined for the link. This is equivalent to specifying a value of 0 for the network-number argument.
local-server-name
(Optional) Name of the local router. It can be up to 47 characters long, and can contain uppercase letters, digits, underscores (_), hyphens (-), and at signs (@). On NetWare 3.x servers, this is the router name. For our routers, this is the name of the router as configured via the hostname command; that is, the name that precedes the standard prompt, which is an angle bracket (>) for EXEC mode or a pound sign (#) for privileged EXEC mode.
retry-interval
(Optional) Retry interval, in seconds. This interval defines how often the software will retry the IPXWAN start-up negotiation if a start-up failure occurs. Retries will occur until the retry limit defined by the retry-limit argument is reached. It can be a value from 1 to 600. The default is 20 seconds.
retry-limit
(Optional) Maximum number of times the software retries the IPXWAN start-up negotiation before taking the action defined by the ipx ipxwan error command. It can be a value from 1 through 100. The default is 3.
Defaults
IPXWAN is disabled.
If you enable IPXWAN, the default is unnumbered.
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
10.3
The following keyword and argument were added:
•
•
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 0 local-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
To define how to handle IPXWAN when IPX fails to negotiate properly at link startup, use the ipx ipxwan error interface configuration command. 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
Enables the IPXWAN protocol on a serial interface.
Negotiates static routes on a link configured for IPXWAN.
ipx ipxwan static
To negotiate static routes on a link configured for IPXWAN, use the ipx ipxwan static interface configuration command. 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
Enables the IPXWAN protocol on a serial interface.
Defines how to handle IPXWAN when IPX fails to negotiate properly at link startup.
ipx link-delay
To specify the link delay, use the ipx link-delay interface configuration command. 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. The value is also supplied to NLSP for use in metric calculations.
Examples
The following example sets the link delay to 20 microseconds:
ipx link-delay 20Related Commands
Enables the IPXWAN protocol on a serial interface.
Sets the amount of time to wait before starting the spoofing of SPX keepalive packets following inactive data transfer.
ipx linkup-request (RIP)
To enable the sending of a general RIP and/or SAP query when an interface comes up, use the
ipx linkup-request interface configuration command. 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.
Configures the router to send a SAP update immediately following a RIP broadcast.
ipx maximum-hops (RIP)
To set the maximum hop count allowed for IPX packets, use the ipx maximum-hops global configuration command. 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
To set the maximum number of equal-cost paths the Cisco IOS software uses when forwarding packets, use the ipx maximum-paths global configuration command. 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
Sets the tick count.
Enables per-host load sharing.
Displays the contents of the IPX routing table.
ipx netbios input-access-filter
To control incoming IPX NetBIOS FindName messages, use the ipx netbios input-access-filter interface configuration command. 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
To control outgoing NetBIOS FindName messages, use the ipx netbios output-access-filter interface configuration command. 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
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-checksipx network
To enable IPX routing on a particular interface and to optionally select the type of encapsulation (framing), use the ipx network interface configuration command. 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
Defaults
IPX routing is disabled.
Encapsulation types:
For Ethernet: novell-ether
For Token Ring: sap
For FDDI: snapIf 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
NLSP does not support secondary networks. You must use subinterfaces in order to use multiple encapsulations with NLSP.
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 using other 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.
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.
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 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.
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 0interface ethernet 0.1ipx network 1 encapsulation novell-etherinterface ethernet 0.2ipx network 2 encapsulation snapinterface ethernet 0.3ipx network 3 encapsulation arpainterface ethernet 0.4ipx 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 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.2ipx network f02 encapsulation snapinterface fddi 0.3ipx network f03 encapsulation novell-fddiRelated Commands
ipx nhrp authentication
To configure the authentication string for an interface using Next Hop Resolution Protocol (NHRP), use the ipx nhrp authentication interface configuration command. 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
To change the number of seconds that NHRP nonbroadcast, multiaccess (NBMA) addresses are advertised as valid in authoritative NHRP responses, use the ipx nhrp holdtime interface configuration command. 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 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
To control which IPX packets can trigger sending a Next Hop Resolution Protocol (NHRP) Request, use the ipx nhrp interest interface configuration command. 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
ipx nhrp map
To statically configure the IPX-to-NBMA address mapping of IPX destinations connected to a nonbroadcast, multiaccess (NBMA) network, use the ipx nhrp map interface configuration command. 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
To change the maximum frequency at which NHRP packets can be sent, use the ipx nhrp max-send interface configuration command. 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 which can be transmitted in the range 1 to 65535.
every interval
Time (in seconds) in the range 10 to 65535. 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 interval.
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
To enable the Next Hop Resolution Protocol (NHRP) on an interface, use the ipx nhrp network-id interface configuration command. 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 4294967295.
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
To specify the address of one or more NHRP Next Hop Servers, use the ipx nhrp nhs interface configuration command. 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
To re-enable the use of forward record and reverse record options in NHRP Request and Reply packets, use the ipx nhrp record interface configuration command. 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
Designates the primary IPX address of the interface that the Next Hop Server uses in NHRP Reply packets when the NHRP requester uses the Responder Address option.
ipx nhrp responder
To designate which interface's primary IPX address that the Next Hop Server uses in NHRP Reply packets when the NHRP requestor uses the Responder Address option, use the ipx nhrp responder interface configuration command. 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
To configure the software so that NHRP is deferred until the system has attempted to send data traffic to a particular destination multiple times, use the ipx nhrp use interface configuration command. 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
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
Controls which IPX packets can trigger sending an NHRP Request.
Changes the maximum frequency at which NHRP packets can be sent.
ipx nlsp csnp-interval
To configure the NLSP complete sequence number PDU (CSNP) interval, use the ipx nlsp csnp-interval interface configuration command. 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
Specifies the hello multiplier used on an interface.
Configures RIP compatibility when NLSP is enabled.
ipx nlsp enable
To enable NLSP routing on the primary network configured on this interface or subinterface, use the ipx nlsp enable interface configuration command. 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
Configures RIP compatibility when NLSP is enabled.
Configures SAP compatibility when NLSP in enabled.
ipx nlsp hello-interval
To configure the interval between the transmission of hello packets, use the ipx nlsp hello-interval interface configuration command. 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 routersCommand 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
Configures the NLSP CSNP interval.
Configures the time delay between successive NLSP LSP transmissions.
Configures RIP compatibility when NLSP is enabled.
ipx nlsp hello-multiplier
To specify the hello multiplier used on an interface, use the ipx nlsp hello-multiplier interface configuration command. 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
To configure the time delay between successive NLSP link-state packet (LSP) transmissions, use the ipx nlsp lsp-interval interface configuration command. To restore the default time delay, use the no form of the 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 milliseconds (10 packets per second) on Ethernet interface 0:
interface Ethernet 0ipx nlsp lsp-interval 100Related Commands
ipx nlsp metric
To configure the NLSP cost for an interface, use the ipx nlsp metric interface configuration command. 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 based on 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 multicast
To configure an interface to use multicast addressing, use the ipx nlsp multicast interface configuration command. 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 ethernet0no ipx nlsp multicastipx nlsp priority
To configure the election priority of the specified interface for designated router election, use the ipx nlsp priority interface configuration command. 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
To configure the link-state packet (LSP) retransmission interval on WAN links, use the ipx nlsp retransmit-interval interface configuration command. 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
Configures the NLSP CSNP interval.
Specifies the hello multiplier used on an interface.
ipx nlsp rip
To configure RIP compatibility when NLSP is enabled, use the ipx nlsp rip interface configuration command. 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
Configures the interval between the transmission of hello packets.
Configures SAP compatibility when NLSP in enabled.
ipx nlsp sap
To configure SAP compatibility when NLSP in enabled, use the ipx nlsp sap interface configuration command. 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
Configures the interval between the transmission of hello packets.
Configures RIP compatibility when NLSP is enabled.
ipx output-gns-filter
To control which servers are included in the GetNearest Server (GNS) responses sent by the Cisco IOS software, use the ipx output-gns-filter interface configuration command. 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)
To control the list of networks included in routing updates sent out an interface, use the ipx output-network-filter interface configuration command. 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
To set the interpacket delay for RIP updates sent on a single interface, use the ipx output-rip-delay interface configuration command. 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, 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
To set the interpacket delay for Service Advertising Protocol (SAP) updates sent on a single interface, use the ipx output-sap-delay interface configuration command. 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
To control which services are included in SAP updates sent by the Cisco IOS software, use the ipx output-sap-filter interface configuration command. 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
The 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
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 interface configuration command. 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 interfacesCommand 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
To enable per-host load sharing, use the ipx per-host-load-share global configuration command. To disable per-host load sharing, use the no form of the 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
Sets the maximum number of equal-cost paths the Cisco IOS software uses when forwarding packets.
ipx ping-default
To select the ping type that the Cisco IOS software transmits, use the ipx ping-default global configuration command. 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 of IPX ping-default when diagnostic 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 rip-max-packetsize
To configure the maximum packet size of RIP updates sent out the interface, use the ipx rip-max-packetsize interface configuration command. 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 rip-multiplier
To configure the interval at which a network's RIP entry ages out, use the ipx rip-multiplier interface configuration command. 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
Configures the router to send a SAP update immediately following a RIP broadcast.
ipx rip-response-delay
To change the delay when responding to Routing Information Protocol (RIP) requests, use the ipx rip-response-delay interface configuration command. 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 route
To add a static route or static NLSP route summary to the routing table, use the ipx route global configuration command. 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
10.0
This command was introduced.
10.3
The following keywords and arguments were added:
•
•
•
•
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
Forwards to the default network all packets for which a route to the destination network is unknown.
Displays the contents of the IPX routing table.
ipx route-cache
To enable IPX fast switching, use the ipx route-cache interface configuration command. 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, 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
To adjust the period and rate of route cache invalidation because of inactivity, use the ipx route-cache inactivity-timeout global configuration command. 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
To set a maximum limit on the number of entries in the IPX route cache, use the ipx route-cache max-size global configuration command. 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
To adjust the period and rate of route cache invalidation because of aging, use the ipx route-cache update-timeout global configuration command. 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
To specify the routing protocol to use, use the ipx router global configuration command. 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
10.0
This command was introduced.
11.0
The following keyword and argument were added:
•
•
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
ipx router-filter
To filter the routers from which packets are accepted, use the ipx router-filter interface configuration command. 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
To filter Service Advertising Protocol (SAP) messages received from a particular router, use the ipx router-sap-filter interface configuration command. 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
To enable IPX routing, use the ipx routing global configuration command. 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
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
Enables IPX routing on a particular interface and optionally selects the type of encapsulation (framing).
ipx sap
To specify static Service Advertising Protocol (SAP) entries, use the ipx sap global configuration command. To remove static SAP entries, use the no form of this command.
ipx sap service-type name network.node socket hop-count
no ipx sap service-type name network.node socket hop-count
Syntax Description
service-type
SAP service-type number. Table 295 earlier in this chapter lists some IPX SAP services.
name
Name of the server that provides the service.
network.node
Network number and node address of the server.
The argument network is an eight-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.
The argument node is the node number of the target Novell server. This is a 48-bit value represented by a dotted triplet of four-digit hexadecimal numbers (xxxx.xxxx.xxxx).
socket
Socket number for this service. earlier in this chapter lists some IPX socket numbers.
hop-count
Number of hops to the server.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
The ipx sap command allows you to add static entries into the SAP table. Each entry has a SAP service associated with it. Static SAP assignments always override any identical entries in the SAP table that are learned dynamically, regardless of hop count. The router will not announce a static SAP entry unless it has a route to that network.
Examples
In the following example, the route to JOES_SERVER is not yet learned, so the system displays an informational message. The JOES_SERVER service will not be announced in the regular SAP updates until the Cisco IOS software learns the route to it either by means of a RIP update from a neighbor or an ipx sap command.
ipx sap 107 MAILSERV 160.0000.0c01.2b72 8104 1ipx sap 4 FILESERV 165.0000.0c01.3d1b 451 1ipx sap 143 JOES_SERVER A1.0000.0c01.1234 8170 2no route to A1, JOES_SERVER won't be announced until route is learnedRelated Commands
ipx sap follow-route-path
To enable a router to accept IPX Service Advertising Protocol (SAP) entries from SAP updates received on an interface only if that interface is one of the best paths to reach the destination networks of those SAPs, use the ipx sap follow-route-path command in global configuration mode. To disable this router function, use no form of this command.
ipx sap follow-route-path
no ipx sap follow-route-path
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
In redundantly connected networks that use IPX-Enhanced IGRP routing in which multiple IPX paths exist, IPX SAP services can be learned on nonoptimal interfaces, causing SAP loops, also known as phantom SAPs, when those services become obsolete. Use the ipx sap follow-route-path command to prevent the occurrence of SAP loops.
When the ipx sap follow-route-path command is used, the router screens individual services (SAPs) in SAP updates. The router looks at the destination network number of each SAP entry's . If the receiving interface is one of the best interfaces to reach the destination network of the SAP, that SAP entry is accepted. Otherwise, the SAP entry is discarded.
Caution
Examples
The following example enables the router to accept only the IPX SAP entries from SAP updates received on an interface deemed to be one of the best paths to the destination address of those SAPs:
ipx sap follow-route-pathRelated Commands
ipx server-split-horizon-on-server-paths
Controls whether Service Information split horizon checking should be based on RIP or SAP.
ipx sap-incremental (EIGRP)
To send Service Advertising Protocol (SAP) updates only when a change occurs in the SAP table, use the ipx sap-incremental interface configuration command. To send periodic SAP updates, use the no form of this command.
ipx sap-incremental eigrp autonomous-system-number [rsup-only]
no ipx sap-incremental eigrp autonomous-system-number [rsup-only]
Syntax Description
Defaults
Enabled on serial interfaces
Disabled on LAN media (Ethernet, Token Ring, FDDI)
Command Modes
Interface configuration
Command History
Usage Guidelines
To use the ipx sap-incremental command, you must enable Enhanced IGRP. This is the case even if you want to use only RIP routing. You must do this because the incremental SAP feature requires the Enhanced IGRP reliable transport mechanisms.
With this functionality enabled, if an IPX Enhanced IGRP peer is found on the interface, SAP updates will be sent only when a change occurs in the SAP table. Periodic SAP updates are not sent. When no IPX Enhanced IGRP peer is present on the interface, periodic SAPs are always sent, regardless of how this command is set.
If you configure the local router to send incremental SAP updates on an Ethernet, and if the local device has at least one IPX Enhanced IGRP neighbor and any servers, clients, or routers that do not have IPX Enhanced IGRP configured on the Ethernet interface, these devices will not receive complete SAP information from the local router.
If the incremental sending of SAP updates on an interface is configured and no IPX Enhanced IGRP peer is found, SAP updates will be sent periodically until a peer is found. Then, updates will be sent only when changes occur in the SAP table.
To take advantage of Enhanced IGRP's incremental SAP update mechanism while using the RIP routing protocol instead of the Enhanced IGRP routing protocol, specify the rsup-only keyword. SAP updates are then sent only when changes occur, and only changes are sent. Use this feature only when you want to use RIP routing; Cisco IOS software disables the exchange of route information via Enhanced IGRP for that interface.
Examples
The following example sends SAP updates on Ethernet interface 0 only when there is a change in the SAP table:
interface ethernet 0ipx sap-incremental eigrp 200ipx sap-incremental split-horizon
To configure incremental SAP split horizon, use the ipx sap-incremental split-horizon interface configuration command. To disable split horizon, use the no form of this command.
ipx sap-incremental split-horizon
no ipx sap-incremental split-horizon
Syntax Description
This command has no argument or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Caution
be turned on. Otherwise, a warning message like the following will be displayed:
%IPX EIGRP not running.
When split horizon is enabled, Enhanced IGRP incremental SAP update packets are not sent back to the same interface from where the SAP is received. This reduces the number of Enhanced IGRP packets on the network.
Split horizon blocks information about SAPs from being advertised by a router to the same interface from where that SAP is received. Typically, this behavior 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 may wish to disable split horizon.
Note
Examples
The following example disables split horizon on serial interface 0:
interface serial 0no ipx sap-incremental split-horizonRelated Commands
Configures Enhanced IGRP SAP split horizon.
ipx split-horizon eigrp
Configures split horizon.
show ipx eigrp neighbors
Displays the neighbors discovered by Enhanced IGRP.
ipx sap-max-packetsize
To configure the maximum packet size of Service Advertising Protocol (SAP) updates sent out the interface, use the ipx sap-max-packetsize interface configuration command. To restore the default packet size, use the no form of this command.
ipx sap-max-packetsize bytes
no ipx sap-max-packetsize bytes
Syntax Description
bytes
Maximum packet size in bytes. The default is 480 bytes, which allows for 7 servers (64 bytes each), plus 32 bytes of IPX network and SAP header information.
Defaults
480 bytes
Command Modes
Interface configuration
Command History
Usage Guidelines
The maximum size is for the IPX packet including the IPX network and SAP header information. For example, to allow 10 servers per SAP packet, you would configure (32 + (10 x 64)), or 672 bytes for the maximum packet size.
You are responsible for guaranteeing that the maximum packet size does not exceed the allowed maximum size of packets for the interface.
Examples
The following example sets the maximum SAP update packet size to 672 bytes:
ipx sap-max-packetsize 672Related Commands
ipx sap-multiplier
To configure the interval at which a network's or server's Service Advertising Protocol (SAP) entry ages out, use the ipx sap-multiplier interface configuration command. To restore the default interval, use the no form of this command.
ipx sap-multiplier multiplier
no ipx sap-multiplier multiplier
Syntax Description
Defaults
Three times the SAP 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 SAP updates are sent once every 1 minute, the interval at which SAP entries age out is set to 10 minutes:
interface ethernet 0ipx sap-multiplier 10Related Commands
ipx sap-queue-maximum
To configure the maximum length of the queue of pending input Service Advertising Protocol (SAP) GNS requests and SAP query packets, use the ipx sap-queue-maximum global configuration command. To return to the default value, use the no form of this command.
ipx sap-queue-maximum number
no ipx sap-queue-maximum
Syntax Description
number
Maximum length of the queue of pending SAP requests. By default, there is no limit to the number of pending SAP requests that the Cisco IOS software stores in this queue.
Defaults
No maximum queue size
Command Modes
Global configuration
Command History
Usage Guidelines
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, the software can be inundated with hundreds of requests for servers. Most of these can be repeated requests from the same clients. The ipx sap-queue-maximum command allows you to configure the maximum length allowed for the pending SAP requests queue. Packets received when the queue is full are dropped.
Examples
The following example sets the length of the queue of pending SAP requests to 20:
ipx sap-queue-maximum 20ipx server-split-horizon-on-server-paths
To control whether Service Information split horizon checking should be based on Router Information Protocol (RIP) paths or Service Advertising Protocol (SAP) paths, use the ipx server-split-horizon-on-server-paths command in global configuration mode. To return to the normal mode of following route paths, use the no form of this command.
ipx server-split-horizon-on-server-paths
no ipx server-split-horizon-on-server-paths
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
By default, split horizon prevents information about periodic SAPs from being advertised by a router to the same interface in which the best route to that SAP is learned. However, in an instance where the SAP may be learned from interfaces other than, or in addition to, the interface on which the best route to that SAP is learned, using the ipx server-split-horizon-on-server-paths command may reduce the number of unnecessary periodic SAP updates. The reduction in the number of SAP updates occurs because each SAP will not be advertised on the interface or interfaces it was learned from. The reduction in the number of SAP updates will also prevent a potential SAP loop in the network.
Examples
The following example shows the application of split horizon blocks:
ipx server-split-horizon-on-server-pathsRelated Commands
ipx split-horizon eigrp
To configure split horizon, use the ipx split-horizon eigrp command in interface configuration mode. To disable split horizon, use the no form of this command.
ipx split-horizon eigrp autonomous-system-number
no ipx split-horizon eigrp autonomous-system-number
Syntax Description
autonomous-system-number
Enhanced Interior Gateway Routing Protocol (EIGRP) autonomous system number. It can be a number from 1 to 65,535.
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
When split horizon is enabled, Enhanced IGRP update and query packets are not sent for destinations that have next hops on this interface. This reduces the number of Enhanced IGRP packets on the network.
Split horizon blocks information about routes from being advertised by Cisco IOS software to any interface from which that information originated. Typically, this behavior optimizes communication among multiple routers, particularly when links are broken. However, with nonbroadcast networks, such as Frame Relay and Switched Multimegabit Data Service (SMDS), situations can arise for which this behavior is less than ideal. For these situations, you may wish to disable split horizon.
Examples
The following example disables split horizon on serial interface 0:
interface serial 0no ipx split-horizon eigrp 200ipx source-network-update
To repair corrupted network numbers, use the ipx source-network-update interface configuration command. To disable this feature, use the no form of this command.
ipx source-network-update
no ipx source-network-update
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
In some early implementations of IPX client software, it was possible for the client's network number to become corrupted. The ipx source-network-update command repairs this number by setting the source network field of any packet on the local network that has a hop count of zero.
You must disable fast switching with the no ipx route-cache command before using the ipx source-network-update command.
Caution
Caution
Examples
The following example repairs corrupted network numbers on serial interface 0:
interface serial 0no ipx route-cacheipx source-network-updateRelated Commands
ipx split-horizon eigrp
To configure split horizon, use the ipx split-horizon eigrp interface configuration command. To disable split horizon, use the no form of this command.
ipx split-horizon eigrp autonomous-system-number
no ipx split-horizon eigrp autonomous-system-number
Syntax Description
autonomous-system-number
Enhanced IGRP autonomous system number. It can be a number from 1 to 65535.
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
When split horizon is enabled, Enhanced IGRP update and query packets are not sent for destinations that have next hops on this interface. This reduces the number of Enhanced IGRP packets on the network.
Split horizon blocks information about routes from being advertised by the Cisco IOS software to any interface from which that information originated. Typically, this behavior 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 may wish to disable split horizon.
Examples
The following example disables split horizon on serial interface 0:
interface serial 0no ipx split-horizon eigrp 200ipx spx-idle-time
To set the amount of time to wait before starting the spoofing of SPX keepalive packets following inactive data transfer, use the ipx spx-idle-time interface configuration command. To disable the current delay time set by this command, use the no form of this command.
ipx spx-idle-time delay-in-seconds
no ipx spx-idle-time
Syntax Description
delay-in-seconds
The amount of time in seconds to wait before spoofing SPX keepalives after data transfer has stopped.
Defaults
60 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
This command sets the elapsed time in seconds after which spoofing of keepalive packets occurs, following the end of data transfer; that is, after the acknowledgment and sequence numbers of the data being transferred have stopped increasing. By default, SPX keepalive packets are sent from servers to clients every 15 to 20 seconds.
If you turn on SPX spoofing and you do not set an idle time, the default of 60 seconds is assumed. This means that the dialer idle time begins when SPX spoofing begins. For example, if the dialer idle time is 3 minutes, the elapse time before SPX spoofing begins is 4 minutes: 3 minutes of dialer idle time plus 1 minute of SPX spoofing idle time.
For this command to take effect, you must first use the ipx spx-spoof interface configuration command to enable SPX spoofing for the interface.
Examples
The following example enables spoofing on serial interface 0 and sets the idle timer to 300 seconds:
interface serial 0ipx spx-spoofno ipx route-cacheipx spx-idle-time 300Related Commands
ipx spx-spoof
To configure the Cisco IOS software to respond to a client or server's SPX keepalive packets on behalf of a remote system so that a dial-on-demand (DDR) link will go idle when data has stopped being transferred, use the ipx spx-spoof interface configuration command. To disable spoofing, use the no form of this command.
ipx spx-spoof [session-clear session-clear-minutes | table-clear table-clear-hours]
no ipx spx-spoof [session-clear | table-clear]
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
You can use the ipx spx-spoof command on any serial dialer or point-to-point interface. Fast switching and autonomous switching must be disabled on the interface; otherwise, SPX spoofing will not be permitted.
SPX keepalive packets are sent from servers to clients every 15 to 20 seconds after a client session has been idle for a certain period of time following the end of data transfer and after which only unsolicited acknowledgments are sent. The idle time may vary, depending on parameters set by the client and server.
Because of acknowledgment packets, a session would never go idle on a DDR link. On pay-per-packet or byte networks, these keepalive packets can incur for the customer large phone connection charges for idle time. You can prevent these calls from being made by configuring the software to respond to the server's keepalive packets on a remote client's behalf. This is sometimes referred to as "spoofing the server."
You can use the ipx spx-idle-time command to set the elapsed time in seconds after which spoofing of keepalive packets occurs, following the end of data transfer. If you turn on SPX spoofing and you do not set an idle time, the default of 60 seconds is assumed. This means that the dialer idle time begins when SPX spoofing begins. For example, if the dialer idle time is 3 minutes, the elapse time before the line goes "idle-spoofing" is 4 minutes: 3 minutes of dialer idle time plus 1 minute of SPX spoofing idle time.
Examples
The following example enables spoofing on serial interface 0:
interface serial 0ipx spx-spoofno ipx route-cacheRelated Commands
Configures the throughput.
Displays the table of SPX connections through interfaces for which SPX spoofing is enabled.
ipx throughput
To configure the throughput, use the ipx throughput interface configuration command. To revert to the current bandwidth setting for the interface, use the no form of this command.
ipx throughput bits-per-second
no ipx throughput bits-per-second
Syntax Description
Defaults
Current bandwidth setting for the interface
Command Modes
Interface configuration
Command History
Usage Guidelines
The value you specify with the ipx throughput command overrides the value measured by IPXWAN when it starts. This value is also supplied to NLSP for use in its metric calculations.
Examples
The following example changes the throughput to 1,000,000 bits per second:
ipx throughput 1000000Related Commands
ipx triggered-rip-delay
To set the interpacket delay for triggered RIP updates sent on a single interface, use the ipx triggered-rip-delay interface configuration command. To return to the default delay, use the no form of this command.
ipx triggered-rip-delay delay
no ipx triggered-rip-delay [delay]
Syntax Description
delay
Delay, in milliseconds, 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. A triggered routing update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.
The ipx triggered-rip-delay command sets the interpacket delay for triggered routing updates sent on a single interface. The delay value set by this command overrides the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered routing updates sent on the interface.
If the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command is high, then we strongly recommend a low delay value for triggered routing updates so that updates triggered by special events are sent in a more timely manner than periodic routing updates.
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.
When you do not set the interpacket delay for triggered routing updates, the system uses the delay specified by the ipx output-rip-delay or ipx default-output-rip-delay command for both periodic and triggered routing updates.
When you use the no form of the ipx triggered-rip-delay command, the system uses the global default delay set by the ipx default-triggered-rip-delay command for triggered RIP updates, if it is set. If it is not set, the system uses the delay set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered RIP updates, if set. Otherwise, the system uses the initial default delay as described in the "Defaults" section.
This command is also useful on limited bandwidth point-to-point links, or X.25 and Frame Relay multipoint interfaces.
Examples
The following example sets an interpacket delay of 55 ms for triggered routing updates sent on interface FDDI 0:
interface FDDI 0ipx triggered-rip-delay 55Related Commands
ipx triggered-sap-delay
To set the interpacket delay for triggered Service Advertising Protocol (SAP) updates sent on a single interface, use the ipx triggered-sap-delay interface configuration command. To return to the default delay, use the no form of this command.
ipx triggered-sap-delay delay
no ipx triggered-sap-delay [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. A triggered SAP update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.
The ipx triggered-sap-delay command sets the interpacket delay for triggered updates sent on a single interface. The delay value set by this command overrides the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered updates sent on the interface.
If the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command is high, then we strongly recommend a low delay value for triggered updates so that updates triggered by special events are sent in a more timely manner than periodic updates.
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 this command forces the router to pace its output to the slower-processing needs of these IPX servers.
The default delay on a NetWare 3.11 server is about 100 ms.
When you do not set the interpacket delay for triggered updates, the system uses the delay specified by the ipx output-sap-delay or ipx default-output-sap-delay command for both periodic and triggered SAP updates.
When you use the no form of the ipx triggered-sap-delay command, the system uses the global default delay set by the ipx default-triggered-sap-delay command for triggered SAP updates, if it is set. If it is not set, the system uses the delay set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered SAP updates, if set. Otherwise, the system uses the initial default delay as described in the "Defaults" section.
This command is also useful on limited bandwidth point-to-point links, or X.25 and Frame Relay multipoint interfaces.
Examples
The following example sets an interpacket delay of 55 ms for triggered SAP updates sent on interface FDDI 0:
interface FDDI 0ipx triggered-sap-delay 55Related Commands
ipx type-20-helpered
To forward IPX type 20 propagation packet broadcasts to specific network segments, use the ipx type-20-helpered global configuration command. To disable this function, use the no form of this command.
ipx type-20-helpered
no ipx type-20-helpered
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
The ipx type-20-helpered command disables the input and output of type 20 propagation packets as done by the ipx type-20-propagation interface configuration command.
The ipx type-20-propagation command broadcasts type 20 packets to all nodes on the network and imposes a hop-count limit of eight routers for broadcasting these packets. These functions are in compliance with the Novell IPX router specification. In contrast, the ipx type-20-helpered command broadcasts type 20 packets to only those nodes indicated by the ipx helper-address interface configuration command and extends the hop-count limit to 16 routers.
Use of the ipx type-20-helpered command does not comply with the Novell IPX router specification; however, you may need to use this command if you have a mixed internetwork that contains routers running Software Release 9.1 and routers running later versions of Cisco IOS software.
Examples
The following example forwards IPX type 20 propagation packet broadcasts to specific network segments:
interface ethernet 0ipx network aaipx type-20-helperedipx helper-address bb.ffff.ffff.ffffRelated Commands
Forwards broadcast packets to a specified server.
Forwards IPX type 20 propagation packet broadcasts to other network segments.
ipx type-20-input-checks
To restrict the acceptance of IPX type 20 propagation packet broadcasts, use the ipx type-20-input-checks global configuration command. To remove these restrictions, use the no form of this command.
ipx type-20-input-checks
no ipx type-20-input-checks
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
By default, the Cisco IOS software is configured to block type 20 propagation packets. When type 20 packet handling is enabled on multiple interfaces, you can use the ipx type-20-input-checks command to impose additional restrictions on the acceptance of type 20 packets. Specifically, the software will accept type 20 propagation packets only on the single network that is the primary route back to the source network. Similar packets received via other networks will be dropped. This behavior can be advantageous in redundant topologies, because it reduces unnecessary duplication of type 20 packets.
Examples
The following example imposes additional restrictions on incoming type 20 broadcasts:
ipx type-20-input-checksRelated Commands
Restricts the forwarding of IPX type 20 propagation packet broadcasts.
Forwards IPX type 20 propagation packet broadcasts to other network segments.
ipx type-20-output-checks
To restrict the forwarding of IPX type 20 propagation packet broadcasts, use the ipx type-20-output-checks global configuration command. To remove these restrictions, use the no form of this command.
ipx type-20-output-checks
no ipx type-20-output-checks
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
By default, the Cisco IOS software is configured to block type 20 propagation packets. When type 20 packet handling is enabled on multiple interfaces, you can use the ipx type-20-output-checks command to impose additional restrictions on outgoing type 20 packets. Specifically, the software will forward these packets only to networks that are not routes back to the source network. (The software uses the current routing table to determine routes.) This behavior can be advantageous in redundant topologies, because it reduces unnecessary duplication of type 20 packets.
Examples
The following example imposes restrictions on outgoing type 20 broadcasts:
ipx type-20-output-checksRelated Commands
Restricts the acceptance of IPX type 20 propagation packet broadcasts.
Forwards IPX type 20 propagation packet broadcasts to other network segments.
ipx type-20-propagation
To forward IPX type 20 propagation packet broadcasts to other network segments, use the ipx type-20-propagation interface configuration command. To disable both the reception and forwarding of type 20 broadcasts on an interface, use the no form of this command.
ipx type-20-propagation
no ipx type-20-propagation
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Routers normally block all broadcast requests. To allow input and output of type 20 propagation packets on an interface, use the ipx type-20-propagation command. Note that type 20 packets are subject to loop detection and control as specified in the IPX router specification.
Additional input and output checks may be imposed by the ipx type-20-input-checks and
ipx type-20-output-checks commands.IPX type 20 propagation packet broadcasts are subject to any filtering defined by the ipx helper-list command.
Examples
The following example enables both the reception and forwarding of type 20 broadcasts on Ethernet interface 0:
interface ethernet 0ipx type-20-propagationThe following example enables the reception and forwarding of type 20 broadcasts between networks 123 and 456, but does not enable reception and forwarding of these broadcasts to and from network 789:
interface ethernet 0ipx network 123ipx type-20-propagation!interface ethernet 1ipx network 456ipx type-20-propagation!interface ethernet 2ipx network 789Related Commands
ipx update interval
To adjust the RIP or SAP update interval, use the ipx update interval interface configuration command. To restore the default values, use the no form of this command.
ipx update interval {rip | sap} {value | changes-only}
no ipx update interval {rip | sap}
Syntax Description
Defaults
The default interval is 60 seconds for both IPX routing updates and SAP updates.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command replaces two commands found in previous releases of the Cisco IOS software: ipx sap-interval and ipx update-time.
Routers exchange information about routes by sending broadcast messages when they are started up and shut down, and periodically while they are running. The ipx update interval command enables you to modify the periodic update interval. By default, this interval is 60 seconds (this default is defined by Novell).
You should set RIP timers only in a configuration in which all routers are Cisco routers or in which all other 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 the internal IPX timers as follows:
•
•
Setting the interval at which SAP updates are sent is most useful on limited-bandwidth links, such as slower-speed serial interfaces.
You should ensure that all IPX servers and routers on a given network have the same SAP interval. Otherwise, they may 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. This means that 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:
•
•
•
Examples
The following example configures the update timers for RIP updates on two interfaces in a router:
interface serial 0ipx update interval rip 40interface ethernet 0ipx update interval rip 20The following example configures SAP updates to be sent (and expected) on serial interface 0 every 300 seconds (5 minutes) to reduce periodic update overhead on a slow-speed link:
interface serial 0ipx update interval sap 300Related Commands
ipx update sap-after-rip
To configure the router to send a SAP update immediately following a RIP broadcast, use the
ipx update sap-after-rip interface configuration command. To restore the default value, use the no form of this command.ipx update sap-after-rip
no ipx update sap-after-rip
Syntax Description
This command has no arguments or keywords.
Defaults
RIP and SAP updates are sent every 60 seconds.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx update sap-after-rip command causes the router to issue a SAP update immediately following a RIP broadcast. This ensures that the SAP update follows the RIP broadcast, and that the SAP update is sent using the RIP update interval. It also ensures that the receiving router has learned the route to the service interface via RIP prior to getting the SAP broadcast.
Examples
The following example configures the router to issue a SAP broadcast immediately following a RIP broadcast on serial interface 0.
interface serial 0ipx update sap-after-ripRelated Commands
ipx watchdog-spoof
To have the Cisco IOS software respond to a server's watchdog packets on behalf of a remote client, use the ipx watchdog-spoof interface configuration command. To disable spoofing, use the no form of this command.
ipx watchdog-spoof
no ipx watchdog-spoof
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
You can use the ipx watchdog-spoof command only on a serial interface on which dial-on-demand routing (DDR) has been enabled. Also, fast switching and autonomous switching must be disabled on the interface.
IPX watchdog packets are keepalive packets that are sent from servers to clients after a client session has been idle for approximately 5 minutes. On a DDR link, this would mean that a call would be made every 5 minutes, regardless of whether there were data packets to send. You can prevent these calls from being made by configuring the software to respond to the server's watchdog packets on a remote client's behalf. This is sometimes referred to as "spoofing the server."
Examples
The following example enables spoofing on serial interface 0:
interface serial 0ipx watchdog-spoofno ipx route-cacheRelated Commands
log-adjacency-changes (IPX)
To generate a log message when an NLSP adjacency changes state (up or down), use the log-adjacency-changes IPX-router configuration command. Use the no form of this command to disable this function.
log-adjacency-changes
no log-adjacency-changes
Syntax Description
This command has no arguments or keywords.
Defaults
Adjacency changes are not logged.
Command Modes
IPX-router configuration
Command History
Usage Guidelines
This command allows the monitoring of NLSP adjacency state changes. Adjacency state monitoring can be very useful when monitoring large networks. Messages are logged using the system error message facility. Messages are of the 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
Messages regarding the use of NLSP multicast and broadcast addressing are also logged. For example, if broadcast addressing is in use on Ethernet interface 1.2, and the last neighbor requiring broadcasts goes down, the following messages will be logged:
%CLNS-5-ADJCHANGE: NLSP: Adjacency to 0000.0C34.D838 (Ethernet1.2) Down, hold time expired
%CLNS-5-MULTICAST: NLSP: Multicast address in use on Ethernet1.2
If multicast addressing is in use and a new neighbor that supports only broadcast addressing comes up, the following messages will be logged:
%CLNS-5-ADJCHANGE: NLSP: Adjacency to 0000.0C34.D838 (Ethernet1.2) Up, new adjacency
%CLNS-5-MULTICAST: NLSP Broadcast address is in use on Ethernet1.2
Examples
The following example instructs the router to log adjacency changes for the NLSP process area1:
ipx router nlsp area1log-adjacency-changesRelated Commands
log-neighbor-changes (EIGRP)
To enable the logging of changes in Enhanced IGRP neighbor adjacencies, use the log-neighbor-changes IPX-router configuration command. Use the no form of the command to disable this function.
log-neighbor-changes
no log-neighbor-changes
Syntax Description
This command has no arguments or keywords.
Defaults
No adjacency changes are logged.
Command Modes
IPX-router configuration
Command History
Usage Guidelines
Enable the logging of neighbor adjacency changes in order to monitor the stability of the routing system and to help detect problems. Log messages are of the following form:
%DUAL-5-NBRCHANGE: IPX EIGRP as-number: Neighbor address (interface) is state: reason
as-number
Autonomous system number
address
Neighbor address
state
Up or down
reason
Reason for change
where the arguments have the following meanings:
Examples
The following configuration will log neighbor changes for Enhanced IGRP process 209:
ipx router eigrp 209log-neighbor-changesRelated Commands
lsp-gen-interval (IPX)
To set the minimum interval at which link-state packets (LSPs) are generated, use the lsp-gen-interval router configuration command. To restore the default interval, use the no form of this command.
lsp-gen-interval seconds
no lsp-gen-interval seconds
Syntax Description
seconds
Minimum interval, in seconds. It can be a number in the range 0 to 120. The default is 5 seconds.
Defaults
5 seconds
Command Modes
Router configuration
Command History
Usage Guidelines
The lsp-gen-interval command controls the rate at which LSPs are generated on a per-LSP basis. For instance, if a link is changing state at a high rate, the default value of the LSP generation interval limits the signaling of this change to once every 5 seconds. Because the generation of an LSP may cause all routers in the area to perform the SPF calculation, controlling this interval may have area-wide impact. Raising this interval can reduce the load on the network imposed by a rapidly changing link.
Examples
The following example sets the minimum interval at which LSPs are generated to 10 seconds:
lsp-gen-interval 10Related Commands
Specifies the routing protocol to use.
Controls how often the Cisco IOS software performs the SPF calculation.
lsp-mtu (IPX)
To set the maximum size of a link-state packet (LSP) generated by the Cisco IOS software, use the lsp-mtu router configuration command. To restore the default MTU size, use the no form of this command.
lsp-mtu bytes
no lsp-mtu bytes
Syntax Description
Defaults
512 bytes
Command Modes
Router configuration
Command History
Usage Guidelines
You can increase the LSP MTU if there is a very large amount of information generated by a single router, because each device is limited to approximately 250 LSPs. In practice, this should never be necessary.
The LSP MTU must never be larger than the smallest MTU of any link in the area. This is because LSPs are flooded throughout the area.
The lsp-mtu command limits the size of LSPs generated by this router only; the Cisco IOS software can receive LSPs of any size up to the maximum.
Examples
The following example sets the maximum LSP size to 1500 bytes:
lsp-mtu 1500Related Commands
lsp-refresh-interval (IPX)
To set the link-state packet (LSP) refresh interval, use the lsp-refresh-interval router configuration command. To restore the default refresh interval, use the no form of this command.
lsp-refresh-interval seconds
no lsp-refresh-interval seconds
Syntax Description
seconds
Refresh interval, in seconds. It can be a value in the range 1 to 50000 seconds. The default is 7200 seconds (2 hours).
Defaults
7,200 seconds (2 hours)
Command Modes
Router configuration
Command History
Usage Guidelines
The refresh interval determines the rate at which the Cisco IOS software periodically transmits the route topology information that it originates. This is done in order to keep the information from becoming too old. By default, the refresh interval is 2 hours.
LSPs must be periodically refreshed before their lifetimes expire. The refresh interval must be less than the LSP lifetime specified with the max-lsp-lifetime (IPX) router configuration command. Reducing the refresh interval reduces the amount of time that undetected link state database corruption can persist at the cost of increased link utilization. (This is an extremely unlikely event, however, because there are other safeguards against corruption.) Increasing the interval reduces the link utilization caused by the flooding of refreshed packets (although this utilization is very small).
Examples
The following example changes the LSP refresh interval to 10,800 seconds (3 hours):
lsp-refresh-interval 10800Related Commands
Specifies the routing protocol to use.
Sets the maximum time that LSPs persist without being refreshed.
max-lsp-lifetime (IPX)
To set the maximum time that link-state packets (LSPs) persist without being refreshed, use the max-lsp-lifetime router configuration command. To restore the default time, use the no form of this command.
max-lsp-lifetime [hours] value
no max-lsp-lifetime
Syntax Description
Defaults
7500 seconds (2 hours, 5 minutes)
Command Modes
Router configuration
Command History
Usage Guidelines
The hours keyword enables the router to interpret the maximum lifetime field in hours, allowing the router to keep LSPs for a much longer time. Keeping LSPs longer reduces overhead on slower-speed serial links and keeps ISDN links from becoming active unnecessarily.
You might need to adjust the maximum LSP lifetime if you change the LSP refresh interval with the lsp-refresh-interval (IPX) router configuration command. The maximum LSP lifetime must be greater than the LSP refresh interval.
Examples
The following example sets the maximum time that the LSP persists to 11,000 seconds (more than 3 hours):
max-lsp-lifetime 11000The following example sets the maximum time that the LSP persists to 15 hours:
max-lsp-lifetime hours 15Related Commands
multicast
To configure the router to use multicast addressing, use the multicast router configuration command. To configure the router to use broadcast addressing, use the no form of this command.
multicast
no multicast
Syntax Description
This command has no arguments or keywords.
Defaults
Multicast addressing is enabled.
Command Modes
Router configuration
Command History
Usage Guidelines
This command allows the router 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 on any interface where multicast addressing is not supported by the hardware or driver.
Examples
The following example disables multicast addressing on the router:
ipx router nlspno multicastnetbios access-list (IPX)
To define an IPX NetBIOS FindName access list filter, use the netbios access-list global configuration command. To remove a filter, use the no form of the command.
netbios access-list host name {deny | permit} string
no netbios access-list host name {deny | permit} string
netbios access-list bytes name {deny | permit} offset byte-pattern
no netbios access-list bytes name {deny | permit} offset byte-pattern
Syntax Description
Defaults
No filters are predefined.
Command Modes
Global configuration
Command History
Usage Guidelines
Keep the following points in mind when configuring IPX NetBIOS access control:
•
•
•
•
•
These filters apply only to IPX NetBIOS FindName packets. They have no effect on LLC2 NetBIOS packets.
To delete an IPX NetBIOS access list, specify the minimum number of keywords and arguments needed to delete the proper list. For example, to delete the entire list, use the following command:
no netbios access-list {host | bytes} name
To delete a single entry from the list, use the following command:
no netbios access-list host name {permit | deny} string
Examples
The following example defines the IPX NetBIOS access list engineering:
netbios access-list host engineering permit eng-ws1 eng-ws2 eng-ws3The following example removes a single entry from the engineering access list:
netbios access-list host engineering deny eng-ws3The following example removes the entire engineering NetBIOS access list:
no netbios access-list host engineeringRelated Commands
network (EIGRP)
To enable Enhanced IGRP, use the network router configuration command. To disable Enhanced IGRP, use the no form of this command.
network {network-number | all}
no network {network-number | all}
Syntax Description
network-number
IPX network number.
all
Enables the routing protocol for all IPX networks configured on the router.
Defaults
Disabled
Command Modes
Router configuration
Command History
Usage Guidelines
Use the network command to enable the routing protocol specified in the ipx router command on each network.
Examples
The following commands disable RIP on network 10 and enable Enhanced IGRP on networks 10 and 20:
ipx router ripno network 10ipx router eigrp 12network 10network 20Related Commands
permit (IPX extended)
To set conditions for a named IPX extended access list, use the permit access-list configuration command. To remove a permit condition from an access list, use the no form of this command.
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-node-mask]] [destination-socket] [log]
no 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-nodemask]] [destination-socket] [log]
Syntax Description
Defaults
There is no specific condition under which a packet passes the named access list.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to specify conditions under which a packet passes the named access list.
For additional information on IPX protocol names and numbers, and IPX socket names and numbers, see the access-list (IPX extended) command.
Examples
The following example creates an extended access list named sal that denies all SPX packets and permits all others:
ipx access-list extended saldeny spx any all any all logpermit anyRelated Commands
permit (IPX standard)
To set conditions for a named IPX access list, use the permit access-list configuration command. To remove a permit condition from an access list, use the no form of this command.
permit source-network[.source-node [source-node-mask]] [destination-network[.destination-node[destination-node-mask]]]
no permit source-network[.source-node [source-node-mask]] [destination-network[.destination-node[destination-node-mask]]]
Syntax Description
Defaults
No access lists are defined.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to specify conditions under which a packet passes the named access list.
For additional information on creating IPX access lists, see the access-list (IPX standard) command.
Examples
The following example creates a standard access list named fred. It permits communication with only IPX network number 5678.
ipx access-list standard fredpermit 5678 anydeny anyRelated Commands
permit (NLSP route aggregation summarization)
To allow explicit route redistribution in a named NLSP route aggregation access list, use the permit access-list configuration command. To remove a permit condition, use the no form of this command.
permit network network-mask [ticks ticks] [area-count area-count]
no permit network network-mask [ticks ticks] [area-count area-count]
Syntax Description
Defaults
No access lists are defined.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to specify conditions under which networks that are permitted by the access list entry can be redistributed as explicit networks, without summarization.
For additional information on creating access lists that deny or permit area addresses that summarize routes, see the access-list (NLSP route aggregation summarization) command.
Examples
The following example allows networks 12345600 and 12345601 to be redistributed explicitly. Other routes in the range 12345600 to 123456FF are summarized into a single aggregated route. All other routes will be redistributed as explicit routes.
ipx access-list summary financepermit 12345600permit 12345601deny 12345600 ffffff00permit -1Related Commands
permit (SAP filtering)
To set conditions for a named IPX SAP filtering access list, use the permit access-list configuration command. To remove a permit condition from an access list, use the no form of this command.
permit network[.node] [network-mask.node-mask] [service-type [server-name]]
no permit network[.node] [network-mask.node-mask] [service-type [server-name]]
Syntax Description
Defaults
No access lists are defined.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to specify conditions under which a packet passes the named access list.
For additional information on IPX SAP service types, see the access-list (SAP filtering) command.
Examples
The following example creates a SAP access list named MyServer that allows only MyServer to be sent in SAP advertisements:
ipx access-list sap MyServerpermit 1234 4 MyServerRelated Commands
prc-interval (IPX)
To control the holddown period between partial route calculations, use the prc-interval router configuration command. To restore the default interval, use the no form of this command.
prc-interval seconds
no prc-interval seconds
Syntax Description
seconds
Minimum amount of time between partial route calculations, in seconds. It can be a number in the range 1 to 120. The default is 5 seconds.
Defaults
5 seconds
Command Modes
Router configuration
Command History
Usage Guidelines
The prc-interval command controls how often the Cisco IOS software can performs a partial route (PRC) calculation. The PRC calculation is processor-intensive. Therefore, it may be useful to limit how often this is done, especially on slower router models. Increasing the PRC interval reduces the processor load of the router, but potentially slows down the rate of convergence.
This command is analogous to the spf-interval command, which controls the holddown period between shortest path first calculations.
Examples
The following example sets the PRC calculation interval to 20 seconds:
prc-interval 20Related Commands
Specifies the routing protocol to use.
Controls how often the Cisco IOS software performs the SPF calculation.
redistribute (IPX)
To redistribute from one routing domain into another, and vice versa, use one of the following redistribute router configuration commands. To disable this feature, use the no form of the commands.
For Enhanced IGRP or RIP environments, use the following command to redistribute from one routing domain into another, and vice versa:
redistribute {connected | eigrp autonomous-system-number | floating-static | nlsp [tag] | rip | static}
no redistribute {connected | eigrp autonomous-system-number | floating-static | nlsp [tag] | rip | static}
For NLSP environments, use the following command to redistribute from one routing domain into another, and vice versa:
redistribute {eigrp autonomous-system-number | nlsp [tag] | rip | static}
[access-list {access-list-number | name}]no redistribute {eigrp autonomous-system-number | nlsp [tag] | rip | static}
[access-list {access-list-number | name}]Syntax Description
Defaults
Redistribution is enabled between all routing domains except between separate Enhanced IGRP processes.
Redistribution of floating static routes is disabled.
Redistribution between NLSP and Enhanced IGRP is disabled.
Command Modes
Router configuration
Command History
Usage Guidelines
Redistribution provides for routing information generated by one protocol to be advertised in another.
The only connected routes affected by this redistribute command are the routes not specified by the network command.
If you have enabled floating static routes by specifying the floating keyword in the ipx route global configuration command and you redistribute floating static routes into a dynamic IPX routing protocol, any nonhierarchical topology causes the floating static destination to be redistributed immediately via a dynamic protocol back to the originating router, causing a routing loop. This occurs because dynamic protocol information overrides floating static routes. For this reason, automatic redistribution of floating static routes is off by default. If you redistribute floating static routes, you should specify filters to eliminate routing loops.
For NLSP environments, you can use the NLSP redistribute command to configure IPX route aggregation with customized route summarization. Configure IPX route aggregation with customized route summarization in the following:
•
•
Note
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.
Examples
The following example does not redistributes RIP routing information:
ipx router eigrp 222no redistribute ripThe following example redistributes Enhanced IGRP routes from autonomous system 100 into Enhanced IGRP autonomous system 300:
ipx router eigrp 300redistribute eigrp 100The following example redistributes Enhanced IGRP routes from autonomous system 300 into the NLSP process area3:
ipx router nlsp area3redistribute eigrp 300The following example enables route summarization and redistributes routes learned from one NLSP instance to another. Any routes learned via NLSP a1 that are subsumed by route summary aaaa0000 ffff0000 are not redistributed into NLSP a2. Instead, an aggregated route is generated. Likewise, any routes learned via NLSP a2 that are subsumed by route summary bbbb0000 ffff0000 are not redistributed into NLSP a1—an aggregated route is generated.
ipx routing ipx internal-network 2000!interface ethernet 1 ipx network 1001 ipx nlsp a1 enable!interface ethernet 2 ipx network 2001 ipx nlsp a2 enable!access-list 1200 deny aaaa0000 ffff0000 access-list 1200 permit -1access-list 1201 deny bbbb0000 ffff0000 access-list 1201 permit -1!ipx router nlsp a1 area-address 1000 fffff000 route-aggregationredistribute nlsp a2 access-list 1201!ipx router nlsp a2 area-address 2000 fffff000route-aggregation redistribute nlsp a1 access-list 1200Related Commands
route-aggregation (NLSP)
To enable the generation of aggregated routes in an NLSP area, use the route-aggregation router configuration command. To disable generation, use the no form of this command.
route-aggregation
no route-aggregation
Syntax Description
This command has no arguments or keywords.
Defaults
Route summarization is disabled by default.
Command Modes
Router configuration
Command History
Usage Guidelines
When route summarization is disabled, all routes redistributed into an NLSP area will be explicit routes.
When route summarization is enabled, the router uses the access list associated with the redistribute command (if one exists) for the routing process associated with each route as a template for route summarization. Explicit routes that match a range denied by the access list trigger generation of an aggregated route instead. Routes permitted by the access list are redistributed as explicit routes.
If no access list exists, the router instead uses the area address (if one exists) of the routing process associated with each route as a template for route summarization. Explicit routes that match the area address trigger generation of an aggregated route instead.
Note
Examples
The following example enables route summarization between two NLSP areas. Route summarization is based on the area addresses configured for each area.
ipx routingipx internal-network 123!interface ethernet 1ipx nlsp area1 enable!interface ethernet 2ipx nlsp area2 enable!ipx router nlsp area1area-address 1000 fffff000route-aggregation!ipx router nlsp area2area-address 2000 fffff000route-aggregationRelated Commands
Specifies the routing protocol to use.
Redistributes from one routing domain into another.
show ipx access-list
To display the contents of all current IPX access lists, use the show ipx access-list EXEC command.
show ipx access-list [access-list-number | name]
Syntax Description
Defaults
Displays all standard, extended, SAP, and NLSP route aggregation summary IPX access lists.
Command Modes
EXEC
Command History
Usage Guidelines
The show ipx access-list command provides output identical to the show access-lists command, except that it is IPX specific and allows you to specify a particular access list.
Examples
The following is sample output from the show ipx access-list command when all access lists are requested:
Router# show ipx access-listIPX extended access list 900deny any 1IPX sap access list Londondeny FFFFFFFF 107deny FFFFFFFF 301Cpermit FFFFFFFF 0The following is sample output from the show ipx access-list command when the name of a specific access list is requested:
Router# show ipx access-list LondonIPX sap access list Londondeny FFFFFFFF 107deny FFFFFFFF 301Cpermit FFFFFFFF 0show ipx accounting
To display the active or checkpoint accounting database, use the show ipx accounting EXEC command.
show ipx accounting [checkpoint]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx accounting command:
Router# show ipx accountingSource Destination Packets Bytes0000C003.0000.0c05.6030 0000C003.0260.8c9b.4e33 72 28800000C001.0260.8c8d.da75 0000C003.0260.8c9b.4e33 14 6240000C003.0260.8c9b.4e33 0000C001.0260.8c8d.da75 62 31100000C001.0260.8c8d.e7c6 0000C003.0260.8c9b.4e33 20 14700000C003.0260.8c9b.4e33 0000C001.0260.8c8d.e7c6 20 1470Accounting data age is 6Table 296 describes the fields shown in the display.
Related Commands
show ipx cache
To display the contents of the IPX fast-switching cache, use the show ipx cache EXEC command.
show ipx cache
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx cache command:
Router# show ipx cacheNovell routing cache version is 9Destination Interface MAC Header*1006A Ethernet 0 00000C0062E600000C003EB0064*14BB Ethernet 1 00000C003E2A00000C003EB0064Table 297 describes the fields shown in the display.
Related Commands
show ipx eigrp interfaces
To display information about interfaces configured for Enhanced IGRP, use the show ipx eigrp interfaces EXEC command.
show ipx eigrp interfaces [type number] [as-number]
Syntax Description
type
(Optional) Interface type.
number
(Optional) Interface number.
as-number
(Optional) Autonomous system number.
Command Modes
EXEC
Command History
Usage Guidelines
Use the show ipx eigrp interfaces command to determine on which interfaces Enhanced IGRP is active and to find out information about Enhanced IGRP relating to those interfaces.
If an interface is specified, only that interface is displayed. Otherwise, all interfaces on which Enhanced IGRP is running are displayed.
If an autonomous system is specified, only the routing process for the specified autonomous system is displayed. Otherwise, all Enhanced IGRP processes are displayed.
Examples
The following is sample output from the show ipx eigrp interfaces command:
Router> show ipx eigrp interfacesIPX EIGRP interfaces for process 109Xmit Queue Mean Pacing Time Multicast PendingInterface Peers Un/Reliable SRTT Un/Reliable Flow Timer RoutesDi0 0 0/0 0 11/434 0 0Et0 1 0/0 337 0/10 0 0SE0:1.16 1 0/0 10 1/63 103 0Tu0 1 0/0 330 0/16 0 0Table 298 describes the fields shown in the display.
Related Commands
show ipx eigrp neighbors
To display the neighbors discovered by Enhanced IGRP, use the show ipx eigrp neighbors EXEC command.
show ipx eigrp neighbors [servers] [autonomous-system-number | interface] [regexp name]
Syntax Description
Command Modes
EXEC
Command History
10.0
This command was introduced.
12.0
The following keyword and argument were added:
•
Examples
The following is sample output from the show ipx eigrp neighbors command:
Router# show ipx eigrp neighborsIPX EIGRP Neighbors for process 1H Address Interface Hold Uptime SRTT RTO Q Seq(sec) (ms) Cnt Num0 200.0000.0c34.d83b Et0/2 11 00:00:18 2 200 0 102 total IPX servers for this peerType Name Address Port Hops4 server 2037.0000.0000.0001:0001 24 server2 2037.0000.0000.0001:0001 21 200.0000.0c34.d83c Et0/2 11 00:00:18 2 200 0 101 total IPX servers for this peerType Name Address Port Hops4 server 2037.0000.0000.0001:0001 2Table 299 describes the fields shown in the display.
Table 299 show ipx eigrp neighbors Field Descriptions
process 200
Autonomous system number specified in the ipx router configuration command.
H
Handle. An arbitrary and unique number inside this router that identifies the neighbor.
Address
IPX address of the Enhanced IGRP peer.
Interface
Interface on which the router is receiving hello packets from the peer.
Hold
Length of time, in seconds, that the Cisco IOS software will wait to hear from the peer before declaring it down. If the peer is using the default hold time, this number will be less than 15. If the peer configures a nondefault hold time, it will be reflected here.
Uptime
Elapsed time (in hours, minutes, and seconds) since the local router first heard from this neighbor.
Q Cnt
Number of IPX Enhanced IGRP packets (Update, Query, and Reply) that the Cisco IOS software is waiting to send.
Seq Num
Sequence number of the last Update, Query, or Reply packet that was received from this neighbor.
SRTT
Smooth round-trip time. This is the number of milliseconds it takes for an IPX Enhanced IGRP packet to be sent to this neighbor and for the local router to receive an acknowledgment of that packet.
RTO
Retransmission timeout, in milliseconds. This is the amount of time the Cisco IOS software waits before retransmitting a packet from the retransmission queue to a neighbor.
RTO
Retransmission timeout, in milliseconds. This is the amount of time the Cisco IOS software waits before retransmitting a packet from the retransmission queue to a neighbor.
Q Cnt
Number of IPX Enhanced IGRP packets (Update, Query, and Reply) that the Cisco IOS software is waiting to send.
Seq Num
Sequence number of the last Update, Query, or Reply packet that was received from this neighbor.
Type
Contains codes from the Codes field to indicates how service was learned.
Name
Name of server.
Address
Network address of server.
Port
Source socket number.
Related Commands
ipx sap-incremental
Sends SAP updates only when a change occurs in the SAP table.
show ipx eigrp topology
To display the Enhanced IGRP topology table, use the show ipx eigrp topology EXEC command.
show ipx eigrp topology [network-number]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx eigrp topology command:
Router# show ipx eigrp topologyIPX EIGRP Topology Table for process 109Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,r - Reply statusP 42, 1 successors, FD is 0via 160.0000.0c00.8ea9 (345088/319488), Ethernet0P 160, 1 successor via Connected, Ethernetvia 160.0000.0c00.8ea9 (307200/281600), Ethernet0P 165, 1 successors, FD is 307200via Redistributed (287744/0)via 160.0000.0c00.8ea9 (313344/287744), Ethernet0P 164, 1 successors, flags: U, FD is 200via 160.0000.0c00.8ea9 (307200/281600), Ethernet1via 160.0000.0c01.2b71 (332800/307200), Ethernet1P A112, 1 successors, FD is 0via Connected, Ethernet2via 160.0000.0c00.8ea9 (332800/307200), Ethernet0P AAABBB, 1 successors, FD is 10003via Redistributed (287744/0),via 160.0000.0c00.8ea9 (313344/287744), Ethernet0A A112, 0 successors, 1 replies, state: 0, FD is 0via 160.0000.0c01.2b71 (307200/281600), Ethernet1via 160.0000.0c00.8ea9 (332800/307200), r, Ethernet1Table 300 describes the fields shown in the output.
The following is sample output from the show ipx eigrp topology command when you specify an IPX network number:
Router# show ipx eigrp topology 160IPX-EIGRP topology entry for 160State is Passive, Query origin flag is 1, 1 Successor(s)Routing Descriptor Blocks:Next hop is Connected (Ethernet0), from 0.0000.0000.0000Composite metric is (0/0), Send flag is 0x0, Route is InternalVector metric:Minimum bandwidth is 10000 KbitTotal delay is 1000000 nanosecondsReliability is 255/255Load is 1/255Minimum MTU is 1500Hop count is 0Next hop is 164.0000.0c00.8ea9 (Ethernet1), from 164.0000.0c00.8ea9Composite metric is (307200/281600), Send flag is 0x0, Route is ExternalThis is an ignored routeVector metric:Minimum bandwidth is 10000 KbitTotal delay is 2000000 nanosecondsReliability is 255/255Load is 1/255Minimum MTU is 1500Hop count is 1External data:Originating router is 0000.0c00.8ea9External protocol is RIP, metric is 1, delay 2Administrator tag is 0 (0x00000000)Flag is 0x00000000Table 301 describes the fields shown in the display.
Table 301 show ipx eigrp topology Field Descriptions—Specific Network
160
IPX network number of the destination.
State is ...
State of this entry. It can be either Passive or Active. Passive means that no Enhanced IGRP computations are being performed for this destination, and Active means that they are being performed.
Query origin flag
Exact Enhanced IGRP state that this destination is in. It can be the number 0, 1, 2, or 3. This information appears only when the destination is Active.
Successor(s)
Number of successors. This number corresponds to the number of next hops in the IPX routing table.
Next hop is ...
Indicates how this destination was learned. It can be one of the following:
•
•
•
Ethernet0
Interface from which this information was learned.
from
Peer from whom the information was learned. For connected and redistributed routers, this is 0.0000.0000.0000. For information learned via Enhanced IGRP, this is the peer's address. Currently, for information learned via Enhanced IGRP, the peer's IPX address always matches the address in the "Next hop is" field.
Composite metric is
Enhanced IGRP composite metric. The first number is this device's metric to the destination, and the second is the peer's metric to the destination.
Send flag
Numeric representation of the "flags" field described in Table 299. It is 0 when nothing is being sent, 1 when an Update is being sent, 3 when a Query is being sent, and 4 when a Reply is being sent. Currently, 2 is not used.
Route is ...
Type of router. It can be either internal or external. Internal routes are those that originated in an Enhanced IGRP autonomous system, and external are routes that did not. Routes learned via RIP are always external.
This is an ignored route
Indicates that this path is being ignored because of filtering.
Vector metric:
This section describes the components of the Enhanced IGRP metric.
Minimum bandwidth
Minimum bandwidth of the network used to reach the next hop.
Total delay
Delay time to reach the next hop.
Reliability
Reliability value used to reach the next hop.
Load
Load value used to reach the next hop.
Minimum MTU
Minimum MTU size of the network used to reach the next hop.
Hop count
Number of hops to the next hop.
External data:
This section describes the original protocol from which this route was redistributed. It appears only for external routes.
Originating router
Network address of the router that first distributed this route into Enhanced IGRP.
External protocol..metric..delay
External protocol from which this route was learned. The metric will match the external hop count displayed by the show ipx route command for this destination. The delay is the external delay.
Administrator tag
Not currently used.
Flag
Not currently used.
Related Commands
show ipx interface
To display the status of the IPX interfaces configured in the Cisco IOS software and the parameters configured on each interface, use the show ipx interface EXEC command.
show ipx interface [type number]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx interface command:
Router# show ipx interface ethernet 1Ethernet1 is up, line protocol is upIPX address is C03.0000.0c05.6030, NOVELL-ETHER [up] line-up, RIPPQ: 0, SAPPQ : 0Delay of this Novell network, in ticks is 1IPXWAN processing not enabled on this interface.IPX SAP update interval is 1 minute(s)IPX type 20 propagation packet forwarding is disabledOutgoing access list is not setIPX Helper access list is not setSAP Input filter list is not setSAP Output filter list is not setSAP Router filter list is not setSAP GNS output filter list is not setInput filter list is not setOutput filter list is not setRouter filter list is not setNetbios Input host access list is not setNetbios Input bytes access list is not setNetbios Output host access list is not setNetbios Output bytes access list is not setUpdate time is 60 secondsIPX accounting is enabledIPX fast switching is configured (enabled)IPX SSE switching is disabledThe following is sample output from the show ipx interface command when NLSP is enabled:
Router# show ipx interface ethernet 1Ethernet0 is up, line protocol is upIPX address is E001.0000.0c02.8cf9, SAP [up] line-up, RIPPQ: 0, SAPPQ : 0Delay of this IPX network, in ticks is 1 throughput 0 link delay 0IPXWAN processing not enabled on this interface.IPX SAP update interval is 1 minute(s)IPX type 20 propagation packet forwarding is disabledOutgoing access list is not setIPX Helper access list is not setSAP Input filter list is not setSAP Output filter list is not setSAP Router filter list is not setSAP GNS output filter list is not setInput filter list is not setOutput filter list is not setRouter filter list is not setNetbios Input host access list is not setNetbios Input bytes access list is not setNetbios Output host access list is not setNetbios Output bytes access list is not setUpdate time is 60 secondsIPX accounting is enabledIPX fast switching is configured (enabled)IPX SSE switching is disabledIPX NLSP is running on primary network E001RIP compatibility mode is AUTO (OFF)SAP compatibility mode is AUTO (OFF)Level 1 Hello interval 20 secLevel 1 Designated Router Hello interval 10 secLevel 1 CSNP interval 30 secLevel 1 LSP retransmit interval 5 sec, LSP (pacing) interval 1000 mSecLevel 1 adjacency count is 1Level 1 circuit ID is 0000.0C02.8CF9.02Table 302 describes the fields shown in the display.
Table 302 show ipx interface Field Descriptions
Ethernet1 is ..., line protocol is ...
Type of interface and whether it is currently active and inserted into the network (up) or inactive and not inserted (down).
IPX address is ...
Network and node address of the local router interface, followed by the type of encapsulation configured on the interface and the interface's status. Refer to the ipx network command for a list of possible values.
NOVELL-ETHER
Type of encapsulation being used on the interface, if any.
[up] line-up
Indicates whether IPX routing is enabled or disabled on the interface. The "line-up" indicates that IPX routing has been enabled with the ipx routing command. The "line-down" indicates that it is not enabled. The word in square brackets provides more detail about the status of IPX routing when it is in the process of being enabled or disabled.
RIPPQ
Number of packets in the RIP queue.
SAPPQ
Number of packets in the SAP queue.
Secondary address is ...
Address of a secondary network configured on this interface, if any, followed by the type of encapsulation configured on the interface and the interface's status. Refer to the ipx routing command for a list of possible values. This line is displayed only if you have configured a secondary address with the ipx routing command.
Delay of this IPX network, in ticks, ...
Value of the ticks field (configured with the ipx delay command).
throughput
Throughput of the interface (configured with the ipx spx-idle-time interface configuration command).
link delay
Link delay of the interface (configured with the ipx link-delay interface configuration command).
IPXWAN processing...
Indicates whether IPXWAN processing has been enabled on this interface with the ipx ipxwan command.
IPX SAP update interval
Indicates the frequency of outgoing SAP updates (configured with the ipx update interval command).
IPX type 20 propagation packet forwarding...
Indicates whether forwarding of IPX type 20 propagation packets (used by NetBIOS) is enabled or disabled on this interface, as configured with the ipx type-20-propagation command.
Outgoing access list
Indicates whether an access list has been enabled with the
ipx access-group command.IPX Helper access list
Number of the broadcast helper list applied to the interface with the ipx helper-list command.
SAP Input filter list
Number of the input SAP filter applied to the interface with the ipx input-sap-filter command.
SAP Output filter list
Number of the output SAP filter applied to the interface with the ipx output-sap-filter command.
SAP Router filter list
Number of the router SAP filter applied to the interface with the ipx router-sap-filter command.
SAP GNS output filter list
Number of the Get Nearest Server (GNS) response filter applied to the interface with the ipx output-gns-filter command.
Input filter list
Number of the input filter applied to the interface with the
ipx input-network-filter (RIP) command.Output filter list
Number of the output filter applied to the interface with the
ipx output-network-filter (RIP) command.Router filter list
Number of the router entry filter applied to the interface with the ipx router-filter command.
Netbios Input host access list
Name of the IPX NetBIOS input host filter applied to the interface with the ipx netbios input-access-filter host command.
Netbios Input bytes access list
Name of the IPX NetBIOS input bytes filter applied to the interface with the ipx netbios input-access-filter bytes command.
Netbios Output host access list
Name of the IPX NetBIOS output host filter applied to the interface with the ipx netbios input-access-filter host command.
Netbios Output bytes access list
Name of the IPX NetBIOS output bytes filter applied to the interface with the ipx netbios input-access-filter bytes command.
Update time
How often the Cisco IOS software sends RIP updates, as configured with the ipx update sap-after-rip command.
Watchdog spoofing ...
Indicates whether watchdog spoofing is enabled of disabled for this interface, as configured with the ipx watchdog-spoof command. This information is displayed only on serial interfaces.
IPX accounting
Indicates whether IPX accounting has been enabled with the ipx accounting command.
IPX fast switching
IPX autonomous switchingIndicates whether IPX fast switching is enabled (default) or disabled for this interface, as configured with ipx route-cache command. (If IPX autonomous switching is enabled, it is configured with the ipx route-cache cbus command.)
IPX SSE switching
Indicates whether IPX SSE switching is enabled for this interface, as configured with the ipx route-cache sse command.
IPX NLSP is running on primary network E001
Indicates that NLSP is running and the number of the primary IPX network on which it is running.
RIP compatibility mode
State of RIP compatibility (configured by the ipx nlsp rip interface configuration command).
SAP compatibility mode
State of SAP compatibility (configured by the ipx nlsp sap interface configuration command).
Level 1 Hello interval
Interval between transmission of hello packets for nondesignated routers (configured by the ipx nlsp hello-interval interface configuration command).
Level 1 Designated Router Hello interval
Interval between transmission of hello packets for designated routers (configured by the ipx nlsp hello-interval interface configuration command).
Level 1 CSNP interval
CSNP interval (as configured by the ipx nlsp csnp-interval interface configuration command).
Level 1 LSP retransmit interval
LSP retransmission interval (as configured by the
ipx nlsp retransmit-interval interface configuration command).LSP (pacing) interval
LSP transmission interval (as configured by the ipx nlsp lsp-interval interface configuration command).
Level 1 adjacency count
Number of Level 1 adjacencies in the adjacency database.
Level 1 circuit ID
System ID and pseudonode number of the designated router. In this example, 0000.0C02.8CF9 is the system ID, and 02 is the pseudonode number.
Related Commands
show ipx nhrp
To display the Next Hop Resolution Protocol (NHRP) cache, use the show ipx nhrp EXEC command.
show ipx nhrp [dynamic | static] [type number]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx nhrp command:
Router# show ipx nhrp1.0000.0c35.de01, Serial1 created 0:00:43 expire 1:59:16Type: dynamic Flags: authoritativeNBMA address: c141.0001.00011.0000.0c35.e605, Serial1 created 0:10:03 expire 1:49:56Type: static Flags: authoritativeNBMA address: c141.0001.0002Router#Table 303 describes the fields shown in the display.
Related Commands
Statically configures the IPX-to-NBMA address mapping of IPX destinations connected to an NBMA network.
show ipx nhrp traffic
To display Next Hop Resolution Protocol (NHRP) traffic statistics, use the show ipx nhrp traffic EXEC command.
show ipx nhrp traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx nhrp traffic command:
Router# show ipx nhrp trafficTunnel0request packets sent: 2request packets received: 4reply packets sent: 4reply packets received: 2register packets sent: 0register packets received: 0error packets sent: 0error packets received: 0Router#Table 304 describes the fields shown in the display.
show ipx nlsp database
To display the entries in the link-state packet (LSP) database, use the show ipx nlsp database EXEC command.
show ipx nlsp [tag] database [lspid] [detail]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
When you specify an NLSP tag, the router displays the link-state packet database entries for that 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.
Note
If you omit all options, a summary display is shown.
Examples
The following is sample output from the show ipx nlsp database command:
Router# show ipx nlsp database detailLSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL0000.0C00.3097.00-00* 0x00000042 0xC512 699 0/0/00000.0C00.3097.06-00* 0x00000027 0x0C27 698 0/0/00000.0C02.7471.00-00 0x0000003A 0x4A0F 702 0/0/00000.0C02.7471.08-00 0x00000027 0x0AF0 702 0/0/00000.0C02.7471.0A-00 0x00000027 0xC589 702 0/0/00000.0C02.747D.00-00 0x0000002E 0xC489 715 0/0/00000.0C02.747D.06-00 0x00000027 0xEEFE 716 0/0/00000.0C02.747D.0A-00 0x00000027 0xFE38 716 0/0/00000.0C02.74AB.00-00 0x00000035 0xE4AF 1059 0/0/00000.0C02.74AB.0A-00 0x00000027 0x34A4 705 0/0/00000.0C06.FBEE.00-00 0x00000038 0x3838 1056 0/0/00000.0C06.FBEE.0D-00 0x0000002C 0xD248 1056 0/0/00000.0C06.FBEE.0E-00 0x0000002D 0x7DD2 1056 0/0/00000.0C06.FBEE.17-00 0x00000029 0x32FB 1056 0/0/00000.0C00.AECC.00-00* 0x000000B6 0x62A8 7497 0/0/0IPX Area Address: 00000000 00000000IPX Mgmt Info 87.0000.0000.0001 Ver 1 Name oscarMetric: 45 Lnk 0000.0C00.AECC.06 MTU 1500 Dly 8000 Thru 64K PPPMetric: 20 Lnk 0000.0C00.AECC.02 MTU 1500 Dly 1000 Thru 10000K 802.3 RawMetric: 20 Lnk 0000.0C01.EF90.0C MTU 1500 Dly 1000 Thru 10000K 802.3 Raw0000.0C00.AECC.02-00* 0x00000002 0xDA74 3118 0/0/0IPX Mgmt Info E0.0000.0c00.aecc Ver 1 Name Ethernet0Metric: 0 Lnk 0000.0C00.AECC.00 MTU 0 Dly 0 Thru 0K 802.3 Raw0000.0C00.AECC.06-00* 0x00000002 0x5DB9 7494 0/0/0IPX Mgmt Info 0.0000.0000.0000 Ver 1 Name Serial0Metric: 0 Lnk 0000.0C00.AECC.00 MTU 0 Dly 0 Thru 0K PPPMetric: 1 IPX Ext D001 Ticks 0Metric: 1 IPX SVC Second-floor-printer D001.0000.0000.0001 Sock 1 Type 4Table 305 describes the fields shown in the display.
show ipx nlsp neighbors
To display NLSP neighbors and their states, use the show ipx nlsp neighbors EXEC command.
show ipx nlsp [tag] neighbors [interface] [detail]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
When you specify an NLSP tag value, the router displays the NLSP neighbors for that NLSP process. An NLSP process is a router's databases working together to manage route information about an area. NLSP version 1.0 routers must be in a single 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 adjacencies, link-state, and area address databases 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.
You must configure multiple NLSP processes when a router interconnects multiple NLSP areas.
Note
If you omit the keyword detail, a summary display is shown.
Examples
The following command output for the show ipx nlsp neighbors command shows a summary display of three adjacencies on two circuits:
Router# show ipx nlsp neighborsSystem Id Interface State Holdtime Priority Cir Adj Circuit Iddtp-37 Et1.2 Up 21 64 mc mc dtp-37.03dtp-37 Et1.1 Up 58 44 bc mc dtp-17.02dtp-17 ET1.1 Up 27 64 bc bc dtp-17.02This display indicates the following information about the first circuit (Circuit Id = dtp-37.03):
•
•
This display indicates the following information about the second circuit (Circuit Id = dtp-17.02):
•
•
•
The following is sample output from the show ipx nlsp neighbors detail command:
Router# show ipx nlsp neighbors detailSystem Id Interface State Holdtime Priority Cir Adj Circuit Id0000.0C01.EF90 Ethernet1 Up 25 64 mc mc 0000.0C01.EF90.0CIPX Address: E1.0000.0c01.ef91IPX Areas: 00000000/00000000Uptime: 2:59:11Table 306 describes the fields shown in the display.
show ipx nlsp spf-log
To display a history of the shortest path first (SPF) calculations for NLSP, use the show ipx nlsp spf-log EXEC command.
show ipx nlsp [tag] spf-log
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx nlsp spf-log command:
Router> show ipx nlsp spf-logLevel 1 SPF logWhen Duration Nodes Count Triggers0:30:59 1028 84 1 TLVCONTENT0:27:09 1016 84 1 TLVCONTENT0:26:30 1136 84 1 TLVCONTENT0:23:11 1244 84 1 TLVCONTENT0:22:39 924 84 2 TLVCONTENT0:22:08 1036 84 1 TLVCONTENT0:20:02 1096 84 1 TLVCONTENT0:19:31 1140 84 1 TLVCONTENT0:17:25 964 84 2 PERIODIC TLVCONTENT0:16:54 996 84 1 TLVCONTENT0:16:23 984 84 1 TLVCONTENT0:15:52 1052 84 1 TLVCONTENT0:14:34 1112 84 1 TLVCONTENT0:13:37 992 84 1 TLVCONTENT0:13:06 1036 84 1 TLVCONTENT0:12:35 1008 84 1 TLVCONTENT0:02:52 1032 84 1 TLVCONTENT0:02:16 1032 84 1 PERIODIC0:01:44 1000 84 3 TLVCONTENTTable 307 describes the fields shown in the display.
show ipx route
To display the contents of the IPX routing table, use the show ipx route user EXEC command.
show ipx route [network] [default] [detailed]
Syntax Description
Command Modes
EXEC
Command History
10.0
This command was introduced prior to Cisco IOS Release 10.0.
10.0
The following keywords were added:
•
•
Examples
The following is sample output from the show ipx route command:
Router# show ipx routeCodes: C - Connected primary network, c - Connected secondary networkS - Static, F - Floating static, L - Local (internal), W - IPXWANR - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregates - seconds, u - uses8 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.No default route known.L D40 is the internal networkC 100 (NOVELL-ETHER), Et1C 7000 (TUNNEL), Tu1S 200 via 7000.0000.0c05.6023, Tu1R 300 [02/01] via 100.0260.8c8d.e748, 19s, Et1S 2008 via 7000.0000.0c05.6023, Tu1R CC0001 [02/01] via 100.0260.8c8d.e748, 19s, Et1Table 308 describes the fields shown in the display.
Table 308 show ipx route Field Descriptions
Codes
Codes defining how the route was learned.
L - Local
Internal network number.
C - Connected primary network
Directly connected primary network.
c - connected secondary network
Directly connected secondary network.
S - Static
Statically defined route via the ipx route command.
R - RIP
Route learned from a RIP update.
E - EIGRP
Route learned from an Enhanced IGRP (EIGRP) update.
W - IPXWAN
Directly connected route determined via IPXWAN.
8 Total IPX routes
Number of routes in the IPX routing table.
No parallel paths allowed
Maximum number of parallel paths for which the Cisco IOS software has been configured with the ipx maximum-paths command.
Novell routing algorithm variant in use
Indicates whether the Cisco IOS software is using the IPX-compliant routing algorithms (default).
Net 1
Network to which the route goes.
[3/2]
Delay/Metric. Delay is the number of IBM clock ticks (each tick is 1/18 seconds) reported to the destination network. Metric is the number of hops reported to the same network. Delay is used as the primary routing metric, and the metric (hop count) is used as a tie breaker.
via network.node
Address of a router that is the next hop to the remote network.
age
Amount of time (in hours, minutes, and seconds) that has elapsed since information about this network was last received.
uses
Number of times this network has been looked up in the route table. This field is incremented when a packet is process-switched, even if the packet is eventually filtered and not sent. As such, this field represents a fair estimate of the number of times a route gets used.
Ethernet0
Interface through which packets to the remote network will be sent.
(NOVELL-ETHER)
Encapsulation (frame) type. This is shown only for directly connected networks.
is directly connected
Indicates that the network is directly connected to the router.
When the Cisco IOS software generates an aggregated route, the show ipx route command displays a line item similar to the following:
NA 1000 FFFFF000 [**][**/06] via 0.0000.0000.0000, 163s, Nu0In the following example, the router that sends the aggregated route also generates the aggregated route line item in its table. But the entry in the table points to the null interface (Nu0), indicating that if this aggregated route is the most-specific route when a packet is being forwarded, the router drops the packet instead.
Router# show ipx routeCodes: C - Connected primary network, c - Connected secondary networkS - Static, F - Floating static, L - Local (internal), W - IPXWANR - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregates - seconds, u - uses13 Total IPX routes. Up to 4 parallel paths and 16 hops allowed.No default route known.NA 1000 FFFFF000 [**][**/06] via 0.0000.0000.0000, 163s, Nu0L 2008 is the internal networkC 1 (NOVELL-ETHER), Et0C 89 (SAP), To0C 91 (SAP), To1C 100 (NOVELL-ETHER), Et1N 2 [19][01/01] via 91.0000.30a0.51cd, 317s, To1N 3 [19][01/01] via 91.0000.30a0.51cd, 327s, To1N 20 [20][01/01] via 1.0000.0c05.8b24, 2024s, Et0N 101 [19][01/01] via 91.0000.30a0.51cd, 327s, To1NX 1000 [20][02/02][01/01] via 1.0000.0c05.8b24, 2024s, Et0N 2010 [20][02/01] via 1.0000.0c05.8b24, 2025s, Et0N 2011 [19][02/01] via 91.0000.30a0.51cd, 328s, To1The following is sample output from the show ipx route detailed command:
Router# show ipx route detailedCodes: C - Connected primary network, c - Connected secondary networkS - Static, F - Floating static, L - Local (internal), W - IPXWANR - RIP, E - EIGRP, N - NLSP, X - External, s - seconds, u - uses9 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.No default route known.L D35 is the internal networkC E001 (SAP), Et0C D35E2 (NOVELL-ETHER), Et2R D34 [02/01]-- via E001.0000.0c02.8cf9, 43s, 1u, Et0N D36 [20][02/01]-- via D35E2.0000.0c02.8cfc, 704s, 1u, Et210000000:1000:1500:0000.0c02.8cfb:6:0000.0c02.8cfcNX D40 [20][03/02][02/01]-- via D35E2.0000.0c02.8cfc, 704s, 1u, Et210000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfcR D34E1 [01/01]-- via E001.0000.0c02.8cf9, 43s, 1u, Et0NX D40E1 [20][02/02][01/01]-- via D35E2.0000.0c02.8cfc, 704s, 3u, Et210000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfcN D36E02 [20][01/01]-- via D35E2.0000.0c02.8cfc, 705s, 2u, Et210000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfcTable 309 explains the additional fields shown in the display.
Related Commands
show ipx servers
To list the IPX servers discovered through Service Advertising Protocol (SAP) advertisements, use the show ipx servers EXEC command.
show ipx servers [unsorted | [sorted [name | net | type]]] [regexp name]
Syntax Description
Defaults
IPX servers are displayed numerically by SAP service type.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx servers command when NLSP is enabled:
Router# show ipx serversCodes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail9 Total IPX ServersTable ordering is based on routing and server infoType Name Net Address Port Route Hops ItfN+ 4 MERLIN1-VIA-E03 E03E03.0002.0004.0006:0451 4/03 4 Et0N+ 4 merlin E03E03.0002.0004.0006:0451 4/03 3 Et0N+ 4 merlin 123456789012345 E03E03.0002.0004.0006:0451 4/03 3 Et0S 4 WIZARD1--VIA-E0 E0.0002.0004.0006:0451 none 2N+ 4 dtp-15-AB E002.0002.0004.0006:0451 none 4 Et0N+ 4 dtp-15-ABC E002.0002.0004.0006:0451 none 4 Et0N+ 4 dtp-15-ABCD E002.0002.0004.0006:0451 none 4 Et0N+ 4 merlin E03E03.0002.0004.0006:0451 4/03 3 Et0N+ 4 dtp-15-ABC E002.0002.0004.0006:0451 none 4 Et0Table 310 describes the fields shown in the display.
Table 310 show ipx servers Field Descriptions
Codes:
Codes defining how the service was learned.
S - Static
Statically defined service via the ipx sap command.
P - Periodic
Service learned via a SAP update.
E - EIGRP
Service learned via Enhanced IGRP.
N - NLSP
Service learned via NLSP.
H- Holddown
Indicates that the entry is in holddown mode and is not reachable.
+ - detail
Indicates that multiple paths to the server exist. Use the show ipx servers detailed EXEC command to display more detailed information about the paths.
Type
Contains codes from Codes field to indicates how service was learned.
Name
Name of server.
Net
Network on which server is located.
Address
Network address of server.
Port
Source socket number.
Route
Ticks/hops (from the routing table).
Hops
Hops (from the SAP protocol).
Itf
Interface through which to reach server.
The following example uses a regular expression to display SAP table entries corresponding to a particular group of servers in the accounting department of a company:
Router# show ipx servers regexp ACCT\_SERV.+Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail9 Total IPX ServersTable ordering is based on routing and server infoType Name Net Address Port Route Hops ItfS 108 ACCT_SERV_1 7001.0000.0000.0001:0001 1/01 2 Et0S 108 ACCT_SERV_2 7001.0000.0000.0001:0001 1/01 2 Et0S 108 ACCT_SERV_3 7001.0000.0000.0001:0001 1/01 2 Et0See Table 310 for show IPX servers field descriptions.
Note
Related Commands
show ipx spx-spoof
To display the table of SPX connections through interfaces for which SPX spoofing is enabled, use the show ipx spx-spoof EXEC command.
show ipx spx-spoof
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx spx-spoof command:
Router> show ipx spx-spoofLocal SPX Network.Host:sock Cid Remote SPX Network.Host:sock Cid Seq Ack Idle CC0001.0000.0000.0001:8104 0D08 200.0260.8c8d.e7c6:4017 7204 09 0021 120 CC0001.0000.0000.0001:8104 0C08 200.0260.8c8d.c558:4016 7304 07 0025 120Table 311 describes the fields shown in the display.
Related Commands
show ipx traffic
To display information about the number and type of IPX packets transmitted and received, use the show ipx traffic user EXEC command.
show ipx traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx traffic command:
Router> show ipx trafficSystem Traffic for 0.0000.0000.0001 System-Name: routerTime since last clear: neverRcvd: 0 total, 0 format errors, 0 checksum errors, 0 bad hop count0 packets pitched, 0 local destination, 0 multicastBcast: 0 received, 0 sentSent: 0 generated, 0 forwarded0 encapsulation failed, 0 no routeSAP: 0 Total SAP requests, 0 Total SAP replies, 1 servers0 SAP General Requests, 2 sent, 0 ignored, 0 replies0 SAP Get Nearest Server requests, 0 replies0 SAP Nearest Name requests, 0 replies0 SAP General Name requests, 0 replies0 SAP advertisements received, 324 sent, 0 Throttled0 SAP flash updates sent, 0 SAP format errorsRIP: 0 RIP requests, 0 ignored, 0 RIP replies, 3 routes0 RIP advertisements received, 684 sent, 0 Throttled0 RIP flash updates sent, 0 atlr sent2 RIP general requests sent0 RIP format errorsEcho: Rcvd 0 requests, 0 repliesSent 0 requests, 0 replies0 unknown: 0 no socket, 0 filtered, 0 no helper0 SAPs throttled, freed NDB len 0Watchdog:0 packets received, 0 replies spoofedQueue lengths:IPX input: 0, SAP 0, RIP 0, GNS 0SAP throttling length: 0/(no limit), 0 nets pending lost route replyDelayed process creation: 0EIGRP: Total received 0, sent 0Updates received 0, sent 0Queries received 0, sent 0Replies received 0, sent 0SAPs received 0, sent 0NLSP: Time since last clear: neverNLSP: Level-1 Hellos (sent/rcvd): 0/0PTP Hellos (sent/rcvd): 0/0Level-1 LSPs sourced (new/refresh): 1/0Level-1 LSPs flooded (sent/rcvd): 0/0LSP Retransmissions: 0Level-1 CSNPs (sent/rcvd): 0/0Level-1 PSNPs (sent/rcvd): 0/0Level-1 DR Elections: 0Level-1 SPF Calculations: 1Level-1 Partial Route Calculations: 0LSP checksum errors received: 0Trace: Rcvd 0 requests, 0 repliesSent 0 requests, 0 repliesTable 312 describes the fields shown in the display.
show sse summary
To display a summary of Silicon Switch Processor (SSP) statistics, use the show sse summary EXEC command.
show sse summary
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show sse summary command:
Router# show sse summarySSE utilization statisticsProgram words Rewrite bytes Internal nodes DepthOverhead 499 1 8IP 0 0 0 0IPX 0 0 0 0SRB 0 0 0 0CLNP 0 0 0 0IP access lists 0 0 0Total used 499 1 8Total free 65037 262143Total available 65536 262144Free program memory[499..65535]Free rewrite memory[1..262143]Internals75032 internal nodes allocated, 75024 freedSSE manager process enabled, microcode enabled, 0 hangsLongest cache computation 4ms, longest quantum 160ms at 0x53AC8spf-interval
To control how often the Cisco IOS software performs the Shortest Path First (SPF) calculation, use the spf-interval router configuration command. To restore the default interval, use the no form of this command.
spf-interval seconds
no spf-interval seconds
Syntax Description
seconds
Minimum amount of time between SPF calculations, in seconds. It can be a number from 1 to 120. The default is 5 seconds.
Defaults
5 seconds
Command Modes
Router configuration
Command History
Usage Guidelines
SPF calculations are performed only when the topology changes. They are not performed when external routes change.
The spf-interval command controls how often the Cisco IOS software can perform the SPF calculation. The SPF calculation is processor-intensive. Therefore, it may be useful to limit how often this is done, especially when the area is large and the topology changes often. Increasing the SPF interval reduces the processor load of the router, but potentially slows down the rate of convergence.
Examples
The following example sets the SPF calculation interval to 30 seconds:
spf-interval 30Related Commands
Specifies the routing protocol to use.
Enables the logging of changes in Enhanced IGRP neighbor adjacencies.
Controls the hold-down period between partial route calculations.
