Table Of Contents
DLSw+ Commands
clear dlsw circuit
clear dlsw history
clear dlsw local-circuit
clear dlsw reachability
clear dlsw statistics
clear dlsw transparent
dlsw allroute-netbios
dlsw allroute-sna
dlsw bgroup-list
dlsw bridge-group
dlsw cache-ignore-netbios-datagram
dlsw disable
dlsw duplicate-path-bias
dlsw group-cache disable
dlsw group-cache max-entries
dlsw history-log
dlsw icannotreach saps
dlsw icanreach
dlsw llc2 nornr
dlsw load-balance
dlsw local-peer
dlsw mac-addr
dlsw max-multiple-rifs
dlsw multicast
dlsw netbios-cache-length
dlsw netbios-keepalive-filter
dlsw netbios-name
dlsw peer-on-demand-defaults
dlsw port-list
dlsw prom-peer-defaults
dlsw redundant-rings
dlsw remote-peer frame-relay
dlsw remote-peer fst
dlsw remote-peer interface
dlsw remote-peer tcp
dlsw ring-list
dlsw rsvp
dlsw timer
dlsw tos disable
dlsw tos map
dlsw transparent map
dlsw transparent redundancy-enable
dlsw transparent switch-support
dlsw transparent timers
dlsw udp-disable
qllc dlsw
sdlc dlsw
show dlsw capabilities
show dlsw circuits
show dlsw circuits history
show dlsw fastcache
show dlsw local-circuit
show dlsw peers
show dlsw reachability
show dlsw statistics
show dlsw transparent cache
show dlsw transparent map
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
circuit-id
|
Circuit ID for a specific remote circuit. The valid range is 0 to 4294967295.
|
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2 F
|
This command was introduced.
|
Usage Guidelines
A user can specify a circuit ID of a specific circuit to clear rather than clearing all circuits.
Caution 
This 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 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
Release
|
Modification
|
12.1
|
This command was introduced.
|
Examples
The following example clears all inactive circuits from the DLSW+ circuit history:
clear 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
circuit-id
|
Circuit ID for a specific remote circuit. The valid range is 0 to 4294967295.
|
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1
|
This command was introduced.
|
Usage Guidelines
A user can specify a circuit ID of a specific circuit to clear rather than clearing all local-switched circuits.
Caution 
This 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 the locally-switched DLSw+ circuit with ID number 100:
clear dlsw local-circuit 100
clear 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
Release
|
Modification
|
11.2 F
|
This command was introduced.
|
Usage Guidelines
This command does not affect existing sessions.
Examples
The following example removes all entries from the DLSw+ reachability cache:
clear 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
Release
|
Modification
|
11.2 F
|
This command was introduced.
|
Examples
The following example resets to zero the number of frames in the local, remote, and group cache:
clear 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
Release
|
Modification
|
12.1
|
This command was introduced.
|
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:
dlsw allroute-netbios
To change the single-route explorer to an all-route broadcast for NetBIOS, use the dlsw allroute-netbios global configuration command. Use the no form of this command to return to the default single-route explorer.
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
Release
|
Modification
|
11.1
|
This command was introduced.
|
Examples
The following example specifies all-route broadcasts for NetBIOS:
dlsw allroute-sna
To change the single-route explorer, use the dlsw allroute-sna global configuration command. Use the no form of this command to return to the default single-route explorer.
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
Release
|
Modification
|
11.1
|
This command was introduced.
|
Examples
The following example specifies all-route broadcasts for SNA:
dlsw bgroup-list
To map traffic on the local Ethernet bridge group interface to remote peers, use the dlsw bgroup-list global configuration command. Use the no form of this command to cancel the map.
dlsw bgroup-list list-number bgroups number
no dlsw bgroup-list
Syntax Description
list-number
|
The ring list number. This number is subsequently used in the dlsw remote-peer command to define the segment to which the bridge-group should be applied. The valid range is 1 to 255.
|
bgroups number
|
The transparent bridge group list number. The valid range is 1 to 63.
|
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
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 33
Related Commands
Command
|
Description
|
dlsw bridge-group
|
Links DLSw+ to the bridge group of the Ethernet LANs.
|
dlsw ring-list
|
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. Use the no form of this command to disable the link.
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
group-number
|
Transparent bridge group to which DLSw+ will be attached. The valid range is 1 to 63.
|
llc2
|
(Optional) LLC2 interface subcommands.
|
N2 number
|
(Optional) Number of times router should retry various operations. The valid range is 1 to 255.
|
ack-delay-time milliseconds
|
(Optional) Maximum time the router allows incoming I-frames to stay unacknowledged. The valid range is 1 to 60000.
|
ack-max number
|
(Optional) Maximim number of I-frames received before an acknowledgment must be sent. The valid range is 1 to 255.
|
idle-time milliseconds
|
(Optional) Frequency of polls during periods of idle traffic. The valid range is 1 to 60000.
|
local-window number
|
(Optional) Maximum number of I-frames to send before waiting for an acknowledgment. The valid range is 1 to 127.
|
t1-time milliseconds
|
(Optional) Amount of time router waits for an acknowledgment to transmitted I-frames. The valid range is 1 to 60000.
|
tbusy-time milliseconds
|
(Optional) Amount of time router waits while the other LLC2 station is in a busy state before attempting to poll the remote station. The valid range is 1 to 60000.
|
tpf-time milliseconds
|
(Optional) Amount of time router waits for a final response to a poll frame before re-sending the original poll frame. The valid range is 1 to 60000.
|
trej-time milliseconds
|
(Optional) Amount of time router waits for a resend of a rejected frame before sending the reject command. The valid range is 1 to 60000.
|
txq-max number
|
(Optional) Queue for holding LLC2 information frames. The valid range is 20 to 200.
|
xid-neg-val-time milliseconds]
|
(Optional) Frequency of exchange of identification (XID). The valid range is 1 to 60000.
|
xid-retry-time milliseconds
|
(Optional) Amount of time router waits for reply to XID. The valid range is 1 to 60000.
|
locaddr-priority lu address priority list number
|
(Optional) Assigns an input SNA LU Addr priority list to this bridge group. The valid range is 1 to 10.
|
sap-priority priority list number
|
(Optional) Assigns an input sap priority list to this bridge group. The valid range is 1 to 10.
|
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
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.1
dlsw remote-peer 0 tcp 2.2.2.2
Related Commands
Command
|
Description
|
dlsw bgroup-list
|
Maps traffic on the local Ethernet bridge group interface to remote peers.
|
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. Use the no form of this command to remove the filter.
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
Release
|
Modification
|
11.3
|
This command was introduced.
|
Examples
The following example helps maintain a smaller name cache:
dlsw cache-ignore-netbios-datagram
dlsw disable
To disable DLSw+ without altering the configuration, use the dlsw disable global configuration command. Use the no form of this command to reenable DLSw+.
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
Release
|
Modification
|
11.0
|
This command was introduced.
|
Examples
The following example reenables DLSw+:
dlsw 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. Use the no form of this command to return to the default (fault-tolerance).
dlsw duplicate-path-bias [load-balance]
no dlsw duplicate-path-bias [load-balance]
Syntax Description
load-balance
|
(Optional) Specifies that sessions are load-balanced across duplicate paths.
|
Defaults
Fault-tolerance is the default logic used to handle duplicate paths.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
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-balance
dlsw group-cache disable
To disable the border peer caching feature, use the dlsw group cache disable global configuration command. Use the no form of this command to return to the default peer caching feature.
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
Release
|
Modification
|
11.2 F
|
This command was introduced.
|
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:
Related 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. Use the no form of this command to return to the default.
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
Release
|
Modification
|
11.2 F
|
This command was introduced.
|
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 1800
Related 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
size
|
Specifies the number of circuits for which to retain history. The history size per circuit is fixed at the last 16 events. The size argument can range from 16 to 65536.
|
connected-only
|
(Optional) Specifies that history will only be recorded for circuits that reach the CONNECTED state, and only FSM events following the move to the CONNECTED state will be retained.
|
ignore-info-frames
|
(Optional) Specifies that the following FSM events will not be recorded in the history:
• WAN infoframe
• WAN dgmframe
• DLC udata.ind
• DLC data.ind
|
Defaults
The DLSw history log is enabled with a value of 32 for the size argument.
Command Modes
Global configuration
Command History
Release
|
Modification
|
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-only
dlsw 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. Use the no form of this command to remove the list.
dlsw icannotreach saps sap...
no dlsw icannotreach saps sap...
Syntax Description
sap. . .
|
One or more SAPs.
|
Defaults
No lists are configured.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
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 F0
dlsw icanreach
To configure a resource that is locally reachable by this router, use the dlsw icanreach global configuration command. Use the no form of this command to remove the resource.
dlsw icanreach {mac-exclusive | netbios-exclusive [remote] | mac-address mac-addr [mask
mask] | netbios-name name | saps}
no dlsw icanreach {mac-exclusive | netbios-exclusive [remote] | mac-address mac-add [mask
mask] | netbios-name name | saps}
Syntax Description
mac-exclusive
|
Router can reach only the MAC addresses that are user configured.
|
netbios-exclusive
|
Router can reach only the NetBIOS names that are user configured.
|
remote
|
(Optional) Gives the NetBIOS workstations (that are local to the router and that are not already defined in the dlsw icanreach netbios-name name statement) access to remote servers.
|
mac-address mac-addr
|
Configures a MAC address that this router can locally reach.
|
mask mask
|
(Optional) MAC address mask in hexadecimal h.h.h. The "f" value represents the "care" bit and the "0" value represents the "don't care" bit. The mask indicates which bits in the MAC address are relevant.
|
netbios-name name
|
Configures a NetBIOS name that this router can locally reach. Wildcards (*) are allowed at the end of the name. Trailing white spaces are ignored when comparing against an actual name in a NetBIOS frame.
|
saps
|
(Optional) Array of SAPs.
|
Defaults
No resources are configured.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
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 keword allows roving workstations to access remote servers. With the remote keyword specified, all local NetBIOS stations will be able to make outgoing connections regardless of whether their own NetBIOS name is configured in the icanreach netbios-name list. Incoming connections will be limited to those with a destination name that is specified in the list.
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 DLSw+, whether incoming or outgoing.
Note
Because the configuration of the mac-address and netbios-name keywords prevents the DLSw+ peer from exploring, a misconfiguration could prevent DLSw+ from being able to find a resource actually available elsewhere in the network.
Examples
The following example indicates that this peer 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 "lanserv" will be able to establish a DLSw+ connection:
dlsw icanreach netbios-exclusive
dlsw icanreach netbios-name lanserv
Related Commands
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. Use the no form of this command to return to the default.
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
Release
|
Modification
|
11.0
|
This command was introduced.
|
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.
The 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 400023491026
8 0.173 LLC C D=00 S=04 TEST P
9 0.003 LLC R D=04 S=00 TEST F
10 0.002 SNA XID Fmt 2 T4
11 0.059 SNA XID Fmt 2 T4
12 0.004 SNA XID Fmt 2 T4
13 0.065 SNA XID Fmt 2 T4
14 0.005 SNA XID Fmt 2 T4
16 0.054 LLC C D=04 S=04 SABME P
17 0.003 LLC R D=04 S=04 UA
The router sends a receiver not ready message:
18 0.001 LLC C D=04 S=04 RNR NR=0
From frames 19 to 35, the FEP does not respond:
19 0.002 LLC C D=04 S=04 RR NR=0
20 0.048 SNA C NC NC-ER-OP
21 0.997 LLC C D=04 S=04 RR NR=0 P
22 1.000 LLC C D=04 S=04 RR NR=0 P
24 1.000 LLC C D=04 S=04 RR NR=0 P
25 1.000 LLC C D=04 S=04 RR NR=0 P
31 1.000 LLC C D=04 S=04 RR NR=0 P
32 1.000 LLC C D=04 S=04 RR NR=0 P
34 1.000 LLC C D=04 S=04 RR NR=0 P
35 1.000 LLC C D=04 S=04 RR NR=0 P
The router disconnects the circuit:
37 1.000 LLC C D=04 S=04 DISC P
38 0.002 LLC R D=04 S=04 UA F
The sequence repeats:
39 0.179 LLC C D=00 S=04 TEST P
41 0.767 SNA XID Fmt 2 T4
42 0.634 SNA XID Fmt 2 T4
43 0.173 LLC C D=00 S=04 TEST
44 0.003 LLC R D=04 S=00 TEST F
45 0.002 SNA XID Fmt 2 T4
46 0.060 SNA XID Fmt 2 T4
47 0.004 SNA XID Fmt 2 T4
48 0.063 SNA XID Fmt 2 T4
49 0.005 SNA XID Fmt 2 T4
dlsw 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. Use the no form of this command to disable the previous assignments.
dlsw load-balance [round-robin | circuit-count circuit weight]
no dlsw load-balance [round-robin | circuit-count circuit weight]
Syntax Description
round-robin
|
(Optional) Enables round-robin type of load balancing.
|
circuit-count circuit weight
|
(Optional) Enables the DLSw+ Enhanced Load Balancing feature. The value represents the default circuit-weight to be used for the peers that are not explicitly configured with a circuit-weight value in the dlsw remote-peer tcp command. The valid range is 1 to 100.
|
Defaults
Fault-tolerant mode is the default setting. The default value for the circuit weight is 10.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.0(3)T
|
This command was introduced.
|
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 10
dlsw local-peer
To define the parameters of the DLSw+ local peer, use the dlsw local-peer global configuration command. Use the no form of this command to cancel the definitions.
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
cluster cluster-id
|
(Optional) Implements the DLSw+ Peer Clusters feature and defines the router as part of a particular cluster. The valid range is 1 to 255.
|
peer-id ip-address
|
(Optional) Local peer IP address. This address is required when Fast-Sequenced Transport (FST) or TCP is used.
|
group group
|
(Optional) Peer group number for this router. The valid range is 1 to 255.
|
border
|
(Optional) Enables the router as a border peer. The group option must be specified to use the border peer option.
|
cost cost
|
(Optional) Peer cost advertised to remote peers in the capabilities exchange. The valid range is 1 to 5.
|
lf size
|
(Optional) Largest frame size for this local peer. Valid maximum frame sizes are as follows:
• 516-516 bytes
• 1470-1470 bytes
• 1500-1500 bytes
• 2052-2052 bytes
• 4472-4472 bytes
• 8144-8144 bytes
• 11407-11407 bytes
• 11454-11454 bytes
• 17800-17800 bytes
|
keepalive seconds
|
(Optional) Default remote peer keepalive interval in seconds. The valid range is 0 to 1200 seconds. The default is 30 seconds. The value 0 means no keepalives.
|
passive
|
(Optional) Specifies that this router does not initiate remote peer connections to configured peers.
|
promiscuous
|
(Optional) Accept connections from nonconfigured remote peers.
|
biu-segment
|
(Optional) DLSw+ spoofs the maximum receivable I-frame size in XID so that each end station sends its largest frame.
|
init-pacing-window size
|
(Optional) Size of the initial pacing window as defined in RFC 1795. The valid range is 1 to 2000.
|
max-pacing-window size
|
(Optional) Maximum size of the pacing window as defined in RFC 1795. The valid range is 1 to 2000.
|
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
12.0(3)T
|
The cluster keyword was added.
|
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 2
Related Commands
dlsw mac-addr
To configure a static MAC address, use the dlsw mac-addr global configuration command. Use the no form of this command to cancel the configuration.
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
mac-addr
|
Specifies the MAC address.
|
ring ring-number
|
Maps the MAC address to a ring number or ring group number. The valid range is 1 to 4095.
|
remote-peer
|
Maps the MAC address to a specific remote peer.
|
interface serial number
|
Specifies the remote peer by direct serial interface.
|
ip-address ip-address
|
Specifies the remote peer by IP address.
|
rif rif-string
|
Maps the MAC address to a local interface using a RIF string. The RIF string describes a source-routed path from the router to the MAC address. It starts at the router's ring-group and ends on the ring where the MAC address is located. The direction should be from the router toward the MAC address. See IEEE 802.5 standard for details.
|
group group
|
Maps the MAC address to a specified peer group. Valid numbers are in the range 1 to 255.
|
Defaults
No static MAC address is configured.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
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
Because the configuration of this command prevents the DLSw+ peer from exploring, a misconfiguration could prevent DLSw+ from being able to find a resource actually available elsewhere in the network.
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.2
Related Commands
dlsw max-multiple-rifs
To enable caching of multiple RIFs per interface, use the dlsw max-multiple-rifs global configuration command. Use the no form of this command to turn off the feature.
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
Release
|
Modification
|
11.3
|
This command was introduced.
|
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 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]