Table Of Contents
dlsw cache-ignore-netbios-datagram
dlsw transparent redundancy-enable
dlsw transparent switch-support
show dlsw transparent neighbor
DLSw+ Commands
This chapter describes the commands to configure data-link switching plus (DLSw+), our implementation of the DLSw standard. For DLSw+ configuration tasks and examples, refer to the "Configuring Data-Link Switching Plus" chapter of the Cisco IOS Bridging and IBM Networking Configuration Guide. For specific SDLC commands to configure DLSw+ for SDLC, refer to the "LLC2 and SDLC Commands" chapter in this publication.
clear dlsw circuit
To cause all DLSw+ circuits to be closed, use the clear dlsw circuit privileged EXEC command.
clear dlsw circuit [circuit-id]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
A user can specify a circuit ID of a specific circuit to clear rather than clearing all local-switched circuits.
CautionThis command also drops the associated LLC2 session. The command usage should be used with caution and under the advice of a Cisco engineer.
Examples
The following example closes all DLSw+ circuits:
clear dlsw circuitclear dlsw history
To clear all currently inactive circuits from the DLSw+ circuit history, use the clear dlsw history privileged EXEC command.
clear dlsw history
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears all inactive circuits from the DLSW+ circuit history:
clear dlsw historyclear dlsw local-circuit
To cause all locally-switched DLSw+ circuits to be closed, use the clear dlsw local-circuit privileged EXEC command.
clear dlsw local-circuit [circuit-id]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
A user can specify a circuit ID of a specific circuit to clear rather than clearing all local-switched circuits.
Caution
Examples
The following example closes the locally-switched DLSw+ circuit with ID number 100:
clear dlsw local-circuit 100clear dlsw reachability
To remove all entries from the DLSw+ reachability cache, use the clear dlsw reachability privileged EXEC command.
clear dlsw reachability
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command does not affect existing sessions.
Examples
The following example removes all entries from the DLSw+ reachability cache:
clear dlsw reachabilityclear dlsw statistics
To reset to zero the number of frames that have been processed in the local, remote, and group cache, use the clear dlsw statistics privileged EXEC command.
clear dlsw statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example resets to zero the number of frames in the local, remote, and group cache:
clear dlsw statisticsclear dlsw transparent
To clear DLSw+ transparent local MAC entries, use the clear dlsw transparent privileged EXEC command.
clear dlsw transparent
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is designed to be used in networks that employ DLSw+ Ethernet redundancy without transparent mappings.
Examples
The following example clears DLSw+ transparent local MAC entries:
clear dlsw transparentdlsw allroute-netbios
To change the single-route explorer to an all-route broadcast for NetBIOS, use the dlsw allroute-netbios global configuration command. To return to the default single-route explorer, use the no form of this command.
dlsw allroute-netbios
no dlsw allroute-netbios
Syntax Description
This command has no arguments or keywords.
Defaults
Single-route explorer
Command Modes
Global configuration
Command History
Examples
The following example specifies all-route broadcasts for NetBIOS:
dlsw allroute-netbiosdlsw allroute-sna
To change the single-route explorer to an all-route broadcast for SNA, use the dlsw allroute-sna global configuration command. To return to the default single-route explorer, use the no form of this command.
dlsw allroute-sna
no dlsw allroute-sna
Syntax Description
This command has no arguments or keywords.
Defaults
Single-route explorer
Command Modes
Global configuration
Command History
Examples
The following example specifies all-route broadcasts for SNA:
dlsw allroute-snadlsw bgroup-list
To map traffic on the local Ethernet bridge group interface to remote peers, use the dlsw bgroup-list global configuration command. To cancel the map, use the no form of this command.
dlsw bgroup-list list-number bgroups number
no dlsw bgroup-list
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Traffic received from a remote peer is forwarded only to the bridge group specified in the bridge group list. Traffic received from a local interface is forwarded to peers if the input bridge group number appears in the bridge group list applied to the remote peer definition. The definition of a bridge group list is optional. Each remote peer has a single list number associated with it; therefore, if you want traffic to go to a bridge group and to either a ring list or port list, you should specify the same list number in each definition.
Examples
The following example configures bridge-group list 1:
dlsw bgroup-list 1 bgroups 33Related Commands
Links DLSw+ to the bridge group of the Ethernet LANs.
Configures a ring list, mapping traffic on a local interface to remote peers.
dlsw bridge-group
To link DLSw+ to the bridge group of the Ethernet LANs, use the dlsw bridge-group global configuration command. To disable the link, use the no form of this command.
dlsw bridge-group group-number [llc2 [N2 number] [ack-delay-time milliseconds] [ack-max number] [idle-time milliseconds] [local-window number] [t1-time milliseconds] [tbusy-time milliseconds] [tpf-time milliseconds] [trej-time milliseconds] [txq-max number] [xid-neg-val-time milliseconds] [xid-retry-time milliseconds]] [locaddr-priority lu address priority list number] [sap-priority priority list number]
no dlsw bridge-group group-number [llc2 [N2 number] [ack-delay-time milliseconds] [ack-max number] [idle-time milliseconds] [local-window number] [t1-time milliseconds] [tbusy-time milliseconds] [tpf-time milliseconds] [trej-time milliseconds] [txq-max number] [xid-neg-val-time milliseconds] [xid-retry-time milliseconds]] [locaddr-priority lu address priority list number ] [sap-priority priority list number]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guideliness
More than one bridge group can be attached to DLSw+ by using this command multiple times. Multiple bridge group support is available in Cisco IOS Release 11.3.
Examples
The following example links DLSw+ to bridge groups 1, 2, and 3:
dlsw local-peer peer-id 1.1.1.1dlsw remote-peer 0 tcp 2.2.2.2dlsw bridge-group 1dlsw bridge-group 2dlsw bridge-group 3interface Ethernet0bridge-group 1interface Ethernet1bridge-group 2interface Ethernet2bridge-group 3bridge 1 protocol ieeebridge 2 protocol ieeebridge 3 protocol ieeeRelated Commands
dlsw cache-ignore-netbios-datagram
To prevent DLSw from caching NetBIOS names when a datagram (0x08) NetBIOS command is received, use the dlsw cache-ignore-netbios-datagram global configuration command. To remove the filter, use the no form of this command.
dlsw cache-ignore-netbios-datagram
no dlsw cache-ignore-netbios-datagram
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Examples
The following example helps maintain a smaller name cache:
dlsw cache-ignore-netbios-datagramdlsw disable
To disable DLSw+ without altering the configuration, use the dlsw disable global configuration command. To reenable DLSw+, use the no form of this command.
dlsw disable
no dlsw disable
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Examples
The following example reenables DLSw+:
no dlsw disabledlsw duplicate-path-bias
To specify how DLSw+ handles duplicate paths to the same Media Access Control (MAC) address or NetBIOS name, use the dlsw duplicate-path-bias global configuration command. To return to the default (fault-tolerance), use the no form of this command.
dlsw duplicate-path-bias [load-balance]
no dlsw duplicate-path-bias [load-balance]
Syntax Description
Defaults
Fault-tolerance is the default logic used to handle duplicate paths.
Command Modes
Global configuration
Command History
Usage Guidelines
A path is either a remote peer or a local port.
In full-tolerance mode, the preferred path is always used unless it is unavailable. The preferred path is either the path over which the first response to an explorer was received, or, in the case of remote peers, the peer with the least cost.
Examples
The following example specifies load balancing to resolve duplicate paths:
dlsw duplicate-path-bias load-balancedlsw explorerq-depth
To establish queue depth for multiple queues that handle various types of explorer traffic, including SNA and NetBIOS frames, use the dlsw explorerq-depth global configuration command. To remove the queues, use the no form of this command.
dlsw explorerq-depth {sna value | netbios value | other value}
no dlsw explorerq-depth {sna value | netbios value | other value}
Syntax Description
Defaults
The default value for the sna queue and netbios queue is unlimited (that is, if no value is specified, there is no threshold for these queues). The default for the other queue is 100.
Command Modes
Global configuration
Command History
10.3
This command was introduced.
11.3 (1)
This command was removed from Cisco IOS software.
12.1 (3)T
This command was re-introduced to the Cisco IOS software.
Usage Guidelines
The dlsw explorererq-depth command allows DLSw+ to establish queue depth for multiple queues that handle different types of traffic, including SNA and NetBIOS frames. UI frames are handled by the other queue. Using multiple queues, the SNA and NetBIOS frames will take priority over the UI frames. The UI frames will be dropped when the other queue reaches its threshold.
The dlsw explorererq-depth command is used in an Ethernet and transparent-bridging environment.
Examples
The following example specifies the maximum number of explorers allowed in the SNA queue:
dlsw explorerq-depth sna 100Related Commands
dlsw group-cache disable
To disable the border peer caching feature, use the dlsw group-cache disable global configuration command. To return to the default peer caching feature, use the no form of this command.
dlsw group-cache disable
no dlsw group-cache disable
Syntax Description
This command has no arguments or keywords.
Defaults
Border peer caching is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
If a border peer becomes a nonborder peer, then the group cache is automatically deleted.
This command prevents a border peer from learning reachability information from relay responses. This command also prevents a border peer from using local or remote caches to make forwarding decisions.
Examples
The following example disables the group cache:
dlsw group-cache disableRelated Commands
dlsw group-cache max-entries
To limit the number of entries in the group cache, use the dlsw group-cache max entries global configuration command. To return to the default, use the no form of this command.
dlsw group-cache max-entries number
no dlsw group-cache max entries
Syntax Description
number
Maximum number of entries allowed in the group cache. The valid range is 0 through 12000. If the value is set to 0, then there is no limit to the number of entries. The default is 2000.
Defaults
The default setting is 2000.
Command Modes
Global configuration
Command History
Usage Guidelines
Once the number of entries has reached the maximum number specified, if a new entry needs to be added an entry will be removed to make room.
The value set for number applies to both the NetBIOS and SNA group cache.
Examples
The following configuration defines the maximum number of entries allowed in the NetBIOS or SNA group cache as 1800:
dlsw group-cache max-entries 1800Related Commands
dlsw history-log
To enable the DLSw history log, use the dlsw history-log command in global configuration mode. To disable the DLSw history log, use the no form of this command.
dlsw history-log size [connected-only] [ignore-info-frames]
no dlsw history-log
Syntax Description
Defaults
The DLSw history log is enabled with a value of 32 for the size argument.
Command Modes
Global configuration
Command History
11.2
This command was introduced.
12.0(5)T
The command was enabled by default with a value of 32 for the size argument.
Examples
The following example configures the DLSw history log size to 2000 circuits and specifies that history be recorded only for circuits that reach the CONNECTED state:
router(config)# dlsw history-log 2000 connected-onlydlsw icannotreach saps
To configure a list of service access points (SAPs) not locally reachable by the router, use the dlsw icannotreach saps global configuration command. To remove the list, use the no form of this command.
dlsw icannotreach saps sap...
no dlsw icannotreach saps sap...
Syntax Description
Defaults
No lists are configured.
Command Modes
Global configuration
Command History
Usage Guidelines
The dlsw icannotreach saps command causes the local router to send a control vector to its peers during the capabilities exchange, which tells the peers not to send canureach messages to the local router for sessions using those DSAPs. (They are DSAPs from the peer's perspective, and SSAPs from the perspective of the devices attached to the local router.) The effect is that devices attached to the peer will not be able to initiate sessions to devices attached to the local router using the listed DSAPs. Devices attached to the local router, however, will still be able to start sessions with devices on its peers using the listed saps as SSAPs. The reason is that the local router can still send canureach requests to its peers, since no filtering is actually done on the local router. The filtering done by the peers does not prohibit the peers from responding to canureach requests from the local router sending the control vector, only sending canureach requests to the local router.
Examples
The following example specifies that NetBIOS traffic will be denied:
dlsw icannotreach saps F0dlsw icanreach
To configure a resource that is locally reachable by this router, use the dlsw icanreach command in global configuration mode. To remove the resource, use the no form of this command.
dlsw icanreach {mac-exclusive [remote] | netbios-exclusive [remote] | mac-address mac-addr [mask mask] | netbios-name name | saps sap-value}
no dlsw icanreach {mac-exclusive [remote] | netbios-exclusive [remote] | mac-address mac-add [mask mask] | netbios-name name | saps sap-value}
Syntax Description
Defaults
No resources are configured.
Command Modes
Global configuration
Command History
Usage Guidelines
This command can be entered at any time. It causes a capabilities exchange to relay the information to all active peers. By specifying resource names or MAC addresses in this command, you can avoid broadcasts from remote peers that are looking for this resource. By specifying "exclusive" you can avoid broadcasts to this router or any resources. For example, you could configure the front-end processor (FEP) MAC address or corporate site LAN servers in central site routers to avoid any broadcasts over the WAN for these resources.
Configuring the remote keyword gives the NetBIOS workstations and MACs that are local to the router and that are not already defined in the dlsw icanreach netbios-name name and dlsw icanreach mac-address mac-addr commands access to remote NetBIOS servers and remote MAC addresses. The connection must be from the local Netbios workstation or MAC address to the remote Netbios Server or MAC address.
In the default case (where the remote keyword is not specified), a local NetBIOS station that is not configured in the icanreach netbios-name list will not be able to make a connection in this router over data-link switching plus (DLSw+), whether incoming or outgoing.
Note
Examples
The following example indicates that this peer has information only has information about a single NetBIOS server, and that no peers should send this peer explorers searching for other NetBIOS names. Because the remote option is also configured, NetBIOS workstations that are connected to the NetBIOS server named lanserv will be able to establish a DLSw+ connection:
dlsw icanreach netbios-exclusivedlsw icanreach netbios-name lanservRelated Commands
show dlsw capabilities
Displays the configuration of a specific peer or all peers.
dlsw llc2 nornr
To prevent the receiver not ready (RNR) message from being sent while establishing an LLC2 connection, use the dlsw llc2 nornr global configuration command. To return to the default, use the no form of this command.
dlsw llc2 nornr
no dlsw llc2 nornr
Syntax Description
This command has no arguments or keywords.
Defaults
The command is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used when any device does not handle the LLC2 RNR frames.
Examples
The following example keeps the receiver not ready message from being sent when establishing an LLC2 connection.
dlsw llc2 nornrThe following is output from a Sniffer trace showing when it would be appropriate to use the dlsw llc2 nornr command because the RNR message is being rejected from the FEP when the router is trying to establish an LLC2 connection:
SUMMARY Delta T From 400020401003 From 4000234910268 0.173 LLC C D=00 S=04 TEST P9 0.003 LLC R D=04 S=00 TEST F10 0.002 SNA XID Fmt 2 T411 0.059 SNA XID Fmt 2 T412 0.004 SNA XID Fmt 2 T413 0.065 SNA XID Fmt 2 T414 0.005 SNA XID Fmt 2 T416 0.054 LLC C D=04 S=04 SABME P17 0.003 LLC R D=04 S=04 UAThe router sends a receiver not ready message:
18 0.001 LLC C D=04 S=04 RNR NR=0From frames 19 to 35, the FEP does not respond:
19 0.002 LLC C D=04 S=04 RR NR=020 0.048 SNA C NC NC-ER-OP21 0.997 LLC C D=04 S=04 RR NR=0 P22 1.000 LLC C D=04 S=04 RR NR=0 P24 1.000 LLC C D=04 S=04 RR NR=0 P25 1.000 LLC C D=04 S=04 RR NR=0 P31 1.000 LLC C D=04 S=04 RR NR=0 P32 1.000 LLC C D=04 S=04 RR NR=0 P34 1.000 LLC C D=04 S=04 RR NR=0 P35 1.000 LLC C D=04 S=04 RR NR=0 PThe router disconnects the circuit:
37 1.000 LLC C D=04 S=04 DISC P38 0.002 LLC R D=04 S=04 UA FThe sequence repeats:
39 0.179 LLC C D=00 S=04 TEST P41 0.767 SNA XID Fmt 2 T442 0.634 SNA XID Fmt 2 T443 0.173 LLC C D=00 S=04 TEST44 0.003 LLC R D=04 S=00 TEST F45 0.002 SNA XID Fmt 2 T446 0.060 SNA XID Fmt 2 T447 0.004 SNA XID Fmt 2 T448 0.063 SNA XID Fmt 2 T449 0.005 SNA XID Fmt 2 T4dlsw load-balance
To enable load balancing and to select either round robin or circuit-count-based load balancing, use the dlsw load-balance global configuration command. To disable the previous assignments, use the no form of this command.
dlsw load-balance [round-robin | circuit-count circuit weight]
no dlsw load-balance [round-robin | circuit-count circuit weight]
Syntax Description
Defaults
Fault-tolerant mode is the default setting. The default value for the circuit weight is 10.
Command Modes
Global configuration
Command History
Usage Guidelines
A circuit is never be taken down and reestablished by the code in an attempt to rebalance the load. The DLSw+ Enhanced Load Balancing feature only changes the decision-making process at the time a new circuit is desired.
The dlsw load-balance command replaces the dlsw duplicate-path-bias load balance command. The latter command continues to be accepted, however, it will be converted to the new command if the configuration is displayed or saved.
Examples
The following example enables the DLSw+ Enhanced Load Balancing feature:
dlsw load -balance circuit-count 10dlsw local-peer
To define the parameters of the DLSw+ local peer, use the dlsw local-peer global configuration command. To cancel the definitions, use the no form of this command.
dlsw local-peer [cluster cluster-id] [peer-id ip-address] [group group] [border] [cost cost] [lf size] [keepalive seconds] [passive] [promiscuous] [biu-segment] [init-pacing-window size] [max-pacing-window size]
no dlsw local-peer [cluster cluster-id] [peer-id ip-address] [group group] [border] [cost cost] [lf size] [keepalive seconds] [passive] [promiscuous] [biu-segment] [init-pacing-window size] [max-pacing-window size]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
When there are multiple peers to a given destination, use the cost keyword to determine which router is preferred and which is capable. The cost keyword only applies in fault tolerance mode.
The biu-segment option is a performance/utilization improvement. If a frame that arrives from a remote peer is too large for the destination station to handle, DLSw+ segments the frame. If you choose to implement this option, you must add the option to both DLSw peer partners.
Examples
The following command defines the local peer IP address and specifies the peer group number for this router:
dlsw local-peer peer-id 10.2.17.1 group 2Related Commands
Specifies how DLSw+ handles duplicate paths to the same MAC address or NetBIOS name.
Displays the configuration of a specific peer or all peers.
dlsw mac-addr
To configure a static MAC address, use the dlsw mac-addr global configuration command. To cancel the configuration, use the no form of this command.
dlsw mac-addr mac-addr {ring ring-number | remote-peer {interface serial number | ip-address ip-address}| rif rif-string | group group}
no dlsw mac-addr mac-addr {ring ring -number| remote-peer {interface serial number | ip-address ip-address}| rif rif-string | group group}
Syntax Description
Defaults
No static MAC address is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
You can statically define resources to prevent the Cisco IOS software from sending explorer frames for the specified resource. For example, you can include the MAC address of a FEP in the configuration for each remote router to eliminate any broadcasts that are searching for a FEP. Alternately, you can specify a single dlsw icanreach statement in the router attached to the FEP indicating the MAC address of the FEP. This information is sent to all remote routers as part of the capabilities exchange.
Note
Examples
The following example maps the static MAC address 1000.5A12.3456 to the remote peer at IP address 10.17.3.2:
dlsw mac-addr 1000.5A12.3456 remote-peer ip-address 10.17.3.2Related Commands
dlsw max-multiple-rifs
To enable caching of multiple RIFs per interface, use the dlsw max-multiple-rifs global configuration command. To turn off the feature, use the no form of this command.
dlsw max-multiple-rifs multiple-rifs-per-port
no dlsw max-multiple-rifs multiple-rifs-per-port
Syntax Description
multiple-rifs-per-port
Number of multiple RIF entries per interface. The valid range is 1 to 4. The default value is 1.
Defaults
The default value is 1.
Command Modes
Global configuration
Command History
Usage Guidelines
A MAC address or NetBIOS name can have several RIF entries. Prior to this command, DLSw+ could cache only one of these RIF entries per local Token Ring port. With the dlsw max-multiple-rifs command configured, however, DLSw+ can cache multiple RIF entries (up to 4) for a specific MAC address or NetBIOS name on one Token Ring port.
If the value 1 is specified, multiple RIF caching is not enabled.
Examples
The following example enables the router to cache up to 2 RIFs per interface:
dlsw max-multiple-rifs 2dlsw multicast
To enable a DLSw router to participate in a multicast group, use the dlsw multicast command in global configuration mode. To remove the router from the multicast group, use the no form of this command.
dlsw multicast [multicast-ip-address]
no dlsw multicast [multicast-ip-address]
Syntax Description
multicast-ip-address
(Optional) The IP address used by the multicast group. The default is 224.0.10.0.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
In order for routers to be able to receive multicast traffic through DLSw, they must be properly configured to receive multicasts. The appropriate multicast configuration will depend on the specific topologies used.
The dlsw multicast command is implemented together with the DLSw version 2 support (RFC2166). It allows anybody-to-anybody communication without configuring a full mesh of the DLSw peers.
Examples
The following example configures a router to be part of the multicast group using 224.0.11.0 as the multicast address:
dlsw local-peer peer-id 172.18.62.11 promiscuousdlsw multicast 224.0.11.0dlsw netbios-cache-length
To customize the number of characters of a NetBIOS name that are retained in the cache, use the dlsw netbios-cache-length command in global configuration mode. To restore the default cache length, use the no form of this command.
dlsw netbios-cache-length [15 | 16]
no dlsw netbios-cache-length
Syntax Description
15
The first 15 characters of NetBIOS names are cached.
16
The full 16 characters of NetBIOS names are cached.
Defaults
The first 15 characters of NetBIOS names are cached.
Command Modes
Global configuration
Command History
Usage Guidelines
Configure the cache length to 16 characters only if the router will be dealing with NetBIOS names that differ only in the 16th byte.
Examples
The following example configures the cache to retain the full 16 characters of the NetBIOS name:
router(config)# dlsw netbios-cache-length 16The following comand restores the default behavior of caching only the first 15 characters of the NetBIOS name:
router(config)# no dlsw netbios-cache-lengthdlsw netbios-keepalive-filter
To enable the NetBIOS dial-on-demand routing (DDR) feature, use the dlsw netbios-keepalive-filter command in global configuration mode. To turn off the feature, use the no form of this command.
dlsw netbios-keepalive-filter
no dlsw netbios-keepalive-filter
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
The dlsw netbios-keepalive-filter command filters out NetBIOS session keepalive packets. DLSw+ treats these keepalive packets as data, and thus keeps DDR circuits (such as ISDN) up, even if no traffic is on the circuit. This command is also useful in X.25 networks where the user must pay for every X.25 call or packet. In such cases, the dlsw netbios-keepalive-filter command eliminates keepalive traffic, which is nonessential.
Refer to the "Cisco IOS Bridging and IBM Networking Overview" chapter of the Cisco IOS Bridging and IBM Networking Configuration Guide for more details on the NetBIOS DDR feature.
Examples
The following example enables NetBIOS DDR:
dlsw netbios-keepalive-filterdlsw netbios-name
To configure a static NetBIOS name, use the dlsw netbios-name global configuration command. To cancel the configuration, use the no form of this command.
dlsw netbios-name netbios-name {ring ring-number | remote-peer {interface serial number | ip-address ip-address}| rif rif-string | group group}
no dlsw netbios-name netbios-name {ring ring-number | remote-peer {interface serial number | ip-address ip-address}| rif rif-string | group group}
Syntax Description
Defaults
No static NetBIOS name is configured.
Command Modes
Global configuration
Command History
Note
Examples
The following example configures a static NetBIOS name and links it to group 3:
dlsw netbios-name netname group 3Related Commands
dlsw peer-log-changes
To enable the logging of Syslog messages related to DLSw peer state changes, use the dlsw peer-log-changes global configuration command. To disable the logging of Syslog messages related to DLSw peer state changes, use the no form of this command.
dlsw peer-log-changes [extend]
no dlsw peer-log-changes
Syntax Description
extend
(Optional) Enables more verbose logging of messages, beyond the basic connection and disconnection messages.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
When the dlsw peer-log-changes command is enabled, Syslog messages are generated for the following events:
•
•
•
When the extended keyword is enabled, Syslog messages are also generated for the following events:
•
•
•
•
•
Examples
The following example enables verbose logging of Syslog messages related to DLSw peer state changes:
Router(config)# dlsw peer-log-changes extendeddlsw peer-on-demand-defaults
To configure defaults for peer-on-demand transport, use the dlsw peer-on-demand-defaults global configuration command. To disable the previous assignment, use the no form of this command.
dlsw peer-on-demand-defaults [fst] [bytes-netbios-out bytes-list-name] [cost cost] [dest-mac destination-mac-address] [dmac-output-list access-list-number] [host-netbios-out host-list-name] [inactivity minutes] [keepalive seconds] [lf size] [lsap-output-list list] [port-list port-list-number] [priority] [rsvp {global | average-bit-rate maximum burst}] [tcp-queue-max]
no dlsw peer-on-demand-defaults [fst] [bytes-netbios-out bytes-list-name] [cost cost] [dest-mac destination-mac-address] [dmac-output-list access-list-number] [host-netbios-out host-list-name] [inactivity minutes] [keepalive seconds] [lf size] [lsap-output-list list] [port-list port-list-number] [priority] [rsvp {global | average-bit-rate maximum burst}] [tcp-queue-max]
Syntax Description
Defaults
The default peer-on-demand transport is TCP. The default cost is 3. The default inactivity is 600 seconds. The default keepalive is 30 seconds.The default priority state is off.
Command Modes
Global configuration
Command History
Usage Guidelines
A peer-on-demand peer is a non-configured remote-peer that was connected because of an LLC2 session established through a border peer DLSw+ network.
Setting the average-bit-rate and maximum burst values to 0 disables the RSVP bandwidth reservation for the peer connections.
Examples
The following example configures FST for peer-on-demand transport:
dlsw peer-on-demand-defaults fstRelated Commands
dlsw port-list
To map traffic on a local interface (Token Ring or serial) to remote peers, use the dlsw port-list global configuration command. To disable the previous map assignment, use the no form of this command.
dlsw port-list list-number type number
no dlsw port-list list-number type number
Syntax Description
list-number
Port list number. The valid range is 1 to 255.
type
Interface type.
number
Interface number.
Defaults
No port list is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
Traffic received from a remote peer is forwarded only to the ports specified in the port list. Traffic received from a local interface is forwarded to peers if the input port number appears in the port list applied to the remote peer definition. The definition of a port list is optional.
Examples
The following example configures a DLSw peer port list for Token Ring interface 1:
dlsw port-list 3 token ring 1Related Commands
Maps traffic on the local Ethernet bridge group interface to remote peers.
Configures a ring list, mapping traffic on a local interface to remote peers.
dlsw prom-peer-defaults
To configure defaults for promiscuous transport, use the dlsw prom-peer-defaults global configuration command. To disable the previous assignment, use the no form of this command.
dlsw prom-peer-defaults [fst] [bytes-netbios-out bytes-list-name] [cost cost] [dest-mac destination-mac-address] [dmac-output-list access-list-number] [host-netbios-out host-list-name] [keepalive seconds] [lf size] [lsap-output-list list] [rsvp {global | learn | [average-bit-rate maximum burst]}] [tcp-queue-max size]
no dlsw prom-peer-defaults [fst] [bytes-netbios-out bytes-list-name] [cost cost] [dest-mac destination-mac-address] [dmac-output-list access-list-number] [host-netbios-out host-list-name] [keepalive seconds] [lf size] [lsap-output-list list] [rsvp {global | learn | [average-bit-rate maximum burst]}] [tcp-queue-max size]
Syntax Description
Defaults
The default prom-peer transport is TCP.
The default cost is 3.
The default keepalive value is 30 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines-
A prom-peer is a peer not configured as a remote-peer on this DLSw+ device, but which initiated a peer connection which was accepted because promiscuous peering was enabled.
Setting the average-bit-rate and maximum burst values to 0 disables the RSVP bandwidth reservation for non-configured remote peers.
Examples
The following example configures cost for promiscuous peers:
dlsw prom-peer-defaults cost 4Related Commands
dlsw redundant-rings
To eliminate caching problems and explorer looping when multiple DLSw+ peers are connected to a single Token Ring LAN where the virtual ring numbers configured in those DLSw+ routers are different, use the dlsw redundant-rings global configuration command. To disable the previous settings, use the no form of this command.
dlsw redundant-rings [ring]...
no dlsw redundant-rings [ring]...
Syntax Description
ring
(Optional) Virtual ring number. You can configure up to 10 redundant rings, separated by spaces.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Examples
The following example configures router milan so that the redundant virtual ring 300 should drop any explorer that is sourced from ring number 300. Similarly, router madrid knows that 300 is a redundant ring and any explorer sourced from ring 300 should be dropped.
milan# dlsw redundant-rings 300madrid# dlsw redundant-rings 300dlsw remote-peer frame-relay
To specify the remote peer with which the router will connect, use the dlsw remote-peer frame-relay global configuration command. To disable the previous assignments, use the no form of this command.
dlsw remote-peer list-number frame-relay interface serial number dlci-number [backup-peer [ip-address | frame-relay interface serial number dlci-number | interface name | circuit-inactivity minutes]] [bytes-netbios-out bytes-list-name] [circuit-weight weight] [cost cost] [dest-mac mac-address] [dmac-output-list access-list-number] [host-netbios-out host-list-name] [keepalive seconds] [lf size] [linger minutes] [lsap-output-list list] [passive] pass-thru
no dlsw remote-peer list-number frame-relay interface serial number dlci-number [backup-peer [ip-address | frame-relay interface serial number dlci-number | interface name | circuit-inactivity minutes]] [bytes-netbios-out bytes-list-name] [circuit-weight weight] [cost cost] [dest-mac mac-address] [dmac-output-list access-list-number] [host-netbios-out host-list-name] [keepalive seconds] [lf size] [linger minutes] [lsap-output-list list] [passive] pass-thru
Syntax Description
Defaults
No remote peers are specified.
The linger default is 5 minutes.
The pass-thru default is local acknowledgement mode.
Command Modes
Global configuration
Command History
Usage Guidelines
The following keywords and arguments first appeared in Cisco IOS Release 11.2: The cost keyword specified in a remote peer statement takes precedence over the cost learned as part of the capabilities exchange with the remote peer. The cost keyword is relevant only in fault tolerance mode.
When you need to permit access to only a single MAC address, the dest-mac option is a shortcut over the dmac-output-list option.
When pass-thru is not specified, traffic will be locally acknowledged and reliably transported in LLC2 across the WAN.
The following keywords and arguments first appeared in Cisco IOS Release 12.2:
The backup-peer circuit-inactivity is only configurable in tandem with the backup-peer command for TCP or LLC2 peers.
Examples
The following example specifies a DLSw+ Lite peer as a backup to a primary direct peer:
dlsw remote-peer 0 frame-relay interface serial 1 40 pass-thrudlsw remote-peer 0 frame-relay interface serial 0 30 backup-peer frame-relay interface serial 1 40The following example specifies Frame Relay encapsulation connection for remote peer transport:
dlsw remote-peer 0 frame-relay interface 0 30The following example specifies Remote Peer Backup Peer circuit-inactivity linger before termination:dlsw local-peer peer-id 10.1.1.3dlsw remote-peer 0 tcp 10.1.1.1dlsw remote-peer 0 tcp 10.1.1.2 backup-peer 10.1.1.1 linger 20circuit-inactivity 3Related Commands
dlsw remote-peer fst
To specify an FST encapsulation connection for remote peer transport, use the dlsw remote-peer fst global configuration command. To disable the previous FST assignments, use the no form of this command.
dlsw remote-peer list-number fst ip-address [backup-peer [ip-address | frame-relay interface serial number dlci-number | interface name]] [bytes-netbios-out bytes-list-name] [cost cost] [dest-mac mac-address] [dmac-output-list access-list-number] [host-netbios-out host-list-name] [keepalive seconds] [lf size] [linger minutes] [lsap-output-list list] [passive]
no dlsw remote-peer list-number fst ip-address [backup-peer [ip-address | frame-relay interface serial number dlci-number | interface name]] [bytes-netbios-out bytes-list-name] [cost cost] [dest-mac mac-address] [dmac-output-list access-list-number] [host-netbios-out host-list-name] [keepalive seconds] [lf size] [linger minutes] [lsap-output-list list] [passive]
Syntax Description
Defaults
No FST encapsulation connection is specified.
The linger default is 5 minutes.
Command Modes
Global configuration
Command History
10.3
This command was introduced.
11.2
The following keywords and arguments were added:
•
•
•
Usage Guidelines
The cost keyword specified in a remote peer statement takes precedence over the cost learned as part of the capabilities exchange with the remote peer. The cost keyword is relevant only in fault tolerance mode.
When you need to permit access to a single MAC address, the dest-mac option is a shortcut over the dmac-output-list option.
Examples
The following example specifies an FST peer as backup to a primary TCP peer:
dlsw remote-peer 0 tcp 10.2.18.1dlsw remote-peer 1 fst 10.2.17.8 backup-peer 10.2.18.1The following example specifies an FST encapsulation connection for remote peer transport:
dlsw remote-peer 1 fst 10.2.17.8The following example specifies Remote Peer Backup Peer circuit-inactivity linger before termination:
dlsw local-peer peer-id 10.1.1.3dlsw remote-peer 0 tcp 10.1.1.1dlsw remote-peer 0 tcp 10.1.1.2 backup-peer 10.1.1.1 linger 20circuit-inactivity 3Related Commands
dlsw remote-peer interface
To specify a point-to-point direct encapsulation connection, use the dlsw remote-peer interface global configuration command. To disable previous interface assignments, use the no form of this command.
dlsw remote-peer list-number interface serial number [backup-peer [ip-address | frame-relay interface serial number dlci-number | interface name | circuit-inactivity minutes]] [bytes-netbios-out bytes-list-name] [cost cost] [dest-mac mac-address] [dmac-output-list access-list-number] [host-netbios-out host-list-name] [keepalive seconds] [lf size] [linger minutes] [lsap-output-list list] [passive] [pass-thru]
no dlsw remote-peer list-number interface serial number [backup-peer [ip-address | frame-relay interface serial number dlci-number | interface name | circuit-inactivity minutes]] [bytes-netbios-out bytes-list-name] [cost cost] [dest-mac mac-address] [dmac-output-list access-list-number] [host-netbios-out host-list-name] [keepalive seconds] [lf size] [linger minutes] [lsap-output-list list] [passive] [pass-thru]
Syntax Description
Defaults
No point-to-point direct encapsulation connection is specified.
The linger default is 5 minutes.
The pass-thru default is local acknowledgment mode.
Command Modes
Global configuration
Command History
Usage Guidelines
The cost keyword specified in a remote peer statement takes precedence over the cost learned as part of the capabilities exchange with the remote peer. The cost keyword is relevant only in fault tolerance mode.
When you need to permit access to a single MAC address only, the dest-mac option is a shortcut over the dmac-output-list option.
Examples
The following example specifies a point-to-point direct peer backup to a primary direct peer:
dlsw remote-peer 0 interface serial 1 pass-thrudlsw remote-peer 1 interface serial 2 pass-thru backup-peer interface serial 1The following example specifies a point-to-point direct encapsulation connection for remote peer transport:
dlsw remote-peer 1 interface serial 2 pass-thruThe following example specifies Remote Peer Backup Peer circuit-inactivity linger before termination:
dlsw local-peer peer-id 10.1.1.3dlsw remote-peer 0 tcp 10.1.1.1dlsw remote-peer 0 tcp 10.1.1.2 backup-peer 10.1.1.1 linger 20circuit-inactivity 3Related Commands
dlsw remote-peer tcp
To identify the IP address of a peer with which to exchange traffic using TCP, use the dlsw remote-peer tcp global configuration command. To remove a remote peer, use the no form of this command.
dlsw remote-peer list-number tcp ip-address [backup-peer [ip-address | frame-relay interface serial number dlci-number | interface name | circuit-inactivity minutes]] [bytes-netbios-out bytes-list-name] [cluster cluster-id] [circuit-weight value] [cost cost] [dest-mac mac-address] dmac-output-list access-list-number] [dynamic] [host-netbios-out host-list-name] [inactivity minutes] [dynamic] [keepalive seconds] [lf size] [linger minutes] [lsap-output-list list] [no-llc minutes] [passive] [priority] [rif-passthru virtual-ring-number] [rsvp {global | average-bit-rate maximum burst}] [tcp-queue-max size] [timeout seconds]
no dlsw remote-peer list-number tcp ip-address [backup-peer [ip-address | frame-relay interface serial number dlci-number | interface name | circuit-inactivity minutes]] [bytes-netbios-out bytes-list-name] [cluster cluster-id] [circuit-weight value] [cost cost] [dest-mac mac-address] [dmac-output-list access-list-number] [dynamic] [host-netbios-out host-list-name] [inactivity minutes] [dynamic] [keepalive seconds] [lf size] [linger minutes] lsap-output-list list] [no-llc minutes] [passive] [priority] [rif-passthru virtual-ring-number] [rsvp {global | average-bit-rate maximum burst}] [tcp-queue-max size] [timeout seconds]
Syntax Description
Defaults
No peer IP address is identified.
The dynamic option is not on by default. If the dynamic option is added without either the inactivity or no-llc argument specified, the default is to terminate the TCP connection to the remote peer after 5 minutes of no active LLC2 connection.
The inactivity default is 5 minutes.
The no-llc default is 5 minutes.
The timeout default is 90 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
SNA DDR technology allows switched links to be closed during idle periods. To enable this feature, set the keepalive option to 0 and configure the timeout option. When the dynamic option is configured, the keepalive option is automatically set to 0.
To enhance DDR cost-savings, you can configure the TCP connection to a remote peer to be dynamically established (that is, established only when there is DLSw data to send). You can further configure the TCP connection to terminate after a specified period of idle time on the peer or after a specified period of no active LLC sessions on the peer.
You cannot use both no-llc and inactivity in a command specifying a dynamic peer.
When you need to permit access to a single MAC address, the dest-mac option is a shortcut over the dmac-output-list option.
Use the linger option to specify that a backup peer will remain connected for a specified period of time after the primary connection is reestablished. Setting the linger option to 0 causes sessions connected to the backup peer to drop immediately when the primary peer recovers. If the linger option is omitted, all sessions connected to the backup peer remain active until they terminate on their own.
When the priority option on the dlsw remote-peer command is configured, DLSw+ automatically activates four TCP ports to that remote peer (ports 2065, 1981, 1982 and 1983) and assigns traffic to specific ports. Furthermore, if APPN is running with DLSw+ and you specify the priority option on the dlsw remote-peer command, then the SNA ToS will map APPN class of service (COS) to TCP ToS and will preserve the APPN COS characteristics throughout the network.
The rif passthru option works only on Token Ring LANs via SRB. Other LAN types, such as SDLC and QLLC, are not supported. The RIF Passthru feature is supported with TCP encapsulation and it disables local acknowledgment.
The following features are not supported with the DLSw+ RIF Passthru feature:
•
•
•
•
The cluster keyword is available only on border peers.This option enables the DLSw+ Peer Clusters feature without forcing every DLSw+ router in the network to upgrade their software.
Setting the average-bit-rate or maximum burst to 0 turns off RSVP for this peer.
Examples
The following example specifies a TCP encapsulation connection for remote peer transport:
dlsw remote-peer 0 tcp 10.2.17.8The following example specifies a TCP peer as backup to a primary FST peer:
dlsw remote-peer 0 fst 10.2.18.9dlsw remote-peer 0 tcp 10.2.17.8 backup-peer 10.2.18.9Related Commands
dlsw ring-list
To configure a ring list, mapping traffic on a local interface to remote peers, use the dlsw ring-list global configuration command. To cancel the definition, use the no form of this command.
dlsw ring-list list-number rings ring-number
no dlsw ring-list list-number rings ring-number
Syntax Description
list-number
Ring list number. The valid range is 1 to 255.
rings
Specify one or more physical or virtual rings.
ring-number
Physical or virtual ring number. The valid range is 1 to 4095.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Traffic received from a remote peer is forwarded only to the rings specified in the ring list. Traffic received from a local interface is forwarded to peers if the input ring number appears in the ring list applied to the remote peer definition. The definition of a ring list is optional.
Examples
The following example configures a DLSw ring list, assigning rings 1, 2, and 3 to ring list 3:
dlsw ring-list 3 rings 1 2 3Related Commands
dlsw rsvp
To enable the DLSw+ RSVP Bandwidth Reservation feature on the local peer, use the dlsw rsvp global configuration command. To disable the DLSw+ RSVP Bandwidth Reservation feature for all peers in the router, use the no form of this command.
dlsw rsvp {default | [average-bit-rate maximum-burst]}
no dlsw rsvp {default | [average-bit-rate maximum-burst]}
Syntax Description
Defaults
The default values for the average-bit-rate and maximum-burst are 10 kbps and 28 kBps, respectively.
Command Modes
Global configuration
Command History
Usage Guidelines
The DLSw+ RSVP Bandwidth Reservation feature does not require that all peers in a network have RSVP configured. However, the feature does require that the end peer devices are configured with RSVP and that all devices in the middle are IP RSVP capable.
The default value assumes that the DLSw+ peer is connected via a 56 kbps link. If this is not the case, then the default values will likely not produce optimal results. Even if the line speed is 56 kbps, the default values (10 kbps average-bit-rate and 28 kBps maximum-burst) may not be optimal in a particular network environment and should be changed accordingly.
Setting the average-bit-rate or maximum-burst to 0 turns off RSVP for this peer.
Examples
The following example configures the DLSw+ RSVP Bandwidth Reservation feature with an average-bit-rate of 10 kbps and a maximum-burst of 28 kBps:
dlsw rsvp defaultRelated Commands
dlsw timer
To tune an existing configuration parameter, use the dlsw timer global configuration command. To restore the default parameters, use the no form of this command.
dlsw timer {icannotreach-block-time | netbios-cache-timeout | netbios-explorer-timeout | netbios-group-cache | netbios-retry-interval | netbios-verify-interval | sna-cache-timeout | explorer-delay-time | sna-explorer-timeout | explorer-wait-time | sna-group-cache | sna-retry-interval | sna-verify-interval} time
no dlsw timer {icannotreach-block-time | netbios-cache-timeout | netbios-explorer-timeout | netbios-group-cache | netbios-retry-interval | netbios-verify-interval | sna-cache-timeout | explorer-delay-time | sna-explorer-timeout | explorer-wait-time | sna-group-cache | sna-retry-interval | sna-verify-interval} time
Syntax Description
Defaults
The icannotreach-block-time default is 0 (disabled).
The netbios-cache-timeout default is 960 seconds (16 minutes).
The netbios-explorer-timeout default is 6 seconds.
The netbios-group-cache default is 240 seconds (4 minutes).
The netbios-retry-interval default is 1 second.
The netbios-verify-interval default is 240 seconds (4 minutes).
The sna-cache-timeout default is 960 seconds (16 minutes).
The explorer-delay-time default is 0.
The sna-explorer-timeout default is 180 seconds (3 minutes).
The explorer-wait-time default is 0.
The sna-group-cache default is 240 seconds (4 minutes).
The sna-retry-interval default is 30 seconds.
The sna-verify-interval default is 240 seconds (4 minutes).
Command Modes
Global configuration
Command History
Usage Guidelines
The netbios-group-cache and sna-group-cache options were added to this command for the border peer caching feature.
Examples
The following configuration defines the length of time that an entry will stay in the group cache as 120 seconds (2 minutes):
dlsw timers sna-group-cache 120The following example configures the length of time that an SNA MAC location cache entry exists before it is discarded:
dlsw timer sna-cache-timeout 3dlsw tos disable
To disable any ToS bits in DLSw+ generated packets, use the dlsw tos disable global configuration command. To return to the default, use the no form of this command.
dlsw tos disable
no dlsw tos disable
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Examples
The following example disables the ToS bits in DLSw+ generated packets:
dlsw tos disabledlsw tos map
To associate a ToS value for priority peers, use the dlsw tos map global configuration command. To return to the default, use the no form of this command.
dlsw tos map [high value [medium value | normal value | low value]]
no dlsw tos map [high value [medium value | normal value | low value]]
Syntax Description
Defaults
The default settings, with priority peers configured, are defined in Table 31.
Command Modes
Global configuration
Usage Guidelines
By default, DLSw+ peer traffic is set to Critical-ECP. When the priority keyword is specified in the dlsw remote peer tcp command, DLSw+ automatically activates four TCP ports to that remote peer (ports 2065, 1981, 1982 and 1983) and associates a priority level. This command enables the user to customize the prioritization of DLSw+ traffic within the network. If priority peers are not configured, however, high is the only option. See Table 31 for corresponding priority levels and options.
Table 31 Priority Levels and Options
01
Routine
11
Priority
2
Immediate
Low
1983
3
Flash
Normal
1982
4
Flash Override
Medium
1981
5
Critical ECP
High
2065
62
Internetwork Control
72
Network Control
1 Using ToS bit values 0 and 1 does not cause negative impact to the network, but these values do not prioritize the traffic.
2 ToS bit values 6 and 7 are not recommended because of potential interference with critical network infrastructure flows.
Examples
The following example changes the default setting on IP packets generated by DLSw+ from high to low:
dlsw tos map low 2The following is an example policy routing configuration that shows how to modify the default setting of TCP port 2065. The configuration changes the default setting on IP packets from network control priority to routine priority.
ip local policy route-map testaccess-list 101 permit tcp any eq 2065 anyaccess-list 101 permit tcp any any eq 2065route-map test permit 20match ip address 101set ip precedence routinedlsw transparent map
To enable MAC address mapping in a switch-based environment, use the dlsw transparent map interface configuration command. To disable MAC address mapping, use the no form of this command.
dlsw transparent map local mac mac address remote mac mac address [neighbor mac address]
no dlsw transparent map local mac mac address remote mac mac address
[neighbor mac address]Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
Only the routers that are connected to the switch are configured for address mapping.
Examples
The following example maps MAC address 4000.1000.1234 to the actual device with the MAC address of 4000.3754.1000 and designates the DLSw+ device with MAC address 0000.0c12.0001 as backup:
dlsw transparent map local-mac 4000.1000.1234 remote mac 4000.3754.1000 neighbor 0000.0c12.0001Related Commands
Enables the special support that is required for the interfaces connected to an Ethernet switch with the dlsw transparent redundancy-enable command configured.
dlsw transparent redundancy-enable
To configure transparent redundancy, use the dlsw transparent redundancy-enable interface configuration command. To disable transparent redundancy, use the no form of this command.
dlsw transparent redundancy-enable multicast-mac-address [master-priority value]
no dlsw transparent redundancy-enable multicast-mac-address [master-priority value]
Syntax Description
Defaults
No default value or behaviors.
The master-priority default is 100.
Command Modes
Interface configuration
Command History
Usage Guidelines
The same multicast-mac-address must be configured on all DLSw+ devices within the same transparent bridged domain. All the DLSw+ devices advertise their presence via frames to this multicast-mac-address.
All routers in the transparent bridged domain compete and elect one master router. The master router is elected based on its master-priority value. In the case of equal master priority setting, the router with the lowest MAC address is the elected master router.
Examples
The following example configures Ethernet Redundancy with a master-priority of 100:
dlsw transparent redundancy-enable 9999.9999.9999 master-priority 100Related Commands
Displays DLSw neighbors in a transparent bridged domain.
Displays the master circuit cache for each transparent bridged domain.
dlsw transparent switch-support
To enable the special support that is required for the interfaces connected to an Ethernet switch with the dlsw transparent redundancy-enable command configured, use the dlsw transparent switch-support global configuration command. To disable DLSW transparent switch support, use the no form of this command.
dlsw transparent switch-support
no dlsw transparent switch-support
Syntax Description
This command has no arguments or keywords.
Defaults
Switch support is off.
Command Modes
Global configuration
Command History
Usage Guidelines
The dlsw transparent switch-support command must be configured before the dlsw transparent map command.
Examples
The following example configures Ethernet switch support:
dlsw transparent switch-supportRelated Commands
dlsw transparent timers
To configure the timeout value the master router waits for all requests for a circuit before giving the permission for a router for a circuit, use the dlsw transparent timers interface configuration command. To disable the timeout value, use the no form of this command.
dlsw transparent timers [netbios value | sna value]
no dlsw transparent timers [netbios value | sna value]
Syntax Description
Defaults
The default NetBIOS value is 400 ms.
The default SNA value is 1000 ms (1 second).
Command Modes
Interface configuration
Command History
Usage Guidelines
The dlsw transparent redundancy-enable command must be configured before the dlsw transparent timers command.
Examples
The following example configures the master router to wait 500 ms for a NetBIOS session before giving or denying permission to a router to create a circuit:
dlsw transparent timers netbios 500Related Commands
dlsw udp-disable
To disable the UDP unicast feature, use the dlsw udp-disable global configuration command. To return to the default UDP unicast feature, use the no form of this command.
dlsw udp-disable
no dlsw udp-disable
Syntax Description
This command has no arguments or keywords.
Defaults
The UDP unicast feature is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
If the dlsw udp-disable command is configured, then a DLSw+ node will not send packets via UDP unicast and will not advertise UDP Unicast support in its capabilities exchange message.
Refer to the "Bridging and IBM Networking Overview" chapter of the Bridging and IBM Networking Configuration Guide for more information on the UDP Unicast feature.
Examples
The following example disables the UDP unicast feature:
dlsw udp-disableqllc dlsw
To enable DLSw+ over Qualified Logical Link Control (QLLC), use the qllc dlsw interface configuration command. To cancel the configuration, use the no form of this command.
qllc dlsw {subaddress subaddress | pvc pvc-low [pvc-high]} [vmac vmacaddr poolsize] [partner partner-macaddr] [sap ssap dsap] [xid xidstring] [npsi-poll]
no qllc dlsw {subaddress subaddress | pvc pvc-low [pvc-high]} [vmac vmacaddr poolsize] [partner partner-macaddr] [sap ssap dsap] [xid xidstring] [npsi-poll]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
Any incoming call whose X.121 destination address matches the router's X.121 address and this subaddress will be dispatched to DLSw+ (with an ID.STN IND). If a router is providing several QLLC services different subaddresses must be used to discriminate between them. Subaddresses can be used even if a remote X.25 device is not explicitly mapped to a specific virtual MAC address. This is most useful when PU 2.1 devices are connecting to a host because the X.25 device's control point name and network name are used to validate the connection, rather than some virtual MAC address. The subaddress is optional. If no subaddress is provided, any incoming call that matches the router's X.121 address will be dispatched to DLSw+. On outgoing calls the subaddress is concatenated to the interface's X.121 address.
When DLSw+ receives a Can You Reach inquiry about a virtual MAC address in the pool, the QLLC code will attempt to set up a virtual circuit to the X.121 address that maps to the virtual MAC address specified. If an incoming call is received, QLLC sends an ID.STN.IND with a virtual MAC address from the pool to DLSw+. If there is no virtual MAC address, then the x25 map qllc or x25 pvc qllc command must provide a virtual MAC address.
The npsi-poll parameter is needed to support PU 2.0 on the partner side that wishes to connect to a FEP on the X.25 side. In a Token Ring or DLSw+ environment the PU 2.0 will send a null XID to the FEP. If the software forwards this null XID to an X.25 attached FEP the FEP will assume that it is connecting to PU2.1, and will break off the connection when the PU 2.0 next send an XID Format 0 Type 2.
Examples
The following commands assign virtual MAC address 1000.0000.0001 to a remote X.25-attached 3174, which is then mapped to the X.121 address of the 3174 (31104150101) in an X.25-attached router:
interface serial 0x25 address 3110212011x25 map qllc 1000.000.0001 31104150101qllc dlsw partner 4000.1161.1234sdlc dlsw
To attach SDLC addresses to DLSw+, use the sdlc dlsw interface configuration command. To cancel the configuration, use the no form of this command.
sdlc dlsw {sdlc-address | default | partner mac-address [inbound | outbound]}
no sdlc dlsw {sdlc-address | default | partner mac-address [inbound | outbound]}
Syntax Description
Defaults
No correspondence is defined between SDLC addresses and DLSw+.
Command Modes
Interface configuration
Command History
Examples
The following command attaches SDLC address d2 to DLSw+:
sdlc dlsw d2The following command attaches SDLC addresses d2, d5, e3, e4, e6, b1, c3, d4, a1 and a5:
sdlc dlsw d2 d5 e3 e4 e6 b1 c3 d4 a1 a5Related Commands
show dlsw capabilities
To display the configuration of a specific peer or all peers, use the show dlsw capabilities command in privileged EXEC mode.
show dlsw capabilities [interface type number | ip-address ip-address | local]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
10.3
This command was introduced.
12.0(7)
The output of this command was modified to include additional fields.
Examples
The following is sample output from the show dlsw capabilities command:
Router# show dlsw capabilitiesDLSw: Capabilities for peer 172.18.62.144(2065)vendor id (OUI) : '00C' (cisco)version number : 2release number : 0init pacing window : 20unsupported saps : nonenum of tcp sessions : 1loop prevent support : noicanreach mac-exclusive : noicanreach netbios-excl. : noreachable mac addresses : nonereachable netbios names : noneV2 multicast capable : yesDLSw multicast address : nonecisco version number : 1peer group number : 0peer cluster support : noborder peer capable : nopeer cost : 3biu-segment configured : noUDP Unicast support : yesFast-switched HPR supp. : noNetBIOS Namecache length : 15local-ack configured : yespriority configured : nocisco RSVP support : noconfigured ip address : 172.18.62.144peer type : confversion string :Cisco Internetwork Operating System SoftwareIOS (tm) c6sup2_rp Software (c6sup2_rp-JSV-M), Experimental Version12.1(20020828:194631) [mbinzer-CSCdw44026-121E 144]Copyright (c) 1986-2002 by cisco Systems, Inc.Compiled Fri 30-Aug-02 00:17 by mbinzerTable 32 describes the significant fields shownin the display.
show dlsw circuits
To display the state of all circuits involving this MAC address as a source and destination, use the show dlsw circuits privileged EXEC command.
show dlsw circuits [detail] [mac-address address | sap-value value | circuit-id]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show dlsw circuits command:
Router# show dlsw circuitsIndex local addr(lsap) remote addr(dsap) state uptime4060086272 4000.0000.0056(F0) 4001.0000.0049(F0) CONNECTED 00:00:13Total number of circuits connected: 1The following is sample output from the show dlsw circuits command with the detail argument:
Router# show dlsw circuits detailIndex local addr(lsap) remote addr(dsap) state uptime194 0800.5a9b.b3b2(F0) 800.5ac1.302d(F0) CONNECTED 00:00:13PCEP: 995AA4 UCEP: A52274Port: To0/0 peer 172.18.15.166(2065)Flow-Control-Tx SQ CW:20, Permitted:28; Rx CW:22, Granted:25 Op:IWOCongestion: LOW(02), Flow Op: Half: 12/5 Reset 1/0RIF = 0680.0011.0640Table 33 describes significant fields shown in the display.
show dlsw circuits history
To display the details of the last status of all DLSW circuits either currently active or not active, use the show dlsw circuits history command in privileged EXEC mode.
show dlsw circuits history [detail] [mac-address address | sap-value value | circuit id]
Syntax Description
Command Default
None
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show dlsw circuits history command keeps the history for the last 32 circuits. For every circuit it stores a maximum of 16 entries.
Examples
The following is a sample output from the show dlsw circuits history command
Router# c7500-1-r443Circuit history kept for last 32 circuits using 4096 bytes:Index local addr(lsap) remote addr(dsap) remote peer1761607680 0000.6666.4242(04) 4000.1000.2000(04) 172.18.62.1983657433089 0000.6666.4242(04) 4000.1000.2000(04) 172.18.62.198 Ckt ActiveThe following is a sample output from the show dlsw circuits history command with the detail argument
Router# show dlsw circuits history detailCircuit history kept for last 32 circuits, using 4096 bytesIndex local addr(lsap) remote addr(dsap) remote peer1761607680 0000.6666.4242(04) 4000.1000.2000(04) 172.18.62.198Created at : 08:19:14.440 EDT Wed Sep 21 2005Connected at : 08:19:14.476 EDT Wed Sep 21 2005Destroyed at : 08:20:21.159 EDT Wed Sep 21 2005Local Corr : 1761607680 Remote Corr: 1962934272Bytes: 633/731 Info-frames: 7/7XID-frames: 4/5 UInfo-frames: 0/0Flags: Remote created, Local connectedLast events:Current State Event Add. Info Next State-------------------------------------------------------------------CONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED WAN halt-noack 0x0 HALT_NOACK_PENDHALT_NOACK_PEND DLC DiscCnf 0x0 CLOSE_PENDCLOSE_PEND DLC DiscInd 0x0 CLOSE_PENDCLOSE_PEND DLC CloseStnCnf 0x0 DISCONNECTED3657433089 0000.6666.4242(04) 4000.1000.2000(04) 172.18.62.198 Ckt ActiveCreated at : 08:20:51.146 EDT Wed Sep 21 2005Connected at : 08:20:51.182 EDT Wed Sep 21 2005Local Corr : 3657433089 Remote Corr: 3137339393Bytes: 633/731 Info-frames: 7/7XID-frames: 4/5 UInfo-frames: 0/0Flags: Remote created, Local connectedLast events:Current State Event Add. Info Next State-------------------------------------------------------------------CONNECT_PENDING WAN contacted 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED DLC ConnectCnf 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED WAN infoframe 0x0 CONNECTEDCONNECTED DLC DataInd 0x0 CONNECTEDThe following is a sample output from the show dlsw circuits history command for specific circuits only
Router# show dlsw circuits history mac-address 0000.6666.4242Circuit history kept for last 32 circuits, using 4096 bytesIndex local addr(lsap) remote addr(dsap) remote peer1761607680 0000.6666.4242(04) 4000.1000.2000(04) 172.18.62.1983657433089 0000.6666.4242(04) 4000.1000.2000(04) 172.18.62.198 Ckt ActiveRouter# c7500-1-r443 mac-address 4000.1000.2000Circuit history kept for last 32 circuits, using 4096 bytesIndex local addr(lsap) remote addr(dsap) remote peer1761607680 0000.6666.4242(04) 4000.1000.2000(04) 172.18.62.1983657433089 0000.6666.4242(04) 4000.1000.2000(04) 172.18.62.198 Ckt Active.
Related Commands
show dlsw circuits
Displays state of all circuits involving a common MAC address as a source and destination.
show dlsw fastcache
To display the fast cache for FST and direct-encapsulated peers, use the show dlsw fastcache privileged EXEC command.
show dlsw fastcache
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show dlsw fastcache command with an FST peer:
Router# show dlsw fastcachepeer local-mac remote-mac l/r sap rifFST 10.2.32.1 0800.5a8f.881c 0800.5a8f.8822 04/04 0680.02D5.1360The following is sample output from the show dlsw fastcache command:
Router# show dlsw fastcachepeer local-mac remote-mac l/r sap rifIF Se1 0800.5a8f.881c 0800.5a8f.8822 F0/F0 0680.02D5.1360Table 35 describes significant fields shown in the display.
show dlsw local-circuit
To display the state of all locally-switched DLSw+ circuits, use the show dlsw local-circuit privileged EXEC command.
show dlsw local-circuit [mac-address address | sap-value value | circuit-id]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show dlsw local-circuit command:
Router# show dlsw local-circuit~ key mac-addr sap state port rif34886696 4000.1111.22c1 04 CONNECTED Se2/0 --no rif--~ PCEP: 2145198 UCEP: 2145428~ 4000.3745.0001 04 CONNECTED DL0 --no rif--~ PCEP: 2176C90 UCEP: 2145428Table 33 describes significant fields shown in the display
show dlsw peers
To display DLSw peer information, use the show dlsw peers privileged EXEC command.
show dlsw peers [interface type number | ip-address ip-address | ssp-dlx [interface type number | ip-address ip-address] | udp]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show dlsw peers command:
Router# show dlsw peers udpPeers: tot-Q'd total-rx total-tx tot-retx tot-drop curr-Q'd TCP uptime1.1.1. 0 23 0 0 0 0 0 00:01:02Total number of connected peers: 2Total number of connections: 8The following is sample output from the show dlsw peers command with a TCP connection:
Router# show dlsw peersPeers: state pkts_rx pkts_tx type drops ckts TCP uptimeTCP 1.1.91.1High priority CONNECT 43 40 conf 0 1 0 00:01:02Medium priority CONNECT 0 0 conf 0 - 0 00:01:02Normal priority CONNECT 4 41 conf 0 - 5 00:01:02Low priority CONNECT 1 0 conf 0 - 0 00:01:02TCP 1.1.93.1High priority CONNECT 3 3 conf 0 0 0 00:00:58Medium priority CONNECT 0 0 conf 0 - 0 00:00:58Normal priority CONNECT 0 0 conf 0 - 0 00:00:58Low priority CONNECT 0 39 conf 0 - 0 00:00:58Total number of connected peers: 2Total number of connections: 8The following is sample output from the show dlsw peers command with a Direct Frame Relay connection:
Router # show dlsw peersPeers: state pkts_rx pkts_tx type drops ckts TCP uptimeIF SE1 16 connect 53 2597 conf 0 - - 00:04:09Total number of connected peers: 2Total number of connections: 8The following is sample output from the show dlsw peers command with a Direct Frame Relay with local acknowledgment (LLC2) connection:
Router # show dlsw peersPeers: state pkts_rx pkts_tx type drops ckts TCP uptimeLLC2 SE1 16 connect 1179 108 conf 0 1 - - 00:04:09Total number of connected peers: 2Total number of connections: 8The following is sample output from the show dlsw peers ssp-dlx command:
Router # show dlsw peers ssp-dlxPeer:1.1.1.6 received transmittedCUR_ex Can U Reach Explorers 5 2CUR_cs Can U Reach Circuit Start 2 5ICR_ex I Can Reach Explorers 4 5ICR_cs I Can Reach Circuit Start 4 1ACK Reach Acknowledgement 1 4XID Frame 22 20CONQ Contact Remote Station 4 0CONR Remote Station Contacted 0 4INFO Information (I) Frame 39 39HLTQ Halt Data Link 0 1HLTR Data Link Halted 1 0HLTN Halt Data Link (no ack) 1 2CAPX Capabilities Exchange 2 2Total SSP Primitives 85 85DLX Peer Test Request 122 146DLX Peer Test Response 146 122DLX Border to Border Message 53 9--> SSP:CUR Can U Reach 53 2--> SSP:DATA Data Frames 0 7Last SSP Received: INFOLast SSP Sent: ICRTotal number of connected peers:1Total number of connections: 1Table 37 describes the significant fields shown in the show dlsw peers command display.
show dlsw reachability
To display DLSw+ reachability information, use the show dlsw reachability privileged EXEC command.
show dlsw reachability [[group [value] | local | remote] | [mac-address [address] [netbios-names [name]]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If none of the group, local, or remote options are specified, then the caches will be displayed in the following order: local, remote, and group.
Examples
The following is sample output from the show dlsw reachability group command:
Router# show dlsw reachability groupDLSw Group MAC address reachability cache listMac Addr Group0000.3072.1070 10DLSW Group NetBIOS Name reachability cache listNetBIOS Name GroupThe following is sample output from the show dlsw reachability command:
Router# show dlsw reachabilityDLSw MAC address reachability cache listMac Addr status Loc. peer/port rif0000.f641.91e8 SEARCHING LOCAL0006.7c9a.7a48 FOUND LOCAL TokenRing0/0 0CB0.0011.3E71.A041.0DE5.06400800.5a4b.1cbc SEARCHING LOCAL0800.5a54.ee59 SEARCHING LOCAL0800.5a8f.9c3f FOUND LOCAL TokenRing0/0 08B0.A041.0DE5.06404000.0000.0050 FOUND LOCAL TokenRing0/0 0CB0.0011.3E71.A041.0DE5.06404000.0000.0306 FOUND LOCAL TokenRing0/0 0CB0.0011.3E71.A041.0DE5.06404000.0000.0307 SEARCHING LOCAL4000.0000.0308 SEARCHING LOCAL4000.1234.56c1 FOUND LOCAL Serial3/7 --no rif--4000.1234.56c2 FOUND LOCAL Serial3/7 --no rif--4000.3000.0100 FOUND LOCAL TokenRing0/0 08B0.A041.0DE5.06404000.4000.ff40 SEARCHING LOCAL4000.7470.00e7 SEARCHING LOCAL4000.ac0b.0001 FOUND LOCAL TokenRing0/0 08B0.A041.0DE5.06404001.0000.0064 FOUND LOCAL TokenRing0/0 0CB0.0011.3E71.A041.0DE5.06404001.3745.1088 FOUND LOCAL TokenRing0/0 08B0.A041.0DE5.06404100.0131.1030 FOUND LOCAL TokenRing0/010B0.FFF1.4041.0041.3E71.A041.0DE5.0640DLSw NetBIOS Name reachability cache listNetBIOS Name status Loc. peer/port rifAPPNCLT2 FOUND LOCAL TokenRing0/0 08B0.A041.0DE5.0640The following is sample output from the show dlsw reachability command with the mac-address argument:
Router# show dlsw reachability mac-address 4000.00000306DLSw MAC address reachability cache listMac Addr status Loc. peer/port rif4000.0000.0306 FOUND LOCAL TokenRing0/0 0CB0.0011.3E71.A041.0DE5.0640The following is sample output from the show dlsw reachability command with the netbios-names argument:
Router# show dlsw reachability netbios-namesDLSw NetBIOS Name reachability cache listNetBIOS Name status Loc. peer/port rifAPPNCLT2 FOUND LOCAL TokenRing0/0 08B0.A041.0DE5.0640Table 38 describes the significant fields shown in the show dlsw reachability command.
.
show dlsw statistics
To display the number of frames that have been processed in the local, remote, and group cache, use the show dlsw statistics privileged EXEC command.
show dlsw statistics [border-peers]
Syntax Description
border-peers
(Optional) Displays the number of frames processed in the local, remote, and group caches.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following sample is a sample output from the show dlsw statistics command. The output displays the number of frames processed in the local, remote, and group cache.
Router# show dlsw statistics border-peers100 Border Peer Frames processed10 Border frames found Local20 Border frames found Remote17 Border frames found Group Cacheshow dlsw transparent cache
To display the master circuit cache for each transparent bridged domain, use the show dlsw transparent cache privileged EXEC command.
show dlsw transparent cache
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Issue the show dlsw transparent cache command on the master router of the transparent bridged domain.
Examples
The following is sample output from the show dlsw transparent cache command:
Router# show dlsw transparent cacheInterface Ethernet0/1Circuit Cachelocal addr(lsap) remote addr(dsap) state Owner0000.3028.92b6(08) 0007.0db1.238c(08) POSITIVE SELF0000.3028.92b6(08) 0008.dec3.609e(12) NEGATIVE 0009.fa50.0b1cTotal number of circuits in the Cache:2show dlsw transparent map
To display MAC address mappings on the local router and any mappings for which the local router is acting as backup for a neighbor peer, use the show dlsw transparent map privileged EXEC command.
show dlsw transparent map
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Issue the show dlsw transparent map command to ensure that the local MAC address is the address created in the dlsw transparent map command. The command should be issued on all the routers configured for the Ethernet Redundancy feature to ensure the local MAC addresses match.
Examples
The following is sample output from the show dlsw transparent map command on two routers configured for the Ethernet Redundancy feature:
Router6# show dlsw transparent mapInterface Ethernet6/2LOCAL Mac REMOTE MAC BACKUP--------- ---------- ------0008.dec3.0080 0008.dec3.609e 0007.7fb0.1080 STATIC0008.dec3.0040 0008.dec3.609e 0007.7fb0.1080 DYNAMIC(Passive)Router7# show dlsw transparent mapInterface Ethernet0/1LOCAL Mac REMOTE MAC BACKUP--------- ---------- ------0008.dec3.0080 0008.dec3.609e 0006.3a0a.1a55 DYNAMIC(Passive)0008.dec3.0040 0008.dec3.609e 0006.3a0a.1a55 STATICThe output from Router 6 and Router 7 shows the created MAC addresses are 0008.dec3.0080 and 0008.dec3.0040.
show dlsw transparent neighbor
To display DLSw neighbors in a transparent bridged domain, use the show dlsw transparent neighbor privileged EXEC command.
show dlsw transparent neighbor
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show dlsw transparent neighbor command:
Router7# show dlsw transparent neighborInterface ATM0.10006.e278.6c0e SELF Master0009.fa50.0b1c Rcvd Master-Accepted VALIDThe output shows that Router 7 is the master router whose MAC address is 0006.e278.6c0e. The other router, with a MAC address of 0009.fa50.0b1c, is a slave router on the common domain. The master router received a packet from the slave and notes the router is VALID
