DOCSLIB.ORG

Cisco IOS Appletalk and Novell IPX Configuration Guide Release 12.2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cisco IOS Appletalk and Novell IPX Configuration Guide Release 12.2 Cisco OS AppUeTalk and NovelU IPX Configuration Guide Release 12.2 Documentation also available on CD-ROM and the World Wide Web SYSTEMS Cisco Reader Comment Card General Information Years of with Cisco Years of networking experience ______ experience products have these network types fl LAN fl Backbone WAN LI Other have these Cisco products Switches Routers Other specify models perform these types of tasks 111W installation and/or maintenance S/W configuration Network management LI Other ______________________________________________ use these types of documentation 111W installation H/W configuration S/W configuration Command reference Quick reference Release notes Online help Other access this information through Cisco.com CD-ROM Printed docs Other ________________ prefer this access method ________________________________________ use the following three product features the most Document Information Document Title Cisco lOS AppleTalk and Novell IPX Configuration Guide Part Number 78-11734-01 S/W Release if applicable Release 12.2 On scale of 15 being the best please let us know how we rate in the following areas The document is written at my technical The information is accurate level of understanding The document is complete The information wanted was easy to find useful The information is well organized The information found was to my job Please comment on our lowest scores Mailing Information Company Name Date Contact Name Job Title Mailing Address ZIP/Postal Code City State/Province Country Phone Extension Fax E-mail No Can we contact you further concerning our documentation LI Yes LI e-mail to or fax to 408-527-8089 You can also send us your comments by [email protected] by NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO 4631 SAN JOSE CA POSTAGE WILL BE PAID BY ADDRESSEE ATTN DOCUMENT RESOURCE CONNECTION CSCO SYSTEMS NC 170 WEST TASMAN DRIVE SAN JOSE CA 95134-9883 II II Corporate Headquarters Cisco Systems Inc 170 West Tasman Drive San Jose CA 95134-1706 USA http//wwwcisco.com Tel 408 526-4000 800 553-NETS 6387 Fax 408 526-4100 Customer Order Number DOC-781 1734 Text Part Number 78-11734-01 TIlE SPECIFICATIONS AN 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 SOFIWARE LICENSE AJID 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 UCENSE OR LIMITED WARRANTY CONTACT YOUR CISCO REPRESENTATIVE FOR COPY The Cisco implementation of TCP header compression is an adaptation of program developed by the University of California Berkeley UCB as part of domain version the All reserved of the of California UCBs public of UNIX operating system rights Copyright 1981 Regents University 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 PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM 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 INABIUTY TO USE THIS MANTJAL EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AccessPath AtmDirector Browse with Me CCDA CCDE CCDP CCIE CCNA CCNP CCSI CD-PAC CiscoLink the Cisco Net Works logo the Cisco Powered Network logo Cisco Systems Networking Academy the Cisco Systems Networking Academy logo Fast Step Follow Me Browsing FormShare FrameShare GigaStack IGX Internet Quotient IP/VC iQ Breakthrough iQ Expertise iQ FastTrack the iQ Logo iQ Net Readiness Scorecard MGX the Networkers logo Packet PIX RaIeMUX ScriptBuilder ScriptShare SlideCast SMARTneI TransPath Unity Voice LAN Wavelength Router and WebViewer are trademarks of Cisco Systems Inc Changing the Way We Work Live Play and Learn Discover All Thats Possible and Empowering the Internet Generation are service marks of Cisco Systems Inc and Aironet ASIST BPX Catalyst Cisco the Cisco Certified Internetwork Expert logo Cisco lOS the Cisco lOS logo Cisco Systems Cisco Systems Capital the Cisco Systems logo Enterprise/Solver EtherChannel EtherSwitch FastHub FsstSwitch lOS IF/TV LightStream MICA Network Registrar Post-Routing Pre-Routing Registrar StrataView Plus Stratm SwitchProbe TeleRouter and VCO are registered trademarks of Cisco Systems Inc or its affiliates in the U.S and certain other countries All other trademarks mentioned in this document Web site the their The of the word brands names or or are property of respective owners use partner does not between Cisco and other imply partnership relationship any company 0102R Cisco lOS and Novell IPX Guide AppleTalk Configuration Copyright 2001 Cisco Systems Inc All rights reserved About Cisco lOS Software Documentation xiii Documentation Objectives xiii Audience xiii Documentation Organization xiii Documentation Modules xiii Master Indexes xvi Supporting Documents and Resources xvi Document Conventions xvii Obtaining Documentation xviii World Wide Web xviii Documentation CD-ROM xviii Ordering Documentation xviii Documentation Feedback xix Obtaining Technical Assistance xix Cisco.com xix Technical Assistance Center xx Contacting TAC by Using the Cisco TAC Website xx Contacting TAC by Telephone xx Using Cisco lOS Software xxi Understanding Command Modes xxi Getting Help xxii Example How to Find Command Options xxiii Using the no and default Forms of Commands xxv Saving Configuration Changes xxvi Filtering Output from the show and more Commands xxvi Identifying Supported Platforms xxvii Using Feature Navigator xxvii Using Software Release Notes xxvii AppleTalk and Novell IPX Overview P2C-1 AppleTalk Overview P2C-1 Background on AppleTalk P2C-2 Cisco lOS AppleTalk and Novell IPX Configuration Guide Contents The Cisco Implementation of AppleTalk P2C-2 Media Support P2C-2 Standard AppleTalk Services P2C-2 Enhancements to Standard AppleTalk Services P2c-3 Security P2C-4 Novell IPX Overview P2C-4 Background on Novell IPX P2C-4 The Cisco Implementation of Novell IPX P2c-4 IPX MIB Support P2C-5 IPX Enhanced IGRP Support P2c-5 LANE Support P2C-5 VLAN Support P2C-5 Multilayer Switching Support P2C-5 Contigurinj AppleTalk P2C-7 AppleTalk Phases P2C-7 AppleTalk Phase P2C-7 AppleTalk Phase P2C-7 Types of AppleTalk Phase Networks P2C-8 AppleTalk Addresses P2C-9 Network Numbers P2c-9 Node Numbers P2C-1O AppleTalk Address Example P2C-lo AppleTalk Zones P2C1O Configuration Guidelines and Compatibility Rules P2C-lo AppleTalk Configuration Task List P2c-11 Configuring AppleTalk Routing P2c-11 Enabling AppleTalk Routing P2C-12 Configuring an Interface for AppleTalk P2C-12 Selecting an AppleTalk Routing Protocol P2C-15 Configuring Transition Mode P2c-15 Enabling Concurrent Routing and Bridging P2c-16 Configuring Integrated Routing and Bridging P2c-16 Controlling Access to AppleTalk Networks P2c-16 Types of Access Lists P2c-17 Types of Filters P2c-18 __ Cisco lOS AppleTalk and Novell IPX Configuration Guide Contents Implementation Considerations P2c-19 Controlling Access to AppleTalk Networks Task List P2c-19 Creating Access Lists P2C-19 Creating Filters P2C-21 Configuring the Name Display Facility P2C-26 Sethng Up Special Configurations P2C-26 Configuring Free-Trade Zones PZC-26 Configuring SNMP over DDP in AppleTalk Networks P2C-27 Configuring AppleTalk Tunneling P2C-27 Configuring AppleTalk MaciP P2C-30 Configuring AppleTalk MaciP Task List P2C-32 Configuring lPTalk P2C-33 Configuring SMRP over AppleTalk P2C-36 Configuring AppleTalk Control Protocol for PPP P2c-38 Tuning AppleTalk Network Performance PZC-39 Controlling Routing Updates P2C-39 Assigning Proxy Network Numbers P2C-41 Enabling Round-Robin Load Sharing P2c-42 Disabling Checksum Generation and Verification P2C-42 Controlling the AppleTalk ARP Table P2C-42 Controlling the Delay Between ZIP Queries P2C-43 Logging Significant Network Events P2C-44 Disabling Fast Switching P2C-44 Configuring AppleTalk Enhanced IGRP P2C-44 Convergence Technology P2C-44 Enhanced IGRP Features P2C-45 Enhanced IGRP Components P2C-45 The Cisco Implementation of Enhanced IGRP P2c-46 Enhanced IGRP Configuration Task List P2C-46 Configuring AppleTalk Interenterprise Routing P2C-49 Understanding AppleTalk Domains P2C-50 Understanding Domain Routers P2C-50 AppleTalk Interenterprise Routing Features P2c-50 Redundant Paths Between Domains P2C-50 AppleTalk Interenterprise Routing Task List P2C-51 Cisco lOS AppleTalk and Novell IPX Configuration Guide Contents Configuring AppleTalk over WANs P2c-52 AppleTalk over DDR P2C-53 AppleTalk over X.25 P2C-54 Configuring AppleTalk Between LANs P2C-54 Configuring AppleTalk Between VLANs P2C-54 Monitoring and Maintaining the AppleTalk Network P2C-54 Monitoring and Maintaining the AppleTalk Network Using Cisco lOS Software Commands P2C-54 Monitoring the AppleTalk Network Using Network Monitoring Packages P2C-56 AppleTalk Configuration Examples P2C-57 Extended AppleTalk Network Example P2C-58 Nonextended AppleTalk Network Example
Load more

