Cisco IOS AppleTalk and Novell IPX Command Reference, Release 12.2
ipx nlsp enable to ipx sap-helper

Table Of Contents

ipx nlsp enable

ipx nlsp hello-interval

ipx nlsp hello-multiplier

ipx nlsp lsp-interval

ipx nlsp metric

ipx nlsp multicast

ipx nlsp priority

ipx nlsp retransmit-interval

ipx nlsp rip

ipx nlsp sap

ipx output-ggs-filter

ipx output-gns-filter

ipx output-network-filter (RIP)

ipx output-rip-delay

ipx output-sap-delay

ipx output-sap-filter

ipx pad-process-switched-packets

ipx per-host-load-share

ipx ping-default

ipx potential-pseudonode (NLSP)

ipx rip-max-packetsize

ipx rip-multiplier

ipx rip-queue-maximum

ipx rip-update-queue-maximum

ipx rip-response-delay

ipx route

ipx route-cache

ipx route-cache inactivity-timeout

ipx route-cache max-size

ipx route-cache update-timeout

ipx router

ipx router-filter

ipx router-sap-filter

ipx routing

ipx sap

ipx sap follow-route-path

ipx sap-helper


ipx nlsp enable

To enable NetWare Link-Services Protocol (NLSP) routing on the primary network configured on this interface or subinterface, use the ipx nlsp enable command in interface configuration mode. To disable NLSP routing on the primary network configured on this interface or subinterface, use the no form of this command.

ipx nlsp [tag] enable

no ipx nlsp [tag] enable

Syntax Description

tag

(Optional) Names the NLSP process. The tag can be any combination of printable characters.


Defaults

NLSP is disabled on all interfaces.

Command Modes

Interface configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines

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

When you specify an NLSP tag, the router enables NLSP on the specified process. An NLSP process is a router's databases working together to manage route information about an area. NLSP version 1.0 routers are always in the same area. Each router has its own adjacencies, link-state, and forwarding databases. These databases operate collectively as a single process to discover, select, and maintain route information about the area. NLSP version 1.1 routers that exist within a single area also use a single process.

NLSP version 1.1 routers that interconnect multiple areas use multiple processes to discover, select, and maintain route information about the areas they interconnect. These routers manage an adjacencies, link-state, and area address database for each area to which they attach. Collectively, these databases are still referred to as a process. The forwarding database is shared among processes within a router. The sharing of entries in the forwarding database is automatic when all processes interconnect NLSP version 1.1 areas.

Configure multiple NLSP processes when a router interconnects multiple NLSP areas.


Note NLSP version 1.1 routers refer to routers that support the route aggregation feature, while NLSP version 1.0 routers refer to routers that do not.


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

The following example enables NLSP routing for process area3 on Ethernet interface 0:

interface ethernet 0
 ipx nlsp area3 enable

Related Commands

Command
Description

ipx nlsp rip

Configures RIP compatibility when NLSP is enabled.

ipx nlsp sap

Configures SAP compatibility when NLSP in enabled.


ipx nlsp hello-interval

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

ipx nlsp [tag] hello-interval seconds

no ipx nlsp [tag] hello-interval seconds

Syntax Description

tag

(Optional) Names the NLSP process. The tag can be any combination of printable characters.

seconds

Time, in seconds, between the transmission of hello packets on the interface. It can be a number in the range 1 to 1600. The default is 10 seconds for the designated router and 20 seconds for nondesignated routers.


Defaults

10 seconds for the designated router.
20 seconds for nondesignated routers.

Command Modes

Interface configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines

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

Use this command to improve the speed at which a failed router or link is detected. A router is declared to be down if a hello has not been received from it for the time determined by the holding time (the hello interval multiplied by the holding time multiplier; by default, 60 seconds for nondesignated routers and 30 seconds for designated routers). You can reduce this time by lowering the hello-interval setting, at the cost of increased traffic overhead.

You may also use this command to reduce link overhead on very slow links by raising the hello interval. This will reduce the traffic on the link at the cost of increasing the time required to detect a failed router or link.

Examples

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

interface serial 0
 ipx ipxwan 2442 unnumbered local1
 ipx nlsp enable
 ipx nlsp hello-interval 30

Related Commands

Command
Description

ipx nlsp csnp-interval

Configures the NLSP CSNP interval.

ipx nlsp hello-multiplier

Configures the time delay between successive NLSP LSP transmissions.

