-
Cisco IOS Release 12.0 Bridging and IBM Networking Command Reference
-
About the Cisco IOS Software Documentation
-
Using Cisco IOS Software
- Part 1: Bridging
-
Part 2: IBM Networking
-
Remote Source-Route Bridging Commands
-
DLSw+ Commands
-
Serial Tunnel and Block Serial Tunnel Commands
-
LLC2 and SDLC Commands
-
IBM Network Media Translation Commands
-
DSPU and SNA Service Point Commands
-
SNA Frame Relay Access Commands
-
APPN Configuration Commands
-
Cisco Database Connection Commands
-
NCIA Server Configuration Commands
-
Cisco Mainframe Channel Connection Commands
-
Airline Product Set Commands
-
- Part 3: Appendix
-
Table Of Contents
DLSw+ Configuration 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 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
Use the clear dlsw circuit privileged EXEC command to cause all DLSw+ circuits to be closed.
clear dlsw circuit [circuit id]
Syntax Description
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 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 reachability
Use the clear dlsw reachability privileged EXEC command to remove all entries from the DLSw+ reachability cache.
clear dlsw reachability
Syntax Description
This command has no arguments or keywords.
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
Use the clear dlsw statistics privileged EXEC command to reset to zero the number of frames that have been processed in the local, remote, and group cache.
clear dlsw statistics
Syntax Description
This command has no arguments or keywords.
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 statisticsdlsw allroute-netbios
Use the dlsw allroute-netbios global configuration command to change the single-route explorer to an all-route broadcast for NetBIOS. 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
Examples
The following example specifies all-route broadcasts for NetBIOS:
dlsw allroute-netbiosdlsw allroute-sna
Use the dlsw allroute-sna global configuration command to change the single-route explorer to an all-route broadcast for SNA. 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
Examples
The following example specifies all-route broadcasts for SNA:
dlsw allroute-snadlsw bgroup-list
Use the dlsw bgroup-list global configuration command to map traffic on the local Ethernet bridge group interface to remote peers. Use the no form of this command to cancel the map.
dlsw bgroup-list list-number bgroups number
no dlsw bgroup-list
Syntax Description
Defaults
There is no default setting.
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
Use the dlsw bridge-group global configuration command to link DLSw+ to the bridge group of the Ethernet LANs. 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
Defaults
There is no default setting.
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 group 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 disable
Use the dlsw disable global configuration command to disable DLSw+ without altering the configuration. 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
There is no default setting.
Command Modes
Global configuration
Command History
Examples
The following example reenables DLSw+:
no dlsw disabledlsw duplicate-path-bias
Use the dlsw duplicate-path-bias global configuration command to specify how DLSw+ handles duplicate paths to the same Media Access Control (MAC) address or NetBIOS name. 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
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 group-cache disable
Use the dlsw group cache disable global configuration command to disable the border peer caching feature. 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
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
Use the dlsw group-cache max entries global configuration command to limit the number of entries in the group cache. 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
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 icannotreach saps
Use the dlsw icannotreach saps global configuration command to configure a list of service access points (SAPs) not locally reachable by the router. Use the no form of this command to remove the list.
dlsw icannotreach saps sap [sap...]
no dlsw icannotreach saps sap [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
Use the dlsw icanreach global configuration command to configure a resource that is locally reachable by this router. 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
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 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
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-exclusivedlsw icanreach netbios-name lanservRelated Commands
dlsw llc2 nornr
Use the dlsw llc2 nornr global configuration command to prevent the receiver not ready (RNR) message from being sent while establishing an LLC2 connection. Use the no form of this command to return to the default.
dlsw llc2 nornr
no dlsw llc2 nornr
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 local-peer
Use the dlsw local-peer global configuration command to define the parameters of the DLSw+ local peer. Use the no form of this command to cancel the definitions.
dlsw local-peer [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 [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 parameters are defined.
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
Use the dlsw mac-addr global configuration command to configure a static MAC address. 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
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. Alternatively, 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
Use the dlsw max-multiple-rifs global configuration command to enable caching of multiple RIFs per interface. 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
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-keepalive-filter
Use the dlsw netbios-keepalive-filter global configuration command to enable the NetBIOS dial-on-demand routing (DDR) feature. Use the no form of this command to turn off the feature.
dlsw netbios-keepalive-filter
no dlsw netbios-keepalive-filter
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
See the "Bridging and IBM Networking Overview" chapter of the 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
Use the dlsw netbios-name global configuration command to configure a static NetBIOS name. Use the no form of this command to cancel the configuration.
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
Usage Guidelines
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 configures a static NetBIOS name and links it to group 3:
dlsw netbios-name netname group 3Related Commands
dlsw peer-on-demand-defaults
Use the dlsw peer-on-demand-defaults global configuration command to configure defaults for peer-on-demand transport. Use the no form of this command to disable the previous assignment.
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] [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] [tcp-queue-max]
Syntax Description
