ATM Configuration and Management Manual

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "ATM Configuration and Management Manual"

Transcription

1 ATM Configuration and Management Manual Abstract This manual describes how to configure, operate, and manage the ATM subsystem on an HP NonStop S-series server. The manual includes descriptions of the Subsystem Control Facility (SCF) commands used with the ATM subsystem and a quick-reference section showing the command syntax. Product Version ATM G06 Supported Release Version Updates (RVUs) This manual supports G06.21 and all subsequent RVUs until otherwise indicated in a new edition. Part Number Published March 2004

2 Document History Part Number Product Version Published ATM G06 May ATM G06 June ATM G06 November ATM G06 September ATM G06 March 2004

3 ATM Configuration and Management Manual Glossary Index Figures Tables What s New in This Manual ix Manual Information ix New and Changed Information About This Manual xi Who Should Use This Manual What s in This Manual xi Where to Get More Information Notation Conventions xii Abbreviations xvii 1. Configuration Quick Start Task Summary 1-1 Assumptions 1-1 Task 1: Logging On to the NonStop S-Series Server 1-2 Task 2: Creating the ASM Process 1-2 Task 3: Adding an Adapter 1-3 Task 4: Configuring the ATM Address 1-3 Task 5: Starting the ATM LINE 1-3 Task 6: Starting the ATMSAP Object 1-4 Task 7: Adding the Permanent Virtual Circuit (PVC) Object Overview of the ATM Subsystem The Asynchronous Transfer Mode (ATM) Protocol 2-1 ATM Cells 2-3 ATM Standards Supported 2-4 Architecture of the ATM Subsystem 2-4 System-Level Processes and Libraries 2-5 ATM Service Providers 2-5 ATM Clients 2-6 ATM Subsystem Management 2-6 ATM Subsystem Manager (ASM) 2-7 ATM Manager Process (AMP) 2-8 ix xi xii Hewlett-Packard Company i

4 Contents 2. Overview of the ATM Subsystem (continued) 2. Overview of the ATM Subsystem (continued) Driver/Interrupt Handler (DIH) 2-9 ATM ADAPTER 2-10 Interim Local Management Interface (ILMI) 2-10 ATM ATMSAPs 2-11 ATM LINE 2-11 ATM NULL 2-11 ATM PVC 2-11 ATM SUBSYS 2-11 ATM SVC Configuring the ATM Subsystem Before You Configure 3-1 Configuring the NonStop S-Series Server 3-1 Configuration Forms 3-2 Configuration File 3-4 Configuration Quick Start 3-5 Step 1: Create and Start the ASM Process 3-5 ADD PROCESS Command 3-5 START PROCESS Command 3-8 Verifying the ASM Process 3-9 Examples 3-9 Step 2: Create and Start the ATM Adapter 3-10 ADD ADAPTER Command 3-10 Example 3-13 START ADAPTER Command 3-14 Example 3-14 Step 3: Configure the ATM Address and Start the Line 3-14 ALTER LINE Command 3-14 START LINE Command 3-17 Step 4: Start the ATMSAP Object 3-18 START ATMSAP Command 3-18 Example 3-18 Step 5: Create and Start the PVC Object 3-18 ADD PVC Command 3-18 Example 3-19 START PVC Command 3-19 Example 3-19 ii

5 Contents 4. SCF Commands 4. SCF Commands Overview 4-1 Subsystem Control Point (SCP) 4-3 SCF Commands 4-3 How SCF Works 4-4 SCF Objects 4-5 General SCF Command Format 4-6 Commands That Have No Object Type or Object Name 4-6 Commands That Have an Object Type and Object Name 4-6 Commands That Have a SUB Parameter 4-6 SCF Object States 4-7 Using SCF 4-7 Running SCF 4-7 Ending an SCF Session 4-10 Modes of Operation 4-10 Input Sources 4-12 Setting the Initial Input Source 4-12 Changing the Input Source 4-12 Output Destinations 4-13 Setting the Initial Output Destination 4-13 Changing the Output Destination 4-13 Logging Input and Output to a File 4-14 Entering SCF Commands 4-14 Using the SCF HELP Command 4-14 SCF Menu-Mode Help 4-15 ATM Subsystem SCF Commands 4-16 Sensitive and Nonsensitive Commands 4-17 SCF Object Hierarchy 4-17 SCF Object States 4-18 Generic Processes 4-19 ABORT Command 4-20 ABORT ADAPTER Command 4-20 ABORT ATMSAP Command 4-22 ABORT LINE Command 4-23 ABORT PVC Command 4-24 ABORT SUBSYS Command 4-25 ABORT SVC Command 4-26 ADD Command 4-27 ADD ADAPTER Command 4-27 iii

6 Contents 4. SCF Commands (continued) 4. SCF Commands (continued) ADD PVC Command 4-32 ALTER Command 4-33 ALTER ADAPTER Command 4-33 ALTER LINE Command 4-37 ALTER PVC Command 4-40 DELETE Command 4-41 DELETE ADAPTER Command 4-41 DELETE PVC Command 4-42 DUMP Command 4-43 DUMP ADAPTER Command 4-43 INFO Command 4-44 INFO ADAPTER Command 4-45 INFO ATMSAP Command 4-50 INFO LINE Command 4-53 INFO PROCESS Command 4-56 INFO PVC Command 4-57 INFO SUBSYS Command 4-58 INFO SVC Command 4-59 NAMES Command 4-60 NAMES ADAPTER Command 4-60 NAMES ATMSAP Command 4-61 NAMES LINE Command 4-62 NAMES PROCESS Command 4-63 NAMES PVC Command 4-63 NAMES SUBSYS Command 4-64 NAMES SVC Command 4-64 START Command 4-65 START ADAPTER Command 4-65 START ATMSAP Command 4-67 START LINE Command 4-68 START PVC Command 4-69 START SUBSYS Command 4-70 STATS Command 4-71 STATS ATMSAP Command 4-71 STATS LINE Command 4-72 STATS PROCESS Command 4-74 STATS PVC Command 4-77 STATS SVC Command 4-78 iv

7 Contents 4. SCF Commands (continued) 4. SCF Commands (continued) STATUS Command 4-80 STATUS ADAPTER Command 4-80 STATUS ATMSAP Command 4-84 STATUS LINE Command 4-85 STATUS PROCESS Command 4-87 STATUS PVC Command 4-91 STATUS SUBSYS Command 4-92 STATUS SVC Command 4-96 TRACE Command 4-97 TRACE ADAPTER Command 4-98 TRACE PROCESS Command TRACE SUBSYS Command VERSION Command VERSION ADAPTER Command VERSION PROCESS Command VERSION SUBSYS Command A. SCF Command Summary B. ATM Event Messages 100 B B B B B B B B B B B B B B B B B B-15 v

8 Contents B. ATM Event Messages (continued) B. ATM Event Messages (continued) 603 B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B-54 C. Tracing for QIO TRACE Command C-1 TRACE ADAPTER Command C-1 vi

9 Contents D. ATM Error Codes D. ATM Error Codes ATM Driver Error Codes D-1 ATM Signaling Error Codes D-3 ATM API Error Codes D-3 ATM Network Error Code D-5 Glossary Index Figures Tables Figure 2-1. ATM Cell Structure 2-3 Figure 2-2. ATM Subsystem Architecture 2-5 Figure 2-3. SCF Interface to the ATM Subsystem 2-6 Figure 2-4. Relationship Between ATM SCF Objects and the ATM3SA 2-7 Figure 2-5. ATM Subsystem Manager (ASM) Process 2-8 Figure 2-6. ATM Manager Process (AMP) 2-9 Figure 2-7. Driver/Interrupt Handler (DIH) 2-10 Figure 3-1. ATM3SA Configuration Form (sample entries) 3-3 Figure 4-1. SCF and SCP Overview 4-2 Figure 4-2. Online Help Menu Hierarchy 4-15 Figure 4-3. SCF Object Hierarchy 4-18 Table i. Summary of Contents xi Table 4-1. SCF Commands and Objects 4-16 Table 4-2. Sensitive and Nonsensitive Commands 4-17 Table 4-3. Possible Object States for ATM Objects 4-19 Table 4-4. select-spec for an ADAPTER Object Table 4-5. select-spec for a PROCESS Object Table 4-6. select-spec for a SUBSYS Object vii

10 Contents viii

11 What s New in This Manual Manual Information Abstract ATM Configuration and Management Manual This manual describes how to configure, operate, and manage the ATM subsystem on an HP NonStop S-series server. The manual includes descriptions of the Subsystem Control Facility (SCF) commands used with the ATM subsystem and a quick-reference section showing the command syntax. Product Version ATM G06 Supported Release Version Updates (RVUs) This manual supports G06.21 and all subsequent RVUs until otherwise indicated in a new edition. Part Number Published March 2004 Document History Part Number Product Version Published ATM G06 May ATM G06 June ATM G06 November ATM G06 September ATM G06 March 2004 New and Changed Information Since product names are changing over time, this publication might contain both HP and Compaq product names. Product names in graphic representations are consistent with the current product interface. Other changes include: Removed references to $zhome as an infile in: Task 2: Creating the ASM Process on page 1-2 Configuration File on page 3-4 ix

12 What s New in This Manual New and Changed Information Examples on page 3-9 Corrected the ASM Process in Task 2: Creating the ASM Process on page 1-2. x

