DOCSLIB.ORG

Data Link Switching: Switch-To-Switch Protocol

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Data Link Switching: Switch-To-Switch Protocol Network Working Group R. Dixon Request for Comments: 1434 D. Kushi IBM March 1993 Data Link Switching: Switch-to-Switch Protocol Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Abstract This RFC describes IBM's support of Data Link Switching over TCP/IP. The RFC is being distributed to members of the Internet community in order to solicit their reactions to the proposals contained in it. While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementors. Any questions or comments relative to the contents of this RFC should be sent to the following Internet address: [email protected]. Table of Contents 1. Introduction..................................................................................................................................... 3 2. Overview ......................................................................................................................................... 3 3. Transport Connection ...................................................................................................................... 4 3.1. SSP Frame Formats......................................................................................................... 5 3.2. Address Parameters.........................................................................................................7 3.3. Message Types................................................................................................................ 9 4. Protocol Specification ...................................................................................................................... 9 4.1. Protocol Flow Diagrams.................................................................................................. 9 4.1.1. Connect Protocols........................................................................................... 10 4.1.2. Link Restart Protocols .................................................................................... 11 4.1.3. Disconnect Protocols ...................................................................................... 11 4.2. DLS State Machine ......................................................................................................... 12 4.2.1. Data Link Switch States.................................................................................. 12 4.2.2. State Transition Tables................................................................................... 15 Dixon & Kushi [Page 1] RFC: 1434 DLS: Switch-to-Switch Protocol March 1993 4.3. NetBIOS Datagrams........................................................................................................ 22 Acknowledgments ............................................................................................................................... 23 References ........................................................................................................................................... 23 Security Considerations ....................................................................................................................... 23 Authors' Addresses .............................................................................................................................. 24 Dixon & Kushi [Page 2] RFC: 1434 DLS: Switch-to-Switch Protocol March 1993 1. Introduction Data Link Switching (DLS) is a forwarding mechanism for the IBM SNA and IBM NetBIOS protocols. It does not provide full routing, but instead provides switching at the Data Link layer and encapsulation in TCP/IP for transport over the Internet. This memo documents the Switch-to-Switch Protocol (SSP) that is used between IBM 6611 Network Processors. Today, the IBM 6611 supports SNA (PU 2 and PU 4) systems and NetBIOS systems attached to token- ring networks, as well as SNA (PU 2) systems attached to SDLC links. For the later case, the SDLC attached systems are provided with a LAN appearance within the IBM 6611. For the LAN attached systems, the IBM 6611 appears as a source-routing bridge. Remote systems that are accessed through the IBM 6611 appear as systems attached to an adjacent ring. This ring is a virtual ring that is manifested within each IBM 6611. 2. Overview Data Link Switching was developed to provide support for SNA and NetBIOS in multi-protocol routers. Since SNA and NetBIOS are basically connection oriented protocols, the Data Link Control procedure that they use on the LAN is IEEE 802.2 Logical Link Control (LLC) Type 2. Data Link Switching also accommodates SNA protocols over WAN links via the SDLC protocol. IEEE 802.2 LLC Type 2 was designed with the assumption that the network transit delay would be small and predictable (i.e., a local LAN). Therefore the LLC elements of procedure use a fixed timer for detecting lost frames. When bridging is used over wide area lines (especially at lower speeds), the network delay is larger and it can vary greatly based upon congestion. When the delay exceeds the time- out value LLC attempts to retransmit. If the frame is not actually lost, only delayed, it is possible for the LLC Type 2 procedures to become confused. And as a result, the link is eventually taken down. Given the use of LLC Type 2 services, Data Link Switching addresses the following bridging problems: • DLC Time-outs • DLC Acknowledgments over the WAN • Flow and Congestion Control • Broadcast Control of Search Packets • Source-Route Bridging Hop Count Limits NetBIOS also makes extensive use of datagram services that use LLC Type 1. In this case, Data Link Switching addresses the last two problems in the above list. The principal difference between Data Link Switching and bridging is that DLS terminates the Data Link Control whereas bridging does not. The following figure illustrates this difference based upon two end systems operating with LLC Type 2 services. Dixon & Kushi [Page 3] RFC: 1434 DLS: Switch-to-Switch Protocol March 1993 Bridging TCP/IP Bridge Bridge Info RR Data Link Switching TCP/IP DLS DLS Info Info RR Info RR Figure 1. Data Link Switching Contrasted to Bridging In traditional bridging, the Data Link Control is end-to-end. Data Link Switching terminates the LLC Type 2 connection at the switch. This means that the LLC Type 2 connections do not cross the wide area network. The DLS multiplexes LLC connections onto a TCP connection to another DLS. Therefore, the LLC connections at each end are totally independent of each other. It is the responsibility of the Data Link Switch to deliver frames that it has received from a LLC connection to the other end. TCP is used between the Data Link Switches to guarantee delivery of frames. As a result of this design, LLC time-outs are limited to the local LAN (i.e., they do not traverse the wide area). Also, the LLC Type 2 acknowledgments (RR's) do not traverse the WAN, thereby reducing traffic across the wide area links. For SDLC links, polling and poll response occurs locally, not over the WAN. Broadcast of search frames is controlled by the Data Link Switches once the location of a target system is discovered. Finally, the switches can now apply back pressure to the end systems to provide flow and congestion control. Data Link Switching uses LAN addressing to set up connections between SNA systems. SDLC attached devices are defined with MAC addresses to enable them to communicate with LAN attached devices. For NetBIOS systems, Data Link Switching uses the NetBIOS name to forward datagrams and to set up connections for NetBIOS sessions. For circuit establishment, SNA systems send TEST (or in some cases, XID) frames to the null (x'00') SAP. NetBIOS systems have an address resolution procedure, based upon the Name Query and Name Recognized frames, that is used to establish an end-to-end circuit. Since Data Link Switching may be implemented in multi-protocol routers, there may be situations where both bridging and switching are enabled. SNA frames can be identified by their link SAP. Typical SAP values for SNA are x'04', x'08', and x'0C'. NetBIOS always uses a link SAP value of x'F0'. 3. Transport Connection Data Link Switches can be in used in pairs or by themselves. A Single DLS internally switches one data link to another without using TCP (DLC(1) to DLC(2) in the figure below). A paired DLS multiplexes data links over a reliable transport using a Switch-to-Switch Protocol (SSP). This RFC will document the frame formats and protocols for this multiplexing between Data Link Switches. The initial implementation of SSP uses TCP as the reliable transport between Data Link Switches. However, other transport connections such as OSI TP4 could be used. Dixon & Kushi [Page 4] RFC: 1434 DLS: Switch-to-Switch Protocol March 1993 D L C In te r fa c e S w it c h -t o - S w itc h P ro t o c o l (S S P ) DLC Request Data Link Control (1) DLC Indication Send SSP Frame Data Link Switch Receive SSP Frame DLC Request Data Link Control (2) DLC Indication Multi-protocol Router Figure 2. DLS System Diagram Before Data Link Switching can occur between two routers, they must establish a TCP connection between them. Each DLS will maintain a list of DLS capable routers and their status (active/inactive). Once this connection is established, the DLS will employ SSP to establish end-to-end circuits over the transport connection. Within the transport connection is a specific set of DLS message
Load more

Recommended publications
  • DSU Routefinder Model MTASR2-201
    LAN-to-LAN Routing for Central-Site and Branch Office Networks DSU RouteFinder Model MTASR2-201 User Guide User Guide 88301701 Revision B DSU RouteFinder (Model MTASR2-201) This publication may not be reproduced, in whole or in part, without prior expressed written permission from Multi-Tech Systems, Inc. All rights reserved. Copyright © 1998, 1999, by Multi-Tech Systems, Inc. Multi-Tech Systems, Inc. makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, Multi-Tech Systems, Inc. reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Multi-Tech Systems, Inc. to notify any person or organization of such revisions or changes. Record of Revisions Revision Description A Manual released; covers software revision 3.00. All pages at revision A. (11/3/98) B Manual revised to show E1 (2.048 Mbps) synchronous capability for WAN link; (11/30/99) also added new command cable. All pages at revision B. Patents This Product is covered by one or more of the following U.S. Patent Numbers: 5.301.274; 5.309.562; 5.355.365; 5.355.653; 5.452.289; 5.453.986. Other Patents Pending. TRADEMARK Trademark of Multi-Tech Systems, Inc. is the Multi-Tech logo and RouteFinder. Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Multi-Tech Systems, Inc. 2205 Woodale Drive Mounds View, Minnesota 55112 (612) 785-3500 or (800) 328-9717 Fax 612-785-9874 Tech Support (800) 972-2439 BBS (612) 785-3702 or (800) 392-2432 Internet Address: http://www.multitech.com Contents Chapter 1 - Introduction and Description Introduction ......................................................................................................................................................
    [Show full text]
  • Zbigniew S. Szewczak Systemy Operacyjne
    Zbigniew S. Szewczak Systemy Operacyjne Wykład 4 Sieciowe systemy operacyjne. Toruń, 2005 Terminy egzaminów ✦ piątek, 17.02.2006, g.12.00-14.00 ✦ ✦ niedziela, 5.03.2006, g.14.00-16.00 ✦ O czym będzie? ✦ Systemy sieciowe ✦ System sieciowy NFS ✦ System sieciowy SMB ✦ NetBIOS ✦ Protokół SMB/CIFS ✦ Funkcje Samby ✦ Struktura systemu Samba ✦ SMB w systemie Windows ✦ System sieciowy NCP Sieciowy system komputerowy ✦ Sieciowy system komputerowy jest tą częścią systemu komputerowego, która dziedziczy odpowiedzialność za komunikowanie się komputerów poprzez łącza ✦ sprzęt - medium transmisji danych, karta sieciowa, modem ✦ system operacyjny - implementacja protokołu (TCP/IP, NetBEUI, IPX/SPX ) w jądrze ✦sieciowy podsystem operacyjny : SMB, NFS, NCP ✦inne systemy : Andrew FS (IBM), Coda FS (CMU) ✦ programy użytkowe - przeglądarka WWW, telnet, ftp ✦ użytkownicy: zdalny komputer, osoba używająca ftp Sieciowe systemy operacyjne - modus operandi ✦ Sieciowy system operacyjny (ang. network operating system ) tworzy środowisko, w którym użytkownicy - świadomi wielości maszyn - uzyskują dostęp do zdalnych zasobów rejestrując się na odpowiednich zdalnych maszynach lub też użyczają zdalnie swoich lokalnych zasobów nadając im w tym celu na swojej maszynie stosowne uprawnienia do zdalnego dostępu ✦ zdalne zasoby: urządzenia we/wy (dyski, drukarki), procesory, pamięć operacyjna , (magistrala?) Sieciowe systemy operacyjne - modus procedendi ✦ Aby sieciowe systemy operacyjne mogły się komunikować potrzebne są sieci komputerowe ✦ Komunikacja w sieci komputerowej odbywa się na podstawie ściśle określonego zbioru reguł zwanego protokołem ✦ Sieciowy system operacyjny realizuje zwykle wiele protokołów komunikowania się ✦ Protokoły komunikowania się klasyfikujemy według modelu OSI lub TCP/IP Sieciowe systemy operacyjne - modus procedendi (c.d.) ✦ Problem sposobu komunikowania się ✦ model klient/serwer ✦ Peer-to-Peer (P2P) ✦ Protokoły sieciowe działają pomiędzy różnymi: ✦ architekturami komputerów ✦reprezentacja danych: kolejność bajtów, rozmiary danych (np.
    [Show full text]
  • Japanese Translation, Using Optivity Campus
    Optivity Campus 7.0 Using Optivity Campus 7.0 302730-A Rev.00 April 1998 4401 Great America Parkway 8 Federal Street Santa Clara, CA 95054 Billerica, MA 01821 Copyright © 1998 Bay Networks, Inc. All rights reserved. Printed in the USA. April 1998. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Bay Networks, Inc. Trademarks Optivity, and Bay Networks are registered trademarks of Bay Networks, Inc. Autotopology, Expanded View, NodalView, Campus Command Center, LANarchitect, RouterMan, Quick2Config, System 800, System 2000, System 3000, System 5000, BayStack, ANH, ASN, Segment View, EZ Install, Accelar 100, BaySecure and LattisSwitch are trademarks of Bay Networks, Inc. Windows, Windows 95, and Windows NT are registered trademarks of Microsoft Corporation. Other brand and product names are registered trademarks or trademarks of their respective holders. Statement of Conditions In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the right to make changes to the products described in this document without notice. Bay Networks, does not assume any liability that may occur due to the use or application of the product(s) or circuit
    [Show full text]
  • Multi-Protocol Transport Services
    Multi-ProtocolMulti-Protocol TransportTransport ServicesServices NetBIOS, NetBEUI, TCP/IP, NetBIOS over TCP/IP IntroductionIntroduction Overview of OSI Reference Model Local Area Networking Concepts NetBIOS/NetBEUI overview TCP/IP overview NetBIOS over TCP/IP OS/2 TCPBEUI Windows Clients Troubleshooting IBM MPTS Class - munich 2002 1-2 TheThe OSIOSI ReferenceReference ModelModel An Introduction OSIOSI referencereference modelmodel Developed by International Organization for Standardization (ISO) in 1984 Conceptual model composed of seven layers Provides a conceptual framework for communication between computers Acutal communication is made possible by the usage of "communication protocols" Tasks assigned to each layer can be implemented independently IBM MPTS Class - munich 2002 3-4 TheThe sevenseven layerslayers ofof OSIOSI modelmodel The seven layers of OSI model are shown below TheThe PhysicalPhysical layerlayer Defines electrical, mechanical, procedural and functional specifications for activating, maintaining and deactivating physical link between systems Define characteristics such as voltage levels, timing of voltage changes, physical data rates, maximum transmission distances and physical connectors used Examples: Ethernet, Token-Ring, FDDI, etc. IBM MPTS Class - munich 2002 5-6 TheThe DataData LinkLink layerlayer Provides reliable transit of data across the network Data Link characteristics include: Physical addressing: Defines how devices are addressed at the data link layer Network topology: Specifies how devices are to be
    [Show full text]
  • Puter Center, CS , N CT U
    Samba Computer Center, CS, NCTU CS, Computer Center, Network-based File Sharing FTP (File Transfer Protocol) NFS (UNIX-based) • mountd is responsible for mount request • nfsd and nfsiod Applikation • Based on RPC SMB CIFS (Microsoft) • Common Internet File System NetBIOS • 網路芳鄰 NetBEUI TCP/IP IPX/SPX • SMB (Server Message Block) • Share access to files, printers, … NDIS (2,3,3.1,4,5)-Interface • Based on NetBIOS Karten-Treiber (MAC) Netzwerk-Karte 2 Computer Center, CS, NCTU CS, Computer Center, Service of SMB and NetBIOS NetBIOS (Network Basic Input/Output System) • API related to the session layer allowing applications to communicate over a local area network • Name Service for name registration and resolution • Session service for connection-oriented communication • Datagram distribution service for connectionless communication SMB • File and printer sharing service • Authentication 3 Computer Center, CS, NCTU CS, Computer Center, NetBIOS – Network Basic Input/Output System NetBIOS (API) • 1983 – developed as an API for software communication over IBM’s PC-Network LAN NetBIOS relied on proprietary Sytek networking protocols • In 1985, IBM went forward with the token ring network scheme NetBEUI – NetBIOS Extended User Interface using the NetBIOS Frames (NBF) routing protocol • 1985 – Microsoft created a NetBIOS implementation for its MS-Net network topology By NBF protocol • Difference between local filesystem and network filesystem when accessing • Used to share or access network-based filesystem just as BIOS does in local
    [Show full text]
  • Order Jo 6000.200
    U.S. DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION ORDER JO 6000.200 Effective Date: 08/07/2006 Changed by CHG 1 11/24/2008 SUBJ: MAINTENANCE OF FAA TELECOMMUNICATIONS INFRASTRUCTURE (FTI) SERVICES 1. PURPOSE. This handbook provides guidance, technical standards and tolerances, and procedures applicable to the maintenance of FAA Telecommunication Infrastructure (FTI) Services. This information augments information available in instruction books and other handbooks, and complements the latest edition of Order 6000.15, General Maintenance Handbook for NAS Facilities. * 2. DISTRIBUTION. This document requires actions by the Airway Transportation System Specialist (ATSS) at operational facilities with Facility, Service, and Equipment Profile (FSEP) equipment: DIST and DISTG. a. The ATSS and all administrative personnel must subscribe to the Auto-Notifications Services for electronic library release notifications at http://technet.faa.gov/. Administrative offices can print these documents for local use as required. b. For electronic copies, use the Technical Library website at http://nas.amc.faa.gov. c. The ATSS must keep accurate FSEP records and Logistics Inventory System (LIS) addresses to receive printed copies. Printed copies are mailed to the ATSS at operational facilities with an accurate FSEP record using the LIS mailing address per Orders 6000.5D, Facility, Service, and Equipment Profile (FSEP) and Order 1720.30C, Distribution of Airway Facilities Technical Directives. d. To update LIS, contact the LIS point of contact for your service area. To update FSEP information, visit this link: https://intranet.faa.gov/faaemployees/org/linebusiness/ato/operations/technical_operations/ajw162/fsep/cont acts/. * 3. MAINTENANCE AND MODIFICATION PROCEDURE. a. Order 6000.15, this handbook, the applicable equipment instruction book, and other applicable handbooks shall be consulted and used together by the maintenance technician in all duties and activities for the maintenance of FTI facilities and equipment.
    [Show full text]
  • Technical Reference Third Edition (November 1988)
    ------ --- SC30-3383-2 ---- - - --- . Local Area Network --------' - 25F7688 Technical Reference SC30-3383-2 -------- ------- Local Area Network -------_.---- - --- Technical Reference Third Edition (November 1988) Changes are made periodically to the information herein; these changes will be incorporated in new editions of this publication. It is possible that this material may contain reference to, or information about, IBM products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that IBM intends to announce such IBM products, programming, or services in your country. Publications are not stocked at the address given below; requests for IBM publications should be made to your IBM representative or to the IBM branch office serving your locality. A form for reader's comments is provided at the back of this publication. If the form has been removed, comments may be addressed to IBM Corporation, Communication Products Information Development, Department E02, PO Box 12195, Research Triangle Park, North Carolina, U.S.A. 27709. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation whatever. You may, of course, continue to use the information you supply. © Copyright International Business Machines Corporation 1986, 1988 About This Book This manual provides information for using IBM local area network adapters and supporting software in IBM Personal Computers and IBM PERSONAL SYSTEM/2® computers. It is intended for use by those who are: • Preparing programs that will use an IBM Personal Computer or Personal System/2 with IBM local area networks • Using the IBM local area network adapters in IBM devices • Obtaining information to understand an adapter for use in an IBM Personal Computer or IBM Personal System/2.
    [Show full text]
  • Netbios, Netbeui, NBF, NBT, NBIPX, SMB, CIFS Networking
    NetBIOS, NetBEUI, NBF, NBT, NBIPX, SMB, CIFS Networking Timothy D Evans NetBIOS, NetBEUI, NBF, NBT, NBIPX, SMB, CIFS Networking by Timothy D Evans Copyright © 1998, 2003 by Timothy D Evans Unlimited non-commercial distribution of this document in its entirety is encouraged, please contact the author prior to commercial publication. Important: This documentation is revised from time to time. Some of the technology described is constantly changing and being developed, especially the higher level protocols. Thus this document may not always be up to date. The reader is encouraged to ensure they have the latest version. All trade marks are respectfully acknowledged. While every precaution has been taken in the preparation of this documentation the author assumes no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. Table of Contents Preface.....................................................................................................................................7 Who should read this documentation.......................................................................7 Organization of this documentation .........................................................................7 Acknowledgments .......................................................................................................8 Notation.........................................................................................................................8 Language .......................................................................................................................8
    [Show full text]
  • Model MTASR1-100 Single WAN Multi-Protocol Router Owner's Manual
    Model MTASR1-100 Single WAN Multi-Protocol Router Owner’s Manual Owner's Manual 82052804 Revision E RouteFinder100TM (Model No MTASR1-100) This publication may not be reproduced, in whole or in part, without prior expressed written permission from Multi-Tech Systems, Inc. All rights reserved. Copyright © 1997, by Multi-Tech Systems, Inc. Multi-Tech Systems, Inc. makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, Multi-Tech Systems, Inc. reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Multi-Tech Systems, Inc. to notify any person or organization of such revisions or changes. Record of Revisions Revision Description C Manual revised to include new software version 2.01 and configuration examples. All pages at revision C. (5/19/97) D Manual revised to include new RouteFinder software version 2.20 and configuration examples. All pages at (9/22/97) revision D. E Manual revised to include new SIMM module and features. All pages at revision E. (12/15/97) Patents This Product is covered by one or more of the following U.S. Patent Numbers: 5.301.274; 5.309.562; 5.355.365; 5.355.653; 5.452.289; 5.453.986. Other Patents Pending. TRADEMARKS Trademark of Multi-Tech Systems, Inc. are as follows: RouteFinder, MultiRouter, MultiExpress, and the Multi-Tech logo. Windows is a registered trademark of Microsoft. BONDING: The BONDING Consortium Banyan, VINES and VIP Multi-Tech Systems, Inc.
    [Show full text]
  • Stealthwatch V7.0 Default Applications Definitions
    Cisco Stealthwatch Default Applications Definitions 7.0 Stealthwatch® v7.0 Default Applications Definitions Stealthwatch® v7.0 Default Applications Definitions The table in this document lists the default Stealthwatch applications defined on the Custom Applications page in the SMC Web App. The intended audience for this document includes users who want a clearer understanding of what com- prises a default application that Stealthwatch monitors. In the table below, the number in parentheses after the application name is a unique identifier (UID). Application Criteria Name Description Stealthwatch Classification Port/Protocol Registered with IANA on port 629 3com AMP3 3com AMP3 (719) TCP/UDP. Registered with IANA on port 106 3com TSMUX 3com TSMUX (720) TCP/UDP. The Application Configuration Access Pro- tocol (ACAP) is a protocol for storing and synchronizing general configuration and preference data. It was originally ACAP ACAP (722) developed so that IMAP clients can easily access address books, user options, and other data on a central server and be kept in sync across all clients. AccessBuilder (Access Builder) is a family AccessBuilder AccessBuilder (724) Copyright © 2018 Cisco Systems, Inc. All rights reserved. - 2 - Stealthwatch® v7.0 Default Applications Definitions Application Criteria Name Description Stealthwatch Classification Port/Protocol of dial-in remote access servers that give mobile computer users and remote office workers full access to workgroup, depart- mental, and enterprise network resources. Remote users dial into AccessBuilder via analog or digital connections to get direct, transparent links to Ethernet and Token Ring LANs-just as if they were connected locally. AccessBuilder products support a broad range of computing platforms, net- work operating systems, and protocols to fit a variety of network environments.
    [Show full text]
  • Local Area Network Concepts and Products: Adapters, Hubs and ATM
    SG24-4754-00 Local Area Network Concepts and Products: Adapters, Hubs and ATM May 1996 IBM International Technical Support Organization SG24-4754-00 Local Area Network Concepts and Products: Adapters, Hubs and ATM May 1996 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix E, “Special Notices” on page 291. First Edition (May 1996) This edition applies to the most recent IBM LAN products and LAN architectures. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. HZ8 Building 678 P.O. Box 12195 Research Triangle Park, NC 27709-2195 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1996. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Preface . ix How This Redbook Is Organized ........................... ix The Team That Wrote This Redbook ......................... x Comments Welcome . xi Chapter 1. LAN Adapters and Support ....................... 1 1.1 OSI Reference Model and LAN Components ................. 1 1.2 Shared RAM Adapters ............................... 2 1.3 Bus Master/DMA Adapters ............................ 3 1.4 Bus Architectures . 4 1.4.1 Micro Channel Bus .............................. 4 1.4.2 ISA Bus . 5 1.4.3 EISA Bus . 5 1.4.4 PCI Bus . 5 1.4.5 VL Bus (Local Bus) .............................. 5 1.4.6 PCMCIA LAN Adapter ...........................
    [Show full text]
  • M P Uter Center, CS, N
    Samba jnlin Computer CS,Center, NCTU Network-based File Sharing q FTP (File Transfer Protocol) q NFS (UNIX-based) • mountd is responsible for mount request • nfsd and nfsiod Applikation • Based on RPC SMB q CIFS (Microsoft) • Common Internet File System NetBIOS • 網路芳鄰 NetBEUI TCP/IP IPX/SPX • SMB (Server Message Block) • Share access to files, printers, … NDIS (2,3,3.1,4,5)-Interface • Based on NetBIOS Karten-Treiber (MAC) Netzwerk-Karte 2 Computer CS,Center, NCTU Service of SMB and NetBIOS q NetBIOS (Network Basic Input/Output System) • API related to the session layer allowing applications to communicate over a local area network • Name Service for name registration and resolution • Session service for connection-oriented communication • Datagram distribution service for connectionless communication q SMB • File and printer sharing service • Authentication 3 Computer CS,Center, NCTU NetBIOS – Network Basic Input/Output System q NetBIOS (API) • 1983 – developed as an API for software communication over IBM’s PC-Network LAN Ø NetBIOS relied on proprietary Sytek networking protocols • In 1985, IBM went forward with the token ring network scheme Ø NetBEUI – NetBIOS Extended User Interface Ø using the NetBIOS Frames (NBF) routing protocol • 1985 – Microsoft created a NetBIOS implementation for its MS-Net network topology Ø By NBF protocol • Difference between local filesystem and network filesystem when accessing • Used to share or access network-based filesystem just as BIOS does in local filesystem q NetBIOS over TCP/IP • In 1987 • NBT
    [Show full text]