- access-list (connect initiate)
- access-list (DECnet extended)
- access-list (DECnet standard)
- clear decnet accounting
- clear decnet counters
- decnet access-group
- decnet accounting list
- decnet accounting threshold
- decnet accounting transits
- decnet accounting
- decnet advertise
- decnet area-max-cost
- decnet area-max-hops
- decnet cluster-alias update
- decnet cluster-holdtime
- decnet congestion-threshold
- decnet conversion
- decnet cost
- decnet encapsulation
- decnet hello-timer
- decnet host
- decnet in-routing-filter
- decnet map
- decnet max-address
- decnet max-area
- decnet max-cost
- decnet max-hops
- decnet max-paths
- decnet max-visits
- decnet multicast-map
- decnet node-type
- decnet out-routing-filter
- decnet path-split-mode
- decnet propagate static
- decnet route (interface static route)
- decnet route (specific static route)
- decnet route default (interface default route)
- decnet route default (specific default route)
- decnet route-cache
- decnet router-priority
- decnet routing
- decnet routing-timer
- decnet split-horizon
- lat host-delay
- lat service autocommand
- mop enabled
- show decnet accounting
- show decnet interface
- show decnet map
- show decnet neighbors
- show decnet route
- show decnet static
- show decnet traffic
- show decnet
Cisco IOS DECnet Commands
Digital Equipment Corporation developed the DECnet protocol to provide a way for its computers to communicate with one another. Currently in its fifth major product release, DECnet Phase V is a superset of the Open System Interconnection (OSI) protocol suite, it supports all OSI protocols, and it is compatible with the previous release (Phase IV). DECnet Phase IV Prime supports inherent MAC addresses, which allow DECnet nodes to coexist with systems that run other protocols that have MAC address restrictions. DECnet support on Cisco routers includes local-area and wide-area DECnet Phase IV routing over Ethernet, Token Ring, FDDI, and serial lines such as X.25, Frame Relay, and Switched Multimegabit Data Service (SMDS).
Use the commands in this book to configure and monitor DECnet networks. For DECnet configuration information and examples, see the Cisco IOS Apollo Domain, Banyan VINES, DECnet, ISO CLNS, and XNS Configuration Guide, Release 12.2.
Note 
Not all Cisco access servers support DECnet. For more information, refer to the release notes for the current Cisco IOS release.
access-list (connect initiate)
Note The access-list (connect initiate) command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To create an access list that filters connect initiate packets, use this version of the access-list command in global configuration mode. To disable the access list, use the no form of this command.
access-list access-list-number {permit | deny} source source-mask [destination destination-mask] {eq | neq} [[source-object] [destination-object] [identification] any]
no access-list
The optional argument source-object consists of the following string:
src [{eq | neq | gt | lt} object-number] [exp regular-expression] [uic [group, user]]
The optional argument destination-object consists of the following string:
dst [{eq | neq | gt | lt} object-number] [exp regular-expression] [uic [group, user]]
The optional argument identification consists of the following string:
[id regular-expression] [password regular-expression] [account regular-expression]
Syntax Description
Defaults
No access list is defined.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Depending upon the arguments you use, you can define access lists in three ways:
•Restrict access based on source addresses
Use the source and source-mask arguments only.
•Restrict access based on destination addresses
Use the source, source-mask, destination, and destination-mask arguments.
•Add filters to further narrow access
Use the source, source-mask, destination, and destination-mask arguments, the eq, neq, or any keywords, and any or all of the following arguments: source-object, destination-object, and
identification.
Table 1 lists the DECnet object numbers.
Examples
The following example illustrates an access list for matching all connect packets for object number 27:
access-list 300 permit 0.0 63.1023 eq dst eq 27
The following example illustrates an access list for matching all connect packets except for the object number 17:
access-list 300 permit 0.0 63.1023 neq dst eq 17
The following example illustrates an access list for matching all connect packets where the access identification was SYSTEM:
access-list 300 permit 0.0 63.1023 eq id ^SYSTEM$
The following example illustrates an access list for matching all connect packets from area 1 to object number 27(27 = VAX/VMS Personal Utility or MAIL) where SYSTEM is the originating user:
access-list 300 permit 1.0 0.1023 eq src exp ^SYSTEM$ dst eq 27
The following example illustrates an access list for matching any connect packet and can be used at the end of a list to permit any packets not already matched:
access-list 300 permit 0.0 63.1023 eq any
Related Commands
access-list (DECnet extended)
Note The access-list (DECnet extended) command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To create an extended access list, use the access-list command in global configuration mode. To delete the entire access list, use the no form of this command.
access-list access-list-number {permit | deny} source source-mask [destination destination-mask]
no access-list
Syntax Description
Defaults
No access list is defined.
Command Modes
Global configuration (config)
Command History
Examples
The following example configures access list 301 to allow traffic from any host in networks 1 and 3. It implies no other traffic is permitted. (The end of a list contains an implicit "deny all else" statement.)
access-list 301 permit 1.0 0.1023 0.0 63.1023
access-list 301 permit 3.0 0.1023 0.0 63.1023
Related Commands
access-list (DECnet standard)
Note The access-list (DECnet standard) command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To create a standard access list, use the standard version of the access-list command in global configuration mode. To delete the entire access list, use the no form of this command.
access-list access-list-number {permit | deny} source source-mask
no access-list
Syntax Description
Defaults
No access list is defined.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
In contrast with IP masks, a DECnet mask specification of "all ones" is entered as the decimal value 1023. In IP, the equivalent is 255.
Examples
The following example sets up access list 300 to deny packets coming from node 4.51 and to permit packets coming from node 2.31:
access-list 300 deny 4.51 0.0
access-list 300 permit 2.31 0.0
Related Commands
clear decnet accounting
Note The clear decnet accounting command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To delete all entries in the accounting database when DECnet accounting is enabled, use the clear decnet accounting command in EXEC mode.
clear decnet accounting [checkpoint]
Syntax Description
checkpoint |
(Optional) Clears the checkpoint database. |
Command Modes
EXEC (#)
Command History
Usage Guidelines
Specifying the clear decnet accounting command without the checkpoint keyword copies the active database to the checkpoint database and clears the active database.
The active data set is copied to the checkpoint database; the active database entry values are reset to zero. If there are entries in the database that were found dynamically, they are deleted. If there are entries that were entered statically, such as decnet accounting list 5.3.17.26, they are not removed. Their values are reset to zero.
Any traffic that traverses the router after the clear decnet accounting command has been issued is saved in the active database. Accounting information in the checkpoint database at that time reflects traffic prior to the most recent clear decnet accounting command.
You can also delete all entries in both the active and the checkpoint databases by issuing the clear decnet accounting command twice in succession.
Examples
In the following example, the first display from the show decnet accounting command shows the active database before a clear command is issued. The clear decnet accounting command is issued, and a second show display shows no accounting information in the active database. The display from the show decnet accounting checkpoint command shows the data collected in the active database prior to the clear decnet accounting command.
Router# show decnet accounting
Source Destination Bytes Packets
2.329 37.4 153 6
5.7 7.8 326 4
27.100 27.107 145 5
7.8 5.7 152 12
27.107 27.100 500 5
37.4 2.329 78 4
Accounting data age is 12.41
Router# clear decnet accounting
Router# show decnet accounting
Source Destination Bytes Packets
Accounting data age is 0
Router# show decnet accounting checkpoint
Source Destination Bytes Packets
2.329 37.4 153 6
5.7 7.8 326 4
27.100 27.107 145 5
7.8 5.7 152 12
27.107 27.100 500 5
37.4 2.329 78 4
Accounting data age is 12.41
Related Commands
clear decnet counters
Note The clear decnet counters command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To clear DECnet counters that are shown in the output of the show decnet traffic EXEC command, use the clear decnet counters command in EXEC mode.
clear decnet counters
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following example zeros all DECnet counters:
clear decnet counters
Related Commands
|
|
|
|---|---|
show decnet traffic |
Shows the DECnet traffic statistics (including datagrams sent, received, and forwarded). |
decnet access-group
Note The decnet access-group command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To create a DECnet access group, use the decnet access-group command in interface configuration mode. To delete a DECnet access-group, use the no form of this command.
decnet access-group access-list-number
no decnet access-group
Syntax Description
Defaults
No access group is defined.
Command Modes
Interface configuration (config-if)
Command History
Examples
The following example applies access list 389 to Ethernet interface 1:
interface ethernet 1
decnet access-group 389
Related Commands
|
|
|
|---|---|
access-list (DECnet standard) |
Creates a standard access list. |
show decnet interface |
Displays the global DECnet status and configuration for all interfaces. |
decnet accounting list
Note The decnet accounting list command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To specify the source and destination address pairs for which DECnet accounting information is kept, use the decnet accounting list command in global configuration mode. DECnet accounting tracks all traffic that traverses the router between the source and destination address pairs specified with this command. To remove the accounting filter, use the no form of this command.
decnet accounting list src-dec-address dest-dec-address
no decnet accounting list {src-dec-address dest-dec-address | all}
Syntax Description
Defaults
No filters are predefined.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The source and destination addresses of each DECnet packet are paired to create an entry in the database. When DECnet traffic traverses the router and a match is found, accounting information about the DECnet packet is entered into the accounting database. If DECnet accounting is enabled on an interface, but no accounting list is specified, the transit parameter does not come into play. DECnet accounting will track all traffic through the interface, up to the accounting threshold limit. All traffic up to the threshold limit is collected and added to the aggregate value for all DECnet traffic passing through the router.
Use the no decnet accounting list all to delete the entire entry list.
Examples
The following example adds DECnet host pair 5.37 and 6.126 to the list of networks for which accounting information is kept:
decnet accounting list 5.37 6.126
Related Commands
decnet accounting threshold
Note The decnet accounting threshold command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set the maximum number of accounting database entries, use the decnet accounting threshold command in global configuration mode. To restore the default, use the no form of this command.
decnet accounting threshold threshold
no decnet accounting threshold threshold
Syntax Description
threshold |
Maximum number of entries (source and destination address pairs) that Cisco IOS software can accumulate. |
Defaults
512 entries
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The accounting threshold defines the maximum number of entries (source and destination address pairs) that the software accumulates. The threshold is designed to prevent DECnet accounting from consuming all available free memory. This level of memory consumption could occur in a router that is switching traffic for many hosts. To determine whether overflows have occurred, use the show decnet accounting EXEC command.
Examples
The following example sets the DECnet accounting database threshold to 256 entries:
decnet accounting threshold 256
Related Commands
decnet accounting transits
Note The decnet accounting transits command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set the maximum number of transit entries that will be stored in the DECnet accounting database, use the decnet accounting transits command in global configuration mode. To disable this function, use the no form of this command.
decnet accounting transits count
no decnet accounting transits
Syntax Description
count |
Number of transit entries that will be stored in the DECnet accounting database. |
Defaults
0 entries
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Transit entries are those that do not match any of the source and destination address pair filters specified by decnet accounting list global configuration commands. If an accounting list is not defined, DECnet accounting will track all traffic through the interface (all transit entries) up to the accounting threshold limit.
To maintain accurate accounting totals, Cisco IOS software maintains two accounting databases: an active database and a checkpoint database.
Examples
The following example specifies a maximum of 100 transit records to be stored in the DECnet accounting database:
decnet accounting transits 100
Related Commands
decnet accounting
Note The decnet accounting command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To enable DECnet accounting, use the decnet accounting command in interface configuration mode. To disable DECnet accounting, use the no form of this command.
decnet accounting
no decnet accounting
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The Cisco IOS software maintains two accounting databases: an active database and a checkpoint database. The active database contains accounting data tracked until the database is cleared. When the active database is cleared, its contents are copied to the checkpoint database. Using these two databases together allows you to monitor both current traffic and traffic that has previously traversed the router.
DECnet accounting statistics will be accurate, even if DECnet fast switching is enabled, or if DECnet access lists are being used.
Enabling DECnet accounting significantly decreases the performance of a fast-switched interface.
DECnet accounting is disabled if autonomous or SSE switching is enabled.
Examples
This example shows DECnet accounting enabled on serial interface 0:
interface serial 0
decnet accounting
Related Commands
decnet advertise
Note The decnet advertise command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To configure border routers to propagate Phase IV areas through an OSI backbone, use the decnet advertise command in global configuration mode. To disable this function, use the no form of this command.
decnet advertise [decnet-area] hops cost
no decnet advertise [decnet-area]
Syntax Description
Defaults
Disabled
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The output from the show decnet route EXEC command shows the cost and hop count for routes.
The decnet advertise command is used by border routers for propagating Phase IV areas through an OSI backbone.
The decnet advertise command and the clns route nsap-prefix discard command work together. When a router has DECnet Phase IV/V conversion enabled, any packet with the specified Connectionless Network Service (CLNS) Network Service Access Point (NSAP) prefix will cause CLNS to behave as if no route were found. That router then looks up the route to the border router that is advertising the Phase IV route. In turn, the router that is advertising the DECnet Phase IV route converts the packet to Phase V and sends it through the OSI cloud to the border router that is advertising the CLNS discard static route. After the packet gets to the border router, it is converted back to Phase IV.
The CLNS discard routes are created dynamically when the advertised adjacencies are propagated through the CLNS cloud. When a DECnet interface is disabled, the adjacencies are lost and the CLNS discard route is deleted. The DECnet area routing states are displayed in the output from the show decnet route EXEC command.
Examples
The following example shows a partial use of the decnet advertise command:
decnet conversion 49
decnet advertise 4
clns route 49.0001 discard
Related Commands
|
|
|
|---|---|
clns route discard |
Explicitly tells a router to discard packets with NSAP addresses that match the specified nsap-prefix. |
show decnet route |
Displays the DECnet routing table. |
decnet area-max-cost
Note The decnet area-max-cost command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set the maximum cost specification value for interarea routing, use the decnet area-max-cost command in global configuration mode.
decnet [network-number] area-max-cost value
Syntax Description
Defaults
network-number: 0
value: 1022
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Be sure that you have used the decnet node-type area global configuration command before using this command.
Examples
The following example specifies the node type as area and sets the maximum cost to 500. Any route with a cost exceeding 500 is considered unreachable by this router.
decnet node-type area
decnet area-max-cost 500
Related Commands
decnet area-max-hops
Note The decnet area-max-hops command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set the maximum hop count value for interarea routing, use the decnet area-max-hops command in global configuration mode.
decnet [network-number] area-max-hops value
Syntax Description
Defaults
network-number: 0
hops: 30
Command Modes
Global configuration (config)
Command History
Usage Guidelines
This command is only valid for area routers. Be sure that you have issued the decnet node-type area global configuration command before using this command.
Examples
The following example sets the router to be a Level 2 router and then sets a maximum hop count of 21:
decnet node-type area
decnet area-max-hops 21
Related Commands
decnet cluster-alias update
Note The decnet cluster-alias update command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To allow all cluster aliases to be propagated, use the decnet cluster-alias update command in interface configuration mode. To prevent cluster aliases from being propagated, use the no form of this command.
decnet cluster-alias update
no decnet cluster-alias update
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
By default, cluster aliases updates are disabled because they can cause loops in topologies in which DECnet Phase IV is running and where there is a VAX cluster with multiple LAN links between them. If you want to propagate the cluster aliases updates, you can use the decnet cluster-alias update interface configuration command.
Examples
The following example enables the cluster alias updates:
decnet cluster-alias update
Related Commands
|
|
|
|---|---|
decnet cluster holdtime |
Sets a holdtime for a cluster alias adjacency. |
decnet cost |
Assigns a cost to an interface. |
decnet cluster-holdtime
Note The decnet cluster-holdtime command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set a holdtime for a cluster alias adjacency, use the decnet cluster-holdtime command in interface configuration mode. To restore the default, use the no form of this command.
decnet cluster-holdtime seconds
no decnet cluster-holdtime
Syntax Description
seconds |
Amount of time, in seconds, before the cluster alias adjacency times out. |
Defaults
300 seconds
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
When you have Phase IV VAX clusters and have enabled cluster aliases, you must ensure that the Phase IV VAX clusters are reachable by remote end systems. The Phase IV router will look for the L1 routing updates from the VAX machine that is acting as the gratuitous router for the VAX cluster, extracting the cluster alias from the update and injecting it into the Phase V cloud, thus allowing reachability to remote end systems. In order for updates to be accepted, the DECnet cluster holdtime must be set to a greater time than the VAX broadcast routing timer. Using the decnet cluster-holdtime command will allow you to ensure that the holdtime has been set to a time period greater than the VAX broadcast timer. The VAX broadcast timer will determine the rate at which entries are refreshed. To see the current setting of the decnet cluster-holdtime command, enter the show decnet interface command.
Examples
The following example sets a cost of 1 for the Ethernet interface 1/0 and a cluster time of 200 seconds:
decnet routing 21.456
interface ethernet 1/0
decnet cost 1
decnet cluster-holdtime 200
Related Commands
|
|
|
|---|---|
show decnet interface |
Displays the global DECnet status and configuration for all interfaces. |
decnet congestion-threshold
Note The decnet congestion-threshold command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set the congestion-experienced bit if the output queue has more than the specified number of packets in it, use the decnet congestion-threshold command in interface configuration mode. To remove the parameter setting and set it to 0, use the no form of this command.
decnet congestion-threshold number
no decnet congestion-threshold
Syntax Description
Defaults
1 packet
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
If a router configured for DECnet experiences congestion, it sets the congestion-experienced bit. A number value of zero or the no form of the command prevents this bit from being set.
Examples
The following example sets the congestion threshold to 10:
interface ethernet 0
decnet congestion-threshold 10
decnet conversion
Note The decnet conversion command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To allow Phase IV routers (running Cisco Release 9.1 or higher) to run in a Phase V network and vice versa, enable conversion with the decnet conversion command in global configuration mode. To disable conversion, use the no form of this command.
decnet conversion nsap-prefix
no decnet conversion nsap-prefix
Syntax Description
nsap-prefix |
Value used for the IDP field when constructing NSAPs from a Phase IV address. |
Defaults
Disabled
Command Modes
Global configuration (config)
Command History
Usage Guidelines
To enable DECnet conversion, you must configure both DECnet and ISO CLNS on your router.
DECnet Phase V is OSI-compatible and conforms to the ISO 8473 (CLNP/CLNS) and
ISO 9542 (ES-IS) standards. Digital has defined algorithms for mapping a subset of the Phase V address space onto the Phase IV address space and for converting Phase IV and Phase V packets back and forth. This allows a network administrator to support both Phase IV hosts in Phase V networks and Phase V hosts in Phase IV networks.
Cisco's implementation differs from Digital's in how reachability information is advertised. Cisco's implementation allows you to add Phase V support without modifying your existing Phase IV support. It also delays converting packets from Phase IV to Phase V, while Digital's implementation converts as soon as possible.
It is essential that the area you specify in the decnet routing global configuration command is the same as the local area you specified with the net router configuration command for the CLNS network.
Be sure that the area you specify in the decnet conversion command is the same as the area you specified for the CLNS network. Also note that the DECnet area is specified in decimal, and the CLNS area is specified in hexadecimal.
The decnet routing command is specified with a decimal address, while the net command address is specified in hexadecimal. In addition, the nsap-prefix specified on the decnet conversion command must match one of the NETs for this router.
The following guidelines apply:
•Host connectivity across multiple areas is only possible if a Level 2 path exists for which every Level 2 router in the path supports a common protocol: Phase IV or Phase V. If not all routers support both protocols, those routers that do must have conversion enabled.
•Host connectivity across a single area is only possible if a Level 1 path exists for which every Level 1 router in the path supports a common protocol: Phase IV or Phase V. If not all routers support both protocols, those routers that do must have conversion enabled.
•The Level 2 backbone must have conversion enabled in all Level 2 routers that support an area that needs conversion.
Examples
The following example enables DECnet conversion on a router with the area tag xy and Phase IV address 20.401 using an ISO IGRP router:
clns routing
decnet routing 20.401
decnet max-address 600
!
router iso-igrp xy
net 47.0004.004d.0014.aa00.0400.9151.00
!
decnet conversion 47.0004.004d
!
interface ethernet 0
decnet cost 4
clns router iso-igrp xy
Related Commands
decnet cost
Note The decnet cost command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set a cost value for an interface, use the decnet cost command in interface configuration mode. To disable DECnet routing for an interface, use the no form of this command.
decnet cost cost-value
no decnet cost
Syntax Description
cost-value |
Integer from 1 to 63. There is no default cost for an interface, although a suggested cost for FDDI is 1, for Ethernet is 4, and for serial links is greater than 10. |
Defaults
Disabled
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The decnet cost command is required for all interfaces on which DECnet routing is configured.
After DECnet routing has been enabled, you must assign a cost to each interface over which you want DECnet to run. Assigning a cost in effect enables DECnet routing for an interface. Most DECnet installations have an individualized routing strategy for using costs. Therefore, check the routing strategy used at your installation to ensure that costs you specify are consistent with those set for other hosts on the network.
Examples
The following example establishes a DECnet routing process for a router and sets the router's DECnet address to 21.456, and then sets a cost of 4 for the Ethernet interface 0:
decnet routing 21.456
interface ethernet 0
decnet cost 4
Related Commands
decnet encapsulation
Note The decnet encapsulation command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To provide DECnet encapsulation over Token Ring, use the decnet encapsulation command in interface configuration mode.
decnet encapsulation {pre-dec | dec}
Syntax Description
Defaults
Encapsulation is compatible with other Digital equipment.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
If you have both Release 9.0 and 9.1 routers in the same network, you must use the pre-dec encapsulation type on the 9.1 routers.
Note You must first enable DECnet routing on the selected Token Ring interface before you can configure the DECnet encapsulation mode.
Examples
The following example sets Cisco-style encapsulation for DECnet routing, which means that Cisco and Digital equipment will not interoperate over Token Ring:
interface tokenring 0
decnet encapsulation pre-dec
decnet cost 4
Related Commands
|
|
|
|---|---|
decnet cost |
Sets a cost value for an interface. |
show decnet interface |
Displays the global DECnet status and configuration for all interfaces. |
decnet hello-timer
Note The decnet hello-timer command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To change the interval for sending broadcast hello messages, use the decnet hello-timer command in interface configuration mode. To restore the default value, use the no form of this command.
decnet hello-timer seconds
no decnet hello-timer
Syntax Description
seconds |
Interval at which Cisco IOS software sends hello messages. It can be a decimal number in the range 1 to 8191 seconds. The default is 15 seconds. |
Defaults
15 seconds
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Cisco IOS software broadcasts hello messages on all interfaces with DECnet enabled. Other hosts on the network use the hello messages to identify the hosts with which they can communicate directly. On extremely slow serial lines, you may want to increase the default value to reduce overhead on the line.
Examples
The following example increases the hello interval to 2 minutes (120 seconds) on serial interface 1:
interface serial 1
decnet hello-timer 120
Related Commands
|
|
|
|---|---|
show decnet interface |
Displays the global DECnet status and configuration for all interfaces. |
decnet host
Note The decnet host command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To associate a name-to-DECnet address mapping, use the decnet host command in global configuration mode. To disable name mapping, use the no form of this command.
decnet host name decnet-address
no decnet host name
Syntax Description
Defaults
No name is defined.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The assigned name is displayed, where applicable, in show decnet route and show hosts EXEC command output.
The name can also be used with the ping decnet command.
Examples
The following example defines name-to-DECnet address mapping:
decnet host cisco1 3.33
Related Commands
decnet in-routing-filter
Note The decnet in-routing-filter command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To provide access control to hello messages or routing information received on an interface, use the decnet in-routing-filter command in interface configuration mode. To remove access control, use the no form of this command.
decnet in-routing-filter access-list-number
no decnet in-routing-filter
Syntax Description
access-list-number |
Standard DECnet access list. This list applies to source addresses. The value can be in the range 300 to 399. |
Defaults
No access control is defined.
Command Modes
Interface configuration (config-if)
Command History
Examples
The following example sets up Ethernet interface 0 with a DECnet in-routing filter of 321, which means that any hello messages sent from addresses that are denied in list 321 are ignored. Additionally, all node addresses listed in received routing messages on this interface are checked against the access list, and only routes passing the filter are considered usable.
interface ethernet 0
decnet in-routing-filter 321
Related Commands
decnet map
Note The decnet map command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To establish an address translation for selected nodes, use the decnet map command in global configuration mode.
decnet first-network map virtual-address second-network real-address
Syntax Description
Defaults
No address translation is defined.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Keep the following limitations in mind when configuring the address translation gateway (ATG):
•Both nodes that want to communicate across the ATG must exist in the translation map. Other nodes outside of the map will see route advertisements for the mapped address, but will be unable to communicate with them. An unmapped node trying to communicate with a mapped node will always get the message, "Node unreachable." This can be confusing if another nearby node can communicate with mapped nodes because it is also a mapped node.
•Third-party DECnet applications could fail if they pass node number information in a data stream (most likely a sign of a poorly designed application).
•Routing information for mapped addresses is static and does not reflect the reachability of the actual node in the destination network.
As an additional feature and security caution, DECnet "Poor Man's Routing" can be used between nodes outside of the translation map as long as those nodes have access to nodes that are in the map, so that a user on node B could issue the following VMS command:
$ dir A::D::E::
When a Poor Man's Routing connection is made between two networks, only the two adjacent nodes between the networks will have any direct knowledge about the other network. Application-level network access may then be specified to route through the connection.
Note Cisco does not support "Poor Man's Routing" directly; the intermediate nodes must be VMS systems with "Poor Man's Routing" enabled in file-access language.
Examples
In the following example, packets in network 0 sent to address 19.5 will be routed to network 1, and the destination address will be translated to 50.1. Packets sent to address 47.1 in network 1 will be routed to network 0 as 19.1.
decnet 0 map 19.5 1 50.1
decnet 1 map 47.1 0 19.1
Related Commands
|
|
|
|---|---|
show decnet map |
Displays the address mapping information used by the DECnet Address Translation Gateway. |
decnet max-address
Note The decnet max-addressers command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To configure Cisco IOS software with a maximum number of node addresses, use the decnet max-address command in global configuration mode.
decnet [network-number] max-address value
Syntax Description
Defaults
network-number: 0
1023 node addresses
Command Modes
Global configuration (config)
Command History
Usage Guidelines
DECnet routers do not have the concept of aging out a route. Therefore, all possible areas or nodes must be advertised as unreachable if they cannot be reached. Since it is best to keep routing updates small, you must indicate the default maximum possible node and area numbers that can exist in the network.
Examples
The following example configures a small network to a maximum address value of 300:
decnet max-address 300
Related Commands
|
|
|
|---|---|
decnet max-area |
Sets the largest number of areas that Cisco IOS software can handle in its routing table. |
decnet max-area
Note The decnet max-area command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set the largest number of areas that Cisco IOS software can handle in its routing table, use the decnet max-area command in global configuration mode.
decnet [network-number] max-area area-number
Syntax Description
Defaults
network-number: 0
63 areas
Command Modes
Global configuration (config)
Command History
Examples
In the following example, the largest area to be stored in the routing table is 45:
decnet max-area 45
Related Commands
decnet max-cost
Note The decnet max-cost command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set the maximum cost specification for intra-area routing, use the decnet max-cost command in global configuration mode.
decnet [network-number] max-cost cost
Syntax Description
network-number |
(Optional) Network number in the range 0 to 3. Specified when using ATG. |
cost |
Cost from 1 to 1022. The default is 1022. |
Defaults
network-number: 0
cost: 1022
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Cisco IOS software ignores routes within its local area that have a cost greater than the value you specify.
Examples
The following example specifies the node type as a Level 1 router and sets the maximum cost to 335. Any route whose cost exceeds 335 is considered unreachable by this router.
decnet node-type routing-iv
decnet max-cost 335
Related Commands
decnet max-hops
Note The decnet max-hops command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set the maximum hop count specification value for intra-area routing, use the decnet max-hops command in global configuration mode.
decnet [network-number] max-hops hop-count
Syntax Description
Defaults
network-number: 0
30 hops
Command Modes
Global configuration (config)
Command History
Examples
The following example sets the router to be a Level 1 router and then sets a maximum hop count of 2:
decnet node-type routing-iv
decnet max-hops 2
Related Commands
decnet max-paths
Note The decnet max-paths command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To define the maximum number of equal-cost paths to a destination that Cisco IOS software keeps in its routing table, use the decnet max-paths command in global configuration mode.
decnet [network-number] max-paths value
Syntax Description
Defaults
network-number: 0
1 equal-cost path
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Limiting the number of equal-cost paths can save memory on routers with limited memory or very large configurations. Additionally, in networks with a large number of multiple paths and end-systems with limited ability to cache out-of-sequence packets, performance may suffer when traffic is split between many paths.
Limiting the size of the routing table does not affect the ability of your routers to recover from network failures transparently, provided that you do not make the maximum number of paths too small. If more than the specified number of equal-cost paths exist, and one of those paths suddenly becomes unusable, the software will discover an additional path from the paths it has been ignoring.
Examples
In the following example, the software will save no more than three equal-cost paths:
decnet max-paths 3
Related Commands
decnet max-visits
Note The decnet max-visits command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set the limit on the number of times a packet can pass through a router, use the decnet max-visits command in global configuration mode.
decnet [network-number] max-visits value
Syntax Description
Defaults
network-number: 0
63 times
Command Modes
Global configuration (config)
Command History
Examples
The following example of intra-area routing configuration specifies Level 1 routing, a maximum hop count of 28, and a maximum number of visits of 62 (which is more than twice 28):
decnet node-type routing-iv
decnet max-hops 28
decnet max-visits 62
Related Commands
decnet multicast-map
Note The decnet multicast-map command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To specify a mapping between DECnet multicast addresses and Token Ring functional addresses, other than the default mapping, use the decnet multicast-map command in interface configuration mode. To delete the specified information, use the no form of this command.
decnet multicast-map multicast-address-type functional-address
no decnet multicast-map multicast-address-type functional-address
Syntax Description
Defaults
Enabled, with the default mapping listed in Table 2.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
This command is valid for Token Ring interfaces only. The command will reject a functional address that does not start with "C000" or "c000."
Routing multicasts and end node multicasts must be on different functional addresses. Table 2 shows the default mapping of DECnet multicast address types to Token Ring functional addresses.
Examples
The following example configures Token Ring interface 1 for multicasts of all Phase IV end nodes and the multicast ID is configured to map to MAC address c000.2222.3333:
interface tokenring 1
decnet multicast-map iv-all-endnodes c000.2222.3333
decnet node-type
Note The decnet node-type command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To specify the node type, use the decnet node-type command in global configuration mode.
decnet [network-number] node-type {area | routing-iv}
Syntax Description
Defaults
No node type is specified.
Command Modes
Global configuration (config)
Command History
Examples
In the following example, the router node type is specified as area, or Level 2:
decnet node-type area
Related Commands
decnet out-routing-filter
Note The decnet out-routing-filter command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To provide access control to routing information being sent out on an interface, use the decnet out-routing-filter command in interface configuration mode. To remove access control, use the no form of this command.
decnet out-routing-filter access-list-number
no decnet out-routing-filter
Syntax Description
access-list-number |
Standard DECnet access list applying to source addresses. The value can be in the range 300 to 399. |
Defaults
No access control to routing information is defined.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Addresses that fail this test are shown in the update message as unreachable.
Examples
The following example sets up Ethernet interface 1 with a DECnet out-routing filter of 351. This filter is applied to addresses in the transmitted routing updates. Transmitted hello messages are not filtered.
interface ethernet 1
decnet out-routing-filter 351
Related Commands
decnet path-split-mode
Note The decnet path-split-mode command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To specify how Cisco IOS software splits the routable packets between equal-cost paths, use the decnet path-split-mode command in global configuration mode.
decnet path-split-mode {normal | interim}
Syntax Description
Defaults
Normal mode
Command Modes
Global configuration (config)
Command History
Examples
In the following example, a router will split routable packets between equal-cost paths using the round-robin (or first-come, first-served) basis:
decnet path-split-mode normal
Related Commands
decnet propagate static
Note The decnet propagate static command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To enable static route propagation, use the decnet propagate static command in global configuration mode. To disable propagation, use the no form of this command.
decnet propagate static
no decnet propagate static
Syntax Description
This command has no arguments or keywords.
Defaults
No default routes are propagated.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
By default, DECnet static routes are not propagated to other routers. Use the decnet propagate static command to enable static route propagation. A default route is used only after DECnet conversion is checked.
Examples
The following example enables static route propagation for the specified static and default routes:
decnet propagate static
!
decnet route 3.0 ethernet 0 aa00.0400.0404
decnet route 5.0 serial 0
decnet route 5.100 serial 2
decnet route default 2.100
decnet route 6.0 2.3 4 5
Related Commands
decnet route (interface static route)
Note The decnet route (interface static route) command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To create an interface static route, use this version of the decnet route command in global configuration mode. To remove this route, use the no form of this command.
decnet route decnet-address next-hop-type number [snpa-address] [hops [cost]]
no decnet route decnet-address next-hop-type number
Syntax Description
Defaults
hops: 0
cost: 0
No interface static routes are created.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
If you do not specify a Subnetwork Point of Attachment (SNPA) address when you have a multiaccess network, you receive an error message indicating a bad SNPA. By default, DECnet static routes are not propagated to other routers. Use the decnet propagate static command to enable propagation.
Examples
The following example creates a static route for a serial interface. No SNPA need be specified for point-to-point interfaces.
decnet route 3.1 serial 1
The following example creates a static route for an Ethernet interface. The SNPA must be specified for an interface that is not point-to-point.
decnet route 3.2 ethernet 1 aa00.0400.0104
Related Commands
decnet route (specific static route)
Note The decnet route (specific static route) command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To enter a specific static route, use this version of the decnet route command in global configuration mode. DECnet addresses that match are forwarded to the next-hop-address. To remove this route, use the no form of this command.
decnet route decnet-address next-hop-address [hops [cost]]
no decnet route decnet-address next-hop-address
Syntax Description
Defaults
No interface static routes are created.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Area static routes can be configured by specifying a DECnet node address of 0. By default, DECnet static routes are not propagated to other routers. Use the decnet propagate static command to enable propagation.
Examples
The following example creates a static route for 1.1 that points to 1.9 and uses default values of 0 for the hops and cost arguments:
decnet route 1.1 1.9
The following example creates a static route for 3.100 that points to 3.4 and specifies values for the hops and cost:
decnet route 3.100 3.4 9 8
The following example creates a static route for area 1 that points to 2.999:
decnet route 1.0 2.999
Related Commands
decnet route default (interface default route)
Note The decnet route default (interface default route) command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To create an interface default route, use this version of the decnet route default command in global configuration mode. To remove this route, use the no form of this command.
decnet route default next-hop-type number [snpa-address] [hops [cost]]
no decnet route default next-hop-type number
Syntax Description
Defaults
No interface default routes are created.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
If you do not specify an SNPA address when you have a multiaccess network, you receive an error message indicating a bad SNPA.
A default route is used only after DECnet conversion is checked. DECnet default routes are not propagated to other routers.
Examples
The following example creates a default route for a serial interface. No SNPA need be specified for point-to-point interfaces.
decnet route default serial 1
The following example creates a default route for an Ethernet interface. The SNPA must be specified for an interface that is not point-to-point.
decnet route default ethernet 1 aa00.0400.0104
Related Commands
decnet route default (specific default route)
Note The decnet route default (specific default route) command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To enter a specific default route, use this version of the decnet route default command in global configuration mode. To remove this route, use the no form of this command.
decnet route default next-hop-address [hops [cost]]
no decnet route default next-hop-address
Syntax Description
Defaults
hops: 0
cost: 0
No interface default routes are created.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
A default route is used only after DECnet conversion is checked. By default, DECnet static routes are not propagated to other routers. Use the decnet propagate static command to enable propagation.
DECnet packets not for the current area are forwarded to the next-hop-address.
Examples
The following example creates a default route for 1.3, which uses default values of 0 for hops and cost:
decnet route default 1.3
Related Commands
decnet route-cache
Note The decnet route-cache command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To enable fast switching, use the decnet route-cache command in interface configuration mode. To disable fast switching, use the no form of this command.
decnet route-cache
no decnet route-cache
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
By default, Cisco's DECnet routing software implements fast switching of DECnet datagrams. There are times when it makes sense to disable fast switching. This is especially important when using rates slower than T1.
Fast switching uses memory space on interface cards. In situations where a high-bandwidth interface is writing large amounts of information to a low-bandwidth interface, additional memory could help avoid congestion on the slow interface.
On a Cisco router that has DECnet traffic passing through a GRE tunnel interface and the decnet route-cache command enabled, loss of connectivity over the tunnel may occur after a tunnel key is configured on the tunnel interface. If this occurs, enter the no decnet route-cache command on the tunnel interface, followed by the decnet route-cache command to clear the problem.
Examples
The following example disables fast switching on Ethernet interface 0:
interface ethernet 0
no decnet route-cache
decnet router-priority
Note The decnet router-priority command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To elect a designated router to which packets are sent when no destination is specified, use the decnet router-priority command in interface configuration mode.
decnet router-priority value
Syntax Description
value |
Priority of the router. This can be a number in the range 0 to 127. The larger the number the higher the priority. |
Defaults
64
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The designated router is the router to which all end nodes on an Ethernet communicate if they do not know where else to send a packet. The designated router is chosen through an election process in which the router with the highest priority gets the job. When two or more routers on a single Ethernet in a single area share the same highest priority, the unit with the highest node number is elected. You can reset a router's priority to help ensure that it is elected designated router in its area.
On a LAN with both DECnet IV and DECnet IV Prime hosts, make sure that a bilingual router always becomes the designated router.
DECnet end systems use the designated router only when they have no other information about how to reach a particular system. The end systems maintain a cache of how to reach other systems on the network. The cache contains the following information:
<remote system DECnet address> <next hop DECnet address>
When an end system receives a packet, it examines three pieces of information: the intra-LAN bit, the source address, and the previous hop. If the intra-LAN bit is set, indicating that the packet has never left this wire (and, thus, the remote system is reachable without a router), a cache entry is created as follows:
<remote system DECnet address> = <source address>
<next hop DECnet address> = <source address>
If the intra-LAN bit is not set, indicating that the packet has come from another network, the cache entry is created as follows:
<remote system DECnet address> = <source address>
<next hop DECnet address> = <previous hop>
If there is no cache entry, then the designated router is used. This means that when starting a session, the designated router is used, but the reverse traffic will populate a cache entry so that the router can later communicate directly.
A DECnet IV Prime end node sends a packet to the Unknown Destination multicast if it has no cache entry for the destination and has no designated router.
Examples
The following example sets DECnet priority for this router to 110 on Ethernet interface 1:
interface ethernet 1
decnet router-priority 110
decnet routing
Note The decnet routing command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To enable DECnet routing, use the decnet routing command in global configuration mode. To disable DECnet routing, use the no form of this command.
decnet [network-number] routing [iv-prime] decnet-address
no decnet routing
Syntax Description
Defaults
Disabled
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Enabling DECnet changes the MAC addresses of the router's interfaces. This is not a problem on routers equipped with nonvolatile memory. On systems that attempt to get their IP network addresses from network servers rather than from nonvolatile memory, there may be a problem as with the hardware addresses changing and confusing other IP-speaking hosts. This potential problem can be avoided by configuring and enabling DECnet before enabling other protocols.
Note You can configure up to four DECnet networks (numbered 0 to 3). To set up multiple DECnet networks, use the decnet global configuration commands with the appropriate network number and keywords. If the network number is omitted from the commands, network 0 is configured for DECnet routing.
DECnet Phase IV Prime eliminates the DEC addressing restrictions so that DECnet nodes can coexist with systems running other protocols that have other MAC address restrictions. If iv-prime is not specified, only Phase IV is enabled; configuring the MAC address will then make DECnet inoperable. The standard "AA-00-04-00" form will be set as the address of the interface on which DECnet is enabled. If Phase IV Prime was already running and this command is reissued without the iv-prime keyword (that is, going from Phase IV Prime to Phase IV), the command returns an error if any of the interfaces that have DECnet enabled have MAC addresses that are not compliant with DECnet Phase IV, requiring the user to evaluate conflicting interface commands.
The no form of this command disables Phase IV and Phase IV Prime routing.
Examples
The following example enables DECnet routing for the router in area 21 with node number 456:
decnet routing 21.456
Related Commands
|
|
|
|---|---|
decnet cost |
Sets a cost value for an interface. |
decnet node-type |
Specifies the node type. |
decnet routing-timer
Note The decnet routing-timer command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To specify how often Cisco IOS software sends routing updates that list the hosts that the router can reach, use the decnet routing-timer command in interface configuration mode. To disable the routing update timer, use the no form of this command.
decnet routing-timer seconds
no decnet routing-timer
Syntax Description
seconds |
Time, in seconds, from 1 to 65,535. The default is 40 seconds. |
Defaults
40 seconds
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Other routers use this information to construct local routing tables. In a network where changes occur infrequently or do not need to be responded to immediately (it is small and uncomplicated, applications are not particularly sensitive to delays or occasional packet loss, slow serial links, and so on), increasing the time between routing updates reduces the amount of unnecessary network traffic. Digital calls this argument the broadcast routing timer because they use a different timer for serial lines; Cisco's DECnet implementation does not make this distinction.
Examples
The following example sets a serial interface to broadcast routing updates every 2 minutes (120 seconds):
interface serial 0
decnet routing-timer 120
decnet split-horizon
Note The decnet split-horizon command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To use split horizon when sending routing updates, use the decnet split-horizon command in interface configuration mode. To disable split horizon, use the no form of this command.
decnet split-horizon
no decnet split-horizon
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The decnet split-horizon command also affects whether broadcast packets received on an interface are resent on the same interface.
The decnet split-horizon command determines how much information is included in routing updates sent out an interface. It also determines whether received broadcasts are retransmitted on the same interface. When you enable split horizon, routing updates sent out on a given interface will not include any information that was originally learned from that interface, and broadcasts will not be retransmitted on the receiving interface. This is because split horizon is designed for networks that are either broadcast networks, or are fully connected mesh networks. In these types of networks, resending this information is a waste of network bandwidth because all other stations on that network have already heard the information. Disabling split horizon causes Cisco IOS software to include all information in routing updates, and to resend broadcast packets on the network from which they were received.
You can use this command on any interface, but generally it makes sense to use it only for X.25 and Frame Relay interfaces. You should disable split horizon on X.25 and Frame Relay networks that are not fully connected mesh topologies.
Examples
The following example disables split horizon on an X.25 network:
interface serial 0
no decnet split-horizon
lat host-delay
Note The lat host-delay command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To set the delayed acknowledgment for incoming local-area transport (LAT) slave connections, use the lat host-delay command in global configuration mode. To restore the default, use the no form of this command.
lat host-delay number
no host-delay
Syntax Description
number |
Delay, in milliseconds. |
Defaults
Disabled
Command Modes
Global configuration (config)
Command History
Examples
The following example sets the acknowledgment for incoming LAT slave connections to 100 milliseconds:
lat host-delay 100
lat service autocommand
Note The lat service autocommand command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To associate a command with a service, use the lat service autocommand command in global configuration mode. To remove the specified autocommand, use the no form of this command.
lat service service-name autocommand command
no lat service service-name autocommand command
Syntax Description
service-name |
Name of the service. |
command |
Command to be associated with the service. |
Defaults
No commands are automatically associated with a service.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
When an inbound connection is received for the specified service, the command associated with the service is automatically executed instead of the user receiving a virtual terminal session.
Authentication is bypassed for these services; only the LAT password is checked.
Note Do not use this option with the rotary keyword.
Examples
The following example associates the command telnet ramana to the service RAMANA:
lat service RAMANA autocommand telnet ramana
mop enabled
To enable an interface to support the Maintenance Operation Protocol (MOP), use the mop enabled command in interface configuration mode. To disable MOP on an interface, use the no form of this command.
mop enabled
no mop enabled
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled on Ethernet interfaces and disabled on all other interfaces.
Command Modes
Interface configuration (config-if)
Command History
Examples
The following example enables MOP for serial interface 0:
Router(config)# interface serial 0
Router(config-if)# mop enabled
Usage Guidelines
To disable MOP packets on member links, disable MOP on the port-channel interface by using the no mop enabled command.
Related Commands
show decnet accounting
Note The show decnet accounting command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To display the active accounting or checkpointed database, use the show decnet accounting command in EXEC mode.
show decnet accounting [checkpoint]
Syntax Description
checkpoint |
(Optional) Displays entries in the checkpoint database. |
Command Modes
EXEC (#)
Command History
Examples
This sample output from the show decnet accounting command shows accounting data collected for traffic passing between the DECnet address pair 27.100 and 27.107:
Router# show decnet accounting
Source Destination Bytes Packets
27.100 27.107 145 5
27.107 27.100 500 5
Accounting data age is 5
Table 3 describes the fields shown in the display.
Related Commands
show decnet interface
Note The show decnet interface command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To display the global DECnet status and configuration for all interfaces, or the status and configuration for a specified interface, use the show decnet interface command in EXEC mode.
show decnet interface [type number]
Syntax Description
type |
(Optional) Interface type. |
number |
(Optional) Interface number. |
Command Modes
EXEC (#)
Command History
Examples
The following is sample output from the show decnet interface command:
Router# show decnet interface
Global DECnet parameters for network 0:
Local address is 19.15, node type is area
Maximum node is 350, maximum area is 63, maximum visits is 63
Maximum paths is 1, path split mode is normal
Local maximum cost is 1022, maximum hops is 30
Area maximum cost is 1022, maximum hops is 30
Ethernet 1 is up, line protocol is up, encapsulation is ARPA
Interface cost is 4, priority is 64, DECnet network: 0
The designated router is 1.9
Sending HELLOs every 15 seconds, routing updates 40 seconds
Smallest router blocksize seen is 1498 bytes
Routing input list is not set, output list is not set
Access list is not set
DECnet fast switching is enabled
Number of L1 router adjacencies is: 3
Number of non-PhaseIV+ router adjacencies is: 3
Number of PhaseIV+ router adjacencies is: 0
Router is bilingual
Table 4 describes significant fields shown in the display.
The following is sample output from the show decnet interface command when you specify an interface:
Router# show decnet interface ethernet 0
Ethernet0 is up, line protocol is up, encapsulation is ARPA
Interface cost is 4, priority is 64, DECnet network: 0
The designated router is 1.3
Sending HELLOs every 15 seconds, routing updates 40 seconds
Smallest router blocksize seen is 1498 bytes
Routing input list is not set, output list is not set
Access list is not set
DECnet fast switching is enabled
Number of L1 router adjacencies is: 1
Number of non-PhaseIV+ router adjacencies is: 3
Number of PhaseIV+ router adjacencies is: 0
Router is bilingual
Table 5 describes significant fields shown in the display.
show decnet map
Note The show decnet map command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To display the address mapping information used by the DECnet Address Translation Gateway, use the show decnet map command in EXEC mode.
show decnet map
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC (#)
Command History
Examples
The following is sample output from the show decnet map command:
Router# show decnet map
Net Node -> Net Node Uses Cost Hops
0 1.100 1 2.100 0
Table 6 describes significant fields shown in the display.
show decnet neighbors
Note The show decnet neighbors command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To display all Phase IV and Phase IV Prime adjacencies and the MAC address associated with each neighbor, use the show decnet neighbors command in privileged EXEC mode.
show decnet neighbors
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the show decnet neighbors command:
Router# show decnet neighbors
Net Node Interface MAC address Flags
0 3.11 Ethernet0 aa00.0400.0b0c A
0 1.1 Ethernet0 aa00.0400.0104 V
0 1.3 Ethernet1 aa00.0400.0304 V
0 1.6 Ethernet1 aa00.0400.0604 V
0 2.2 TokenRing 5500.2000.4020 V IV-PRIME
Table 7 describes the fields shown in the display.
show decnet route
Note The show decnet route command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To display the DECnet routing table, use the show decnet route command in EXEC mode.
show decnet route [decnet-address]
Syntax Description
decnet-address |
(Optional) Displays the DECnet address and, when specified, the first hop route to that address. |
Command Modes
EXEC (#)
Command History
Examples
The following is sample output from the show decnet route command when a DECnet address name is not specified, so the entire routing table is displayed:
Router# show decnet route
Area Cost Hops Next Hop to Node Expires Prio
1 4 1 Ethernet1 -> 1.300 26 64 A
*1 4 1 Ethernet1 -> 1.400 37 64 A
*2 8 2 Ethernet1 -> 1.400
*5 0 0 (Local) -> 5.5
*10 4 1 Ethernet2 -> 10.1 36 64 A
*13 11 3 Ethernet1 -> 1.400
*44 22 6 Ethernet1 -> 1.400
*51 18 4 Ethernet1 -> 1.400
*61 1 1 (OSI) -> 5.5
*62 1 1 (OSI) -> 5.5
*3 0 0 (STATIC) Ethernet0, snpa aa00.0400.0404
*4 0 0 (STATIC) Serial0
*6 5 4 (STATIC) forwarding to 2.3
Node Cost Hops Next Hop to Node Expires Prio
*(Area) 0 0 (Local) -> 5.5
*5.5 0 0 (Local) -> 5.5 32 64 A+
*DEFAULT*: 0 0 using next hop address of 2.100
As the display shows, the show decnet route command can display more than one route for a destination when equal-cost paths have been set with the decnet max-paths global configuration command and when there is more than one equal-cost path to a destination. The display also shows that this node is an area router.
Table 8 describes significant fields shown in the display.
show decnet static
Note The show decnet static command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To display all statically configured DECnet routes, use the show decnet static command in privileged EXEC mode.
show decnet static
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
All static routes are stored in a static route queue, which allows static routes to be reinstated when DECnet routing is turned off then on again.
Not all routes in the static route queue will show up in the routing table. This happens under the following conditions:
•The router is a Level 1 router and any of the following apply. Assume the router DECnet address is 1.1:
–A Level 2 area static route is configured.
decnet route 2.0 1.2
–A static route is configured not in the same area as the router.
decnet route 3.10 1.200
–A static route is configured for the same address as the router.
decnet route 1.1 1.200
•The router is a Level 2 router and any of the following apply. Assume the router DECnet address is 2.1:
–A Level 1 static router is not in the same area as the router.
decnet route 4.1 10.200
–A static route appears because a Level 2 route is installed to area 4.
decnet route 4.0 10.200
–A Level 2 static route is configured for the router's own area.
decnet route 2.0 10.200
–A static route is configured for the same address as the router.
decnet route 2.1 5.4
Examples
The following is sample output from the show decnet static command:
Router# show decnet static
Address Cost Hops Next hop SNPA
3 0 0 Ethernet0 aa00.0400.0404
5 0 0 Serial0
5.100 0 0 Serial2
DEFAULT 0 0 2.100
6 5 4 2.3
Note that this router is a Level 2 router with a DECnet address of 1.2, so a static route configured for 5.100 is not relevant here. This route appears in the show decnet static command display, but not in the routing table.
show decnet traffic
Note The show decnet traffic command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To show the DECnet traffic statistics (including datagrams sent, received, and forwarded), use the show decnet traffic command in EXEC mode.
show decnet traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC (#)
Command History
Examples
The following is sample output from the show decnet traffic command:
Router# show decnet traffic
Total: 42 received, 0 format errors, 0 unimplemented
0 not a gateway, 0 no memory, 0 no routing vector
0 congestion encountered
Hellos: 21 received, 0 bad, 0 other area, 16 sent
Level 1 routing: 14 received, 0 bad, 0 other area, 16 sent
Level 2 routing: 7 received, 0 not primary router, 8 sent
Data: 0 received, 0 not long format, 0 too many visits
0 forwarded, 0 returned, 0 converted, 0 local destination
0 access control failed, 0 no route, 0 encapsulation failed
0 inactive network, 0 incomplete map
Table 9 describes the fields shown in the display.
show decnet
Note The show decnet command is not available in Cisco IOS Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
To display the global DECnet parameters, use the show decnet command in privileged EXEC mode.
show decnet
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the show decnet command:
Router# show decnet
Global DECnet parameters for network 0:
Local address is 19.15, node type is area (Phase-IV Prime)
Level-2 `Attached' flag is FALSE, nearest level-2 router is 19.5
Maximum node is 350, maximum area is 63, maximum visits is 63
Maximum paths is 1, path split mode is normal
Local maximum cost is 1022, maximum hops is 30
Area maximum cost is 1022, maximum hops is 30
Static routes *NOT* being sent in routing updates
Default route configured; next hop address of 2.100
Table 10 describes significant fields shown in the display.
Feedback