13 About This Manual This manual describes how to configure, operate, and manage the ATM subsystem on a NonStop S-series server. The manual includes detailed descriptions of the SCF commands used with the ATM subsystem and a quick-reference section showing the command syntax. Who Should Use This Manual This manual is written for anyone who is responsible for installing, configuring, managing, or monitoring the ATM subsystem on a NonStop S-series server. Note. NonStop S-series refers to the hardware that makes up the server. G-series refers to the software that runs on the server. What s in This Manual Table i summarizes the contents of this manual. Table i. Summary of Contents Section Title This section... 1 Configuration Quick Start Explains how to set up the initial ATM processes, objects, and adapters on a NonStop S-series server. 2 Overview of the ATM Subsystem 3 Configuring the ATM Subsystem Describes the components that make up the ATM subsystem. Provides configuration information for the ATM subsystem and describes the current configuration restrictions. 4 SCF Commands Provides a description and complete syntax for the SCF commands applicable to the ATM subsystem along with examples of how an user might use those commands. A SCF Command Summary Provides a quick reference to the syntax of the SCF commands for the ATM subsystem. B ATM Event Messages Describes event messages that can be returned from the ATM subsystem. C Tracing for QIO Describes the TRACE command, which supports ADAPTER, PROCESS, and SUBSYS objects for the ATM subsystem. D ATM Error Codes Describes the ATM subsystem error codes. This manual also contains a glossary of technical terms and abbreviations used throughout the text. xi

14 About This Manual Where to Get More Information Where to Get More Information Depending on the tasks you are performing, you might need the following manuals: OSM Migration Guide OSM User s Guide QIO Configuration and Management Manual TCP/IPv6 Configuration and Management Manual TSM Online User Guide Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.c italic computer type. Italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. Items not enclosed in brackets are required. For example: pathname xii

15 About This Manual General Syntax Notation [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X D ] address { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON OFF } Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF ON SAVEABEND } Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address [, new-value ] [ - ] { } An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char " Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "[" repetition-constant-list "]" xiii

16 About This Manual Notation for Messages Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: $process-name.#su-name Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [, attribute-spec ]!i and!o. In procedure calls, the!i notation follows an input parameter (one that passes data to the called procedure); the!o notation follows an output parameter (one that returns data to the calling program). For example: CALL CHECKRESIZESEGMENT ( segment-id!i, error ) ;!o!i,o. In procedure calls, the!i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ;!i,o!i:i. In procedure calls, the!i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes. For example: error := FILENAME_COMPARE_ ( filename1:length!i:i, filename2:length ) ;!i:i!o:i. In procedure calls, the!o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum!i, [ filename:maxlen ] ) ;!o:i Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. xiv

17 About This Manual Notation for Messages Bold Text. Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE?123 CODE RECEIVED: The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: proc-name trapped [ in SQL in SQL file system ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object Operator Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK Failed } xv

18 About This Manual Notation for Management Programming Interfaces % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: % %B %H2F P=%p-register E=%e-register Notation for Management Programming Interfaces This list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual. UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type!r.!o. The!r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING.!r The!o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32.!o Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE). The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. xvi

19 About This Manual Abbreviations Abbreviations The following list defines abbreviations and acronyms used in this manual. Both industry-standard terms and HP terms are included. Because this list covers ATM subsystem as a whole, not all of the terms given here are used in this particular manual. AAL. ATM Adaptation Layer AMP. ATM Management Process API. Application Program Interface ARP. Address Resolution Protocol ASM. ATM Subsystem Manager ATM. Asynchronous Transfer Mode (a type of LAN, WAN, or both) ATMSAP. ATM Service Access Point CLP. Cell Lost Priority DCT. Destination Control Table DFC. Data Forwarding Count DFT. Data Forward Timer DIH. Driver/Interrupt Handler DSM. Distributed Systems Management EMS. Event Management Service E4SA. Ethernet 4-port ServerNet adapter FTP. File Transfer Protocol HEC. Header Error Control IETF. Internet Engineering Task Force ILMI. Interim Local Management Interface IP. Internet Protocol ITU-T. International Telecommunications Union-Telecommunication Sector LAN. Local Area Network xvii

20 About This Manual Abbreviations LLC. Logical Link Control MAC. Media Access Control MIB. Management Information Base NNI. Network-Node Interface NSAP. Network Service Access Point PIN. Process Identification Number PPD. Process-Pair Directory PVC. Permanent Virtual Circuit RFC. Request for Comment SAP. Service Access Point SAR. Segmentation and reassembly SCF. Subsystem Control Facility SCP. Subsystem Control Point SDU. Service Data Unit SLSA. ServerNet LAN Systems Access SM. Shared Memory Interface SMLIB. Shared Memory Library SONET. Synchronous Optical Network SVC. Switched Virtual Circuit SWAN. ServerNet Wide Area Network TCP. Transmission Control Protocol UBR. Unspecified Bit Rate UDP. User Datagram Protocol UME. UNI Management Entity UNI. User-Network Interface VC. Virtual Channel xviii

21 About This Manual Abbreviations VCI. Virtual Channel Identifier VP. Virtual Path VPI. Virtual Path Identifier WAN. Wide Area Network xix

22 About This Manual Abbreviations xx

23 1 Configuration Quick Start This section is a configuration quick start for the ATM subsystem. This procedure explains how to set up the initial ATM processes, objects, and adapters on a NonStop S-series server. To help you complete the configuration tasks quickly, this section recommends you accept the default values provided by the ATM subsystem. If you want to change your ATM configuration, or if you want to complete the initial configuration without using the default configuration values, refer to the appropriate sections of this manual. Task Summary Task 1: Logging On to the NonStop S-Series Server Task 2: Creating the ASM Process Task 3: Adding an Adapter Task 4: Configuring the ATM Address Task 5: Starting the ATM LINE Task 6: Starting the ATMSAP Object Task 7: Adding the Permanent Virtual Circuit (PVC) Object Assumptions At the beginning of the procedure, the NonStop S-series server is in the following state: The default software configuration is as shipped by manufacturing. The initial TSM or OSM configuration is complete. A third-party ATM switch has been installed and configured. The port used on the ATM switch to connect to the ATM adapter must be enabled by the Interim Local Management Interface (ILMI). If you do not use the ILMI feature, you must also make a note of the ATM address for manual registration. For more information, see Task 4: Configuring the ATM Address on page 1-3. The ServerNet LAN Systems Access (SLSA) subsystem has been defined and started with the generic configuration provided from manufacturing, and Ethernet 4-port ServerNet adapters (E4SAs) have been installed and started. The QIO subsystem is started. 1-1

24 Configuration Quick Start Task 1: Logging On to the NonStop S-Series Server Task 1: Logging On to the NonStop S-Series Server Log on to the NonStop S-series server using the super ID (SUPER.SUPER) and enter the correct password at the Password: prompt. > logon super.super Password: Task 2: Creating the ASM Process To add the ASM process to the ATM subsystem: 1. Use the SCF ADD PROCESS command to add the PROCESS to the ATM subsystem. -> add process $zzkrn.#zzatm, & name $zzatm, & program $system.system.atmasm, & primarycpu 0, & backupcpu 1, & autorestart 10, & startmode kernel, & priority 180, & defautvol $system.system, & outfile $zhome, & hometerm $zhome, & saveabend on, & startupmsg "<BCKP-CPU>" 2. To start the ASM process, use the Kernel subsystem SCF START PROCESS command. -> start process $zzkrn.#zzatm 3. To verify the ASM process has started successfully, enter the SCF STATUS PROCESS command. -> status process $zzkrn.#zzatm ATM Status PROCESS Name State PID Pri Trace SvrNetStatus $ZZATM STARTED 1, OFF ACCESSIBLE If the ASM process was not started successfully, the following message will be displayed: (Process does not exist) 1-2

25 Configuration Quick Start Task 3: Adding an Adapter Task 2 is required only when you configure the ATM subsystem for the first time. Task 3: Adding an Adapter To add an adapter to the ATM subsystem: 1. Fill out a configuration form for the adapter as described in Section 3, Configuring the ATM Subsystem. 2. Install the adapter in the system. For more information on how to install an ATM3SA ServerNet adapter, see the ATM Adapter Installation and Support Guide. 3. Use the SCF ADD ADAPTER command to add the adapter to the ATM subsystem. There is a 3-character limit on the name of the adapter. ->ADD ADAPTER $ZZATM.$AM1, LOCATION (1,1,53), ACCESSLIST (0,1) 4. Use the SCF START ADAPTER command to start the adapter. ->START ADAPTER $AM1 Task 4: Configuring the ATM Address This task is optional. If you allow the ILMI feature to automatically create the address, you do not need to manually set the address yourself. If you do not want to use the ILMI feature, you must configure the ATM address for each ATM adapter you are running on a NonStop S-series server. The ATM address is the one previously used when installing and configuring the third-party ATM switch. To configure the ATM address, use the SCF ALTER LINE command. -> ALTER LINE $AM1,ATMADDR (isonsap:%h4700dd01272b4a ) Task 5: Starting the ATM LINE Once you have configured the ATM address, you must start the LINE using the SCF START LINE command. Use the SCF START LINE command to start the LINE object. ->START LINE $AM1 1-3

26 Configuration Quick Start Task 6: Starting the ATMSAP Object Task 6: Starting the ATMSAP Object The ATMSAP object must be started to complete your ATM subsystem configuration. Note. The LINE and ATMSAP objects are created automatically by the ASM. To start the ATMSAP object, use the SCF START ATMSAP command. ->START ATMSAP $AM1.#IP Task 7: Adding the Permanent Virtual Circuit (PVC) Object The PVC object must be added using the SCF ADD PVC command. 1. To add the PVC object, use the SCF ADD PVC LINE command. ->ADD PVC $AM1.#IP.PVC01, VPI 1, VCI To start the PVC object, use the SCF START PVC command. ->START PVC $AM1.#IP.PVC01 1-4