Recommended publications
  • OES 2 SP3: Novell CIFS for Linux Administration Guide 9.2.1 Mapping Drives from a Windows 2000 Or XP Client
    www.novell.com/documentation Novell CIFS Administration Guide Open Enterprise Server 2 SP3 May 03, 2013 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Service Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software.
    [Show full text]
  • Shared Resource Matrix Methodology: an Approach to Identifying Storage and Timing Channels
    Shared Resource Matrix Methodology: An Approach to Identifying Storage and Timing Channels RICHARD A. KEMMERER University of California, Santa Barbara Recognizing and dealing with storage and timing channels when performing the security analysis of a computer system is an elusive task. Methods for discovering and dealing with these channels have mostly been informal, and formal methods have been restricted to a particular specification language. A methodology for discovering storage and timing channels that can be used through all phases of the software life cycle to increase confidence that all channels have been identified is presented. The methodology is presented and applied to an example system having three different descriptions: English, formal specification, and high-order language implementation. Categories and Subject Descriptors: C.2.0 [Computer-Communication Networks]: General--se- curity and protection; D.4.6 ]Operating Systems]: Security and Protection--information flow controls General Terms: Security Additional Key Words and Phrases: Protection, confinement, flow analysis, covert channels, storage channels, timing channels, validation 1. INTRODUCTION When performing a security analysis of a system, both overt and covert channels of the system must be considered. Overt channels use the system's protected data objects to transfer information. That is, one subject writes into a data object and another subject reads from the object. Subjects in this context are not only active users, but are also processes and procedures acting on behalf of the user. The channels, such as buffers, files, and I/O devices, are overt because the entity used to hold the information is a data object; that is, it is an object that is normally viewed as a data container.
    [Show full text]
  • Shared Resource
    Shared resource In computing, a shared resource, or network share, is a computer resource made available from one host to other hosts on a computer network.[1][2] It is a device or piece of information on a computer that can be remotely accessed from another computer transparently as if it were a resource in the local machine. Network sharing is made possible by inter-process communication over the network.[2][3] Some examples of shareable resources are computer programs, data, storage devices, and printers. E.g. shared file access (also known as disk sharing and folder sharing), shared printer access, shared scanner access, etc. The shared resource is called a shared disk, shared folder or shared document The term file sharing traditionally means shared file access, especially in the context of operating systems and LAN and Intranet services, for example in Microsoft Windows documentation.[4] Though, as BitTorrent and similar applications became available in the early 2000s, the term file sharing increasingly has become associated with peer-to-peer file sharing over the Internet. Contents Common file systems and protocols Naming convention and mapping Security issues Workgroup topology or centralized server Comparison to file transfer Comparison to file synchronization See also References Common file systems and protocols Shared file and printer access require an operating system on the client that supports access to resources on a server, an operating system on the server that supports access to its resources from a client, and an application layer (in the four or five layer TCP/IP reference model) file sharing protocol and transport layer protocol to provide that shared access.
    [Show full text]
  • Resource Management in Multimedia Networked Systems
    University of Pennsylvania ScholarlyCommons Technical Reports (CIS) Department of Computer & Information Science May 1994 Resource Management in Multimedia Networked Systems Klara Nahrstedt University of Pennsylvania Ralf Steinmetz University of Pennsylvania Follow this and additional works at: https://repository.upenn.edu/cis_reports Recommended Citation Klara Nahrstedt and Ralf Steinmetz, "Resource Management in Multimedia Networked Systems ", . May 1994. University of Pennsylvania Department of Computer and Information Science Technical Report No. MS-CIS-94-29. This paper is posted at ScholarlyCommons. https://repository.upenn.edu/cis_reports/331 For more information, please contact [email protected]. Resource Management in Multimedia Networked Systems Abstract Error-free multimedia data processing and communication includes providing guaranteed services such as the colloquial telephone. A set of problems have to be solved and handled in the control-management level of the host and underlying network architectures. We discuss in this paper 'resource management' at the host and network level, and their cooperation to achieve global guaranteed transmission and presentation services, which means end-to-end guarantees. The emphasize is on 'network resources' (e.g., bandwidth, buffer space) and 'host resources' (e.g., CPU processing time) which need to be controlled in order to satisfy the Quality of Service (QoS) requirements set by the users of the multimedia networked system. The control of the specified esourr ces involves three actions: (1) properly allocate resources (end-to-end) during the multimedia call establishment, so that traffic can flow according to the QoS specification; (2) control resource allocation during the multimedia transmission; (3) adapt to changes when degradation of system components occurs.
    [Show full text]
  • Novell Cluster Services,. for Linux. and Netware
    Novell Cluster Services,. for Linux. and NetWare. ROB BASTIAANSEN SANDER VAN VUGT Novell PRESS. Novell. Published by Pearson Education, Inc. 800 East 96th Street, Indianapolis, Indiana 46240 USA Table of Contents Introduction 1 CHAPTER 1: Introduction to Clustering and High Availability 5 Novell Cluster Services Defined 5 Shared Disk Access 6 Secondary IP Addresses 7 Clustering Terminology 8 High-Availability Solutions Overview 12 Novell Cluster Services 12 Business Continuity Clustering 13 PolyServe Matrix Server 15 Heartbeat Subsystem for High-Availability Linux 16 When Not to Cluster Applications 16 Availability Defined 18 High Availability Defined 18 Calculating Average Downtime 21 Avoiding Downtime 22 Hardware 22 Environment 23 Software 23 Procedures 24 Novell Cluster Services Requirements 24 Hardware Requirements 24 Software Requirements 26 CHAPTER 2: Examining Novell Cluster Services Architecture 27 Novell Cluster Services Objects and Modules 27 Cluster eDirectory Objects 28 Cluster Modules 31 IH Novell Cluster Services for Linux and NetWare Heartbeats, Epoch Numbers, and the Split Brain Detector 35 Removing a Failing Slave Node 36 Removing a Failed Master Node 37 Summary 37 CHAPTER 3: Clustering Design 39 Cluster Design Guidelines 39 How Many Nodes to Choose 39 Using a Heartbeat LAN or Not 40 Use NIC Teaming 41 Choosing Storage Methods 42 Mirror the Split Brain Detector Partition 48 Selecting Applications to Run in a Cluster 48 eDirectory Cluster Guidelines 50 Creating a Failover Matrix 52 Application-Specific Design Guidelines
    [Show full text]
  • Novell® Platespin® Recon 3.7.4 User Guide 5.6.4 Printing and Exporting Reports
    www.novell.com/documentation User Guide Novell® PlateSpin® Recon 3.7.4 September 2012 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software.
    [Show full text]
  • Characterizing Peer-Level Performance of Bittorrent
    Characterizing Peer-level Performance of BitTorrent DRP Report Amir H. Rasti ABSTRACT 1. INTRODUCTION BitTorrent is one of the most popular Peer-to-Peer During the past few years, peer-to-peer appli- (P2P) content distribution applications over the cations have become very popular on the In- Internet that significantly contributes in network ternet. BitTorrent in one of the most popu- traffic. lar peer-to-peer applications providing scalable peer-to-peer content distribution over the In- In BitTorrent, a file is divided into segments ternet. Some recent studies [8] have shown that and participating peers contribute their outgoing BitTorrent is accountable for approximately bandwidth by providing their available segments 35% of the Internet traffic. BitTorrent is a to other peers while obtaining their missing peers scalable peer-to-peer content distribution sys- from others. Characterization of BitTorrent is use- tem that enables one-to-many distribution of ful in determining its performance bottlenecks as large files without requiring a large access link well as its impact on the network. bandwidth at the source. Similar to other peer- In this study, we try to address the following two to-peer systems, it uses resources of participat- key questions through measurement: (i) What are ing peers to increase the capacity of the system. the main factors that affect observed performance The main shared resource in BitTorrent is the by individual peers in BitTorrent?, and (ii) What up-link bandwidth of individual peers. The file are the contributions of these factors on the per- being distributed is divided into a large number formance of individual peers? To address these of segments.
    [Show full text]
  • Server I/O Networks Past, Present, and Future Renato John Recio Chief Architect, IBM Eserver I/O IBM Systems Group, Austin, Texas [email protected]
    Server I/O Networks Past, Present, and Future Renato John Recio Chief Architect, IBM eServer I/O IBM Systems Group, Austin, Texas [email protected] Abstract • Low latency - the total time required to transfer the first bit of a message from the local application to the remote appli- Enterprise and technical customers place a diverse set of cation, including the transit times spent in intermediate requirements on server I/O networks. In the past, no single switches and I/O adapters. network type has been able to satisfy all of these requirements. As • High throughput - the number of small block transactions a result several fabric types evolved and several interconnects performed per second. The size and rate of small block I/O emerged to satisfy a subset of the requirements. Recently several depends on the workload and fabric type. A first level technologies have emerged that enable a single interconnect to be approximation of the I/O block size and I/O throughput rates required for various I/O workloads can be found in used as more than one fabric type. This paper will describe the “I/O Workload Characteristics of Modern Servers” [4]. requirements customers place on server I/O networks; the various • High bandwidth - the number of bytes per second sup- fabric types and interconnects that have been used to satisfy those ported by the network. Typically, used to gauge perfor- requirements; the technologies that are enabling network mance for large block data transfers. Peek bandwidth convergence; and how these new technologies are being deployed describes the bandwidth provided by a given link; whereas on various network families.
    [Show full text]
  • NFS Gateway for Netware 6 Administration Guide October 22, 2003
    Novell Confidential Manual (99a) 11 September 2003 Novell * NFS Gateway for NetWare® 6 www.novell.com ADMINISTRATION GUIDE October 22, 2003 Novell Confidential Manual (99a) 11 September 2003 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside. Copyright © 2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent No. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,572,528; 5,594,863; 5,608,903;5,633,931; 5,652,859; 5,671,414;
    [Show full text]
  • Casual Resource Sharing with Shared Virtual Folders
    MASTER THESIS IN COMPUTER SCIENCE Casual Resource Sharing with Shared Virtual Folders Siri Birgitte Uldal June 15th, 2007 FACULTY OF SCIENCE Department of Computer Science University of Tromsø, N-9037 Tromsø Casual Resource Sharing with Shared Virtual Folders Siri Birgitte Uldal June 15th, 2007 ___________________ University of Tromsø 2007 Abstract Proliferation of wireless networks has been a major trigger behind increased mobility of computing devices. Along with increased mobility come requests for ad-hoc exchange of resources between computing devices as an extension of humans interacting. We termed it casual resource sharing where resources in this thesis have been narrowed down to files only. We have named our casual resource sharing model for shared virtual folders (SVF). SVFs can be looked upon as a common repository much in the same way as the tuplespace model. The SVF members perceive the repository similarly to a common file directory on a server, while in reality all participating devices stores their own contribution of files. All types of files could be added to the repository and shared. To become a SVF member one needs to be invited by another member or initiate a SVF oneself. All members are free to withdraw their SVF membership whenever they wish. They are also free to log on to the SVF and log out as they please. The SVF cease to exist when the last member has drawn his membership. The SVF implements a simple versioning detection system to alert members when a file has been modified by another member. Feasibility of the model is demonstrated in a prototype implementation based on Java and the JXTA middleware, a peer-to-peer (P2P) infrastructure middleware supporting the Internet protocol.
    [Show full text]
  • A Pattern Language for Designing Application-Level Communication Protocols and the Improvement of Computer Science Education Through Cloud Computing
    Utah State University DigitalCommons@USU All Graduate Theses and Dissertations Graduate Studies 5-2017 A Pattern Language for Designing Application-Level Communication Protocols and the Improvement of Computer Science Education through Cloud Computing Jorge Edison Lascano Utah State University Follow this and additional works at: https://digitalcommons.usu.edu/etd Part of the Computer Sciences Commons Recommended Citation Lascano, Jorge Edison, "A Pattern Language for Designing Application-Level Communication Protocols and the Improvement of Computer Science Education through Cloud Computing" (2017). All Graduate Theses and Dissertations. 6547. https://digitalcommons.usu.edu/etd/6547 This Dissertation is brought to you for free and open access by the Graduate Studies at DigitalCommons@USU. It has been accepted for inclusion in All Graduate Theses and Dissertations by an authorized administrator of DigitalCommons@USU. For more information, please contact [email protected]. A PATTERN LANGUAGE FOR DESIGNING APPLICATION-LEVEL COMMUNICATION PROTOCOLS AND THE IMPROVEMENT OF COMPUTER SCIENCE EDUCATION THROUGH CLOUD COMPUTING by Jorge Edison Lascano A dissertation submitted in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY in Computer Science Approved: ______________________ ____________________ Stephen W. Clyde, Ph.D. Curtis Dyreson, Ph.D. Major Professor Committee Member ______________________ ____________________ Haitao Wang, Ph.D. Young-Woo Kwon, Ph.D. Committee Member Committee Member ______________________ ____________________ Luis Gordillo, Ph.D. Mark R. McLellan, Ph.D. Committee Member Vice President for Research and Dean of the School of Graduate Studies UTAH STATE UNIVERSITY Logan, Utah 2017 ii Copyright © Jorge Edison Lascano 2017 All Rights Reserved iii ABSTRACT A Pattern Language for Designing Application-Level Communication Protocols and the Improvement of Computer Science Education through Cloud Computing by Jorge Edison Lascano, Doctor of Philosophy Utah State University, 2017 Major Professor: Stephen W.
    [Show full text]
  • Architecture Layers Document
    CTMS/CTIS INTEGRATION Contract Routing No. 04 HAA 00063 Architecture Layers Version 1.1 Approved By Robert Wycoff CDOT ITS Office Signature: ___________________________ Date: _______________________________ John Williams CDOT ITS Office Signature: ___________________________ Date: _______________________________ Prepared By: CTMS/CTIS Version: 1.1 Architecture Layers Date: 08 Mar 2004 Revision History Date Version Description Author 08-Mar-2004 0.1 First Draft Jason Westra Sachin Saindane 27-Apr-04 0.2 Scheduler and Communications are Jason Westra services, not layers. Added Delegate Layer. 11-May-04 0.3 Added Notifications service and Services Jason Westra Catalog 21-May-04 0.4 Added New Architecture Drawing Sachin Saindane 07-March-05 1.1 Added more depth around layers and Jason Westra guidelines Confidential ©EnRoute Traffic Systems, Inc. Page 2 of 17 CTMS/CTIS Version: 1.1 Architecture Layers Date: 08 Mar 2004 Table of Contents i. Executive Summary 5 1.Introduction 6 1.1 Purpose 6 1.2 Scope 6 1.3 Audience 6 1.4 References 6 2. Logical Architecture Reference Model 7 2.1 Architectural Layers 7 3. Application Layer 9 3.1 Client Layer 10 3.2 Delegate Layer 11 3.3 Messaging Layer 11 3.4 Services Layer 12 4. Application Support Layer 13 5. External Services Layer 14 6. Platform Services Layer 15 7. Tiers 16 7.1 Client Tier 16 7.2 Presentation Tier 16 7.3 Business Tier 16 7.4 Integration Tier 17 7.5 Resource Tier 17 7.6 Achieving Deployment Agility 17 Confidential ©EnRoute Traffic Systems, Inc. Page 3 of 17 CTMS/CTIS Version: 1.1 Architecture
    [Show full text]