-
Access and Communication Servers Command Reference
-
About This Manual
-
Access Server and Communication Server Product Overview
-
User Interface Commands
-
System Image and Configuration File Load Commands
-
Configuring Terminal Lines and Modem Support
-
System Management Commands
-
User Interface Config Commands
-
Dial on Demand Routing Commands
-
X.25 Configuration Commands
-
Frame Relay Commands
-
SMDS Commands
-
Telnet Configuration Commands
-
LAT Configuration Commands
-
TN3270 Configuration
-
AppleTalk Remote Access Commands
-
SLIP and PPP Configuration Commands
-
XRemote Configuration Commands
-
AppleTalk Routing Commands
-
IP Commands
-
IP Routing Protocols Commands
-
Novell IPX Commands
-
Protocol Translation Configuration Commands
-
Appendix A, ASCII Character Set
-
Appendix B, Modem and Chat Script Configuration
-
Appendix C, Regular Expressions
-
Appendix D, Refs and Reading
-
Appendix E, X.3 PAD Parameters
-
Table Of Contents
ipx advertise-default-route-only
ipx backup-server-query-interval
ipx default-triggered-rip-delay
ipx default-triggered-sap-delay
ipx netbios input-access-filter
ipx netbios output-access-filter
ipx pad-process-switched-packets
Novell IPX Commands
Novell Internet Packet Exchange (IPX) is derived from the Xerox Network Systems (XNS) Internet Datagram Protocol (IDP). One major difference between IPX and XNS is that they do not always use the same Ethernet encapsulation format. A second difference is that IPX uses Novell's proprietary Service Advertisement Protocol (SAP) to advertise special network services.
Our implementation of Novell's IPX protocol has been certified as providing full IPX access server functionality. Our access server connects Ethernet, Token Ring, and FDDI networks, either directly or through high-speed serial lines (56 kbps to T1 speeds), X.25, or Frame Relay. The Cisco X.25 and T1 support currently is not compatible with Novell. This means that our access servers must be used on both ends of T1 and X.25 circuits.
Note
One or more of the commands that previously appeared this chapter have been replaced by new commands. See the Router Products Command Reference publication for command information. The old commands continue to perform their normal function in the current release, but support for them will cease in future releases.
Use the commands in this chapter to configure and monitor Novell IPX networks. For IPX configuration information and examples, refer to the "Configuring Novell IPX" chapter in the Access and Communication Servers Configuration Guide.
Note
access-list (extended)
To define an extended Novell IPX access list, use the extended version of the access-list global configuration command. To remove an extended access list, use the no form of this command.
access-list access-list-number {deny | 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]no access-list access-list-number {deny | 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]Syntax Description
Default
No access lists are predefined.
Command Mode
Global configuration
Usage Guidelines
Extended IPX access lists filter on protocol type. All other parameters are optional.
If a network mask is used, all other fields are required.
Use the ipx access-group command to assign an access list to an interface. You can apply only one extended or one standard access list to an interface. The access list filters all outgoing packets on the interface.
Note
lists some IPX protocol numbers. lists some IPX socket numbers. For additional information about IPX protocol numbers and socket numbers, contact Novell.
Table 20-1 Some IPX Protocol Numbers
Table 20-2 Some IPX Socket Numbers
To delete an extended access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:
no access-list access-list-number
To delete the access list for a specific protocol, use the following command:
no access-list access-list-number {deny | permit} protocol
Examples
The following example denies access to all RIP packets (protocol number 1) from socket 453 (RIP process socket) on source network 1 that are destined for socket 453 on network 2. It permits all other traffic.
access-list 900 deny 1 453 2 453 access-list 900 permit 0 -1 0 -1 0The following example permits type 2 packets from any socket on network 10 to access any sockets on any nodes on networks 1000 through 100F. It denies all other traffic (with an implicit deny all):
access-list 910 permit 20 10.0000.0C00.0000 0000.0000.FFFF 0 1000.0000.0000.0000 F.FFFF.FFFF.FFFF 0
Note
Related Commands
A dagger (†) indicates that the command is documented in another chapter.
access-list (standard)
ipx access-group
ipx input-network-filter
ipx output-network-filter
ipx router-filter
priority-list protocol†access-list (SAP filtering)
To define an access list for filtering Service Advertisement Protocol (SAP) requests, use the SAP filtering form of the access-list global configuration command. To remove the access list, use the no form of this command.
access-list access-list-number {deny | permit} network[.node] [network.node-mask]
[service-type [server-name]]
no access-list access-list-number {deny | permit} network[.node] [network.node-mask]
[service-type [server-name]]Syntax Description
Default
No access lists are predefined.
Command Mode
Global configuration
Usage Guidelines
When configuring SAP filters for NetWare 3.11 and later servers, use the server's internal network and node number (the node number is always 0000.0000.0001) as its address in the access-list command. Do not use the network.node address of the particular interface board.
lists some sample IPX SAP types. For more information about SAP types, contact Novell. Note that in the filter (specified by the service-type argument), we define a value of 0 to filter all SAP services. If, however, you receive a SAP packet with a SAP type of 0, this indicates an unknown service.
Table 20-3 Sample IPX SAP Services
To delete a SAP access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:
no access-list access-list-number
To delete the access list for a specific network, use the following command:
no access-list access-list-number {deny | permit} network
Example
The following access list blocks all access to a file server (service type 4) on the directly attached network by resources on other Novell networks, but allows access to all other available services on the interface:
access-list 1001 deny -1 4access-list 1001 permit -1Related Commands
A dagger (†) indicates that the command is documented in another chapter.
ipx input-sap-filter
ipx output-gns-filter
ipx output-sap-filter
ipx router-sap-filter
priority-list protocol†access-list (standard)
To define a standard IPX access list, use the standard version of the access-list global configuration command. To remove a standard access list, use the no form of this command.
access-list access-list-number {deny | permit} source-network[.source-node
[source-node-mask]] [destination-network[.destination-node [destination-node-mask]]]
no access-list access-list-number {deny | permit} source-network[.source-node
[source-node-mask]] [destination-network[.destination-node [destination-node-mask]]]Syntax Description
Default
No access lists are predefined.
Command Mode
Global configuration
Usage Guidelines
Standard IPX access lists filter on the source network. All other parameters are optional.
Use the ipx access-group command to assign an access list to an interface. You can apply only one extended or one standard access list to an interface. The access list filters all outgoing packets on the interface.
To delete a standard access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:
no access-list access-list-number
To delete the access list for a specific network, use the following command:
no access-list access-list-number {deny | permit} source-network
Examples
The following example denies access to traffic from all IPX networks (-1) to destination network 2:
access-list 800 deny -1 2The following example denies access to all traffic from IPX address 1.0000.0c00.1111:
access-list 800 deny 1.0000.0c00.1111The following example denies access from all nodes on network 1 that have a source address beginning with 0000.0c:
access-list 800 deny 1.0000.0c00.0000 0000.00ff.ffffThe following example denies access from source address 1111.1111.1111 on network 1 to destination address 2222.2222.2222 on network 2:
access-list 800 deny 1.1111.1111.1111 0000.0000.0000 2.2222.2222.2222 0000.0000.0000or
access-list 800 deny 1.1111.1111.1111 2.2222.2222.2222Related Commands
A dagger (†) indicates that the command is documented in another chapter.
access-list (extended)
ipx access-group
ipx input-network-filter
ipx output-network-filter
ipx router-filter
priority-list protocol †area-address
To define a set of network numbers to be part of the current NLSP area, use the area-address router configuration command. To remove a set of network numbers from the current NLSP area, use the no form of this command.
area-address address mask
no area-address address maskSyntax Description
address
Network number prefix. This is a 32-bit hexadecimal number.
mask
Mask that defines the length of the network number prefix. This is a 32-bit hexadecimal number.
Default
No area address is defined by default.
Command Mode
Router configuration
Usage Guidelines
You must configure at least one area address before NLSP will operate.
The area-address command defines a prefix that includes all networks that are in the area.
All networks that are part of the NLSP area (that is, all networks that are configured on an interface on which NLSP is enabled) must fall under the area address prefix. This configuration is for future compatibility: when Level 2 NLSP becomes available, the only route advertised for the area will be the area address prefix (the prefix represents all networks within the area).
All routers and access server in an NLSP area must be configured with a common area address, or they will form separate areas.
The area address must have zero bits in all bit positions where the mask has zero bits. The mask must consist of only left-justified contiguous one bits.
Examples
The following example defines an area address that includes networks AAAABBC0 through AAAABBDF:
area-address AAAABBC0 FFFFFFE0The following example defines an area address that includes all networks:
area-address 0 0Related Command
ipx router nlsp
clear ipx accounting
To delete all entries in the active accounting database when IPX accounting is enabled, use the clear ipx accounting EXEC command.
clear ipx accounting [checkpoint]
Syntax Description
Command Mode
EXEC
Usage Guidelines
If you omit the checkpoint argument, all the entries in the active database are deleted. You can also delete all entries in the checkpointed database by issuing the clear ipx accounting command twice in succession.
Example
The following example clears all entries in the active database:
clear ipx accountingRelated Commands
ipx accounting
ipx accounting-list
ipx accounting-threshold
ipx accounting-transits
show ipx accountingclear ipx cache
To delete entries from the IPX fast-switching cache, use the clear ipx cache EXEC command.
clear ipx cache
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Usage Guidelines
The clear ipx cache command clears entries used for fast switching.
Example
The following example deletes all entries from the IPX fast-switching cache:
clear ipx cacheRelated Commands
clear ipx nlsp neighbors
To delete all NLSP adjacencies from the router's adjacency database, use the clear ipx nlsp neighbors EXEC command.
clear ipx nlsp neighbors
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Usage Guidelines
Deleting all entries from the adjacency database forces all routers in the area to perform the shortest path first (SPF) calculation.
Example
The following example deletes all NLSP adjacencies from the router's adjacency database:
clear ipx nlsp neighborsRelated Commands
clear ipx route
To delete routes from the IPX routing table, use the clear ipx route EXEC command.
clear ipx route {network | default | *}
Syntax Description
Command Mode
EXEC
Usage Guidelines
After you use the clear ipx route command, RIP/SAP general requests are issued on all IPX interfaces.
Example
The following example clears the entry for network 3 from the IPX routing table:
clear ipx route 3Related Command
distribute-list in
To filter networks received in updates, use the distribute-list in router configuration command. To change or cancel the filter, use the no form of this command.
distribute-list access-list-number in [interface-name]
no distribute-list access-list-number in [interface-name]Syntax Description
Default
Disabled
Command Mode
Router configuration
Example
The following example causes only two networks—network 2 and network 3—to be accepted by an IP Enhanced IGRP routing process:
access-list 800 permit 2access-list 800 permit 3access-list 800 deny -1!ipx router eigrp 100network 3distribute-list 800 inRelated Commands
A dagger (†) indicates that the command is documented in another chapter.
access-list †
distribute-list out
redistributedistribute-list out
To suppress networks from being advertised in updates, use the distribute-list out router configuration command. To cancel this function, use the no form of this command.
distribute-list access-list-number out [interface-name | routing-process]
no distribute-list access-list-number out [interface-name | routing-process]Syntax Description
Default
Disabled
Usage Guidelines
When redistributing networks, a routing process name can be specified as an optional trailing argument to the distribute-list out command. This causes the access list to be applied to only those routes derived from the specified routing process. After the process-specific access list is applied, any access list specified by a distribute-list out command without a process name argument is applied. Addresses not specified in the distribute-list out command are not advertised in outgoing routing updates.
Example
The following example causes only one network—network 3—to be advertised by an IPX Enhanced IGRP routing process:
access-list 800 permit 3access-list 800 deny -1!ipx router eigrp 100network 3distribute-list 800 outRelated Commands
A dagger (†) indicates that the command is documented in another chapter.
access-list †
distribute-list in
redistributeipx access-group
To apply a generic output filter to an interface, use ipx access-group interface configuration command. To remove the access list, use the no form of this command.
ipx access-group access-list-number
no ipx access-group access-list-numberSyntax Description
Default
No filters are predefined.
Command Mode
Interface configuration
Usage Guidelines
Generic filters control which packets are sent out an interface based on the packet's source and destination addresses, IPX protocol type, and source and destination socket numbers. You use the standard access-list and extended access-list commands to specify the filtering conditions.
You can apply only one generic filter to an interface.
Example
In the following example, access list 801 is applied to Ethernet interface 1:
interface ethernet 1ipx access-group 801Related Commands
A dagger (†) indicates that the command is documented in another chapter.
access-list (standard)
access-list (SAP filtering)
priority-list protocol †ipx accounting
To enable IPX accounting, use the ipx accounting interface configuration command. To disable IPX accounting, use the no form of this command.
ipx accounting
no ipx accountingSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
IPX accounting allows you to collect information about IPX packets and the number of bytes that are switched through the access server. You collect information based on the source and destination IPX address. Accounting tracks only IPX traffic that is passing out of the access server; it does not track traffic generated by or terminating at the access server.
IPX accounting statistics will be accurate even if IPX fast switching is enabled or if IPX access lists are being used. However, IPX accounting does not keep statistics if autonomous switching is enabled.
The access server software maintains two accounting databases: an active database and a checkpointed database.
Example
The following example enables IPX accounting on Ethernet interface 0:
interface ethernet 0ipx accountingRelated Commands
clear ipx accounting
ipx accounting-list
ipx accounting-threshold
ipx accounting-transits
show ipx accountingipx accounting-list
To filter the networks for which IPX accounting information is kept, use the ipx accounting-list global configuration command. To remove the filter, use the no form of this command.
ipx accounting-list number mask
no ipx accounting-list number maskSyntax Description
Default
No filters are predefined.
Command Mode
Global configuration
Usage Guidelines
The source and destination addresses of each IPX packet are logically ANDed with the mask and compared with the network number. If there is a match, accounting information about the IPX packet is entered into the accounting database. If there is no match, the IPX packet is considered to be a transit packet and may be counted, depending on the setting of the ipx accounting-transits global configuration command.
Example
The following example adds all networks with IPX network numbers beginning with 1 to the list of networks for which accounting information is kept:
ipx accounting-list 1 0000.0000.0000Related Commands
clear ipx accounting
ipx accounting
ipx accounting-threshold
ipx accounting-transits
show ipx accountingipx accounting-threshold
To set the maximum number of accounting database entries, use the ipx accounting-threshold global configuration command. To restore the default, use the no form of this command.
ipx accounting-threshold threshold
no ipx accounting-threshold thresholdSyntax Description
threshold
Maximum number of entries (source and destination address pairs) that the access server can accumulate
Default
512 entries
Command Mode
Global configuration
Usage Guidelines
The accounting threshold defines the maximum number of entries (source and destination address pairs) that the access server accumulates. The threshold is designed to prevent IPX accounting from consuming all available free memory. This level of memory consumption could occur in an access server that is switching traffic for many hosts. To determine whether overflows have occurred, used the show ipx accounting EXEC command.
Example
The following example sets the IPX accounting database threshold to 500 entries:
ipx accounting-threshold 500Related Commands
clear ipx accounting
ipx accounting
ipx accounting-list
ipx accounting-list
show ipx accountingipx accounting-transits
To set the maximum number of transit entries that will be stored in the IPX accounting database, use the ipx accounting-transits global configuration command. To disable this function, use the no form of this command.
ipx accounting-transits count
no ipx accounting-transitsSyntax Description
Default
0 entries
Command Mode
Global configuration
Usage Guidelines
Transit entries are those that do not match any of the filters specified by ipx accounting-list global configuration commands. If you have not defined any filters, no transit entries are possible.
To maintain accurate accounting totals, the access server software maintains two accounting databases: an active database and a checkpointed database.
Example
The following example specifies a maximum of 100 transit records to be stored in the IPX accounting database:
ipx accounting-transits 100Related Commands
clear ipx accounting
ipx accounting
ipx accounting-list
ipx accounting-threshold
show ipx accountingipx advertise-default-route-only
To advertise only the RIP default route via the specified network, use the ipx advertise-default-route-only interface configuration command. To advertise all routes out the interface, use the no form of this command.
ipx advertise-default-route-only network
no ipx advertise-default-route-only networkSyntax Description
network
Number of the network via which to advertise the RIP default route. This is the only network advertised.
Default
Disabled. All default routes are advertised.
Command Mode
Interface configuration
Usage Guidelines
If you specify the ipx advertise-default-route-only command, only the default route, if known, will be advertised out the interface. If you have a large number of routes in the routing table, for example, 1000 routes, none of them will be advertised out the interface. Nodes on the interface can still reach any of the 1000 networks because they know the default. Specifying the ipx advertise-default-route-only command results in a significant reduction in CPU processing overhead when there are many routes and many interfaces. It also reduces the load on downstream routers.
Note
Example
The following example enables the advertising of the RIP default route only:
ipx advertise-default-route-only 3c.7389.4339ipx backup-server-query-interval
To change the time between successive queries of each IPX Enhanced IGRP neighbor's backup server table, use the ipx backup-server-query-interval global configuration command. To restore the default time, use the no form of this command.
ipx backup-server-query-interval interval
no ipx backup-server-query-intervalSyntax Description
interval
Minimum time, in seconds, between successive queries of each Enhanced IGRP neighbor's backup server table. The default is 15 seconds.
Default
15 seconds
Command Mode
Global configuration
Usage Guidelines
A lower interval may use more CPU resources, but may cause lost server information to be retrieved from other servers' tables sooner.
Example
The following example changes the server query time to 5 seconds:
ipx backup-server-query-interval 5ipx default-output-rip-delay
To set the default interpacket delay for Routing Information Protocol (RIP) updates sent on all interfaces, use the ipx default-output-rip-delay global configuration command. To return to the initial default delay value, use the no form of this command.
ipx default-output-rip-delay delay
no ipx default-output-rip-delay [delay]Syntax Description
Default
With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between routing update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.
Command Mode
Global configuration
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet routing update. The ipx default-output-rip-delay command sets a default interpacket delay for all interfaces.
The system uses the delay specified by the ipx default-output-rip-delay command for periodic and triggered routing updates when no delay is set for periodic and triggered routing updates on an interface. When you set a delay for triggered routing updates, the system uses the delay specified by the ipx default-output-rip-delay command for only the periodic routing updates sent on all interfaces.
To set a delay for triggered routing updates, see the ipx triggered-rip-delay or ipx default-triggered-rip-delay commands.
Novell recommends a delay of 55 ms for compatibility with older and slower IPX machines. These machines may lose RIP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX machines.
The default delay on a NetWare 3.11 server is about 100 ms.
This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.
Example
The following example sets a default interpacket delay of 55 ms for RIP updates sent on all interfaces:
ipx default-output-rip-delay 55Related Command
ipx default-triggered-rip-delay
ipx output-rip-delay
ipx triggered-rip-delayipx default-output-sap-delay
To set a default interpacket delay for Service Advertisement Protocol (SAP) updates sent on all interfaces, use the ipx default-output-sap-delay global configuration command. To return to the initial default delay value, use the no form of this command.
ipx default-output-sap-delay delay
no ipx default-output-sap-delay [delay]Syntax Description
Default
With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.
Command Mode
Global configuration
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet SAP update. The ipx default-output-sap-delay command sets a default interpacket delay for all interfaces.
The system uses the delay specified by the ipx default-output-sap-delay command for periodic and triggered SAP updates when no delay is set for periodic and triggered updates on an interface. When you set a delay for triggered updates, the system uses the delay specified by the ipx default-output-sap-delay command only for the periodic SAP updates sent on all interfaces.
To set a delay for triggered updates, see the ipx triggered-sap-delay or ipx default-triggered-sap-delay commands.
Novell recommends a delay of 55 ms for compatibility with older and slower IPX servers. These servers may lose SAP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these servers.
The default delay on a NetWare 3.11 server is about 100 ms.
This command is also useful on limited bandwidth point-to-point links or X.25 interfaces.
Example
The following example sets a default interpacket delay of 55 ms for SAP updates sent on all interfaces:
ipx default-output-sap-delay 55Related Command
ipx default-triggered-sap-delay
ipx output-sap-delay
ipx triggered-sap-delayipx default-route
To forward packets to a default network it the a route to the packet's destination network is unknown, use the ipx default-route global configuration command. To discard all packets if the route to the destination network is unknown, use the no form of this command.
ipx default-route
no ipx default-routeSyntax Description
This command has no arguments or keywords.
Default
Enabled; that is, all packets for which a route to the destination is unknown are forwarded towards the default network, which is -2.
Command Mode
Global configuration
Example
The following example disables the forwarding of packets towards the default network:
no ipx default-routeRelated Command
ipx advertise-default-route-only
ipx default-triggered-rip-delay
To set the default interpacket delay for triggered Routing Information Protocol (RIP) updates sent on all interfaces, use the ipx default-triggered-rip-delay global configuration command. To return to the system default delay, use the no form of this command.
ipx default-triggered-rip-delay delay
no ipx default-triggered-rip-delay [delay]Syntax Description
Default
With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between routing update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.
Command Mode
Global configuration
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet routing update. A triggered routing update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.
The ipx default-triggered-rip-delay command sets the default interpacket delay for triggered routing updates sent on all interfaces. On a single interface, you can override this global default delay for triggered routing updates using the ipx triggered-rip-delay interface command.
The global default delay for triggered routing updates overrides the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered routing updates.
If the delay value set by the ipx output-rip-delay or ipx default-output-rip-delay command is high, then we strongly recommend a low delay value for triggered routing updates so that updates triggered by special events are sent in a more timely manner than periodic routing updates.
Novell recommends a delay of 55 ms for compatibility with older and slower IPX machines. These machines may lose RIP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX machines.
The default delay on a NetWare 3.11 server is about 100 ms.
When you do not set the interpacket delay for triggered routing updates, the system uses the delay specified by the ipx output-rip-delay or ipx default-output-rip-delay command for both periodic and triggered routing updates.
When you use the no form of the ipx default-triggered-rip-delay command, the system uses the delay set by the ipx output-rip-delay or ipx default-output-rip-delay command for triggered RIP updates, if set. Otherwise, the system uses the initial default delay as described in the "Default" section.
This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.
Example
The following example sets an interpacket delay of 55 ms for triggered routing updates sent on all interfaces:
ipx default-triggered-rip-delay 55Related Command
ipx default-output-rip-delay
ipx output-rip-delay
ipx triggered-rip-delayipx default-triggered-sap-delay
To set the default interpacket delay for triggered Service Advertisement Protocol (SAP) updates sent on all interfaces, use the ipx default-triggered-sap-delay global configuration command. To return to the system default delay, use the no form of this command.
ipx default-triggered-sap-delay delay
no ipx default-triggered-sap-delay [delay]Syntax Description
Default
With Cisco IOS Release 10.0 and Release 10.2, the default delay is 0 ms (that is, no additional delay between update packets). With Cisco IOS Release 10.3 and Release 11.0, the default delay is 5 ms.
Command Mode
Global configuration
Usage Guidelines
The interpacket delay is the delay between the individual packets sent in a multiple-packet SAP update. A triggered SAP update is one that the system sends in response to a "trigger" event, such as a request packet, interface up/down, route up/down, or server up/down.
The ipx default-triggered-sap-delay command sets the default interpacket delay for triggered SAP updates sent on all interfaces. On a single interface, you can override this global default delay for triggered updates using the ipx triggered-sap-delay interface command.
The global default delay for triggered updates overrides the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered updates.
If the delay value set by the ipx output-sap-delay or ipx default-output-sap-delay command is high, then we strongly recommend a low delay value for triggered updates so that updates triggered by special events are sent in a more timely manner than periodic updates.
Novell recommends a delay of 55 ms for compatibility with older and slower IPX servers. These servers may lose SAP updates because they process packets more slowly than the router sends them. The delay imposed by this command forces the router to pace its output to the slower-processing needs of these IPX servers.
The default delay on a NetWare 3.11 server is about 100 ms.
When you do not set the interpacket delay for triggered SAP updates, the system uses the delay specified by the ipx output-sap-delay or ipx default-output-sap-delay command for both periodic and triggered SAP updates.
When you use the no form of the ipx default-triggered-sap-delay command, the system uses the delay set by the ipx output-sap-delay or ipx default-output-sap-delay command for triggered SAP updates, if set. Otherwise, the system uses the initial default delay as described in the "Default" section.
This command is also useful on limited bandwidth point-to-point links or X.25 and Frame Relay multipoint interfaces.
Example
The following example sets an interpacket delay of 55 ms for triggered SAP updates sent on all interfaces:
ipx default-triggered-sap-delay 55Related Command
ipx default-output-sap-delay
ipx output-sap-delay
ipx triggered-sap-delayipx delay
To set the tick count, use the ipx delay interface configuration command. To reset the default increment in the delay field, use the no form of this command.
ipx delay ticks
no ipx delaySyntax Description
ticks
Number of IBM clock ticks of delay to use. One clock tick is 1/18th of a second (approximately 55 milliseconds).
Default
The default delay is determined from the delay configured on the interface with the delay command. It is (interface delay + 333) / 334. Therefore, unless you change the delay by a value greater than 334, you will not notice a difference.
Command Mode
Interface configuration
Usage Guidelines
The ipx delay command sets the count used in the IPX RIP delay field, which is also known as the ticks field.
Leaving the delay at its default value is sufficient for most interfaces.
If you do not specify the ipx delay command on an interface and you have not changed the interface delays with the interface delay interface configuration command, all LAN interfaces have a delay of 1 and all WAN interfaces have a delay of 6. The preferred method of adjusting delays is to use the ipx delay command, not the interface delay command. The show ipx interface EXEC command display only the delay value configured with the ipx delay command.
With IPXWAN, if you change the interface delay with the interface delay command, the ipx delay command uses that delay when calculating a delay to use. Also, when changing delays with IPXWAN, the changes affect only the link's calculated delay on the side considered to be the master.
Example
The following example changes the delay for serial interface 0 to 10 ticks:
interface serial 0 ipx delay 10Related Commands
A dagger (†) indicates that the command is document
