DOCSLIB.ORG

Digital Technical Journal, Volume 3, Number 3: Availability in Vaxcluster

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

• Availability in VAXcluster Systems • Network Performance and Adapters Digital Technical Journal Digital Equipment Corporation Volume 3 Number 3 Summer 1991 Editorial Jane C. Blake, Editor Kathleen M. Stetson, Associate Editor Leon Descoteaux, Associate Editor Circulation Catherine M. Phillips, Administrator Sherry L. Gonzalez Production Mildred R. Rosenzweig, Production Editor Margaret Burdine, Typographer Peter Woodbury, illustrator Advisory Board Samuel H. Fuller, Chairman Richard W. Beane Robert M. Glorioso Richard]. Hollingsworth John W. McCredie Alan G. Nemeth Mahendra R. Patel E Grant Saviers Victor A. Vyssotsky Gayn B. Winters The Digital Technicaljournal is published quarterly by Digital Equipment Corporation, 146 Main Street ML01-3/B68, Maynard, Massachusetts 01754-2571. Subscriptions to the journal are $40.00 for four issues and must be prepaid in U.S. funds. University and college professors and Ph.D. students in the electri­ cal engineering and computer science fields receive complimen­ tary subscriptions upon request. Orders, inquiries, and address changes should be sent to the Digital Technical journal at the published-by address. Inquiries can also be sent electronically to DTJ®CRL.DEC.COM. Single copies and back issues are available for $16.00 each from Digital Press of Digital Equipment Corporation, 12 Crosby Drive, Bedford, MA 01730-1493. Digital employees may send subscription orders on the ENET to RDVAX::JOURNAL or by interoffice mail to mailstop ML01-3/B68. Orders should include badge number, site location code, and address. Allemployees must advise of changes of address. Comments on the content of any paper are welcomed and may be sent to the editor at the published-by or network address. Copyright© 1991 Digital Equipment Corporation. Copying without fee is permitted provided that such copies are made for use in educational institutions by faculty members and are not dis­ tributed for commercial advantage. Abstracting with credit of Digital Equipment Corporation's authorship is permitted. All rights reserved. The information in the journal is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in the journal. ISSN 0898-901X Documentation Number EY-H890E-DP The following are tmdemarks of Digital Equipment Corporation: Cover Design Bl, CI, DEC, DECconcentmtor, DECdtm, DEC FDD!controller, Our cover graphic represents the shadowing, or replication, of DECnet, DELNl, DSA, DSSI, Digital, the Digital logo, HSC, LAT, Local Area VAXcluster, MSCI� RA, Rdb(VMS, TA, ULTRlX, UNIBUS, data on multiple physicaldisks in a cluster environment. VAX VAX, VAX DBMS, VAX MACRO, VAX RMS, VAX 6000, VAX 9000, VMS host-based volume shadowing pmvides the high data avail­ VAXcluster, VMS, VMS Volume Shadowing. ability required for applications such as transaction Motorola and 68000 are registered trademarks of Motorola, Inc. processing and is the subject of one of the papers in this issue. Book production was done by Digital's Database Publishing Group The cover was designed by Sandra Calef of Calef Associates. in Northboro, MA. I Contents 5 Fo reword Howard H. Hayakawa and George S. Hoff Availability in VAXcluster Systems Network Performance and Adapters 7 Design of VMS Volume Shadowing Phase II-Host-based Shadowing Scott H. Davis 16 Application Design in a VAXclusterSystem William E. Snaman, Jr. 27 New Availability Features of Local Area VAXcluster Systems Lee Leahy 36 Design of the DEC LANcontroller 400 Adapter Richard E. Stockdale and Judy B. We iss 48 The Architecture and Implementation of a High-performance FDDI Adapter Sat ish L. Rege 64 Performance Analysis of a High-speed FDDI Adapter Ramsesh S. Kalkunte 78 Performance Analysis of FDDI Raj Jain I Editor's Introduction fo r network delay detection and reduction, and fa il­ ure analysis in local area VA Xcluster systems. The fo cus then moves from VMS-Ievel concerns to the design of network adapters and performance measurement. The adapter described by Dick Stockdale and Judy We iss is the DEC LANcontroller 400, which connects systems based on Digital's XMI bus to an Ethernet LAN. This particular design improves on previous designs by transforming the adapter from a dumb to an intelligent adapter which can off- load the host. Consequently, the adapter supports systems that utilize the fu ll band­ Jane C. Blake width of Ethernet. The authors provide a system Editor overview, performance metrics, and a critical exam­ This issue of the Digital Te chnical jo urnalcontains ination of firmware-based design. a collection of papers on two general topics­ Like the LANcontroller400, the FDDicontroller400 VA Xcluster systems, and network adapters and per­ is an adapter that interfaces XMI-based systems to a formance. The first set of three papers describes LAN. However, as Satish Rege relates, this adapter new VMS VAX cluster developments and features; was required to transmit data 30 times faster than the second set addresses the topics of LAN adapter Ethernet adapters. Satish discusses the architec­ design and performance measurement techniques. ture and the choices designers made to address the A common theme across these papers is the devel­ problem of interfacing a parallel high-bandwidth opment of technologies fo r interconnecting sys­ CPU bus (XMI) to a serial fi ber-optic network bus tems that offer high data availability without (FDDJ). Their design choices included a three-stage sacrificing performance. pipeline approach to buffe ring that enables these VMS Vo lume Shadowing, described by Scott Davis, stages to proceed in an asynchronous fashion. is a means of ensuring dataavaila bility and integrity To ensure that the perfo rmance goals fo r the in VMS VA Xcluster systems. By maintaining multiple FDDicontroller would be met, a simulation model copies of data on separate devices, the volume was created. In his paper, Ram Kalkunte details the shadowing technique protects data from being modeling methodology, reviews components, and lost as the result of media deterioration or device presents simulation results. Ram describes how in failures. Scott discusses the advantages of the addition to perfo rmance projections, the model new design over controller-based shadowing and provided designers with buffe r sufficiency analysis explains how this fu lly distributed software makes and helped engineers analyze the functional cor­ a broad range of topologies suitable fo r shadowing. rectness of the adapter design. The growth capabilities and availability of VMS The high level of performance achieved by the VAXcluster systems are characteristics well suited FDDicontroller was driven by the high performance to applications with high-availability requirements. of the FDDI LA N itself- 100 megabits per second. Sanely Snaman first presents an overview of the Raj Jain's subject is performance measurement at VA Xcluster system architecture, including explana­ the level of the FDDI LAN. Raj describes the perfor­ tions of the layers, their purpose and function. He mance analysis of Digital's implementation of FDDI then gives practical insights into how the system and how various parameters affect system perfor­ implementation affects application design and mance. As part of his presentation of the modeling reviews the choices available to application design­ and simulation methods used, he shares guidelines ers in the areas of client-server computing and data fo r setting the value of one of the key parameters, sharing. target token rotation time, to optimize performance. The availability of applications and cluster con­ Raj has recently published a book on computer sys­ figurations is also enhanced by developments in a tems performance analysis, which is reviewed in new release of the VMS operating system. Lee Leahy the Further Readings section of this issue. describes a VMS feature that enables fail-over between multiple LA N adapters and compares this approach to a single-adapter implementation. He then discusses and gives examples of VMS features 2 Biographies I Scott H. Davis Consultant software engineer Scott Davis is the VMS Cluster Technical Director. He is involved in future VMS 1/0 subsystem, VAX cluster, and storage strategies and led the VMS Volume Shadowing Phase II and VMS mixed-interconnect VAX cluster 1/0 projects. Since joining Digital in 1979, Scott worked on RT-11 development and led various real-time operating systems pro­ jects. He holds a B.S. (1978, cum laude) in computer science and applied mathe­ matics from the State University of New Yo rk at Albany. Scott is a coinventor for four patents on the shadowing design. Raj Jain Raj Jain is a senior consulting engineer involved in the performance modeling and analysis of computer systems and networks, including VAX cluster, DECnet, Ethernet, and FDDI products. He holds a Ph.D. (1978) from Harvard University and has taught courses in performance analysis at M.l.T. A member of the Authors' Guild and senior member of IEEE, Raj has written over 25 papers and is listed in Who's Who in the Computer Industry, 1989. He is the author of The Art of Computer Sy stems Performance Analysis published recently by Wiley. Ram Kalkunte As a member of the VAX VMS Systems and Servers Group, senior engineer Ram Kalkunte worked on the development of the high­ performance XMI-to-FDDI adapter. Since joining Digital in 1987, he has also worked on various performance analysis and modeling projects. Ram received a B.E. (1984) in instrumentation engineering from Mysore University in India and an M.S. (1987) in electrical engineering from Worcester Polytechnic Institute. He has a pending patent related to dynamically arbitrating conflicts in a multipart memory controller. Lee Leahy Lee Leahy is a principal software engineer in the VAX cluster group in ALPHA/EVMS Development. He is currently the project leader of the Local Area VAX cluster development effort and was responsible fo r the final design and implementation of the multiple-adapter version of PEDRIVER.
Recommended publications
  • Digital Technical Journal, Number 3, September 1986: Networking

    Digital Technical Journal, Number 3, September 1986: Networking

    Netwo;king Products Digital TechnicalJournal Digital Equipment Corporation Number 3 September I 986 Contents 8 Foreword William R. Johnson, Jr. New Products 10 Digital Network Architecture Overview Anthony G. Lauck, David R. Oran, and Radia J. Perlman 2 5 PerformanceAn alysis andModeling of Digital's Networking Architecture Raj Jain and William R. Hawe 35 The DECnetjSNA Gateway Product-A Case Study in Cross Vendor Networking John P:.. �orency, David Poner, Richard P. Pitkin, and David R. Oran ._ 54 The Extended Local Area Network Architecture and LANBridge 100 William R. Hawe, Mark F. Kempf, and Alan). Kirby 7 3 Terminal Servers on Ethernet Local Area Networks Bruce E. Mann, Colin Strutt, and Mark F. Kempf 88 The DECnet-VAXProduct -A n IntegratedAp proach to Networking Paul R. Beck and James A. Krycka 100 The DECnet-ULTRIXSoftware John Forecast, James L. Jackson, and Jeffrey A. Schriesheim 108 The DECnet-DOS System Peter 0. Mierswa, David). Mitton, and Ma�ha L. Spence 117 The Evolution of Network Management Products Nancy R. La Pelle, Mark). Seger, and Mark W. Sylor 129 The NMCCjDECnet Monitor Design Mark W. Sylor 1 Editor's Introduction The paper by Bill Hawe, Mark Kempf, and AI Kirby reports how studies of potential new broad­ band products led to the development of the Extended LAN Architecture. The design of the LANBridge 100, the first product incorporating that architecture, is described, along with the trade-offs made to achieve high performance. The speed of communication between terminals and systems depends on how they are connected. Bruce Mann, Colin Strutt, and Mark Kempf explain how they developed the LAT protocol to connect terminals to hosts on an Ethernet.
  • The Design and Verification of the Alphastation 600 5-Series Workstation by John H

    The Design and Verification of the Alphastation 600 5-Series Workstation by John H

    The Design and Verification of the AlphaStation 600 5-series Workstation by John H. Zurawski, John E. Murray, and Paul J. Lemmon ABSTRACT The AlphaStation 600 5-series workstation is a high-performance, uniprocessor design based on the Alpha 21164 microprocessor and on the PCI bus. Six CMOS ASICs provide high-bandwidth, low-latency interconnects between the CPU, the main memory, and the I/O subsystem. The verification effort used directed, pseudorandom testing on a VERILOG software model. A hardware-based verification technique provided a test throughput that resulted in a significant improvement over software tests. This technique currently involves the use of graphics cards to emulate generic DMA devices. A PCI hardware demon is under development to further enhance the capability of the hardware-based verification. INTRODUCTION The high-performance AlphaStation 600 5-series workstation is based on the fastest Alpha microprocessor to date -- the Alpha 21164.[1] The I/O subsystem uses the 64-bit version of the Peripheral Component Interconnect (PCI) and the Extended Industry Standard Architecture (EISA) bus. The AlphaStation 600 supports three operating systems: Digital UNIX (formerly DEC OSF/1), OpenVMS, and Microsoft's Windows NT. This workstation series uses the DECchip 21171 chip set designed and built by Digital. These chips provide high-bandwidth, low-latency interconnects between the CPU, the main memory, and the PCI bus. This paper describes the architecture and features of the AlphaStation 600 5-series workstation and the DECchip 21171 chip set. The system overview is first presented, followed by a detailed discussion of the chip set. The paper then describes the cache and memory designs, detailing how the memory design evolved from the workstation's requirements.
  • Networks· Communications

    Networks· Communications

    - Networks· Communications, ;--___...........................................e e_e __ • • • • • • • • • • • • • • • • • • • • • • • • • • • • . ... • • • • • • • • • ~---- Local Area Transport (LAT) Architecture i Network Manager's Guide " wore~D~DD~D Local Area Transport (LAT) Arch itectu re Network Manager's Guide Order No. AA-OJ 188-TK July 1985 The Local Area Transport (LA T) Architecture Network Manager's Guide is intended for network managers and system managers. It contains information about the LAT architecture. This guide also in­ cludes information for configuring and managing LAT networks. SUPERSESSION/UPDATE INFORMATION: This is a revised manual. AA-DJ18B-TK First Printing, July 1985 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corpora­ tion assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital or its affiliated companies. Copyright © 1985 by Digital .Equipment Corporation The postage-prepaid Reader's Comments form on the last page of this document requests the user's critical evaluation to assist us in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC MASSBUS RT DECmate PDP UNIBUS DECnet P/OS VAX DECUS Professional VAXcluster DECwriter Rainbow VMS DIBOL RSTS VT ~D~DDmD RSX Work Processor Ethernet is a trademark of Xerox Corporation. This manual was produced by Networks and Communications Publications.
  • Openvms Cluster Load Balancing

    Openvms Cluster Load Balancing

    OpenVMS Cluster Load Balancing Presented by Paul Williams www.parsec.com | 888-4-PARSEC To Download this Presentation, please visit: http://www.parsec.com/public/ClusterLoadBalancing.pdf To E-mail Paul [email protected] www.parsec.com | 888-4-PARSEC Outline • Load Balancing Mechanisms • Batch and Print Queues • TCP/IP • DECnet • Local Area Transport (LAT) • Host Based Volume Shadowing • MSCP Server • Lock Manager • Questions and Answers Evaluating Load Balancing Mechanisms What happens when? •A new request is made •A node fails •Resources are exhausted on a node •A node is returned to service Load Balancing Goals •Never direct a request to a non- functional node •Direct requests to the node which can provide the best level of service •Direct requests to other nodes prior to scheduled downtime •Make failover and recovery transparent to user Load Balancing Mechanisms •Failover - All requests go to a single node while it is up •Round Robin - Balanced based only on number of requests serviced •Load Based - Balances requests based on ability of serving nodes to handle the work OpenVMS Queue Manager • Maintains all queues, forms and characteristics • Manages all jobs in each queue • Must run on one node in a VMScluster • Default is any node • Failover is automatic and transparent to users $ start /queue /manager /on=(class2,class3,*) $ show queue /manager /full Master file: STAFF_DISK:[COMMON]QMAN$MASTER.DAT; Queue manager SYS$QUEUE_MANAGER, running, on CLASS2:: /ON=(CLASS2,CLASS3,*) Database location: STAFF_DISK:[COMMON] Generic Batch Queues
  • Alpha and VAX Comparison Based on Industry-Standard Benchmark

    Alpha and VAX Comparison Based on Industry-Standard Benchmark

    Alpha and VAX Comparison based on Industry-standard Benchmark Results Digital Equipment Corporation December 1994 EC-N3909-10 Version 3.0 December 1994 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. Digital conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1 )(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227 7013. Copyright© 1994 Digital Equipment Corporation All rights reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: AlphaServer, AlphaStation, AlphaGeneration, DEC, OpenVMS, VMS, ULTRIX, and the DIGITAL logo. The following are third-party trademarks: MIPS is a trademark of MIPS Computer Systems, Inc. TPC-A is a trademark of the Transaction Processing Performance Council. INFORMIX is a registered trademark of lnformix Software, Inc. OSF/1 is a registered trademark of the Open Software Foundation, Inc. ORACLE is a registered trademark of Oracle Corporation. SPEC, SPECfp92, and SPECratio are trademarks of Standard Performance Evaluation Corporation. MIPS is a trademark of MIPS Computer Systems, Inc. All other trademarks and registered
  • Personal Decstation 5000 User's Guide

    Personal Decstation 5000 User's Guide

    Personal DECstation 5000 User’s Guide Order Number: EK–PM30E–RB.003 Digital Equipment Corporation Maynard, Massachusetts Second Printing, Sept, 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. All rights reserved. Printed in U.S.A. © Digital Equipment Corporation 1992. The postpaid Reader’s Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC, DECconnect, DECnet, DECstation, DECsystem, DECUS, DESTA, ThinWire, Turbochannel, ULTRIX, ULTRIX-32, and the DIGITAL logo. Motif is a trademark of the Open Software Foundation, Inc. MS–DOS is a registered trademark of Microsoft Corporation. PostScript is a registered trademark of Adobe Systems, Inc. VELCRO is a trademark of VELCRO USA, Inc. FCC NOTICE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense.
  • Computer Architectures an Overview

    Computer Architectures an Overview

    Computer Architectures An Overview PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sat, 25 Feb 2012 22:35:32 UTC Contents Articles Microarchitecture 1 x86 7 PowerPC 23 IBM POWER 33 MIPS architecture 39 SPARC 57 ARM architecture 65 DEC Alpha 80 AlphaStation 92 AlphaServer 95 Very long instruction word 103 Instruction-level parallelism 107 Explicitly parallel instruction computing 108 References Article Sources and Contributors 111 Image Sources, Licenses and Contributors 113 Article Licenses License 114 Microarchitecture 1 Microarchitecture In computer engineering, microarchitecture (sometimes abbreviated to µarch or uarch), also called computer organization, is the way a given instruction set architecture (ISA) is implemented on a processor. A given ISA may be implemented with different microarchitectures.[1] Implementations might vary due to different goals of a given design or due to shifts in technology.[2] Computer architecture is the combination of microarchitecture and instruction set design. Relation to instruction set architecture The ISA is roughly the same as the programming model of a processor as seen by an assembly language programmer or compiler writer. The ISA includes the execution model, processor registers, address and data formats among other things. The Intel Core microarchitecture microarchitecture includes the constituent parts of the processor and how these interconnect and interoperate to implement the ISA. The microarchitecture of a machine is usually represented as (more or less detailed) diagrams that describe the interconnections of the various microarchitectural elements of the machine, which may be everything from single gates and registers, to complete arithmetic logic units (ALU)s and even larger elements.
  • CERN Guide to Installing ULTRIX

    CERN Guide to Installing ULTRIX

    CERN Guide To Installing ULTRIX Alan Lovell CN Division Version February Contents Intro duction Conguration Hardware Installation General SCSI Identication Settings DECstation DECstation Connection to the Network Before Ordering Making the Connection System Software Installation Preparing for the Installation System Backup Disk Partitions Factory Installed Software FIS Performing the Installation Installing the Supp orted Software Subsets Installing The Unsupp orted Software Subsets Remote Installation Services How Do I Use the Remote Installation Service Remote Installation of the Supp orted Software Subsets Remote Installation of Additional Software Upgrading Your System Upgrading to Version A Upgrading to Version Preparing for the Upgrade Performing the Upgrade Post Upgrade Pro cedures The License ManagementFacility LMF Registering a License Loading the License System Tailoring Setting up TCPIP Dening the External Gateway Conguring the BINDHesio d Naming Service Dening the SearchOrder Adding the Names Servers Setting up Mail ULTRIX Version Systems ULTRIX Version Systems Starting the Network File System NFS Time Setting After
  • Decstation/Decsystem 5000 Model 200 Series Maintenance Guide

    Decstation/Decsystem 5000 Model 200 Series Maintenance Guide

    EK-PM38C-MG-002 DECstation/DECsystem 5000 Model 200 Series Maintenance Guide digital equipment corporation maynard, massachusetts First printing, January 1992 Second printing, April 1993 © Digital Equipment Corporation 1993. USA This equipment generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference. Operation of this equipment in a residential area may cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference. The following are trademarks of Digital Equipment Corporation: DEC PDP VAXBI DECnet ThinWire VAXcluster DECstation TURBOchannel VAXstation DECsystem ULTRIX VMS DECUS ULTRIX-32 VT MicroVAX UNIBUS MicroVMS VAX dt Contents About This Guide .......................................... xix Part I Hardware 1 System Overview System Hardware Configurations . .................... 1–2 System Unit ......................................... 1–4 Controls and Indicators ............................ 1–6 External System Unit Connectors ................... 1–8 Internal Base System Module Connectors . ........... 1–10 Hardware Options and Peripherals . .................... 1–12 CPU Module Description ........................... 1–13 System Boot ROM ................................. 1–13 Memory Modules .................................
  • Decserver 90L+ Owner's Manual

    Decserver 90L+ Owner's Manual

    DECserver 90L+ Owner’s Manual Order Number: EK-DSRVG-OM.001 January 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1992. All Rights Reserved. Printed in U.S.A. FCC NOTICE: The equipment described in this manual generates, uses and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference when operated in a commercial environment. Operation of this equipment in a residential area may cause interference, in which case the user at his own expense may be required to take measures to correct the interference. The following are trademarks of Digital Equipment Corporation: DEC, DECbridge, DECconnect, DECnet, DECserver, Digital, VMS, LAT, VAX, and the DIGITAL logo.
  • Software Product Description

    Software Product Description

    Software Product Description PRODUCT NAME: DECnet-ULTRIX, Version 4.0 for RISC and VAX SPD 26.83.08 ULTRIX Network Software (End-node Only) DESCRIPTION functions. The DECnet products and functions avail­ able to users on mixed networks can be determined by DECnet-ULTRIX, Version 4.0 is a Phase IV end­ comparison of the SPDs for the appropriate products. node implementation of Digital Network Architecture (DNA) for the ULTRIX Operating System and ULTRIX Note that incoming connections from all Phase III sys­ Worksystem Software (UWS) for VAX and RISC sys­ tems to DECnet-ULTRIX systems are supported. SUI>­ tems. port for outgoing connections Is limited to the following Phase I II systems: DECnet-VAX and DECnet-RT. In The DECnet-ULTRIX software enables communication addition, DECnet-ULTRIX only supports the connec­ among different networked Digital systems that use the tion of Phase IV routers/routing nodes on the point-to­ DNA Phase IIIIIV· protocols. At the same time, users point lines. and user programs can communicate with non-Digital systems that use the Internet (TCP/IP-based) proto­ Phase IV End Node cols. DECnet-ULTRIX offers the following capabilities: task-to-task communications, network virtual terminal, DECnet-ULTRIX is a Phase IV end-node only imple­ remote file transfer, mail, coexistence with the Internet mentation of DNA and as such, can communicate di­ protocols (TCPIIP-based), and network-wide resource rectly with any other Phase IV node on the Ethernet sharing and management as defined by the DNA pro­ or with any other Phase III/IV· node in the network via tocols.
  • Cisco IOS Decnet Command Reference August 2010

    Cisco IOS Decnet Command Reference August 2010

    Cisco IOS DECnet Command Reference August 2010 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.