ipx nlsp retransmit-interval

Configures RIP compatibility when NLSP is enabled.


ipx nlsp hello-multiplier

To specify the hello multiplier used on an interface, use the ipx nlsp hello-multiplier command in interface configuration mode. To restore the default value, use the no form of this command.

ipx nlsp [tag] hello-multiplier multiplier

no ipx nlsp [tag] hello-multiplier

Syntax Description

tag

(Optional) Names the NLSP process. The tag can be any combination of printable characters.

multiplier

Value by which to multiply the hello interval. It can be a number in the range 3 to 1000. The default is 3.


Defaults

The default multiplier is 3.

Command Modes

Interface configuration

Command History

Release
Modification

11.1

This command was introduced.


Usage Guidelines

You use the hello modifier in conjunction with the hello interval to determine the holding time value sent in a hello packet. The holding time is equal to the hello interval multiplied by the hello multiplier.

The holding time tells the neighboring router how long to wait for another hello packet from the sending router. If the neighboring router does not receive another hello packet in the specified time, then the neighboring router declares that the sending router is down.

You can use this method of determining the holding time when hello packets are lost with some frequency and NLSP adjacencies are failing unnecessarily. You raise the hello multiplier and lower the hello interval correspondingly to make the hello protocol more reliable without increasing the time required to detect a link failure.

Examples

In the following example, serial interface 0 will advertise hello packets every 15 seconds. The multiplier is 5. These values determine that the hello packet holding time is 75 seconds.

interface serial 0
 ipx nlsp hello-interval 15
 ipx nlsp hello-multiplier 5

Related Commands

Command
Description

ipx nlsp hello-interval

Specifies the hello multiplier used on an interface.


ipx nlsp lsp-interval

To configure the time delay between successive NetWare Link-Services Protocol (NLSP) link-state packet (LSP) transmissions, use the ipx nlsp lsp-interval command in interface configuration mode. To restore the default time delay, use the no form of this command.

ipx nlsp [tag] lsp-interval interval

no ipx nlsp [tag] lsp-interval

Syntax Description

tag

(Optional) Names the NLSP process. The tag can be any combination of printable characters.

interval

Time, in milliseconds, between successive LSP transmissions. The interval can be a number in the range 55 and 5000. The default interval is 55 milliseconds (ms).


Defaults

55 milliseconds

Command Modes

Interface configuration

Command History

Release
Modification

11.1

This command was introduced.


Usage Guidelines

This command allows you to control how fast LSPs can be flooded out an interface.

In topologies with a large number of NLSP neighbors and interfaces, a router may have difficulty with the CPU load imposed by LSP transmission and reception. This command allows you to reduce the LSP transmission rate (and by implication the reception rate of other systems).

Examples

The following example causes the system to transmit LSPs every 100 ms (10 packets per second) on Ethernet interface 0:

interface Ethernet 0
 ipx nlsp lsp-interval 100

Related Commands

Command
Description

ipx nlsp retransmit-interval

Configures RIP compatibility when NLSP is enabled.


ipx nlsp metric

To configure the NetWare Link-Services Protocol (NLSP) cost for an interface, use the ipx nlsp metric command in interface configuration mode. To restore the default cost, use the no form of this command.

ipx nlsp [tag] metric metric-number

no ipx nlsp [tag] metric metric-number

Syntax Description

tag

(Optional) Names the NLSP process. The tag can be any combination of printable characters.

metric-number

Metric value for the interface. It can be a number from 0 to 63.


Defaults

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

Command Modes

Interface configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines

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

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

Examples

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

interface serial 0
 ipx network 107
 ipx nlsp enable
 ipx nlsp metric 10

Related Commands

Command
Description

ipx nlsp enable

Configures the interval between the transmission of hello packets.


ipx nlsp multicast

To configure an interface to use multicast addressing, use the ipx nlsp multicast command in interface configuration mode. To configure the interface to use broadcast addressing, use the no form of this command.

ipx nlsp [tag] multicast

no ipx nlsp [tag] multicast

Syntax Description

tag

(Optional) Names the NLSP process. The tag can be any combination of printable characters.


Defaults

Multicast addressing is enabled.

Command Modes

Interface configuration

Command History

Release
Modification

11.3

This command was introduced.


Usage Guidelines

This command allows the router interface to use NLSP multicast addressing. If an adjacent neighbor does not support NLSP multicast addressing, the router will revert to using broadcasts on the affected interface.