27 2 Overview of the ATM Subsystem The ATM subsystem provides access to ATM networks from a NonStop S-series server. The ATM subsystem supports the ATM User-Network Interface (UNI) specification over a 155Mbps OC-3 Synchronous Optical Network (SONET) connection. The Asynchronous Transfer Mode (ATM) Protocol The ATM protocol is a packet-switched, broadband network architecture that uses a cell-relay mechanism for transmitting data, voice, and video information. ATM is organized into layers and planes. The layers define the services related to cell creation, channels and paths, and protocol translation between other communications services. 2-1

28 Overview of the ATM Subsystem The Asynchronous Transfer Mode (ATM) Protocol The layers are: Physical Layer ATM Layer ATM Adaptation Layer (AAL) Corresponds to layer 1 of the seven layer OSI reference model. This layer handles bit-timing and checks the validity of cells created and transmitted. Creates cell headers and trailers, defines virtual channels and paths and gives them unique identifiers, and multiplexes or demultiplexes cells. This layer is service-independent. Provides translation between ATM and other services (voice, video, or data) involved in transmission. AAL has four classes, which use five protocols, and two sublayers. The classes are: Class A used for constant bit-rate data and appropriate for the transmission of voice data. Class A uses the AAL 1 protocol. Class B used for variable bit-rate data and appropriate for the transmission of video data. Class B uses the AAL 2 protocol. Class C used for connection-oriented data transmissions. Class C uses the AAL 3 or AAL 5 protocol. Class D used for the connectionless data transmission. Class D uses the AAL 4 or AAL 5 protocol. The two sublayers are: Convergence sublayer provides the interface for the various services. Segmentation and reassembly (SAR) sublayer, packages variable-sized packets into fixed-size cells at transmission and repackages them at reception. The plane specifies domains of activity in the protocol. The planes in the ATM protocol are: Control plane. Calls and connection are established and maintained on the control plane. User plane. Users exchange data on the user plane. Management plane. Network and layer management occurs on the management plane. The management plane also coordinates the planes and manages resources for the layers. The ATM protocol also has two interfaces: the UNI and the network-node interface (NNI). 2-2

29 Overview of the ATM Subsystem ATM Cells The UNI connects an end user to the network through an ATM switch or other device, thus supplying network access to the end user. The NNI connects nodes within a network to each other and provides network routing. ATM Cells ATM cells consist of a 5-octet header and 48-octet data or payload section. The 48-octet payload is a SAR protocol data unit (SAR PDU) to which the header is attached. Most of the bits in the header are used for path and channel identification. The header also contains a cell lost priority (CLP) bit and a header error control (HEC) field. The cells are not byte-oriented, and a header field can extend over byte boundaries. Within a cell, bit order goes from left to right, and across octets bit order goes down as octets go up.. Figure 2-1. ATM Cell Structure Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Generic Flow Control Virtual Path Identifier 1 Virtual Path Identifier Virtual Channel Idenfitier 2 Virtual Channel Idenfitier 3 Virtual Channel Idenfitier Payload Type CLP 4 Header Error Control 5 Payload 6 Payload 52 Payload 53 VST201.vsd 2-3

30 Overview of the ATM Subsystem ATM Standards Supported ATM Standards Supported ATM UNI Specification: ATM forum Version 3.0 and Version 3.1 Request for Comment (RFC) 1577: Classical Internet Protocol (IP) and Address Resolution Protocol (ARP) over ATM Architecture of the ATM Subsystem The ATM subsystem is made up of software processes and hardware components, libraries, and services including: System-level processes and libraries ATM (Asynchronous Transfer Mode) service providers ATM clients ATM subsystem management ATM subsystem SCF objects ATM Subsystem Manager (ASM) ATM Manager Process (AMP) Signaling Manager Driver Interrupt Handler Adapters Lines ATMSAPs PVCs Switched Virtual Circuit (SVCs) Hardware: ATM ServerNet adapters (ATM3SA) 2-4

31 Overview of the ATM Subsystem System-Level Processes and Libraries Figure 2-2 shows the relationship between the elements of the ATM subsystem. These elements are described in the following subsections. Figure 2-2. ATM Subsystem Architecture QIO Subsystem TCP/IP AMP ASM ATM Drivers and DIH ServerNet SAN Adapter SVC PVC Adapter SVC PVC VST202.vsd System-Level Processes and Libraries The ATM subsystem uses the shared-memory segment provided by the QIO subsystem to move the ownership of data between processes. (For more information about QIO, see the QIO Configuration and Management Manual.) The subsystem also uses QIO-based driver/interrupt handlers (DIHs) to communicate to the appropriate adapter type over the ServerNet SAN. The driver controls the ServerNet adapters through a set of system-library routines accessible by each process that needs to use the ATM subsystem. ATM Service Providers ATM (Asynchronous Transfer Mode) service providers are processes that use the ATM subsystem to send and receive data on ATM networks attached to the system. TCP/IP is the only ATM service provider currently supported. 2-5

32 Overview of the ATM Subsystem ATM Clients QIO API clients are protocol subsystems that communicate with the ATM service provider directly through QIO. Currently, these are: Expand connecting through the QIO application program interface (API) to TCP/IP in order to provide Expand/IP capability Transmission Control Protocol/Internet Protocol (TCP/IP) to provide connectivity to a TCP/IP network ATM Clients ATM clients are processes, user applications, or subsystems that use the ATM subsystem and related ATM service providers to connect to the ATM network attached to a NonStop S-series server. ATM Subsystem Management SCF is the interface that manages the processes and objects of the ATM subsystem. Figure 2-3 shows the SCF interface to the ATM subsystem. For more information about SCF, see the SCF Reference Manual for G-Series RVUs. For a description of the SCF commands, object hierarchy, and object states for the ATM subsystem, see Section 4, SCF Commands. Figure 2-3. SCF Interface to the ATM Subsystem Terminal Application Process SCF Command File SCF Log File SCP ($ZNET) $ZZATM VST203.vsd 2-6

33 Overview of the ATM Subsystem ATM Subsystem Manager (ASM) Note. Programmatic management of the ATM subsystem through the Subsystem Programmatic Interface (SPI) is not supported The SCF objects for the ATM subsystem consist of manager and monitor processes and several other objects that correspond to components of the ATM adapters that connect the ATM network to the server. The process and monitor objects correspond to the processes that manage (ASM) and monitor (AMPs) the ATM subsystem through SCF. The SCF objects related to the ATM adapters are the PROCESS, ADAPTER, LINE, ATMSAP, PVC and SVC objects. Figure 2-4 shows the relationship between the ATM SCF objects as they correspond to a ServerNet adapter. Figure 2-4. Relationship Between ATM SCF Objects and the ATM3SA ATM ServerNet Adapter ATM Subsystem Manager ($ZZATM) ADAPTER SUBSYS (ASM) ATM Line ATM Management Process LINE PROCESS (AMP) SVC PVC ATMSAP VST204.vsd Note. The dashed line in Figure 2-4 indicates the logical connections between objects. ATM Subsystem Manager (ASM) The ATM subsystem processes manage and control the ATM subsystem. The subsystem manager process is the ASM process. The SUBSYS object represents the ASM. The ASM process ($ZZATM) is the central point of management for all ATM connections in an NonStop S-series server. The ASM process runs as a process pair and can only run in processors 0 and 1 (the same processors as the system disk). ASM performs the following tasks: 2-7

34 Overview of the ATM Subsystem ATM Manager Process (AMP) Accepts all Distributed Systems Management (DSM) requests from the SCF product module through the Subsystem Control Point (SCP) Starts each manager process (AMPs) in each processor and maintains each process persistently across failures Handles the assignment of ADAPTERs to specific AMP processes Figure 2-5. ATM Subsystem Manager (ASM) Process CPU 0 CPU 1 NSK Persistence Manager SCF SCP Primary ASM Backup ASM AMP AMP Drivers and DIH ATM Drivers and DIH ServerNet SAN ServerNet SAN Adapter Adapter Adapter Adapter VST205.vsd ATM Manager Process (AMP) The AMP is a set of control processes in the ATM subsystem. The PROCESS object represents an AMP residing in a particular processor. The ASM process creates a manager in each processor defined in the ACCESSLIST attribute at system initialization and when an adapter is added. If a manager process fails, ASM restarts it. Each AMP performs the following functions: Initializes the QIO interface to the ATM3SA Provides configuration information to the ATM3SA Creates data structures representing all of the adapters, lines, and ATMSAPs Handles error reporting from the DIHs 2-8

35 Overview of the ATM Subsystem Driver/Interrupt Handler (DIH) AMP names are defined by $ZZATM. The AMP name is composed of the letter Z followed by the adapter name and one hexadecimal digit between 1 and F (identifies the processor number in which the AMP is running). For example, $ZAM11. Figure 2-6. ATM Manager Process (AMP) CPU 0 CPU 1 NSK Persistence Manager SCF SCP Primary ASM Backup ASM AMP AMP Drivers and DIH ATM Drivers and DIH ServerNet SAN ServerNet SAN Adapter Adapter Adapter Adapter VST206.vsd Driver/Interrupt Handler (DIH) The DIH provides an interface to the ATM adapter for clients performing I/O transfers between a NonStop S-series server and an ATM adapter. Figure 2-7 on page 2-10 shows the relationship of the DIH and the ATM subsystem. 2-9

