DOCSLIB.ORG

VSI X.25 for Openvms Management Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
VSI X.25 for Openvms Management Guide VSI OpenVMS VSI X.25 for OpenVMS Management Guide Document Number: DO-DX25MG-01A Publication Date: August 2018 Revision Update Information: This is a new manual. Operating System and Version: VSI OpenVMS Integrity Version 8.4-2 VSI OpenVMS Alpha Version 8.4-2L1 Software Version: VSI X.25 for OpenVMS Version 2.1 VMS Software, Inc. (VSI) Burlington, Massachusetts, USA VSI X.25 for OpenVMS Management Guide Copyright © 2018 VMS Software, Inc. (VSI), Burlington, Massachusetts, USA Legal Notice Confidential computer software. Valid license from VSI required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for VSI products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. VSI shall not be liable for technical or editorial errors or omissions contained herein. HPE, HPE Integrity, HPE Alpha, and HPE Proliant are trademarks or registered trademarks of Hewlett Packard Enterprise. The VSI OpenVMS documentation set is available on DVD. ii VSI X.25 for OpenVMS Management Guide Preface ................................................................................................................................... vii 1. About VSI .................................................................................................................... vii 2. Intended Audience ........................................................................................................ vii 3. Document Structure ...................................................................................................... vii 4. Associated Manuals ..................................................................................................... viii 5. VSI Encourages Your Comments .................................................................................... ix 6. Terminology ................................................................................................................... x 7. Conventions .................................................................................................................... x Chapter 1. Introduction ........................................................................................................ 1 1.1. Facilities Provided by X.25 for OpenVMS .................................................................... 1 1.1.1. Management ...................................................................................................... 1 1.1.2. Security ............................................................................................................ 1 1.1.3. Accounting ........................................................................................................ 2 1.1.4. X.25 and X.29 Programming ............................................................................. 2 1.1.5. X.29 Access ...................................................................................................... 2 1.1.6. X.25 Mail ......................................................................................................... 3 1.1.7. Common Trace Facility (CTF) ........................................................................... 3 1.2. Introduction to X.25 Management ................................................................................. 3 1.3. How to Use this Manual .............................................................................................. 4 Part I. Conceptual Information Chapter 2. The X.25 Management Model ........................................................................... 7 2.1. Introduction ................................................................................................................. 7 2.2. Modules Used in an X.25 for OpenVMS System ........................................................... 7 2.3. Entities ........................................................................................................................ 8 2.3.1. Device .............................................................................................................. 8 2.3.2. Modem Connect ................................................................................................ 9 2.3.3. LAPB ............................................................................................................... 9 2.3.4. CSMA-CD or FDDI .......................................................................................... 9 2.3.5. LLC2 ................................................................................................................ 9 2.3.6. XOT (OpenVMS I64 and OpenVMS Alpha) ..................................................... 10 2.3.7. X25 Protocol ................................................................................................... 10 2.3.8. X25 Access ..................................................................................................... 10 2.3.9. X25 Server ...................................................................................................... 11 2.3.10. X25 Client ..................................................................................................... 11 2.3.11. X25 Relay (OpenVMS I64 and OpenVMS Alpha) ........................................... 11 2.4. Modules and Entities Used in Each Type of X.25 System ............................................. 12 2.5. Example Configurations ............................................................................................. 13 2.5.1. X.25 Client System Configuration .................................................................... 13 2.5.2. X.25 Direct Connect System Configuration ....................................................... 14 2.5.3. Connector System Configuration ...................................................................... 18 2.5.4. X.25 Relay System (OpenVMS I64 and OpenVMS Alpha) ................................ 19 2.5.5. Combination Systems ...................................................................................... 21 Chapter 3. The Components of an X.25 for OpenVMS System ..................................... 23 3.1. Summary of Call Handling ......................................................................................... 23 3.1.1. Making a Call from a Direct Connect System ................................................... 24 3.1.2. Receiving a Call on a Direct Connect System ................................................... 24 3.1.3. Making a Call from a Client System ................................................................. 25 3.1.4. Receiving a Call on a Client System ................................................................. 25 3.2. DTE Classes, DTEs, Links, and Lines ......................................................................... 26 iii VSI X.25 for OpenVMS Management Guide 3.2.1. DTE Classes .................................................................................................... 27 3.2.2. DTEs .............................................................................................................. 29 3.2.3. LAPB Links .................................................................................................... 32 3.2.4. Physical Synchronous Communication Lines .................................................... 33 3.2.5. LLC2 Links ..................................................................................................... 34 3.2.6. LAN Stations .................................................................................................. 35 3.2.7. XOT Links (OpenVMS I64 and OpenVMS Alpha) ........................................... 36 3.2.8. PVCs .............................................................................................................. 37 3.2.9. Groups ............................................................................................................ 38 3.3. Templates ................................................................................................................... 38 3.3.1. Predefined Templates ....................................................................................... 41 3.3.2. Designing Templates ........................................................................................ 42 3.4. Application Filters ...................................................................................................... 44 3.4.1. How Filters Are Used ...................................................................................... 46 3.4.2. Predefined Filters ............................................................................................ 46 3.4.3. Designing Filters ............................................................................................. 47 3.5. Server–Client Filters ................................................................................................... 49 3.5.1. Designing Server–Client Filters ........................................................................ 49 3.6. X.25 Applications ...................................................................................................... 50 3.6.1. Designing Applications ...................................................................................
Load more