The router will also revert to using broadcasts if multicast addressing is not supported by the hardware or driver.

Examples

The following example disables multicast addressing on Ethernet interface 0:

interface ethernet 0
 no ipx nlsp multicast

ipx nlsp priority

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

ipx nlsp [tag] priority priority-number

no ipx nlsp [tag] priority priority-number

Syntax Description

tag

(Optional) Names the NLSP process. The tag can be any combination of printable characters.

priority-number

Election priority of the designated router for the specified interface. This can be a number in the range 0 to 127. This value is unitless. The default is 44.


Defaults

44

Command Modes

Interface configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines

Use the ipx nlsp priority command to control which router is elected designated router. The device with the highest priority number is selected as the designated router.

The designated router increases its own priority by 20 in order to keep its state as of the designated router more stable. To have a particular router be selected as the designated router, configure its priority to be at least 65.

Examples

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

interface ethernet 0
 ipx network 101
 ipx nlsp enable
 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 command in interface configuration mode. To restore the default interval, use the no form of this command.

ipx nlsp [tag] retransmit-interval seconds

no ipx nlsp [tag] retransmit-interval seconds

Syntax Description

tag

(Optional) Names the NLSP process. The tag can be any combination of printable characters.

seconds

LSP retransmission interval, in seconds. This can be a number in the range 1 to 30. The default is 5 seconds.


Defaults

5 seconds

Command Modes

Interface configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines

This command sets the maximum amount of time that can pass before an LSP will be sent again (retransmitted) on a WAN link, if no acknowledgment is received.

Reducing the retransmission interval can improve the convergence rate of the network in the face of lost WAN links. The cost of reducing the retransmission interval is the potential increase in link utilization.

Examples

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

ipx nlsp retransmit-interval 2

Related Commands

Command
Description

ipx nlsp csnp-interval

Configures the NLSP CSNP interval.

ipx nlsp hello-interval

Specifies the hello multiplier used on an interface.


ipx nlsp rip

To configure RIP compatibility when NetWare Link-Services Protocol (NLSP) is enabled, use the ipx nlsp rip command in interface configuration mode. To restore the default, use the no form of this command.

ipx nlsp [tag] rip [on | off | auto]

no ipx nlsp [tag] rip [on | off | auto]

Syntax Description

tag

(Optional) Names the NLSP process. The tag can be any combination of printable characters.

on

(Optional) Always generates and sends RIP periodic traffic.

off

(Optional) Never generates and sends RIP periodic traffic.

auto

(Optional) Sends RIP periodic traffic only if another RIP router in sending periodic RIP traffic. This is the default.


Defaults

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

Command Modes

Interface configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines

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

Examples

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

interface ethernet 0
 ipx nlsp rip off

Related Commands

Command
Description

ipx nlsp enable

Configures the interval between the transmission of hello packets.

ipx nlsp sap

Configures SAP compatibility when NLSP in enabled.


ipx nlsp sap

To configure SAP compatibility when NetWare Link-Services Protocol (NLSP) in enabled, use the ipx nlsp sap command in interface configuration mode. To restore the default, use the no form of this command.

ipx nlsp [tag] sap [on | off | auto]

no ipx nlsp [tag] sap [on | off | auto]

Syntax Description

tag

(Optional) Names the NLSP process. The tag can be any combination of printable characters.

on

(Optional) Always generates and sends SAP periodic traffic.

off

(Optional) Never generates and sends SAP periodic traffic.

auto

(Optional) Sends SAP periodic traffic only if another SAP router in sending periodic SAP traffic. This is the default.


Defaults

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

Command Modes

Interface configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines

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

Examples

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

interface ethernet 0
 ipx nlsp sap off

Related Commands

Command
Description

ipx nlsp enable

Configures the interval between the transmission of hello packets.

ipx nlsp rip

Configures RIP compatibility when NLSP is enabled.


ipx output-ggs-filter

To control which servers are included in the Get General Service (GGS) responses sent by Cisco IOS software, use the ipx output-ggs-filter command in interface configuration mode. To remove the filter from the interface, use the no form of this command.

ipx output-ggs-filter {access-list-number | name}

no ipx output-ggs-filter {access-list-number | name}

Syntax Description

access-list-number

Number of the Service Advertising Protocol (SAP) access list. All outgoing GGS packets are filtered by the entries in this list. The access-list number is a number from 1000 to 1099.

