IBM BC-201 manual Comparing Qllc Conversion to Sdllc, BC-222

Page 22

Overview of IBM Networking

IBM Network Media Translation

Figure 97 QLLC Conversion Between a Single 37x5 and Multiple 3x74s across an Arbitrary WAN

Without local

acknowledgment LLC2 session QLLC/X.25 session

With local LLC2 session TCP session QLLC/X.25 session acknowledgment

VR1

 

 

 

 

 

VR2

 

Token

T0

Arbitrary

 

X.25

37x5

 

 

 

 

 

Ring

 

WAN

S0

Virtual

 

 

 

 

 

 

Router A

Router B

ring

3270

3x74

3x74

51924

3270

How communication sessions are established over the communication link varies depending on whether or not LLC2 local acknowledgment has been configured on Router A’s Token Ring interface. In both cases, the SNA session extends end-to-end and the QLLC/X.25 session extends from Router B to the 3x74 cluster controller. If LLC2 local acknowledgment has not been configured, the LLC2 session extends from the 37x5 FEP across the Token Ring network and the arbitrary WAN to Router B. In contrast, when LLC2 local acknowledgment has been configured, the LLC2 session extends from the 37x5 FEP Router A, where it is locally terminated. A TCP session is then used across the arbitrary WAN to Router B.

Comparing QLLC Conversion to SDLLC

Although the procedures you use to configure QLLC are similar to those used to configure SDLLC, there are structural and philosophical differences between the point-to-point links that SDLC uses and the multiplexed virtual circuits that X.25 uses.

The most significant structural difference between QLLC conversion and SDLLC is the addressing. To allow a device to use LLC2 to transfer data, both SDLLC and QLLC provide virtual MAC addresses. In SDLLC, the actual MAC address is built by combining the defined virtual MAC (whose last byte is 0x00) with the secondary address used on the SDLC link; in this way, SDLLC supports multidrop. In QLLC conversion, multidrop is meaningless, so the virtual MAC address represents just one session and is defined as part of the X.25 configuration. Because one physical X.25 interface can support many simultaneous connections for many different remote devices, you only need one physical link to the X.25 network. The different connections on different virtual circuits all use the same physical link.

The most significant difference between QLLC conversion and SDLLC is the fact that a typical SDLC/SDLLC operation uses a leased line. In SDLC, dial-up connections are possible, but the maximum data rate is limited. In QLLC, both switched virtual circuits (SVCs) and permanent virtual circuits (PVCs) are available, but the favored use is SVC. While the router maintains a permanent connection to the X.25 network, a remote device can use each SVC for some bounded period of time and then relinquish it for use by another device. Using a PVC is very much like using a leased line.

 

Cisco IOS Bridging and IBM Networking Configuration Guide

BC-222

78-11737-02

Image 22
Contents Overview of IBM Networking BC-201Rsrb BC-202Configuration Considerations BC-203DLSw+ BC-204DLSw Version 2 Standard DLSw StandardBC-205 IP Multicast DLSw+ FeaturesEnhanced Peer-on-Demand Routing Feature UDP UnicastLocal Acknowledgment BC-207BC-208 LLC2 Session Without Local AcknowledgmentBC-209 DLSw+ Support for Other SNA Features BC-210Stun Networks Stun and BstunBC-211 Stun Features BC-212BC-213 BC-214 StunBstun Networks Bstun FeaturesLLC2 and Sdlc Parameters BC-215Cisco Implementation of LLC2 BC-216Cisco Implementation of Sdlc IBM Network Media TranslationBC-217 Virtual Token Ring Concept Sdllc Media Translation FeaturesBC-218 Other Considerations Resolving Differences in LLC2 and Sdlc Frame SizeMaintaining a Dynamic RIF Cache BC-219Qllc Conversion BC-220Cisco Implementation of Qllc Conversion BC-221Comparing Qllc Conversion to Sdllc BC-222Other Implementation Considerations BC-223RFC 1490 Routed Format for LLC2 BNN BC-224RFC 1490 Bridged Format for LLC2 BAN BC-225Ncia Server BC-226Ncia Client/Server Model BC-227Extended Scalability Advantages of the Client/Server ModelBC-228 Migration Support BC-229Dspu and SNA Service Point BC-230Shows a router functioning as a Dspu concentrator BC-231Benefits of SNASw SNA Switching ServicesBC-232 IP Infrastructure Support Reduced Configuration RequirementsScalable Appn Networks Network Design SimplicityBranch Extender HPR Capable SNA Routing ServicesBC-234 Enterprise Extender HPR/IP BC-235Dynamic CP Name Generation Support Usability FeaturesResponsive Mode Adaptive Rate-Based Flow Control Dynamic SNA BTU SizeUser-Settable Port Limits Interprocess Signal TracingManagement Enhancements Console Message ArchivingToken Ring, Ethernet, and Fddi LAN and IP-Focused Connection TypesMIB Support for Advanced Network Management Awareness Virtual Token RingVirtual Data-Link Control Cisco Transaction ConnectionNative IP Data-Link Control HPR/IP Ctrc and Cics BC-240Ctrc and DB2 BC-241Benefits of Ctrc Cmcc Adapter HardwareBC-242 Channel Port Adapter Channel Interface ProcessorBC-243 Parallel Channel Port Adapter Differences Between the CIP and CPAEscon Channel Port Adapter BC-244Supported Environments Cmcc Adapter Features for TCP/IP EnvironmentsCommon Link Access to Workstation TCP/IP OffloadCisco Multipath Channel+ IP Host BackupBC-246 Cisco SNA Cmcc Adapter Features for SNA EnvironmentsBC-247 TN3270 Server Cisco Multipath ChannelBC-248 Telnet Server Functions SNA FunctionsBC-249 BC-250