36 Overview of the ATM Subsystem ATM ADAPTER Figure 2-7. Driver/Interrupt Handler (DIH) CPU 0 TCP/IP CPU 1 TCP/IP AMP QIO Subsystem QIO Subsystem AMP ATM Drivers and DIH ATM Drivers and DIH ServerNet SAN Adapter VST207.vsd ATM ADAPTER The ADAPTER object represents an ATM3SA adapter. One ADAPTER object is specified for each ATM adapter. The ADAPTER object is created using the SCF ADD ADAPTER command. Adapter names have the form $adapter-name, where adapter-name consists of up to three alphanumeric characters with a leading alphabetic character; for example, $AM1. The name of the adapter also defines the name of the ATM LINE. Note. $ZZATM is specified only for the ADD command. Interim Local Management Interface (ILMI) ILMI on the adapter implements the ILMI functions described in the ATM UNI 3.0/3.1 specification. The two major functions are: ILMI participates in the address registration with the ATM switch. You no longer need to manually enter the ATM address using the SCF ALTER LINE command. ILMI can be used to monitor the configuration and status of the adapter by issuing SNMP commands from the switch. It is unlikely that you will want to do this because the SCF interface can give you similar information. 2-10

37 Overview of the ATM Subsystem ATM ATMSAPs ATM ATMSAPs The ATMSAP object represents a service access point (SAP) for native-mode clients. Native-mode clients, such as TCP/IP, register to the service-access points. ATMSAP objects are created by the subsystem after the ADAPTER has been started. Currently, the only ATMSAP object is #IP. ATMSAP names have the form $line-name.#atmsap-name, where $line-name is the name of the ATM logical line. #ATMSAP-name is the name of the ATMSAP. The ATMSAP-name consists of up to seven alphanumeric characters with a leading alphabetic character; for example, $AM1.#IP. The names are predefined by the adapter. The ATMSAP object is subordinate to the LINE object. ATM LINE The LINE object represents the ATM line or link connected to the ATM adapter. The LINE object is created by the subsystem when an ADAPTER object is added to the subsystem. The LINE receives its name from the ADAPTER object. The LINE object is subordinate to the ADAPTER object. ATM NULL The null object means that no object type was specified. ATM PVC The PVC object represents a permanent virtual circuit. PVCs are created by using the SCF ADD PVC command. PVC names have the form $line-name.#atmsap-name.pvc-name. $line-name is the name of the ATM line to whom the PVC is subordinate. #atmsap-name is the name of the SAP to which service is being provided. pvc-name is the name assigned by the adapter to identify the circuit. The pvc-name consists of up to eight alphanumeric characters with a leading alphabetic character; for example, $AM1.#IP.PVC0. Note. Although the PVC object name includes the name of the ATMSAP, the PVC object is not subordinate to the ATMSAP. The naming format shows only that there is a fixed relationship between a PVC and an ATMSAP. ATM SUBSYS The SUBSYS object represents the ASM. The ASM runs as a process pair and is added to the system that uses the $ZZKRN subsystem. 2-11

38 Overview of the ATM Subsystem ATM SVC The name of the subsystem manager is $ZZATM. ATM SVC The SVC object represents a switched virtual circuit. SVCs are created when an ATM circuit is established. SVC names have the format $line-name. #atmsap-name.svc-name. $line-name is the name of the ATM line to whom the SVC is subordinate. $atmsap-name is the name of the SAP to which service is being provided. svc-name is the name assigned by the adapter to identify the circuit. For example: $AM1.#IP.SVC00001 Note. Although the SVC object name includes the name of the ATMSAP, the SVC object is not subordinate to the ATMSAP. The naming format shows only that there is a fixed relationship between a SVC and an ATMSAP. 2-12

39 3 Configuring the ATM Subsystem This section describes the configuration of the ATM subsystem on a NonStop S-series server. It also describes the prerequisites to getting started and provides a configuration quick start that takes you through each step of the configuration. For information on configuring TCP/IP over the ATM subsystem, see the TCP/IPv6 Configuration and Management Manual. Before You Configure Before you can configure and start the ATM subsystem, you previously must have configured and started a NonStop S-series server and several underlying processes and subsystems. Before you attempt to start a line between the NonStop S-series server and the external environment, you must install and configure a third-party ATM switch, connecting it on one side to the ATM adapter and on the other side to an external network. Configuring the NonStop S-Series Server Before you configure the ATM subsystem: 1. Check that the NonStop S-series server is configured and started by the system generation (SYSGENR) program. For more information on planning and configuring the NonStop S-series server, see the NonStop S-Series Planning and Configuration Guide. 2. Check that the $ZPM persistence manager process is started. $ZPM starts and maintains persistence of SCF subsystem managers; starts, stops, and (optionally) restarts generic processes; and coordinates system load and processor reload activities. 3. Check that the $ZZLAN subsystem manager process is started. $ZZLAN configures local area network (LAN) connections and facilities. 4. Check that the $ZZSTO subsystem manager process is started. $ZZSTO configures all storage devices such as disk and tape. 5. Check that the $ZZKRN subsystem manager process is started. $ZZKRN configures the X and Y fabrics, all system attributes, and generic processes. For more information, see the SCF Reference Manual for the Kernel Subsystem. 3-1

40 Configuring the ATM Subsystem Configuration Forms 6. Check that the $ZNET subsystem manager process is started. $ZNET configures the SCP management process. 7. Check that the QIO subsystem is started. QIO is preconfigured and started during the system-load sequence as a generic process. Generic processes are part of the SCF Kernel subsystem ($ZZKRN). For more information about generic processes, see the SCF Reference Manual for the Kernel Subsystem. QIO subsystem configuration is described in the QIO Configuration and Management Manual. 8. Check that the TSM or OSM processes are running. For more information, see the TSM or OSM manuals and online help. Configuration Forms Before you configure the ATM subsystem, you need to complete a configuration form for each ATM3SA adapter as described in the NonStop S-Series Planning and Configuration Guide. You need the information on the configuration form for your configuration. Figure 3-1 on page 3-3 shows a sample completed ATM3SA Configuration Form. For each ATM3SA: Enter the name of the system in the System Name field. Enter the group number for this enclosure in the Group Number field. Enter the slot number of this ATM3SA in the Slot Number field. ATM3SAs can be installed in slots 53 and 54. Because there is one module in a system enclosure, the module number 1, is already indicated on the form. Complete the ATM port information block for each port on the adapter. Enter the ATM address to be assigned to the port in the ATM address field. The address is the one used by the third-party switch connected to this particular ATM adapter. Optionally, to save time and effort, you can leave this address blank and allow the ILMI feature to perform automatic address registration. Enter the adapter name. Enter the line name. Enter the numbers of the processors that will have access to the Access List field. When you complete this form, enter today s date in the Date field. 3-2

41 Configuring the ATM Subsystem Configuration Forms Figure 3-1. ATM3SA Configuration Form (sample entries) ATM ServerNet Adapter (ATM3SA) Configuration Form System Name Date \Case1 05/15/98 Group Module Slot 53 ATM ATM Address: h4700dd01272b4a ServerNet ATM Adapter Adapter Name: LINE Name: $AM1 $AM1 SAC Access List: 0, 1, 2, 3 VST301.vsd 3-3

42 Configuring the ATM Subsystem Configuration File Configuration File You can use a TACL macro to configure the ATM subsystem or use SCF interactively. The following TACL macro configures and starts an ATM3SA adapter. For the SCF steps, see Configuration Quick Start on page 3-5.?TACL MACRO PUSH #INLINEPREFIX + SET VARIABLE #INLINEPREFIX + SCF /INLINE, OUT [#MYTERM], NAME/ + ALLOW ALL ERRORS + ASSUME PROCESS $ZZKRN + ABORT PROCESS #ZZATM + DELETE PROCESS #ZZATM + ADD PROCESS #ZZATM, NAME $ZZATM, & PROGRAM $SYSTEM.SYSTEM.ATMASM, & PRIMARYCPU 0, & BACKUPCPU 1, & AUTORESTART 10, & STARTMODE KERNEL, & PRIORITY 180, & DEFAULTVOL $SYSTEM.SYSTEM & OUTFILE $ZHOME & HOMETERM $ZHOME & SAVEABEND ON & STARTUPMSG "<BCKP-CPU>" & START PROCESS #ZZATM + EXIT POP #INLINEPREFIX PUSH #INLINEPREFIX + SET VARIABLE #INLINEPREFIX + SCF /INLINE, OUT [#MYTERM], NAME/ + TIMEOUT ADD ADAPTER $ZZATM.$AM1, LOCATION (1,1,53), ACCESSLIST (1,2) + START ADAPTER $AM1 + ALTER LINE $AM1, ATMADDRESS & (ISONSAP:%%H4700DD01272B4A ) + START LINE $AM1 + START ATMSAP $AM1.#IP + ADD PVC $AM1.#IP.PVC1, VPI 1, VCI START PVC $AM1.#IP.PVC1 + EXIT POP #INLINEPREFIX 3-4