name

Name of the access list. Names cannot contain a space or quotation mark, and they must begin with an alphabetic character to prevent their being confused with numbered access lists.


Defaults

No filters are predefined.

Command Modes

Interface configuration

Command History

Release
Modification

12.0(1)T

This command was introduced.


Usage Guidelines

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


Note Because GGS SAP response filters are applied ahead of output SAP filters, a SAP entry permitted to pass through the GGS SAP response filter can still be filtered by the output SAP filter.


Examples

The following example excludes the server at address 3c.0800.89a1.1527 from GGS responses sent on Ethernet interface 0, but allows all other servers:

access-list 1000 deny 3c.0800.89a1.1527
access-list 1000 permit -1
ipx routing

interface ethernet 0
 ipx network 2B 
 ipx output-ggs-filter 1000

Related Commands

Command
Description

access-list (SAP filtering)

Defines an access list for filtering SAP requests.

deny (SAP filtering)

Sets conditions for a named IPX SAP filtering access list.

ipx access-list

Defines an IPX access list by name.

ipx output-gns-filter

Controls which servers are included in the GGS responses sent by the Cisco IOS software.

ipx output-sap-filter

Controls which services are included in SAP updates sent by the Cisco IOS software.

ipx router-sap-filter

Filters SAP messages received from a particular router.

permit (SAP filtering)

Sets conditions for a named IPX SAP filtering access list.


ipx output-gns-filter

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

ipx output-gns-filter {access-list-number | name}

no ipx output-gns-filter {access-list-number | name}

Syntax Description

access-list-number

Number of the SAP access list. All outgoing GNS packets are filtered by the entries in this access list. The argument access-list-number is a number from 1000 to 1099.

name

Name of the access list. Names cannot contain a space or quotation mark, and they must begin with an alphabetic character to prevent ambiguity with numbered access lists.


Defaults

No filters are predefined.

Command Modes

Interface configuration

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

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

Examples

The following example excludes the server at address 3c.0800.89a1.1527 from GNS responses sent on Ethernet interface 0, but allows all other servers:

access-list 1000 deny 3c.0800.89a1.1527
access-list 1000 permit -1
ipx routing

interface ethernet 0
 ipx network 2B
 ipx output-gns-filter 1000

Related Commands

Command
Description

access-list (SAP filtering)

Defines an access list for filtering SAP requests.

deny (SAP filtering)

Sets conditions for a named IPX SAP filtering access list.

ipx access-list

Defines an IPX access list by name.

ipx gns-round-robin

Rotates using a round-robin selection method through a set of eligible servers when responding to GNS requests.

permit (SAP filtering)

Sets conditions for a named IPX SAP filtering access list.


ipx output-network-filter (RIP)

To control the list of networks included in routing updates sent out an interface, use the ipx output-network-filter command in interface configuration mode. To remove the filter from the interface, use the no form of this command.

ipx output-network-filter {access-list-number | name}

no ipx output-network-filter {access-list-number | name}

Syntax Description

access-list-number

Number of the access list. All outgoing packets defined with either standard or extended access lists are filtered by the entries in this access list. For standard access lists, access-list-number is a number from 800 to 899. For extended access lists, it is a number from 900 to 999.

name

Name of the access list. Names cannot contain a space or quotation mark, and they must begin with an alphabetic character to prevent ambiguity with numbered access lists.


Defaults

No filters are predefined.

Command Modes

Interface configuration

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

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

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

Examples

In the following example, access list 896 controls which networks are specified in routing updates sent out the serial 1 interface. This configuration causes network 2b to be the only network advertised in Novell routing updates sent on the specified serial interface.

access-list 896 permit 2b

interface serial 1
 ipx output-network-filter 896

Related Commands

Command
Description

access-list (IPX extended)

Defines an extended Novell IPX access list.

access-list (IPX standard)

Defines a standard IPX access list.

deny (extended)

Sets conditions for a named IPX extended access list.

deny (standard)

Sets conditions for a named IPX access list.

ipx access-list

Defines an IPX access list by name.

ipx input-network-filter

Controls which networks are added to the routing table of the Cisco IOS software.

ipx router-filter

Filters the routers from which packets are accepted.

permit (IPX extended)

Sets conditions for a named IPX extended access list.

prc-interval

Sets conditions for a named IPX access list.


ipx output-rip-delay

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

