IBM BC-203 manual BC-230, Ncia Server Client/Server Model

Page 28

Overview of IBM Networking

NCIA

Figure 101 NCIA Server Client/Server Model

SNASw

 

DLSw+

 

DLSw local switch

 

DSPU

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

LLC2

 

 

NCIA Server

 

RSRB

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Ethernet

 

 

 

Token Ring

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

TCP/IP

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

NDLC

SNA

NCIA Client

TCP/IP

S4696

 

NCIA Data Link Control (NDLC) is the protocol used between clients and servers. NDLC serves two purposes:

Establishes the peer connection

Establishes the circuit between the client and the server

The peer session must be established before an end-to-end circuit can be set up. During the set up period for the peer session, the MAC address representing a client is defined. The MAC address can be defined by the client or by the server when the client does not have a MAC address.

The NCIA Server feature supports connect-in and connect-out (from the server’s perspective), but connect-out is not supported if the client station does not listen for the incoming connection. For a server to connect-out, clients must connect to the server first. After registering itself by providing its own MAC address, the client can then optionally disconnect from the server. When a server receives an explorer, and its destination MAC address is registered, an NCIA server will connect to that client if it is not connected. For NetBIOS explorers (addressed to functional address 0xC00000000080), the TCP session must remain up so that the server can broadcast the explorers to the client. If the TCP session is down, the server will not send the NetBIOS explorers to a client, even when the client is registered.

After the peer session has been established, the NDLC protocol establishes the circuit between the client and server. This circuit is used to transfer end-user data between the client and the server. Because the client and its target station are not on the same transport, they cannot form a direct, end-to-end circuit. Each client must form a circuit between the client and server, and the server must form another circuit between the server and the target station. The server links those two circuits to form an end-to-end circuit. The server acts as a mediator between the client and the target station so that packets can be transferred between them.

In the NCIA server only peer keepalive is maintained. There is no keepalive at circuit level.

The NCIA server acts as a data-link provider, like Token Ring or Ethernet, in the router. It uses CLSI to communicate with other software modules, just as other data-link providers do. The network administrator configures the router to communicate with specific modules. For data-link users, such as SNASw, DLSw+, and DSPU, the NCIA server can interface to them directly. For other data-link providers, the NCIA server must go through a DLSw+ local peer to communicate with them. The DLSw+ local peer passes packets back and forth among different data-link providers.

Cisco IOS Bridging and IBM Networking Configuration Guide

BC-230

Image 28
Contents Overview of IBM Networking BC-203Rsrb BC-204Configuration Considerations BC-205DLSw+ BC-206DLSw Version 2 Standard DLSw StandardBC-207 DLSw+ Features Enhanced Peer-on-Demand Routing FeatureIP Multicast UDP UnicastLocal Acknowledgment BC-209BC-210 LLC2 Session Without Local AcknowledgmentBC-211 DLSw+ Support for Other SNA Features BC-212Stun Networks Stun and BstunBC-213 Stun Features BC-214BC-215 BC-216 StunBstun Features LLC2 and Sdlc ParametersBstun Networks BC-217Cisco’s Implementation of LLC2 BC-218Cisco’s Implementation of Sdlc IBM Network Media TranslationBC-219 Virtual Token Ring Concept Sdllc Media Translation FeaturesBC-220 Resolving Differences in LLC2 and Sdlc Frame Size Maintaining a Dynamic RIF CacheOther Considerations BC-221Qllc Conversion BC-222Cisco’s Implementation of Qllc Conversion BC-223Comparing Qllc Conversion to Sdllc BC-224Other Implementation Considerations BC-225RFC 1490 Routed Format for LLC2 BNN BC-226RFC 1490 Bridged Format for LLC2 BAN BC-227BC-228 NciaNcia Client/Server Model Ncia ServerBC-229 BC-230 Ncia Server Client/Server ModelAdvantages of the Client/Server Model Extended ScalabilityMigration Support BC-231BC-232 AlpsDspu and SNA Service Point BC-233BC-234 Router Acting as a Dspu ConcentratorBenefits of SNASw SNA Switching ServicesBC-235 Reduced Configuration Requirements Scalable Appn NetworksIP Infrastructure Support Network Design SimplicityBranch Extender HPR Capable SNA Routing ServicesBC-237 Enterprise Extender HPR/IP BC-238Usability Features Dynamic CP Name Generation SupportDynamic SNA BTU Size Dlur Connect-OutManagement Enhancements LAN and IP-Focused Connection Types Trap MIB Support for Advanced Network Management AwarenessToken Ring, Ethernet, and Fddi Virtual Token RingDLC Switching Support for Access to Sdlc and Qllc Cisco Transaction ConnectionVirtual Data-Link Control Native IP Data-Link Control HPR/IPCtrc and Cics BC-243Ctrc and DB2 BC-244Benefits of Ctrc Cmcc Adapter HardwareBC-245 Channel Port Adapter Channel Interface ProcessorBC-246 Differences between the CIP and CPA Escon Channel Port AdapterParallel Channel Port Adapter BC-247Cmcc Adapter Features for TCP/IP Environments Common Link Access to WorkstationSupported Environments TCP/IP OffloadCisco Multipath Channel+ IP Host BackupBC-249 Cisco SNA Cmcc Adapter Features for SNA EnvironmentsBC-250 TN3270 Server Cisco Multipath ChannelBC-251 Telnet Server Functions SNA FunctionsBC-252 BC-253 BC-254