43 Configuring the ATM Subsystem Configuration Quick Start Configuration Quick Start To configure ATM ServerNet connections: Task Step 1: Create and Start the ASM Process on page 3-5. Step 2: Create and Start the ATM Adapter on page Step 3: Configure the ATM Address and Start the Line on page Step 4: Start the ATMSAP Object on page 3-18 Step 5: Create and Start the PVC Object on page 3-18 Tool Used SCF interface to the Kernel subsystem SCF interface to the ATM subsystem SCF interface to the ATM subsystem SCF interface to the ATM subsystem SCF interface to the ATM subsystem Note. The SCF syntax in this subsection which you use to configure ATM ServerNet connections is not the complete syntax for the described SCF commands. For more information about the SCF command syntax for other subsystems, see the appropriate SCF reference manual. Step 1: Create and Start the ASM Process Before you can start the ATM subsystem process, you must create and start one ASM process on each NonStop S-series server where you are connecting an ATM adapter. Use the SCF ADD PROCESS and START PROCESS commands. Note. Step 1 is required only when you configure the ATM subsystem for the first time. ADD PROCESS Command Create the ASM process as a generic process. Use the Kernel subsystem SCF ADD PROCESS command: ADD PROCESS $ZZKRN.#gpname, AUTORESTART n, BACKUPCPU n, DEFAULTVOL $vol [.subvol ], HOMETERM $device [.#subdevice], INFILE {$device [[$vol.]subvol.]filename }, NAME $name, OUTFILE {$device [[$vol.]subvol.]filename, PRIMARYCPU n, PRIORITY n, PROGRAM [[$vol.]subvol.]filename, SAVEABEND { ON OFF }, STARTMODE { KERNEL SYSTEM APPLICATION MANUAL DISABLED }, STARTUPMSG "text", TYPE { SUBSYSTEM-MANAGER OTHER } 3-5

44 Configuring the ATM Subsystem ADD PROCESS Command $ZZKRN.#gpname specifies the name of the generic process controlled by the Kernel subsystem manager process ($ZZKRN). AUTORESTART n optionally specifies the number of times that the $ZPM persistence manager tries to restart this process within a 10-minute interval after an abnormal termination. (For example, the process abends or stops by a means other than the ABORT command.) If n is 0 (the default), the process is not automatically restarted. If n is 1 through 10, the process is restarted as many as n times in 10 minutes. If n is greater than 0, the process is restarted after a processor failure without decrementing the value of n. For more information about using the AUTORESTART attribute, see the SCF Reference Manual for the Kernel Subsystem. BACKUPCPU n optionally specifies the processor in which this process should start its backup process. For more information on specifying this attribute, see the SCF Reference Manual for the Kernel Subsystem. You can specify this attribute only if you also specify the PRIMARYCPU attribute and do not specify the CPU attribute. The variable n can be from 0 through the maximum number of processors (except that the BACKUPCPU value specified cannot be the same number as the PRIMARYCPU value). Default: None. DEFAULTVOL $vol [.subvol ] optionally specifies the default volume and subvolume information sent to this process (in the startup message) when it is started. If not specified, the startup default volume and subvolume is $SYSTEM.NOSUBVOL. HOMETERM $device [.#subdevice] optionally specifies the home terminal to use when starting this process. If not specified, the process has the same home terminal as $ZPM has when it starts the process. 3-6