ipx output-rip-delay delay

no ipx output-rip-delay [delay]

Syntax Description

delay

Delay, in milliseconds (ms), between packets in a multiple-packet RIP update. The default delay is 55 ms. Novell recommends a delay of 55 ms.


Defaults

55 ms

Command Modes

Interface configuration

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

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

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

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

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

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

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

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

Examples

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

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

Related Commands

Command
Description

ipx default-output-rip-delay

Sets the default interpacket delay for RIP updates sent on all interfaces

ipx default-triggered-rip-delay

Sets the default interpacket delay for triggered RIP updates sent on all interfaces.

ipx triggered-rip-delay

Sets the interpacket delay for triggered RIP updates sent on a single interface.

ipx update sap-after-rip

Configures the router to send a SAP update immediately following a RIP broadcast.


ipx output-sap-delay

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

ipx output-sap-delay delay

no ipx output-sap-delay

Syntax Description

delay

Delay, in milliseconds, between packets in a multiple-packet SAP update. The default delay is 55 ms. Novell recommends a delay of 55 ms.


Defaults

55 ms

Command Modes

Interface configuration

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

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

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

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

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

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

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

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

Examples

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

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

Related Commands

Command
Description

ipx default-output-sap-delay

Sets a default interpacket delay for SAP updates sent on all interfaces.

ipx default-triggered-sap-delay

Sets the default interpacket delay for triggered SAP updates sent on all interfaces.

ipx linkup-request

Enables the sending of a general RIP or SAP query when an interface comes up.

ipx triggered-sap-delay

Sets the interpacket delay for triggered SAP updates sent on a single interface.


ipx output-sap-filter

To control which services are included in Service Advertising Protocol (SAP) updates sent by Cisco IOS software, use the ipx output-sap-filter command in interface configuration mode. To remove the filter, use the no form of this command.

ipx output-sap-filter {access-list-number | name}

no ipx output-sap-filter {access-list-number | name}

Syntax Description

access-list-number

Number of the SAP access list. All outgoing service advertisements are filtered by the entries in this access list. The argument access-list-number is a number from 1000 to 1099.

name

Name of the access list. Names cannot contain a space or quotation mark, and must begin with an alphabetic character to prevent ambiguity with numbered access lists.


Defaults

No filters are predefined.

Command Modes

Interface configuration

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

Cisco IOS software applies output SAP filters prior to sending SAP packets.

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

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

Examples

The following example denies service advertisements about server 0000.0000.0001 on network aa from being sent on network 4d (via Ethernet interface 1). All other services are advertised via this network. All services, included those from server aa.0000.0000.0001, are advertised via networks 3c and 2b.

access-list 1000 deny aa.0000.0000.0001
access-list 1000 permit -1

interface ethernet 0
 ipx network 3c

interface ethernet 1
 ipx network 4d
 ipx output-sap-filter 1000

interface serial 0
 ipx network 2b

Related Commands

Command
Description

access-list (SAP filtering)

Defines an access list for filtering SAP requests.

deny (SAP filtering)

Sets conditions for a named IPX SAP filtering access list.

ipx access-list

Defines an IPX access list by name.

ipx gns-round-robin

Rotates using a round-robin selection method through a set of eligible servers when responding to GNS requests.

ipx input-sap-filter

Controls which services are added to the routing table of the Cisco IOS software SAP table.

ipx router-sap-filter

Filters SAP messages received from a particular router.

permit (SAP filtering)

Sets conditions for a named IPX SAP filtering access list.


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 command in interface configuration mode. To disable padding, use the no form of this command.

ipx pad-process-switched-packets

no ipx pad-process-switched-packets

Syntax Description

This command has no arguments or keywords.

Defaults

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

Command Modes

Interface configuration

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

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

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

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

Examples

The following example configures the Cisco IOS software to pad odd-length packets so that they are sent as even-length packets on FDDI interface 1.

interface fddi 1
 ipx network 2A
 no ipx route-cache
 ipx pad-process-switched-packets

Related Commands

Command
Description

ipx route-cache

Enables IPX fast switching.


ipx per-host-load-share

To enable per-host load sharing, use the ipx per-host-load-share command in global configuration mode. To disable per-host load sharing, use the no form of this command.

ipx per-host-load-share

no ipx per-host-load-share

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Global configuration

Command History

Release
Modification

11.1

This command was introduced.


Usage Guidelines

