Novell IPX Commands

Novell Internet Packet Exchange (IPX) is derived from the Xerox Network Systems (XNS) Internet Datagram Protocol (IDP). One major difference between IPX and XNS is that they do not always use the same Ethernet encapsulation format. A second difference is that IPX uses Novell's proprietary Service Advertisement Protocol (SAP) to advertise special network services.

Our implementation of Novell's IPX protocol has been certified as providing full IPX access server functionality. Our access 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 access 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.

access-list (extended)

To define an extended Novell IPX access list, use the extended version of the access-list global configuration command. To remove an extended access list, use the no form of this command.

Syntax Description

Default

No access lists are predefined.

Command Mode

Global configuration

Usage Guidelines

Extended IPX access lists filter on protocol type. All other parameters are optional.

If a network mask is used, all other fields are required.

Use the ipx access-group command to assign an access list to an interface. You can apply only one extended or one standard access list to an interface. The access list filters all outgoing packets on the interface.

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.

Examples

The 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

Related Commands

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⁺

access-list (SAP filtering)

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.

Syntax Description

Default

No access lists are predefined.

Command Mode

Global configuration

Usage Guidelines

When configuring SAP filters for NetWare 3.11 and later servers, use the server's internal network and node number (the node number is always 0000.0000.0001) as its address in the access-list command. Do not use the network.node address of the particular interface board.

Table 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.

Example

The following access list blocks all access to a file server (service type 4) on the directly attached network by resources on other Novell networks, but allows access to all other available services on the interface:

access-list 1001 deny -1 4
access-list 1001 permit -1

Related Commands

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⁺

access-list (standard)

To define a standard IPX access list, use the standard version of the access-list global configuration command. To remove a standard access list, use the no form of this command.

Syntax Description

Default

No access lists are predefined.

Command Mode

Global configuration

Usage Guidelines

Standard IPX access lists filter on the source network. All other parameters are optional.

Use the ipx access-group command to assign an access list to an interface. You can apply only one extended or one standard access list to an interface. The access list filters all outgoing packets on the interface.

To delete a standard access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:

To delete the access list for a specific network, use the following command:

Examples

The 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

or

access-list 800 deny 1.1111.1111.1111 2.2222.2222.2222

Related Commands

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 ⁺

area-address

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.

Syntax Description

Default

No area address is defined by default.

Command Mode

Router configuration

Usage Guidelines

You must configure at least one area address before NLSP will operate.

The area-address command defines a prefix that includes all networks 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 access 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.

Examples

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

Related Command

ipx router nlsp

clear ipx accounting

To delete all entries in the active accounting database when IPX accounting is enabled, use the clear ipx accounting EXEC command.

Syntax Description

Command Mode

EXEC

Usage Guidelines

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.

Example

The following example clears all entries in the active database:

clear ipx accounting

Related Commands

ipx accounting
ipx accounting-list
ipx accounting-threshold
ipx accounting-transits
show ipx accounting

clear ipx cache

To delete entries from the IPX fast-switching cache, use the clear ipx cache EXEC command.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The clear ipx cache command clears entries used for fast switching.

Example

The following example deletes all entries from the IPX fast-switching cache:

clear ipx cache

Related Commands

ipx route-cache
show ipx cache

clear ipx nlsp neighbors

To delete all NLSP adjacencies from the router's adjacency database, use the clear ipx nlsp neighbors EXEC command.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

Deleting all entries from the adjacency database forces all routers in the area to perform the shortest path first (SPF) calculation.

Example

The following example deletes all NLSP adjacencies from the router's adjacency database:

clear ipx nlsp neighbors

Related Commands

ipx router nlsp
spf-interval

clear ipx route

To delete routes from the IPX routing table, use the clear ipx route EXEC command.

Syntax Description

Command Mode

EXEC

Usage Guidelines

After you use the clear ipx route command, RIP/SAP general requests are issued on all IPX interfaces.

Example

The following example clears the entry for network 3 from the IPX routing table:

clear ipx route 3

Related Command

show ipx route

distribute-list in

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.

Syntax Description

Default

Disabled

Command Mode

Router configuration

Example

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

Related Commands

A dagger (⁺) indicates that the command is documented in another chapter.

access-list ⁺
distribute-list out
redistribute

distribute-list out

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.

Syntax Description

Default

Disabled

Usage Guidelines

When redistributing networks, a routing process name can be specified as an optional trailing argument to the distribute-list out command. This causes the access list to be applied to only those routes derived from the specified routing process. After the process-specific access list is applied, any access list specified by a distribute-list out command without a process name argument is applied. Addresses not specified in the distribute-list out command are not advertised in outgoing routing updates.

Example

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

Related Commands

A dagger (⁺) indicates that the command is documented in another chapter.

access-list ⁺
distribute-list in
redistribute

ipx access-group

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.

Syntax Description

Default

No filters are predefined.

Command Mode

Interface configuration

Usage Guidelines

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.

Example

In the following example, access list 801 is applied to Ethernet interface 1:

interface ethernet 1
 ipx access-group 801

Related Commands

A dagger (⁺) indicates that the command is documented in another chapter.

access-list (standard)
access-list (SAP filtering)
priority-list protocol ⁺

ipx accounting

To enable IPX accounting, use the ipx accounting interface configuration command. To disable IPX accounting, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Interface configuration

Usage Guidelines

IPX accounting allows you to collect information about IPX packets and the number of bytes that are switched through the access server. You collect information based on the source and destination IPX address. Accounting tracks only IPX traffic that is passing out of the access server; it does not track traffic generated by or terminating at the access 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 access server software maintains two accounting databases: an active database and a checkpointed database.

Example

The following example enables IPX accounting on Ethernet interface 0:

interface ethernet 0
 ipx accounting

Related Commands

clear ipx accounting
ipx accounting-list
ipx accounting-threshold
ipx accounting-transits
show ipx accounting

ipx accounting-list

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.

Syntax Description

Default

No filters are predefined.

Command Mode

Global configuration

Usage Guidelines

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.

Example

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

Related Commands

clear ipx accounting
ipx accounting
ipx accounting-threshold
ipx accounting-transits
show ipx accounting

ipx accounting-threshold

To set the maximum number of accounting database entries, use the ipx accounting-threshold global configuration command. To restore the default, use the no form of this command.

Syntax Description

Default

512 entries

Command Mode

Global configuration

Usage Guidelines

The accounting threshold defines the maximum number of entries (source and destination address pairs) that the access server accumulates. The threshold is designed to prevent IPX accounting from consuming all available free memory. This level of memory consumption could occur in an access server that is switching traffic for many hosts. To determine whether overflows have occurred, used the show ipx accounting EXEC command.

Example

The following example sets the IPX accounting database threshold to 500 entries:

ipx accounting-threshold 500

Related Commands

clear ipx accounting
ipx accounting
ipx accounting-list
ipx accounting-list
show ipx accounting

ipx accounting-transits

To set the maximum number of transit entries that will be stored in the IPX accounting database, use the ipx accounting-transits global configuration command. To disable this function, use the no form of this command.

Syntax Description

Default

0 entries

Command Mode

Global configuration

Usage Guidelines

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 access server software maintains two accounting databases: an active database and a checkpointed database.

Example

The following example specifies a maximum of 100 transit records to be stored in the IPX accounting database:

ipx accounting-transits 100

Related Commands

clear ipx accounting
ipx accounting
ipx accounting-list
ipx accounting-threshold
show ipx accounting

ipx advertise-default-route-only

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.

Syntax Description

Default

Disabled. All default routes are advertised.

Command Mode

Interface configuration

Usage Guidelines

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.

Example

The following example enables the advertising of the RIP default route only:

ipx advertise-default-route-only 3c.7389.4339

ipx backup-server-query-interval

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.

Syntax Description

Default

15 seconds

Command Mode

Global configuration

Usage Guidelines

A lower interval may use more CPU resources, but may cause lost server information to be retrieved from other servers' tables sooner.

Example

The following example changes the server query time to 5 seconds:

ipx backup-server-query-interval 5

ipx default-output-rip-delay

To set the default interpacket delay for Routing Information Protocol (RIP) updates sent on all interfaces, use the ipx default-output-rip-delay global configuration command. To return to the initial default delay value, use the no form of this command.

Syntax Description

Default

With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between routing update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.

Command Mode

Global configuration

Usage Guidelines

The interpacket delay is the delay between the individual packets sent in a multiple-packet routing update. The ipx default-output-rip-delay command sets a default interpacket delay for all interfaces.

The system uses the delay specified by the ipx default-output-rip-delay command for periodic and triggered routing updates when no delay is set for periodic and triggered routing updates on an interface. When you set a delay for triggered routing updates, the system uses the delay specified by the ipx default-output-rip-delay command for only the periodic routing updates sent on all interfaces.

To set a delay for triggered routing updates, see the ipx triggered-rip-delay or ipx default-triggered-rip-delay commands.

Novell recommends a delay of 55 ms for compatibility with older and slower IPX machines. These machines may lose RIP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX machines.

The default delay on a NetWare 3.11 server is about 100 ms.

This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.

Example

The following example sets a default interpacket delay of 55 ms for RIP updates sent on all interfaces:

ipx default-output-rip-delay 55

Related Command

ipx default-triggered-rip-delay
ipx output-rip-delay
ipx triggered-rip-delay

ipx default-output-sap-delay

