|
|
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 Advertisement Protocol (SAP) to advertise special network services.
Our implementation of Novell's IPX protocol has been certified as providing full IPX communication server functionality. Our communication server connects Ethernet, Token Ring, and FDDI networks, either directly or through high-speed serial lines (56 kbps to T1 speeds), X.25, or Frame Relay. The Cisco X.25 and T1 support currently is not compatible with Novell. This means that our communication servers must be used on both ends of T1 and X.25 circuits.
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 Access and Communication Servers Configuration Guide.
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 just 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 just 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
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 in another chapter.
access-list (extended)
ipx access-group
ipx input-network-filter
ipx output-network-filter
ipx router-filter
priority-list protocol †
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 | Number of an IPX protocol type, in decimal. This also is sometimes referred to as the packet type. Table 20-1 in the "Usage Guidelines" section lists some IPX protocol 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 just 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 number from which the packet is being sent, in hexadecimal. Table 20-2 in the "Usage Guidelines" section lists some IPX socket 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 just 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-node-mask | (Optional) Mask to be applied to destination-node. This is a 48-bit value represented as a dotted triplet of four-digit hexadecimal numbers (xxxx.xxxx.xxxx). Place ones in the bit positions you want to mask. |
destination-socket | (Optional) Socket number to which the packet is being sent, in hexadecimal. Table 20-2 in the "Usage Guidelines" section lists some IPX socket numbers. |
No access lists are predefined.
Global configuration
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 20-1 lists some IPX protocol numbers. Table 20-2 lists some IPX socket numbers. For additional information about IPX protocol numbers and socket numbers, contact Novell.
To delete an extended access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:
no access-list access-list-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 (protocol number 1) from socket 453 (RIP process socket) on source network 1 that are destined for socket 453 on network 2. It permits all other traffic.
access-list 900 deny 1 453 2 453
access-list 900 permit 0 -1 0 -1 0
The following example permits type 2 packets from any socket on network 10 to access any sockets on any nodes on networks 1000 through 100F. It denies all other traffic (with an implicit deny all):
access-list 910 permit 20 10.0000.0C00.0000 0000.0000.FFFF 0
1000.0000.0000.0000 F.FFFF.FFFF.FFFF 0
A dagger (†) indicates that the command is documented in another 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 for filtering Service Advertisement 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.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 just 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.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 20-3 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
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 20-3 lists some sample IPX SAP types. For more information about SAP types, contact Novell. Note that in the filter (specified by the service-type argument), we define a value of 0 to filter all SAP services. If, however, you receive a SAP packet with a SAP type of 0, this indicates an unknown service.
To delete a SAP access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:
no access-list access-list-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 in another chapter.
ipx input-sap-filter
ipx output-gns-filter
ipx output-sap-filter
ipx router-sap-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
You must configure at least one area address before NLSP will operate.
The area-address command defines a prefix that includes all networks that are in the area.
All networks that are part of the NLSP area (that is, all networks that are configured on an interface 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 and communication server in an NLSP area must be configured with a common area address, or they will form separate areas.
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 active 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
If you omit the checkpoint argument, all the entries in the active database are deleted. 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
The clear ipx cache command clears entries used for fast switching.
The following example deletes all entries from the IPX fast-switching cache:
clear ipx cache
ipx route-cache
show ipx cache
To delete routes from the IPX routing table, use the clear ipx route EXEC command.
clear ipx route {network | 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 just AA. |
default | Deletes the default route from the routing table. |
* | Deletes all routes in the routing table. |
EXEC
The following example clears the entry for network 3 from the IPX routing table:
clear ipx route 3
show ipx route
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 [type number]
access-list-number | Standard IPX access list number in the range 800 to 899. The list explicitly specifies which networks are to be received and which are to be suppressed. |
type | (Optional) Interface type. |
number | (Optional) Interface number. |
Disabled
Router configuration
The following example causes only two networks—network 2 and network 3—to be accepted by an IP 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
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. The list explicitly specifies which networks are to be sent and which are to be suppressed in 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 (rip or eigrp autonomous system number). |
Disabled
Router configuration
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 IPX 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
distribute-list in
redistribute
To apply a generic output filter to an interface, use ipx access-group interface configuration command. To remove the access list, use the no form of this command.
ipx access-group access-list-number
access-list-number | Number of the access list. 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. 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. |
No filters are predefined.
Interface configuration
Generic filters control which packets are sent out an interface 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 generic filter to an interface.
In the following example, access list 801 is applied to Ethernet interface 1:
interface ethernet 1
ipx access-group 801
A dagger (†) indicates that the command is documented in another chapter.
access-list (standard)
access-list (extended)
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
IPX accounting allows you to collect information about IPX packets and the number of bytes that are switched through the communication server. You collect information based on the source and destination IPX address. Accounting tracks only IPX traffic that is passing out of the communication server; it does not track traffic generated by or terminating at the communication server.
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 communication server 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
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 communication server can accumulate |
512 entries
Global configuration
The accounting threshold defines the maximum number of entries (source and destination address pairs) that the communication server accumulates. The threshold is designed to prevent IPX accounting from consuming all available free memory. This level of memory consumption could occur in a communication server that is switching traffic for many hosts. To determine whether overflows have occurred, used 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
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 communication server 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
ipx accounting-list
ipx accounting-threshold
show ipx accounting
To advertise only the RIP default route via the specified network, use the ipx advertise-default-route-only interface configuration command. To advertise all 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 RIP default route. This is the only network advertised. |
Disabled. All default routes are advertised.
Interface configuration
If you specify the ipx advertise-default-route-only command, only the default route, if known, will be advertised out the interface. If you have a large number of routes in the routing table, for example, 1000 routes, none of them will be advertised out the interface. Nodes on the interface can still reach any of the 1000 networks because they know the default. 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.
The following example enables the advertising of the RIP default route only:
ipx advertise-default-route-only 3c.7389.4339
To change the time between successive queries of each IPX 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
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 forward packets to a default network it the a route to the packet's destination network is unknown, use the ipx default-route global configuration command. To discard all packets if the 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 towards the default network, which is -2.
Global configuration
The following example disables the forwarding of packets towards the default network:
no ipx default-route
ipx advertise-default-route-only
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/18th of a second (approximately 55 milliseconds). |
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
The ipx delay command sets the count used in the IPX RIP delay field, which is also known as the ticks field.
Leaving the delay at its default value is sufficient for most interfaces.
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.
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 in another 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 just AA. |
Disabled
Interface configuration
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.
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 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
The following example disables the sending of replies to GNS queries on Ethernet interface 0:
interfac e ethernet 0
ipx gns-reply-disable
ipx gns-response-delay
To change the delay when responding to Get Nearest Server (GNS) requests, use the ipx gns-response-delay global 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 communication server waits after receiving a Get Nearest Server request from an IPX client before responding with a server name to that client. The default time is 0 milliseconds. A value of zero indicates no delay. |
0 milliseconds (no delay)
Global configuration
The delay in responding to Get Nearest Server requests is imposed so that in certain topologies any local Novell IPX servers can respond to the GNS requests before our communication server does. It is desirable to have these end-host server systems get their reply to the client before the communication server does, because the client typically takes the first response, not the best, and 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 or communication server functioning as 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 always must connect to routers to reach 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 milliseconds (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
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 communication server maintains a list of the nearest servers eligible to provide specific services. It uses this list when responding to Get Nearest Server (GNS) requests. Responses to requests are distributed in a round-robin fashion across all active IPX interfaces on the communication server.
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-filter
To configure the interval between IPX 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 | IPX 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. |
5 seconds
Interface configuration
If the current value for the hold time is less than two times the interval between hello packets, the hold time will be reset.
The following example changes the hello interval to 10 seconds:
interface ethernet 0
ipx network 10
ipx hello-interval eigrp 4 10
ipx hold-time eigrp
To forward broadcast packets (except type 20 propagation 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 just 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
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 (except type 20 propagation packets). 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.
Note that type 20 propagation packet handling is controlled by a separate mechanism. See the discussion of the ipx type-20-packet-propagation command for more information.
You can specify multiple ipx helper-address commands on a given interface.
Our routers and communication servers support 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 routers and communication servers take 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.
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
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 (standard)
access-list (extended)
ipx helper-address
ipx type-20-propagation
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 three times the hello interval. |
15 seconds
Interface configuration
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 following example changes the hold time to 45 seconds:
interface ethernet 0
ipx network 10
ipx hold-time eigrp 4 45
ipx hello-interval eigrp
To control which networks are added to the communication server'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
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 (standard)
access-list (extended)
ipx output-network-filter
ipx router-filter
To control which services are added to the communication server'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
The ipx input-sap-filter command filters all incoming service advertisements received by the communication server. This is done prior to a communication server's 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 SAP access-list 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
An internal network number is a number assigned to the communication server.
You must configure an internal network number on each communication server on an NLSP-capable network in order for NLSP to operate.
When you set an internal network number, the communication server 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
ipx router nlsp
ipx routing
To configure 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 local-server [retry-interval] [retry-attempts]
local-node | Primary network number of the communication server. This is an IPX network number that is unique across the entire internet. On NetWare 3.x servers, the primary network number is called the internal network number. The communication server with the higher number is determined to be the link Master. |
network | The IPX network number to be used for the link if this communication server 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 1 to FFFFFFFE. You do not need to specify leading zeros in the network number. For example, for the network number 000000AA, you can enter just AA. |
local-server | Name of the local communication server. It can be up to 47 characters long, and can contain uppercase letters, digits, underscores (_), hyphens (-), and at signs (@). On NetWare 3.x servers, the local server is called the communication server name. |
retry-interval | (Optional) Retry interval, in seconds. This interval defines how often the communication server will retry failed negotiation attempts. It can be a value from 1 through 600. The default is 20 seconds. |
retry-attempts | (Optional) Maximum number of times the communication server will retry failed negotiation attempts. It can be a value from 1 through 100. The default is 3. The communication server intentionally ignores the IPXWAN retry counter and continues to send TIMER_REQUEST packets until it receives a TIMER_RESPONSE packet. |
IPXWAN is disabled.
When enabled, the command has the following defaults:
retry-interval: 20 seconds
retry-attempts: 3
Interface configuration
IPXWAN is a startup 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, Ethernet 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.
If you want 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 1 on device CHICAGO-CS. When the link comes up, CHICAGO-CS will be the master because it has a larger internal network number. It will give the IPX number 100 to NYC-CS 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 communication servers.
On the local communication server (CHICAGO-CS):
interface serial 1
no ipx network
encapsulation ppp
ipx ipxwan 6666 100 CHICAGO-CS
On the remote router (NYC-CS):
interface serial 0
no ipx network
encapsulation ppp
ipx ipxwan 1000 101 NYC-CS
A dagger (†) indicates that the command is documented in another chapter.
encapsulation ppp †
ipx delay
ipx network
show ipx interfaces
To define how to handle IPXWAN when a serial link fails, 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 it fails. This is the default action. |
resume | (Optional) When a link fails, IPXWAN ignores the failure, takes no special action, and resumes the start-up negotiation attempt. |
shutdown | (Optional) Shuts down the link when it fails. |
Reset the link.
Interface configuration
Use the ipx ipxwan error command to define what action to take if the IPXWAN start-up negotiation fails.
In the following example, the serial link will be shut down if the IPXWAN start-up negotiation fails after three attempts spaced 20 seconds apart:
interface serial 0
encapsulation ppp
ipx ipxwan
ipx ipxwan error shutdown
ipx ipxwan
ipx ipxwan static
To enable static routing with IPXWAN, use the ipx ipxwan static interface configuration command. To disable static routing with IPXWAN, use the no form of this command.
ipx ipxwan staticThis command has no arguments and keywords.
Static routing is disabled.
Interface configuration
When you specify the ipx ipxwan static command, the interface negotiates static routing on the link. If the router or communication server at the other side of the link is not configured 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
ipx ipxwan
ipx ipxwan error
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
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
ipx ipxwan
ipx throughput
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 through 254. The default is 16 hops. |
16 hops
Global configuration
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 router never advertises any network with a hop count greater than 15. However, using protocols other than RIP, the router might learn routes that are farther away than 15 hops. The ipx maximum-hops command defines the maximum number of hops that the router will accept as reachable, as well as the maximum number of hops that an IPX packet can traverse before it is dropped by the router. Also, the router 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 router to accept routes that are up to 64 hops away:
ipx maximum-hops 64
To set the maximum number of equal-cost paths the communication server 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 communication server will use. The argument paths can be a value from 1 to 512. The default value is 1. |
1 path
Global configuration
The ipx maximum-paths command is designed to increase throughput by allowing the communication server to choose among several equal-cost, parallel paths. (Note that when paths have differing costs, the communication server chooses lower-cost routes in preference to higher-cost routes.) IPX does 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 communication servers with limited memory or very large configurations. Additionally, in networks with a large number of multiple paths and systems with limited ability to cache out-of-sequence packets, performance might suffer when traffic is split between many paths.
In the following example, the communication server uses up to three parallel paths:
ipx maximum-paths 3
ipx delay
show ipx route
To control incoming IPX NetBIOS 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
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 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 token 1
ipx netbios input-access-filter engineering
ipx netbios output-access filter
netbios access-list
show ipx interface
To control outgoing NetBIOS 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
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 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
The ipx network command allows you to configure 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. You can also use this command to configure a single logical network on a physical network. 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 numberThe 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.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 earlier 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
interface ethernet 0
ipx network 1 encapsulation novell-ether
ipx network 2 encapsulation snap secondary
ipx network 3 encapsulation arpa secondary
ipx network 4 encapsulation sap secondary
ipx routing
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 csnp-interval seconds
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
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 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 enableThis command has no arguments or keywords.
NLSP is disabled on all interfaces.
Interface configuration
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.
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
ipx nlsp rip
ipx nlsp sap
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 hello-interval seconds
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
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 is detected. A router is declared to be down if a hello has not been received from it for three times the hello interval (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.
The following example configures serial interface 0 to transmit hello packets every 30 seconds:
interface serial 0
ipx nlsp hello-interval 30
ipx nlsp csnp-interval
ipx nlsp retransmit-interval
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 metric metric-number
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
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 nlsp metric 10
ipx nlsp enable
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 priority priority-number
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
Use the ipx nlsp priority command to control which router is elected designated router. The router 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 elected designated router, configure its priority to be at least 65.
The following example sets the designated router election priority to 65:
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 retransmit-interval seconds
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
Reducing the retransmission interval can improve the rate of convergence of the network in the face of lossy WAN links at the cost of potentially increasing 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 rip [on | off | auto]
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 or communication server in sending periodic RIP traffic.
Interface configuration
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
ipx nlsp enable
ipx nlsp sap
To configure SAP compatibility when NLSP in enabled, use the ipx nlsp sap interface configuration command. To restore the default, use the no form of this command.
ipx nlsp sap [on | off | auto]
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
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
ipx nlsp enable
ipx nlsp rip
To control which servers are included in the Get Nearest Server (GNS) responses sent by the communication server, 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
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 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
The ipx output-network-filter command controls which networks the communication server 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 interface 1. 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 (standard)
access-list (extended)
ipx input-network-filter
ipx router-filter
To adjust the delay between the individual packets sent in a multiple-packet routing update, 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 milliseconds
milliseconds | Delay, in milliseconds, between packets in a multipacket RIP update. The default delay is 0 (that is, no delay). The delay recommended by Novell is 55 ms. |
No delay between routing update packets
Interface configuration
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 communication server sends them. The delay imposed by the ipx output-sap-delay command forces the communication server interface 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 establishes a 55-ms delay between packets in multiple-packet route updates on serial interface 0:
interface serial 0
ipx network 106A
ipx output-rip-delay 55
ipx update-time
ipx output-sap-delay
To set a delay between packets sent in a multipacket Service Advertisement Protocol (SAP) update, use the ipx output-sap-delay interface configuration command. To disable the delay mechanism, use the no form of this command.
ipx output-sap-delay milliseconds
milliseconds | Delay, in milliseconds, between packets in a multipacket SAP update. The default delay is 0 (that is, no delay). The delay recommended by Novell is 55 ms. |
No delay between SAP update packets.
Interface configuration
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 communication server sends them. The delay imposed by the ipx output-sap-delay command forces the communication server interface 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 establishes a 55-ms delay between packets in multipacket SAP updates on Ethernet interface 0:
interface ethernet 0
ipx network 106A
ipx output-sap-delay 55
ipx sap-interval
To control which services are included in Service Advertisement Protocol (SAP) updates sent by the communication server, 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
The communication server 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
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.
ipx route-cache
To add a static route 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 | default} network.node [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 FFFFFFFE. You do not need to specify leading zeros in the network number. For example, for the network number 000000AA, you can enter just AA. |
default | Default network number as defined by the ipx default-route global configuration command. |
network.node | Communication server 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 FFFFFFFE. You do not need to specify leading zeros in the network number. For example, for the network number 000000AA, you can enter just AA. The argument node is the node number of the target communication server. This is a 48-bit value represented by a dotted triplet of four-digit hexadecimal numbers (xxxx.xxxx.xxxx). |
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
The ipx route command forwards packets destined for the specified network (network) via the specified communication server (network.node), regardless of whether that communication server is sending dynamic routing information.
Be careful when assigning static routes. When links associated with static routes are lost, traffic may stop being forwarded, even though alternative paths might be available.
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 communication server 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 router 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.
Note that by default, floating-static routes are not redistributed into other dynamic protocols.
In the following example, the communication server at address 3abc.0000.0c00.1ac9 handles all traffic destined for network 5e:
ipx routing
ipx route 5e 3abc.0000.0c00.1ac9
show ipx route
To enable IPX fast switching, use the ipx route-cache interface configuration command. To disable fast switching, use the no form of this command.
ipx route-cacheThis command has no arguments or keywords.
Fast switching enabled
Interface configuration
Fast switching allows higher throughput by switching packets using a cache created by previous transit packets. On ciscoBus2 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 or a Token Ring 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.
The following example enables fast switching on an interface:
interface ethernet 0
ipx route-cache
The following example disables fast switching on an interface:
interface ethernet 0
no ipx route-cache
clear ipx cache
ipx source-network-update
ipx watchdog-spoof
show ipx cache
To specify the routing protocol to use, use the ipx router global configuration command.
ipx router {eigrp autonomous-system-number | rip}
eigrp autonomous-system-number | Specifies the IPX Enhanced IGRP routing protocol. The argument autonomous-system-number is the IPX Enhanced IGRP autonomous system number. It can be a decimal integer from 1 to 65535. |
rip | Specifies the RIP routing protocol. It is on by default. |
RIP
Global configuration
You can configure multiple IPX Enhanced IGRP processes on a communication server. To do so, assign each a different autonomous system number.
You must explicitly disable RIP if you do not want to use this routing protocol.
The following example enables IPX Enhanced IGRP on the communication:
ipx router eigrp 4
A dagger (†) indicates that the command is documented in another chapter.
network †
redistribute
To control the communication servers 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
You can issue only one ipx router-filter command on each interface.
In the following example, access list 866 controls the communication servers from which packets are accepted. For Ethernet interface 0, only packets from the communication server 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 (standard)
access-list (extended)
ipx input-network-filter
ipx output-network-filter
To filter Service Advertisement Protocol (SAP) messages received from a particular communication server, 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
You can issue only one ipx router-sap-filter command on each interface.
In the following example, the communication server will receive service advertisements only from communication server 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 communication server. 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 communication server 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 communication server (such as only serial interfaces), you must specify node. |
Disabled
Global configuration
The ipx routing command enables the IPX Routing Information Protocol (RIP) and Service Advertisement Protocol (SAP) services on the communication server.
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 communication server's new address.
If you plan to use DECnet and IPX routing concurrently on the same interface, you should enable DECnet communication server 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
ipx network
To specify static Service Advertisement 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 20-3 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 just 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. Refer to the IPX socket numbers table in the Router Products Command Reference. |
hop-count | Number of hops to the server. |
Disabled
Global configuration
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 communication server 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 communication server 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 serversi
To send SAP updates only when a change occurs in the SAP table, use the ipx sap-incremental eigrp interface configuration command. To send periodic SAP updates, use the no form of this command.
ipx sap-incremental eigrp autonomous-system-number [rsup-only]
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. |
Enabled on serial interfaces
Disabled on LAN media (Ethernet, Token Ring, FDDI)
Interface configuration
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 communication server to send incremental SAP updates on an Ethernet, and if the local communication server 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 communication server.
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 reduce SAP traffic by sending partial SAP updates, specify the rsup-only keyword. SAP updates are then sent only when changes occur, and only changes are sent. This feature works with existing IPX RIP networks and IPX Enhanced IGRP networks.
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 Advertisement 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 minutes
minutes | Interval, in minutes, between SAP updates sent by the communication server. The default value is 1 minute. If minutes is 0, periodic updates are never sent. |
1 minute
Interface configuration
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 communication servers 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, communication servers 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
ipx output-sap-delay
To configure the maximum packet size of 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 seven servers (64 bytes each) plus a 32-byte IPX SAP header. |
480 bytes
Interface configuration
The maximum packet size refers to IPX packets and excludes the media header. For example, to allow ten 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 examples sets the maximum SAP update packet size to 672 bytes:
ipx sap-max-packetsize 672
ipx rip-max-packetsize
To configure the interval at which a network's or server's 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 cache 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
All routers and communication servers 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 rip-multiplier 10
ipx sap-max-packetsize
To configure the maximum length of the queue of pending input 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 communication server stores in this queue. |
No maximum queue size
Global configuration
The communication server maintains a list of SAP requests to process, including all pending Get Nearest Server (GNS) queries from clients attempting to reach servers. When the network is restarted, the communication server 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
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.
This command interferes with the proper working of OS/2 Requestors. Therefore, do not use this command in a network that has OS/2 Requestors.
Do not use the ipx source-network-update command on interfaces on which NetWare servers are using internal network numbers.
 | 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. Also, 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
ipx route-cache
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 | IPX Enhanced IGRP autonomous system number. It can be a decimal integer from 1 to 65535. |
Enabled
Interface configuration
When split horizon is enabled, IPX 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 configure the throughput, use the ipx throughput interface configuration command. To restore the default throughput, use the no form of this command.
ipx throughput bits-per-second
bits-per-second | Throughput, in bits per second. |
No default throughput is defined.
Interface configuration
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 1000000 bits per second:
ipx throughput 1000000
ipx ipxwan
To forward IPX type 20 propagation packet broadcasts to specific network segments, use the ipx type-20-helpered interface configuration command. To disable this function, use the no form of this command.
ipx type-20-helperedThis command has no arguments or keywords.
Disabled
Interface configuration
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 or communication servers 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 devices.
Use of the ipx type-20-helpered command does not comply with the Novell IPX router specification.
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
By default, the communication server 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 communication server 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 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
Communication servers 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-address
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 seconds
seconds | 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
The ipx update-time command sets the routing update timer on a per-interface basis.
Communication servers exchange information about routes by sending broadcast messages when they are brought up and shut down, and periodically while they are running. The ipx update-time command lets you 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 communication servers are our communication servers or in which the IPX communication servers allow configurable timers. The timers should be the same for all communication servers connected to the same cable segment.
The update value you choose affects the internal IPX timers as follows:
The following example sets the update timers on two interfaces in the communication server. 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
show ipx interface
To have the communication server 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
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 communication server 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
ipx route-cache
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 through 120. The default is 5 seconds. |
5 seconds
Router configuration
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
ipx router nlsp
spf-interval
To set the maximum size of a link-state packet (LSP), 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 through 4096. The default is 512 bytes. |
512 bytes
Router configuration
You can increase the LSP MTU if there is a very large amount of information generated by a single router or communication server, because each of these devices is limited to approximately 250 LSPs. In practice, this should never be necessary.
The LSP MTU must be set on every routing device in an area and it must be no 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 router 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 through 50000 seconds. The default is 7200 seconds (2 hours). |
7200 seconds (2 hours)
Router configuration
LSPs must be periodically refreshed before their lifetime expires. 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 (this is an extremely unlikely event, however, because there are other safeguards against corruption) and cause increased link traffic. 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 10800 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 through 50000 seconds. The default is 7500 seconds. |
7500 seconds (2 hours, 5 minutes)
Router configuration
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 11000 seconds (just over 3 hours):
max-lsp-lifetime 11000
ipx router nlsp
lsp-refresh-interval
To define an IPX NetBIOS access list filter, use the netbios access-list global configuration command. To remove a filter, use the no form of this 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 following wildcard character: ♦ **—Match any digits for that byte. |
No filters are predefined.
Global configuration
Keep the following points in mind when configuring IPX NetBIOS access control:
These filters apply only to IPX NetBIOS 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 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. |
EXEC
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.
You cannot ping a communication server from itself.
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 20-4 describes the test characters displayed in ping responses.
| Character | Meaning |
|---|---|
! | Each exclamation point indicates receipt of a reply. |
. | Each period indicates the network server timed out while waiting for a reply. |
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 user ping command:
cs> 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)
ping (privileged)
To check host reachability and network connectivity, use the ping privileged EXEC command.
ping [ipx] [host | address]
ipx | (Optional) Specifies the IPX protocol |
host | (Optional) Host name of system to ping |
address | (Optional) Address of system to ping |
Privileged EXEC
The privileged ping (packet internet groper function) command provides a complete ping facility for users who have system privileges.
You cannot ping a communication server from itself.
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 ping command. 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 20-5 describes the test characters displayed in ping responses.
The following sample display shows input to and output from the ping command:
cs# ping
Protocol [ip]: ipx
Target Novell 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 Novell echoes to 211.0000.0c01.f4cf, timeout is 2 seconds.
!!!!!
Success rate is 100%, round trip min/avg/max = 1/2/4 ms.
ping (user)
To redistribute routing information from one routing domain into another, and vice versa, use the redistribute IPX-router configuration command. To disable this feature, use the no form of this command.
redistribute {connected | eigrp autonomous-system-number | floating-static | 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. |
rip | Specifies the RIP protocol. |
static | Specifies static routes. |
Redistribution is enabled between all routing domains except between separate Enhanced IGRP processes.
Redistribution of floating static routes is disabled.
IPX-router configuration
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.
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:
router eigrp 300
redistribute eigrp 100
ipx route
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. |
EXEC
The following is sample output from the show ipx accounting command:
cs# 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 20-6 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
The following is sample output from the show ipx cache command:
cs# show ipx cache
Novell routing cache version is 9
Destination Interface MAC Header
*1006A Ethernet 0 00000C0062E600000C003EB0064
*14BB Ethernet 1 00000C003E2A00000C003EB0064
Table 20-7 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 | Communication server interface through which this packet is transmitted. |
MAC Header | Contents of this packet's MAC header. |
clear ipx cache
ipx route-cache
To display the neighbors discovered by Enhanced IGRP, use the show ipx eigrp neighbors EXEC command.
show ipx eigrp neighbors [servers] [autonomous-system-number | type number]
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. |
type | (Optional) Interface type. |
number | (Optional) Interface number. |
EXEC
The following is sample output from the show ipx eigrp neighbors command:
cs# show ipx eigrp neighbors
IPX EIGRP Neighbors for process 200
Address Interface Holdtime Uptime Q Seq SRTT RTO
(secs) (h:m:s) Count Num (ms) (ms)
160.0000.0c00.8ea9 Ethernet0 10 2:08:29 0 18 4 20
Table 20-8 explains the fields in the output.
| Field | Description |
|---|---|
process 200 | Autonomous system number specified in the ipx router configuration command. |
H | Handle. An arbitrary and unique number inside this communication server that identifies the neighbor. |
Address | IPX address of the Enhanced IGRP peer. |
Interface | Interface on which the communication server is receiving hello packets from the peer. |
Holdtime | Length of time, in seconds, that the communication server 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 communication server first heard from this neighbor. |
Q Cnt | Number of IPX Enhanced IGRP packets (Update, Query, and Reply) that the communication server 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 communication server to receive an acknowledgment of that packet. |
RTO | Retransmission timeout, in milliseconds. This is the amount of time the communication server waits before retransmitting a packet from the retransmission queue to a neighbor. |
To display the IPX 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
The following is sample output from the show ipx eigrp topology command:
cs# 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 20-9 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 communication server 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 communication server 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 communication server 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:
cs# 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 20-10 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 communication server'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 20-8. 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 communication server. 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 communication server 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. |
show ipx route
To display the status of the IPX interfaces configured in the communication server 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), loopback, null, serial, token ring, or tunnel. |
number | (Optional) Interface number. |
EXEC
The following is sample output from the show ipx interface command:
cs# 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
Table 20-11 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 communication server 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. "line-up" indicates that IPX routing has been enabled with the ipx routing command. "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 network command for a list of possible values. This line is displayed only if you have configured a secondary address with the ipx network command. |
Delay of this Novell network, in ticks, | Value of the ticks field (configured with the ipx delay 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 communication server 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 communication server 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 output-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 output-access-filter bytes command. |
Update time | How often the communication server 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 | 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. |
access-list (standard)
access-list (extended)
access-list (SAP)
ipx accounting
ipx delay
ipx encapsulation
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 entries in the link-state packet (LSP) database, use the show ipx nlsp database EXEC command.
show ipx nlsp database [lspid] [detail]
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:
|
detail | (Optional) Displays the contents of the LSP database entries. If you omit this keyword, only a summary display is shown. |
EXEC
If you omit all options, a summary display is shown.
The following is sample output from the show ipx nlsp database command:
CS> 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.0C02.7471.00-00 0x0000003A 0x4A0F 653 0/0/0
IPX Area Address: 00000000 00000000
IPX Mgmt Info 2.0000.0000.0001 Ver 1 Name georgia
Metric: 45 Lnk 0000.0C02.7471.0A MTU 1500 Dly 50 Thru 56K Generic LAN
Metric: 20 Lnk 0000.0C06.FBEE.0E MTU 1500 Dly 1000 Thru 10000K 802.3 Raw
Metric: 20 Lnk 0000.0C02.7471.08 MTU 1500 Dly 10000 Thru 10000K 802.3 Raw
0000.0C02.7471.08-00 0x00000027 0x0AF0 647 0/0/0
IPX Mgmt Info C3.0000.0c02.7474 Ver 1 Name Ethernet3
Metric: 0 Lnk 0000.0C02.7471.00 MTU 0 Dly 0 Thru 0K Generic LAN
0000.0C02.7471.0A-00 0x00000027 0xC589 641 0/0/0
IPX Mgmt Info 0.0000.0000.0000 Ver 1 Name Statics
Metric: 0 Lnk 0000.0C02.7471.00 MTU 0 Dly 0 Thru 0K Generic LAN
Table 20-12 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. |
To display the communication server's NLSP neighbors and their states, use the show ipx nlsp neighbors EXEC command.
show ipx nlsp neighbor [interface] [detail]
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
If you omit the keyword detail, a summary display is shown.
The following is sample output from the show ipx nlsp neighbors command:
cs> 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 20-13 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 the contents of the IPX routing table, use the show ipx route EXEC command.
show ipx route [network]
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 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 just enter AA. |
EXEC
The following is sample output from the show ipx route command:
cs> show ipx route
Codes: C - Connected primary network, c - Connected secondary network
R - RIP, E - EIGRP, S - static, W - IPXWAN connected
8 Total IPX routes
No parallel paths allowed Novell routing algorithm variant in use
E Net 1 [307200/0] via 2.0000.0c05.84b6, age 0:01:25,
1 uses, Ethernet2
C Net 2 (NOVELL-ETHER), is directly connected, 30 uses, Ethernet2
E Net 3 [2195456/0] via 2.0000.0c05.84b6, age 0:01:25,
1 uses, Ethernet2
E Net 11 [281600/0] via 2.0000.0c05.84b6, age 0:01:25,
1 uses, Ethernet2
c Net 2000 (SAP), is directly connected, 3 uses, Ethernet2
R Net 22 [1/1] via 2.0000.0c05.84b6, 13 sec, 1 uses, Ethernet2
C Net 55 (NOVELL-ETHER), is directly connected, 30 uses, Ethernet3
S Net 70 via 55.0011.0022.0033, 1 uses, Ethernet3
Table 20-14 describes the fields shown in the display.
| Field | Description |
|---|---|
Codes | Codes defining how the route was learned. |
C | Directly connected primary network. |
c | Directly connected secondary network |
R | Route learned from a RIP update. |
E | Route learned from an Enhanced IGRP update. |
S | Statically defined route via the ipx route command. |
W | Directly connected route determined via IPXWAN. |
8 Total IPX routes | Numbers of routes in the IPX routing table. |
No parallel paths allowed | Maximum number of parallel paths for which the communication server has been configured with the ipx maximum-paths command. |
Novell routing algorithm variant in use | Indicates whether the communication server 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 communication server that is the next hop to the remote network. |
age | Amount of time, in hours, minutes, and seconds, that has elapsed since information about this network was last received. |
uses | Number of times this network has been looked up in the route table. This field is incremented when a packet is process-switched, even if the packet is eventually filtered and not sent. As such, this field represents a fair estimate of the number of times a route gets used. |
Ethernet0 | Interface through which packets to the remote network will be sent. |
(NOVELL-ETHER) | Encapsulation (frame) type. This is shown only for directly connected networks. |
is directly connected | Indicates that the network is directly connected to the communication server. |
clear ipx route
ipx maximum-paths
ipx route
To list the IPX servers discovered through SAP advertisements, use the show ipx servers EXEC command.
show ipx servers [sorted [name | net | type]]
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. |
type
EXEC
The following is sample output from the show ipx servers command:
cs> show ipx servers
Codes: R - RIP, E - EIGRP, C - connected, S - static, 5 Total IPX routes
No parallel paths allowed Novell routing algorithm variant in use
E Net 42 [345088/2] via 160.0000.0c00.8ea9, age 2d21 1 uses, Ethernet0
C Net FFFF01 (NOVELL-ETHER), is directly connected, 33 uses, Ethernet3
R Net E04 [120/2] via 165.0000.0c01.d879, 17 sec, 1 uses, Ethernet0
R Net E02 [120/2] via 165.0000.0c01.d879, 17 sec, 2 uses, Ethernet0
R Net E03 [120/2] via 165.0000.0c01.d879, 17 sec, 57 uses, Ethernet0
C Net CC00C1 (HDLC), is directly connected, 0 uses, serial3, (down)
Table 20-15 describes the fields shown in the display.
| Field | Description |
|---|---|
Codes | Codes defining how the route was learned. |
R | Route learned from a RIP update. |
E | Route learned via Enhanced IGRP. |
C | Directly connected network. |
S | Statically defined route via the ipx route command. |
No parallel paths allowed | Maximum number of parallel paths for which the communication server has been configured with the ipx maximum-paths command. |
Novell routing algorithm variant in use | Indicates whether the communication server is using the IPX-compliant routing algorithms (default). |
sec | Number of seconds that have elapsed since information about this network was last received. |
uses | Fair estimate of the number of times a route gets used. It actually indicates the number of times the route has been selected for use prior to operations such as access list filtering. |
Ethernet0 | Possible interface through which updates to the remote network will be sent. |
(NOVELL-ETHER) | Encapsulation type. This is shown only for directly connected networks. |
is directly connected | Indicates that the network is directly connected to the communication server. |
Net E04 | Network to which the route goes. |
[345088/2] | The first number is the Enhanced IGRP metric, and the second number is the external hop count (for routes learned from Enhanced IGRP). The external hop count is the hop count that was advertised when this destination first entered the Enhanced IGRP autonomous system. If the external hop count is 0, this is an internal Enhanced IGRP route. When this destination is announced via RIP by this communication server, the communication server will add one to this value and use the result as the RIP hop count. The external hop count is not incremented when the destination is advertised via Enhanced IGRP. |
[120/2] | Ticks/metric (for routes learned from RIP). Ticks are the number of IBM clock ticks (1/18th second). When ipx algorithms is enabled, hop count is used as a tie-breaker between routes if the tick count is the same. The metric is the IPX metric used in making routing decisions. |
age | (For routes learned from Enhanced IGRP only.) Length of time since this route was first learned. The time is represented in the format hh:mm:ss until 24 hours have elapsed, after which it is represented dd:hh until one week has elapsed. After one week, the age is represented wade. |
via network.node | Address of a router that is the next hop to the remote network. |
ipx sap
To display information about the number and type of IPX packets transmitted and received by the communication server, use the show ipx traffic user EXEC command.
show ipx trafficThis command has no arguments or keywords.
EXEC
The following is sample output from the show ipx traffic command:
cs> 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
61 SAP advertisements received, 120 sent
0 SAP flash updates sent, 0 SAP poison 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
Table 20-16 describes the fields that might possibly be shown in the display.
| Field | Description |
|---|---|
Rcvd: | Description of the packets the communication server has received. |
644 total | Total number of packets the communication server has received. |
1705 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 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). |
0 packets pitched | Number of times the communication server received its own broadcast packet. |
644 local destination | Number of packets sent to the local broadcast address or specifically to the communication server. |
0 multicast | Number of packets received that were addressed to multiple destinations. |
Bcast: | Description of the broadcast packets the communication server has received and sent. |
589 received | Number of broadcast packets received. |
324 sent | Number of broadcast packets sent. It includes broadcast packets the communication server is either forwarding or has generated. |
Sent: | Description of those packets that the communication server generated and then sent, and also those the communication server has received and then routed to other destinations. |
380 generated | Number of packets the communication server transmitted that it generated itself. |
0 forwarded | Number of packets the communication server transmitted that it forwarded from other sources. |
0 encapsulation failed | Number of packets the communication server was unable to encapsulate. |
4 no route | Number of times the communication server could not locate a route to the destination in the routing table. |
SAP: | Description of the SAP packets the communication server has sent and received. |
1 SAP requests | Number of SAP requests the communication server has received. |
1 SAP replies | Number of SAP replies the communication server has sent in response to SAP requests. |
61 SAP advertisements | Number of SAP advertisements the communication server has received from another router. |
120 sent | Number of SAP advertisements the communication server has generated and then sent. |
0 SAP flash updates sent | Number of SAP advertisements the communication server has generated and then sent as a result of a change in its routing table. |
0 SAP poison sent | Number of times the communication server has generated an update indicating that a service is no longer reachable. |
0 SAP format errors | Number of SAP advertisements that were incorrectly formatted. |
RIP: | Description of the RIP packets the communication server has sent and received. |
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 communication server's routing table. |
Watchdog: | Description of the watchdog packets the communication server has handled. |
0 packets received | Number of watchdog packets the communication server has received from IPX servers on the local network. |
0 replies spoofed | Number of times the communication server has responded to a watchdog packet on behalf of the remote client. |
Echo: | Description of the ping replies and requests the communication server has sent and received. |
Rcvd 55 request 0 replies | Number of ping requests and replies received by the communication server. |
Sent 0 requests, 55 replies | Number of ping requests and replies sent by the communication server. |
0 unknown | Number of incomprehensible ping packets received by the communication server. |
0 SAPs throttled | Number of ping 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 | 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 communication server has sent and received. |
Updates | Number of Enhanced IGRP updates the communication server has sent and received. |
Queries | Number of Enhanced IGRP queries the communication server has sent and received. |
Replies | Number of Enhanced IGRP replies the communication server has sent and received. |
SAPs | Number of SAP packets the communication server has sent to and received from Enhanced IGRP neighbors. |
unknown counter | Number of packets the communication server was unable to forward, for example, because of a misconfigured helper address or because no route was available. |
To control how often the communication server 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 Shortest Path First (SPF) calculations, in seconds. It can be a number in the range 1 through 120. The default is 5 seconds. |
5 seconds
Router configuration
SPF calculations are performed only when the router or communication server topology changes. They are not performed when external routes change.
The spf-interval command controls how often the communication server can perform the Shortest Path First (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 communication server, 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
lsp-gen-interval
Posted: Mon Oct 21 12:31:33 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.