Use this command to enable per-host load sharing. Per-host load sharing transmits traffic across multiple, equal-cost paths while guaranteeing that packets for a given end host always take the same path.

When you do not enable per-host load sharing, the software uses a round-robin algorithm to accomplish load sharing. Round-robin load sharing transmits successive packets over alternate, equal-cost paths, regardless of the destination host. With round-robin load sharing, successive packets destined for the same end host might take different paths. Thus, round-robin load sharing increases the possibility that successive packets to a given end host might arrive out of order or be dropped, but ensures true load balancing of a given workload across multiple links.

In contrast, per-host load sharing decreases the possibility that successive packets to a given end host will arrive out of order; but, there is a potential decrease in true load balancing across multiple links. True load sharing occurs only when different end hosts utilize different paths; equal link utilization cannot be guaranteed.

With per-host load balancing, the number of equal-cost paths set by the ipx maximum-paths command must be greater than one; otherwise, per-host load sharing has no effect.

Examples

The following command globally enables per-host load sharing:

ipx per-host-load share

Related Commands

Command
Description

ipx maximum-paths

Sets the maximum number of equal-cost paths the Cisco IOS software uses when forwarding packets.


ipx ping-default

To select the ping type that Cisco IOS software transmits, use the ipx ping-default command in global configuration mode. To return to the default ping type, use the no form of this command.

ipx ping-default {cisco | novell | diagnostic}

no ipx ping-default {cisco | novell | diagnostic}

Syntax Description

cisco

Transmits Cisco pings.

novell

Transmits standard Novell pings.

diagnostic

Transmits diagnostic request/response for IPX pings.


Defaults

Cisco pings

Command Modes

Global configuration

Command History

Release
Modification

10.3

This command was introduced.

12.0

The diagnostic keyword was added.


Usage Guidelines

This command can transmit Cisco pings, standard Novell pings as defined in the NLSP specification, and IPX diagnostic pings.

The IPX diagnostic ping feature addresses diagnostic related issues by accepting and processing unicast or broadcast diagnostic packets. It makes enhancements to the current IPX ping command to ping other stations using the diagnostic packets and display the configuration information in the response packet.


Note When a ping is sent from one station to another, the response is expected to come back immediately; when ipx ping-default is set to diagnostics, the response could consist of more than one packet and each node is expected to respond within 0.5 seconds of receipt of the request. Due to the absence of an end-of-message flag, there is a delay and the requester must wait for all responses to arrive. Therefore, in verbose mode there may be a brief delay of 0.5 seconds before the response data is displayed.

The ipx ping-default command using the diagnostic keyword can be used to conduct a reachability test and should not be used to measure accurate roundtrip delay.


Examples

The following is sample output from the ipx ping-default command when the diagnostic keyword is enabled:

Router# ipx ping-default diagnostic

Protocol [ip]: ipx
Target IPX address: 20.0000.0000.0001
Verbose [n]: y
Timeout in seconds [2]: 1
Type escape sequence to abort.
Sending 1, 31-byte IPX Diagnostic Echoes to 20.0000.0000.0001, timeout is 1 seconds:
Diagnostic Response from 20.0000.0000.0001 in 4 ms
Major Version: 1
Minor Version: 0
SPX Diagnostic Socket: 4002
Number of components: 3
Component ID: 0 (IPX / SPX)
Component ID: 1 (Router Driver)
Component ID: 5 (Router)
Number of Local Networks: 2
 Local Network Type: 0 (LAN Board)
  Network Address1 20
  Node Address1 0000.0000.0001
 Local Network Type: 0 (LAN Board)
  Network Address2 30
  Node Address2 0060.70cc.bc65

Note Verbose mode must be enabled to get diagnostic information.


Related Commands

Command
Description

ping (privileged)

Diagnoses basic network connectivity on AppleTalk, CLNS, IP, Novell, Apollo, VINES, DECnet, or XNS networks.

trace (privileged)

Discovers the specified protocol's routes that packets will actually take when traveling to their destination.


ipx potential-pseudonode (NLSP)

To enable NetWare Link Services Protocol (NLSP) to keep backup router and service information for potential pseudonode, use the ipx potential-pseudonode command in global configuration mode. To disable the feature so that NLSP does not keep backup router and service information for potential pseudonode, use the no form of this command.

ipx potential-pseudonode

no ipx potential-pseudonode

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled

Command Modes

Global configurat