Recommended publications
  • Data Networks
    Second Ed ition Data Networks DIMITRI BERTSEKAS Massachusetts Institute of Technology ROBERT GALLAGER Massachusetts Institute ofTechnology PRENTICE HALL, Englewood Cliffs, New Jersey 07632 2 Node A Node B Time at B --------- Packet 0 Point-to-Point Protocols and Links 2.1 INTRODUCTION This chapter first provides an introduction to the physical communication links that constitute the building blocks of data networks. The major focus of the chapter is then data link control (i.e., the point-to-point protocols needed to control the passage of data over a communication link). Finally, a number of point-to-point protocols at the network, transport, and physical layers are discussed. There are many similarities between the point-to-point protocols at these different layers, and it is desirable to discuss them together before addressing the more complex network-wide protocols for routing, flow control, and multiaccess control. The treatment of physical links in Section 2.2 is a brief introduction to a very large topic. The reason for the brevity is not that the subject lacks importance or inherent interest, but rather, that a thorough understanding requires a background in linear system theory, random processes, and modem communication theory. In this section we pro­ vide a sufficient overview for those lacking this background and provide a review and perspective for those with more background. 37 38 Point-to-Point Protocols and Links Chap. 2 In dealing with the physical layer in Section 2.2, we discuss both the actual com­ munication channels used by the network and whatever interface modules are required at the ends of the channels to transmit and receive digital data (see Fig 2.1).
    [Show full text]
  • High-Level Data Link Control
    ELEC3030 (EL336) Computer Networks S Chen High-Level Data Link Control • This class of data link layer protocols includes High-level Data Link Control (HDLC), Link Access Procedure Balanced (LAPB) for X.25, Link Access Procedure for D-channel (LAPD) for ISDN, and Logic Link Control (LLC) for FDDI • The frame format is: Flag Address Control Data FCS Flag Note that address and control bits 8 8 8 variable 16 8 can be extended to 16 bits, so bit position 12 3 4 5 6 7 8 N(S)=send sequence number N(R)=receive sequence number that sequence number is 7-bit Information: 0 N(S) P/F N(R) S=supervisory function bits P/F • Frame flag: 01111110, so bit Supervisory: 1 0 S N(R) M=unumbered function bits stuffing is used Unumbered: 1 1 M P/F M P/F=poll/final bit • Address: For multipoint operation, it is used to identify the terminal that transmits or receives the frame and, in point-to-point link, it is used to distinguish Commands from Responses (2nd bit for C/R: 0/1). The address is now extended to 16 bits (1st bit indicates long/short 16/8 bits) • Checksum: FCS contains the remainder of a 16-bit CRC calculation of the frame. It may be extended to 32 bits, using a 32-bit CRC • Control: Three types of frames, I, S and U frames. The old protocol uses a sliding window with 3-bit sequence number and the maximum window size is N = 7. The control field is now extended to 16 bits with 7-bit sequence number 60 ELEC3030 (EL336) Computer Networks S Chen HDLC (continue) • I-frames: carry user data.
    [Show full text]
  • International Civil Aviation Organization
    Guidance for the Implementation of National IP Networks INTERNATIONAL CIVIL AVIATION ORGANIZATION PROJECT RLA/06/901 GUIDANCE FOR THE IMPLEMENTATION OF NATIONAL DIGITAL NETWORKS THAT USE THE IP PROTOCOL, TO SUPPORT CURRENT AND FUTURE AERONAUTICAL APPLICATIONS Project RLA/06/901 Page 1 Guidance for the Implementation of National IP Networks The designations employed and the presentation of material in this publication do not imply the expression of any opinion whatsoever on the part of ICAO concerning the legal status of any country, territory, city or area or of its authorities, or concerning the delimination of its frontiers or boundaries. Project RLA/06/901 Page 2 Guidance for the Implementation of National IP Networks TABLE OF CONTENTS i. Table of Contents..................................................................................................................... 3 ii. Background.............................................................................................................................. 4 General Decision-Making Considerations ............................................................................... 5 Business ......................................................................................................................... 5 Industrial Support........................................................................................................... 5 Security Policies............................................................................................................. 5 Implementation .............................................................................................................
    [Show full text]
  • Chapter 5 Peer-To-Peer Protocols and Data Link Layer
    Chapter 5 Peer-to-Peer Protocols and Data Link Layer PART I: Peer-to-Peer Protocols Peer-to-Peer Protocols and Service Models ARQ Protocols and Reliable Data Transfer Flow Control Timing Recovery TCP Reliable Stream Service & Flow Control Chapter 5 Peer-to-Peer Protocols and Data Link Layer PART II: Data Link Controls Framing Point-to-Point Protocol High-Level Data Link Control Link Sharing Using Statistical Multiplexing Chapter Overview z Peer-to-Peer protocols: many protocols involve the interaction between two peers z Service Models are discussed & examples given z Detailed discussion of ARQ provides example of development of peer-to-peer protocols z Flow control, TCP reliable stream, and timing recovery z Data Link Layer z Framing z PPP & HDLC protocols z Statistical multiplexing for link sharing Chapter 5 Peer-to-Peer Protocols and Data Link Layer Peer-to-Peer Protocols and Service Models Peer-to-Peer Protocols zzz zzz z Peer-to-Peer processes execute layer-n protocol to provide service to n + 1 peer process n + 1 peer process layer-(n+1) z Layer-(n+1) peer calls SDU SDU layer-n and passes PDU Service Data Units n peer process n peer process (SDUs) for transfer z Layer-n peers exchange Protocol Data Units (PDUs) to effect transfer n – 1 peer process n – 1 peer process z Layer-n delivers SDUs to destination layer-(n+1) peer zzz zzz Service Models z The service model specifies the information transfer service layer-n provides to layer-(n+1) z The most important distinction is whether the service is: z Connection-oriented z Connectionless z Service model possible features: z Arbitrary message size or structure z Sequencing and Reliability z Timing, Pacing, and Flow control z Multiplexing z Privacy, integrity, and authentication Connection-Oriented Transfer Service z Connection Establishment z Connection must be established between layer-(n+1) peers z Layer-n protocol must: Set initial parameters, e.g.
    [Show full text]
  • Infrastructure Layers Dr
    Infrastructure Internet perspective Change in point of view Internet standards do not discuss Data Link + Physical Layers Hardware developers define standards Infrastructure Internet Layer Model Internet application Application Layers Expects Internet services from OS Internet Aware Local + remote ports Transport Service requirements Network End-to-end IP routing + forwarding Data Link Layer — hardware management Not Internet Infrastructure Physical Layer — hardware Aware Computer Networks — Hadassah College — Fall 2015 Infrastructure Layers Dr. Martin Land 1 Computer Networks — Hadassah College — Fall 2015 Infrastructure Layers Dr. Martin Land 2 Infrastructure Infrastructure Engineering perspective Economic perspective Infrastructure layers Enormous investment in existing equipment Bottom-up design physical bits Global network of hardware nodes + transmission lines Physical layer (PHY) Developed to provide many services Internet (IP-based unreliable connectionless) just one service Defines physical transmission of bits Exploits a physical technology Most developed before Internet Telegraph — 1794 Data Link layer (DL) defines management of Physical Layer Telephone — 1876 How to make physical technology do what we want Teletype modem — 1943 Infrastructure management Digital telephone — 1962 Delivering data messages — 10% of effort Internet opened to public — 1992 Making hardware work correctly — 90% of effort Hardware updates OAM = Operations+Administration+Maintenance Replacement of manufactured hardware Application assumes infrastructure
    [Show full text]
  • Analysis and Application of Frame Relay Dongyue Cheng,Guoyou Han,Yuanguo Pan Information Engineering College, Xining University of Technology, Qinghai, China
    Journal of Networking and Telecomunications （2018） Original Research Article Analysis and Application of Frame Relay Dongyue Cheng,Guoyou Han,Yuanguo Pan Information Engineering College, Xining University of Technology, Qinghai, China ABSTRACT Frame relay is developed from integrated services digital network, in 1984, recommended as the International Telegraph and telephone Consultative Committee (CCITT) standard, in addition, TIS the United States authorized by the American National Standards Institute Standards Committee also made some preliminary work on frame relay. Due to the optical fi ber network of the bit error rate (less than 10^-9) than early telephone network error rate (10^- 4~10^-5) is much lower, therefore can reduce some X.25 procedures, which can reduce processing time and improve network throughput. Frame relay is produced in this environment. Is provided by the frame relay data link layer and physical layer specifi cation, any higher-layer protocols are independent of the frame relay Protocol, therefore, greatly simplifies the implementation of frame relay. Frame Relay LAN interconnection is one of the main application, especially when the LAN interconnection over a wide area network, using frame relay can refl ect the low network delay, the advantages of low cost, high bandwidth utilization. Frame relay is an advanced WAN technologies is a form of group communication, except that it will be between X.25 packet switches in the network, error recovery, to prevent the obstruction of the process was simplifi ed. KEYWORDS: Frame Relay throughput WAN technology packet communication 1. Overview Frame relay is a provider of connectivity and the ability to support multiple protocols, multiple applications of WAN technology for communication between multiple locations, which defi nes the process that sends data in public data networks, belonging to high-performance, high-speed data connectivity technologies.
    [Show full text]
  • Les Mécanismes De Fiabilisation (Protocoles ARQ) Et Leur Adaptation Dans Les Réseaux Radiomobiles De 3G Robert Bestak
    Les mécanismes de fiabilisation (protocoles ARQ) et leur adaptation dans les réseaux radiomobiles de 3G Robert Bestak To cite this version: Robert Bestak. Les mécanismes de fiabilisation (protocoles ARQ) et leur adaptation dans les réseaux radiomobiles de 3G. Traitement du signal et de l’image [eess.SP]. Télécom ParisTech, 2003. Français. tel-00005738 HAL Id: tel-00005738 https://pastel.archives-ouvertes.fr/tel-00005738 Submitted on 5 Apr 2004 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Thèse présentée pour obtenir le grade de docteur de l’Ecole Nationale Supérieure des Télécommunic ations Spécialité : Informatique et Réseaux Robert BESTAK Les mécanismes de fiabilisation (protocoles ARQ) et leur adaptation dans les réseaux radiomobiles de 3G Soutenue le 18 décembre 2003 devant le jury composé de Xavier LAGRANGE Président Khaldoun AL AGHA Rapporteurs Laurent TOUTAIN Philippe MARTINS Examinateurs Boris SIMAK Jérôme BROUET Invités Rémy ROGACKI Philippe GODLEWSKI Directeur de thèse A mes parents v Remerciements Tout d’abord, je tiens à remercier mon directeur de thèse le professeur Philippe Godlewski. Ses conseils et ses critiques constructives m’ont beaucoup apporté tout au long de ces années. Je lui suis très reconnaissant pour sa patience et ses efforts à me guider durant ma formation scientifique.
    [Show full text]
  • UNIT II DATA-LINK LAYER & MEDIA ACCESS Introduction – Link-Layer
    UNIT II DATA-LINK LAYER & MEDIA ACCESS Introduction – Link-Layer Addressing – DLC Services – Data-Link Layer Protocols – HDLC – PPP - Media Access Control - Wired LANs: Ethernet - Wireless LANs – Introduction – IEEE 802.11, Bluetooth – Connecting Devices. 2.1 Introduction What is DLL (Data Link Layer)? The Data Link Layer is the second layer in the OSI model, above the Physical Layer, which ensures that the error free data is transferred between the adjacent nodes in the network. It breaks the datagram passed down by above layers and converts them into frames ready for transfer. This is called Framing. It provides two main functionalities Reliable data transfer service between two peer network layers Flow Control mechanism which regulates the flow of frames such that data congestion is not there at slow receivers due to fast senders. 2.2 LINK-LAYER ADDRESSING In a connectionless internetwork such as the Internet we cannot make a datagram reach its destination using only IP addresses. The reason is that each datagram in the Internet, from the same source host to the same destination host, may take a different path. The source and destination IP addresses define the two ends but cannot define which links the datagram should pass through. Three Types of addresses Some link-layer protocols define three types of addresses: unicast, multicast, and broadcast. Unicast Address Each host or each interface of a router is assigned a unicast address. Unicasting means one-to-one communication. A frame with a unicast address destination is destined only for one entity in the link. A3:34:45:11:92:F1 Multicast Address Some link-layer protocols define multicast addresses.
    [Show full text]
  • An Overview on Integrated Localization and Communication Towards 6G Zhiqiang Xiao and Yong Zeng, Member, IEEE
    1 An Overview on Integrated Localization and Communication Towards 6G Zhiqiang Xiao and Yong Zeng, Member, IEEE Abstract—While the fifth generation (5G) cellular system is information of mobile terminals is expected to play an in- being deployed worldwide, researchers have started the investiga- creasingly important role in future wireless networks. While tion of the sixth generation (6G) mobile communication networks. the deployment of 5G networks is ongoing, researchers around Although the essential requirements and key usage scenarios of 6G are yet to be defined, it is believed that 6G should be the world have already started the investigation on the sixth able to provide intelligent and ubiquitous wireless connectivity generation (6G) mobile communication targeting for network with Terabits per second (Tbps) data rate and sub-millisecond 2030, with various visions proposed [2]–[7]. For example, it (sub-ms) latency over three-dimensional (3D) network coverage. was envisioned that 6G should achieve “ubiquitous wireless To achieve such goals, acquiring accurate location information intelligence” [5], for providing users smart context-aware of the mobile terminals is becoming extremely useful, not only for location-based services but also for improving wireless services through wireless connectivity anywhere in the world. communication performance in various ways such as channel This renders that acquiring the accurate real-time location estimation, beam alignment, medium access control, routing, information of users becomes more critical
    [Show full text]
  • Trillium 3G Wireless Software White Paper | Radisys
    White Paper | Feburary 2010 Trillium 3G Wireless Software By Ravi Raj Bhat, Vice President of Engineering This white paper presents an overview of technology trends in the wireless CONTENTS market, a historical overview of the evolving wireless technologies. The paper also presents Radisys’ Trillium software solutions which 3G Wireless Market Drivers pg. 1 enable wireless communications and Internet infrastructure equipment Existing Mobile Networks pg. 2 manufacturers to develop 3G network elements for quick and efficient deployment. Next Generation Mobile Networks pg. 2 Third Generation (3G) Wireless Networks pg. 4 3G Wireless Market Drivers Interworking with 2G and 2G+ Wireless Telecommunications service providers and network operators have embraced Networks pg.6 third generation (3G) wireless standards in order to address emerging user demands and to provide new services. The concept of 3G wireless technology Comparison of 2G and 3G Mobile Networks pg. 7 represents a shift from voice-centric services to multimedia-oriented (voice, Trillium 3G Wireless Solutions pg. 8 data, video, fax) services. In addition, heavy demand for remote access to personalized data is fueling development of applications, such as the Wireless Application Protocol (WAP) and multimedia management, to complement the 3G protocols. Complementary standards, such as Bluetooth, will enable interoperability between a mobile terminal (phone, PDA etc.) and other electronic devices, such as a laptop/desktop and peripherals, providing added convenience to the consumer and allowing for the synchronization and uploading of information at all times. The third generation of mobile communications greatly enhances the implementation of sophisticated wireless applications. Users will be able to utilize personal, location-based wireless information and interactive services.
    [Show full text]
  • Switched Communication Networks
    Module 4 Switched Communication Networks Version 2 CSE IIT, Kharagpur Lesson 4 X.25 Version 2 CSE IIT, Kharagpur Special Instructional Objective On completion of this lesson, the student will be able to: • State the key features of X.25 • Explain the frame format of X.25 • Specify the function of the Packet layer of X.25 • State the limitations of X.25 4.4.1 Introduction In the early 1970's there were many data communication networks (also known as Public Networks), which were owned by private companies, organizations and governments agencies. Since those public networks were quite different internally, and the interconnection of networks was growing very fast, there was a need for a common network interface protocol. In 1976 X.25 was recommended as the desired protocol by the International Consultative Committee for Telegraphy and Telephony (CCITT) called the International Telecommunication Union (ITU) since 1993. X.25 is a standard for WAN communications that defines how connections between user devices and network devices are established and maintained. X.25 is designed to operate effectively regardless of the type of systems connected to the network. It is typically used in the packet-switched networks (PSNs) of common carriers, such as the telephone companies. Subscribers are charged based on their use of the network. 4.4.2 X.25 Devices and Protocol Operation X.25 network devices fall into three general categories: data terminal equipment (DTE), data circuit-terminating equipment (DCE), and packet-switching exchange (PSE) as shown in Fig. 4.4.1. Data terminal equipment (DTE) devices are end systems that communicate across the X.25 network.
    [Show full text]
  • Frame Relay/ATM PVC Service Interworking Implementation Agreement FRF.8.1
    Frame Relay/ATM PVC Service Interworking Implementation Agreement FRF. 8.1 Frame Relay Forum Technical Committee February, 2000 Note: The user’s attention is called to the possibility that implementation of the frame relay implementation agreement contained herein may require the use of inventions covered by patent rights held by third parties. By publication of this frame relay implementation agreement the Frame Relay Forum makes no representation that the implementation of the specification will not infringe on any third party rights. The Frame Relay Forum take no position with respect to any claim that has been or may be asserted by any third party, the validity of any patent rights related to any such claims, or the extent to which a license to use any such rights may not be available. Editor: Doug O'Leary Bell Atlantic For more information contact: The Frame Relay Forum Suite 307 39355 California Street Fremont, CA 94538 USA Phone: +1 (510) 608-5920 FAX: +1 (510) 608-5917 E-Mail: [email protected] WWW: http://www.frforum.com Copyright © Frame Relay Forum 2000. All Rights Reserved. This document and translations of it may be copied and furnished to others, and works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Frame Relay Forum, except as needed for the purpose of developing Frame Relay standards (in which case the procedures for copyrights defined by the Frame Relay Forum must be followed), or as required to translate it into languages other than English.
    [Show full text]