-
Bridging and IBM Networking Configuration Guide
-
About The Cisco IOS Software Documentation
-
Bridging and IBM Networking Overview
- Part 1: Bridging
-
Part 2: IBM Networking
-
Configuring Remote Source-Route Bridging
-
Configuring DLSw+
-
Configuring STUN and BSTUN
-
Configuring LLC2 and SDLC Parameters
-
Configuring IBM Network Media Translation
-
Configuring DSPU and SNA Service Point Support
-
Configuring SNA Frame Relay Access Support
-
Configuring APPN
-
Configuring NCIA Client/Server Topologies
-
Configuring IBM Channel Attach
-
-
Table Of Contents
Configuring Data-Link Switching Plus
Define a Source-Bridge Ring Group for DLSw+
Define a DLSw+ Local Peer for the Router
Define a DLSw+ Ring List or Port List
Define a DLSw+ Bridge Group List
Configure Direct Encapsulation
Enable DLSw+ on a Token Ring or FDDI Interface
Enable DLSw+ on an Ethernet Interface
Enable DLSw+ on an SDLC Interface
Enable NetBIOS Dial-on-Demand Routing
Configure Maximum Entries in Group Cache
Configure Peer-on-Demand Defaults
Configure Promiscuous Peer Defaults
Configure Static Resources Capabilities Exchange
Configure Duplicate Path Handling
Monitor and Maintain the DLSw+ Network
DLSw+ Using TCP Encapsulation and LLC2 Local Acknowledgment—Basic Configuration Example
Notes on Using LLC2 Local Acknowledgment
DLSw+ Using TCP Encapsulation with Local Acknowledgment—Peer Groups Configuration Example 1
DLSw+ Using TCP Encapsulation with Local Acknowledgment—Peer Group Configuration Example 2
DLSw+ with SDLC Multidrop Support Configuration Example
DLSw+ with LLC2-to-SDLC Conversion between PU 4-to-PU 4 Communication
DLSw+ Translation between Ethernet and Token Ring Configuration Example
DLSw+ Translation between FDDI and Token Ring Configuration Example
DLSw+ Translation between SDLC and Token Ring Media Example
DLSw+ over Frame Relay Configuration Example
DLSw+ over QLLC Configuration Examples
Configuring Data-Link Switching Plus
This chapter describes how to configure data-link switching plus (DLSw+), our implementation of the DLSw standard for Systems Network Architecture (SNA) and NetBIOS devices. For a complete description of the commands in this chapter, refer to the "DLSw+ Configuration Commands" chapter of the Bridging and IBM Networking Command Reference. To locate documentation of specific commands that appear in this chapter, use the command reference master index or search online.
DLSw+ Configuration Task List
DLSw+ supports local or remote media conversion between LANs and SDLC or QLLC. For clarity, the configuration task list below describes configuration in a Token Ring environment. The only differences for SDLC and Ethernet are the specific commands needed to configure those media, plus a media-specific command to associate the interface with DLSw+.
Note
By default, the Cisco IOS software translates Token Ring LLC2 to Ethernet 802.3 LLC2. To configure the router to translate Token Ring LLC2 frames into Ethernet 0x80d5 format frames, refer to the section "Enable Token Ring LLC2-to-Ethernet Conversion" in the "Configuring Source-Route Bridging" chapter of the Bridging and IBM Networking Command Reference.
To configure DLSw+, complete the tasks in the following sections:
•
•
•
•
•
•
•
•
•
See the end of this chapter for "DLSw+ Configuration Examples." Media-specific configuration examples for Ethernet and SDLC are also provided. For details of SDLC commands in the sample SDLC configuration, refer to the "LLC2 and SDLC Commands" chapter of the Bridging and IBM Networking Command Reference.
Define a Source-Bridge Ring Group for DLSw+
The source-bridge ring can be shared between DLSw+ and SRB/RSRB. In DLSw+, the source-bridge ring group specifies the virtual ring that will appear to be the last ring in the RIF. Because RIFs are terminated at the router, there is no correlation between the ring-group number specified in DLSw+ peers. The numbers can be the same for management simplicity, but they do not have to be. To define a source-bridge ring group for DLSw+, perform the following task in global configuration mode:
Refer to "DLSw+ Using TCP Encapsulation and LLC2 Local Acknowledgment—Basic Configuration Example" for a sample configuration file.
Define a DLSw+ Local Peer for the Router
Defining a DLSw+ local peer for a router enables DLSw+. You specify all local DLSw+ parameters as part of the local peer definition. To define a local peer, perform the following task in global configuration mode:
Refer to "DLSw+ Using TCP Encapsulation and LLC2 Local Acknowledgment—Basic Configuration Example" for a sample configuration.
Define a DLSw+ Ring List or Port List
DLSw+ ring lists map traffic on a local interface to remote peers. You can create a ring list of local ring numbers and apply the list to remote peer definitions. Traffic received from a remote peer is only forwarded to the rings specified in the ring list. Traffic received from a local interface is only 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. If you want all peers and all rings to receive all traffic, you do not have to define a ring list. Specify 0 for the list number in the remote peer statement.
To define a ring list, perform the following task in global configuration mode:
DLSw+ port lists map traffic on a local interface (either Token Ring or serial) to remote peers. You can create a port list of local ports and apply the list to remote peer definitions. Traffic received from a remote peer is only forwarded to peers if the input port number appears in the port list applied to the remote peer definition. The port list command provides a single command to specify both serial and Token Ring interfaces. shows how port lists are used to map traffic.
Figure 81 Mapping Traffic Using Port Lists
The definition of a port list is optional. If you want all peers and all interfaces to receive all traffic, you do not have to define a port list. Simply specify 0 for the list number in the remote peer statement.
To define a port list, perform the following task in global configuration mode:
Note
Define a DLSw+ Bridge Group List
DLSw+ bridge group lists map traffic on the local Ethernet bridge group interface to remote peers. You can create a bridge group list and apply the list to remote peer definitions. Traffic received from a remote peer is only forwarded to the bridge group specified in the bridge group list. Traffic received from a local interface is only 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. Because each remote peer has a single list number associated with it, 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.
Define DLSw+ Remote Peers
You can define three types of encapsulation on a remote peer by performing the following tasks:
•
The configuration commands for each of the encapsulation methods share some optional parameters that permit support for specific features, such as backup peers. There are some command options for TCP encapsulation support features that are not available with other encapsulation types: SNA dial-on-demand routing (DDR) and configured dynamic peers. The configuration combinations for each of the encapsulation methods and features are described in greater detail following the task tables.
Configure Direct Encapsulation
Direct encapsulation is supported over HDLC and Frame Relay. Direct encapsulation over Frame Relay comes in two forms: DLSw Lite (LLC2 encapsulation) and Passthru. To configure direct encapsulation, perform the following tasks in global configuration mode:
Note
Configure FST Encapsulation
To configure FST encapsulation on a remote peer, perform the following task in global configuration mode:
Configure TCP Encapsulation
To configure TCP encapsulation on a remote peer, perform the following task in global configuration mode:
is a list of valid port numbers used for TCP connections when the priority keyword is used with the dlsw remote-peer command:
Table 4
Valid port Numbers for TCP Connections
Backup Peers
The backup-peer option is common to all encapsulation types (direct, FST, and TCP) on a remote peer and specifies that this remote peer is a backup peer for the router with the specified IP-address, Frame Relay DLCI number, or interface name. When the primary peer fails, all circuits over this peer are disconnected and the user can start a new session via their backup peer. Prior to Cisco IOS Release 11.2(6)F, you could configure backup peers only for primary FST and TCP.
Also, when you specify the backup-peer option in a dlsw remote-peer tcp command, the backup peer is activated only when the primary peer becomes unreachable. Once the primary peer is reactivated, all new sessions use the primary peer and the backup peer remains active only as long as there are LLC2 connections using it. You can use the linger option to specify a period (in minutes) that the backup peer remains connected after the connection to the primary peer is reestablished. When the linger period expires, the backup peer connection is taken down.
Note
SNA Dial-on-Demand Routing
In TCP encapsulation you can use the keepalive and timeout options to run DLSw+ over a switched line and have the Cisco IOS software take the switched line down dynamically when it is not in use. Utilizing these options gives the IP Routing table more time to converge when a network problem hinders a remote peer connection. In small networks with good IP convergence time and ISDN lines that start quickly, it is not as neccesary to use the keepalive option. To use this feature, you must set the keepalive value to zero, and you may need to use a lower value for the timeout option than the default, which is 90 seconds.
Configured Dynamic Peers
In TCP encapsulation, the dynamic option and its suboptions no-llc and inactivity allow you to specify and control the activation of dynamic peers, which are configured peers that are activated only when required. Dynamic peer connections are established only when there is DLSw+ data to send. The dynamic peer connections are taken down when the last LLC2 connection using them terminates and the time period specified in the no-llc option expires. You can also use the inactivity option to take down dynamic peers when the circuits using them are inactive for a specified number of minutes.
Note
The dest-mac and dmac-output-list options allow you to specify filter lists as part of the dlsw remote-peer command to control access to remote peers. For static peers in direct, FST, or TCP encapsulation, these filters control which explorers are sent to remote peers. For dynamic peers in TCP encapsulation, these filters also control the activation of the dynamic peer. For example, you can specify at a branch office that a remote peer is only activated when there is an explorer frame destined for the MAC address of an FEP.
The dest-mac option permits the connection to be established only when there is an explorer frame destined for the specified MAC address. The dmac-output-list option permits the connection to be established only when the explorer frame passes the specified access list. To permit access to a single MAC address, use the dest-mac option, because it is a configuration "short-cut" compared to the dmac-output-list option.
Refer to "DLSw+ Using TCP Encapsulation and LLC2 Local Acknowledgment—Basic Configuration Example" for a sample configuration.
Enable DLSw+ over Frame Relay
You can configure the Cisco IOS software for direct encapsulation of DLSw+ in Frame Relay according to RFC 1490. DLSw+ direct encapsulation over RFC 1490 supports either pass-through or local acknowledgment (data link control termination). DLSw+ supports transport for both SNA and NetBIOS data. SNA PU 2.0 and PU 2.1 are supported.
The configuration requires a minimum number of PVCs (since multiple protocols can share a single PVC). A minimum number of PVCs simplifies configuration because multiple PUs can share a PVC without requiring configuration of multiple SAPs.
The pass-thru option adds the smallest amount of link overhead and requires minimal processing cycles in the attaching routers when compared to TCP/IP encapsulation.
The local acknowledgment option prevents data link control timeouts during periods of WAN congestion. It also minimizes WAN traffic by keeping data link control acknowledgments and keepalives off the WAN.
No controller or FEP upgrades are required to take advantage of this feature (if already Token Ring attached), reducing costs and simplifying migration to Frame Relay.
To enable DLSw+ over Frame Relay with passthrough, perform the following tasks, beginning in global configuration mode:
Note
To enable DLSw+ over Frame Relay with local acknowledgment (also known as DLSw Lite), perform the following tasks, beginning in global configuration mode:
Enable DLSw+ on a Token Ring or FDDI Interface
To enable DLSw+ on a Token Ring or FDDI interface, perform the following task in interface configuration mode:
Enable DLSw+ on a Token Ring or FDDI interface.
source-bridge local-ring bridge-number ring-group
Enable DLSw+ on an Ethernet Interface
To enable DLSw+ on certain Ethernet interfaces, perform the following task in global configuration mode:
In interface mode, the interfaces must also be put into the bridge-group.
Enable DLSw+ on an SDLC Interface
To establish devices as SDLC stations, complete the following tasks in interface configuration mode:
Set the encapsulation type of the serial interface to SDLC.
encapsulation sdlc
Establish the role of the interface.
sdlc role {none | primary | secondary | prim-xid-poll}
Configure a MAC address for the serial interface.
sdlc vmac mac-address1
Assign a set of secondary stations attached to the serial link.
sdlc address hexbyte [echo]
Specify the destination address with which an LLC session is established for the SDLC station.
sdlc partner mac-address sdlc-address
1 The last byte of the MAC address must be 00.
To enable DLSw+ on an SDLC interface, perform the following task in interface configuration mode:
Enable DLSw+ on an SDLC interface.
sdlc dlsw {sdlc-address | default | partner mac address [inbound | outbound]}
Use the default option if you have more than 10 SDLC devices to attach to the DLSw+ network. To configure an SDLC multidrop line downstream, you configure the SDLC role as either primary or prim-xid-poll. SDLC role primary specifies that any PU without the xid-poll parameter in the sdlc address command is a PU 2.0 device. SDLC role prim-xid-poll specifies that every PU is type 2.1. We recommend that you specify sdlc role primary if all SDLC devices are type PU 2.0 or a mix of PU 2.0 and PU 2.1. Specify sdlc role prim-xid-poll if all devices are type PU 2.1
To configure DLSw+ to support LLC2-to-SDLC conversion for PU 4 or PU 5 devices, specify the echo option in the sdlc address command. A PU 4-to-PU 4 configuration requires that none be specified in the sdlc role command.
Refer to the sections "DLSw+ with SDLC Multidrop Support Configuration Example" and "DLSw+ with LLC2-to-SDLC Conversion between PU 4-to-PU 4 Communication" for sample configurations.
Enable DLSw+ over QLLC
You can configure DLSw+ for QLLC connectivity, which enables both of the following two scenarios:
•
Our QLLC support allows remote X.25-attached SNA devices to access a FEP without requiring NPSI in the FEP. This may eliminate the requirement for NPSI (if GATE and DATE are not required), thereby eliminating the recurring license cost. In addition, because the QLLC attached devices appear to be Token Ring-attached to the NCP, they require no preconfiguration in the FEP. Remote X.25-attached SNA devices can also connect to an AS/400 over Token Ring using this support.
•
For environments just beginning to migrate to LANs, our QLLC support allows deployment of LANs in remote sites while maintaining access to the FEP over existing NPSI links. Remote LAN-attached devices (physical units) or SDLC- attached devices can access a FEP over an X.25 network without requiring X.25 hardware or software in the LAN-attached devices. The Cisco IOS software supports direct attachment to the FEP over X.25 without the need for routers at the data center for SNA traffic.
To enable QLLC connectivity for DLSw+, perform the following tasks in interface configuration mode:
Enable NetBIOS Dial-on-Demand Routing
DLSw+ can filter NetBIOS Session Alive packets from the WAN. NetBIOS periodically sends Session Alive packets as LLC2 I-frames. These packets do not require a response and are superfluous to the function of proper data flow. Furthermore, these packets keep dial-on-demand interfaces up and this up time causes unwanted per-packet charges in DDR networks. By filtering these NetBIOS Session Alive packets, you reduce traffic on the WAN as well as some costs that are associated with DDR.
To enable NetBIOS Dial-on-Demand Routing, perform the following task in global configuration mode:
Tune the DLSw+ Configuration
To modify an existing configuration parameter, perform one or more of the tasks in the following sections:
•
•
•
•
•
Configure DLSw+ Timers
To configure DLSw+ timers (including group cache entries), perform the following task in global configuration mode:
Configure Maximum Entries in Group Cache
To define the maximum entries in a group cache, perform the following task in global configuration mode:
Configure Peer-on-Demand Defaults
To configure peer-on-demand defaults, perform one of the following task in global configuration mode:
Configure Promiscuous Peer Defaults
To configure promiscuous peer defaults, perform one of the following task in global configuration mode:
Configure Static Resources Capabilities Exchange
To reduce explorer traffic destined for this peer, the peer can send other peers a list of resources for which it has information (icanreach) or does not have information (icannotreach). This information is exchanged as part of a capabilities exchange.To configure static resources that will be exchanged as part of a capabilities exchange, perform one of the following tasks in global configuration mode:
Configure Static Paths
To configure static paths to minimize explorer traffic originating in this peer, perform one of the following tasks in global configuration mode:
Configure Duplicate Path Handling
To configure duplicate path handling, perform the following task in global configuration mode:
Disable Border Peer Caching
To disable the border peer caching feature, perform the following task in global configuration mode:
Disable UDP Unicast
DLSw Version 2 uses User Datagram Protocol (UDP) Unicast in response to an IP multicast. When address resolution packets (CANUREACH_EX, NETBIOS_NQ_ex, NETBIOS_ANQ, and DATAFRAME) are sent to multiple destinations (IP multicast service), DLSw Version 2 sends the response frames (ICANREACH_ex and NAME_RECOGNIZED_ex) via UDP Unicast.
UDP Unicast uses UDP source port 0. However, some firewall products treat packets that use UDP source port 0 as security violations, discarding the packets and preventing DLSw connections. To avoid this situation, use one of the following procedures:
•
•
To disable UDP Unicast, perform the following task in global configuration mode:
Monitor and Maintain the DLSw+ Network
To monitor and maintain activity on the DLSw+ network, perform one or more of the following tasks in privileged EXEC mode:
DLSw+ Configuration Examples
The following sections provide DLSw+ configuration examples:
•
•
•
•
•
•
•
•
•
•
DLSw+ Using TCP Encapsulation and LLC2 Local Acknowledgment—Basic Configuration Example
This sample configuration requires the following tasks, which are described in earlier sections of this document:
•
•
•
•
Encapsulate the source-route bridged traffic inside IP datagrams passed over a TCP connection between two routers with local acknowledgment enabled when you have LANs separated by wide geographic distances, and you want to avoid multiple retransmissions or loss of user sessions that can occur with time delays.
Logical Link Control, type 2 (LLC2) is an ISO standard data-link level protocol used in Token Ring networks. LLC2 was designed to provide reliable transmission of data across LAN media and to cause minimal or at least predictable time delays. However, RSRB and WAN backbones created LANs that are separated by wide, geographic distances spanning countries and continents. As a result, LANs have time delays that are longer than LLC2 allows for bidirectional communication between hosts. Local acknowledgment addresses the problem of unpredictable time delays, multiple retransmissions, and loss of user sessions.
In a typical LLC2 session, when one host sends a frame to another host, the sending host expects the receiving host to respond positively or negatively in a predefined period of time commonly called the T1 time. If the sending host does not receive an acknowledgment of the frame it sent within the T1 time, it retries a few times (normally 8 to 10). If there is still no response, the sending host drops the session.
illustrates an LLC2 session. A 37x5 on a LAN segment can communicate with a 3x74 on a different LAN segment separated via a wide-area backbone network. Frames are transported between Router A and Router B by means of DLSw+. However, the LLC2 session between the 37x5 and the 3x74 is still end-to-end; that is, every frame generated by the 37x5 traverses the backbone network to the 3x74, and the 3x74, on receipt of the frame, acknowledges it.
Figure 82 LLC2 Session without Local Acknowledgment
On backbone networks consisting of slow serial links, the T1 timer on end hosts could expire before the frames reach the remote hosts, causing the end host to retransmit. Retransmission results in duplicate frames reaching the remote host at the same time as the first frame reaches the remote host. Such frame duplication breaks the LLC2 protocol, resulting in the loss of sessions between the two IBM machines.
One way to solve this time delay is to increase the timeout value on the end nodes to account for the maximum transit time between the two end machines. However, in networks consisting of hundreds or even thousands of nodes, every machine would need to be reconfigured with new values. With local acknowledgment for LLC2 enabled, the LLC2 session between the two end nodes would not be not end-to-end, but instead, would terminate at two local routers. shows the LLC2 session with the 37x5 ending at Router A and the LLC2 session with the 3x74 ending at Router B. Both Router A and Router B execute the full LLC2 protocol as part of local acknowledgment for LLC2.
Figure 83 LLC2 Session with Local Acknowledgment
With local acknowledgment for LLC2 enabled in both routers, Router A acknowledges frames received from the 37x5. The 37x5 still operates as if the acknowledgments it receives are from the 3x74. Router A looks like the 3x74 to the 37x5. Similarly, Router B acknowledges frames received from the 3x74. The 3x74 operates as if the acknowledgments it receives are from the 37x5. Router B looks like the 3x74 to 37x5. Because the frames no longer have to travel the WAN backbone networks to be acknowledged, but instead are locally acknowledged by routers, the end machines do not time out, resulting in no loss of sessions.
Enabling local acknowledgment for LLC2 has the following advantages:
•
•
Notes on Using LLC2 Local Acknowledgment
LLC2 local acknowledgment is enabled with TCP and DLSw+ lite remote peers.
If the LLC2 session between the local host and the router terminates in either router, the other will be informed to terminate its connection to its local host.
If the TCP queue length of the connection between the two routers reaches the high-water mark, the routers sends Receiver-Not-Ready (RNR) messages to the local hosts until the queue limit is reduced to below this limit. It is possible, however, to prevent the RNR messages from being sent by using the dlsw llc2 nornr command.
The configuration of the LLC2 parameters for the local Token Ring interfaces can affect overall performance. Refer to the chapter "Configuring LLC2 and SDLC Parameters" in this manual for more details about fine-tuning your network through the LLC2 parameters.
The routers at each end of the LLC2 session execute the full LLC2 protocol, which could result in some overhead. The decision to use local acknowledgment for LLC2 should be based on the speed of the backbone network in relation to the Token Ring speed. For LAN segments separated by slow-speed serial links (for example, 56 kbps), the T1 timer problem could occur more frequently. In such cases, it might be wise to turn on local acknowledgment for LLC2. For LAN segments separated by a T1, backbone delays will be minimal; in such cases, FST or direct should be considered. Speed mismatch between the LAN segments and the backbone network is one criterion to help you decide to use local acknowledgment for LLC2.
There are some situations (such as the receiving host failing between the time the sending host sends data and the time the receiving host receives it), in which the sending host would determine, at the LLC2 layer, that data was received when it actually was not. This error occurs because the router acknowledges that it received data from the sending host before it determines that the receiving host can actually receive the data. But because both NetBIOS and SNA have error recovery in situations where an end device goes down, these higher-level protocols will resend any missing or lost data. Because these transaction request/confirmation protocols exist above LLC2, they are not affected by tight timers, as is LLC2. They also are transparent to local acknowledgment.
If you are using NetBIOS applications, note that there are two NetBIOS timers—one at the link level and one at the next higher level. Local acknowledgment for LLC2 is designed to solve link timeouts only. If you are experiencing NetBIOS session timeouts, you have two options:
•
•
illustrates a DLSw+ configuration with local acknowledgment.
Figure 84 DLSw+ with Local Acknowledgment—Simple Configuration
Configuration for Router A
source-bridge ring-group 10!dlsw local-peer peer-id 10.2.25.1dlsw remote-peer 0 tcp 10.2.5.2interface loopback 0ip address 10.2.25.1 255.255.255.0...interface tokenring 0no ip addressring-speed 16source-bridge active 25 1 10source-bridge spanningConfiguration for Router B
source-bridge ring-group 12dlsw local-peer peer-id 10.2.5.2dlsw remote-peer 0 tcp 10.2.25.1interface loopback 0ip address 10.2.5.2 255.255.255.0...interface tokenring 0no ip addressring-speed 16source-bridge active 5 1 12source-bridge spanningDLSw+ Using TCP Encapsulation with Local Acknowledgment—Peer Groups Configuration Example 1
illustrates DLSw+ configured using acknowledgmentborder peers, showing circuits to each other. Router A is configured to operate in promiscuous mode, and border peers Routers B and C forward broadcasts. This configuration reduces processing requirements in Router A (the access router) and still support any-to-any networks.
Figure 85 DLSw+ with Peer Groups Specified (Example 1)
The following are configuration files for the routers in .
Configuration for Router A
hostname RouterA!source-bridge ring group 31dlsw local-peer peer-id 128.207.152.5 group 70 promiscuousdlsw remote peer 0 tcp 128.207.150.8!interface serial 0ip unnumbered tokenringclockrate 56000!interface tokenring 0ip address 128.207.152.5 255.255.255.0ring-speed 16source-bridge 200 13 31source-bridge spanning!...router igrp 777network 128.207.0.0Configuration for Router B
hostname RouterB!...source-bridge ring-group 31dlsw local-peer peer-id 128.207.150.8 group 70 border promiscuousdlsw remote-peer 0 tcp 128.207.169.3dlsw remote-peer 0 tcp 128.207.152.5!...interface serial 0ip unnumbered tokenring 0bandwidth 56!...interface tokenring 0ip address 128.207.150.8 255.255.255.0ring-speed 16source-bridge 3 14 31source-bridge spanning!router igrp 777network 128.207.0.0Configuration for Router C
hostname RouterC!...source-bridge ring-group 69dlsw local-peer peer-id 128.207.169.3 group 69 border promiscuousdlsw remote-peer 0 tcp 128.207.150.8!...interface tokenring 3/0description fixed to flashnetip address 128.207.2.152 255.255.255.0ring-speed 16multiring all!interface tokenring 3/1ip address 128.207.169.3 255.255.255.0ring-speed 16source-bridge 33 2 69source-bridge spanning!...router igrp 777network 128.207.0.0DLSw+ Using TCP Encapsulation with Local Acknowledgment—Peer Group Configuration Example 2
illustrates a peer group configuration that allows any-to-any connection except for Router B. Router B has no connectivity to anything except router C because the promiscuous keyword is omitted
Figure 86 DLSw+ with Peer Groups Specified (Example 2)
The following are configuration files for the routers in .
Configuration for Router A
hostname Router A!...source-bridge ring-group 2000dlsw local-peer peer-id 150.150.99.1 group 2 promiscuousdlsw remote-peer 0 tcp 150.150.100.1!interface loopback 0ip address 150.150.99.1 255.255.255.192!interface serial 0ip address 150.150.9.1 255.255.255.192!...interface tokenring 0no ip addressring-speed 16source-bridge 99 1 2000source-bridge spanning!...router eigrp 202network 150.150.0.0Configuration for Router B
hostname RouterB!...source-bridge ring-group 2000dlsw local-peer peer-id 150.150.98.1 group 2dlsw remote-peer 0 tcp 150.150.100.1!interface loopback 0ip address 150.150.98.1 255.255.255.192!...interface serial 1no ip addressencapsulation sdlcno keepalivepriority-group 1clockrate 9600sdlc role primarysdlc vmac 4000.8888.0100sdlc address 01sdlc xid 01 05d20006sdlc partner 4000.1020.1000 01sdlc dlsw 1!interface tokenring 0no ip addressring-speed 16multiring allsource-bridge 98 1 2000source-bridge spanning!...router eigrp 202network 150.150.0.0Configuration for Router C
hostname RouterC!...source-bridge ring-group 2000dlsw local-peer peer-id 150.150.100.1 group 2 border promiscuousdlsw remote-peer 0 tcp 150.150.96.1dlsw remote-peer 0 tcp 150.150.98.1dlsw remote-peer 0 tcp 150.150.99.1!interface loopback 0ip address 150.150.100.1 255.255.255.192!...interface serial 7ip address 150.150.9.2 255.255.255.192clockrate 56000!interface serial 8ip address 150.150.10.2 255.255.255.192!interface serial 9ip address 150.150.8.2 255.255.255.192!interface tokenring 0no ip addressring-speed 16multiring allsource-bridge 500 1 2000!router eigrp 202network 150.150.0.0Configuration for Router D
hostname RouterD!...source-bridge ring-group 2000dlsw local-peer peer-id 150.150.96.1 group 1 border promiscuousdlsw remote-peer 0 tcp 150.150.97.1dlsw remote-peer 0 tcp 150.150.100.1!interface loopback 0ip address 150.150.96.1 255.255.255.192!...interface serial 1/0ip address 150.150.8.1 255.255.255.192clockrate 56000!interface serial 1/1ip address 150.150.16.1 255.255.255.192!...interface tokenring g0/0ip address 150.150.2.1 255.255.255.192ring-speed 16source-bridge 96 1 2000source-bridge spanning!interface tokenring 0/1ip address 150.150.13.1 255.255.255.192no ip addressring-speed 16source-bridge 92 1 2000source-bridge spanning!...router eigrp 202network 150.150.0.0Configuration for Router E
hostname RouterE!...source-bridge ring-group 2000dlsw local-peer peer-id 150.150.97.1 group 1 promiscuousdlsw remote-peer 0 tcp 150.150.96.1!interface loopback 0ip address 150.150.97.1 255.255.255.192!interface serial 0mtu 1400ip address 150.150.16.2 255.255.255.192!...interface tokenring 0no ip addressno ip route-cachering-speed 16source-bridge 97 1 2000source-bridge spanning!...router eigrp 202network 150.150.0.0DLSw+ with SDLC Multidrop Support Configuration Example
In the following example all devices are type PU 2.0:
interface serial 2mtu 4400no ip addressencapsulation sdlcno keepaliveclockrate 19200sdlc role primarysdlc vmac 4000.1234.5600sdlc N1 27200sdlc address C1sdlc xid C1 05DCCCC1sdlc partner 4001.3745.1088 C1sdlc address C2sdlc xid C2 05DCCCC2sdlc partner 4001.3745.1088 C2sdlc dlsw C1 C2The following example shows mixed PU 2.0 (device using address C1) and PU 2.1 (device using address C2) devices:
interface serial 2mtu 4400no ip addressencapsulation sdlcno keepaliveclockrate 19200sdlc role primarysdlc vmac 4000.1234.5600sdlc N1 27200sdlc address C1sdlc xid C1 05DCCCC1sdlc partner 4001.3745.1088 C1sdlc address C2 xid-pollsdlc partner 4001.3745.1088 C2sdlc dlsw C1 C2In the following example all devices are type PU 2.1 (Method 1):
interface serial 2mtu 4400no ip addressencapsulation sdlcno keepaliveclockrate 19200sdlc role primarysdlc vmac 4000.1234.5600sdlc N1 27200sdlc address C1 xid-pollsdlc partner 4001.3745.1088 C1sdlc address C2 xid-pollsdlc partner 4001.3745.1088 C2sdlc dlsw C1 C2In the following example all devices are type PU 2.1 (Method 2):
interface serial 2mtu 4400no ip addressencapsulation sdlcno keepaliveclockrate 19200sdlc role prim-xid-pollsdlc vmac 4000.1234.5600sdlc N1 27200sdlc address C1 xid-pollsdlc partner 4001.3745.1088 C1sdlc address C2sdlc xid C2 05DCCCC2sdlc partner 4001.3745.1088 C2sdlc dlsw C1 C2DLSw+ with LLC2-to-SDLC Conversion between PU 4-to-PU 4 Communication
The following example is a sample configuration for LLC2-to-SDLC conversion for PU 4-to-PU 4 communication as shown in :
Figure 87 LLC2-to-SDLC Conversion for PU 4-to-PU 4 Communication
Router A
interface serial 0mtu 4096ip address 10.4.21.2 255.255.255.0encapsulation frame-relay IETFkeepalive 12frame-relay map llc2 46frame-relay map llc2 45frame-relay map ip 10.4.21.1 43 broadcastframe-relay map ip 10.4.21.3 45 broadcastframe-relay map ip 10.4.21.4 46 broadcastframe-relay lmi-type ansiinterface TokenRing 0mac-address 4000.1250.1001no ip addressring-speed 16fras map llc 4000.1060.1000 4 4 Serial0 frame-relay 45 4 4Router B
interface serial 0mtu 4096ip address 10.4.21.3 255.255.255.0encapsulation frame-relay IETFkeepalive 12no fair-queueframe-relay map llc2 53frame-relay map llc2 54frame-relay map llc2 56frame-relay map ip 10.4.21.1 53 broadcastframe-relay map ip 10.4.21.2 54 broadcastframe-relay map ip 10.4.21.4 56 broadcastframe-relay lmi-type ansiinterface serial 1no ip addressencapsulation sdlcno keepaliveclockrate 9600sdlc address 01 echofras map sdlc 1 Serial0 frame-relay 54 4 4 fid4DLSw+ Translation between Ethernet and Token Ring Configuration Example
DLSw+ also supports Ethernet media. Except for configuring for a specific media, in this case Ethernet, the configuration is similar to other DLSw+ configuration (see ).
Figure 88 DLSw+ Translation between Ethernet and Token Ring
The following are the configuration files for the routers in .
Configuration for Router A
hostname RouterA!...source-bridge ring-group 31dlsw local-peer peer-id 128.207.111.1dlsw remote-peer 0 tcp 128.207.1.145 lf 1500dlsw bridge-group 5!interface Ethernet 0ip address 128.207.111.1 255.255.255.0bridge-group 5!..bridge 5 protocol ieee!.Configuration for Router B
hostname RouterB!...source-bridge ring-group 500source-bridge transparent 500 1000 1 5dlsw local-peer peer-id 128.207.1.145dlsw remote-peer 0 tcp 128.207.111.1 lf 1500dlsw bridge-group 5...interface ethernet 1/2ip address 128.207.1.145 255.255.255.0bridge-group 5...interface tokenring 2/0no ip addressring-speed 16source-bridge 7 1 500source-bridge spanning!...bridge 5 protocol ieeeBecause DLSw+ does not do local translation between different LAN types, Router B must be configured for SR/TLB by issuing the source-bridge transparent command. Also, note that the bridge groups are configured on the ethernet interfaces.
DLSw+ Translation between FDDI and Token Ring Configuration Example
DLSw+ also supports FDDI media. Except for configuring for a specific media type, in this case FDDI (see Figure 89), the configuration is similar to other DLSw+ configurations.
Figure 89 DLSw+ Translation between FDDI and Token Ring
In the following example, an FDDI ring on Router A is connected to a Token Ring on Router B across a DLSw+ link.
Configuration for Router A
source-bridge ring-group 10dlsw local-peer peer-id 132.11.11.2dlsw remote-peer 0 tcp 132.11.11.3interface fddi 0no ip addresssource-bridge active 26 1 10source-bridge spanningConfiguration for Router B
source-bridge ring-group 10dlsw local peer peer-id 132.11.dlsw remote-peer 0 tcp 132.11.11.2interface tokenring 0no ip addresssource-bridge active 25 1 10source-bridge spanningDLSw+ Translation between SDLC and Token Ring Media Example
DLSw+ provides media conversion between local or remote LANs and SDLC. For additional information about configuring SDLC parameters, refer to the chapter "Configuring LLC2 and SDLC Parameters."
illustrates DLSw+ with SDLC encapsulation. For this example, 4000.1020.1000 is the MAC address of the FEP host (PU 4.0). The MAC address of the AS/400 host is 1000.5aed.1f53, which is defined as Node Type 2.1. Router B serves as the primary station for the remote secondary station 01. Router B can serve as either primary station or secondary station to remote station D2.
Figure 90 DLSw+ Translation between SDLC and Token Ring Media
The following is the configuration file for Router A.
Configuration for Router A
hostname RouterA!...source-bridge ring-group 2000dlsw local-peer peer-id 150.150.10.2dlsw remote-peer 0 tcp 150.150.10.1!...interface serial 8ip address 150.150.10.2 255.255.255.192clockrate 56000!...interface tokenring 0no ip addressring-speed 16source-bridge 500 1 2000source-bridge spanning!...router eigrp 202network 150.150.0.0Configuration for Router B
hostname RouterB!...source-bridge ring-group 2000dlsw local-peer peer-id 150.150.10.1dlsw remote-peer 0 tcp 150.150.10.2!...interface serial 0ip address 150.150.10.1 255.255.255.192!interface serial 1description PU2 with SDLC station role set to secondaryno ip addressencapsulation sdlcno keepaliveclockrate 9600sdlc role primarysdlc vmac 4000.9999.0100sdlc address 01sdlc xid 01 05d20006sdlc partner 4000.1020.1000 01sdlc dlsw 1!interface serial 2description Node Type 2.1 with SDLC station role set to negotiable or primaryencapsulation sdlcsdlc role nonesdlc vmac 1234.3174.0000sdlc address d2sdlc partner 1000.5aed.1f53 d2sdlc dlsw d2!interface tokenring 0no ip addressearly-token-releasering-speed 16multiring allsource-bridge 100 1 2000source-bridge spanning!interface tokenring 1no ip addressring-speed 16multiring allsource-bridge 400 1 2000source-bridge spanning!router eigrp 202network 150.150.0.0DLSw+ over Frame Relay Configuration Example
Frame Relay support extends the DLSw+ capabilities to include Frame Relay in direct mode. Frame Relay support includes permanent virtual circuit capability . DLSw+ runs over Frame Relay with or without local acknowledgement. It supports the Token Ring-to-Token Ring connections similar to Fast-Sequenced Transport and other direct data link controls. Figure 91 illustrates a DLSw+ configuration over Frame Relay with local acknowledgement.
Figure 91 DLSw+ over Frame Relay
The following configuration examples are based on Figure 91. The Token Rings in the illustration are in Ring 2.
Configuration for Router A
source-bridge ring-group 100dlsw local-peer peer-id 1.1.1.1dlsw remote-peer 0 frame-relay interface serial 0 30!interface tokenring 0ring-speed 16source-bridge active 1 1 100!interface serial 0mtu 3000no ip addressencapsulation frame-relayframe-relay lmi-type ansiframe-relay map llc2 30Configuration for Router B
source-bridge ring-group 100dlsw local-peer peer-id 1.1.1.2dlsw remote-peer 0 frame-relay interface serial 0 30!interface tokenring 0ring-speed 16source-bridge active 2 1 100!interface serial 0mtu 3000no ip addressencapsulation frame-relayframe-relay lmi-type ansiframe-relay map llc2 30DLSw+ over QLLC Configuration Examples
The following three examples describe QLLC support for DLSw+.
Example 1
In this configuration, DLSw+ is used to allow remote devices to connect to a DLSw+ network over an X.25 public packet-switched network.
In this example, all QLLC traffic is addressed to destination address 4000.1161.1234, which is the MAC address of the FEP.
The remote X.25-attached IBM 3174 cluster controller is given a virtual MAC address of 1000.0000.0001. This virtual MAC address is mapped to the X.121 address of the 3174 (31104150101) in the X.25 attached router.
interface serial 0encapsulation x25x25 address 3110212011x25 map qllc 1000.0000.0001 31104150101qllc dlsw partner 4000.1611.1234Example 2
In this configuration, a single IBM 3174 cluster controller needs to communicate with both an AS/400 and a FEP. The FEP is associated with subaddress 150101 and the AS/400 is associated with subaddress 151102.
If an X.25 call comes in for 33204150101, the call is mapped to the FEP and forwarded to MAC address 4000.1161.1234. The IBM 3174 appears to the FEP as a Token Ring-attached resource with MAC address 1000.0000.0001. The IBM 3174 uses a source SAP of 04 when communicating with the FEP, and a source SAP of 08 when communicating with the AS/400.
interface serial 0encapsulation x25x25 address 31102x25 map qllc 1000.0000.0001 33204qllc dlsw subaddress 150101 partner 4000.1161.1234qllc dlsw subaddress 150102 partner 4000.2034.5678 sap 04 08Example 3
In this example, two different X.25 resources want to communicate over X.25 to the same FEP.
In the router attached to the X.25 network, every X.25 connection request for X.121 address 31102150101 is directed to DLSw+. The first SVC to be established will be mapped to virtual MAC address 1000.0000.0001. The second SVC to be established will be mapped to virtual MAC address 1000.0000.0002.
interface serial 0encapsulation x25x25 address 31102x25 map qllc 33204x25 map qllc 35765qllc dlsw subaddress 150101 vmacaddr 1000.0000.0001 2 partner 4000.1611.1234