45 Configuring the ATM Subsystem ADD PROCESS Command INFILE {$device [[$vol.]subvol.]filename } optionally specifies the input file or process name sent to this process (in the startup message) when it is started. NAME $ZZATM specifies the process name of this process, as recognized by TACL. This attribute is required. The length limitation is six characters. If you specify the CPU attribute and more than one processor, the length of the NAME value cannot exceed three characters (after the dollar-sign) because the two-digit processor number is appended to the process name. OUTFILE {$device [[$vol.]subvol.]filename optionally specifies the output file or process name sent to this process (in the startup message) when the process is started. PRIMARYCPU n optionally specifies the processor in which this process starts its primary process. n can be from 0 through the maximum number of processors. The PRIMARYCPU value cannot be the same as the BACKUPCPU value. PRIORITY n optionally specifies the priority to use when starting this process. The range is 1 through 199. If not specified, the priority is the same as the current SCF session minus 1. If a process must be higher than 199, it must set its own priority through call PROCESS_SETINFO_. PROGRAM [[$vol.]subvol.]filename specifies the program object file for this process to use when started. If you specify the SYSTEM subvolume, SCF searches for the file first on the SYSTEM subvolume, then searches on the current SYSnn subvolume. SAVEABEND { ON OFF } optionally specifies whether a saveabend file is created if this process stops abnormally. This attribute overrides the SAVEABEND setting in the PROGRAM file for this process. ON specifies that a saveabend file is created automatically if the process ends abnormally. 3-7

HP NonStop TCP/IPv6 Configuration and Management Manual

HP NonStop TCP/IPv6 Configuration and Management Manual HP NonStop TCP/IPv6 Configuration and Management Manual Abstract This manual describes how to configure and manage the HP NonStop TCP/IPv6 subsystem on HP NonStop S-series servers and HP Integrity NonStop

More information

Spooler Plus Programmer s Guide

Spooler Plus Programmer s Guide Spooler Plus Programmer s Guide Abstract This manual describes the Spooler Plus subsystem, its uses, and its applications. This guide is intended for application programmers who want to use the Spooler

More information

OSI/FTAM Responder Manual

OSI/FTAM Responder Manual OSI/FTAM Responder Manual Abstract This manual describes the operation of the Compaq Open Systems Interconnection/File Transfer, Access and Management (OSI/FTAM) responder and its virtual filestore (VFS).

More information

Virtual Hometerm Subsystem (VHS) Manual

Virtual Hometerm Subsystem (VHS) Manual Virtual Hometerm Subsystem (VHS) Manual Abstract This manual describes the Compaq NonStop Virtual Hometerm Subsystem (VHS). VHS acts as a virtual home terminal for applications by emulating a 6530 terminal.

More information

DSM/SCM Messages Manual

DSM/SCM Messages Manual DSM/SCM Messages Manual Abstract This manual provides cause, effect, and recovery information for messages and errors that you might encounter while using the Distributed Systems Management/Software Configuration

More information

OSI /MHS SCF Reference Manual

OSI /MHS SCF Reference Manual OSI /MHS SCF Reference Manual Abstract This manual describes how to use the Subsystem Control Facility (SCF) interactive interface to configure and control a Compaq Open System Interconnection/Message

More information

HP NonStop TCP/IPv6 Migration Guide

HP NonStop TCP/IPv6 Migration Guide HP NonStop TCP/IPv6 Migration Guide Abstract Version This manual discusses the differences between HP NonStop TCP/IP and NonStop TCP/IPv6 and the differences between Parallel Library TCP/IP and NonStop

More information

EMS FastStart Manual. Abstract. Product Version. Supported Releases. Part Number Published Release ID

EMS FastStart Manual. Abstract. Product Version. Supported Releases. Part Number Published Release ID EMS FastStart Manual Abstract This manual provides information about the EMS FastStart program including installation, event message design, instructions for running the program, and customizing EMS FastStart

More information

Native Inspect Manual

Native Inspect Manual Native Inspect Manual Abstract This manual describes how to use the symbolic command-line debugger Native Inspect for debugging TNS/E native processes and snapshot files on HP NonStop Series TNS/E systems.

More information

DLL Programmer s Guide for TNS/E Systems

DLL Programmer s Guide for TNS/E Systems DLL Programmer s Guide for TNS/E Systems Abstract This guide describes how application programmers can use the DLL facilities provided on TNS/E systems and recommends good practices in using them. Product

More information

Object Code Accelerator Manual

Object Code Accelerator Manual Object Code Accelerator Manual Abstract This manual describes how to use the Object Code Accelerator (OCA) to optimize TNS object code for HP TNS/E systems. OCA processes files for the Guardian environment.

More information

Mid-Range Library Media Manager Installation and User s Guide

Mid-Range Library Media Manager Installation and User s Guide Mid-Range Library Media Manager Installation and User s Guide Abstract This guide describes how to install and use the Mid-Range Library Media Manager software. It includes information about connection

More information

HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide

HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide Abstract This manual describes the installation, configuration, and management of RSC/MP software on a HP NonStop system acting

More information

Common Run-Time Environment (CRE) Programmer s Guide

Common Run-Time Environment (CRE) Programmer s Guide Common Run-Time Environment (CRE) Programmer s Guide Abstract This manual describes the Common Run-Time Environment (CRE), a set of run-time services that enable system and application programmers to write

More information

A T M. Cell Switched Technology. not SMDS. Defacto Standard Multimedia capable Use with SONET or SDH. Fixed Length - 53 bytes. DigiPoints Volume 1

A T M. Cell Switched Technology. not SMDS. Defacto Standard Multimedia capable Use with SONET or SDH. Fixed Length - 53 bytes. DigiPoints Volume 1 A T M Cell Switched Technology Fixed Length - 53 bytes not SMDS Defacto Standard Multimedia capable Use with SONET or SDH SCTE VA 12.1 SONET Optical Carrier (OC) Rates and SDH Synchronous Transport Module

More information

HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide

HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide Abstract This manual explains how to migrate databases and applications from HP NonStop SQL/MX 2.3.x to SQL/MX Release 3.0

More information

Measure User s Guide Abstract Product Version Supported Release Version Updates (RVUs) Part Number Published

Measure User s Guide Abstract Product Version Supported Release Version Updates (RVUs) Part Number Published Measure User s Guide Abstract This manual describes how to use the Measure performance monitor to collect and examine data, through either a command interface or programmatic interface. This manual is

More information

ATM Technology in Detail. Objectives. Presentation Outline

ATM Technology in Detail. Objectives. Presentation Outline ATM Technology in Detail Professor Richard Harris Objectives You should be able to: Discuss the ATM protocol stack Identify the different layers and their purpose Explain the ATM Adaptation Layer Discuss

More information

HP NonStop Server Guide for BEA WebLogic Server 8.1

HP NonStop Server Guide for BEA WebLogic Server 8.1 HP NonStop Server Guide for BEA WebLogic Server 8.1 Abstract This manual describes the installation, configuration, and management of the BEA WebLogic Server on HP Integrity NonStop NS-series servers.

More information

NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator s Guide

NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator s Guide NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator s Guide Abstract NonStop Servlets for JavaServer Pages (NSJSP) is a container that runs Java servlets and JavaServer Pages (JSPs)

More information

! Cell streams relating to different media types are multiplexed together on a statistical basis for transmission and switching.

! Cell streams relating to different media types are multiplexed together on a statistical basis for transmission and switching. Asynchronous Transfer Mode (ATM) Networks! All source media is first broken down into a stream of fixed sized units known as cells.! Cell streams relating to different media types are multiplexed together

More information

NonStop Server for Java Message Service User s Manual

NonStop Server for Java Message Service User s Manual NonStop Server for Java Message Service User s Manual Abstract NonStop Server for Java Message Service (NSJMS) is an implementation of Sun Microsystems Java Message Service (JMS) API on HP NonStop S-series

More information

Asynchronous Transfer Mode

Asynchronous Transfer Mode ATM Asynchronous Transfer Mode CS420/520 Axel Krings Page 1 Protocol Architecture (diag) CS420/520 Axel Krings Page 2 1 Reference Model Planes User plane Provides for user information transfer Control

More information

ATM. Asynchronous Transfer Mode. these slides are based on USP ATM slides from Tereza Carvalho. ATM Networks Outline

ATM. Asynchronous Transfer Mode. these slides are based on USP ATM slides from Tereza Carvalho. ATM Networks Outline ATM Asynchronous Transfer Mode these slides are based on USP ATM slides from Tereza Carvalho 1 ATM Networks Outline ATM technology designed as a support for ISDN Definitions: STM and ATM Standardization

More information

Tandem OSI/AS and OSI/TS Supplement (Includes RFC-1006 Support)

Tandem OSI/AS and OSI/TS Supplement (Includes RFC-1006 Support) Networking and Data Communications Library Tandem OSI/AS and OSI/TS Supplement (Includes RFC-1006 Support) Abstract Part Number 107751 Edition This manual supplements the C30.08/D10 editions of the seven-manual

More information

CPEG 514. Lecture 11 Asynchronous Transfer Mode (ATM) CPEG 514

CPEG 514. Lecture 11 Asynchronous Transfer Mode (ATM) CPEG 514 Lecture 11 Asynchronous Transfer Mode () Outline Introduction Virtual Circuit Setup PVC vs. SVC Quality of Service and Congestion Control IP over and Frame Relay interworking Network (integrated voice,

More information

HP NonStop Server Guide for BEA WebLogic Server 9.2

HP NonStop Server Guide for BEA WebLogic Server 9.2 HP NonStop Server Guide for BEA WebLogic Server 9.2 Abstract This manual describes the installation, configuration, and management of the BEA WebLogic Server on HP Integrity NonStop NS-series servers.

More information

CROSSREF Manual. Tools and Utilities Library

CROSSREF Manual. Tools and Utilities Library Tools and Utilities Library CROSSREF Manual Abstract This manual describes the CROSSREF cross-referencing utility, including how to use it with C, COBOL 74, COBOL85, EXTENDED BASIC, FORTRAN, Pascal, SCREEN

More information

Part 5: Link Layer Technologies. CSE 3461: Introduction to Computer Networking Reading: Chapter 5, Kurose and Ross

Part 5: Link Layer Technologies. CSE 3461: Introduction to Computer Networking Reading: Chapter 5, Kurose and Ross Part 5: Link Layer Technologies CSE 3461: Introduction to Computer Networking Reading: Chapter 5, Kurose and Ross 1 Outline PPP ATM X.25 Frame Relay 2 Point to Point Data Link Control One sender, one receiver,

More information

ATM. Asynchronous Transfer Mode. (and some SDH) (Synchronous Digital Hierarchy)

ATM. Asynchronous Transfer Mode. (and some SDH) (Synchronous Digital Hierarchy) ATM Asynchronous Transfer Mode (and some SDH) (Synchronous Digital Hierarchy) Why use ATM? Circuit switched connections: After initial setup no processing in network nodes Fixed bit rates, fixed time delay

More information

Asynchronous Transfer Mode (ATM) Broadband ISDN (B-ISDN)

Asynchronous Transfer Mode (ATM) Broadband ISDN (B-ISDN) Asynchronous Transfer Mode (ATM) Broadband ISDN (B-ISDN) Petr Grygárek rek 1 ATM basic characteristics Integrates transfer of voice, video, data and other media using statistical al multiplexing ing multiplexes

More information

BROADBAND AND HIGH SPEED NETWORKS

BROADBAND AND HIGH SPEED NETWORKS BROADBAND AND HIGH SEED NETWORKS LAYERS The function and associated information of the planes is as follows: The reference model is composed of the following planes: Control lane manages the call and connection.

More information

HPE NonStop X Cluster Solution Manual

HPE NonStop X Cluster Solution Manual HPE NonStop X Cluster Solution Manual Part Number: 828081-003b Published: April 2017 Edition: L15.08 and subsequent L-series RVUs Contents About This Document...5 Supported Release Version Updates (RVUs)...

More information

Packet Switching - Asynchronous Transfer Mode. Introduction. Areas for Discussion. 3.3 Cell Switching (ATM) ATM - Introduction

Packet Switching - Asynchronous Transfer Mode. Introduction. Areas for Discussion. 3.3 Cell Switching (ATM) ATM - Introduction Areas for Discussion Packet Switching - Asynchronous Transfer Mode 3.3 Cell Switching (ATM) Introduction Cells Joseph Spring School of Computer Science BSc - Computer Network Protocols & Arch s Based on

More information

NonStop SOAP for Java User s Manual

NonStop SOAP for Java User s Manual NonStop SOAP for Java User s Manual Abstract This manual provides reference and user information for NonStop SOAP for Java, a product that runs on a Compaq NonStop server and provides Simple Object Access

More information

DataLoader/MX Reference Manual

DataLoader/MX Reference Manual DataLoader/MX Reference Manual Abstract This manual describes the features and functionality of the DataLoader/MX product, a tool to load HP NonStop SQL/MX, SQL/MP, and Enscribe databases. Product Version

More information

SNMP Subagent Programmer s Guide

SNMP Subagent Programmer s Guide Networking and Data Communications Library SNMP Subagent Programmer s Guide Abstract This manual explains how to use the NonStop SNMP (Simple Network Management Protocol) Subagent Toolkit. The Toolkit

More information

Module 10 Frame Relay and ATM

Module 10 Frame Relay and ATM Module 10 Frame Relay and ATM Lesson 35 ATM: Virtual Path, Virtual Channel. ATM Adaptation Layer (AAL) 10.3.1 VIRTUAL PATH AND VIRTUAL CHANNEL Connection between two endpoints is accomplished through virtual

More information

Switched Multimegabit Data Service (SMDS)

Switched Multimegabit Data Service (SMDS) CHAPTER 14 Switched Multimegabit Data Service (SMDS) Background Switched Multimegabit Data Service (SMDS) is a high-speed, packet-switched, datagram-based WAN networking technology used for communication

More information

Packet Switching. Hongwei Zhang Nature seems to reach her ends by long circuitous routes.

Packet Switching. Hongwei Zhang  Nature seems to reach her ends by long circuitous routes. Problem: not all networks are directly connected Limitations of directly connected networks: limit on the number of hosts supportable limit on the geographic span of the network Packet Switching Hongwei

More information

Advanced Internet Technologies

Advanced Internet Technologies Advanced Internet Technologies Chapter 2 ATM Dr.-Ing. Falko Dressler Chair for Computer Networks & Internet Wilhelm-Schickard-Institute for Computer Science University of Tübingen http://net.informatik.uni-tuebingen.de/

More information

William Stallings Data and Computer Communications 7 th Edition. Chapter 11 Asynchronous Transfer Mode

William Stallings Data and Computer Communications 7 th Edition. Chapter 11 Asynchronous Transfer Mode William Stallings Data and Computer Communications 7 th Edition Chapter 11 Asynchronous Transfer Mode Protocol Architecture Similarities between ATM and packet switching Transfer of data in discrete chunks

More information

Native Inspect Manual

Native Inspect Manual Native Inspect Manual Part Number: 528122-015R Published: November 2015 Edition: H06.23 and subsequent H-series RVUs, J06.12 and subsequent J-series RVUs, and L15.02 and subsequent L-series RVUs Copyright

More information

This chapter describes how to configure ATM on Cisco routers.

This chapter describes how to configure ATM on Cisco routers. Configuring ATM First Published: November 27, 2007 Last Updated: March 10, 2011 This chapter describes how to configure ATM on Cisco routers. Finding Feature Infmation Your software release may not suppt

More information

Distributed Data Processing (DDP-PPC) OSI Interface C Language

Distributed Data Processing (DDP-PPC) OSI Interface C Language !()+ OS 2200 Distributed Data Processing (DDP-PPC) OSI Interface C Language Programming Guide Copyright ( 1997 Unisys Corporation. All rights reserved. Unisys is a registered trademark of Unisys Corporation.

More information

HP NonStop ASAP Messages Manual

HP NonStop ASAP Messages Manual HP NonStop ASAP Messages Manual Abstract This manual documents the messages produced by the Availability Statistics and Performance Monitor (ASAP) an availability, state, and performance statistics collection

More information

Switched Multimegabit Data Service

Switched Multimegabit Data Service CHAPTER 14 Chapter Goals Tell how SMDS works, and describe its components. Describe the operational elements of the SMDS environment, and outline its underlying protocol. Discuss related technologies.

More information

nld Manual Abstract Product Version Supported Release Updates (RVUs) Part Number Published

nld Manual Abstract Product Version Supported Release Updates (RVUs) Part Number Published nld Manual Abstract This publication explains how to use the TNS/R native link editor nld (T6017), which links and changes object file attributes. Product Version nld D44 Supported Release Updates (RVUs)

More information

ATM Software Segmentation and Reassembly

ATM Software Segmentation and Reassembly Feature History Release Modification 12.2(2)XB Cisco 2600 Series T1/E1 ATM and Cisco 3660 T1 Inverse Multiplexing over ATM (IMA) ATM Adaption Layer 2 (AAL2) Support was introduced. 12.2(8)T This feature

More information

Guardian Procedure Errors and Messages Manual

Guardian Procedure Errors and Messages Manual Guardian Procedure Errors and Messages Manual Abstract This manual describes the Guardian messages for HP systems that use the HP NonStopTM operating system. The manual covers the following types of messages:

More information

ATM networks. C. Pham Université de Pau et des Pays de l Adour LIUPPA Laboratory

ATM networks. C. Pham Université de Pau et des Pays de l Adour LIUPPA Laboratory ATM networks C. Pham Université de Pau et des Pays de l Adour LIUPPA Laboratory http://www.univ-pau.fr/~cpham Congduc.Pham@univ-pau.fr Issues Driving LAN Changes Traffic Integration Voice, video and data

More information

StarKeeper II NMS SNMP Proxy Agent Guide

StarKeeper II NMS SNMP Proxy Agent Guide StarKeeper II NMS SNMP Proxy Agent Guide 255-114-761 Issue 1 Release 10.0 Copyright 1998 Lucent Technologies All Rights Reserved Printed in USA Datakit and StarKeeper are registered trademarks of Lucent

More information

HP Integrity NonStop BladeSystem Planning Guide

HP Integrity NonStop BladeSystem Planning Guide HP Integrity NonStop BladeSystem Planning Guide HP Part Number: 545740-08 Published: November 202 Edition: J06.3 and subsequent J-series RVUs Copyright 202 Hewlett-Packard Development Company, L.P. Legal

More information

TCP/IP Application Services (TAS) Mail Processor

TCP/IP Application Services (TAS) Mail Processor !()+ OS 2200 TCP/IP Application Services (TAS) Mail Processor User Guide Copyright ( 1997 Unisys Corporation. All rights reserved. Unisys is a registered trademark of Unisys Corporation. Level 6R1 September

More information

ATM PVC Bundle Enhancement MPLS EXP-Based PVC Selection

ATM PVC Bundle Enhancement MPLS EXP-Based PVC Selection ATM PVC Bundle Enhancement MPLS EXP-Based PVC Selection This document describes enhancements to the ATM virtual circuit (VC) bundle management feature, which allows you to configure multiple VCs that have

More information

ETSI TS V3.6.0 ( )

ETSI TS V3.6.0 ( ) TS 125 414 V3.6.0 (2000-12) Technical Specification Universal Mobile Telecommunications System (UMTS); UTRAN Iu Inteface Data Transport and Transport Signalling (3GPP TS 25.414 version 3.6.0 Release 1999)

More information

TCP/IP and the OSI Model

TCP/IP and the OSI Model TCP/IP BASICS TCP/IP and the OSI Model TCP/IP BASICS The network protocol of the Internet Composed of six main protocols IP Internet Protocol UDP User Datagram Protocol TCP Transmission Control Protocol

More information

MPLS AToM ATM AAL5 over MPLS

MPLS AToM ATM AAL5 over MPLS MPLS AToM ATM AAL5 over MPLS Feature History Release 12.0(10)ST 12.0(21)ST 12.0(22)S Modification This feature was introduced to support the Cisco 12000 Series router. This feature was updated to support

More information

Voice And Telephony over ATM: Status

Voice And Telephony over ATM: Status Voice And Telephony over ATM: Status Columbus, OH 43210 Jain@CIS.Ohio-State.Edu http://www.cis.ohio-state.edu/~jain/ March 1998 1 Overview VTOA: Protocol Stack and Services AAL: AAL1, AAL5, New AAL2 Interworking

More information

Chapter 2 - Part 1. The TCP/IP Protocol: The Language of the Internet

Chapter 2 - Part 1. The TCP/IP Protocol: The Language of the Internet Chapter 2 - Part 1 The TCP/IP Protocol: The Language of the Internet Protocols A protocol is a language or set of rules that two or more computers use to communicate 2 Protocol Analogy: Phone Call Parties

More information

Network Working Group Request for Comments: 2514 Category: Standards Track Cisco Systems K. Tesink Bellcore Editors February 1999

Network Working Group Request for Comments: 2514 Category: Standards Track Cisco Systems K. Tesink Bellcore Editors February 1999 Network Working Group Request for Comments: 2514 Category: Standards Track M. Noto 3Com E. Spiegel Cisco Systems K. Tesink Bellcore Editors February 1999 Definitions of Textual Conventions and OBJECT-IDENTITIES

More information

WAN Technologies (to interconnect IP routers) Mario Baldi

WAN Technologies (to interconnect IP routers) Mario Baldi WAN Technologies (to interconnect IP routers) Mario Baldi www.baldi.info WAN_Technologies - 1 Copyright: see page 2 Copyright Notice This set of transparencies, hereinafter referred to as slides, is protected

More information

COMP9332 Network Routing & Switching

COMP9332 Network Routing & Switching COMP9332 Network Routing & Switching Switching in IP Networks with MPLS http://www.cse.unsw.edu.au/~cs9332 1 Lecture Overview This lecture introduces the concept of switching, which allows faster processing

More information

Peer entities. Protocol Layering. Protocols. Example

Peer entities. Protocol Layering. Protocols. Example Peer entities Protocol Layering An Engineering Approach to Computer Networking Customer A and B are peers Postal worker A and B are peers Protocols A protocol is a set of rules and formats that govern

More information

LightSpeed1000 (w/ GigE and USB 2.0) OC-3/STM-1, OC-12/STM-4 Analysis and Emulation Card

LightSpeed1000 (w/ GigE and USB 2.0) OC-3/STM-1, OC-12/STM-4 Analysis and Emulation Card Wirespeed Record/Playback/ Processing of ATM, PoS, RAW, and Ethernet Traffic LightSpeed1000 (w/ GigE and USB 2.0) OC-3/STM-1, OC-12/STM-4 Analysis and Emulation Card x4 PCIExpress, USB 2.0, and Gigabit

More information

ITU-T I.150. B-ISDN asynchronous transfer mode functional characteristics

ITU-T I.150. B-ISDN asynchronous transfer mode functional characteristics INTERNATIONAL TELECOMMUNICATION UNION ITU-T I.150 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (02/99) SERIES I: INTEGRATED SERVICES DIGITAL NETWORK General structure General description of asynchronous

More information

Quality of Service Commands policy-map. This command has no default behavior or values.

Quality of Service Commands policy-map. This command has no default behavior or values. Quality of Service Commands policy-map policy-map To create or modify a policy map that can be attached to one or more interfaces to specify a service policy, use the policy-map global configuration command.

More information

Broadband Access Aggregation and DSL Configuration Guide, Cisco IOS XE Release 3S

Broadband Access Aggregation and DSL Configuration Guide, Cisco IOS XE Release 3S Broadband Access Aggregation and DSL Configuration Guide, Cisco IOS XE Release 3S Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408

More information

Networks 15.2 Multiplexing Technologies Access Networks 15.5 Common Peripheral Interfaces

Networks 15.2 Multiplexing Technologies Access Networks 15.5 Common Peripheral Interfaces Chapter 15 Computer and Multimedia Networks 15.11 Basics of Computer and Multimedia Networks 15.2 Multiplexing Technologies 15.3 LAN and WAN 15.4 Access Networks 15.5 Common Peripheral Interfaces 15.6

More information

Internet. 1) Internet basic technology (overview) 3) Quality of Service (QoS) aspects

Internet. 1) Internet basic technology (overview) 3) Quality of Service (QoS) aspects Internet 1) Internet basic technology (overview) 2) Mobility aspects 3) Quality of Service (QoS) aspects Relevant information: these slides (overview) course textbook (Part H) www.ietf.org (details) IP

