|
|
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.
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]| access-list-number | Number of the access list. This is a decimal 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 (decimal) of an IPX protocol type. This is sometimes referred to as the packet type. Table 45 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-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-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-socket | Socket name or number (hexadecimal) from which the packet is being sent. Table 45 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-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-nodemask | (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-socket | (Optional) Socket name or number (hexadecimal) to which the packet is being sent. Table 45 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). |
No access lists are predefined.
Global configuration
This command first appeared in Cisco IOS Release 10.0. The log keyword first appeared in Cisco IOS Relese 11.2.
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.
Table 45 lists some IPX protocol names and numbers. Table 45 lists some IPX socket names and numbers. For additional information about IPX protocol numbers and socket numbers, contact Novell.
| IPX Protocol Number (Decimal) | IPX Protocol Name | Protocol (Packet Type) |
|---|---|---|
| -1 | any | Wildcard; matches any packet type in 900 lists |
| 0 | Undefined; refer to the socket number to determine the packet type | |
| 1 | rip | Routing Information Protocol (RIP) |
| 4 | sap | Service Advertising Protocol (SAP) |
| 5 | spx | Sequenced Packet Exchange (SPX) |
| 17 | ncp | NetWare Core Protocol (NCP) |
| 20 | netbios | IPX NetBIOS |
| IPX Socket Number (Hexadecimal) | IPX Socket Name | Socket |
|---|---|---|
| 0 | all | All sockets, wildcard used to match all sockets |
| 2 | cping | Cisco IPX ping packet |
| 451 | ncp | NetWare Core Protocol (NCP) process |
| 452 | sap | Service Advertising Protocol (SAP) process |
| 453 | rip | Routing Information Protocol (RIP) process |
| 455 | netbios | Novell NetBIOS process |
| 456 | diagnostic | Novell diagnostic packet |
| 457 | Novell serialization socket | |
| 4000-7FFF | Dynamic sockets; used by workstations for interaction with file servers and other network servers | |
| 8000-FFFF | Sockets as assigned by Novell, Inc. | |
| 85BE | eigrp | IPX Enhanced Interior Gateway Routing Protocol (Enhanced IGRP) |
| 9001 | nlsp | NetWare Link Services Protocol |
| 9086 | nping | Novell standard ping packet |
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--lst-numberTo delete the access list for a specific protocol, use the following command:
no access-list access-list-number {deny | permit} protocolThe 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 -1
The 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):
access-list 910 permit 2 10.0000.0C01.5234 0000.0000.0000 0 1000.0000.0000.0000 F.FFFF.FFFF.FFFF 0
A dagger (+) indicates that the command is documented outside this chapter.
access-list (standard)
ipx access-group
ipx input-network-filter
ipx output-network-filter
ipx router-filter
priority-list protocol +
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 [ticks ticks]| access-list-number | Number of the access list. This is a decimal number from 1200 to 1299. |
| deny | Denies redistribution of explicit routes if the conditions are matched. If you have enabled route summarization with route-aggregation command, the router redistributes an aggregated route instead. |
| permit | Permits redistribution of explicit routes if the conditions are matched. |
| network | Network number to summarize. An IPX network number 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. |
| network-mask | Specifies the portion of the network address that is common to all addresses in the route summary. The high-order bits of network-mask must be contiguous Fs, while the low-order bits must be contiguous zeros (0). An arbitrary mix of Fs and 0s is not permitted. |
| ticks ticks | (Optional) Metric assigned to the route summary. The default is 1 tick. |
| area-count area-count | (Optional) Maximum number of NLSP areas to which the route summary can be redistributed. The default is 6 areas. |
No access lists are predefined.
Global configuration
This command first appeared in Cisco IOS Release 11.1.
Use the NLSP route aggregation access list in the following situations:
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 routing ipx internal-network 2000 interface ethernet 1 ipx network 1001 ipx nlsp area1 enable interface ethernet 2 ipx network 2001 access-list 1200 deny aaaa0000 ffff0000 access-list 1200 permit -1 ipx router nlsp area area-address 1000 fffff000 route-aggregation redistribute rip access-list 1200
area-address
ipx nlsp enable
ipx router
redistribute
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]| access-list-number | Number of the SAP access list. This is a decimal 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 47 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. |
No access lists are predefined.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
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 47 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.
| Service Type (Hexadecimal) | Description |
|---|---|
| 1 | User |
| 2 | User group |
| 3 | Print server queue |
| 4 | File server |
| 5 | Job server |
| 7 | Print server |
| 9 | Archive server |
| A | Queue for job servers |
| 21 | Network Application Support Systems Network Architecture (NAS SNA) gateway |
| 2D | Time Synchronization value-added process (VAP) |
| 2E | Dynamic SAP |
| 47 | Advertising print server |
| 4B | Btrieve VAP 5.0 |
| 4C | SQL VAP |
| 7A | TES--NetWare for Virtual Memory System (VMS) |
| 98 | NetWare access server |
| 9A | Named Pipes server |
| 9E | Portable NetWare--UNIX |
| 107 | RCONSOLE |
| 111 | Test server |
| 166 | NetWare management (Novell's Network Management Station [NMS]) |
| 26A | NetWare management (NMS console) |
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-numberTo delete the access list for a specific network, use the following command:
no access-list access-list-number {deny | permit} networkThe 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 4 access-list 1001 permit -1
A dagger (+) indicates that the command is documented outside this chapter.
ipx input-sap-filter
ipx output-gns-filter
ipx output-sap-filter
ipx router-sap-filter
priority-list protocol +
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| access-list-number | Number of the access list. This is a decimal number from 800 to 899. |
| deny | Denies access if the conditions are matched. |
| permit | Permits access if the conditions are matched. |
| source-network | 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. |
| 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. |
No access lists are predefined.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
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-numberTo delete the access list for a specific network, use the following command:
no access-list access-list-number {deny | permit} source-networkThe following example denies access to traffic from all IPX networks (-1) to destination network 2:
access-list 800 deny -1 2
The following example denies access to all traffic from IPX address 1.0000.0c00.1111:
access-list 800 deny 1.0000.0c00.1111
The 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.ffff
The 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.0000
access-list 800 deny 1.1111.1111.1111 2.2222.2222.2222
A dagger (+) indicates that the command is documented outside this chapter.
access-list (extended)
ipx access-group
ipx input-network-filter
ipx output-network-filter
ipx router-filter
priority-list protocol +
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| 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. |
No area address is defined by default.
Router configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example defines an area address that includes networks AAAABBC0 through AAAABBDF:
area-address AAAABBC0 FFFFFFE0
The following example defines an area address that includes all networks:
area-address 0 0
ipx router nlsp
To delete all entries in the accounting database when IPX accounting is enabled, use the clear ipx accounting EXEC command.
clear ipx accounting [checkpoint]| checkpoint | (Optional) Clears the checkpointed database. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
Specifying the clear ipx accounting command with no keywords deletes all entries in the active database.
You can also delete all entries in the checkpointed database by issuing the clear ipx accounting command twice in succession.
The following example clears all entries in the active database:
clear ipx accounting
ipx accounting
ipx accounting-list
ipx accounting-threshold
ipx accounting-transits
show ipx accounting
To delete entries from the IPX fast-switching cache, use the clear ipx cache EXEC command.
clear ipx cacheThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The clear ipx cache command clears entries used for fast switching, autonomous switching, and silicon switching engine (SSE) fast switching.
The following example deletes all entries from the IPX fast-switching cache:
clear ipx cache
To clear all dynamic entries from the Next Hop Resolution Protocol (NHRP) cache, use the clear ipx nhrp EXEC command.
clear ipx nhrpThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
This command does not clear any static (configured) IPX-to-NBMA address mappings from the NHRP cache.
The following example clears all dynamic entries from the NHRP cache for the interface:
clear ipx nhrp
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| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
EXEC
This command first appeared in Cisco IOS Release 10.3.
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.
The following example deletes all NLSP adjacencies from the adjacency database:
clear ipx nlsp neighbors
The following example deletes the NLSP adjacencies for process area2:
clear ipx nlsp area2 neighbors
To delete routes from the IPX routing table, use the clear ipx route EXEC command.
clear ipx route {network [network-mask] | default | *}| network | Number of the network whose routing table entry you want to delete. This 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. |
| network-mask | (Optional) Specifies the portion of the network address that is common to all addresses in an NLSP route summary. When used with the network argument, it specifies the an NLSP route summary to clear.
The high-order bits of network-mask must be contiguous Fs, while the low-order bits must be contiguous zeros (0). An arbitrary mix of Fs and 0s is not permitted. |
| default | Deletes the default route from the routing table. |
| * | Deletes all routes in the routing table. |
EXEC
This command first appeared in Cisco IOS Release 10.0. The network-mask argument and default keyword first appeared in Cisco IOS Release 11.1.
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.
The following example clears the entry for network 3 from the IPX routing table:
clear ipx route 3
The following example clears a route summary entry from the IPX routing table:
clear ipx route ccc00000 fff00000
To have the Cisco 7000 series Route Processor recompute the entries in the IPX SSE fast-switching cache, use the clear ipx sse EXEC command.
clear ipx sseThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
Recomputing the entries in the SSE fast-switching cache of the rendezvous point (RP) also updates the fast-switching cache of the Silicon Switch Processor (SSP).
The following example recomputes the entries in the IPX SSE fast-switching cache:
clear ipx sse
To reinitialize the Route Processor on the Cisco 7000 series, use the clear sse EXEC command.
clear sseThis command has no arguments or keywords.
Disabled
EXEC
This command first appeared in Cisco IOS Release 10.3.
The silicon switching engine (SSE) is on the Silicon Switch Processor (SSP) board in the Cisco 7000 series.
The following example causes the route processor to be reinitialized:
clear sse
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 in [interface-name]| access-list-number | Standard IPX access list number in the range 800 to 899 or NLSP access list number in the range 1200 to 1299. The list explicitly specifies which networks are to be received and which are to be suppressed. |
| in | Applies the access list to incoming routing updates. |
| interface-name | (Optional) Interface on which the access list should be applied to incoming updates. If no interface is specified, the access list is applied to all incoming updates. |
Disabled
Router configuration
This command first appeared in Cisco IOS Release 10.0.
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 2 access-list 800 permit 3 access-list 800 deny -1 ! ipx router eigrp 100 network 3 distribute-list 800 in
access-list (NLSP route aggregation filtering)
access-list (standard)
distribute-list out
redistribute
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 out [interface-name | routing-process]| access-list-number | Standard IPX access list number in the range 800 to 899 or NLSP access list number in the range 1200 to 1299. The list explicitly specifies which networks are to be sent and which are to be suppressed in routing updates. |
| out | Applies the access list to outgoing routing updates. |
| interface-name | (Optional) Interface on which the access list should be applied to outgoing updates. If no interface is specified, the access list is applied to all outgoing updates. |
| routing-process | (Optional) Name of a particular routing process as follows:
· eigrp autonomous-system-number · rip · nlsp [tag] |
Disabled
Router configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example causes only one network--network 3--to be advertised by an Enhanced IGRP routing process:
access-list 800 permit 3 access-list 800 deny -1 ! ipx router eigrp 100 network 3 distribute-list 800 out
access-list (NLSP route aggregation filtering)
access-list (standard)
distribute-list in
redistribute
To filter services 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-sap-list access-list-number in [interface-name]| access-list-number | SAP access list number in the range 1000 to 1099. The list explicitly specifies which services are to be received and which are to be suppressed. |
| in | Applies the access list to incoming routing updates. |
| interface-name | (Optional) Interface on which the access list should be applied to incoming updates. If no interface is specified, the access list is applied to all incoming updates. |
Disabled
Router configuration
This command first appeared in Cisco IOS Release 11.1.
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 2 access-list 1000 permit 3 access-list 1000 deny -1 ! ipx router nlsp area1 redistribute eigrp distribute-sap-list 1000 in
access-list (SAP filtering)
distribute-list out
redistribute
To suppress services from being advertised in SAP updates, SAP (Service Advertising Protocol) 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 out [interface-name | routing-process]| access-list-number | SAP access list number in the range 1000 to 1099. The list explicitly specifies which networks are to be sent and which are to be suppressed in routing updates. |
| out | Applies the access list to outgoing routing updates. |
| interface-name | (Optional) Interface on which the access list should be applied to outgoing updates. If no interface is specified, the access list is applied to all outgoing updates. |
| routing-process | (Optional) Name of a particular routing process as follows:
· eigrp autonomous-system-number · rip · nlsp [tag] |
Disabled
Router configuration
This command first appeared in Cisco IOS Release 11.1.
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.
The following example causes only services from network 3 to be advertised by an Enhanced IGRP routing process:
access-list 1010 permit 3 access-list 1010 deny -1 ! ipx router eigrp 100 network 3 distribute-sap-list 1010 out
access-list (SAP filtering)
distribute-sap-list in
redistribute
To apply generic input and output filters to an interface, use ipx access-group interface configuration command. To remove filters, use the no form of this command.
ipx access-group access-list-number [in | out]| access-list-number | Number of the access list. For standard access lists, access-list-number is a decimal number from 800 to 899. For extended access lists, access-list-number is a decimal number from 900 to 999. |
| in | Filters inbound packets. All incoming packets defined with either standard or extended access lists are filtered by the entries in this access list. |
| out | Filter outbound packets. All outgoing packets defined with either standard or extended access lists and forwarded through the interface are filtered by the entries in this access list. This is the default when you do not specify an input (in) or output (out) keyword in the command line. |
No filters are predefined.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
In the following example, access list 801 is applied 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 1 ipx access-group 801
In the following example, access list 901 is applied to Ethernet interface 0. The access list is an input filter access list as specified by the keyword in.
interface ethernet 0 ipx access-group 901 in
To 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 0 no ipx access-group 901 in
A dagger (+) indicates that the command is documented outside this chapter.
access-list (extended)
access-list (standard)
priority-list protocol +
To enable IPX accounting, use the ipx accounting interface configuration command. To disable IPX accounting, use the no form of this command.
ipx accountingThis command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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. Accounting tracks only IPX traffic that is passing out of the router; it does not track traffic generated by or terminating at this device.
IPX accounting statistics will be accurate even if IPX fast switching is enabled or if IPX access lists are being used. However, IPX accounting does not keep statistics if autonomous switching is enabled.
The software maintains two accounting databases: an active database and a checkpointed database.
The following example enables IPX accounting on Ethernet interface 0:
interface ethernet 0 ipx accounting
clear ipx accounting
ipx accounting-list
ipx accounting-threshold
ipx accounting-transits
show ipx accounting
To filter the 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| number | 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 FFFFFFFD.
You do not need to specify leading zeros in the network number. For example, for the network number 000000AA you can enter AA. |
| mask | Network mask. |
No filters are predefined.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
The source and destination addresses of each IPX packet are logically ANDed with the mask and compared with the network number. If there is a match, accounting information about the IPX packet is entered into the 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.
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.0000
clear ipx accounting
ipx accounting
ipx accounting-threshold
ipx accounting-transits
show ipx accounting
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| threshold | Maximum number of entries (source and destination address pairs) that the Cisco IOS software can accumulate. |
512 entries
Global configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example sets the IPX accounting database threshold to 500 entries:
ipx accounting-threshold 500
clear ipx accounting
ipx accounting
ipx accounting-list
ipx accounting-transits
show ipx accounting
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| count | Number of transit entries that will be stored in the IPX accounting database. |
0 entries
Global configuration
This command first appeared in Cisco IOS Release 10.0.
Transit entries are those that do not match any of the filters specified by ipx accounting-list global configuration commands. If you have not defined any filters, no transit entries are possible.
To maintain accurate accounting totals, the Cisco IOS software maintains two accounting databases: an active database and a checkpointed database.
The following example specifies a maximum of 100 transit records to be stored in the IPX accounting database:
ipx accounting-transits 100
clear ipx accounting
ipx accounting-list
ipx accounting-threshold
show ipx accounting
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| network | Number of the network via which to advertise the default route. |
Disabled (that is, all known routes advertised out the interface)
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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 1,000 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 1,000 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.
The following example enables the advertising of the default route only:
interface ethernet 1 ipx network 1234 ipx advertise-default-route-only 1234
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| interval | Minimum time, in seconds, between successive queries of each Enhanced IGRP neighbor's backup server table. The default is 15 seconds. |
15 seconds
Global configuration
This command first appeared in Cisco IOS Release 10.0.
A lower interval may use more CPU resources, but may cause lost server information to be retrieved from other servers' tables sooner.
The following example changes the server query time to 5 seconds:
ipx backup-server-query-interval 5
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| as-number | Autonomous system number. |
| percent | Percentage of bandwidth that Enhanced IGRP may use. |
50 percent
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
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.
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 0 bandwidth 56 ipx bandwidth-percent eigrp 209 75
A dagger (+) indicates that the command is documented outside this chapter.
bandwidth +
ipx router
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-fastswitchingThis command has no arguments or keywords.
Disabled
The default behavior is to process-switch directed broadcast packets.
Global configuration
This command first appeared in Cisco IOS Release 11.1
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.
The following example enables the router to fast switch IPX directed broadcast packets:
ipx broadcast-fastswitching
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| 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. |
55 ms
Global configuration
This command first appeared in Cisco IOS Release 11.1.
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.
The following example sets a default interpacket delay of 55 ms for RIP updates sent on all interfaces:
ipx default-output-rip-delay 55
ipx default-triggered-rip-delay
ipx output-rip-delay
ipx triggered-rip-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| 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. |
55 ms
Global configuration
This command first appeared in Cisco IOS Release 11.1.
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.
The following example sets a default interpacket delay of 55 ms for SAP updates sent on all interfaces:
ipx default-output-sap-delay 55
ipx default-triggered-sap-delay
ipx output-sap-delay
ipx triggered-sap-delay
To forward towards the default network, if known, all packets for which a route to the destination network is unknown, use the ipx default-route global configuration command. To discard all packets for which a route to the destination network is unknown, use the no form of this command.
ipx default-routeThis command has no arguments or keywords.
Enabled; that is, all packets for which a route to the destination is unknown are forwarded toward the default network, which is -2 (0xFFFFFFFE).
Global configuration
This command first appeared in Cisco IOS Release 10.3.
The following example disables the forwarding of packets towards the default network:
no ipx default-route
ipx advertise-default-route-only
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| 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. |
55 ms
Global configuration
This command first appeared in Cisco IOS Release 11.1.
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 "Default" section.
This command is also useful on limited bandwidth point-to-point links, or X.25 and Frame Relay multipoint interfaces.
The following example sets an interpacket delay of 55 ms for triggered routing updates sent on all interfaces:
ipx default-triggered-rip-delay 55
ipx default-output-rip-delay
ipx output-rip-delay
ipx triggered-rip-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| 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. |
55 ms
Global configuration
This command first appeared in Cisco IOS Release 11.1.
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 "Default" section.
This command is also useful on limited bandwidth point-to-point links, or X.25 and Frame Relay multipoint interfaces.
The following example sets an interpacket delay of 55 ms for triggered SAP updates sent on all interfaces:
ipx default-triggered-sap-delay 55
ipx default-output-sap-delay
ipx output-sap-delay
ipx triggered-sap-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| ticks | Number of IBM clock ticks of delay to use. One clock tick is 1/18 of a second (approximately 55 ms). |
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.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example changes the delay for serial interface 0 to 10 ticks:
interface serial 0 ipx delay 10
A dagger (+) indicates that the command is documented outside this chapter.
delay +
ipx maximum-paths
ipx output-network-filter
ipx output-rip-delay
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| network | Number of the network to shut down. This 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. |
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example administratively shuts down network AA on Ethernet interface 0:
interface ethernet 0 ipx down AA
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-disableThis command has no arguments or keywords.
Replies are sent to IPX GNS queries.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The following example disables the sending of replies to GNS queries on Ethernet interface 0:
interface ethernet 0 ipx gns-reply-disable
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]| milliseconds | (Optional) Time, in milliseconds, that the Cisco IOS software waits after receiving a GNS request from an IPX client before responding with a server name to that client. The default is zero, which indicates no delay. |
0 (no delay)
Global configuration (globally changes the delay for the router)
Interface configuration (overrides the globally configured delay for an interface)
This command first appeared in Cisco IOS Release 10.0.
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.
The following example sets the delay in responding to GNS requests to 500 ms (0.5 second):
ipx gns-response-delay 500
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-robinThe command has no arguments or keywords.
The most recently learned, eligible server is used.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example responds to GNS requests using a round-robin selection method from a list of eligible nearest servers:
ipx gns-round-robin
ipx output-gns-filter
ipx output-sap-delay
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| autonomous-system-number | Enhanced IGRP autonomous system number. It can be a decimal integer from 1 to 65535. |
| seconds | Interval between hello packets, in seconds. The default interval is 5 seconds, which is one-third of the default hold time. |
For low-speed NBMA networks: 60 seconds
For all other networks: 5 seconds
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example changes the hello interval to 10 seconds:
interface ethernet 0 ipx network 10 ipx hello-interval eigrp 4 10
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| network | Network on which the target IPX server resides. This is an eight-digit hexadecimal number that uniquely identifies a network cable segment. It can be a number in the range 1 to FFFFFFFD. A network number of -1 indicates all-nets flooding. You do not need to specify leading zeros in the network number. For example, for the network number 000000AA, you can enter AA. |
| .node | 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). A node number of FFFF.FFFF.FFFF matches all servers. |
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.FFFF
On systems configured for IPX routing, this helper address is displayed as follows (via the show ipx interface command):
FFFFFFFF.FFFF.FFFF.FFFF
Although 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.
In the following example, 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.110a
ipx helper-list
ipx type-20-propagation
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| access-list-number | Number of the access list. All outgoing packets defined with either standard or extended access lists are filtered by the entries in this access list. For standard access lists, access-list-number is a decimal number from 800 to 899. For extended access lists, it is a decimal number from 900 to 999. |
No access list is preassigned.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
You should filter IPX broadcasts on dial-on-demand routing (DDR) and other similar interfaces, because IPX sends broadcast messages very regularly.
The following example assigns access list 900 to Ethernet interface 0 to control broadcast traffic:
interface ethernet 0 ipx helper-list 900
access-list (extended)
access-list (standard)
ipx helper-address
ipx type-20-propagation
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| autonomous-system-number | Enhanced IGRP autonomous system number. It can be a decimal integer from 1 to 65535. |
| seconds | Hold-down time, in seconds. The default hold time is 5 seconds. |
5 seconds
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example changes the hold-down time for autonomous system 4 to 45 seconds:
interface ethernet 0 ipx network 10 ipx hold-down eigrp 4 45
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| autonomous-system-number | Enhanced IGRP autonomous system number. It can be a decimal integer from 1 to 65535. |
| seconds | Hold time, in seconds. The hold time is advertised in hello packets and indicates to neighbors the length of time they should consider the sender valid. The default hold time is 15 seconds, which is 3 times the hello interval. |
For low-speed NBMA networks: 180 seconds
For all other networks: 15 seconds
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example changes the hold time to 45 seconds:
interface ethernet 0 ipx network 10 ipx hold-time eigrp 4 45
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| access-list-number | Number of the access list. All incoming packets defined with either standard or extended access lists are filtered by the entries in this access list. For standard access lists, access-list-number is a decimal number from 800 to 899. For extended access lists, it is a decimal number from 900 to 999. |
No filters are predefined.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
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 1b interface ethernet 1 ipx input-network-filter 876
The 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 -1
access-list (extended)
access-list (standard)
ipx output-network-filter
ipx router-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| access-list-number | Number of the SAP access list. All incoming packets are filtered by the entries in this access list. The argument access-list-number is a decimal number from 1000 to 1099. |
No filters are predefined.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
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.1527 access-list 1000 permit -1 interface ethernet 0 ipx input-sap-filter 1000
access-list (SAP filtering)
ipx output-sap-filter
ipx router-sap-filter
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| network-number | Number of the internal network. |
No internal network number is set.
Global configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example assigns internal network number e001 to the local router:
ipx routing ipx internal-network e001
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| 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. |
IPXWAN is disabled.
If you enable IPXWAN, the default is unnumbered.
Interface configuration
This command first appeared in Cisco IOS Release 10.0. The unnumbered keyword and retry-interval argument first appeared in Cisco IOS Release 10.3.
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.
The following example enables IPXWAN on serial interface 0:
interface serial 0 encapsulation ppp ipx ipxwan
The 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 1 no ipx network encapsulation ppp ipx ipxwan 6666 100 CHICAGO-AS
On the remote router (NYC-AS):
interface serial 0 no ipx network encapsulation ppp ipx ipxwan 1000 101 NYC-AS
A dagger (+) indicates that the command is documented outside this chapter.
encapsulation ppp +
hostname +
ipx delay
ipx internal-network
ipx ipxwan error
ipx ipxwan static
ipx network
show ipx interface
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]| reset | (Optional) Resets the link when negotiations fail. This is the default action. |
| resume | (Optional) When negotiations fail, IPXWAN ignores the failure, takes no special action, and resumes the start-up negotiation attempt. |
| shutdown | (Optional) Shuts down the link when negotiations fail. |
The link is reset.
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
Use the ipx ipxwan error command to define what action to take if the IPXWAN startup negotiation fails.
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 0 encapsulation ppp ipx ipxwan ipx ipxwan error shutdown
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 staticThis command has no arguments or keywords.
Static routing is disabled.
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example enables static routing with IPXWAN:
interface serial 0 encapsulation ppp ipx ipxwan ipx ipxwan static
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| microseconds | Delay, in microseconds. |
No link delay (delay of 0)
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example sets the link delay to 20 microseconds:
ipx link-delay 20
To set the maximum hop count allowed for IPX packets, use the ipx maximum-hop global configuration command. To return to the default number of hops, use the no form of this command.
ipx maximum-hops hops| hops | Maximum number of hops considered to be reachable by non-RIP routing protocols. Also, maximum number of routers that an IPX packet can traverse before being dropped. It can be a value from 16 to 254. The default is 16 hops. |
16 hops
Global configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following command configures the software to accept routes that are up to 64 hops away:
ipx maximum-hops 64
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| paths | Maximum number of equal-cost paths which the Cisco IOS software will use. It can be an integer from 1 to 512. The default value is 1. |
1 path
Global configuration
This command first appeared in Cisco IOS Release 10.0.
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.
In the following example, the software uses up to three parallel paths:
ipx maximum-paths 3
ipx delay
ipx per-host-load-share
show ipx route
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| host | Indicates that the following argument is the name of a NetBIOS access filter previously defined with one or more netbios access-list host commands. |
| bytes | Indicates that the following argument is the name of a NetBIOS access filter previously defined with one or more netbios access-list bytes commands. |
| name | Name of a NetBIOS access list. |
No filters are predefined.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example filters packets arriving on Token Ring interface 1 using the NetBIOS access list engineering:
netbios access-list host engineering permit eng* netbios access-list host engineering deny manu* interface tokenring 1 ipx netbios input-access-filter engineering
ipx netbios output-access-filter
netbios access-list
show ipx interface
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| host | Indicates that the following argument is the name of a NetBIOS access filter previously defined with one or more netbios access-list host commands. |
| bytes | Indicates that the following argument is the name of a NetBIOS access filter previously defined with one or more netbios access-list bytes commands. |
| name | Name of a previously defined NetBIOS access list. |
No filters are predefined.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example filters packets leaving Token Ring interface 1 using the NetBIOS access list engineering:
netbios access-list bytes engineering permit 20 AA**04 interface token 1 ipx netbios output-access-filter bytes engineering
ipx netbios input-access-filter
netbios access-list
show ipx interface
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]]IPX routing is disabled.
Encapsulation types:
For Ethernet: novell-ether
For Token Ring: sap
For FDDI: snap
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
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.
NLSP does not support secondary networks. You must use subinterfaces in order to use multiple encapsulations with NLSP.
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 networkDeleting 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 numberTo 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 numberNovell'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.
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 routing interface ethernet 0 interface ethernet 0.1 ipx network 1 encapsulation novell-ether interface ethernet 0.2 ipx network 2 encapsulation snap interface ethernet 0.3 ipx network 3 encapsulation arpa interface ethernet 0.4 ipx network 4 encapsulation sap
The 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 routing ipx network 1 encapsulation novell-ether ipx network 2 encapsulation snap secondary ipx network 3 encapsulation arpa secondary ipx network 4 encapsulation sap secondary
The following example enables IPX routing on a 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 routing interface fddi 0.2 ipx network f02 encapsulation snap interface fddi 0.3 ipx network f03 encapsulation novell-fddi
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| 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. |
No authentication string is configured; the Cisco IOS software adds no authentication option to NHRP packets it generates.
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
All routers configured with NHRP on a fabric (for an interface) must share the same authentication string.
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 specialxx
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]| seconds-positive | Time in seconds that NBMA addresses are advertised as valid in positive authoritative NHRP responses. |
| seconds-negative | (Optional) Time in seconds that NBMA addresses are advertised as valid in negative authoritative NHRP responses. |
7200 seconds (2 hours) for both arguments
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
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.
In the following example, NHRP NBMA addresses are advertised as valid in positive authoritative NHRP responses for one hour:
ipx nhrp holdtime 3600
In the following example, NHRP NBMA addresses are advertised as valid in negative authoritative NHRP responses for one hour and in positive authoritative NHRP responses for two hours:
ipx nhrp holdtime 7200 3600
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| access-list-number | Standard or extended IPX access list number from 800 through 999. |
All non-NHRP packets can trigger NHRP requests.
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
Use this command with the access-list command to control which IPX packets trigger NHRP Requests.
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 901 access-list 901 permit 20
access-list (extended)
access-list (standard)
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| ipx-address | IPX address of the destinations reachable through the NBMA network. This address is mapped to the NBMA address. |
| nbma-address | NBMA address that is directly reachable through the NBMA network. The address format varies depending on the medium you are using. For example, ATM has a network-service access point (NSAP) address, and SMDS has an E.164 address. This address is mapped to the IPX address. |
No static IPX-to-NBMA cache entries exist.
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
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.
In the following example, this station in an SMDS network is statically configured 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 0 ipx nhrp nhs 1.0000.0c14.59ef ipx nhrp nhs 1.0000.0c14.59d0 ipx nhrp map 1.0000.0c14.59ef c141.0001.0001 ipx nhrp map 1.0000.0c14.59d0 c141.0001.0002
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| pkt-count | Number of packets which can be transmitted in the range 1 to 65,535. |
| interval | Time (in seconds) in the range 10 to 65,535. |
pkt-count = 5 packets
interval = 10 seconds
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
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.
In the following example, only 1 NHRP packet can be sent out serial interface 0 each minute:
interface serial 0 ipx nhrp max-send 1 every 60
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| number | Globally unique, 32-bit network identifier for a nonbroadcast, multiaccess (NBMA) network. The range is 1 to 4294967295. |
NHRP is disabled on the interface.
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
In general, all NHRP stations within a fabric must be configured with the same network identifier.
The following example enables NHRP on the interface:
ipx nhrp network-id 1
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]| nhs-address | Address of the Next Hop Server being specified. |
| net-address | (Optional) IPX address of a network served by the Next Hop Server. |
No Next Hop Servers are explicitly configured, so normal network layer routing decisions forward NHRP traffic.
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
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.
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 2
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 recordThis command has no arguments or keywords.
Forward record and reverse record options are enabled by default.
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
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.
The following example suppresses forward record and reverse record options:
no ipx nhrp record
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| type | Interface type whose primary IPX address is used when a Next Hop Server complies with a Responder Address option. Valid options are atm, serial, and tunnel. |
| number | Interface number whose primary IPX address is used when a Next Hop Server complies with a Responder Address option. |
The Next Hop Server uses the IPX address of the interface where the NHRP Request was received.
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
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.
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 0
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| usage-count | Packet count in the range 1 to 65535. |
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.
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
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.
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 5
ipx nhrp interest
ipx nhrp max-send
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| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
| seconds | Time, in seconds, between the transmission of CSNPs on multiaccess networks. This interval applies to the designated router only. The interval can be a number in the range 1 to 600. The default is 30 seconds. |
30 seconds
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example configures Ethernet interface 0 to transmit CSNPs every 10 seconds:
interface ethernet 0 ipx network 101 ipx nlsp enable ipx nlsp csnp-interval 10
ipx nlsp hello-interval
ipx nlsp retransmit-interval
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| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
NLSP is disabled on all interfaces.
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example enables NLSP routing on Ethernet interface 0:
interface ethernet 0 ipx nlsp enable
The following example enables NLSP routing on serial interface 0:
interface serial 0 ipx ipxwan 2442 unnumbered local1 ipx nlsp enable
The following example enables NLSP routing for process area3 on Ethernet interface 0:
interface ethernet 0 ipx nlsp area3 enable
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| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
| seconds | Time, in seconds, between the transmission of hello packets on the interface. It can be a decimal integer in the range 1 to 1600. The default is 10 seconds for the designated router and 20 seconds for nondesignated routers. |
10 seconds for the designated router
20 seconds for nondesignated routers
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example configures serial interface 0 to transmit hello packets every 30 seconds:
interface serial 0 ipx ipxwan 2442 unnumbered local1 ipx nlsp enable ipx nlsp hello-interval 30
ipx nlsp csnp-interval
ipx nlsp hello-multiplier
ipx nlsp retransmit-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 lsp-interval interval| interval | Time, in milliseconds, between successive LSP transmissions. The interval can be a number in the range 55 and 5000. The default interval is 55 milliseconds. |
55 milliseconds
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
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).
The following example causes the system to transmit LSPs every 100 milliseconds (10 packets per second) on Ethernet interface 0:
interface Ethernet 0 ipx nlsp lsp-interval 100
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| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
| multiplier | Value by which to multiply the hello interval. It can be a decimal integer in the range 3 to 1000. The default is 3. |
The default multiplier is 3.
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
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.
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 0 ipx nlsp hello-interval 15 ipx nlsp hello-multiplier 5
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| 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 decimal integer from 0 to 63. |
The default varies based on the throughput of the link connected to the interface.
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example configures a metric of 10 on serial interface 0:
interface serial 0 ipx network 107 ipx nlsp enable ipx nlsp metric 10
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| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
| priority-number | Election priority of the designated router for the specified interface. This can be a number in the range 0 to 127. This value is unitless. The default is 44. |
44
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example sets the designated router election priority to 65:
interface e 0 ipx network 101 ipx nlsp enable ipx nlsp priority 65
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| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
| seconds | LSP retransmission interval, in seconds. This can be a number in the range 1 to 30. The default is 5 seconds. |
5 seconds
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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 acknowledgement 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.
The following example configures the LSP retransmission interval to 2 seconds:
ipx nlsp retransmit-interval 2
ipx nlsp csnp-interval
ipx nlsp hello-interval
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]| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
| on | (Optional) Always generates and sends RIP periodic traffic. |
| off | (Optional) Never generates and sends RIP periodic traffic. |
| auto | (Optional) Sends RIP periodic traffic only if another RIP router in sending periodic RIP traffic. This is the default. |
RIP periodic traffic is sent only if another router in sending periodic RIP traffic.
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
In the following example, the interface never generates or sends RIP periodic traffic:
interface ethernet 0 ipx nlsp rip off
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]| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
| on | (Optional) Always generates and sends SAP periodic traffic. |
| off | (Optional) Never generates and sends SAP periodic traffic. |
| auto | (Optional) Sends SAP periodic traffic only if another SAP router in sending periodic SAP traffic. This is the default. |
SAP periodic traffic is sent only if another router in sending periodic SAP traffic.
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
In the following example, the interface never generates or sends SAP periodic traffic:
interface ethernet 0 ipx nlsp sap off
To control which servers are included in the Get Nearest 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| access-list-number | Number of the SAP access list. All outgoing GNS packets are filtered by the entries in this access list. The argument access-list-number is a decimal number from 1000 to 1099. |
No filters are predefined.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
You can issue only one ipx output-gns-filter command on each interface.
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.1527 access-list 1000 permit -1 ipx routing interface ethernet 0 ipx network 2B ipx output-gns-filter 1000
access-list (SAP filtering)
ipx gns-round-robin
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| access-list-number | Number of the access list. All outgoing packets defined with either standard or extended access lists are filtered by the entries in this access list. For standard access lists, access-list-number is a decimal number from 800 to 899. For extended access lists, it is a decimal number from 900 to 999. |
No filters are predefined.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
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 2b interface serial 1 ipx output-network-filter 896
access-list (extended)
access-list (standard)
ipx input-network-filter
ipx router-filter
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| 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. |
55 ms
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example establishes a 55-ms interpacket delay on serial interface 0:
interface serial 0 ipx network 106A ipx output-rip-delay 55
ipx default-output-rip-delay
ipx default-triggered-rip-delay
ipx triggered-rip-delay
ipx update-time
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| 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. |
55 ms
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example establishes a 55-ms delay between packets in multiple-packet SAP updates on Ethernet interface 0:
interface ethernet 0 ipx network 106A ipx output-sap-delay 55
ipx default-output-sap-delay
ipx default-triggered-sap-delay
ipx sap-interval
ipx triggered-sap-delay
To control which services are included in SAP updates sent by the Cisco IOS software, use the ipx output-network-filter interface configuration command. To remove the filter, use the no form of this command.
ipx output-sap-filter access-list-number| access-list-number | Number of the SAP access list. All outgoing service advertisements are filtered by the entries in this access list. The argument access-list-number is a decimal number from 1000 to 1099. |
No filters are predefined.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example denies service advertisements about server 0000.0000.0001 on network aa from being send 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.0001 access-list 1000 permit -1 interface ethernet 0 ipx net 3c interface ethernet 1 ipx network 4d ipx output-sap-filter 1000 interface serial 0 ipx network 2b
access-list (SAP filtering)
ipx gns-round-robin
ipx input-sap-filter
ipx router-sap-filter
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-packetsThis command has no arguments or keywords.
Enabled on Ethernet interfaces
Disabled on Token Ring, FDDI, and serial interfaces
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following command 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 1 ipx network 2A no ipx route-cache ipx pad-process-switched-packets
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-shareThis command has no arguments or keywords.
Disabled
Global configuration
This command first appeared in Cisco IOS Release 11.1.
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.
The following command globally enables per-host load sharing:
ipx per-host-load share
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}| cisco | Transmits Cisco pings. |
| novell | Transmits standard Novell pings. |
Cisco pings
Global configuration
This command first appeared in Cisco IOS Release 10.3.
Standard Novell pings conform to the definition in the Novell NLSP specification.
The following example enables standard Novell pings:
ipx ping-default novell
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| 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. |
432 bytes
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example sets the maximum RIP update packet to 832 bytes:
ipx rip-max-packetsize 832
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| multiplier | Multiplier used to calculate the interval at which to age out RIP routing table entries. This can be any positive integer. The value you specify is multiplied by the RIP update interval to determine the aging-out interval. The default is three times the RIP update interval. |
Three times the RIP update interval
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
All routers on the same physical cable should use the same multiplier value.
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 0 ipx rip-multiplier 5
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} [floating-static]| network | Network to which you want to establish a static route.
This 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. |
| network-mask | (Optional) Specifies the portion of the network address that is common to all addresses in an NLSP route summary. When used with the network argument, it specifies the static route summary.
The high-order bits of network-mask must be contiguous Fs, while the low-order bits must be contiguous zeros (0). An arbitrary mix of Fs and 0s is not permitted. |
| default | Creates a static entry for the "default route." The router forwards all nonlocal packets for which no explicit route is known via the specified next hop address (network.node) or interface. |
| network.node | Router to which to forward packets destined for the specified network.
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 router. This is a 48-bit value represented by a dotted triplet of four-digit hexadecimal numbers (xxxx.xxxx.xxxx). |
| interface | Network interface to which to forward packets destined for the specified network. Interface is serial 0 or serial 0.2. Specifying an interface instead of a network node is intended for use on IPXWAN unnumbered interfaces. The specified interface can be a null interface. |
| floating-static | (Optional) Specifies that this route is a floating static route, which is a static route that can be overridden by a dynamically learned route. |
No static routes are predefined.
Global configuration
This command first appeared in Cisco IOS Release 10.0. The following arguments and keywords first appeared in Cisco IOS 10.3: network-mask, default, interface, floating-static.
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.
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.1ac9
The following example defines a static NLSP route summary:
ipx routing ipx route aaaa0000 ffff0000
ipx default-route
show ipx route
To enable IPX fast switching and autonomous switching, use the ipx route-cache interface configuration command. To disable fast switching, use the no form of this command.
ipx route-cache [cbus | sse]| cbus | (Optional) Enables IPX autonomous switching. |
| sse | (Optional) Enables SSE fast switching. |
Fast switching is enabled.
Autonomous switching is disabled.
SSE switching is disabled.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Specifying the ipx route-cache command with no keywords enables fast switching.
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.
Autonomous switching provides faster packet switching by allowing the ciscoBus processor to switch packets independently without having to interrupt the system processor. It is available only in Cisco 7000 systems.
Autonomous switching is supported to and from all encapsulation types that you can use on IEEE interfaces; it is also supported to and from serial HDLC encapsulation. Table 48 lists the encapsulation types you can use on IEEE interfaces and shows the correspondence between the encapsulation type and the IPX frame type.
SSE fast switching uses the silicon switching engine (SSE) on the Cisco 7000 series SSP card to perform packet switching.
The following example enables fast switching and autonomous switching on an interface:
interface ethernet 0 ipx route-cache cbus
The following example enables fast switching and SSE fast switching on an interface:
interface ethernet 0/1 ipx route-cache sse
In the following example, both fast switching and autonomous switching are turned off on an interface:
interface ethernet 0 no ipx route-cache
Assuming that Ethernet 0 has ipx route-cache and ipx route-cache cbus is enabled, the following example turns off only autonomous switching on an interface, but leaves fast switching enabled:
interface ethernet 0 no ipx route-cache cbus
clear ipx cache
ipx source-network-update
ipx watchdog-spoof
show ipx cache
show ipx interface
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]| period | Number of minutes that a valid cache entry may be inactive before it is invalidated. Valid values are 0 through 65535. A value of zero disables this feature. |
| rate | The maximum number of inactive entries that may be invalidated per minute. Valid values are 0 through 65535. A value of zero means no limit. |
The default period is 2 minutes. The default rate is 0 (unlimited invalidations).
Global configuration
This command first appeared in Cisco IOS Release 11.2.
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.
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 10
clear ipx cache
ipx route-cache
ipx route-cache update-timeout
show ipx cache
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| size | Maximum number of entries allowed in the IPX route cache. |
The default setting is no limit on the number of entries.
Global configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example sets the maximum route cache size to 10,000 entries.
ipx route-cache max-size 10000
ipx route-cache
ipx route-cache inactivity-timeout
ipx route-cache update-timeout
show ipx cache
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]| period | Number of minutes since a valid cache entry was created before it may be invalidated. A value of zero disables this feature. |
| rate | The maximum number of aged entries that may be invalidated per minute. A value of zero means no limit. |
The default setting is disabled.
Global configuration
This command first appeared in Cisco IOS Release 11.2.
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 or silicon switch processor. 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.
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 10
clear ipx cache
ipx route-cache
ipx route-cache inactivity-timeout
show ipx cache
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}RIP is enabled.
Global configuration
This command first appeared in Cisco IOS Release 10.0. The nlsp keyword and tag argument first appeared in Cisco IOS Release 11.0.
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.
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.
The following example enables Enhanced IGRP:
ipx router eigrp 4
The following example enables NLSP on process area1. This process handles routing for NLSP area 1.
ipx router nlsp area1
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| access-list-number | Number of the access list. All incoming packets defined with either standard or extended access lists are filtered by the entries in this access list. For standard access lists, access-list-number is a decimal number from 800 to 899. For extended access lists, it is a decimal number from 900 to 999. |
No filters are predefined.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
You can issue only one ipx router-filter command on each interface.
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.047d interface ethernet 0 ipx router-filter 866
access-list (extended)
access-list (standard)
ipx input-network-filter
ipx output-network-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| access-list-number | Number of the access list. All incoming service advertisements are filtered by the entries in this access list. The argument access-list-number is a decimal number from 1000 to 1099. |
No filters are predefined.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
You can issue only one ipx router-sap-filter command on each interface.
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.0874 access-list 1000 deny -1 interface ethernet 0 ipx router-sap-filter 1000
access-list (SAP filtering)
ipx input-sap-filter
ipx output-sap-filter
ipx sap
show ipx interface
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]| node | (Optional) Node number of the router. This is a 48-bit value represented by a dotted triplet of four-digit hexadecimal numbers (xxxx.xxxx.xxxx). It must not be a multicast address.
If you omit node, the Cisco IOS software uses the hardware MAC address currently assigned to it as its node address. This is the MAC address of the first Ethernet, Token Ring, or FDDI interface card. If no satisfactory interfaces are present in the router (such as only serial interfaces), you must specify node. |
Disabled
Global configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example enables IPX routing:
ipx routing
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| service-type | SAP service-type number. Table 47 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. Table 45 earlier in this chapter lists some IPX socket numbers. |
| hop-count | Number of hops to the server. |
Disabled
Global configuration
This command first appeared in Cisco IOS Release 10.0.
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.
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 1 ipx sap 4 FILESERV 165.0000.0c01.3d1b 451 1 ipx sap 143 JOES_SERVER A1.0000.0c01.1234 8170 2 no route to A1, JOES_SERVER won't be announced until route is learned
ipx input-sap-filter
ipx output-sap-filter
ipx router-sap-filter
show ipx servers
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]| eigrp autonomous-system-number | IPX Enhanced IGRP autonomous system number. It can be a decimal integer from 1 to 65535. |
| rsup-only | (Optional) Indicates that the system uses Enhanced IGRP on this interface to carry reliable SAP update information only. RIP routing updates are used, and Enhanced IGRP routing updates are ignored. |
Enabled on serial interfaces
Disabled on LAN media (Ethernet, Token Ring, FDDI)
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example sends SAP updates on Ethernet interface 0 only when there is a change in the SAP table:
interface ethernet 0 ipx sap-incremental eigrp 200
To configure less frequent Service Advertising Protocol (SAP) updates over slow links, use the ipx sap-interval interface configuration command. To return to the default value, use the no form of this command.
ipx sap-interval interval| interval | Interval, in minutes, between SAP updates sent by the Cisco IOS software. The default value is 1 minute. If interval is 0, periodic updates are never sent. |
1 minute
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Setting the interval at which SAP updates are sent is most useful on limited-bandwidth, point-to-point links, or on X.25 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.
Setting the interval to zero means that periodic SAP updates are never sent. It is recommended that you never do this. If you set the interval to zero, routers that are inaccessible for any reason when a server powers up or shuts down will miss that event, and will either fail to learn about new servers or fail to detect that the server shut down.
In the following example, SAP updates are sent (and expected) on serial interface 0 every 5 minutes:
interface serial 0 ipx sap-interval 5
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| 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. |
480 bytes
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example sets the maximum SAP update packet size to 672 bytes:
ipx sap-max-packetsize 672
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| multiplier | Multiplier used to calculate the interval at which to age out SAP routing table entries. This can be any positive integer. The value you specify is multiplied by the SAP update interval to determine the aging-out interval. The default is three times the SAP update interval. |
Three times the SAP update interval.
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
All routers on the same physical cable should use the same multiplier value.
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 0 ipx sap-multiplier 10
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| 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. |
No maximum queue size
Global configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example sets the length of the queue of pending SAP requests to 20:
ipx sap-queue-maximum 20
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-updateThis command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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 The ipx source-network-update command interferes with the proper working of OS/2 Requestors. Do not use this command in a network that has OS/2 Requestors. |
| Caution Do not use the ipx source-network-update command on interfaces on which NetWare (NetWare 3.1x or 4.0 or later) servers are using internal network numbers. |
In the following example, corrupted network numbers on serial interface 0 are repaired:
interface serial 0 no ipx route-cache ipx source-network-update
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| autonomous-system-number | Enhanced IGRP autonomous system number. It can be a decimal integer from 1 to 65535. |
Enabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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 a router out any interface from which that information originated. This behavior usually optimizes communication among multiple routers, particularly when links are broken. However, with nonbroadcast networks, such as Frame Relay and SMDS, situations can arise for which this behavior is less than ideal. For these situations, you may wish to disable split horizon.
The following example disables split horizon on serial interface 0:
interface serial 0 no ipx split-horizon eigrp 200
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| delay-in-seconds | The amount of time in seconds to wait before spoofing SPX keepalives after data transfer has stopped. |
60 seconds
Interface configuration
This command first appeared in Cisco IOS Release 11.0.
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.
The following example enables spoofing on serial interface 0 and sets the idle timer to 300 seconds:
interface serial 0 ipx spx-spoof no ipx route-cache ipx spx-idle-time 300
ipx spx-spoof
show 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-spoofThis command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 11.0.
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-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.
The following example enables spoofing on serial interface 0:
interface serial 0 ipx spx-spoof no ipx route-cache
ipx throughput
show ipx spx-spoof
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| bits-per-second | Throughput, in bits per second. |
Current bandwidth setting for the interface
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example changes the throughput to 1,000,000 bits per second:
ipx throughput 1000000
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| 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. |
55 ms
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
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 "Default" section.
This command is also useful on limited bandwidth point-to-point links, or X.25 and Frame Relay multipoint interfaces.
The following example sets an interpacket delay of 55 ms for triggered routing updates sent on interface FDDI 0:
int FDDI 0 ipx triggered-rip-delay 55
ipx default-output-rip-delay
ipx default-triggered-rip-delay
ipx output-rip-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| 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. |
55 ms
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
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 "Default" section.
This command is also useful on limited bandwidth point-to-point links, or X.25 and Frame Relay multipoint interfaces.
The following example sets an interpacket delay of 55 ms for triggered SAP updates sent on interface FDDI 0:
int FDDI 0 ipx triggered-sap-delay 55
ipx default-output-sap-delay
ipx default-triggered-sap-delay
ipx output-sap-delay
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-helperedThis command has no arguments or keywords.
Disabled
Global configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example forwards IPX type 20 propagation packet broadcasts to specific network segments:
interface ethernet 0 ipx network aa ipx type-20-helpered ipx helper-address bb.ffff.ffff.ffff
ipx helper-address
ipx type-20-propagation
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-checksThis command has no arguments or keywords.
Disabled
Global configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example imposes additional restrictions on incoming type 20 broadcasts:
ipx type-20-input-checks
ipx type-20-output-checks
ipx type-20-propagation
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-checksThis command has no arguments or keywords.
Disabled
Global configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example imposes restrictions on outgoing type 20 broadcasts:
ipx type-20-output-checks
ipx type-20-input-checks
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-propagationThis command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example enables both the reception and forwarding of type 20 broadcasts on Ethernet interface 0:
interface ethernet 0 ipx type-20-propagation
The 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 0 ipx network 123 ipx type-20-propagation ! interface ethernet 1 ipx network 456 ipx type-20-propagation ! interface ethernet 2 ipx network 789
ipx helper-list
ipx type-20-input-checks
ipx type-20-output-checks
To adjust the IPX routing update timers, use the ipx update-time interface configuration command. To restore the default value, use the no form of this command.
ipx update-time interval| interval | Interval, in seconds, at which IPX routing updates are sent. The default is 60 seconds. The minimum interval is 10 seconds. |
60 seconds
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The ipx update-time command sets the routing update timer on a per-interface basis.
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-time command enables you to modify the periodic update interval. By default, this interval is 60 seconds (this default is defined by Novell).
You can set RIP timers only in a configuration in which all routers are our routers or in which the IPX routers allow configurable timers. The timers should be the same for all devices connected to the same cable segment.
The update value you choose affects the internal IPX timers as follows:
The concept of granularity is best explained by an example. (This example is illustrated in the "Example" section following.) If you have two interfaces in the device and you set the update timer on one to 20 seconds and the second to 30 seconds, the software wakes up every 20 seconds to try to send routing updates. So, at time 0:00:20, the software sends an update out the first interface only, and at time 0:00:40 it sends updates out the first and second interfaces. The software does not wake up at 0:00:30 to see if it needs to send an update out the second interface. This means that routing updates are sent out the second interface at N:NN:40 and N:NN:00. That is, the interval alternates between 40 seconds and 20 seconds; it is never 30 seconds. The interval on the first interface is always 20 seconds.
The following example sets the update timers on two interfaces in a router. The update timer granularity would be 20 seconds because this is the lowest value specified.
interface serial 0 ipx update-time 40 interface ethernet 0 ipx update-time 20
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-spoofThis command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
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."
The following example enables spoofing on serial interface 0:
interface serial 0 ipx watchdog-spoof no ipx route-cache
To generate a log message when an NLSP adjacency changes state (up or down), use the log-adjacency-changes router configuration command. Use the no form of this command to disable this function.
log-adjacency-changesThis command has no arguments or keywords.
Adjacency changes are not logged.
Router configuration
This command first appeared in Cisco IOS Release 11.1.
This command allows the monitoring of NLSP adjacency state changes. This may 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
The following example instructs the router to log adjacency changes for the NLSP process area1:
ipx router nlsp area1log-adjacency-changes
A dagger (+) indicates that the command is documented outside this chapter.
logging+
To enable the logging of changes in Enhanced IGRP neighbor adjacencies, use the log-neighbor-changes router configuration command.
log-neighbor-changesThis command has no arguments or keywords.
No adjacency changes are logged.
Router configuration
This command first appeared in Cisco IOS Release 11.2.
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
where the following is true:
| as-number | Autonomous system number |
| address | Neighbor address |
| State | Up or down |
| reason | Reason for change |
The following configuration will log neighbor changes for Enhanced IGRP process 209:
ipx router eigrp 209 log-neighbor-changes
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| seconds | Minimum interval, in seconds. It can be a number in the range 0 to 120. The default is 5 seconds. |
5 seconds
Router configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example sets the minimum interval at which LSPs are generated to 10 seconds:
lsp-gen-interval 10
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| bytes | MTU size, in bytes. It can be a decimal number in the range 512 to 4096. The default is 512 bytes. |
512 bytes
Router configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example sets the maximum LSP size to 1500 bytes:
lsp-mtu 1500
ipx router nlsp
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| seconds | Refresh interval, in seconds. It can be a value in the range 1 to 50000 seconds. The default is 7200 seconds (2 hours). |
7,200 seconds (2 hours)
Router configuration
This command first appeared in Cisco IOS Release 10.3.
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 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).
The following example changes the LSP refresh interval to 10,800 seconds (3 hours):
lsp-refresh-interval 10800
ipx router nlsp
max-lsp-lifetime
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 seconds| seconds | Lifetime of LSP, in seconds. It can be a number in the range 1 to 50000 seconds. The default is 7500 seconds. |
7500 seconds (2 hours, 5 minutes)
Router configuration
This command first appeared in Cisco IOS Release 10.3.
You might need to adjust the maximum LSP lifetime if you change the LSP refresh interval with the lsp-refresh-interval router configuration command. The maximum LSP lifetime must be greater than the LSP refresh interval.
The following example sets the maximum time that the LSP persists to 11,000 seconds (more than 3 hours):
max-lsp-lifetime 11000
ipx router nlsp
lsp-refresh-interval
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| host | Indicates that the following argument is the name of a NetBIOS access filter previously defined with one or more netbios access-list host commands. |
| bytes | Indicates that the following argument is the name of a NetBIOS access filter previously defined with one or more netbios access-list bytes commands. |
| name | Name of the access list being defined. The name can be an alphanumeric string. |
| deny | Denies access if the conditions are matched. |
| permit | Permits access if the conditions are matched. |
| string | Character string that identifies one or more NetBIOS host names. It can be up to 14 characters long. The argument string can include the following wildcard characters:
· *--Match one or more characters. You can use this wildcard character only at the end of a string. · ?--Match any single character. |
| offset | Decimal number that indicates the number of bytes into the packet at which the byte comparison should begin. An offset of 0 indicates the beginning of the NetBIOS packet header, which is at the end of the IPX header. |
| byte-pattern | Hexadecimal pattern that represents the byte pattern to match. It can be up to 16 bytes (32 digits) long and must be an even number of digits. The argument byte-pattern can include the double asterisk (**) wildcard character to match any digits for that byte. |
No filters are predefined.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
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} nameTo delete a single entry from the list, use the following command:
no netbios access-list host name {permit | deny} stringThe following example defines the IPX NetBIOS access list engineering:
netbios access-list host engineering permit eng-ws1 eng-ws2 eng-ws3
The following example removes a single entry from the engineering access list:
netbios access-list host engineering deny eng-ws3
The following example removes the entire engineering NetBIOS access list:
no netbios access-list host engineering
ipx netbios input-access-filter
ipx netbios output-access-filter
show ipx interface
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}| network-number | IPX network number. |
| all | Enables the routing protocol for all IPX networks configured on the router. |
Disabled
Router configuration
This command first appeared in Cisco IOS Release 10.3.
Use the network command to enable the routing protocol specified in the ipx router command on each network.
The following commands disable RIP on network 10 and enable Enhanced IGRP on networks 10 and 20:
ipx router rip no network 10 ipx router eigrp 12 network 10 network 20
To check host reachability and network connectivity, use the ping privileged EXEC command.
ping [ipx] [network.node]| ipx | (Optional) Specifies the IPX protocol. |
| network.node | (Optional) Address of the system to ping. |
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
The privileged ping (IPX echo) command provides a complete ping facility for users who have system privileges.
The ping command with ipx ping-default set to Cisco works only on our routers running Software Release 8.2 or later.
Novell IPX devices that support the echo function defined in version 1.0 of the NLSP specification will respond to this command if you answer Y to the prompt Novell Standard Echo that is displayed when you use the privileged ping command or if ipx ping-default is set to Novell. If you answer N to this prompt, Novell IPX devices will not respond.
To abort a ping session, type the escape sequence. By default, this is Ctrl-^ X. You enter this by simultaneously pressing the Ctrl, Shift, and 6 keys, letting go, and then pressing the X key.
Table 49 describes the test characters displayed in ping responses.
| Character | Meaning |
|---|---|
| ! | Each exclamation point indicates the receipt of a reply from the target address. |
| . | Each period indicates the network server timed out while waiting for a reply from the target address. |
| U | A destination unreachable error PDU was received. |
| C | A congestion experienced packet was received. |
| I | User interrupted the test. |
| ? | Unknown packet type. |
| & | Packet lifetime exceeded. |
The following sample display shows input to and output from the ping command:
Router#pingProtocol [ip]:ipxTarget IPX address: 211.0000.0c01.f4cf Repeat count [5]: Datagram size [100]: Timeout in seconds [2]: Verbose [n]: Novell Standard Echo [n]: Type escape sequence to abort. Sending 5 100-byte IPX echoes to 211.0000.0c01.f4cf, timeout is 2 seconds. !!!!! Success rate is 100 percent (0/5)
To check host reachability and network connectivity, use the ping user EXEC command.
ping ipx {host | address}| ipx | Specifies the IPX protocol. |
| host | Host name of system to ping. |
| address | Address of system to ping. |
User EXEC
This command first appeared in Cisco IOS Release 10.0.
The user-level ping (packet internet groper function) command provides a basic ping facility for users who do not have system privileges. This command is equivalent to the nonverbose form of the privileged ping command. It sends five 100-byte ping packets.
The ping command with ipx ping-default set to Cisco works only on our routers running Cisco IOS software Release 8.2 or later. Novell IPX devices will not respond to this command.
You cannot ping a device from itself except on Cisco 7000 systems.
If the system cannot map an address for a host name, it will return an "%Unrecognized host or address" error message.
To abort a ping session, type the escape sequence. By default, this is Ctrl-^ X. You enter this by simultaneously pressing the Ctrl, Shift, and 6 keys, letting go, and then pressing the X key.
Table 49 in the ping (privileged) command section describes the test characters displayed in ping responses.
The following sample display shows input to and output from the user ping command:
Router> ping ipx 211.0000.0c01.f4cf Type escape sequence to abort. Sending 5, 100-byte Novell Echoes to 211.0000.0c01.f4cf, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
ipx ping-default
ping (privileged)
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| 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. |
5 seconds
Router configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example sets the PRC calculation interval to 20 seconds:
prc-interval 20
To redistribute from one routing domain into another, and vice versa, use one of the following redistribute router configuration command. 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] | ripFor 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}| connected | Specifies connected routes. |
| eigrp autonomous-system-number | Specifies the Enhanced IGRP protocol and the Enhanced IGRP autonomous system number. It can be a decimal integer from 1 to 65535. |
| floating-static | Specifies a floating static route. This is a static route that can be overridden by a dynamically learned route. |
| nlsp [tag] | Specifies the NLSP protocol and, optionally, names the NLSP process (tag). The tag can be any combination of printable characters. |
| rip | Specifies the RIP protocol. You can configure only one RIP process on the router. Thus, you cannot redistribute RIP into RIP. |
| static | Specifies static routes. |
| access-list access-list-number | Specifies an NLSP route summary access list. The access-list-number is a decimal number from 1200 to 1299. |
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.
Router configuration
This command first appeared in Cisco IOS Release 11.1.
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
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.
In the following example, RIP routing information is not redistributed:
ipx router eigrp 222 no redistribute rip
In the following example, Enhanced IGRP routes from autonomous system 100 are redistributed into Enhanced IGRP autonomous system 300:
ipx router eigrp 300 redistribute eigrp 100
In the following example, Enhanced IGRP routes from autonomous system 300 are redistributed into the NLSP process area3:
ipx router nlsp area3 redistribute eigrp 300
The 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 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 -1 access-list 1201 deny bbbb0000 ffff0000 access-list 1201 permit -1 ! ipx router nlsp a1 area-address 1000 fffff000 route-aggregation redistribute nlsp a2 access-list 1201 ! ipx router nlsp a2 area-address 2000 fffff000 route-aggregation redistribute nlsp a1 access-list 1200
access-list (NLSP route aggregation filtering)
ipx router
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-aggregationThis command has no arguments or keywords.
Route summarization is disabled by default.
Router configuration
This command first appeared in Cisco IOS Release 11.1.
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.
The following example enables route summarization between two NLSP areas. Route summarization is based on the area addresses configured for each area.
ipx routing ipx internal-network 123 ! int e 1 ipx nlsp area1 enable ! int e 2 ipx nlsp area2 enable ! ipx router nlsp area1 area-address 1000 fffff000 route-aggregation ! ipx router nlsp area2 area-address 2000 fffff000 route-aggregation
To display the active accounting or checkpointed database, use the show ipx accounting EXEC command.
show ipx accounting [checkpoint]| checkpoint | (Optional) Displays entries in the checkpointed database should be displayed. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show ipx accounting command:
Router# show ipx accounting
Source Destination Packets Bytes
0000C003.0000.0c05.6030 0000C003.0260.8c9b.4e33 72 2880
0000C001.0260.8c8d.da75 0000C003.0260.8c9b.4e33 14 624
0000C003.0260.8c9b.4e33 0000C001.0260.8c8d.da75 62 3110
0000C001.0260.8c8d.e7c6 0000C003.0260.8c9b.4e33 20 1470
0000C003.0260.8c9b.4e33 0000C001.0260.8c8d.e7c6 20 1470
Accounting data age is 6
Table 50 describes the fields shown in the display.
| Field | Description |
|---|---|
| Source | Source address of the packet. |
| Destination | Destination address of the packet. |
| Packets | Number of packets transmitted from the source address to the destination address. |
| Bytes | Number of bytes transmitted from the source address to the destination address. |
| Accounting data age is ... | Time since the accounting database has been cleared. It can be in one of the following formats: mm, hh:mm, dd:hh, and xw yd, where m is minutes, h is hours, d is days, and w is weeks. |
clear ipx accounting
ipx accounting
ipx accounting-list
ipx accounting-threshold
ipx accounting-transits
To display the contents of the IPX fast-switching cache, use the show ipx cache EXEC command.
show ipx cacheThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show ipx cache command:
Router# show ipx cache
Novell routing cache version is 9
Destination Interface MAC Header
*1006A Ethernet 0 00000C0062E600000C003EB0064
*14BB Ethernet 1 00000C003E2A00000C003EB0064
Table 51 describes the fields shown in the display.
| Field | Description |
|---|---|
| Novell routing cache version is ... | Number identifying the version of the fast-switching cache table. It increments each time the table changes. |
| Destination | Destination network for this packet. Valid entries are marked by an asterisk (*). |
| Interface | Route interface through which this packet is transmitted. |
| MAC Header | Contents of this packet's MAC header. |
clear ipx cache
ipx route-cache
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]| type | (Optional) Interface type. |
| number | (Optional) Interface number. |
| as-number | (Optional) Autonomous system number. |
EXEC
This command first appeared in Cisco IOS Release 11.2.
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.
The following is sample output from the show ipx eigrp interfaces command:
Router> show ipx eigrp interfaces
IPX EIGRP interfaces for process 109
Xmit Queue Mean Pacing Time Multicast Pending
Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes
Di0 0 0/0 0 11/434 0 0
Et0 1 0/0 337 0/10 0 0
SE0:1.16 1 0/0 10 1/63 103 0
Tu0 1 0/0 330 0/16 0 0
Table 52 describes the fields shown in the display.
| Field | Description |
|---|---|
| process 109 | Autonomous system number of the process. |
| Interface | Interface name. |
| Peers | Number of neighbors on the interface. |
| Xmit Queue | Count of unreliable and reliable packets queued for transmission. |
| Mean SRTT | Average round-trip time for all neighbors on the interface. |
| Pacing Time | Number of milliseconds to wait after transmitting unreliable and reliable packets. |
| Multicast Flow Timer | Number of milliseconds to wait for acknowledgment of a multicast packet by all neighbors before transmitting the next multicast packet. |
| Pending Routes | Number of routes still to be transmitted on this interface. |
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]| servers | (Optional) Displays the server list advertised by each neighbor. This is displayed only if the ipx sap incremental command is enabled on the interface on which the neighbor resides. |
| autonomous-system-number | (Optional) Autonomous system number. It can be a decimal integer from 1 to 65535. |
| interface | (Optional) Interface type and number. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show ipx eigrp neighbors command:
Router# show ipx eigrp neighbors
IPX EIGRP Neighbors for process 200
H Address Interface Hold Uptime Q Seq SRTT RTO
(secs) (h:m:s) Cnt Num (ms) (ms)
6 90.0000.0c02.096e Tunnel44444 13 0:30:57 0 21 9 20
5 80.0000.0c02.34f2 Fddi0 12 0:31:17 0 62 14 28
4 83.5500.2000.a83c TokenRing2 13 0:32:36 0 626 16 32
3 98.0000.3040.a6b0 TokenRing1 12 0:32:37 0 43 9 20
2 80.0000.0c08.cbf9 Fddi0 12 0:32:37 0 624 19 38
1 85.aa00.0400.153c Ethernet2 12 0:32:37 0 627 15 30
0 82.0000.0c03.4d4b Hssi0 12 0:32:38 0 629 12 24
Table 53 explains the fields in the display.
| Field | Description |
|---|---|
| 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. |
To display the Enhanced IGRP topology table, use the show ipx eigrp topology EXEC command.
show ipx eigrp topology [network-number]| network-number | (Optional) IPX network number whose topology table entry to display. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show ipx eigrp topology command:
Router# show ipx eigrp topology
IPX EIGRP Topology Table for process 109
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - Reply status
P 42, 1 successors, FD is 0
via 160.0000.0c00.8ea9 (345088/319488), Ethernet0
P 160, 1 successor via Connected, Ethernet
via 160.0000.0c00.8ea9 (307200/281600), Ethernet0
P 165, 1 successors, FD is 307200
via Redistributed (287744/0)
via 160.0000.0c00.8ea9 (313344/287744), Ethernet0
P 164, 1 successors, flags: U, FD is 200
via 160.0000.0c00.8ea9 (307200/281600), Ethernet1
via 160.0000.0c01.2b71 (332800/307200), Ethernet1
P A112, 1 successors, FD is 0
via Connected, Ethernet2
via 160.0000.0c00.8ea9 (332800/307200), Ethernet0
P AAABBB, 1 successors, FD is 10003
via Redistributed (287744/0),
via 160.0000.0c00.8ea9 (313344/287744), Ethernet0
A A112, 0 successors, 1 replies, state: 0, FD is 0
via 160.0000.0c01.2b71 (307200/281600), Ethernet1
via 160.0000.0c00.8ea9 (332800/307200), r, Ethernet1
Table 54 explains the fields in the output.
| Field | Description |
|---|---|
| Codes | State of this topology table entry. Passive and Active refer to the Enhanced IGRP state with respect to this destination; Update, Query, and Reply refer to the type of packet that is being sent. |
| P - Passive | No Enhanced IGRP computations are being performed for this destination. |
| A - Active | Enhanced IGRP computations are being performed for this destination. |
| U - Update | Indicates that an update packet was sent to this destination. |
| Q - Query | Indicates that a query packet was sent to this destination. |
| R - Reply | Indicates that a reply packet was sent to this destination. |
| r - Reply status | Flag that is set after the Cisco IOS software has sent a query and is waiting for a reply. |
| 42, 160, and so on | Destination IPX network number. |
| successors | Number of successors. This number corresponds to the number of next hops in the IPX routing table. |
| FD | Feasible distance. This value is used in the feasibility condition check. If the neighbor's reported distance (the metric after the slash) is less than the feasible distance, the feasibility condition is met and that path is a feasible successor. Once the router determines it has a feasible successor, it does not have to send a query for that destination. |
| replies | Number of replies that are still outstanding (have not been received) with respect to this destination. This information appears only when the destination is in Active state. |
| state | 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. |
| via | IPX address of the peer who told the Cisco IOS software about this destination. The first n of these entries, where n is the number of successors, are the current successors. The remaining entries on the list are feasible successors. |
| (345088/319488) | The first number is the Enhanced IGRP metric that represents the cost to the destination. The second number is the Enhanced IGRP metric that this peer advertised. |
| Ethernet0 | Interface from which this information was learned. |
The following is sample output from the show ipx eigrp topology command when you specify an IPX network number:
Router# show ipx eigrp topology 160
IPX-EIGRP topology entry for 160
State is Passive, Query origin flag is 1, 1 Successor(s)
Routing Descriptor Blocks:
Next hop is Connected (Ethernet0), from 0.0000.0000.0000
Composite metric is (0/0), Send flag is 0x0, Route is Internal
Vector metric:
Minimum bandwidth is 10000 Kbit
Total delay is 1000000 nanoseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 0
Next hop is 164.0000.0c00.8ea9 (Ethernet1), from 164.0000.0c00.8ea9
Composite metric is (307200/281600), Send flag is 0x0, Route is External
This is an ignored route
Vector metric:
Minimum bandwidth is 10000 Kbit
Total delay is 2000000 nanoseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
External data:
Originating router is 0000.0c00.8ea9
External protocol is RIP, metric is 1, delay 2
Administrator tag is 0 (0x00000000)
Flag is 0x00000000
Table 55 explains the fields in the output
| Field | Description |
|---|---|
| 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. |
| Successors | 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 53. 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. |
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]| type | (Optional) Interface type. It can be one of the following types: asynchronous, dialer, Ethernet (IEEE 802.3), FDDI, loopback, null, serial, Token Ring, or tunnel. |
| number | (Optional) Interface number. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show ipx interface command:
Router# show ipx interface ethernet 1
Ethernet1 is up, line protocol is up
IPX address is C03.0000.0c05.6030, NOVELL-ETHER [up] line-up, RIPPQ: 0, SAPPQ : 0
Delay of this Novell network, in ticks is 1
IPXWAN processing not enabled on this interface.
IPX SAP update interval is 1 minute(s)
IPX type 20 propagation packet forwarding is disabled
Outgoing access list is not set
IPX Helper access list is not set
SAP Input filter list is not set
SAP Output filter list is not set
SAP Router filter list is not set
SAP GNS output filter list is not set
Input filter list is not set
Output filter list is not set
Router filter list is not set
Netbios Input host access list is not set
Netbios Input bytes access list is not set
Netbios Output host access list is not set
Netbios Output bytes access list is not set
Update time is 60 seconds
IPX accounting is enabled
IPX fast switching is configured (enabled)
IPX SSE switching is disabled
The following is sample output from the show ipx interface command when NLSP is enabled:
Router# show ipx interface ethernet 1
Ethernet0 is up, line protocol is up
IPX address is E001.0000.0c02.8cf9, SAP [up] line-up, RIPPQ: 0, SAPPQ : 0
Delay of this IPX network, in ticks is 1 throughput 0 link delay 0
IPXWAN processing not enabled on this interface.
IPX SAP update interval is 1 minute(s)
IPX type 20 propagation packet forwarding is disabled
Outgoing access list is not set
IPX Helper access list is not set
SAP Input filter list is not set
SAP Output filter list is not set
SAP Router filter list is not set
SAP GNS output filter list is not set
Input filter list is not set
Output filter list is not set
Router filter list is not set
Netbios Input host access list is not set
Netbios Input bytes access list is not set
Netbios Output host access list is not set
Netbios Output bytes access list is not set
Update time is 60 seconds
IPX accounting is enabled
IPX fast switching is configured (enabled)
IPX SSE switching is disabled
IPX NLSP is running on primary network E001
RIP compatibility mode is AUTO (OFF)
SAP compatibility mode is AUTO (OFF)
Level 1 Hello interval 20 sec
Level 1 Designated Router Hello interval 10 sec
Level 1 CSNP interval 0 sec
Level 1 LSP retransmit interval 5 sec, LSP (pacing) interval 1000 mSec
Level 1 adjacency count is 1
Level 1 circuit ID is 0000.0C02.8CF9.02
Table 56 describes the fields shown in the display.
| Field | Description |
|---|---|
| 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 sap-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 | Number of the Get Nearest Server (GNS) response filter applied to the interface with the ipx output-gns-filter command. |
| Input filter | Number of the input filter applied to the interface with the ipx input-network-filter command. |
| Output filter | Number of the output filter applied to the interface with the ipx output-network-filter command. |
| Router filter | 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-time 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 switching | Indicates 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. |
access-list (SAP filtering)
access-list (standard)
ipx accounting
ipx delay
ipx helper-list
ipx input-network-filter
ipx input-sap-filter
ipx ipxwan
ipx netbios input-access-filter
ipx netbios output-access-filter
ipx network
ipx output-gns-filter
ipx output-network-filter
ipx output-rip-delay
ipx output-sap-filter
ipx route-cache
ipx router-filter
ipx router-sap-filter
ipx routing
ipx sap-interval
ipx update-time
ipx watchdog-spoof
netbios access-list
To display the Next Hop Resolution Protocol (NHRP) cache, use the show ipx nhrp EXEC command.
show ipx nhrp [dynamic | static] [type number]| dynamic | (Optional) Displays only the dynamic (learned) IPX-to-NBMA address cache entries. |
| static | (Optional) Displays only the static IPX-to-NBMA address entries in the cache (configured through the ipx nhrp map command). |
| type | (Optional) Interface type about which to display the NHRP cache. Valid options are atm, serial, and tunnel). |
| number | (Optional) Interface number about which to display the NHRP cache. |
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show ipx nhrp command:
Router# show ipx nhrp
1.0000.0c35.de01, Serial1 created 0:00:43 expire 1:59:16
Type: dynamic Flags: authoritative
NBMA address: c141.0001.0001
1.0000.0c35.e605, Serial1 created 0:10:03 expire 1:49:56
Type: static Flags: authoritative
NBMA address: c141.0001.0002
Router#
Table 57 describes the fields in the display.
| Field | Description |
|---|---|
| 1.0000.0c35.de01 | IPX address in the IPX-to-NBMA address cache. |
| Serial1 created 0:00:43 | Interface type and number and how long ago it was created (hours:minutes:seconds). |
| expire 1:59:16 | Time in which the positive and negative authoritative NBMA address will expire (hours:minutes:seconds). This value is based on the ipx nhrp holdtime command. |
| Type | Value can be one of the following:
|
|
Flags | Value can be one of the following:
|
|
NBMA address | Nonbroadcast, multiaccess address. The address format is appropriate for the type of network being used (for example, ATM, Ethernet, SMDS, multipoint tunnel). |
To display Next Hop Resolution Protocol (NHRP) traffic statistics, use the show ipx nhrp traffic EXEC command.
show ipx nhrp trafficThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show ipx nhrp traffic command:
Router# show ipx nhrp traffic
Tunnel0
request packets sent: 2
request packets received: 4
reply packets sent: 4
reply packets received: 2
register packets sent: 0
register packets received: 0
error packets sent: 0
error packets received: 0
Router#
Table 58 describes the fields in the display.
| Field | Description |
|---|---|
| Tunnel 0 | Interface type and number. |
| request packets sent | Number of NHRP Request packets originated from this station. |
| request packets received | Number of NHRP Request packets received by this station. |
| reply packets sent | Number of NHRP Reply packets originated from this station. |
| reply packets received | Number of NHRP Reply packets received by this station. |
| register packets sent | Number of NHRP Register packets originated from this station. Currently, our routers do not send Register packets, so this value is 0. |
| register packets received | Number of NHRP Register packets received by this station. Currently, our routers do not send Register packets, so this value is 0. |
| error packets sent | Number of NHRP Error packets originated by this station. |
| error packets received | Number of NHRP Error packets received by this station. |
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]| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
| lspid | (Optional) Link-state protocol ID (LSPID). You must specify this in the format xxxx.xxxx.xxxx.yy-zz. The components of this argument have the following meaning:
· xxxx.xxxx.xxxx is the system identifier. · yy is the pseudo identifier. · zz is the LSP number. |
| detail | (Optional) Displays the contents of the LSP database entries. If you omit this keyword, only a summary display is shown. |
EXEC
This command first appeared in Cisco IOS Release 10.3.
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.
If you omit all options, a summary display is shown.
The following is sample output from the show ipx nlsp database command:
Router# show ipx nlsp database detail
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
0000.0C00.3097.00-00* 0x00000042 0xC512 699 0/0/0
0000.0C00.3097.06-00* 0x00000027 0x0C27 698 0/0/0
0000.0C02.7471.00-00 0x0000003A 0x4A0F 702 0/0/0
0000.0C02.7471.08-00 0x00000027 0x0AF0 702 0/0/0
0000.0C02.7471.0A-00 0x00000027 0xC589 702 0/0/0
0000.0C02.747D.00-00 0x0000002E 0xC489 715 0/0/0
0000.0C02.747D.06-00 0x00000027 0xEEFE 716 0/0/0
0000.0C02.747D.0A-00 0x00000027 0xFE38 716 0/0/0
0000.0C02.74AB.00-00 0x00000035 0xE4AF 1059 0/0/0
0000.0C02.74AB.0A-00 0x00000027 0x34A4 705 0/0/0
0000.0C06.FBEE.00-00 0x00000038 0x3838 1056 0/0/0
0000.0C06.FBEE.0D-00 0x0000002C 0xD248 1056 0/0/0
0000.0C06.FBEE.0E-00 0x0000002D 0x7DD2 1056 0/0/0
0000.0C06.FBEE.17-00 0x00000029 0x32FB 1056 0/0/0
0000.0C00.AECC.00-00* 0x000000B6 0x62A8 7497 0/0/0
IPX Area Address: 00000000 00000000
IPX Mgmt Info 87.0000.0000.0001 Ver 1 Name oscar
Metric: 45 Lnk 0000.0C00.AECC.06 MTU 1500 Dly 8000 Thru 64K PPP
Metric: 20 Lnk 0000.0C00.AECC.02 MTU 1500 Dly 1000 Thru 10000K 802.3 Raw
Metric: 20 Lnk 0000.0C01.EF90.0C MTU 1500 Dly 1000 Thru 10000K 802.3 Raw
0000.0C00.AECC.02-00* 0x00000002 0xDA74 3118 0/0/0
IPX Mgmt Info E0.0000.0c00.aecc Ver 1 Name Ethernet0
Metric: 0 Lnk 0000.0C00.AECC.00 MTU 0 Dly 0 Thru 0K 802.3 Raw
0000.0C00.AECC.06-00* 0x00000002 0x5DB9 7494 0/0/0
IPX Mgmt Info 0.0000.0000.0000 Ver 1 Name Serial0
Metric: 0 Lnk 0000.0C00.AECC.00 MTU 0 Dly 0 Thru 0K PPP
Metric: 1 IPX Ext D001 Ticks 0
Metric: 1 IPX SVC Second-floor-printer D001.0000.0000.0001 Sock 1 Type 4
Table 59 explains the fields in the display.
| Field | Description |
|---|---|
| LSPID | System ID (network number), pseudonode circuit identifier, and fragment number. |
| LSP Seq Num | Sequence number of this LSP. |
| LSP Checksum | Checksum of this LSP. |
| LSP Holdtime | Time until this LSP expires, in seconds. |
| ATT/P/OL | Indicates which of three bits are set. A "1" means the bit is set, and a "0" means it is not set.
ATT is the L2-attached bit. OL is the overload bit. P is the partition repair bit. This bit is not used in NLSP. |
| IPX Area Address: | Area address of the router advertising the LSP. |
| IPX Mgmt Info | Management information. For nonpseudonode LSPs, the internal network number is advertised in this field. For pseudonode LSPs, the network number of the associated interface is advertised. |
| Ver | NLSP version running on the advertising router. |
| Name | For nonpseudonode LSPs, the name of the router. For pseudonode LSPs, the name (or description, if configured) of the associated interface. |
| Link Information | Information about the link. |
| Metric: | NLSP metric (cost) for the link. Links from a pseudonode to real nodes have a cost of 0 so that this link cost is not counted twice. |
| Lnk | System ID of the adjacent node. |
| MTU | MTU of the link in bytes. For pseudonode LSPs, the value in this field is always 0. |
| Dly | Delay of the link in microseconds. For pseudonode LSPs, the value in this field is always 0. |
| Thru | Throughput of the link in bits per second. For pseudonode LSPs, the value in this field is always 0. |
| 802.3 Raw, Generic LAN | Link media type. |
| External (RIP) Networks | Information about an external (RIP) network. |
| Metric: | Received RIP hop count. |
| IPX Ext | IPX network number. |
| Ticks | Received RIP tick count. |
| SAP Services | Information about SAP services. |
| Metric: | Received SAP hop count. |
| IPX SVC | Name of the IPX service. |
| D001.000.0000.0001 | IPX address of the server advertising this service. |
| Sock | Socket number of the service. |
| Type | Type of service. |
The following example shows how to use the show ipx nlsp database detail command with NLSP enabled.
Router#show ipx nlsp database detail NLSP Level-1 Link State Database LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL dtp-8-BOS.00-00 0x00000012 0x8819 7435 0/0/0 IPX Area Address: 00000000 00000000 IPX Mgmt Info 2008.0000.0000.0001 Ver 1 Name dtp-8-BOS Metric: 20 Lnk dtp-8-BOS.04 MTU 1500 Dly 1000 Thru 10000K 802.3 Raw Metric: 20 Lnk dtp-8-BOS.06 MTU 1500 Dly 1000 Thru 10000K 802.3 Raw Metric: 19 Lnk dtp-8-BOS.02 MTU 8141 Dly 630 Thru 16000K 802.5/LLC Metric: 19 Lnk dtp-8-BOS.03 MTU 8141 Dly 630 Thru 16000K 802.5/LLC Area Count: 6 IPX Sum 1000 FFFFF000 Ticks 1 ******** aggregate entry in the LSP **************** dtp-8-BOS.02-00 0x00000005 0x0F36 7434 0/0/0 IPX Mgmt Info 89.0000.3020.cc5b Ver 1 Name TokenRing0 Metric: 0 Lnk dtp-8-BOS.00 MTU 0 Dly 0 Thru 0K 802.5/LLC dtp-8-BOS.03-00 0x00000008 0x96EE 7430 0/0/0 IPX Mgmt Info 91.0000.3020.ccdb Ver 1 Name TokenRing1 Metric: 0 Lnk dtp-8-BOS.00 MTU 0 Dly 0 Thru 0K 802.5/LLC Metric: 0 Lnk dtp-11.00 MTU 0 Dly 0 Thru 0K 802.5/LLC dtp-8-BOS.04-00 0x00000006 0x8C4D 7427 0/0/0 IPX Mgmt Info 1.0000.0c05.6023 Ver 1 Name Ethernet0 Metric: 0 Lnk dtp-8-BOS.00 MTU 0 Dly 0 Thru 0K 802.3 Raw Metric: 1 IPX Ext 2010 Ticks 2 Metric: 1 IPX Ext 20 Ticks 1 dtp-8-BOS.06-00 0x00000005 0x946B 7426 0/0/0 IPX Mgmt Info 100.0000.0c05.6023 Ver 1 Name Ethernet1 Metric: 0 Lnk dtp-8-BOS.00 MTU 0 Dly 0 Thru 0K 802.3 Raw dtp-11.00-00 * 0x00000007 0x7777 7271 0/0/0 IPX Area Address: 00000000 00000000 IPX Mgmt Info 2011.0000.0000.0001 Ver 1 Name dtp-11 Metric: 20 Lnk dtp-11.06 MTU 1500 Dly 1000 Thru 10000K 802.3 Raw Metric: 20 Lnk dtp-11.08 MTU 1500 Dly 1000 Thru 10000K 802.3 Raw Metric: 20 Lnk dtp-11.09 MTU 1500 Dly 1000 Thru 10000K 802.3 Raw
To display NLSP neighbors and their states, use the show ipx nlsp neighbors EXEC command.
show ipx nlsp [tag] neighbors [interface] [detail]| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
| interface | (Optional) Interface type and number. |
| detail | (Optional) Displays detailed information about the neighbor. If you omit this keyword, only a summary display is shown. |
EXEC
This command first appeared in Cisco IOS Release 10.3.
When you specify an NLSP tag, 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 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.
If you omit the keyword detail, a summary display is shown.
The following is sample output from the show ipx nlsp neighbors command:
Router# show ipx nlsp neighbors detail
System Id Interface State Holdtime Priority Circuit Id
0000.0C01.EF90 Ethernet1 Up 25 64 0000.0C01.EF90.0C
IPX Address: E1.0000.0c01.ef91
IPX Areas: 00000000/00000000
Uptime: 2:59:11
Table 60 explains the fields in the display.
| Field | Description |
|---|---|
| System Id | System ID of the neighbor. |
| Interface | Interface on which the neighbor was discovered. |
| State | State of the neighbor adjacency. |
| Holdtime | Remaining time before the neighbor is assumed to have failed. |
| Priority | Designated router election priority. |
| Circuit Id | Neighbor's view of the identity of the designated router. |
| IPX Address: | IPX address on this network of the neighbor. |
| IPX Areas: | IPX area addresses configured on the neighbor. |
| Uptime: | Time since the neighbor was discovered. |
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| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show ipx nlsp spf-log command:
Router>show ipx nlsp spf-logLevel 1 SPF log When Duration Nodes Count Triggers 0:30:59 1028 84 1 TLVCONTENT 0:27:09 1016 84 1 TLVCONTENT 0:26:30 1136 84 1 TLVCONTENT 0:23:11 1244 84 1 TLVCONTENT 0:22:39 924 84 2 TLVCONTENT 0:22:08 1036 84 1 TLVCONTENT 0:20:02 1096 84 1 TLVCONTENT 0:19:31 1140 84 1 TLVCONTENT 0:17:25 964 84 2 PERIODIC TLVCONTENT 0:16:54 996 84 1 TLVCONTENT 0:16:23 984 84 1 TLVCONTENT 0:15:52 1052 84 1 TLVCONTENT 0:14:34 1112 84 1 TLVCONTENT 0:13:37 992 84 1 TLVCONTENT 0:13:06 1036 84 1 TLVCONTENT 0:12:35 1008 84 1 TLVCONTENT 0:02:52 1032 84 1 TLVCONTENT 0:02:16 1032 84 1 PERIODIC 0:01:44 1000 84 3 TLVCONTENT
Table 61 describes the fields shown in the display.
| Field | Descriptions |
|---|---|
| When | Amount of time since the SPF calculation took place. |
| Duration | Amount of time (in milliseconds) that the calculation required. |
| Nodes | Number of link state packets (LSPs) encountered during the calculation. |
| Count | Number of times that the SPF calculation was triggered before it actually took place. An SPF calculation is normally delayed for a short time after the event that triggers it. |
| Triggers | List of the types of triggers that were recorded before the SPF calculation occurred (more than one type may be displayed):
PERIODIC--Periodic SPF calculation (every 15 minutes). NEWSYSID--New system ID was assigned. NEWAREA--New area address was configured. RTCLEARED--IPX routing table was manually cleared. NEWMETRIC--Link metric of an interface was reconfigured. ATTACHFLAG--Level 2 router has become attached or unattached from the rest of the level 2 topology. LSPEXPIRED--LSP has expired. NEWLSP--New LSP has been received. LSPHEADER--LSP with changed header fields was received. TLVCODE--LSP with a changed (Type-Length-Value) TLV code field was received. TLVCONTENT--LSP with changed TLV contents was received. AREASET--Calculated area address set has changed. NEWADJ--New neighbor adjacency came up. DBCHANGED--NLSP link state database was manually cleared. |
To display the contents of the IPX routing table, use the show ipx route user EXEC command.
show ipx route [network] [default] [detailed]| network | (Optional) Number of the network whose routing table entry you want to display. This 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. |
| default | (Optional) Displays the default route. This is equivalent to specifying a value of FFFFFFFE for the argument network. |
| detailed | (Optional) Displays detailed route information. |
EXEC
This command first appeared in Cisco IOS Release 10.0. The default and detailed keywords first appeared in Cisco IOS Relesae 10.0.
The following is sample output from the show ipx route command:
Router# show ipx route
Codes: C - Connected primary network, c - Connected secondary network
S - Static, F - Floating static, L - Local (internal), W - IPXWAN
R - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregate
s - seconds, u - uses
8 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.
No default route known.
L D40 is the internal network
C 100 (NOVELL-ETHER), Et1
C 7000 (TUNNEL), Tu1
S 200 via 7000.0000.0c05.6023, Tu1
R 300 [02/01] via 100.0260.8c8d.e748, 19s, Et1
S 2008 via 7000.0000.0c05.6023, Tu1
R CC0001 [02/01] via 100.0260.8c8d.e748, 19s, Et1
Table 62 describes the fields shown in the display.
| Field | Description |
|---|---|
| Codes | Codes defining how the route was learned. |
| L | Internal network number. |
| C | Directly connected primary network |
| c | Directly connected secondary network |
| S | Statically defined route via the ipx route command. |
| R | Route learned from a RIP update. |
| E | Route learned from an Enhanced IGRP (EIGRP) update. |
| W | 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) (HDLC) (SAP) (SNAP) | 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, Nu0
In 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 route
Codes: C - Connected primary network, c - Connected secondary network
S - Static, F - Floating static, L - Local (internal), W - IPXWAN
R - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregate
s - seconds, u - uses
13 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, Nu0
L 2008 is the internal network
C 1 (NOVELL-ETHER), Et0
C 89 (SAP), To0
C 91 (SAP), To1
C 100 (NOVELL-ETHER), Et1
N 2 [19][01/01] via 91.0000.30a0.51cd, 317s, To1
N 3 [19][01/01] via 91.0000.30a0.51cd, 327s, To1
N 20 [20][01/01] via 1.0000.0c05.8b24, 2024s, Et0
N 101 [19][01/01] via 91.0000.30a0.51cd, 327s, To1
NX 1000 [20][02/02][01/01] via 1.0000.0c05.8b24, 2024s, Et0
N 2010 [20][02/01] via 1.0000.0c05.8b24, 2025s, Et0
N 2011 [19][02/01] via 91.0000.30a0.51cd, 328s, To1
The following is sample output from the show ipx route detailed command:
Router# show ipx route detailed
Codes: C - Connected primary network, c - Connected secondary network
S - Static, F - Floating static, L - Local (internal), W - IPXWAN
R - RIP, E - EIGRP, N - NLSP, X - External, s - seconds, u - uses
9 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.
No default route known.
L D35 is the internal network
C E001 (SAP), Et0
C D35E2 (NOVELL-ETHER), Et2
R D34 [02/01]
-- via E001.0000.0c02.8cf9, 43s, 1u, Et0
N D36 [20][02/01]
-- via D35E2.0000.0c02.8cfc, 704s, 1u, Et2
10000000:1000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc
NX D40 [20][03/02][02/01]
-- via D35E2.0000.0c02.8cfc, 704s, 1u, Et2
10000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc
R D34E1 [01/01]
-- via E001.0000.0c02.8cf9, 43s, 1u, Et0
NX D40E1 [20][02/02][01/01]
-- via D35E2.0000.0c02.8cfc, 704s, 3u, Et2
10000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc
N D36E02 [20][01/01]
-- via D35E2.0000.0c02.8cfc, 705s, 2u, Et2
10000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc
Table 63 explains the additional fields shown in the display.
| Field | Description |
|---|---|
| 1u | 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. |
| 10000000 | (NLSP only) Throughput (end to end). |
| 3000 | (NLSP only) Link delay (end to end). |
| 1500 | (NLSP only) MTU (end to end). |
| 0000.0c02.8cfb | (NLSP only) System ID of the next-hop router. |
| 0000.0c02.8cfc | (NLSP only) MAC address of the next-hop router. |
| 6 | (NLSP only) Local circuit ID. |
clear ipx route
ipx maximum-paths
ipx nlsp metric
ipx route
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]| unsorted | (Optional) Does not sort entries when displaying IPX servers. |
| sorted | (Optional) Sorts the display of IPX servers according to the keyword that follows. |
| name | (Optional) Displays the IPX servers alphabetically by server name. |
| net | (Optional) Displays the IPX servers numerically by network number. |
| type | (Optional) Displays the IPX servers numerically by SAP service type. This is the default. |
| regexp name | (Optional) Displays the IPX servers whose names match the regular expression. |
IPX servers are displayed numerically by SAP service type.
EXEC
This command first appeared in Cisco IOS Release 10.0. The unsorted keyword first appeared in Cisco IOS Release 11.0
The following is sample output from the show ipx servers command when NLSP is enabled:
Router# show ipx servers
Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail
9 Total IPX Servers
Table ordering is based on routing and server info
Type Name Net Address Port Route Hops Itf
N+ 4 MERLIN1-VIA-E03 E03E03.0002.0004.0006:0451 4/03 4 Et0
N+ 4 merlin E03E03.0002.0004.0006:0451 4/03 3 Et0
N+ 4 merlin 123456789012345 E03E03.0002.0004.0006:0451 4/03 3 Et0
S 4 WIZARD1--VIA-E0 E0.0002.0004.0006:0451 none 2
N+ 4 dtp-15-AB E002.0002.0004.0006:0451 none 4 Et0
N+ 4 dtp-15-ABC E002.0002.0004.0006:0451 none 4 Et0
N+ 4 dtp-15-ABCD E002.0002.0004.0006:0451 none 4 Et0
N+ 4 merlin E03E03.0002.0004.0006:0451 4/03 3 Et0
N+ 4 dtp-15-ABC E002.0002.0004.0006:0451 none 4 Et0
Table 64 describes the fields shown in the display.
| Field | Description |
|---|---|
| Codes | Codes defining how the service was learned. |
| S | Statically defined service via the ipx sap command. |
| P | Service learned via a SAP update. |
| E | Service learned via Enhanced IGRP. |
| N | Service learned via NLSP. |
| H | Indicates that the entry is in holddown mode and is not reachable. |
| + | 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, + = detail
9 Total IPX Servers
Table ordering is based on routing and server info
Type Name Net Address Port Route Hops Itf
S 108 ACCT_SERV_1 7001.0000.0000.0001:0001 1/01 2 Et0
S 108 ACCT_SERV_2 7001.0000.0000.0001:0001 1/01 2 Et0
S 108 ACCT_SERV_3 7001.0000.0000.0001:0001 1/01 2 Et0
See Table 64 for show IPX servers field descriptions.
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-spoofThis command has no arguments or keywords.
Disabled
EXEC
This command first appeared in Cisco IOS Release 11.0.
The following is sample output from the show ipx spx-spoof command:
Router> show ipx spx-spoof
Local 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 120
Table 65 describes the fields shown in the display.
| Field | Description |
|---|---|
| Local SPX Network.Host:sock | Address of the local end of the SPX connection. The address is composed of the SPX network number, host, and socket. |
| Cid | Connection identification of the local end of the SPX connection. |
| Remote SPX Network.Host:sock | Address of the remote end of the SPX connection. The address is composed of the SPX network number, host, and socket. |
| Cid | Connection identification of the remote end of the SPX connection. |
| Seq | Sequence number of the last data packet transferred. |
| Ack | Number of the last solicited acknowledge received. |
| Idle | Amount of time elapsed since the last data packet was transferred. |
ipx spx-idle-time
ipx spx-spoof
To display information about the number and type of IPX packets transmitted and received, use the show ipx traffic user EXEC command.
show ipx trafficThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show ipx traffic command:
Router> show ipx traffic
Rcvd: 644 total, 1705 format errors, 0 checksum errors, 0 bad hop count,
0 packets pitched, 644 local destination, 0 multicast
Bcast: 589 received, 324 sent
Sent: 380 generated, 0 forwarded
0 encapsulation failed, 4 no route
SAP: 1 SAP requests, 1 SAP replies, 20servers
10 SAP Nearest Name requests, 10 replies
15 SAP General Name requests, 15 replies
61 SAP advertisements received, 120 sent
0 SAP flash updates sent, 0 SAP format errors
RIP: 0 RIP format errors
Echo: Rcvd 55 requests, 0 replies
Sent 0 requests, 55 replies
0 unknown, 0 SAPs throttled, freed NDB len 0
Watchdog:
0 packets received, 0 replies spoofed
Queue lengths: IPX input: 0, SAP 0, RIP 0, GNS 0
Total length for SAP throttling purposes: 0/(no preset limit)
EIGRP: Total received 0, sent 0
Updates received 0, sent 0
Queries received 0, sent 0
Replies received 0, sent 0
SAPs received 0, sent 0
The following is sample output from the show ipx traffic command when NLSP is enabled:
Router> show ipx traffic
Rcvd: 593135 total, 38792 format errors, 0 checksum errors, 0 bad hop count,
21542 packets pitched, 295493 local destination, 0 multicast
Bcast: 295465 received, 346725 sent
Sent: 429393 generated, 276100 forwarded
0 encapsulation failed, 0 no route
SAP: 4259 SAP requests, 0 SAP replies, 35 servers
0 SAP Nearest Name requests, 0 replies
0 SAP General Name requests, 0 replies
191636 SAP advertisements received, 277136 sent
115 SAP flash updates sent, 0 SAP format errors
RIP: 4676 RIP requests, 336 RIP replies, 18 routes
87274 RIP advertisements received, 69438 sent
74 RIP flash updates sent, 0 RIP format errors
Echo: Rcvd 0 requests, 0 replies
Sent 0 requests, 0 replies
7648 unknown: 0 no socket, 0 filtered, 7648 no helper
0 SAPs throttled, freed NDB len 0
Watchdog:
0 packets received, 0 replies spoofed
Queue lengths:
IPX input: 0, SAP 0, RIP 0, GNS 0
SAP throttling length: 0/(no limit), 0 nets pending lost route reply
Delayed process creation: 0
EIGRP: Total received 0, sent 0
Updates received 0, sent 0
Queries received 0, sent 0
Replies received 0, sent 0
SAPs received 0, sent 0
NLSP: Level-1 Hellos received 0, sent 0
PTP Hello received 0, sent 0
Level-1 LSPs received 0, sent 0
LSP checksum errors received: 0
LSP HT=0 checksum errors received: 0
Level-1 CSNPs received 0, sent 0
Level-1 PSNPs received 0, sent 0
Level-1 DR Elections: 0
Level-1 SPF Calculations: 0
Level-1 Partial Route Calculations: 0
Table 66 describes the fields that might possibly be shown in the display.
| Field | Description |
|---|---|
| Rcvd: | Description of the packets received. |
| 593135 total | Total number of packets received. |
| 38792 format errors | Number of bad packets discarded (for example, packets with a corrupted header). |
| 0 checksum errors | Number of packets containing a checksum error. This number should always be 0, because IPX does not use a checksum. |
| 0 bad hop count | Number of packets discarded because their hop count exceeded 16 (that is, the packets timed out). |
| 21542 packets pitched | Number of times the device received its own broadcast packet. |
| 295493 local destination | Number of packets sent to the local broadcast address or specifically to the router. |
| 0 multicast | Number of packets received that were addressed to multiple destinations. |
| Bcast: | Description of the broadcast packets the router has received and sent. |
| 295465 received | Number of broadcast packets received. |
| 346725 sent | Number of broadcast packets sent. It includes broadcast packets the router is either forwarding or has generated. |
| Sent: | Description of those packets that the software generated and then sent, and also those the software has received and then routed to other destinations. |
| 429393 generated | Number of packets transmitted that it generated itself. |
| 276100 forwarded | Number of packets transmitted that it forwarded from other sources. |
| 0 encapsulation failed | Number of packets the software was unable to encapsulate. |
| 0 no route | Number of times the software could not locate a route to the destination in the routing table. |
| SAP: | Description of the SAP packets sent and received. |
| 4259 SAP requests | Number of SAP requests received. |
| 0 SAP replies | Number of SAP replies sent in response to SAP requests. |
| 35 servers | Number of servers in the SAP table. |
| 0 SAP Nearest Name requests 0 replies | Number of SAP Nearest Name requests and replies. |
| 0 SAP General Name requests 0 replies | Number of SAP General Name requests and replies. |
| 191636 SAP advertisements received | Number of SAP advertisements received from another router. |
| 277136 sent | Number of SAP advertisements generated and then sent. |
| 115 SAP flash updates sent | Number of SAP advertisements generated and then sent as a result of a change in its routing table. |
| 0 SAP format errors | Number of SAP advertisements that were incorrectly formatted. |
| RIP: | Description of the RIP packets sent and received. |
| 4676 RIP requests | Number of RIP requests received. |
| 336 RIP replies | Number of RIP replies sent in response to RIP requests. |
| 18 routes | Number of RIP routes in the current routing table. |
| 87274 RIP advertisements received | Number of RIP advertisements received from another router. |
| 69438 sent | Number of RIP advertisements generated and then sent. |
| 74 RIP flash updates sent | Number of RIP advertisements generated and then sent as a result of a change in its routing table. |
| 0 RIP format errors | Number of RIP packets that were incorrectly formatted. |
| freed NDB length | Number of Network Descriptor Blocks ¬(NDBs) that have been removed from the network but still need to be removed from the router's routing table. |
| Watchdog: | Description of the watchdog packets the software has handled. |
| 0 packets received | Number of watchdog packets received from IPX servers on the local network. |
| 0 replies spoofed | Number of times the software has responded to a watchdog packet on behalf of the remote client. |
| Echo: | Description of the ping replies and requests sent and received. |
| Rcvd 55 requests, 0 replies | Number of ping requests and replies received. |
| Sent 0 requests, 0 replies | Number of ping requests and replies. |
| 7648 unknown | Number of incomprehensible ping packets received. |
| 0 SAPs throttled | Number of sap packets discarded because they exceeded buffer capacity. |
| Queue lengths | Description of outgoing packets currently in buffers that are waiting to be processed. |
| IPX input | Number of incoming packets waiting to be processed. |
| SAP | Number of outgoing SAP packets waiting to be processed. |
| RIP | Number of outgoing RIP packets waiting to be processed. |
| GNS | Number of outgoing GNS packets waiting to be processed. |
| Total length for SAP throttling purposes | Maximum number of outgoing SAP packets allowed in the buffer. Any packets received beyond this number are discarded. |
| EIGRP: | Description of the Enhanced IGRP packets the router has sent and received. |
| Updates | Number of Enhanced IGRP updates sent and received. |
| Queries | Number of Enhanced IGRP queries sent and received. |
| Replies | Number of Enhanced IGRP replies sent and received. |
| SAPs | Number of SAP packets sent to and received from Enhanced IGRP neighbors. |
| unknown counter | Number of packets the software was unable to forward, for example, because of a misconfigured helper address or because no route was available.
<<John, is this the number of packets that arrived at the router for which the router had no such services to process them?? Or, does this change belong in "7648 unknown" row above?>> |
| NLSP: | Description of the NLSP packets the router has sent and received. |
| Level-1 Hellos | Number of LAN hello packets sent and received. |
| PTP Hello | Number of point-to-point packets sent and received. |
| Level-1 LSPs | Number of link-state packets (LSPs) sent and received. |
| Level-1 CSNPs | Number of complete sequence number PDU (CSNP) packets sent and received. |
| Level-1 PSNPs | Number of partial sequence number PDU (PSNP) packets sent and received. |
| Level-1 DR Elections | Number of times the software has calculated its designated router election priority. |
| Level-1 SPF Calculations | Number of times the software has perform the shortest path first (SPF) calculation. |
| Level-1 Partial Route Calculations | Number of times the software has recalculated routes without running SPF. |
To display a summary of Silicon Switch Processor (SSP) statistics, use the show sse summary EXEC command.
show sse summaryThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.0.
The following is sample output from the show sse summary command:
Router# show sse summary
SSE utilization statistics
Program words Rewrite bytes Internal nodes Depth
Overhead 499 1 8
IP 0 0 0 0
IPX 0 0 0 0
SRB 0 0 0 0
CLNP 0 0 0 0
IP access lists 0 0 0
Total used 499 1 8
Total free 65037 262143
Total available 65536 262144
Free program memory
[499..65535]
Free rewrite memory
[1..262143]
Internals
75032 internal nodes allocated, 75024 freed
SSE manager process enabled, microcode enabled, 0 hangs
Longest cache computation 4ms, longest quantum 160ms at 0x53AC8
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| seconds | Minimum amount of time between SPF calculations, in seconds. It can be a number in the range 1 to 120. The default is 5 seconds. |
5 seconds
Router configuration
This command first appeared in Cisco IOS Release 10.3.
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.
The following example sets the SPF calculation interval to 30 seconds:
spf-interval 30
ipx router nlsp
log-neighbor-changes
prc-interval
|
|