To set a default interpacket delay for Service Advertisement Protocol (SAP) updates sent on all interfaces, use the ipx default-output-sap-delay global configuration command. To return to the initial default delay value, use the no form of this command.

Syntax Description

Default

With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.

Command Mode

Global configuration

Usage Guidelines

The interpacket delay is the delay between the individual packets sent in a multiple-packet SAP update. The ipx default-output-sap-delay command sets a default interpacket delay for all interfaces.

The system uses the delay specified by the ipx default-output-sap-delay command for periodic and triggered SAP updates when no delay is set for periodic and triggered updates on an interface. When you set a delay for triggered updates, the system uses the delay specified by the ipx default-output-sap-delay command only for the periodic SAP updates sent on all interfaces.

To set a delay for triggered updates, see the ipx triggered-sap-delay or ipx default-triggered-sap-delay commands.

Novell recommends a delay of 55 ms for compatibility with older and slower IPX servers. These servers may lose SAP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these servers.

The default delay on a NetWare 3.11 server is about 100 ms.

This command is also useful on limited bandwidth point-to-point links or X.25 interfaces.

Example

The following example sets a default interpacket delay of 55 ms for SAP updates sent on all interfaces:

ipx default-output-sap-delay 55

Related Command

ipx default-triggered-sap-delay
ipx output-sap-delay
ipx triggered-sap-delay

ipx default-route

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.

Syntax Description

This command has no arguments or keywords.

Default

Enabled; that is, all packets for which a route to the destination is unknown are forwarded towards the default network, which is -2.

Command Mode

Global configuration

Example

The following example disables the forwarding of packets towards the default network:

no ipx default-route

Related Command

ipx advertise-default-route-only

ipx default-triggered-rip-delay

To set the default interpacket delay for triggered Routing Information Protocol (RIP) updates sent on all interfaces, use the ipx default-triggered-rip-delay global configuration command. To return to the system default delay, use the no form of this command.

Syntax Description

Default

With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between routing update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.

Command Mode

Global configuration

Usage Guidelines

The interpacket delay is the delay between the individual packets sent in a multiple-packet routing update. A triggered routing update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.

The ipx default-triggered-rip-delay command sets the default interpacket delay for triggered routing updates sent on all interfaces. On a single interface, you can override this global default delay for triggered routing updates using the ipx triggered-rip-delay interface command.

The global default delay for triggered routing updates overrides the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered routing updates.

If the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command is high, then we strongly recommend a low delay value for triggered routing updates so that updates triggered by special events are sent in a more timely manner than periodic routing updates.

Novell recommends a delay of 55 ms for compatibility with older and slower IPX machines. These machines may lose RIP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX machines.

The default delay on a NetWare 3.11 server is about 100 ms.

When you do not set the interpacket delay for triggered routing updates, the system uses the delay specified by the ipx output-rip-delay or ipx default-output-rip-delay command for both periodic and triggered routing updates.

When you use the no form of the ipx default-triggered-rip-delay command, the system uses the delay set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered RIP updates, if set. Otherwise, the system uses the initial default delay as described in the "Default" section.

This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.

Example

The following example sets an interpacket delay of 55 ms for triggered routing updates sent on all interfaces:

ipx default-triggered-rip-delay 55

Related Command

ipx default-output-rip-delay
ipx output-rip-delay
ipx triggered-rip-delay

ipx default-triggered-sap-delay

To set the default interpacket delay for triggered Service Advertisement Protocol (SAP) updates sent on all interfaces, use the ipx default-triggered-sap-delay global configuration command. To return to the system default delay, use the no form of this command.

Syntax Description

Default

With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.

Command Mode

Global configuration

Usage Guidelines

The interpacket delay is the delay between the individual packets sent in a multiple-packet SAP update. A triggered SAP update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.

The ipx default-triggered-sap-delay command sets the default interpacket delay for triggered SAP updates sent on all interfaces. On a single interface, you can override this global default delay for triggered updates using the ipx triggered-sap-delay interface command.

The global default delay for triggered updates overrides the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered updates.

If the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command is high, then we strongly recommend a low delay value for triggered updates so that updates triggered by special events are sent in a more timely manner than periodic updates.

Novell recommends a delay of 55 ms for compatibility with older and slower IPX servers. These servers may lose SAP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX servers.

The default delay on a NetWare 3.11 server is about 100 ms.

When you do not set the interpacket delay for triggered SAP updates, the system uses the delay specified by the ipx output-sap-delay or ipx default-output-sap-delay command for both periodic and triggered SAP updates.

When you use the no form of the ipx default-triggered-sap-delay command, the system uses the delay set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered SAP updates, if set. Otherwise, the system uses the initial default delay as described in the "Default" section.

This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.

Example

The following example sets an interpacket delay of 55 ms for triggered SAP updates sent on all interfaces:

ipx default-triggered-sap-delay 55

Related Command

ipx default-output-sap-delay
ipx output-sap-delay
ipx triggered-sap-delay

ipx delay

To set the tick count, use the ipx delay interface configuration command. To reset the default increment in the delay field, use the no form of this command.

Syntax Description

Default

The default delay is determined from the delay configured on the interface with the delay command. It is (interface delay + 333) / 334. Therefore, unless you change the delay by a value greater than 334, you will not notice a difference.

Command Mode

Interface configuration

Usage Guidelines

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.

Example

The following example changes the delay for serial interface 0 to 10 ticks:

interface serial 0
 ipx delay 10

Related Commands

A dagger (⁺) indicates that the command is documented in another chapter.

delay⁺
ipx maximum-paths
ipx output-network-filter
ipx output-rip-delay

ipx down

To administratively shut down an IPX network, use the ipx down interface configuration command. To restart the network, use the no form of this command.

Syntax Description

Default

Disabled

Command Mode

Interface configuration

Usage Guidelines

The ipx down command administratively shuts down the specified network. The network still exists in the configuration, but is not active. When shutting down, the network sends out update packets informing its neighbors that it is shutting down. This allows the neighboring systems to update their routing, SAP, and other tables without having to wait for routes and services learned via this network to time out.

To shut down an interface in a manner that is considerate of one's neighbor, use ipx down before using the shutdown command.

Example

The following example administratively shuts down network AA on Ethernet interface 0:

interface ethernet 0
 ipx down AA

ipx gns-reply-disable

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.

Syntax Description

This command has no arguments or keywords.

Default

Replies are sent to IPX GNS queries.

Command Mode

Interface configuration

Example

The following example disables the sending of replies to GNS queries on Ethernet interface 0:

interfac e ethernet 0
 ipx gns-reply-disable

Related Commands

ipx gns-response-delay

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.

Syntax Description

Default

0 milliseconds (no delay)

Command Mode

Global configuration

Usage Guidelines

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 access server does. It is desirable to have these end-host server systems get their reply to the client before the access 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 access 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.

Example

The following example sets the delay in responding to GNS requests to 500 milliseconds (0.5 second):

ipx gns-response-delay 500

Related Command

ipx gns-reply-disable

ipx gns-round-robin

To rotate using a round-robin selection method through a set of eligible servers when responding to Get Nearest Server (GNS) requests, use the ipx gns-round-robin global configuration command. To use the most recently learned server, use the no form of this command.

Syntax Description

The command has no arguments or keywords.

Default

The most recently learned, eligible server is used.

Command Mode

Global configuration

Usage Guidelines

In the normal server selection process, requests for service are responded to with the most recently learned, closest server. If you enable the round-robin method, the access 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 access 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.

Example

The following example responds to GNS requests using a round-robin selection method from a list of eligible nearest servers:

ipx gns-round-robin 

Related Commands

ipx output-gns-filter
ipx output-sap-filter

ipx hello-interval eigrp

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.

Syntax Description

Default

5 seconds

Command Mode

Interface configuration

Usage Guidelines

If the current value for the hold time is less than two times the interval between hello packets, the hold time will be reset.

Example

The following example changes the hello interval to 10 seconds:

interface ethernet 0
 ipx network 10
 ipx hello-interval eigrp 4 10

Related Command

ipx hold-time eigrp

ipx helper-address

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.

Syntax Description

Default

Disabled

Command Mode

Interface configuration

Usage Guidelines