More information

aaa authentication arap through atm sonet stm-1

aaa authentication arap through atm sonet stm-1 aaa authentication arap through atm sonet stm-1 aaa authentication arap, page 3 abr, page 6 atm, page 8 atm aal aal3 4, page 10 atm abr rate-factor, page 12 atm address-registration, page 14 atm arp-server,

More information

Distributed Data Processing (DDP-PPC) DCA Interface C Language

Distributed Data Processing (DDP-PPC) DCA Interface C Language !()+ OS 2200 Distributed Data Processing (DDP-PPC) DCA Interface C Language Programming Guide Copyright ( 1997 Unisys Corporation. All rights reserved. Unisys is a registered trademark of Unisys Corporation.

More information

Atalla Boxcar Reference Guide

Atalla Boxcar Reference Guide Atalla Boxcar Reference Guide Abstract This document describes Boxcar, its interface to the Atalla Network Security Processor, and the parameters used to start, initialize, and configure the Boxcar process.

More information

Chapter 8 ARP(Address Resolution Protocol) Kyung Hee University

Chapter 8 ARP(Address Resolution Protocol) Kyung Hee University Chapter 8 ARP(Address Resolution Protocol) 1 Logical address 8.1 Address Mapping The hosts and routers are recognized at the network level by their logical address Logical address is unique universal IP

More information

dba/m Database Manager V7.1 Installation and Operations Manual

dba/m Database Manager V7.1 Installation and Operations Manual dba/m Database Manager V7.1 Installation and Operations Manual Release 7.1 May 2005 dba/m Database Manager V7.1 Installation and Operations Manual 540155-001 Copyright Information Copyright 1996 2005 Genus

More information

Single-router APS for the Cisco Series Router

Single-router APS for the Cisco Series Router Single-router APS for the Cisco 12000 Series Router This feature provides 1+1 single-router automatic protection switching (SR-APS) for the Cisco 12000 series ISE ATM line cards (Engine 3) installed in

More information

HP Integrity NonStop NS-Series Planning Guide

HP Integrity NonStop NS-Series Planning Guide HP Integrity NonStop NS-Series Planning Guide Abstract This guide describes the Integrity NonStop NS-series system hardware and provides examples of system configurations to assist in planning for installation

More information

Configuring ATM SNMP Trap and OAM Enhancements

Configuring ATM SNMP Trap and OAM Enhancements Configuring ATM SNMP Trap and OAM Enhancements The ATM SNMP Trap and OAM Enhancements feature provides the ability to send Simple Network Management Protocol (SNMP) notifications for ATM permanent virtual

More information

HP NonStop SQL/MX Release 3.2 Installation and Upgrade Guide

HP NonStop SQL/MX Release 3.2 Installation and Upgrade Guide HP NonStop SQL/MX Release 3.2 Installation and Upgrade Guide HP Part Number: 691118-003 Published: May 2013 Edition: J06.14 and subsequent J-series RVUs; H06.25 and subsequent H-series RVUs Copyright 2013

More information

IBM Spectrum Protect for Databases Version Data Protection for Microsoft SQL Server Installation and User's Guide IBM

IBM Spectrum Protect for Databases Version Data Protection for Microsoft SQL Server Installation and User's Guide IBM IBM Spectrum Protect for Databases Version 8.1.4 Data Protection for Microsoft SQL Server Installation and User's Guide IBM IBM Spectrum Protect for Databases Version 8.1.4 Data Protection for Microsoft

More information

Computer Networks. Andrew S. Tanenbaum

Computer Networks. Andrew S. Tanenbaum Computer Networks Third Edition Andrew S. Tanenbaum 1 ; l Vrije Universiteit Amsterdam, The Netherlands For book and bookstore information Prentice Hall PTR Upper Saddle River, New Jersey 07458 CONTENTS

More information

frame-relay lmi-n391dte

frame-relay lmi-n391dte frame-relay lmi-n391dte frame-relay lmi-n391dte To set a full status polling interval, use the frame-relay lmi-n391dte interface configuration command. To restore the default interval value, assuming that

More information

APPENDIX F THE TCP/IP PROTOCOL ARCHITECTURE

APPENDIX F THE TCP/IP PROTOCOL ARCHITECTURE APPENDIX F THE TCP/IP PROTOCOL ARCHITECTURE William Stallings F.1 TCP/IP LAYERS... 2 F.2 TCP AND UDP... 4 F.3 OPERATION OF TCP/IP... 6 F.4 TCP/IP APPLICATIONS... 10 Copyright 2014 Supplement to Computer

More information

Unable to Connect to the Master Service Processors (MSPs) Over a Low-Level Link

Unable to Connect to the Master Service Processors (MSPs) Over a Low-Level Link Unable to Connect to the Master Service Processors (MSPs) Over a Low-Level Link Symptom Version Problem Fix Unable to connect to a master service processor (MSP) using either the OSM or TSM Low-Level Link,

More information

Asynchronous Transfer Mode

Asynchronous Transfer Mode CHAPTER 20 This chapter describes the level of support that Cisco ANA provides for ATM, as follows: Technology Description, page 20-1 Information Model Objects (IMOs), page 20-3 Vendor-Specific Inventory

More information

Safeguard Administrator s Manual

Safeguard Administrator s Manual Safeguard Administrator s Manual Part Number: 862340-003a Published: June 2017 Edition: L15.02, J06.03, H06.08, and G06.29, and later L-series, J-series, H-series, and G-series RVUs. 2011, 2017 Hewlett

More information

PS TEXT EDIT and PS TEXT FORMAT User s Guide

PS TEXT EDIT and PS TEXT FORMAT User s Guide Information Management Technology Library PS TEXT EDIT and PS TEXT FORMAT User s Guide Part Number 058060 Tandem Computers Incorporated Document History Edition Part Number Product Version OS Version Date

More information

HP X.25 for OpenVMS Security Guide

HP X.25 for OpenVMS Security Guide HP X.25 for OpenVMS Security Guide Order Number: AA Q2P2C TE July 2005 This manual explains how to set up, manage, and monitor X.25 Security to protect your X.25 system from unauthorized incoming calls

More information

8-Port OC-3 STM-1 ATM Line Card for Cisco Series Internet Routers

8-Port OC-3 STM-1 ATM Line Card for Cisco Series Internet Routers 8-Port OC-3 STM-1 ATM Line Card for Cisco 12000 Series Internet Routers Feature History Release 12.0(22)S 12.0(23)S Modification This feature was introduced on Cisco 12000 series Internet Routers. Software

More information

L-Series Application Migration Guide

L-Series Application Migration Guide L-Series Application Migration Guide Abstract This guide introduces the L-series application development and execution environments and explains how to migrate existing H- and J- series applications to

More information

Configuring Ethernet OAM, CFM, and E-LMI

Configuring Ethernet OAM, CFM, and E-LMI CHAPTER 39 Ethernet Operations, Administration, and Maintenance (OAM) is a protocol for installing, monitoring, and troubleshooting Ethernet networks to increase management capability within the context

More information

TEMPORARY DOCUMENT. Attached is a clean copy of Draft Recommendation X.84. TD 1143 Rev3 is the source document used to produce this clean version.

TEMPORARY DOCUMENT. Attached is a clean copy of Draft Recommendation X.84. TD 1143 Rev3 is the source document used to produce this clean version. INTERNATIONAL TELECOMMUNICATION UNION STUDY GROUP 17 TELECOMMUNICATION STANDARDIZATION SECTOR STUDY PERIOD 2001-2004 English only Original: English Question(s): 5/17 Geneva, 10-19 March 2004 Source: Title:

More information

Internet protocols, TCP/IP suite

Internet protocols, TCP/IP suite Internet protocols, TCP/IP suite S-72.353 March 20, 2000 L353_8.shw Slide 1 of 23 Layered structure of TCP/IP /D\HU 6HUYL FHV 6073 '16 KWWS )73 7(/1(7 7 &3 8 '3 193,3,& 03,3 $53 5$53 &60$&' 7RNHQ ULQJ

More information

Category: Standards Track May Default IP MTU for use over ATM AAL5. Status of this Memo

Category: Standards Track May Default IP MTU for use over ATM AAL5. Status of this Memo Network Working Group R. Atkinson Request for Comments: 1626 Naval Research Laboratory Category: Standards Track May 1994 Status of this Memo Default IP MTU for use over ATM AAL5 This document specifies

More information

NAME: (Exam :SECTION A) Notes: Any script without a name will receive no points. You must show the calculations for the descriptive questions.

NAME: (Exam :SECTION A) Notes: Any script without a name will receive no points. You must show the calculations for the descriptive questions. SAMPLE TEST from past EXAMS Exam3 Chapters: 14, 19, 21, 23, 24. Type of questions: multiple choices, Fill in the gaps, short answer questions YOU MUST BRING SCANTRON sheets for the multiple choices (4.5

More information

Technical Committee ATM

Technical Committee ATM Technical Committee ATM Data Exchange Interface (DXI) Specification af-dxi-0014.000 August, 1993 1993 The ATM Forum All Rights Reserved 1993 The ATM Forum. All Rights Reserved. No part of this publication

More information

Architectures of Communication Subsystems

Architectures of Communication Subsystems Architectures of Communication Subsystems Open System Interconnection Reference Model Computer Networks Lecture 2 http://goo.gl/pze5o8 Connection-Oriented versus Connectionless Communication 2 Connection-Oriented

More information

COMMUNICATING WITH VIRTUAL PATHS AND VIRTUAL CHANNELS

COMMUNICATING WITH VIRTUAL PATHS AND VIRTUAL CHANNELS COMMUNICATING WITH VIRTUAL PATHS AND VIRTUAL CHANNELS Rick Bubenik Mike Gaddis John DeHart Applied Research Laboratory Department of Computer Science Washington University St. Louis, Missouri 63130-4899

More information

Software Configuration of ATM ISE Line Cards for Cisco Series Routers

Software Configuration of ATM ISE Line Cards for Cisco Series Routers Software Configuration of ATM ISE Line Cards for Cisco 12000 Series Routers This feature module describes the software configuration for the Cisco 4-Port ATM Internet Services Engine (ISE) line cards in

More information

Cisco RF Switch Firmware Command Reference Guide

Cisco RF Switch Firmware Command Reference Guide Cisco RF Switch Firmware Command Reference Guide March 31, 2011 Cisco RF Switch Firmware Version 4.0 OL-15733-03 This document describes the cable-specific RF Switch Firmware and supporting command-line

More information