- ipx sap
- ipx sap follow-route-path
- ipx sap-helper
- ipx sap-incremental (EIGRP)
- ipx sap-incremental split-horizon
- ipx sap-max-packetsize
- ipx sap-multiplier
- ipx sap-queue-maximum
- ipx sap-update-queue-maximum
- ipx server-split-horizon-on-server-paths
- ipx split-horizon eigrp
- ipx spx-idle-time
- ipx spx-spoof
- ipx throughput
- ipx triggered-rip-delay
- ipx triggered-rip-holddown
- ipx triggered-sap-delay
- ipx triggered-sap-holddown
- ipx type-20-helpered
- ipx type-20-input-checks
- ipx type-20-output-checks
- ipx type-20-propagation
- ipx update interval
- ipx update sap-after-rip
- ipx watchdog
- ipx watchdog-spoof
- log-adjacency-changes (IPX)
- log-neighbor-changes (EIGRP)
- log-neighbor-warnings
- lsp-gen-interval (IPX)
- lsp-mtu (IPX)
- lsp-refresh-interval (IPX)
- max-lsp-lifetime (IPX)
- multicast
- nasi authentication
- netbios access-list (IPX)
- network (IPX Enhanced IGRP)
- permit (IPX extended)
- permit (IPX standard)
- permit (NLSP)
- permit (SAP filtering)
- prc-interval (IPX)
- redistribute (IPX)
- route-aggregation (NLSP)
- show ipx access-list
- show ipx accounting
- show ipx cache
- show ipx eigrp interfaces
- show ipx eigrp neighbors
- show ipx eigrp topology
- show ipx eigrp traffic
- show ipx interface
- show ipx nasi connections
- show ipx nhrp
- show ipx nhrp traffic
- show ipx nlsp database
- show ipx nlsp neighbors
- show ipx nlsp spf-log
- show ipx route
- show ipx servers
- show ipx spx-spoof
- show ipx traffic
- show sse summary
- spf-interval
ipx sap
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx sap command is not supported in Cisco IOS software.
To specify static Service Advertising Protocol (SAP) entries, use the ipx sap command in global configuration mode. To remove static SAP entries, use the no form of this command.
ipx sap service-type name network.node socket hop-count
no ipx sap service-type name network.node socket hop-count
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
The ipx sap command allows you to add static entries into the SAP table. Each entry has a SAP service associated with it. Static SAP assignments always override any identical entries in the SAP table that are learned dynamically, regardless of hop count. The router will not announce a static SAP entry unless it has a route to that network.
Examples
In the following example, the route to JOES_SERVER is not yet learned, so the system displays an informational message. The JOES_SERVER service will not be announced in the regular SAP updates until Cisco IOS software learns the route to it either by means of a RIP update from a neighbor or an ipx sap command.
ipx sap 107 MAILSERV 160.0000.0c01.2b72 8104 1
ipx sap 4 FILESERV 165.0000.0c01.3d1b 451 1
ipx sap 143 JOES_SERVER A1.0000.0c01.1234 8170 2
no route to A1, JOES_SERVER won't be announced until route is learned
Related Commands
ipx sap follow-route-path
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, 15.2(2)T, and 15.1(1)SY, the ipx sap follow-route-path command is not supported in Cisco IOS software.
To enable a router to accept IPX Service Advertising Protocol (SAP) entries from SAP updates received on an interface only if that interface is one of the best paths to reach the destination networks of those SAPs, use the ipx sap follow-route-path command in global configuration mode. To disable this router function, use no form of this command.
ipx sap follow-route-path
no ipx sap follow-route-path
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
In redundantly connected networks that use IPX-Enhanced IGRP routing in which multiple IPX paths exist, IPX SAP services can be learned on nonoptimal interfaces, causing SAP loops, also known as phantom SAPs, when those services become obsolete. Use the ipx sap follow-route-path command to prevent the occurrence of SAP loops.
When the ipx sap follow-route-path command is used, the router screens individual services (SAPs) in SAP updates. The router looks at the destination network number of each SAP entry's . If the receiving interface is one of the best interfaces to reach the destination network of the SAP, that SAP entry is accepted. Otherwise, the SAP entry is discarded.
Examples
The following example enables the router to accept only the IPX SAP entries from SAP updates received on an interface deemed to be one of the best paths to the destination address of those SAPs:
ipx sap follow-route-path
Related Commands
|
|
---|---|
ipx server-split-horizon-on-server-paths |
Controls whether Service Information split horizon checking should be based on RIP or SAP. |
ipx sap-helper
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx sap-helper command is not supported in Cisco IOS software.
To set an address, which should be another Cisco router that is adjacent to the router being configured, to which all Service Advertising Protocol (SAP) request packets are received, use the ipx sap-helper command in interface configuration mode. To remove the address and stop forwarding SAP request packets, use the no form of this command.
ipx sap-helper network.node
no ipx sap-helper network.node
Syntax Description
Defaults
No helper address is specified.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to redirect SAP packet requests that are sent to a remote router that has a limited memory size, CPU speed, and often a slow WAN link joining it to the main corporate backbone. The SAP helper target is usually much a much larger router that has a much larger routing table and a complete SAP table.
Examples
The following example assigns a router with the address 1000.0000.0c00.1234 as the SAP helper:
interface ethernet 0
ipx sap-helper 1000.0000.0c00.1234
Related Commands
|
|
---|---|
ipx helper-address |
Forwards broadcast packets to a specified server. |
ipx sap-incremental (EIGRP)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx sap-incremental (EIGRP) command is not supported in Cisco IOS software.
To send Service Advertising Protocol (SAP) updates only when a change occurs in the SAP table, use the ipx sap-incremental command in interface configuration mode. To send periodic SAP updates, use the no form of this command.
ipx sap-incremental eigrp autonomous-system-number [rsup-only]
no ipx sap-incremental eigrp autonomous-system-number [rsup-only]
Syntax Description
Defaults
Enabled on serial interfaces
Disabled on LAN media (Ethernet, Token Ring, FDDI)
Command Modes
Interface configuration
Command History
Usage Guidelines
To use the ipx sap-incremental command, you must enable Enhanced IGRP. This is the case even if you want to use only RIP routing. You must do this because the incremental SAP feature requires the Enhanced IGRP reliable transport mechanisms.
With this functionality enabled, if an IPX Enhanced IGRP peer is found on the interface, SAP updates will be sent only when a change occurs in the SAP table. Periodic SAP updates are not sent. When no IPX Enhanced IGRP peer is present on the interface, periodic SAPs are always sent, regardless of how this command is set.
If you configure the local router to send incremental SAP updates on an Ethernet, and if the local device has at least one IPX Enhanced IGRP neighbor and any servers, clients, or routers that do not have IPX Enhanced IGRP configured on the Ethernet interface, these devices will not receive complete SAP information from the local router.
If the incremental sending of SAP updates on an interface is configured and no IPX Enhanced IGRP peer is found, SAP updates will be sent periodically until a peer is found. Then, updates will be sent only when changes occur in the SAP table.
To take advantage of Enhanced IGRP's incremental SAP update mechanism while using the RIP routing protocol instead of the Enhanced IGRP routing protocol, specify the rsup-only keyword. SAP updates are then sent only when changes occur, and only changes are sent. Use this feature only when you want to use RIP routing; Cisco IOS software disables the exchange of route information via Enhanced IGRP for that interface.
Examples
The following example sends SAP updates on Ethernet interface 0 only when there is a change in the SAP table:
interface ethernet 0
ipx sap-incremental eigrp 200
ipx sap-incremental split-horizon
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx sap-incremental split-horizon command is not supported in Cisco IOS software.
To configure incremental SAP split horizon, use the ipx sap-incremental split-horizon command in interface configuration mode. To disable split horizon, use the no form of this command.
ipx sap-incremental split-horizon
no ipx sap-incremental split-horizon
Syntax Description
This command has no argument or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
be turned on. Otherwise, a warning message like the following will be displayed:
%IPX EIGRP not running.
When split horizon is enabled, Enhanced IGRP incremental SAP update packets are not sent back to the same interface from where the SAP is received. This reduces the number of Enhanced IGRP packets on the network.
Split horizon blocks information about SAPs from being advertised by a router to the same interface from where that SAP is received. Typically, this behavior optimizes communication among multiple routers, particularly when links are broken. However, with nonbroadcast networks, such as Frame Relay and SMDS, situations can arise for which this behavior is less than ideal. For these situations, you may wish to disable split horizon.
Note IPX incremental SAP split horizon is off for WAN interfaces and subinterfaces, and on for LAN interfaces. The global default stays off. The interface setting takes precedence if the interface setting is modified or when both the global and interface settings are unmodified. The global setting is used only when global setting is modified and the interface setting is unmodified.
Examples
The following example disables split horizon on serial interface 0:
interface serial 0
no ipx sap-incremental split-horizon
Related Commands
ipx sap-max-packetsize
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx sap-max-packetsize command is not supported in Cisco IOS software.
To configure the maximum packet size of Service Advertising Protocol (SAP) updates sent out the interface, use the ipx sap-max-packetsize command in interface configuration mode. To restore the default packet size, use the no form of this command.
ipx sap-max-packetsize bytes
no ipx sap-max-packetsize bytes
Syntax Description
bytes |
Maximum packet size, in bytes. The default is 480 bytes, which allows for 7 servers (64 bytes each), plus 32 bytes of IPX network and SAP header information. |
Defaults
480 bytes
Command Modes
Interface configuration
Command History
Usage Guidelines
The maximum size is for the IPX packet, including the IPX network and SAP header information. For example, to allow 10 servers per SAP packet, you would configure (32 + (10 * 64)), or 672 bytes for the maximum packet size.
You are responsible for guaranteeing that the maximum packet size does not exceed the allowed maximum size of packets for the interface.
Examples
The following example sets the maximum SAP update packet size to 672 bytes:
ipx sap-max-packetsize 672
Related Commands
|
|
---|---|
ipx rip-max-packetsize |
Configures the maximum packet size of RIP updates sent out the interface. |
ipx sap-multiplier
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx sap-multipler command is not supported in Cisco IOS software.
To configure the interval at which a Service Advertising Protocol (SAP) entry for a network or server ages out, use the ipx sap-multiplier command in interface configuration mode. To restore the default interval, use the no form of this command.
ipx sap-multiplier multiplier
no ipx sap-multiplier multiplier
Syntax Description
Defaults
Three times the SAP update interval.
Command Modes
Interface configuration
Command History
Usage Guidelines
All routers on the same physical cable should use the same multiplier value.
Examples
In the following example, in a configuration where SAP updates are sent once every 1 minute, the interval at which SAP entries age out is set to 10 minutes:
interface ethernet 0
ipx sap-multiplier 10
Related Commands
|
|
---|---|
ipx sap-max-packetsize |
Configures the maximum packet size of SAP updates sent out the interface. |
ipx sap-queue-maximum
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, 15.2(2)T, and 15.1(1)SY, the ipx sap-queue-maximum command is not supported in Cisco IOS software.
To set an IPX Service Advertising Protocol (SAP) queue maximum to control how many SAP packets can be waiting to be processed at any given time, use the ipx sap-queue-maximum command in global configuration mode. To clear a set SAP queue maximum, use the no form of this command.
ipx sap-queue-maximum queue-maximum
no ipx sap-queue-maximum queue-maximum
Syntax Description
queue-maximum |
Specifies the queue limit as a number from 0 to the maximum unassigned integer. |
Defaults
No queue limit
Command Modes
Global configuration
Command History
Usage Guidelines
When you use the ipx sap-queue-maximum command to control how many SAP packets can be waiting to be processed at any given time, remember that if the queue limit is reached, the incoming SAP request packets are dropped. Be sure to set a large enough queue limit to handle normal incoming SAP requests on all interfaces, or else the SAP information may time out.
Examples
The following example sets a SAP queue maximum of 500 milliseconds:
ipx sap-queue-maximum 500
Related Commands
ipx sap-update-queue-maximum
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx sap-update-queue-maximum command is not supported in Cisco IOS software.
To set an IPX Service Advertising Protocol (SAP) queue maximum to control how many incoming SAP update packets can be waiting to be processed at any given time, use the ipx sap-update-queue-maximum command in global configuration mode. To clear a set SAP queue maximum, use the no form of this command.
ipx sap-update-queue-maximum queue-maximum
no ipx sap-update-queue-maximum queue-maximum
Syntax Description
queue-maximum |
Specifies the queue limit as a number from 0 to the maximum unassigned integer. |
Defaults
No queue limit
Command Modes
Global configuration
Command History
Usage Guidelines
When you use the ipx sap-update-queue-maximum command to control how many incoming SAP update packets can be waiting to be processed at any given time, remember that if the queue limit is reached, the incoming SAP update packets are dropped.
Note When using the ipx sap-update-queue-maximum command, be sure to set this queue high enough to handle a full update on all interfaces, or else the SAP information may time out.
Examples
The following example sets a SAP update queue maximum of 500:
ipx sap-update-queue-maximum 500
Related Commands
ipx server-split-horizon-on-server-paths
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, and 15.1(1)SY, the ipx server-split-horizon-on-server-paths command is not supported in Cisco IOS software.
To control whether Service Information split horizon checking should be based on Router Information Protocol (RIP) paths or Service Advertising Protocol (SAP) paths, use the ipx server-split-horizon-on-server-paths command in global configuration mode. To return to the normal mode of following route paths, use the no form of this command.
ipx server-split-horizon-on-server-paths
no ipx server-split-horizon-on-server-paths
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
By default, split horizon prevents information about periodic SAPs from being advertised by a router to the same interface in which the best route to that SAP is learned. However, in an instance where the SAP may be learned from interfaces other than, or in addition to, the interface on which the best route to that SAP is learned, using the ipx server-split-horizon-on-server-paths command may reduce the number of unnecessary periodic SAP updates. The reduction in the number of SAP updates occurs because each SAP will not be advertised on the interface or interfaces it was learned from. The reduction in the number of SAP updates will also prevent a potential SAP loop in the network.
Examples
The following example shows the application of split horizon blocks:
ipx server-split-horizon-on-server-paths
Related Commands
ipx split-horizon eigrp
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx split-horizon eigrp command is not supported in Cisco IOS software.
To configure split horizon, use the ipx split-horizon eigrp command in interface configuration mode. To disable split horizon, use the no form of this command.
ipx split-horizon eigrp autonomous-system-number
no ipx split-horizon eigrp autonomous-system-number
Syntax Description
autonomous-system-number |
Enhanced Interior Gateway Routing Protocol (EIGRP) autonomous system number. It can be a number from 1 to 65,535. |
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
When split horizon is enabled, Enhanced IGRP update and query packets are not sent for destinations that have next hops on this interface. This reduces the number of Enhanced IGRP packets on the network.
Split horizon blocks information about routes from being advertised by Cisco IOS software to any interface from which that information originated. Typically, this behavior optimizes communication among multiple routers, particularly when links are broken. However, with nonbroadcast networks, such as Frame Relay and Switched Multimegabit Data Service (SMDS), situations can arise for which this behavior is less than ideal. For these situations, you may wish to disable split horizon.
Examples
The following example disables split horizon on serial interface 0:
interface serial 0
no ipx split-horizon eigrp 200
ipx spx-idle-time
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx spx-idle-time command is not supported in Cisco IOS software.
To set the amount of time to wait before starting the spoofing of Sequenced Packet Exchange (SPX) keepalive packets following inactive data transfer, use the ipx spx-idle-time command in interface configuration mode. To disable the current delay time set by this command, use the no form of this command.
ipx spx-idle-time delay-in-seconds
no ipx spx-idle-time
Syntax Description
delay-in-seconds |
The amount of time, in seconds, to wait before spoofing SPX keepalives after data transfer has stopped. |
Defaults
60 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
This command sets the elapsed time in seconds after which spoofing of keepalive packets occurs, following the end of data transfer; that is, after the acknowledgment and sequence numbers of the data being transferred have stopped increasing. By default, SPX keepalive packets are sent from servers to clients every 15 to 20 seconds.
If you turn on SPX spoofing and you do not set an idle time, the default of 60 seconds is assumed. This means that the dialer idle time begins when SPX spoofing begins. For example, if the dialer idle time is 3 minutes, the elapse time before SPX spoofing begins is 4 minutes: 3 minutes of dialer idle time plus 1 minute of SPX spoofing idle time.
For this command to take effect, you must first use the ipx spx-spoof interface configuration command to enable SPX spoofing for the interface.
Examples
The following example enables spoofing on serial interface 0 and sets the idle timer to 300 seconds:
interface serial 0
ipx spx-spoof
no ipx route-cache
ipx spx-idle-time 300
Related Commands
ipx spx-spoof
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, 15.2(2)T, and 15.1(1)SY, the ipx spx-spoof command is not supported in Cisco IOS software.
To configure Cisco IOS software to respond to a client or server's Sequenced Packet Exchange (SPX) keepalive packets on behalf of a remote system so that a dial-on-demand (DDR) link will go idle when data has stopped being transferred, use the ipx spx-spoof command in interface configuration mode. To disable spoofing, use the no form of this command.
ipx spx-spoof [session-clear session-clear-minutes | table-clear table-clear-hours]
no ipx spx-spoof [session-clear | table-clear]
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
You can use the ipx spx-spoof command on any serial dialer or point-to-point interface. Fast switching and autonomous switching must be disabled on the interface; otherwise, SPX spoofing will not be permitted.
SPX keepalive packets are sent from servers to clients every 15 to 20 seconds after a client session has been idle for a certain period of time following the end of data transfer and after which only unsolicited acknowledgments are sent. The idle time may vary, depending on parameters set by the client and server.
Because of acknowledgment packets, a session would never go idle on a DDR link. On pay-per-packet or byte networks, these keepalive packets can incur for the customer large phone connection charges for idle time. You can prevent these calls from being made by configuring the software to respond to the server's keepalive packets on a remote client's behalf. This is sometimes referred to as "spoofing the server."
You can use the ipx spx-idle-time command to set the elapsed time in seconds after which spoofing of keepalive packets occurs, following the end of data transfer. If you turn on SPX spoofing and you do not set an idle time, the default of 60 seconds is assumed. This means that the dialer idle time begins when SPX spoofing begins. For example, if the dialer idle time is 3 minutes, the elapse time before the line goes "idle-spoofing" is 4 minutes: 3 minutes of dialer idle time plus 1 minute of SPX spoofing idle time.
Examples
The following example enables spoofing on serial interface 0:
interface serial 0
ipx spx-spoof
no ipx route-cache
Related Commands
|
|
---|---|
ipx throughput |
Configures the throughput. |
show ipx spx-spoof |
Displays the table of SPX connections through interfaces for which SPX spoofing is enabled. |
ipx throughput
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx throughput command is not supported in Cisco IOS software.
To configure the throughput, use the ipx throughput command in interface configuration mode. To revert to the current bandwidth setting for the interface, use the no form of this command.
ipx throughput bits-per-second
no ipx throughput bits-per-second
Syntax Description
bits-per-second |
Throughput, in bits per second. |
Defaults
Current bandwidth setting for the interface
Command Modes
Interface configuration
Command History
Usage Guidelines
The value you specify with the ipx throughput command overrides the value measured by IPXWAN when it starts.
Examples
The following example changes the throughput to 1,000,000 bits per second:
ipx throughput 1000000
Related Commands
|
|
---|---|
ipx ipxwan |
Enables the IPXWAN protocol on a serial interface. |
ipx triggered-rip-delay
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx triggered-rip-delay command is not supported in Cisco IOS software.
To set the interpacket delay for triggered Routing Information Protocol (RIP) updates sent on a single interface, use the ipx triggered-rip-delay command in interface configuration mode. To return to the default delay, use the no form of this command.
ipx triggered-rip-delay delay
no ipx triggered-rip-delay [delay]
Syntax Description
delay |
Delay, in milliseconds, between packets in a multiple-packet RIP update. The default delay is 55 ms. Novell recommends a delay of 55 ms. |
Defaults
55 ms
Command Modes
Interface configuration
Command History
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet routing update. A triggered routing update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.
The ipx triggered-rip-delay command sets the interpacket delay for triggered routing updates sent on a single interface. The delay value set by this command overrides the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered routing updates sent on the interface.
If the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command is high, then we strongly recommend a low delay value for triggered routing updates so that updates triggered by special events are sent in a more timely manner than periodic routing updates.
Novell recommends a delay of 55 ms for compatibility with older and slower IPX machines. These machines may lose RIP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX machines.
The default delay on a NetWare 3.11 server is about 100 ms.
When you do not set the interpacket delay for triggered routing updates, the system uses the delay specified by the ipx output-rip-delay or ipx default-output-rip-delay command for both periodic and triggered routing updates.
When you use the no form of the ipx triggered-rip-delay command, the system uses the global default delay set by the ipx default-triggered-rip-delay command for triggered RIP updates, if it is set. If it is not set, the system uses the delay set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered RIP updates, if set. Otherwise, the system uses the initial default delay as described in the "Defaults" section.
This command is also useful on limited bandwidth point-to-point links, or X.25 and Frame Relay multipoint interfaces.
Examples
The following example sets an interpacket delay of 55 ms for triggered routing updates sent on interface FDDI 0:
interface FDDI 0
ipx triggered-rip-delay 55
Related Commands
ipx triggered-rip-holddown
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx triggered-rip-holddown command is not supported in Cisco IOS software.
To set the amount of time for which an IPX Routing Information Protocol (RIP) process will wait before sending flashes about RIP changes, use the ipx triggered-rip-holddown command in interface configuration mode. To remove the RIP hold-down, use the no form of this command.
ipx triggered-rip-holddown milliseconds
no ipx triggered-rip-holddown milliseconds
Syntax Description
milliseconds |
Amount of time, in milliseconds, for which the router will wait before sending flashes about RIP changes. |
Defaults
55 milliseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
To set a default hold-down used for all interfaces, use the ipx default-triggered-rip-holddown command in global configuration mode.
Examples
The following example shows a hold-down time of 100 milliseconds:
interface ether 0
ipx triggered-rip-holddown 100
Related Commands
ipx triggered-sap-delay
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx triggered-sap-delay command is not supported in Cisco IOS software.
To set the interpacket delay for triggered Service Advertising Protocol (SAP) updates sent on a single interface, use the ipx triggered-sap-delay command in interface configuration mode. To return to the default delay, use the no form of this command.
ipx triggered-sap-delay delay
no ipx triggered-sap-delay [delay]
Syntax Description
delay |
Delay, in milliseconds, between packets in a multiple-packet SAP update. The default delay is 55 ms. Novell recommends a delay of 55 ms. |
Defaults
55 ms
Command Modes
Interface configuration
Command History
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet SAP update. A triggered SAP update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.
The ipx triggered-sap-delay command sets the interpacket delay for triggered updates sent on a single interface. The delay value set by this command overrides the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered updates sent on the interface.
If the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command is high, then we strongly recommend a low delay value for triggered updates so that updates triggered by special events are sent in a more timely manner than periodic updates.
Novell recommends a delay of 55 ms for compatibility with older and slower IPX servers. These servers may lose SAP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX servers.
The default delay on a NetWare 3.11 server is about 100 ms.
When you do not set the interpacket delay for triggered updates, the system uses the delay specified by the ipx output-sap-delay or ipx default-output-sap-delay command for both periodic and triggered SAP updates.
When you use the no form of the ipx triggered-sap-delay command, the system uses the global default delay set by the ipx default-triggered-sap-delay command for triggered SAP updates, if it is set. If it is not set, the system uses the delay set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered SAP updates, if set. Otherwise, the system uses the initial default delay as described in the "Defaults" section.
This command is also useful on limited bandwidth point-to-point links, or X.25 and Frame Relay multipoint interfaces.
Examples
The following example sets an interpacket delay of 55 ms for triggered SAP updates sent on interface FDDI 0:
interface FDDI 0
ipx triggered-sap-delay 55
Related Commands
ipx triggered-sap-holddown
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx triggered-sap-holddown command is not supported in Cisco IOS software.
To set the amount of time for which a Service Advertising Protocol (SAP) process will wait before sending flashes about SAP changes, use the ipx triggered-sap-holddown command in interface configuration mode. To remove the SAP hold-down, use the no form of this command.
ipx triggered-sap-holddown milliseconds
no ipx triggered-sap-holddown milliseconds
Syntax Description
milliseconds |
Amount of time, in milliseconds, for which the router will wait before sending flashes about RIP changes. |
Defaults
55 milliseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
To set a default hold-down used for all interfaces, use the ipx default-triggered-sap-holddown command in global configuration mode.
Examples
The following example shows a hold-down time of 100 milliseconds:
interface ethernet 0
ipx triggered-sap-holddown 100
Related Commands
ipx type-20-helpered
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, 15.2(2)T, and 15.1(1)SY, the ipx type-20-helpered command is not supported in Cisco IOS software.
To forward IPX type 20 propagation packet broadcasts to specific network segments, use the ipx type-20-helpered command in global configuration mode. To disable this function, use the no form of this command.
ipx type-20-helpered
no ipx type-20-helpered
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
The ipx type-20-helpered command disables the input and output of type 20 propagation packets as done by the ipx type-20-propagation interface configuration command.
The ipx type-20-propagation command broadcasts type 20 packets to all nodes on the network and imposes a hop-count limit of eight routers for broadcasting these packets. These functions are in compliance with the Novell IPX router specification. In contrast, the ipx type-20-helpered command broadcasts type 20 packets to only those nodes indicated by the ipx helper-address interface configuration command and extends the hop-count limit to 16 routers.
Use of the ipx type-20-helpered command does not comply with the Novell IPX router specification; however, you may need to use this command if you have a mixed internetwork that contains routers running Software Release 9.1 and routers running later versions of Cisco IOS software.
Examples
The following example forwards IPX type 20 propagation packet broadcasts to specific network segments:
interface ethernet 0
ipx network aa
ipx type-20-helpered
ipx helper-address bb.ffff.ffff.ffff
Related Commands
|
|
---|---|
ipx helper-address |
Forwards broadcast packets to a specified server. |
ipx type-20-propagation |
Forwards IPX type 20 propagation packet broadcasts to other network segments. |
ipx type-20-input-checks
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, 15.2(2)T, and 15.1(1)SY, the ipx type-20-input-checks command is not supported in Cisco IOS software.
To restrict the acceptance of IPX type 20 propagation packet broadcasts, use the ipx type-20-input-checks command in global configuration mode. To remove these restrictions, use the no form of this command.
ipx type-20-input-checks
no ipx type-20-input-checks
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
By default, Cisco IOS software is configured to block type 20 propagation packets. When type 20 packet handling is enabled on multiple interfaces, you can use the ipx type-20-input-checks command to impose additional restrictions on the acceptance of type 20 packets. Specifically, the software will accept type 20 propagation packets only on the single network that is the primary route back to the source network. Similar packets received via other networks will be dropped. This behavior can be advantageous in redundant topologies, because it reduces unnecessary duplication of type 20 packets.
Examples
The following example imposes additional restrictions on incoming type 20 broadcasts:
ipx type-20-input-checks
Related Commands
ipx type-20-output-checks
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, 15.2(2)T, and 15.1(1)SY, the ipx type-20-output-checks command is not supported in Cisco IOS software.
To restrict the forwarding of IPX type 20 propagation packet broadcasts, use the ipx type-20-output-checks command in global configuration mode. To remove these restrictions, use the no form of this command.
ipx type-20-output-checks
no ipx type-20-output-checks
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
By default, Cisco IOS software is configured to block type 20 propagation packets. When type 20 packet handling is enabled on multiple interfaces, you can use the ipx type-20-output-checks command to impose additional restrictions on outgoing type 20 packets. Specifically, the software will forward these packets only to networks that are not routes back to the source network. (The software uses the current routing table to determine routes.) This behavior can be advantageous in redundant topologies, because it reduces unnecessary duplication of type 20 packets.
Examples
The following example imposes restrictions on outgoing type 20 broadcasts:
ipx type-20-output-checks
Related Commands
ipx type-20-propagation
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx type-20-propagation command is not supported in Cisco IOS software.
To forward IPX type 20 propagation packet broadcasts to other network segments, use the ipx type-20-propagation command in interface configuration mode. To disable both the reception and forwarding of type 20 broadcasts on an interface, use the no form of this command.
ipx type-20-propagation
no ipx type-20-propagation
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Routers normally block all broadcast requests. To allow input and output of type 20 propagation packets on an interface, use the ipx type-20-propagation command. Note that type 20 packets are subject to loop detection and control as specified in the IPX router specification.
Additional input and output checks may be imposed by the ipx type-20-input-checks and
ipx type-20-output-checks commands.
IPX type 20 propagation packet broadcasts are subject to any filtering defined by the ipx helper-list command.
Examples
The following example enables both the reception and forwarding of type 20 broadcasts on Ethernet interface 0:
interface ethernet 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 update interval
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx update interval command is not supported in Cisco IOS software.
To adjust the Routing Information Protocol (RIP) or Service Advertising Protocol (SAP) update interval, use the ipx update interval command in interface configuration mode. To restore the default values, use the no form of this command.
ipx update interval {rip | sap} {value | changes-only}
no ipx update interval {rip | sap}
Syntax Description
Defaults
The default interval is 60 seconds for both IPX routing updates and SAP updates.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command replaces two commands found in previous releases of Cisco IOS software: ipx sap-interval and ipx update-time.
Routers exchange information about routes by sending broadcast messages when they are started up and shut down, and periodically while they are running. The ipx update interval command enables you to modify the periodic update interval. By default, this interval is 60 seconds (this default is defined by Novell).
You should set RIP timers only in a configuration in which all routers are Cisco routers or in which all other IPX routers allow configurable timers. The timers should be the same for all devices connected to the same cable segment.
The update value you choose affects the internal IPX timers as follows:
•IPX routes are marked invalid if no routing updates are heard within three times the value of the update interval 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.
Setting the interval at which SAP updates are sent is most useful on limited-bandwidth links, such as slower-speed serial interfaces.
You should ensure that all IPX servers and routers on a given network have the same SAP interval. Otherwise, they may decide that a server is down when it is really up.
It is not possible to change the interval at which SAP updates are sent on most PC-based servers. This means that you should never change the interval for an Ethernet or Token Ring network that has servers on it.
You can set the router to send an update only when changes have occurred. Using the changes-only keyword specifies the sending of a SAP update only when the link comes up, when the link is downed administratively, or when the databases change. The changes-only keyword causes the router to do the following:
•Send a single, full broadcast update when the link comes up.
•Send appropriate triggered updates when the link is shut down.
•Send appropriate triggered updates when specific service information changes.
Examples
The following example configures the update timers for RIP updates on two interfaces in a router:
interface serial 0
ipx update interval rip 40
interface ethernet 0
ipx update interval rip 20
The following example configures SAP updates to be sent (and expected) on serial interface 0 every 300 seconds (5 minutes) to reduce periodic update overhead on a slow-speed link:
interface serial 0
ipx update interval sap 300
Related Commands
ipx update sap-after-rip
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx update sap-after-rip command is not supported in Cisco IOS software.
To configure the router to send a Service Advertising Protocol (SAP) update immediately following a Routing Information Protocol (RIP) broadcast, use the ipx update sap-after-rip command in interface configuration mode. To restore the default value, use the no form of this command.
ipx update sap-after-rip
no ipx update sap-after-rip
Syntax Description
This command has no arguments or keywords.
Defaults
RIP and SAP updates are sent every 60 seconds.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipx update sap-after-rip command causes the router to issue a SAP update immediately following a RIP broadcast. This ensures that the SAP update follows the RIP broadcast, and that the SAP update is sent using the RIP update interval. It also ensures that the receiving router has learned the route to the service interface via RIP prior to getting the SAP broadcast.
Examples
The following example configures the router to issue a SAP broadcast immediately following a RIP broadcast on serial interface 0.
interface serial 0
ipx update sap-after-rip
Related Commands
ipx watchdog
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the ipx watchdog command is not supported in Cisco IOS software.
To enable watchdog, use the ipx watchdog command in interface configuration mode. To specify filtering, spoofing, or how long spoofing is to be enabled or disabled, use arguments and keywords. To disable filtering or spoofing, use the no form of this command.
ipx watchdog {filter | spoof [enable-time-hours disable-time-minutes]}
no ipx watchdog {filter | spoof}
Syntax Description
Defaults
There is no watchdog processing.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the ipx watchdog command when you want to enable watchdog processing. Use this command only on a serial interface with dial-on-demand (DDR) routing enabled.
Using the filter keyword when the DDR link is not connected will cause IPX server watchdog packets to be discarded, preventing them from bringing the DDR link up again.
Using the spoof keyword will allow IPX server watchdog packets to be answered when the DDR link is not connected. You can control how long spoofing is to be enabled or disabled by using the enable-time-hours and disable-time-minutes arguments.
Related Commands
ipx watchdog-spoof
The ipx watchdog-spoof command is replaced by the ipx watchdog command. See the description of the ipx watchdog command in this chapter for more information.
log-adjacency-changes (IPX)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the log-adjaceny-changes (IPX) command is not supported in Cisco IOS software.
To generate a log message when an NetWare Link-Services Protocol (NLSP) adjacency changes state (up or down), use the log-adjacency-changes command in IPX-router configuration mode. To disable this function, use the no form of this command.
log-adjacency-changes
no log-adjacency-changes
Syntax Description
This command has no arguments or keywords.
Defaults
Adjacency changes are not logged.
Command Modes
IPX-router configuration
Command History
Usage Guidelines
This command allows the monitoring of NLSP adjacency state changes. Adjacency state monitoring can be very useful when monitoring large networks. Messages are logged using the system error message facility. Messages are of the form:
%CLNS-5-ADJCHANGE: NLSP: Adjacency to 0000.0000.0034 (Serial0) Up, new adjacency
%CLNS-5-ADJCHANGE: NLSP: Adjacency to 0000.0000.0034 (Serial0) Down, hold time expired
Messages regarding the use of NLSP multicast and broadcast addressing are also logged. For example, if broadcast addressing is in use on Ethernet interface 1.2, and the last neighbor requiring broadcasts goes down, the following messages will be logged:
%CLNS-5-ADJCHANGE: NLSP: Adjacency to 0000.0C34.D838 (Ethernet1.2) Down, hold time expired
%CLNS-5-MULTICAST: NLSP: Multicast address in use on Ethernet1.2
If multicast addressing is in use and a new neighbor that supports only broadcast addressing comes up, the following messages will be logged:
%CLNS-5-ADJCHANGE: NLSP: Adjacency to 0000.0C34.D838 (Ethernet1.2) Up, new adjacency
%CLNS-5-MULTICAST: NLSP Broadcast address is in use on Ethernet1.2
Examples
The following example instructs the router to log adjacency changes for the NLSP process area1:
ipx router nlsp area1
log-adjacency-changes
Related Commands
|
|
---|---|
logging |
Logs messages to a syslog server host. |
log-neighbor-changes (EIGRP)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the log-neighbor-changes (EIGRP) command is not supported in Cisco IOS software.
To enable the logging of changes in Enhanced Interior Gateway Routing Protocol (EIGRP) neighbor adjacencies, use the log-neighbor-changes command in IPX-router configuration mode. To disable this function, use the no form of this command.
log-neighbor-changes
no log-neighbor-changes
Syntax Description
This command has no arguments or keywords.
Defaults
No adjacency changes are logged.
Command Modes
IPX-router configuration
Command History
Usage Guidelines
Enable the logging of neighbor adjacency changes in order to monitor the stability of the routing system and to help detect problems. Log messages are of the following form:
%DUAL-5-NBRCHANGE: IPX EIGRP as-number: Neighbor address (interface) is state: reason
as-number |
Autonomous system number |
address (interface) |
Neighbor address |
state |
Up or down |
reason |
Reason for change |
where the arguments have the following meanings:
Examples
The following configuration will log neighbor changes for EIGRP process 209:
ipx router eigrp 209
log-neighbor-changes
log-neighbor-warnings
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the log-neighbor-warnings command is not supported in Cisco IOS software.
Note Effective with Cisco IOS Release 15.0(1)M, 12.2(33)SRE and Cisco IOS XE Release 2.5, the log-neighbor-warnings command was replaced by the eigrp log-neighbor-warnings command for IPv4 and IPv6 configurations. The log-neighbor-warnings command is still available for IPX configurations.
To enable the logging of Enhanced Interior Gateway Routing Protocol (EIGRP) neighbor warning messages, use the log-neighbor-warnings command in router configuration mode. To disable the logging of EIGRP neighbor warning messages, use the no form of this command.
log-neighbor-warnings [seconds]
no log-neighbor-warnings
Syntax Description
seconds |
(Optional) The time interval (in seconds) between repeated neighbor warning messages. The range of seconds is from 1 through 65535. |
Command Default
Neighbor warning messages are logged.
Command Modes
Router configuration (config-router)
Command History
Usage Guidelines
When neighbor warning messages occur, they are logged by default. With the log-neighbor-warnings command, you can disable and enable the logging of neighbor warning messages and configure the interval between repeated neighbor warning messages.
Examples
The following example shows that neighbor warning messages will be logged for EIGRP process 1 and warning messages will be repeated in 5-minute (300 seconds) intervals:
Router(config)# ipv6 router eigrp 1
Router(config-router)# log-neighbor-warnings 300
Related Commands
|
|
---|---|
log-neighbor-changes |
Enables the logging of changes in EIGRP neighbor adjacencies. |
lsp-gen-interval (IPX)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the lsp-gen-interval (IPX) command is not supported in Cisco IOS software.
To set the minimum interval at which link-state packets (LSPs) are generated, use the lsp-gen-interval command in router configuration mode. To restore the default interval, use the no form of this command.
lsp-gen-interval seconds
no lsp-gen-interval seconds
Syntax Description
seconds |
Minimum interval, in seconds. It can be a number in the range 0 to 120. The default is 5 seconds. |
Defaults
5 seconds
Command Modes
Router configuration
Command History
Usage Guidelines
The lsp-gen-interval command controls the rate at which LSPs are generated on a per-LSP basis. For instance, if a link is changing state at a high rate, the default value of the LSP generation interval limits the signaling of this change to once every 5 seconds. Because the generation of an LSP may cause all routers in the area to perform the SPF calculation, controlling this interval may have area-wide impact. Raising this interval can reduce the load on the network imposed by a rapidly changing link.
Examples
The following example sets the minimum interval at which LSPs are generated to 10 seconds:
lsp-gen-interval 10
Related Commands
|
|
---|---|
ipx router |
Specifies the routing protocol to use. |
spf-interval |
Controls how often Cisco IOS software performs the SPF calculation. |
lsp-mtu (IPX)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the lsp-mtu (IPX) command is not supported in Cisco IOS software.
To set the maximum size of a link-state packet (LSP) generated by Cisco IOS software, use the lsp-mtu command in router configuration mode. To restore the default Maximum Transmission Unit (MTU) size, use the no form of this command.
lsp-mtu bytes
no lsp-mtu bytes
Syntax Description
bytes |
MTU size, in bytes. It can be a number in the range 512 to 4096. The default is 512 bytes. |
Defaults
512 bytes
Command Modes
Router configuration
Command History
Usage Guidelines
You can increase the LSP MTU if there is a very large amount of information generated by a single router, because each device is limited to approximately 250 LSPs. In practice, this should never be necessary.
The LSP MTU must never be larger than the smallest MTU of any link in the area. This is because LSPs are flooded throughout the area.
The lsp-mtu command limits the size of LSPs generated by this router only; Cisco IOS software can receive LSPs of any size up to the maximum.
Examples
The following example sets the maximum LSP size to 1500 bytes:
lsp-mtu 1500
Related Commands
|
|
---|---|
ipx router |
Specifies the routing protocol to use. |
lsp-refresh-interval (IPX)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the lsp-refresh-interval (IPX) command is not supported in Cisco IOS software.
To set the link-state packet (LSP) refresh interval, use the lsp-refresh-interval command in router configuration mode. To restore the default refresh interval, use the no form of this command.
lsp-refresh-interval seconds
no lsp-refresh-interval seconds
Syntax Description
seconds |
Refresh interval, in seconds. It can be a value in the range 1 to 50,000 seconds. The default is 7200 seconds (2 hours). |
Defaults
7200 seconds (2 hours)
Command Modes
Router configuration
Command History
Usage Guidelines
The refresh interval determines the rate at which Cisco IOS software periodically transmits the route topology information that it originates. This is done in order to keep the information from becoming too old. By default, the refresh interval is 2 hours.
LSPs must be periodically refreshed before their lifetimes expire. The refresh interval must be less than the LSP lifetime specified with the max-lsp-lifetime (IPX) router configuration command. Reducing the refresh interval reduces the amount of time that undetected link state database corruption can persist at the cost of increased link utilization. (This is an extremely unlikely event, however, because there are other safeguards against corruption.) Increasing the interval reduces the link utilization caused by the flooding of refreshed packets (although this utilization is very small).
Examples
The following example changes the LSP refresh interval to 10,800 seconds (3 hours):
lsp-refresh-interval 10800
Related Commands
|
|
---|---|
ipx router |
Specifies the routing protocol to use. |
max-lsp-lifetime (IPX) |
Sets the maximum time that LSPs persist without being refreshed. |
max-lsp-lifetime (IPX)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the max-lsp-lifetime (IPX) command is not supported in Cisco IOS software.
To set the maximum time for which link-state packets (LSPs) persist without being refreshed, use the max-lsp-lifetime command in router configuration mode. To restore the default time, use the no form of this command.
max-lsp-lifetime [hours] value
no max-lsp-lifetime
Syntax Description
Defaults
7500 seconds (2 hours, 5 minutes)
Command Modes
Router configuration
Command History
Usage Guidelines
The hours keyword enables the router to interpret the maximum lifetime field in hours, allowing the router to keep LSPs for a much longer time. Keeping LSPs longer reduces overhead on slower-speed serial links and keeps ISDN links from becoming active unnecessarily.
You might need to adjust the maximum LSP lifetime if you change the LSP refresh interval with the lsp-refresh-interval (IPX) router configuration command. The maximum LSP lifetime must be greater than the LSP refresh interval.
Examples
The following example sets the maximum time that the LSP persists to 11,000 seconds (more than 3 hours):
max-lsp-lifetime 11000
The following example sets the maximum time that the LSP persists to 15 hours:
max-lsp-lifetime hours 15
Related Commands
|
|
---|---|
ipx router |
Specifies the routing protocol to use. |
lsp-refresh-interval (IPX) |
Sets the LSP refresh interval. |
multicast
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the multicast command is not supported in Cisco IOS software.
To configure the router to use multicast addressing, use the multicast command in router configuration mode. To configure the router to use broadcast addressing, use the no form of this command.
multicast
no multicast
Syntax Description
This command has no arguments or keywords.
Defaults
Multicast addressing is enabled.
Command Modes
Router configuration
Command History
Usage Guidelines
This command allows the router to use NetWare Link-Services Protocol (NLSP) multicast addressing. If an adjacent neighbor does not support NLSP multicast addressing, the router will revert to using broadcasts on the affected interface.
The router will also revert to using broadcasts on any interface where multicast addressing is not supported by the hardware or driver.
Examples
The following example disables multicast addressing on the router:
ipx router nlsp
no multicast
nasi authentication
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the nasi authentication command is not supported in Cisco IOS software.
To enable authentication, authorization, and accounting (AAA) authentication for NetWare Asynchronous Services Interface (NASI) clients connecting to a router, use the nasi authentication command in line configuration mode. To return to the default, as specified by the aaa authentication nasi command, use the no form of the command.
nasi authentication {default | list-name}
no nasi authentication {default | list-name}
Syntax Description
default |
Uses the default list created with the aaa authentication nasi command. |
list-name |
Uses the list created with the aaa authentication nasi command. |
Defaults
Uses the default set with the aaa authentication nasi command.
Command Modes
Line configuration
Command History
Usage Guidelines
This command is a per-line command used with AAA authentication that specifies the name of a list of authentication methods to try at login. If no list is specified, the default list is used, even if it is not specified in the command line. (You create defaults and lists with the aaa authentication nasi command.) Entering the no form of this command has the same effect as entering the command with the default argument.
Before issuing this command, create a list of authentication processes by using the aaa authentication nasi global configuration command.
Examples
The following example specifies that the default AAA authentication be used on line 4:
line 4
nasi authentication default
The following example specifies that the AAA authentication list called list1 be used on line 7:
line 7
nasi authentication list1
Related Commands
netbios access-list (IPX)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the netbios access-list (IPX) command is not supported in Cisco IOS software.
To define an IPX NetBIOS FindName access list filter, use the netbios access-list command in global configuration mode. To remove a filter, use the no form of this command.
netbios access-list host name {deny | permit} string
no netbios access-list host name {deny | permit} string
netbios access-list bytes name {deny | permit} offset byte-pattern
no netbios access-list bytes name {deny | permit} offset byte-pattern
Syntax Description
Defaults
No filters are predefined.
Command Modes
Global configuration
Command History
Usage Guidelines
Keep the following points in mind when configuring IPX NetBIOS access control:
•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:
no netbios access-list {host | bytes} name
To delete a single entry from the list, use the following command:
no netbios access-list host name {permit | deny} string
Examples
The following example defines the IPX NetBIOS access list engineering:
netbios access-list host engineering permit eng-ws1 eng-ws2 eng-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
network (IPX Enhanced IGRP)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the network (IPX Enhanced IGRP) command is not supported in Cisco IOS software.
To enable Enhanced Interior Gateway Routing Protocol (EIGRP), use the network (IPX Enhanced IGRP) command in router configuration mode. To disable Enhanced IGRP, use the no form of this command.
network {network-number | all}
no network {network-number | all}
Syntax Description
network-number |
IPX network number. |
all |
Enables the routing protocol for all IPX networks configured on the router. |
Defaults
Disabled
Command Modes
Router configuration
Command History
Usage Guidelines
Use the network (IPX Enhanced IGRP) command to enable the routing protocol specified in the ipx router command on each network.
Examples
The following commands disable RIP on network 10 and enable Enhanced IGRP on networks 10 and 20:
ipx router rip
no network 10
ipx router eigrp 12
network 10
network 20
Related Commands
|
|
---|---|
ipx router |
Specifies the routing protocol to use. |
permit (IPX extended)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the permit (IPX extended) command is not supported in Cisco IOS software.
To set conditions for a named IPX extended access list, use the permit command in access-list configuration mode. To remove a permit condition from an access list, use the no form of this command.
permit protocol [source-network][[[.source-node] source-node-mask] | [.source-node source-network-mask.source-node-mask]] [source-socket] [destination-network][[[.destination-node] destination-node-mask] | [.destination-node destination-network-mask.destination-node-mask]] [destination-socket] [log] [time-range time-range-name]
no permit protocol [source-network][[[.source-node] source-node-mask] | [.source-node source-network-mask.source-node-mask]] [source-socket] [destination-network][[[.destination-node] destination-node-mask] | [.destination-node destination-network-mask.destination-nodemask]] [destination-socket] [log] [time-range time-range-name]
Syntax Description
Defaults
There is no specific condition under which a packet passes the named access list.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to specify conditions under which a packet passes the named access list.
For additional information on IPX protocol names and numbers, and IPX socket names and numbers, see the access-list (IPX extended) command.
Examples
The following example creates an extended access list named sal that denies all SPX packets and permits all others:
ipx access-list extended sal
deny spx any all any all log
permit any
The following example provides a time range to permit access:
time-range no-spx
periodic weekdays 8:00 to 18:00
!
ipx access-list extended test
permit spx any all any all time-range no spx
Related Commands
permit (IPX standard)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the permit (IPX standard) command is not supported in Cisco IOS software.
To set conditions for a named IPX access list, use the permit command in access-list configuration mode. To remove a permit condition from an access list, use the no form of this command.
permit source-network[.source-node [source-node-mask]] [destination-network[.destination-node[destination-node-mask]]]
no permit source-network[.source-node [source-node-mask]] [destination-network[.destination-node[destination-node-mask]]]
Syntax Description
Defaults
No access lists are defined.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to specify conditions under which a packet passes the named access list.
For additional information on creating IPX access lists, see the access-list (IPX standard) command.
Examples
The following example creates a standard access list named fred. It permits communication with only IPX network number 5678.
ipx access-list standard fred
permit 5678 any
deny any
Related Commands
permit (NLSP)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the permit (NLSP) command is not supported in Cisco IOS software.
To allow explicit route redistribution in a named NetWare Link-Services Protocol (NLSP) route aggregation access list, use the permit command in access-list configuration mode. To remove a permit condition, use the no form of this command.
permit network network-mask [ticks ticks] [area-count area-count]
no permit network network-mask [ticks ticks] [area-count area-count]
Syntax Description
Defaults
No access lists are defined.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to specify conditions under which networks that are permitted by the access list entry can be redistributed as explicit networks, without summarization.
For additional information on creating access lists that deny or permit area addresses that summarize routes, see the access-list (NLSP route aggregation summarization) command.
Examples
The following example allows networks 12345600 and 12345601 to be redistributed explicitly. Other routes in the range 12345600 to 123456FF are summarized into a single aggregated route. All other routes will be redistributed as explicit routes.
ipx access-list summary finance
permit 12345600
permit 12345601
deny 12345600 ffffff00
permit -1
Related Commands
permit (SAP filtering)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the permit (SAP filtering) command is not supported in Cisco IOS software.
To set conditions for a named IPX Service Advertising Protocol (SAP) filtering access list, use the permit command in access-list configuration mode. To remove a permit condition from an access list, use the no form of this command.
permit network[.node] [network-mask.node-mask] [service-type [server-name]]
no permit network[.node] [network-mask.node-mask] [service-type [server-name]]
Syntax Description
Defaults
No access lists are defined.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command following the ipx access-list command to specify conditions under which a packet passes the named access list.
For additional information on IPX SAP service types, see the access-list (SAP filtering) command.
Examples
The following example creates a SAP access list named MyServer that allows only MyServer to be sent in SAP advertisements:
ipx access-list sap MyServer
permit 1234 4 MyServer
Related Commands
prc-interval (IPX)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the prc-interval (IPX) command is not supported in Cisco IOS software.
To control the hold-down period between partial route calculations, use the prc-interval command in router configuration mode. To restore the default interval, use the no form of this command.
prc-interval seconds
no prc-interval seconds
Syntax Description
seconds |
Minimum amount of time between partial route calculations, in seconds. It can be a number in the range 1 to 120. The default is 5 seconds. |
Defaults
5 seconds
Command Modes
Router configuration
Command History
Usage Guidelines
The prc-interval command controls how often Cisco IOS software can performs a partial route (PRC) calculation. The PRC calculation is processor-intensive. Therefore, it may be useful to limit how often this is done, especially on slower router models. Increasing the PRC interval reduces the processor load of the router, but potentially slows down the rate of convergence.
This command is analogous to the spf-interval command, which controls the hold-down period between shortest path first calculations.
Examples
The following example sets the PRC calculation interval to 20 seconds:
prc-interval 20
Related Commands
|
|
---|---|
ipx router |
Specifies the routing protocol to use. |
spf-interval |
Controls how often Cisco IOS software performs the SPF calculation. |
redistribute (IPX)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the redistribute (IPX) command is not supported in Cisco IOS software.
To redistribute from one routing domain into another, and vice versa, use one of the following redistribute commands in router configuration mode. To disable this feature, use the no form of these commands.
For Enhanced Interior Gateway Routing Protocol (EIGRP) or Routing Information Protocol (RIP) environments, use the following command to redistribute from one routing domain into another, and vice versa:
redistribute {connected | eigrp autonomous-system-number | floating-static | rip | static}
no redistribute {connected | eigrp autonomous-system-number | floating-static | rip | static}
Syntax Description
Defaults
Redistribution is enabled between all routing domains except between separate Enhanced IGRP processes.
Redistribution of floating static routes is disabled.
Command Modes
Router configuration
Command History
Usage Guidelines
Redistribution provides for routing information generated by one protocol to be advertised in another.
The only connected routes affected by this redistribute command are the routes not specified by the network command.
If you have enabled floating static routes by specifying the floating keyword in the ipx route global configuration command and you redistribute floating static routes into a dynamic IPX routing protocol, any nonhierarchical topology causes the floating static destination to be redistributed immediately via a dynamic protocol back to the originating router, causing a routing loop. This occurs because dynamic protocol information overrides floating static routes. For this reason, automatic redistribution of floating static routes is off by default. If you redistribute floating static routes, you should specify filters to eliminate routing loops.
•Enhanced IGRP version 1.1 environments
•RIP version 1.1 environments
Examples
The following example does not redistributes RIP routing information:
ipx router eigrp 222
no redistribute rip
The following example redistributes Enhanced IGRP routes from autonomous system 100 into Enhanced IGRP autonomous system 300:
ipx router eigrp 300
redistribute eigrp 100
Related Commands
|
|
---|---|
ipx access-list |
Defines an IPX access list by name. |
ipx router |
Specifies the routing protocol to use. |
route-aggregation (NLSP)
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the route-aggregation (NLSP) command is not supported in Cisco IOS software.
To enable the generation of aggregated routes in an NetWare Link-Services Protocol (NLSP) area, use the route-aggregation command in router configuration mode. To disable generation, use the no form of this command.
route-aggregation
no route-aggregation
Syntax Description
This command has no arguments or keywords.
Defaults
Route summarization is disabled by default.
Command Modes
Router configuration
Command History
Usage Guidelines
When route summarization is disabled, all routes redistributed into an NLSP area will be explicit routes.
When route summarization is enabled, the router uses the access list associated with the redistribute command (if one exists) for the routing process associated with each route as a template for route summarization. Explicit routes that match a range denied by the access list trigger generation of an aggregated route instead. Routes permitted by the access list are redistributed as explicit routes.
If no access list exists, the router instead uses the area address (if one exists) of the routing process associated with each route as a template for route summarization. Explicit routes that match the area address trigger generation of an aggregated route instead.
Note Because an Enhanced Interior Gateway Routing Protocol (EIGRP) or Routing Information Protocol (RIP) routing process cannot have an area address, it is not possible to generate aggregated routes without the use of an access list.
Examples
The following example enables route summarization between two NLSP areas. Route summarization is based on the area addresses configured for each area.
ipx routing
ipx internal-network 123
!
interface ethernet 1
ipx nlsp area1 enable
!
interface ethernet 2
ipx nlsp area2 enable
!
ipx router nlsp area1
area-address 1000 fffff000
route-aggregation
!
ipx router nlsp area2
area-address 2000 fffff000
route-aggregation
Related Commands
|
|
---|---|
ipx router |
Specifies the routing protocol to use. |
redistribute (IPX) |
Redistributes from one routing domain into another. |
show ipx access-list
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx access-list command is not supported in Cisco IOS software.
To display the contents of all current IPX access lists, use the show ipx access-list command in EXEC mode.
show ipx access-list [access-list-number | name]
Syntax Description
Defaults
Displays all standard, extended, and Service Advertising Protocol (SAP) IPX access lists.
Command Modes
EXEC
Command History
Usage Guidelines
The show ipx access-list command provides output identical to the show access-lists command, except that it is IPX specific and allows you to specify a particular access list.
Examples
The following is sample output from the show ipx access-list command when all access lists are requested:
Router# show ipx access-list
IPX extended access list 900
deny any 1
IPX sap access list London
deny FFFFFFFF 107
deny FFFFFFFF 301C
permit FFFFFFFF 0
The following is sample output from the show ipx access-list command when the name of a specific access list is requested:
Router# show ipx access-list London
IPX sap access list London
deny FFFFFFFF 107
deny FFFFFFFF 301C
permit FFFFFFFF 0
show ipx accounting
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx accounting command is not supported in Cisco IOS software.
To display the active or checkpoint accounting database, use the show ipx accounting command in EXEC mode.
show ipx accounting [checkpoint]
Syntax Description
checkpoint |
(Optional) Displays entries in the checkpoint database. |
Command Modes
EXEC
Command History
Examples
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 13 describes the fields shown in the display.
Related Commands
show ipx cache
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx cache command is not supported in Cisco IOS software.
To display the contents of the IPX fast-switching cache, use the show ipx cache command in EXEC mode.
show ipx cache
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx cache command:
Router# show ipx cache
Novell routing cache version is 9
Destination Interface MAC Header
*1006A Ethernet 0 00000C0062E600000C003EB0064
*14BB Ethernet 1 00000C003E2A00000C003EB0064
Table 14 describes the fields shown in the display.
Related Commands
|
|
---|---|
clear ipx cache |
Deletes entries from the IPX fast-switching cache. |
ipx route-cache |
Enables IPX fast switching. |
show ipx eigrp interfaces
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx eigrp interfaces command is not supported in Cisco IOS software.
To display information about interfaces configured for Enhanced Interior Gateway Routing Protocol (EIGRP), use the show ipx eigrp interfaces command in EXEC mode.
show ipx eigrp interfaces [type number] [as-number]
Syntax Description
type |
(Optional) Interface type. |
number |
(Optional) Interface number. |
as-number |
(Optional) Autonomous system number. |
Command Modes
EXEC
Command History
Usage Guidelines
Use the show ipx eigrp interfaces command to determine on which interfaces Enhanced IGRP is active and to find out information about Enhanced IGRP relating to those interfaces.
If an interface is specified, only that interface is displayed. Otherwise, all interfaces on which Enhanced IGRP is running are displayed.
If an autonomous system is specified, only the routing process for the specified autonomous system is displayed. Otherwise, all Enhanced IGRP processes are displayed.
Examples
The following is sample output from the show ipx eigrp interfaces command:
Router> show ipx eigrp interfaces
IPX EIGRP interfaces for process 109
Xmit Queue Mean Pacing Time Multicast Pending
Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes
Di0 0 0/0 0 11/434 0 0
Et0 1 0/0 337 0/10 0 0
SE0:1.16 1 0/0 10 1/63 103 0
Tu0 1 0/0 330 0/16 0 0
Table 15 describes the fields shown in the display.
Related Commands
|
|
---|---|
show ipx eigrp neighbors |
Displays the neighbors discovered by Enhanced IGRP. |
show ipx eigrp neighbors
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx eigrp neighbors command is not supported in Cisco IOS software.
To display the neighbors discovered by Enhanced Interior Gateway Routing Protocol (EIGRP), use the show ipx eigrp neighbors command in user EXEC or privileged EXEC mode.
show ipx eigrp neighbors [servers] [detail | interface interface-number] [regexp name]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Usage Guidelines
Use show ipx eigrp neighbors command to display the neighbors discovered by EIGRP.
Examples
The following are sample outputs of show ipx eigrp neighbors commands:
Router# show ipx eigrp neighbors
EIGRP-IPX Neighbors for AS(1)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
1 10.aabb.cc00.0e00 Et0/0 12 00:01:17 166 996 0 4
0 10.aabb.cc00.0a00 Et0/0 12 00:01:19 173 1038 0 9
Router# show ipx eigrp neighbors detail
EIGRP-IPX Neighbors for AS(1)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
1 10.aabb.cc00.0e00 Et0/0 14 00:01:20 166 996 0 4
Version 5.0/3.0, Retrans: 0, Retries: 0, Prefixes: 1
Topology-ids from peer - 0
0 10.aabb.cc00.0a00 Et0/0 14 00:01:22 173 1038 0 9
Version 5.0/3.0, Retrans: 0, Retries: 0, Prefixes: 1
Topology-ids from peer - 0
Table 16 describes the fields shown in the display.
Related Commands
|
|
---|---|
ipx sap-incremental |
Sends SAP updates only when a change occurs in the SAP table. |
show ipx eigrp topology
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx eigrp topology command is not supported in Cisco IOS software.
To display the Enhanced Interior Gateway Routing Protocol (EIGRP) topology table, use the show ipx eigrp topology command in user EXEC mode or privileged EXEC mode.
show ipx eigrp topology [network-number [ipx-network-mask] | active | all-links | detail-links | pending | summary | zero-successors | base [network-number [ipx-network-mask] | active | all-links | detail-links | pending | summary | zero-successors | accounting | events [[errmsg | sia] [start-event-number end-event-number] | type]]]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Examples
The following is sample output of 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 17 describes the fields shown in the display.
The following are sample outputs from the show ipx eigrp topology command when an IPX network number is specified:
Internal EIGRP IPX Network: Example
Router# show ipx eigrp topology BB
EIGRP-IPX Topology Entry for AS(2)/ID(0.aabb.cc01.f600) for BB
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 409600
Descriptor Blocks:
AA.aabb.cc01.f500 (Ethernet0/0), from AA.aabb.cc01.f500, Send flag is 0x0
Composite metric is (409600/128256), route is Internal
Vector metric:
Minimum bandwidth is 10000 Kbit
Total delay is 6000 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
External EIGRP IPX Network: Example
Router# show ipx eigrp topology CC
EIGRP-IPX Topology Entry for AS(2)/ID(0.aabb.cc01.f600) for CC
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 409600
Descriptor Blocks:
AA.aabb.cc01.f500 (Ethernet0/0), from AA.aabb.cc01.f500, Send flag is 0x0
Composite metric is (409600/128256), route is External
Vector metric:
Minimum bandwidth is 10000 Kbit
Total delay is 6000 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
External data:
Originating router is aabb.cc01.f500
AS number of route is 0
External protocol is RIP, external metric is 1
Administrator tag is 0 (0x00000000)
Table 18 describes the fields shown in the display.
|
|
---|---|
BB, CC |
IPX network number of the destination. |
State is ... |
State of this entry. It can be either Passive or Active. Passive means that no Enhanced IGRP computations are being performed for this destination, and Active means that they are being performed. |
Query origin flag |
Exact Enhanced IGRP state that this destination is in. It can be the number 0, 1, 2, or 3. This information appears only when the destination is Active. |
Successor(s) |
Number of successors. This number corresponds to the number of next hops in the IPX routing table. |
Ethernet0 |
Interface from which this information was learned. |
from |
Peer from whom the information was learned. For connected and redistributed routers, this is 0.0000.0000.0000. For information learned via Enhanced IGRP, this is the peer's address. Currently, for information learned via Enhanced IGRP, the peer's IPX address always matches the address in the "Next hop is" field. |
Composite metric is |
Enhanced IGRP composite metric. The first number is this device's metric to the destination, and the second is the peer's metric to the destination. |
Send flag |
Numeric representation of the "flags" field described in Table 16. It is 0 when nothing is being sent, 1 when an Update is being sent, 3 when a Query is being sent, and 4 when a Reply is being sent. Currently, 2 is not used. |
Route is ... |
Type of router. It can be either internal or external. Internal routes are those that originated in an Enhanced IGRP autonomous system, and external are routes that did not. Routes learned through RIP are always external. |
This is an ignored route |
Indicates that this path is being ignored because of filtering. |
Vector metric: |
This section describes the components of the Enhanced IGRP metric. |
Minimum bandwidth |
Minimum bandwidth of the network used to reach the next hop. |
Total delay |
Delay time to reach the next hop. |
Reliability |
Reliability value used to reach the next hop. |
Load |
Load value used to reach the next hop. |
Minimum MTU |
Minimum MTU size of the network used to reach the next hop. |
Hop count |
Number of hops to the next hop. |
External data: |
This section describes the original protocol from which this route was redistributed. It appears only for external routes. |
Originating router |
Network address of the router that first distributed this route into Enhanced IGRP. |
External protocol..metric..delay |
External protocol from which this route was learned. The metric will match the external hop count displayed by the show ipx route command for this destination. The delay is the external delay. |
Administrator tag |
Not currently used. |
Flag |
Not currently used. |
show ipx eigrp traffic
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx eigrp traffic command is not supported in Cisco IOS software.
To display the number of Enhanced Interior Gateway Routing Protocol (EIGRP) packets that are sent and received, use the show ipx eigrp traffic command in privileged EXEC mode.
show ipx eigrp autonomous-system-number traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is the sample output from the show ipx eigrp traffic command:
Router# show ipx eigrp 2 traffic
EIGRP-IPX Traffic Statistics for AS(2)
Hellos sent/received: 7454/2507
Updates sent/received: 20/20
Queries sent/received: 1/17
Replies sent/received: 9/1
Acks sent/received: 22/27
SIA-Queries sent/received: 0/0
SIA-Replies sent/received: 0/0
Hello Process ID: 199
PDM Process ID: 171
Socket Queue: 0 (current)
Input Queue: 0/2000/2/0 (current/max/highest/drops)
Table 19 describes the significant fields shown in the display.
show ipx interface
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx interface command is not supported in Cisco IOS software.
To display the status of the IPX interfaces configured in Cisco IOS software and the parameters configured on each interface, use the show ipx interface command in EXEC mode.
show ipx interface [type number]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx interface command:
Router# show ipx interface serial 2/0
Serial2/0 is up, line protocol is up
IPX address is 123.00e0.1efc.0b01 [up]
Delay of this IPX network, in ticks is 6 throughput 0 link delay 0
IPXWAN processing not enabled on this interface.
IPX SAP update interval is 60 seconds
IPX type 20 propagation packet forwarding is disabled
Incoming access list is 900
Outgoing access list is not set
IPX helper access list is not set
SAP GGS output filter list is 1000
SAP GNS processing enabled, delay 0 ms, output filter 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
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
Updates each 60 seconds aging multiples RIP:3 SAP:3
SAP interpacket delay is 55 ms, maximum size is 480 bytes
RIP interpacket delay is 55 ms, maximum size is 432 bytes
RIP response delay is not set
Watchdog spoofing is currently enabled
On duration 1 hour(s), 00:24:50 remaining
Off duration 18 minute(s), 00:00:00 remaining
SPX spoofing is disabled, idle time 60
IPX accounting is disabled
IPX fast switching is configured (enabled)
RIP packets received 0, RIP packets sent 906, 0 Throttled
RIP specific requests received 0, RIP specific replies sent 0
RIP general requests received 0, 0 ignored, RIP general replies sent 0
SAP packets received 0, SAP packets sent 25, 0 Throttled
SAP GNS packets received 0,k SAP GNS replies sent 0
SAP GGS packets received 0, 0 ignored, SAP GGS replies sent 0
Table 20 describes the fields shown in the display.
Related Commands
show ipx nasi connections
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx nasi connections command is not supported in Cisco IOS software.
To display the status of NetWare Asynchronous Services Interface (NASI) connections, use the show ipx nasi connections command in EXEC mode.
show ipx nasi connections
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
Use the show ipx nasi connections command to view the addresses of remote NASI clients local connection addresses and status bits. If the connection is associated with a tty port then the Connected to line field appears in the show ipx nasi connections output.
Examples
The following is sample output from the show ipx nasi connections command:
Router# show ipx nasi connections
NASI Remote: A001500::0020.afe5.3ec5:626C Local: ACBB::0000.0000.0001:2010
flags 0
NASI Remote: A001500::0020.afe5.3ec5:6E6C Local: ACBB::0000.0000.0001:20D0
flags 0
Connected to line 2 incount 0 outcount 0 OVF 0
The following sample display shows an incoming NASI connection on tty line 2:
Router# show users
Line User Host(s) Idle Location
* 0 con 0 idle 1
2 tty 2 chris incoming 1 A001500.0020.afe5.3ec5
Table 21 describes the significant fields shown in the display.
Related Commands
|
|
---|---|
ipx nasi-server enable |
Enables NASI clients to connect to asynchronous devices. |
show ipx spx-protocol |
Displays the status of the SPX protocol stack and related counters. |
show ipx nhrp
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx nhrp command is not supported in Cisco IOS software.
To display the Next Hop Resolution Protocol (NHRP) cache, use the show ipx nhrp command in EXEC mode.
show ipx nhrp [dynamic | static] [type number]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx nhrp command:
Router# show ipx nhrp
1.0000.0c35.de01, Serial1 created 0:00:43 expire 1:59:16
Type: dynamic Flags: authoritative
NBMA address: c141.0001.0001
1.0000.0c35.e605, Serial1 created 0:10:03 expire 1:49:56
Type: static Flags: authoritative
NBMA address: c141.0001.0002
Table 22 describes the fields shown in the display.
Related Commands
|
|
---|---|
ipx nhrp map |
Statically configures the IPX-to-NBMA address mapping of IPX destinations connected to an NBMA network. |
show ipx nhrp traffic
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx nhrp traffic command is not supported in Cisco IOS software.
To display Next Hop Resolution Protocol (NHRP) traffic statistics, use the show ipx nhrp traffic command in EXEC mode.
show ipx nhrp traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx nhrp traffic command:
Router# show ipx nhrp traffic
Tunnel0
request packets sent: 2
request packets received: 4
reply packets sent: 4
reply packets received: 2
register packets sent: 0
register packets received: 0
error packets sent: 0
error packets received: 0
Table 23 describes the fields shown in the display.
show ipx nlsp database
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx nlsp database command is not supported in Cisco IOS software.
To display the entries in the link-state packet (LSP) database, use the show ipx nlsp database command in EXEC mode.
show ipx nlsp [tag] database [lspid] [detail]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
When you specify an NLSP tag, the router displays the link-state packet database entries for that NLSP process. An NLSP process is a router's databases working together to manage route information about an area. NLSP version 1.0 routers are always in the same area. Each router has its own adjacencies, link-state, and forwarding databases. These databases operate collectively as a single process to discover, select, and maintain route information about the area. NLSP version 1.1 routers that exist within a single area also use a single process.
NLSP version 1.1 routers that interconnect multiple areas use multiple processes to discover, select, and maintain route information about the areas they interconnect. These routers manage an adjacencies, link-state, and area address database for each area to which they attach. Collectively, these databases are still referred to as a process. The forwarding database is shared among processes within a router. The sharing of entries in the forwarding database is automatic when all processes interconnect NLSP version 1.1 areas.
Configure multiple NLSP processes when a router interconnects multiple NLSP areas.
Note 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.
If you omit all options, a summary display is shown.
Examples
The following is sample output from the show ipx nlsp database command:
Router# show ipx nlsp database detail
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
0000.0C00.3097.00-00* 0x00000042 0xC512 699 0/0/0
0000.0C00.3097.06-00* 0x00000027 0x0C27 698 0/0/0
0000.0C02.7471.00-00 0x0000003A 0x4A0F 702 0/0/0
0000.0C02.7471.08-00 0x00000027 0x0AF0 702 0/0/0
0000.0C02.7471.0A-00 0x00000027 0xC589 702 0/0/0
0000.0C02.747D.00-00 0x0000002E 0xC489 715 0/0/0
0000.0C02.747D.06-00 0x00000027 0xEEFE 716 0/0/0
0000.0C02.747D.0A-00 0x00000027 0xFE38 716 0/0/0
0000.0C02.74AB.00-00 0x00000035 0xE4AF 1059 0/0/0
0000.0C02.74AB.0A-00 0x00000027 0x34A4 705 0/0/0
0000.0C06.FBEE.00-00 0x00000038 0x3838 1056 0/0/0
0000.0C06.FBEE.0D-00 0x0000002C 0xD248 1056 0/0/0
0000.0C06.FBEE.0E-00 0x0000002D 0x7DD2 1056 0/0/0
0000.0C06.FBEE.17-00 0x00000029 0x32FB 1056 0/0/0
0000.0C00.AECC.00-00* 0x000000B6 0x62A8 7497 0/0/0
IPX Area Address: 00000000 00000000
IPX Mgmt Info 87.0000.0000.0001 Ver 1 Name oscar
Metric: 45 Lnk 0000.0C00.AECC.06 MTU 1500 Dly 8000 Thru 64K PPP
Metric: 20 Lnk 0000.0C00.AECC.02 MTU 1500 Dly 1000 Thru 10000K 802.3 Raw
Metric: 20 Lnk 0000.0C01.EF90.0C MTU 1500 Dly 1000 Thru 10000K 802.3 Raw
0000.0C00.AECC.02-00* 0x00000002 0xDA74 3118 0/0/0
IPX Mgmt Info E0.0000.0c00.aecc Ver 1 Name Ethernet0
Metric: 0 Lnk 0000.0C00.AECC.00 MTU 0 Dly 0 Thru 0K 802.3 Raw
0000.0C00.AECC.06-00* 0x00000002 0x5DB9 7494 0/0/0
IPX Mgmt Info 0.0000.0000.0000 Ver 1 Name Serial0
Metric: 0 Lnk 0000.0C00.AECC.00 MTU 0 Dly 0 Thru 0K PPP
Metric: 1 IPX Ext D001 Ticks 0
Metric: 1 IPX SVC Second-floor-printer D001.0000.0000.0001 Sock 1 Type 4
Table 24 describes the fields shown in the display.
show ipx nlsp neighbors
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx nlsp neighbors command is not supported in Cisco IOS software.
To display NetWare Link Services Protocol (NLSP) neighbors and their states, use the show ipx nlsp neighbors command in EXEC mode.
show ipx nlsp [tag] neighbors [interface] [detail]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
When you specify an NLSP tag value, the router displays the NLSP neighbors for that NLSP process. An NLSP process is a router's databases working together to manage route information about an area. NLSP version 1.0 routers must be in a single area. Each router has its own adjacencies, link-state, and forwarding databases. These databases operate collectively as a single process to discover, select, and maintain route information about the area. NLSP version 1.1 routers that exist within a single area also use a single process.
NLSP version 1.1 routers that interconnect multiple areas use multiple processes to discover, select, and maintain route information about the areas they interconnect. These routers manage adjacencies, link-state, and area address databases for each area to which they attach. Collectively, these databases are still referred to as a process. The forwarding database is shared among processes within a router. The sharing of entries in the forwarding database is automatic when all processes interconnect NLSP version 1.1 areas.
You must configure multiple NLSP processes when a router interconnects multiple NLSP areas.
Note 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.
If you omit the keyword detail, a summary display is shown.
Examples
The following command output from the show ipx nlsp neighbors command shows a summary display of three adjacencies on two circuits:
Router# show ipx nlsp neighbors
System Id Interface State Holdtime Priority Cir Adj Circuit Id
dtp-37 Et1.2 Up 21 64 mc mc dtp-37.03
dtp-37 Et1.1 Up 58 44 bc mc dtp-17.02
dtp-17 ET1.1 Up 27 64 bc bc dtp-17.02
This display indicates the following information about the first circuit (Circuit Id = dtp-37.03):
•Multicast addressing is in use (Cir = mc).
•The neighbor supports multicast addressing (Adj = mc).
This display indicates the following information about the second circuit (Circuit Id = dtp-17.02):
•The broadcast address is in use (Cir = bc).
•The first neighbor (System Id = dtp-37) supports multicast addressing (Adj = mc).
•The second neighbor (System Id = dtp-17) does not support multicast addressing (Adj = bc). This adjacency explains why the broadcast address is in use on the second circuit.
The following is sample output from the show ipx nlsp neighbors detail command:
Router# show ipx nlsp neighbors detail
System Id Interface State Holdtime Priority Cir Adj Circuit Id
0000.0C01.EF90 Ethernet1 Up 25 64 mc mc 0000.0C01.EF90.0C
IPX Address: E1.0000.0c01.ef91
IPX Areas: 00000000/00000000
Uptime: 2:59:11
Table 25 describes the fields shown in the display.
show ipx nlsp spf-log
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx nlsp spf-log command is not supported in Cisco IOS software.
To display a history of the shortest path first (SPF) calculations for NetWare Link Services Protocol (NLSP), use the show ipx nlsp spf-log command in EXEC mode.
show ipx nlsp [tag] spf-log
Syntax Description
tag |
(Optional) Names the NLSP process. The tag can be any combination of printable characters. |
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx nlsp spf-log command:
Router#
show ipx nlsp spf-log
Level 1 SPF log
When Duration Nodes Count Triggers
0:30:59 1028 84 1 TLVCONTENT
0:27:09 1016 84 1 TLVCONTENT
0:26:30 1136 84 1 TLVCONTENT
0:23:11 1244 84 1 TLVCONTENT
0:22:39 924 84 2 TLVCONTENT
0:22:08 1036 84 1 TLVCONTENT
0:20:02 1096 84 1 TLVCONTENT
0:19:31 1140 84 1 TLVCONTENT
0:17:25 964 84 2 PERIODIC TLVCONTENT
0:16:54 996 84 1 TLVCONTENT
0:16:23 984 84 1 TLVCONTENT
0:15:52 1052 84 1 TLVCONTENT
0:14:34 1112 84 1 TLVCONTENT
0:13:37 992 84 1 TLVCONTENT
0:13:06 1036 84 1 TLVCONTENT
0:12:35 1008 84 1 TLVCONTENT
0:02:52 1032 84 1 TLVCONTENT
0:02:16 1032 84 1 PERIODIC
0:01:44 1000 84 3 TLVCONTENT
Table 26 describes the fields shown in the display.
show ipx route
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, 15.2(2)T, and 15.1(1)SY, the show ipx route command is not supported in Cisco IOS software.
To display the contents of the IPX routing table, use the show ipx route command in EXEC mode.
show ipx route [network] [default] [detailed]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx route command:
Router# show ipx route
Codes: C - Connected primary network, c - Connected secondary network
S - Static, F - Floating static, L - Local (internal), W - IPXWAN
R - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregate
s - seconds, u - uses
8 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.
No default route known.
L D40 is the internal network
C 100 (NOVELL-ETHER), Et1
C 7000 (TUNNEL), Tu1
S 200 via 7000.0000.0c05.6023, Tu1
R 300 [02/01] via 100.0260.8c8d.e748, 19s, Et1
S 2008 via 7000.0000.0c05.6023, Tu1
R CC0001 [02/01] via 100.0260.8c8d.e748, 19s, Et1
Table 27 describes the fields shown in the display.
When Cisco IOS software generates an aggregated route, the show ipx route command displays a line item similar to the following:
NA 1000 FFFFF000 [**][**/06] via 0.0000.0000.0000, 163s, Nu0
In the following example, the router that sends the aggregated route also generates the aggregated route line item in its table. But the entry in the table points to the null interface (Nu0), indicating that if this aggregated route is the most-specific route when a packet is being forwarded, the router drops the packet instead.
Router# show ipx route
Codes: C - Connected primary network, c - Connected secondary network
S - Static, F - Floating static, L - Local (internal), W - IPXWAN
R - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregate
s - seconds, u - uses
13 Total IPX routes. Up to 4 parallel paths and 16 hops allowed.
No default route known.
NA 1000 FFFFF000 [**][**/06] via 0.0000.0000.0000, 163s, Nu0
L 2008 is the internal network
C 1 (NOVELL-ETHER), Et0
C 89 (SAP), To0
C 91 (SAP), To1
C 100 (NOVELL-ETHER), Et1
N 2 [19][01/01] via 91.0000.30a0.51cd, 317s, To1
N 3 [19][01/01] via 91.0000.30a0.51cd, 327s, To1
N 20 [20][01/01] via 1.0000.0c05.8b24, 2024s, Et0
N 101 [19][01/01] via 91.0000.30a0.51cd, 327s, To1
NX 1000 [20][02/02][01/01] via 1.0000.0c05.8b24, 2024s, Et0
N 2010 [20][02/01] via 1.0000.0c05.8b24, 2025s, Et0
N 2011 [19][02/01] via 91.0000.30a0.51cd, 328s, To1
The following is sample output from the show ipx route detailed command:
Router# show ipx route detailed
Codes: C - Connected primary network, c - Connected secondary network
S - Static, F - Floating static, L - Local (internal), W - IPXWAN
R - RIP, E - EIGRP, N - NLSP, X - External, s - seconds, u - uses
9 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.
No default route known.
L D35 is the internal network
C E001 (SAP), Et0
C D35E2 (NOVELL-ETHER), Et2
R D34 [02/01]
-- via E001.0000.0c02.8cf9, 43s, 1u, Et0
N D36 [20][02/01]
-- via D35E2.0000.0c02.8cfc, 704s, 1u, Et2
10000000:1000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc
NX D40 [20][03/02][02/01]
-- via D35E2.0000.0c02.8cfc, 704s, 1u, Et2
10000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc
R D34E1 [01/01]
-- via E001.0000.0c02.8cf9, 43s, 1u, Et0
NX D40E1 [20][02/02][01/01]
-- via D35E2.0000.0c02.8cfc, 704s, 3u, Et2
10000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc
N D36E02 [20][01/01]
-- via D35E2.0000.0c02.8cfc, 705s, 2u, Et2
10000000:2000:1500:0000.0c02.8cfb:6:0000.0c02.8cfc
Table 28 describes the additional fields shown in the display.
Related Commands
show ipx servers
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx servers command is not supported in Cisco IOS software.
To list the IPX servers discovered through Service Advertising Protocol (SAP) advertisements, use the show ipx servers command in EXEC mode.
show ipx servers [detailed] [network network-number] [type service-type-number] [unsorted | [sorted [name | network | type]]] [regexp name]
Syntax Description
Defaults
IPX servers are displayed numerically by SAP service type.
Command Modes
EXEC
Command History
Examples
The following example uses a regular expression to display SAP table entries corresponding to a particular group of servers in the accounting department of a company:
Router# show ipx servers regexp ACCT\_SERV.+
Codes: S - Static, P - Periodic, E - EIGRP, H - Holddown, + = detail
9 Total IPX Servers
Table ordering is based on routing and server info
Type Name Net Address Port Route Hops Itf
S 108 ACCT_SERV_1 7001.0000.0000.0001:0001 1/01 2 Et0
S 108 ACCT_SERV_2 7001.0000.0000.0001:0001 1/01 2 Et0
S 108 ACCT_SERV_3 7001.0000.0000.0001:0001 1/01 2 Et0
For more information on regular expressions, refer to the "Regular Expressions" appendix in Cisco IOS Dial Technologies Command Reference.
Related Commands
|
|
---|---|
ipx sap |
Specifies static SAP entries. |
show ipx spx-spoof
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx spx-spoof command is not supported in Cisco IOS software.
To display the table of Sequenced Packet Exchange (SPX) connections through interfaces for which SPX spoofing is enabled, use the show ipx spx-spoof command in EXEC mode.
show ipx spx-spoof
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx spx-spoof command:
Router# show ipx spx-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 29 describes the fields shown in the display.
Related Commands
show ipx traffic
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show ipx traffic command is not supported in Cisco IOS software.
To display information about the number and type of IPX packets sent and received, use the show ipx traffic command in EXEC mode.
show ipx [nlsp] traffic [since {bootup | show}]
Syntax Description
Defaults
Display traffic statistics since bootup or since the last clear command was entered.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ipx traffic command:
Router# show ipx traffic
System Traffic for 0.0000.0000.0001 System-Name: Router
Time since last clear: never
Rcvd: 0 total, 0 format errors, 0 checksum errors, 0 bad hop count
0 packets pitched, 0 local destination, 0 multicast
Bcast: 0 received, 0 sent
Sent: 0 generated, 0 forwarded
0 encapsulation failed, 0 no route
SAP: 0 Total SAP requests, 0 Total SAP replies, 1 servers
0 SAP General Requests, 2 sent, 0 ignored, 0 replies
0 SAP Get Nearest Server requests, 0 replies
0 SAP Nearest Name requests, 0 replies
0 SAP General Name requests, 0 replies
0 SAP advertisements received, 324 sent, 0 Throttled
0 SAP flash updates sent, 0 SAP format errors
RIP: 0 RIP requests, 0 ignored, 0 RIP replies, 3 routes
0 RIP advertisements received, 684 sent, 0 Throttled
0 RIP flash updates sent, 0 atlr sent
2 RIP general requests sent
0 RIP format errors
Echo: Rcvd 0 requests, 0 replies
Sent 0 requests, 0 replies
0 unknown: 0 no socket, 0 filtered, 0 no helper
0 SAPs throttled, freed NDB len 0
Watchdog:
0 packets received, 0 replies spoofed
Queue lengths:
IPX input: 0, SAP 0, RIP 0, GNS 0
SAP throttling length: 0/(no limit), 0 nets pending lost route reply
Delayed process creation: 0
EIGRP: Total received 0, sent 0
Updates received 0, sent 0
Queries received 0, sent 0
Replies received 0, sent 0
SAPs received 0, sent 0
NLSP: Time since last clear: never
NLSP: Level-1 Hellos (sent/rcvd): 0/0
PTP Hellos (sent/rcvd): 0/0
Level-1 LSPs sourced (new/refresh): 1/0
Level-1 LSPs flooded (sent/rcvd): 0/0
LSP Retransmissions: 0
Level-1 CSNPs (sent/rcvd): 0/0
Level-1 PSNPs (sent/rcvd): 0/0
Level-1 DR Elections: 0
Level-1 SPF Calculations: 1
Level-1 Partial Route Calculations: 0
LSP checksum errors received: 0
Trace: Rcvd 0 requests, 0 replies
Sent 0 requests, 0 replies
Table 30 describes the fields shown in the display.
Related Commands
|
|
---|---|
clear ipx traffic |
Clears IPX protocol and NLSP traffic counters. |
show sse summary
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the show sse summary command is not supported in Cisco IOS software.
To display a summary of Silicon Switch Processor (SSP) statistics, use the show sse summary command in EXEC mode.
show sse summary
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show sse summary command:
Router# show sse summary
SSE utilization statistics
Program words Rewrite bytes Internal nodes Depth
Overhead 499 1 8
IP 0 0 0 0
IPX 0 0 0 0
SRB 0 0 0 0
CLNP 0 0 0 0
IP access lists 0 0 0
Total used 499 1 8
Total free 65037 262143
Total available 65536 262144
Free program memory
[499..65535]
Free rewrite memory
[1..262143]
Internals
75032 internal nodes allocated, 75024 freed
SSE manager process enabled, microcode enabled, 0 hangs
Longest cache computation 4ms, longest quantum 160ms at 0x53AC8
spf-interval
Note Effective with Cisco IOS Release 15.1(3)S, XE 3.4, and 15.2(2)T, the spf-interval command is not supported in Cisco IOS software.
To customize Intermediate System-to-Intermediate System (IS-IS) throttling of shortest path first (SPF) calculations, use the spf-interval command in router configuration mode. To restore default values, use the no form of this command.
spf-interval [level-1 | level-2] spf-max-wait [spf-initial-wait spf-second-wait]
no spf-interval
Syntax Description
Defaults
spf-max-wait: 10 seconds
spf-initial-wait: 5500 milliseconds
spf-second-wait: 5500 milliseconds
Command Modes
Router configuration
Command History
Usage Guidelines
SPF calculations are performed only when the topology changes. They are not performed when external routes change.
The spf-interval command controls how often Cisco IOS software performs the SPF calculation. The SPF calculation is processor-intensive. Therefore, it may be useful to limit how often this is done, especially when the area is large and the topology changes often. Increasing the SPF interval reduces the processor load of the router, but potentially slows down the rate of convergence.
The following description will help you determine whether to change the default values of this command:
•The spf-initial-wait argument indicates the initial wait time (in milliseconds) after a topology change before the first SPF calculation.
•The spf-second-wait argument indicates the interval (in milliseconds) between the first and second SPF calculation.
•Each subsequent wait interval is twice as long as the previous one until the wait interval reaches the spf-max-wait interval specified; the SPF calculations are throttled or slowed down after the initial and second intervals. Once the spf-max-wait interval is reached, the wait interval continues at this interval until the network calms down.
•After the network calms down and there are no triggers for 2 times the spf-max-wait interval, fast behavior is restored (the initial wait time).
SPF throttling is not a dampening mechanism; that is, SPF throttling does not prevent SPF calculations or mark any route, interface, or router as down. SPF throttling simply increases the intervals between SPF calculations.
Examples
The following example configures intervals for SPF calculations, partial route calculation (PRC), and link-state packet (LSP) generation:
router isis
spf-interval 5 10 20
prc-interval 5 10 20
lsp-gen-interval 2 50 100