Routers normally block all broadcast requests and do not forward them to other network segments. This is done to prevent the degradation of performance over the entire network. The ipx helper-address command allows broadcasts to be forwarded to other networks (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 access 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 access 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.

Example

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

Related Commands

ipx helper-list
ipx type-20-propagation

ipx helper-list

To assign an access list to an interface to control broadcast traffic (including type 20 propagation packets), use the ipx helper-list interface configuration command. To remove the access list from an interface, use the no form of this command.

Syntax Description

Default

No access list is preassigned.

Command Mode

Interface configuration

Usage Guidelines

The ipx helper-list command specifies an access list to use in forwarding broadcast packets. One use of this command is to prevent client nodes from discovering services they should not use.

Because the destination address of a broadcast packet is by definition the broadcast address, this command is useful only for filtering based on the source address of the broadcast packet.

The helper list, if present, is applied to both all-nets broadcast packets and type 20 propagation packets.

The helper list on the input interface is applied to packets before they are output via either the helper address or type 20 propagation packet mechanism.

You should filter IPX broadcasts on dial-on-demand routing (DDR) and other similar interfaces, because IPX sends broadcast messages very regularly.

Example

The following example assigns access list 900 to Ethernet interface 0 to control broadcast traffic:

interface ethernet 0
 ipx helper-list 900

Related Commands

access-list (standard)
access-list (SAP filtering)
ipx helper-address
ipx type-20-propagation

ipx hold-time eigrp

To specify the length of time a neighbor should consider Enhanced IGRP hello packets valid, use the ipx hold-time eigrp interface configuration command. To restore the default time, use the no form of this command.

Syntax Description

Default

15 seconds

Command Mode

Interface configuration

Usage Guidelines

If the current value for the hold time is less than two times the interval between hello packets, the hold time will be reset to three times the hello interval.

If a router does not receive a hello packet within the specified hold time, routes through the router are considered available.

Increasing the hold time delays route convergence across the network.

Example

The following example changes the hold time to 45 seconds:

interface ethernet 0
 ipx network 10
 ipx hold-time eigrp 4 45

Related Command

ipx hello-interval eigrp

ipx input-network-filter

To control which networks are added to the access 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.

Syntax Description

Default

No filters are predefined.

Command Mode

Interface configuration

Usage Guidelines

The ipx input-network-filter command controls which networks are added to the routing table based on the networks learned in incoming IPX routing updates (RIP updates) on the interface.

You can issue only one ipx input-network-filter command on each interface.

Examples

In the following example, access list 876 controls which networks are added to the routing table when IPX routing updates are received on Ethernet interface 1. Routing updates for network 1b will be accepted. Routing updates for all other networks are implicitly denied and are not added to the routing table.

access-list 876 permit 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

Related Commands

access-list (standard)
access-list (SAP filtering)
ipx output-network-filter
ipx router-filter

ipx input-sap-filter

To control which services are added to the access server's SAP table, use the ipx input-sap-filter interface configuration command. To remove the filter, use the no form of this command.

Syntax Description

Default

No filters are predefined.

Command Mode

Interface configuration

Usage Guidelines

The ipx input-sap-filter command filters all incoming service advertisements received by the access server. This is done prior to an access 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.

Example

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

Related Commands

access-list (SAP filtering)
ipx output-sap-filter
ipx router-sap-filter

ipx internal-network

To set an internal network number for use by NLSP and IPXWAN, use the ipx internal-network global configuration command. To remove an internal network number, use the no form of this command.

Syntax Description

Default

No internal network number is set.

Command Mode

Global configuration

Usage Guidelines

An internal network number is a number assigned to the access server.

You must configure an internal network number on each access server on an NLSP-capable network in order for NLSP to operate.

When you set an internal network number, the access server advertises the specified network out all interfaces. It accepts packets destined to that network at the address internal-network.0000.0000.0001.

Example

The following example assigns internal network number e001 to the local router:

ipx routing
ipx internal-network e001

Related Commands

ipx router nlsp
ipx router

ipx ipxwan

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.

Syntax Description

Default

IPXWAN is disabled.

If you enable IPXWAN, the default is unnumbered.

Command Mode

Interface configuration

Usage Guidelines

If you omit all optional arguments and keywords, the ipx ipxwan command defaults to ipx ipxwan 0 unnumbered router-name (which is equivalent to ipx ipxwan 0 local-server-name), where router-name is the name of the router as configured with the hostname global configuration command. For this configuration, the show ipx interface command displays ipx ipxwan 0 0 local-server-name.

If you enter a value of 0 for the network-number argument, the output of the show running-config EXEC command does not show the 0 but rather reports this value as "unnumbered."

The name of each router on each side of the link must be different.

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.

Example

The following example enables IPXWAN on serial interface 1 on device CHICAGO-AS. When the link comes up, CHICAGO-AS will be the master because it has a larger internal network number. It will give the IPX number 100 to NYC-AS to use as the network number for the link. The link delay, in ticks, will be determined by the exchange of packets between the two access servers.

On the local access server (CHICAGO-AS):

interface serial 1
 no ipx network
 encapsulation ppp
 ipx ipxwan 6666 100 CHICAGO-AS

On the remote router (NYC-AS):

interface serial 0
 no ipx network
 encapsulation ppp
 ipx ipxwan 1000 101 NYC-AS

Related Commands

A dagger (⁺) indicates that the command is documented in another chapter.

encapsulation ppp ⁺
ipx delay
ipx network
show ipx interface

ipx ipxwan error

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.

Syntax Description

Default

Reset the link.

Command Mode

Interface configuration

Usage Guidelines

Use the ipx ipxwan error command to define what action to take if the IPXWAN start-up negotiation fails.

Example

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

Related Commands

ipx ipxwan
ipx ipxwan static

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.

Syntax Description

This command has no arguments and keywords.

Default

Static routing is disabled.

Command Mode

Interface configuration

Usage Guidelines

When you specify the ipx ipxwan static command, the interface negotiates static routing on the link. If the router or access server at the other side of the link is not configured for static routing, the link will not initialize.

Example

The following example enables static routing with IPXWAN:

interface serial 0
 encapsulation ppp
 ipx ipxwan 
 ipx ipxwan static

Related Commands

ipx ipxwan
ipx ipxwan error

ipx link-delay

To specify the link delay, use the ipx link-delay interface configuration command. To return to the default link delay, use the no form of this command.

Syntax Description

Default

No link delay (delay of 0)

Command Mode

Interface configuration

Usage Guidelines

The link delay you specify replaces the default value or overrides the value measured by IPXWAN when it starts. The value is also supplied to NLSP for use in metric calculations.

Example

The following example sets the link delay to 20 microseconds:

ipx link-delay 20

Related Commands

ipx ipxwan
ipx spx-idle-time

ipx maximum-hops

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.

Syntax Description

Default

16 hops

Command Mode

Global configuration

Usage Guidelines

Packets whose hop count is equal to or greater than that specified by the ipx maximum-hops command are dropped.

In periodic RIP updates, the 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.

Example

The following command configures the router to accept routes that are up to 64 hops away:

ipx maximum-hops 64

ipx maximum-paths

To set the maximum number of equal-cost paths the access 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.

Syntax Description

Default

1 path

Command Mode

Global configuration

Usage Guidelines

The ipx maximum-paths command is designed to increase throughput by allowing the access server to choose among several equal-cost, parallel paths. (Note that when paths have differing costs, the access 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 access 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.

Example

In the following example, the access server uses up to three parallel paths:

ipx maximum-paths 3

Related Commands

ipx delay
show ipx route

ipx netbios input-access-filter

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.

Syntax Description

Default

No filters are predefined.

Command Mode

Interface configuration

Usage Guidelines

You can issue only one ipx netbios input-access-filter host and one ipx netbios input-access-filter bytes command on each interface.

These filters apply only to IPX NetBIOS packets. They have no effect on LLC2 NetBIOS packets.

Example

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

Related Commands

ipx netbios output-access-filter
netbios access-list
show ipx interface

ipx netbios output-access-filter

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.

Syntax Description

Default

No filters are predefined.

Command Mode

Interface configuration

Usage Guidelines

You can issue only one ipx netbios output-access-filter host and one ipx netbios output-access-filter bytes command on each interface.

These filters apply only to IPX NetBIOS packets. They have no effect on LLC2 NetBIOS packets.

Example

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

Related Commands

ipx netbios input-access-filter
netbios access-list
show ipx interface

ipx network

To enable IPX routing on a particular interface and to optionally select the type of encapsulation (framing), use the ipx network interface configuration command. To disable IPX routing, use the no form of this command.

Syntax Description

Default

IPX routing is disabled.

Encapsulation types:

• For Ethernet: novell-ether

• For Token Ring: sap

Command Mode

Interface configuration

Usage Guidelines

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:

Deleting the primary network with the following command also deletes all networks on that interface. The argument number is the number of the primary network.

To delete a secondary network on an interface, use one of the following commands. The argument number is the number of a secondary network.

Examples

The following example uses subinterfaces to create four logical networks on Ethernet interface 0. Each subinterface has a different encapsulation. Any interface configuration parameters that you specify on an individual subinterface are applied to that subinterface only.

ipx 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

Related Command

ipx routing

ipx nlsp csnp-interval

To configure the NLSP complete sequence number PDU (CSNP) interval, use the ipx nlsp csnp-interval interface configuration command. To restore the default value, use the no form of this command.

Syntax Description

Default

30 seconds

Command Mode

Interface configuration

Usage Guidelines

The ipx nlsp csnp-interval command applies only to the designated router for the specified interface only. This is because only designated routers send CSNP packets, which are used to synchronize the database.

CSNP does not apply to serial point-to-point interfaces. However, it does apply to WAN connections if the WAN is viewed as a multiaccess meshed network.

Example

The following example configures Ethernet interface 0 to transmit CSNPs every 10 seconds:

interface ethernet 0
 ipx nlsp csnp-interval 10

Related Commands

ipx nlsp hello-interval
ipx nlsp retransmit-interval

ipx nlsp enable

To enable NLSP routing on the primary network configured on this interface or subinterface, use the ipx nlsp enable interface configuration command. To disable NLSP routing on the primary network configured on this interface or subinterface, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Default

NLSP is disabled on all interfaces.

Command Mode

Interface configuration

Usage Guidelines

When you enable NLSP routing, the current settings for RIP and SAP compatibility modes as specified with the ipx nlsp rip and ipx nlsp sap interface configuration commands take effect automatically.

Examples

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

Related Commands

ipx nlsp rip
ipx nlsp sap

ipx nlsp hello-interval

To configure the interval between the transmission of hello packets, use the ipx nlsp hello-interval interface configuration command. To restore the default value, use the no form of this command.

Syntax Description

Default

10 seconds for the designated router
20 seconds for nondesignated routers

Command Mode

Interface configuration

Usage Guidelines

The designated router sends hello packets at an interval equal to one-half the configured value.

Use this command to improve the speed at which a failed router 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.

Example

The following example configures serial interface 0 to transmit hello packets every 30 seconds:

interface serial 0
 ipx nlsp hello-interval 30

Related Commands

ipx nlsp csnp-interval
ipx nlsp retransmit-interval

ipx nlsp metric

To configure the NLSP cost for an interface, use the ipx nlsp metric interface configuration command. To restore the default cost, use the no form of this command.

Syntax Description

Default

The default varies based on the throughput of the link connected to the interface.

Command Mode

Interface configuration

Usage Guidelines

Use the ipx nlsp metric command to cause NLSP to prefer some links over others. A link with a lower metric is more preferable than one with a higher metric.

Typically, it is not necessary to configure the metric; however, it may be desirable in some cases when there are wide differences in link bandwidths. For example, using the default metrics, a single 64-kbps ISDN link will be preferable to two 1544-kbps T1 links.

Example

The following example configures a metric of 10 on serial interface 0:

interface serial 0
 ipx nlsp metric 10

Related Command

ipx nlsp enable

ipx nlsp priority

To configure the election priority of the specified interface for designated router election, use the ipx nlsp priority interface configuration command. To restore the default priority, use the no form of this command.

Syntax Description

Default

44

Command Mode

Interface configuration

Usage Guidelines

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.

Example

The following example sets the designated router election priority to 65:

ipx nlsp priority 65

ipx nlsp retransmit-interval

To configure the link-state packet (LSP) retransmission interval on WAN links, use the ipx nlsp retransmit-interval interface configuration command. To restore the default interval, use the no form of this command.

Syntax Description

Default

5 seconds

Command Mode

Interface configuration

Usage Guidelines

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.

Example

The following example configures the LSP retransmission interval to 2 seconds:

ipx nlsp retransmit-interval 2

Related Commands

ipx nlsp csnp-interval
ipx nlsp hello-interval

ipx nlsp rip

To configure RIP compatibility when NLSP is enabled, use the ipx nlsp rip interface configuration command. To restore the default, use the no form of this command.

Syntax Description

Default

RIP periodic traffic is sent only if another router or access server in sending periodic RIP traffic.

Command Mode

Interface configuration

Usage Guidelines

The ipx nlsp rip command is meaningful only on networks on which NLSP is enabled. (RIP and SAP are always on by default on other interfaces.) Because the default mode is auto, no action is normally required to fully support RIP compatibility on an NLSP network.

Example

In the following example, the interface never generates or sends RIP periodic traffic:

interface ethernet 0
 ipx nlsp rip off

Related Commands

ipx nlsp enable
ipx nlsp sap

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.

Syntax Description

Default

SAP periodic traffic is sent only if another router in sending periodic SAP traffic.

Command Mode

Interface configuration

Usage Guidelines

The ipx nlsp sap command is meaningful only on networks on which NLSP is enabled. Because the default mode is auto, no action is normally required to fully support SAP compatibility on an NLSP network.

Example

In the following example, the interface never generates or sends SAP periodic traffic:

interface ethernet 0
 ipx nlsp sap off

Related Commands

ipx nlsp enable
ipx nlsp rip

ipx output-gns-filter

To control which servers are included in the Get Nearest Server (GNS) responses sent by the access server, use the ipx output-gns-filter interface configuration command. To remove the filter from the interface, use the no form of this command.

Syntax Description

Default

No filters are predefined.

Command Mode

Interface configuration

Usage Guidelines

You can issue only one ipx output-gns-filter command on each interface.

Example

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

Related Commands

access-list (SAP filtering)
ipx gns-round-robin

ipx output-network-filter

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.

Syntax Description

Default

No filters are predefined.

Command Mode

Interface configuration

Usage Guidelines

The ipx output-network-filter command controls which networks the access server advertises in its IPX routing updates (RIP updates).

You can issue only one ipx output-network-filter command on each interface.

Example

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

Related Commands

access-list (standard)
access-list (SAP filtering)
ipx input-network-filter
ipx router-filter

ipx output-rip-delay

To set the interpacket delay for Routing Information Protocol (RIP) updates sent on a single interface, use the ipx output-rip-delay interface configuration command. To return to the default value, use the no form of this command.

Syntax Description

Default

With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between routing update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.

Command Mode

Interface configuration

Usage Guidelines

The interpacket delay is the delay between the individual packets sent in a multiple-packet routing update. The ipx output-rip-delay command sets the interpacket delay for a single interface.

The system uses the interpacket delay specified by the ipx output-rip-delay command for periodic and triggered routing updates when no delay is set for triggered routing updates. When you set a delay for triggered routing updates, the system uses the delay specified by the ipx output-rip-delay command for only the periodic routing updates sent on the interface.

To set a delay for triggered routing updates, see the ipx triggered-rip-delay or ipx default-triggered-rip-delay commands.

You can also set a default RIP interpacket delay for all interfaces. See the ipx default-output-rip-delay command for more information.

Novell recommends a delay of 55 ms for compatibility with older and slower IPX machines. These machines may lose RIP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX machines.

The default delay on a NetWare 3.11 server is about 100 ms.

This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.

Example

The following example establishes a 55-ms interpacket delay on serial interface 0:

interface serial 0
ipx network 106A
ipx output-rip-delay 55

Related Command

ipx update-time
ipx default-output-rip-delay
ipx default-triggered-rip-delay
ipx triggered-rip-delay

ipx output-sap-delay

To set the interpacket delay for Service Advertisement Protocol (SAP) updates sent on a single interface, use the ipx output-sap-delay interface configuration command. To return to the default delay value, use the no form of this command.

Syntax Description

Default

With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.

Command Mode

Interface configuration

Usage Guidelines

The interpacket delay is the delay between the individual packets sent in a multiple-packet SAP update. The ipx output-sap-delay command sets the interpacket delay for a single interface.

The system uses the interpacket delay specified by the ipx output-sap-delay command for periodic and triggered SAP updates when no delay is set for triggered updates. When you set a delay for triggered updates, the system uses the delay specified by the ipx output-sap-delay command only for the periodic updates sent on the interface.

To set a delay for triggered updates, see the ipx triggered-sap-delay or ipx default-triggered-sap-delay commands.

You can also set a default SAP interpacket delay for all interfaces. See the ipx default-output-sap-delay command for more information.

Novell recommends a delay of 55 ms for compatibility with older and slower IPX servers. These servers may lose SAP updates because they process packets more slowly than the router sends them. The delay imposed by the ipx output-sap-delay command forces the router to pace its output to the slower-processing needs of these servers.

The default delay on a NetWare 3.11 server is about 100 ms.

This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.

Example

The following example establishes a 55-ms delay between packets in multiple-packet SAP updates on Ethernet interface 0:

interface ethernet 0
ipx network 106A
ipx output-sap-delay 55

Related Command

ipx default-output-sap-delay
ipx default-triggered-sap-delay
ipx sap-interval
ipx triggered-sap-delay

ipx output-sap-filter

To control which services are included in Service Advertisement Protocol (SAP) updates sent by the access server, use the ipx output-network-filter interface configuration command. To remove the filter, use the no form of this command.

Syntax Description

Default

No filters are predefined.

Usage Guidelines

The access 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.

Example

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

Related Commands

access-list (SAP filtering)
ipx gns-round-robin
ipx input-sap-filter
ipx router-sap-filter

ipx pad-process-switched-packets

To control whether odd-length packets are padded so as to be sent as even-length packets on an interface, use the ipx pad-process-switched-packets interface configuration command. To disable padding, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Default

Enabled on Ethernet interfaces
Disabled on Token Ring, FDDI, and serial interfaces.

Command Mode

Interface configuration

Usage Guidelines

Use this command only under the guidance of a customer engineer or other service representative.

The ipx pad-process-switched-packets command affects process-switched packets only, so you must disable fast switching before the ipx pad-process-switched-packets command has any effect.

Some IPX end hosts reject Ethernet packets that are not padded. Certain topologies can result in such packets being forwarded onto a remote Ethernet network. Under specific conditions, padding on intermediate media can be used as a temporary workaround for this problem.

Example

The following command configures the router to pad odd-length packets so that they are sent as even-length packets on Ethernet interface 1.

interface ethernet 1
ipx pad-process-switched-packets

Related Command

ipx route-cache

ipx ping-default

To select the ping type that the access server transmits, use the ipx ping-default global configuration command. To return to the default ping type, use the no form of this command.

Syntax Description

Default

Cisco pings

Command Mode

Global configuration

Usage Guidelines

Standard Novell pings conform to the definition in the Novell NLSP specification.

Example

The following example enables standard Novell pings:

ipx ping-default novell

Related Command

ping (user)

ipx rip-max-packetsize

To configure the maximum packet size of RIP updates sent out the interface, use the ipx rip-max-packetsize interface configuration command. To restore the default packet size, use the no form of this command.

Syntax Description

Default

432 bytes

Command Mode

Interface configuration

Usage Guidelines

The maximum size is for the IPX packet excluding the media header.

Do not allow the maximum packet size to exceed the allowed maximum size of packets for the interface.

Example

The following example sets the maximum RIP update packet to 832 bytes:

ipx rip-max-packetsize 832

Related Command

ipx sap-max-packetsize

ipx rip-multiplier

To configure the interval at which a network's RIP entry ages out, use the ipx rip-multiplier interface configuration command. To restore the default interval, use the no form of this command.

Syntax Description

Default

Three times the RIP update interval.

Command Mode

Interface configuration

Usage Guidelines

All routers on the same physical cable should use the same multiplier value.

Example

In the following example, in a configuration where RIP updates are sent once every 2 minutes, the interval at which RIP entries age out is set to 10 minutes:

interface ethernet 0
ipx rip-multiplier 5

Related Command

ipx update-interval

ipx route

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.

Syntax Description

Default

No static routes are predefined.

Command Mode

Global configuration

Usage Guidelines

The ipx route command forwards packets destined for the specified network (network) via the specified access server (network.node), regardless of whether that access server is sending dynamic routing information.

Floating-static routes are static routes that can be overridden by dynamically learned routes. Floating-static routes allow you to switch to another path whenever routing information for a destination is lost. One application of floating-static routes is to provide back-up routes in topologies where dial-on-demand routing is used.

If you configure a floating-static route, the access 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.

If you specify an interface instead of a network node address, the interface must be an IPXWAN unnumbered interface. For IPXWAN interfaces, the network number need not be preassigned; instead, the nodes may negotiate the network number dynamically.

Note that by default, floating-static routes are not redistributed into other dynamic protocols.

Example

In the following example, the access server at address 3abc.0000.0c00.1ac9 handles all traffic destined for network 5e:

ipx routing
ipx route 5e 3abc.0000.0c00.1ac9

Related Command

show ipx route

ipx route-cache

To enable IPX fast switching, use the ipx route-cache interface configuration command. To disable fast switching, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Default

Fast switching enabled

Command Mode

Interface configuration

Usage Guidelines

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.

Examples

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

Related Commands

clear ipx cache
ipx source-network-update
ipx watchdog-spoof
show ipx cache

ipx router

To specify the routing protocol to use, use the ipx router global configuration command. To disable a particular routing protocol on the router, use the no form of this command

Syntax Description

Default

RIP

Command Mode

Global configuration

Usage Guidelines

You can configure multiple IPX Enhanced IGRP processes on an access server. To do so, assign each a different autonomous system number.

You must explicitly disable RIP by issuing the no ipx router rip command if you do not want to use this routing protocol.

Example

The following example enables IPX Enhanced IGRP on the communication:

ipx router eigrp 4

Related Commands

A dagger (⁺) indicates that the command is documented in another chapter.

network ⁺
redistribute

ipx router-filter

To control the access 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.

Syntax Description

Default

No filters are predefined.

Command Mode

Interface configuration

Usage Guidelines

You can issue only one ipx router-filter command on each interface.

Example

In the following example, access list 866 controls the access servers from which packets are accepted. For Ethernet interface 0, only packets from the access 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

Related Commands

access-list (standard)
access-list (SAP filtering)
ipx input-network-filter
ipx output-network-filter

ipx router-sap-filter

To filter Service Advertisement Protocol (SAP) messages received from a particular access server, use the ipx router-sap-filter interface configuration command. To remove the filter, use the no form of this command.

Syntax Description

Default

No filters are predefined.

Command Mode

Interface configuration

Usage Guidelines

You can issue only one ipx router-sap-filter command on each interface.

Example

In the following example, the access server will receive service advertisements only from access 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

Related Commands

access-list (SAP filtering)
ipx input-sap-filter
ipx output-sap-filter
ipx sap
show ipx interface

ipx routing

To enable IPX routing, use the ipx routing global configuration command. To disable IPX routing, use the no form of this command.

Syntax Description

Default

Disabled

Command Mode

Global configuration

Usage Guidelines

The ipx routing command enables the IPX Routing Information Protocol (RIP) and Service Advertisement Protocol (SAP) services on the access 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 access server's new address.

If you plan to use DECnet and IPX routing concurrently on the same interface, you should enable DECnet access 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.

Example

The following example enables IPX routing:

ipx routing

Related Command

ipx network

ipx sap

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.

Syntax Description

Default

Disabled

Command Mode

Global configuration

Usage Guidelines

The ipx sap command allows you to add static entries into the SAP table. Each entry has a SAP service associated with it. Static SAP assignments always override any identical entries in the SAP table that are learned dynamically, regardless of hop count. The access server will not announce a static SAP entry unless it has a route to that network.

Example

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 access 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

Related Commands

ipx input-sap-filter
ipx output-sap-filter
ipx router-sap-filter
show ipx servers

ipx sap-incremental

To send SAP updates only when a change occurs in the SAP table, use the ipx sap-incremental interface configuration command. To send periodic SAP updates, use the no form of this command.

Syntax Description

Default

Enabled on serial interfaces
Disabled on LAN media (Ethernet, Token Ring, FDDI)

Usage Guidelines

In order to use the ipx sap-incremental command, you must enable Enhanced IGRP on the router. This is the case even if you want to use only RIP routing. You must do this because the incremental SAP feature requires the Enhanced IGRP reliable transport mechanisms.

With this functionality enabled, if an IPX Enhanced IGRP peer is found on the interface, SAP updates will be sent only when a change occurs in the SAP table. Periodic SAP updates are not sent. When no IPX Enhanced IGRP peer is present on the interface, periodic SAPs are always sent regardless of how this command is set.

If you configure the local access server to send incremental SAP updates on an Ethernet, and if the local access 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 access 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 take advantage of Enhanced IGRP's incremental SAP update mechanism while using the RIP routing protocol instead of the Enhanced IGRP routing protocol, specify the rsup-only keyword. SAP updates are then sent only when changes occur, and only changes are sent. Use this feature only when you want to use RIP routing.

Example

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

ipx sap-interval

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.

Syntax Description

Default

1 minute

Command Mode

Interface configuration

Usage Guidelines

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 access 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, access 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.

Example

In the following example, SAP updates are sent (and expected) on serial interface 0 every 5 minutes:

interface serial 0
 ipx sap-interval 5

Related Command

ipx output-sap-delay

ipx sap-max-packetsize

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.

Syntax Description

Default

480 bytes

Command Mode

Interface configuration

Usage Guidelines

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.

Example

The following examples sets the maximum SAP update packet size to 672 bytes:

ipx sap-max-packetsize 672

ipx sap-multiplier

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.

Syntax Description

Default

Three times the SAP update interval.

Command Mode

Interface configuration

Usage Guidelines

All routers and access servers on the same physical cable should use the same multiplier value.

Example

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

Related Command

ipx sap-max-packetsize

ipx sap-queue-maximum

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.

Syntax Description

Default

No maximum queue size

Command Mode

Global configuration

Usage Guidelines

The access 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 access 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.

Example

The following example sets the length of the queue of pending SAP requests to 20:

ipx sap-queue-maximum 20

ipx source-network-update

To repair corrupted network numbers, use the ipx source-network-update interface configuration command. To disable this feature, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Interface configuration

Usage Guidelines

In some early implementations of IPX client software, it was possible for the client's network number to become corrupted. The ipx source-network-update command repairs this number by setting the source network field of any packet on the local network that has a hop count of zero.

You must disable fast switching with the no ipx route-cache command before using the ipx source-network-update command.

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.

Example

In the following example, corrupted network numbers on serial interface 0 are repaired:

interface serial 0
 no ipx route-cache
 ipx source-network-update

Related Command

ipx route-cache

ipx split-horizon eigrp

To configure split horizon, use the ipx split-horizon eigrp interface configuration command. To disable split horizon, use the no form of this command.

Syntax Description

Default

Enabled

Command Mode

Interface configuration

Usage Guidelines

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.

Example

The following example disables split horizon on serial interface 0:

interface serial 0
 no ipx split-horizon eigrp 200 

ipx spx-idle-time

To set the amount of time to wait before starting the spoofing of SPX keepalive packets following inactive data transfer, use the ipx spx-idle-time command. To disable the current delay time set by this command, use the no form of this command.

Syntax Description

Default

60 seconds

Command Mode

Interface configuration

Usage Guidelines

This command sets the elapse time in seconds after which spoofing of keepalive packets occurs, following the end of data transfer; that is, after the acknowledgment and sequence numbers of the data being transferred have stopped increasing. By default, SPX keepalive packets are sent from servers to clients every 15 to 20 seconds.

If you turn on SPX spoofing and you do not set an idle time, the default of 60 seconds is assumed. This means that the dialer idle time begins when SPX spoofing begins. For example, if the dialer idle time is three minutes, the elapse time before SPX spoofing begins is four minutes: three minutes of dialer idle time plus one minute of SPX spoofing idle time.

For this command to take effect, you must first use the ipx spx-spoof interface configuration command to enable SPX spoofing for the interface.

Example

The following example enables spoofing on serial interface 0 and sets the idle timer to 300 seconds:

interface serial 0
ipx spx-spoof 
no ipx route-cache
ipx spx-idle-time 300

Related Commands

ipx spx-spoof
show ipx spx-spoof

ipx spx-spoof

To configure the router respond to a client or server's SPX keepalive packets on behalf of a remote system so that a dial-on-demand link will go idle when data has stopped being transferred, use the ipx spx-spoof interface configuration command. To disable spoofing, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Interface configuration

Usage Guidelines

You can use the ipx spx-spoof command on any serial dialer or point-to-point interface. Fast switching and autonomous switching must be disabled on the interface; otherwise, SPX spoofing will not be permitted.

SPX keepalive packets are sent from servers to clients every 15-20 seconds after a client session has been idle for a certain period of time following the end of data transfer and after which only unsolicited acknowledgments are sent. The idle time may vary depending on parameters set by the client and server.

Due to acknowledgment packets, a session would never go idle on a DDR link. On pay-per-packet or byte networks, these keepalive packets can incur large phone connection charges for idle time on the customer. You can prevent these calls from being made by configuring the router to respond to the server's keepalive packets on a remote client's behalf. This is sometimes referred to as "spoofing the server."

You can use the ipx spx-idle-time command to set the elapse time in seconds after which spoofing of keepalive packets occurs, following the end of data transfer. If you turn on SPX spoofing and you do not set an idle time, the default of 60 seconds is assumed. This means that the dialer idle time begins when SPX spoofing begins. For example, if the dialer idle time is 3 minutes, the elapse time before the line goes "idle-spoofing" is 4 minutes: 3 minutes of dialer idle time plus 1 minute of SPX spoofing idle time.

Example

The following example enables spoofing on serial interface 0:

interface serial 0
ipx spx-spoof 
no ipx route-cache

Related Commands

ipx throughput
show ipx spx-spoof

ipx throughput

To configure the throughput, use the ipx throughput interface configuration command. To restore the default throughput, use the no form of this command.

Syntax Description

Default

No default throughput is defined.

Command Mode

Interface configuration

Usage Guidelines

The value you specify with the ipx throughput command overrides the value measured by IPXWAN when it starts. This value is also supplied to NLSP for use in its metric calculations.

Example

The following example changes the throughput to 1000000 bits per second:

ipx throughput 1000000

Related Command

ipx ipxwan

ipx triggered-rip-delay

To set the interpacket delay for triggered Routing Information Protocol (RIP) updates sent on a single interface, use the ipx triggered-rip-delay interface configuration command. To return to the default delay, use the no form of this command.

Syntax Description

Default

With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between routing update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.

Command Mode

Interface configuration

Usage Guidelines

The interpacket delay is the delay between the individual packets sent in a multiple-packet routing update. A triggered routing update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.

The ipx triggered-rip-delay command sets the interpacket delay for triggered routing updates sent on a single interface. The delay value set by this command overrides the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered routing updates sent on the interface.

If the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command is high, then we strongly recommend a low delay value for triggered routing updates so that updates triggered by special events are sent in a more timely manner than periodic routing updates.

Novell recommends a delay of 55 ms for compatibility with older and slower IPX machines. These machines may lose RIP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX machines.

The default delay on a NetWare 3.11 server is about 100 ms.

When you do not set the interpacket delay for triggered routing updates, the system uses the delay specified by the ipx output-rip-delay or ipx default-output-rip-delay command for both periodic and triggered routing updates.

When you use the no form of the ipx triggered-rip-delay command, the system uses the global default delay set by the ipx default-triggered-rip-delay command for triggered RIP updates, if it is set. If it is not set, the system uses the delay set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered RIP updates, if set. Otherwise, the system uses the initial default delay as described in the "Default" section.

This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.

Example

The following example sets an interpacket delay of 55 ms for triggered routing updates sent on interface FDDI 0:

int FDDI 0
ipx triggered-rip-delay 55

Related Command

ipx default-output-rip-delay
ipx default-triggered-rip-delay
ipx output-rip-delay

ipx triggered-sap-delay

To set the interpacket delay for triggered Service Advertisement Protocol (SAP) updates sent on a single interface, use the ipx triggered-sap-delay interface configuration command. To return to the default delay, use the no form of this command.

Syntax Description

Default

With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.

Command Mode

Interface configuration

Usage Guidelines

The interpacket delay is the delay between the individual packets sent in a multiple-packet SAP update. A triggered SAP update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.

The ipx triggered-sap-delay command sets the interpacket delay for triggered updates sent on a single interface. The delay value set by this command overrides the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered updates sent on the interface.

If the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command is high, then we strongly recommend a low delay value for triggered updates so that updates triggered by special events are sent in a more timely manner than periodic updates.

Novell recommends a delay of 55 ms for compatibility with older and slower IPX servers. These servers may lose SAP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX servers.

The default delay on a NetWare 3.11 server is about 100 ms.

When you do not set the interpacket delay for triggered updates, the system uses the delay specified by the ipx output-sap-delay or ipx default-output-sap-delay command for both periodic and triggered SAP updates.

When you use the no form of the ipx triggered-sap-delay command, the system uses the global default delay set by the ipx default-triggered-sap-delay command for triggered SAP updates, if it is set. If it is not set, the system uses the delay set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered SAP updates, if set. Otherwise, the system uses the initial default delay as described in the "Default" section.

This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.

Example

The following example sets an interpacket delay of 55 ms for triggered SAP updates sent on interface FDDI 0:

int FDDI 0
ipx triggered-sap-delay 55

Related Commands

ipx default-output-sap-delay
ipx default-triggered-sap-delay
ipx output-sap-delay

ipx type-20-helpered

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.

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Interface configuration

Usage Guidelines

The ipx type-20-helpered command disables the input and output of type 20 propagation packets as done by the ipx type-20-propagation interface configuration command.

The ipx type-20-propagation command broadcasts type 20 packets to all nodes on the network and imposes a hop-count limit of eight routers or access 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.

Example

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

Related Commands

ipx helper-address
ipx type-20-propagation

ipx type-20-input-checks

To restrict the acceptance of IPX type 20 propagation packet broadcasts, use the ipx type-20-input-checks global configuration command. To remove these restrictions, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Global configuration

Usage Guidelines

By default, the access 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 access 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.

Example

The following example imposes additional restrictions on incoming type 20 broadcasts:

ipx type-20-input-checks

Related Commands

ipx type-20-propagation

ipx type-20-output-checks

To restrict the forwarding of IPX type 20 propagation packet broadcasts, use the ipx type-20-output-checks global configuration command. To remove these restrictions, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Global configuration

Usage Guidelines

By default, the router is configured to block type 20 propagation packets. When type 20 packet handling is enabled on multiple interfaces, you can use the ipx type-20-output-checks command to impose additional restrictions on outgoing type 20 packets. Specifically, the router will forward these packets only to networks that are not routes back to the source network. (The router uses the current routing table to determine routes.) This behavior can be advantageous in redundant topologies, because it reduces unnecessary duplication of type 20 packets.

Example

The following example imposes restrictions on outgoing type 20 broadcasts:

ipx type-20-output-checks

Related Commands

ipx type-20-input-checks
ipx type-20-propagation

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.

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Usage Guidelines

Access 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.

Examples

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

Related Commands

ipx helper-address
ipx helper-list
ipx type-20-input-checks

ipx update-time

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.

Syntax Description

Default

60 seconds

Command Mode

Interface configuration

Usage Guidelines

The ipx update-time command sets the routing update timer on a per-interface basis.

Access 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 access servers are our access servers or in which the IPX access servers allow configurable timers. The timers should be the same for all access servers connected to the same cable segment.

The update value you choose affects the internal IPX timers as follows:

• IPX routes are marked invalid if no routing updates are heard within three times the value of the update interval (3 ¥ seconds) and are advertised with a metric of infinity.

• IPX routes are removed from the routing table if no routing updates are heard within four times the value of the update interval (4 ¥ seconds).

• If you define an update timer for more than one interface in an access server, the granularity of the update timer is determined by the lowest value defined for one of the interfaces in the access server. The access server "wakes up" at this granularity interval and determines what updates need to be sent.

  The concept of granularity is best explained by an example. (This example is illustrated in the "Example" section following.) If you have two interfaces in the access server and you set the update timer on one to 20 seconds and the second to 30 seconds, the access server wakes up every 20 seconds to try to send routing updates. So at time 0:00:20, the access server sends an update out the first interface only, and at time 0:00:40 it sends updates out the first and second interfaces. The access server does not wake up at 0:00:30 to see if it needs to send an update out the second interface. This means that routing updates are sent out the second interface at N:NN:40 and N:NN:00. That is, the interval alternates between 40 seconds and 20 seconds; it is never 30 seconds. The interval on the first interface is always 20 seconds.

  
  

Example

The following example sets the update timers on two interfaces in the access 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

Related Command

show ipx interface

ipx watchdog-spoof

To have the access 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.

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Interface configuration

Usage Guidelines

You can use the ipx watchdog-spoof command only on a serial interface on which dial-on-demand routing (DDR) has been enabled. Also, fast switching and autonomous switching must be disabled on the interface.

IPX watchdog packets are keepalive packets that are sent from servers to clients after a client session has been idle for approximately 5 minutes. On a DDR link, this would mean that a call would be made every 5 minutes, regardless of whether there were data packets to send. You can prevent these calls from being made by configuring the access server to respond to the server's watchdog packets on a remote client's behalf. This is sometimes referred to as "spoofing the server."

Example

The following example enables spoofing on serial interface 0:

interface serial 0
 ipx watchdog-spoof
 no ipx route-cache

Related Command

ipx route-cache
ipx spx-spoof

lsp-gen-interval

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.

Syntax Description

Default

5 seconds

Command Mode

Router configuration

Usage Guidelines

The lsp-gen-interval command controls the rate at which LSPs are generated on a per-LSP basis. For instance, if a link is changing state at a high rate, the default value of the LSP generation interval limits the signaling of this change to once every 5 seconds. Because the generation of an LSP may cause all routers in the area to perform the SPF calculation, controlling this interval may have area-wide impact. Raising this interval can reduce the load on the network imposed by a rapidly changing link.

Example

The following example sets the minimum interval at which LSPs are generated to 10 seconds:

lsp-gen-interval 10

Related Commands

spf-interval

lsp-mtu

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.

Syntax Description

Default

512 bytes

Command Mode

Router configuration

Usage Guidelines

You can increase the LSP MTU if there is a very large amount of information generated by a single router or access 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.

Example

The following example sets the maximum LSP size to 1500 bytes:

lsp-mtu 1500

lsp-refresh-interval

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.

Syntax Description

Default

7200 seconds (2 hours)

Command Mode

Router configuration

Usage Guidelines

The refresh interval determines the rate at which a router periodically transmits the route topology information that it originates. This is done in order to keep the information from becoming too old. By default, the refresh interval is 2 hours.

LSPs must be periodically refreshed before their 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).

Example

The following example changes the LSP refresh interval to 10800 seconds (3 hours):

lsp-refresh-interval 10800 

Related Commands

max-lsp-lifetime

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.

Syntax Description

Default

7500 seconds (2 hours, 5 minutes)

Command Mode

Router configuration

Usage Guidelines

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.

Example

The following example sets the maximum time that the LSP persists to 11000 seconds (just over 3 hours):

max-lsp-lifetime 11000

Related Commands

lsp-refresh-interval

netbios access-list

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.

Syntax Description

Default

No filters are predefined.

Command Mode

Global configuration

Usage Guidelines

Keep the following points in mind when configuring IPX NetBIOS access control:

• Host (node) names are case sensitive.

• Host and byte access lists can have the same names. They are independent of each other.

• When filtering by node name for IPX NetBIOS, the names in the access lists are compared with the destination name field for IPX NetBIOS "find name" requests.

• When filtering by byte offset, note that these access filters can have a significant impact on the packets' transmission rate across the bridge because each packet must be examined. You should use these access lists only when absolutely necessary.

• If a node name is not found in an access list, the default action is to deny access.

These filters apply only to IPX NetBIOS FindName packets. They have no effect on LLC2 NetBIOS packets.

To delete an IPX NetBIOS access list, specify the minimum number of keywords and arguments needed to delete the proper list. For example, to delete the entire list, use the following command:

To delete a single entry from the list, use the following command:

Examples

The 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 

Related Commands

ipx netbios input-access-filter
ipx netbios output-access-filter
show ipx interface

network

To enable Enhanced IGRP on the access server, use the network IPX-router configuration command. To disable Enhanced IGRP, use the no form of this command.

Syntax Description

Default

Disabled

Command Mode

IPX-router configuration

Usage Guidelines

Use the network command to enable the routing protocol specified in the ipx router command on each network.

Example

The following commands disable RIP on network 10 and enable Enhanced IGRP on networks 10 and 20:

ipx router rip
no network 10
ipx router eigrp 12
network 10
network 20

Related Command

ipx router

ping (privileged)

To check host reachability and network connectivity, use the ping privileged EXEC command.

Syntax Description

Command Mode

Privileged EXEC

Usage Guidelines

The privileged ping (packet internet groper function) command provides a complete ping facility for users who have system privileges.

You cannot ping an access 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-4 describes the test characters displayed in ping responses.

Sample Display

The following sample display shows input to and output from the ping command:

Router# 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.

Related Command

ping (user)

ping (user)

To check host reachability and network connectivity, use the ping user EXEC command.

Syntax Description

Command Mode

EXEC

Usage Guidelines

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 an access 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-5 describes the test characters displayed in ping responses.

Sample Display

The following sample display shows input to and output from the user ping command:

Router> ping ipx 211.0000.0c01.f4cf
Type escape sequence to abort.
Sending 5, 100-byte Novell Echoes to 211.0000.0c01.f4cf, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

Related Command

ping (privileged)

redistribute

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.

Syntax Description

Default

Redistribution is enabled between all routing domains except between separate Enhanced IGRP processes.

Redistribution of floating static routes is disabled.

Command Mode

IPX-router configuration

Usage Guidelines

Redistribution provides for routing information generated by one protocol to be advertised in another.

The only connected routes affected by this redistribute command are the routes not specified by the network command.

If you have enabled floating static routes by specifying the floating keyword in the ipx route global configuration command and you redistribute floating static routes into a dynamic IPX routing protocol, any nonhierarchical topology causes the floating static destination to be redistributed immediately via a dynamic protocol back to the originating router, causing a routing loop. This occurs because dynamic protocol information overrides floating static routes. For this reason, automatic redistribution of floating static routes is off by default. If you redistribute floating static routes, you should specify filters to eliminate routing loops.

Examples

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

Related Command

ipx route

show ipx accounting

To display the active accounting or checkpointed database, use the show ipx accounting EXEC command.

Syntax Description

Command Mode

EXEC

Sample Display

The following is sample output from the show ipx accounting command:

Router# show ipx accounting
Source                  Destination                Packets           Bytes
0000C003.0000.0c05.6030 0000C003.0260.8c9b.4e33         72            2880
0000C001.0260.8c8d.da75 0000C003.0260.8c9b.4e33         14             624
0000C003.0260.8c9b.4e33 0000C001.0260.8c8d.da75         62            3110
0000C001.0260.8c8d.e7c6 0000C003.0260.8c9b.4e33         20            1470
0000C003.0260.8c9b.4e33 0000C001.0260.8c8d.e7c6         20            1470
Accounting data age is     6

Table 20-6 describes the fields shown in the display.

Related Commands

clear ipx accounting
ipx accounting
ipx accounting-list
ipx accounting-threshold
ipx accounting-transits

show ipx cache

To display the contents of the IPX fast-switching cache, use the show ipx cache EXEC command.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

The following is sample output from the show ipx cache command:

Router# show ipx cache
Novell routing cache version is 9
Destination          Interface               MAC Header
*1006A               Ethernet 0              00000C0062E600000C003EB0064
*14BB                Ethernet 1              00000C003E2A00000C003EB0064

Table 20-7 describes the fields shown in the display.

Related Commands

clear ipx cache
ipx route-cache

show ipx eigrp neighbors

To display the neighbors discovered by Enhanced IGRP, use the show ipx eigrp neighbors EXEC command.

Syntax Description

Command Mode

EXEC

Sample Display

The following is sample output from the show ipx eigrp neighbors command:

Router# 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.

show ipx eigrp topology

To display the IPX Enhanced IGRP topology table, use the show ipx eigrp topology EXEC command.

Syntax Description

Command Mode

EXEC

Sample Display

The following is sample output from the show ipx eigrp topology command:

Router# show ipx eigrp topology 
IPX EIGRP Topology Table for process 109
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, 
r - Reply status
P 42, 1 successors, FD is 0
   via 160.0000.0c00.8ea9 (345088/319488), Ethernet0 
P 160, 1 successor via Connected, Ethernet 
   via 160.0000.0c00.8ea9 (307200/281600), Ethernet0 
P 165, 1 successors, FD is 307200
   via Redistributed (287744/0) 
   via 160.0000.0c00.8ea9 (313344/287744), Ethernet0 
P 164, 1 successors, flags: U, FD is 200
   via 160.0000.0c00.8ea9 (307200/281600), Ethernet1 
   via 160.0000.0c01.2b71 (332800/307200), Ethernet1 
P A112, 1 successors, FD is 0
   via Connected, Ethernet2 
   via 160.0000.0c00.8ea9 (332800/307200), Ethernet0 
P AAABBB, 1 successors, FD is 10003
   via Redistributed (287744/0), 
   via 160.0000.0c00.8ea9 (313344/287744), Ethernet0 
A A112, 0 successors, 1 replies, state: 0, FD is 0
   via 160.0000.0c01.2b71 (307200/281600), Ethernet1 
   via 160.0000.0c00.8ea9 (332800/307200) , r, Ethernet1

Table 20-9 explains the fields in the output.

Router# show ipx eigrp topology 160
IPX-EIGRP topology entry for 160 
State is Passive, Query origin flag is 1, 1 Successor(s) 
Routing Descriptor Blocks: 
 Next hop is Connected (Ethernet0), from 0.0000.0000.0000 
 Composite metric is (0/0), Send flag is 0x0, Route is Internal 
 Vector metric: 
  Minimum bandwidth is 10000 Kbit 
  Total delay is 1000000 nanoseconds 
  Reliability is 255/255 
  Load is 1/255 
  Minimum MTU is 1500 
  Hop count is 0 
Next hop is 164.0000.0c00.8ea9 (Ethernet1), from 164.0000.0c00.8ea9 
 Composite metric is (307200/281600), Send flag is 0x0, Route is External 
 This is an ignored route 
 Vector metric: 
  Minimum bandwidth is 10000 Kbit 
  Total delay is 2000000 nanoseconds 
  Reliability is 255/255 
  Load is 1/255 
  Minimum MTU is 1500 
  Hop count is 1 
 External data: 
  Originating router is 0000.0c00.8ea9 
  External protocol is RIP, metric is 1, delay 2 
  Administrator tag is 0 (0x00000000) 
  Flag is 0x00000000

Table 20-10 explains the fields in the output.

Related Command

show ipx route

show ipx interface

To display the status of the IPX interfaces configured in the access server and the parameters configured on each interface, use the show ipx interface EXEC command.

Syntax Description

Command Mode

EXEC

Sample Display

The following is sample output from the show ipx interface command:

Router# show ipx interface ethernet 1
Ethernet1 is up, line protocol is up
  IPX address is C03.0000.0c05.6030, NOVELL-ETHER [up] line-up, RIPPQ: 0, SAPPQ : 0
  Delay of this Novell network, in ticks is 1
  IPXWAN processing not enabled on this interface.
  IPX SAP update interval is 1 minute(s)
  IPX type 20 propagation packet forwarding is disabled
  Outgoing access list is not set
  IPX Helper access list is not set
  SAP Input filter list is not set
  SAP Output filter list is not set
  SAP Router filter list is not set
  SAP GNS output filter list is not set
  Input filter list is not set
  Output filter list is not set
  Router filter list is not set
  Netbios Input host access list is not set
  Netbios Input bytes access list is not set
  Netbios Output host access list is not set
  Netbios Output bytes access list is not set
  Update time is 60 seconds
  IPX accounting is enabled
  IPX fast switching is configured (enabled)
  IPX SSE switching is disabled

Table 20-11 describes the fields shown in the display.

Related Commands

access-list (standard)
access-list (SAP filtering)
access-list (SAP filtering)
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

show ipx nlsp database

To display the entries in the link-state packet (LSP) database, use the show ipx nlsp database EXEC command.

Syntax Description

Command Mode

EXEC

Usage Guidelines

If you omit all options, a summary display is shown.

Sample Displays

The following is sample output from the show ipx nlsp database command:

Router> show ipx nlsp database detail
LSPID                 LSP Seq Num  LSP Checksum  LSP Holdtime  ATT/P/OL
0000.0C00.3097.00-00* 0x00000042   0xC512        699           0/0/0
0000.0C00.3097.06-00* 0x00000027   0x0C27        698           0/0/0
0000.0C02.7471.00-00  0x0000003A   0x4A0F        702           0/0/0
0000.0C02.7471.08-00  0x00000027   0x0AF0        702           0/0/0
0000.0C02.7471.0A-00  0x00000027   0xC589        702           0/0/0
0000.0C02.747D.00-00  0x0000002E   0xC489        715           0/0/0
0000.0C02.747D.06-00  0x00000027   0xEEFE        716           0/0/0
0000.0C02.747D.0A-00  0x00000027   0xFE38        716           0/0/0
0000.0C02.74AB.00-00  0x00000035   0xE4AF        1059          0/0/0
0000.0C02.74AB.0A-00  0x00000027   0x34A4        705           0/0/0
0000.0C06.FBEE.00-00  0x00000038   0x3838        1056          0/0/0
0000.0C06.FBEE.0D-00  0x0000002C   0xD248        1056          0/0/0
0000.0C06.FBEE.0E-00  0x0000002D   0x7DD2        1056          0/0/0
0000.0C06.FBEE.17-00  0x00000029   0x32FB        1056          0/0/0
0000.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.

show ipx nlsp neighbors

To display the access server's NLSP neighbors and their states, use the show ipx nlsp neighbors EXEC command.

Syntax Description

Command Mode

EXEC

Usage Guidelines

If you omit the keyword detail, a summary display is shown.

Sample Displays

The following is sample output from the show ipx nlsp neighbors command:

Router> show ipx nlsp neighbors detail
System Id       Interface   State  Holdtime  Priority  Circuit Id
0000.0C01.EF90  Ethernet1   Up     25        64        0000.0C01.EF90.0C
  IPX Address: E1.0000.0c01.ef91
  IPX Areas:  00000000/00000000
  Uptime: 2:59:11

Table 20-13 explains the fields in the display.

show ipx route

To display the contents of the IPX routing table, use the show ipx route EXEC command.

Syntax Description

Command Mode

EXEC

Sample Display

The following is sample output from the show ipx route command:

Router# show ipx route
Codes: C - Connected primary network,    c - Connected secondary network
       S - Static, F - Floating static, L - Local (internal), W - IPXWAN
       R - RIP, E - EIGRP, N - NLSP, X - External, s - seconds, u - uses
7 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.
No default route known.
L        D40 is the internal network
C        100 (NOVELL-ETHER), Et1
C       7000 (TUNNEL),        Tu1
S        200 via     7000.0000.0c05.6023,        Tu1
R        300 [02/01] via      100.0260.8c8d.e748,   19s, Et1
S       2008 via     7000.0000.0c05.6023,        Tu1
R     CC0001 [02/01] via      100.0260.8c8d.e748,   19s, Et1

Table 20-14 describes the fields shown in the display.

Router# show ipx route detailed
Codes: C - Connected primary network,    c - Connected secondary network
       S - Static, F - Floating static, L - Local (internal), W - IPXWAN
       R - RIP, E - EIGRP, N - NLSP, X - External, s - seconds, u - uses
9 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.
No default route known.
L        D35 is the internal network
C       E001 (SAP),           Et0
C      D35E2 (NOVELL-ETHER),  Et2
R        D34 [02/01]
          -- via     E001.0000.0c02.8cf9,  43s,     1u, Et0
N        D36 [20][02/01]
          -- via    D35E2.0000.0c02.8cfc, 704s,     1u, Et2
                  10000000:1000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc
NX       D40 [20][03/02][02/01]
          -- via    D35E2.0000.0c02.8cfc, 704s,     1u, Et2
                  10000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc
R      D34E1 [01/01]
          -- via     E001.0000.0c02.8cf9,  43s,     1u, Et0
NX     D40E1 [20][02/02][01/01]
          -- via    D35E2.0000.0c02.8cfc, 704s,     3u, Et2
                  10000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc
N     D36E02 [20][01/01]
          -- via    D35E2.0000.0c02.8cfc, 705s,     2u, Et2
                  10000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc

Table 20-15 explains the additional fields shown in the display.

Related Commands

clear ipx nlsp neighbors
ipx maximum-paths
ipx route

show ipx servers

To list the IPX servers discovered through SAP advertisements, use the show ipx servers EXEC command.

Syntax Description

Default

IPX servers are displayed numerically by SAP service type.

Command Mode

EXEC

Sample Display

The following is sample output from the show ipx servers command:

Router# show ipx servers 
Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail
9 Total IPX Servers
Table ordering is based on routing and server info
Type Name                      Net  Address          Port Route Hops Itf
N+   4 MERLIN1-VIA-E03         E03E03.0002.0004.0006:0451 4/03  4    Et0
N+   4 merlin                  E03E03.0002.0004.0006:0451 4/03  3    Et0
N+   4 merlin 123456789012345  E03E03.0002.0004.0006:0451 4/03  3    Et0
S    4 WIZARD1--VIA-E0         E0.0002.0004.0006:0451     none  2
N+   4 dtp-15-AB               E002.0002.0004.0006:0451   none  4    Et0
N+   4 dtp-15-ABC              E002.0002.0004.0006:0451   none  4    Et0
N+   4 dtp-15-ABCD             E002.0002.0004.0006:0451   none  4    Et0
N+   4 merlin                  E03E03.0002.0004.0006:0451 4/03  3    Et0
N+   4 dtp-15-ABC              E002.0002.0004.0006:0451   non

Table 20-16 describes the fields shown in the display.

Related Command

ipx sap

show ipx spx-spoof

To display the table of SPX connections through interfaces for which SPX spoofing is enabled, use the show ipx spx-spoof EXEC command.

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

EXEC

Sample Display

The following is sample output from the show ipx spx-spoof command:

Router> show ipx spx-spoof

Local SPX Network.Host:sock Cid  Remote SPX Network.Host:sock Cid   Seq  Ack  Idle CC0001.0000.0000.0001:8104  0D08 200.0260.8c8d.e7c6:4017      7204  09   0021 120 CC0001.0000.0000.0001:8104  0C08 200.0260.8c8d.c558:4016      7304  07   0025 120

Table 20-17 describes the fields shown in the display.

Related Commands

ipx spx-idle-time
ipx spx-spoof

show ipx traffic

To display information about the number and type of IPX packets transmitted and received by the access server, use the show ipx traffic user EXEC command.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

The following is sample output from the show ipx traffic command:

Router> show ipx traffic
Rcvd:   644 total, 1705 format errors, 0 checksum errors, 0 bad hop count,
        0 packets pitched, 644 local destination, 0 multicast
Bcast:  589 received, 324 sent
Sent:   380 generated, 0 forwarded
        0 encapsulation failed, 4 no route
SAP:    1 SAP requests, 1 SAP replies
        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-18 describes the fields that might possibly be shown in the display.

spf-interval

To control how often the access 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.

Syntax Description

Default

5 seconds

Command Mode

Router configuration

Usage Guidelines

SPF calculations are performed only when the router or access server topology changes. They are not performed when external routes change.

The spf-interval command controls how often the access 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 access server, but potentially slows down the rate of convergence.

Example

The following example sets the SPF calculation interval to 30 seconds:

spf-interval 30

Related Commands

lsp-gen-interval