DOCSLIB.ORG

Network Protocols Configuration Guide Part

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

NETWORK PROTOCOLS CONFIGURATION GUIDE PART Cisco lOS Release 12.0 APPLETALK NOVELL IPX Documentation also available on CD-ROM and the World Wide Web Cisce SYSTEMS Network Protocos Configuration Guide Part Cisco lOS Release 12.0 AppleTalk Novell IPX Corporate Headquarters Cisco Systems Inc 170 West Tasman Drive San Jose CA 95134-1706 USA http//www.cjsco.com Tel 408 526-4000 800 553-NETS 6387 Fax 408 526-4100 Customer Order Number DOC-785832 Text Part Number 78-5832-01 SUBJECT TO CHANGE WITHOUT THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE TO BE ACCURATE BUT ARE NOTICE ALL STATEMENTS INFORMATION AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED RESPONSIBILITY FOR THEIR PRESENTED WITHOUT WARRANTY OF ANY KIND EXPRESS OR IMPLIED USERS MUST TAKE FULL APPLICATION OF ANY PRODUCTS FORTH IN THE INFORMATION THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET ARE UNABLE TO PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE IF YOU LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY CONTACT YOUR CISCO REPRESENTATIVE FOR COPY has been tested and found to with Ihe limits for Class The following information is for FCC compliance of Class devices This equipment comply when the to 15 of the FCC rules These limits are to reasonable protection against harmful interference digital device pursuant part designed provide and used is in commercial environment This uses and can radiate radio-frequency energy and if not installed equipment operated equipment generates communications of this in residential area is in accordance with the instruction manual may cause harmful interference 10 radio Operation equipment harmful in which case users will be to correct the interference at their own expense likely to cause interference required described in this and radiate is for FCC of Class devices The manual generates may radio-frequency The following information compliance equipment installed in accordance with Ciscos installation instructions it cause interference wilts radio and television reception This equipment energy If it is nol may with the in 15 of the FCC rules These has been tested and found to comply with the limits for Class digital device in accordance specifications part reasonable such interference in residential installation However there is no guarantee that specifications are designed to provide prolection against installation interference will not occur in particular without Ciscos written authorization result in the no longer complying svith FCC requirements for Class or Modifying the equipmelsl may equipment be limited and maybe rcquired to correct any interference Class digital devices In that event your right louse the equipment may by FcC regulations yosi communications to radio or television at your own expense it off If the interference it was probably caused by the Cisco equipnsent You can determine whether your equipment is causing interference by turning stops interference to radio or television to correct the interference by using one or more of or one of its peripheral devices If the equipment causes reception try the following measures Tons the television or radio antenna until the interference stops radio Move the equipment to one side or the ottser of tlse television or radio Move the equipment farltser asvay from the television or television or radio is make certain the equipment and tIme television or radio Plug the equipment into an outlet that is on different circuit from the That are on circuits controlled by different circuit breakers or fuses could void the FCC and authority to the product Modifications to this product not authorized by Cisco Systems Inc approval negate your operate of the University of California Berkeley as part of The Cisco implementation of TCP header compression is an adaptation program developed by UCB of of California reserved Copyright 1981 the University UCB public domain version of the UNIX operating system All riglsts Regents 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 FOR PARTICULAR PURPOSE AND OR IMPLIED INCLUDING WITHOUT LIMITATION THOSE OF MERCHANTABILITY FITNESS 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 OUT OF THE USE OR DAMAGES INCLUDING WITHOUT LIMITATION LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING SUPPLIERS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES INABILITY TO USE THIS MANUAL EVEN IF CISCO OR ITS HAVE Cisco CiscoLink the Cisco Net Works logo the Cisco Powered AccessPalh Any to Any AlmDirector the CCIE logo CD-PAC Centri the Capital logo Fast FireRunner IGX lOS JumpStart Kernel Network logo the Cisco Press logo the Cisco Technologies logo ClickStart ControlStream DAGAZ Step Proxy LoopRunner MGX Natural Network Viewer NetRanger NetSonar Packet PIX Point and Click Internetworking Policy Builder RouteStream TransPath VirtualStream VlanDirector Workgroup Director Secure Script SMARTnet SpeedRunner Stratm StreamView The Cell TrafficDirector The Internet and Workgroup Stack are trademarks Changing the Way We Work Live Play and Learn Empowering the Internet Generation Economy Cisco the Cisco lOS Cisco the Cisco Systems logo and The New Internet Economy are service marks and BPX Catalyst Cisco lOS logo Systems Phase/IP StrataViesv Plus and Enterprise/Solver EtherChannet FastHub ForeSight FragmenlFree IP/TV IPX LightStream MICA StrataSphere and certain other countries All other trademarks mentioned in this document are SwitchProbe are registered trademarks of Cisco Systems Inc in the U.S of their owners the property respective 9809R Netmmork Protocols Configuration Guide Part Copyright 1998 Cisco Systems Inc All rights reserved Printed in USA CONTENTS About the Cisco lOS Software Documentation xvii Documentation Objectives xvii Audience xvii Documentation Organization xvii Documentation Modules xvii Master Indexes xvii Documentation Set xviii Supporting Documents xix Document Conventions xix Command Syntax Conventions xx Cisco Connection Online xx Documentation CD-ROM xxi Using Cisco lOS Software xxiii Getting Help xxiii Example How to Find Command Options xxiv Understanding Conmiand Modes xxvi Summary of Main Command Modes xxvii Using the No and Default Forms of Commands xxviii Saving Configuration Changes xxviii AppleTalk and Novell IPX Overview P2C-1 AppleTalk P2C- Background on AppleTalk P2C-1 Ciscos Implementation of AppleTalk P2C-2 Supported Media P2C-2 Standard AppleTalk Services P2C-2 Enhancements to Standard AppleTalk Services P2C-3 Security P2C-4 Novell IPX P2C-4 Background on Novell IPX P2C-4 Cisco Implementation of Novells IPX P2C-4 IPX MIB Support P2C-4 IPX Enhanced IGRP Support P2C-5 LANE Support P2C-5 VLAN Support P2C-5 Configuring AppleTalk P2C-7 AppleTalk Phases P2C-7 AppleTalk Phase P2C-7 AppleTalk Phase P2C-7 Types of AppleTalk Networks P2C-7 Contents iii Networks P2C-8 Comparison of Nonextended and Extended and Network P2C-8 Relationship Between AppleTalk Phases Types Phases P2C-8 Comparison of AppleTalk Phases P2C-9 Cisco-Supported AppleTalk AppleTalk Addresses P2C-9 Network Numbers P2C9 AppleTalk Phase Network Numbers P2C-9 AppleTalk Phase Network Numbers P2C-9 Node Numbers P2C-l0 AppleTalk Phase Node Numbers P2C-10 AppleTalk Phase Node Numbers P2C-10 AppleTalk Address Example P2C- 10 AppleTalk Zones P2C-10 AppleTalk Phase Zones P2C-l0 AppleTalk Phase Zones P2C-10 and Rules P2C- 10 Configuration Guidelines Compatibility Combining AppleTalk Phasel and Phase Routers P2C-1 Combining Cisco Routers with Other Vendors P2C- 11 AppleTalk Configuration Task List P2C- 11 Enable AppleTalk Routing P2C-12 Enable AppleTalk Routing Task List P2C-12 Enable AppleTalk Routing P2C-12 P2C-12 Configure an Interface for AppleTalk 13 Manually Configure an Interface P2C Dynamically Configure an Interface P2C- 13 Select an AppleTalk Routing Protocol P2C-15 16 Configure Transition Mode P2C Enable Concurrent Routing and Bridging P2C- 16 P2C-16 Configure Integrated Routing and Bridging P2C- 17 Control Access to AppleTalk Networks Types of Access Lists P2C-17 P2C-17 AppleTalk-Style Access Lists IP-Style Access Lists P2C-18 Entries P2C- 18 Combining AppleTalk-Style and IP-Style Types of Filters P2C- 18 Implementation Considerations P2C- 19 Task List P2C-20 Control Access to AppleTalk Networks Create Access Lists P2C-20 Set Priority Queuing P2C-20 Automatic Fast Switching P2C-20 Create AppleTalk-Style Access Lists P2C-20 Create IP-Style Access Lists P2C-21 Create Filters P2C-22 Create NBP Packet Filters P2C-22 Create Data Packet Filters P2C-23 Create Routing Table Update Filters P2C-23 iv Network Protocols Configuration Guide Part Create GetZoneList GZL Filters P2C-24 Enable ZIP Reply Filters P2C-25 Enable Partial Zone Filters P2C-26 Configure the Name Display Facility P2C-26 Set Up Special Configurations P2C-26 Configure AURP P2C-27 Configure Free-Trade Zones P2C-28 Configure SNMP over DDP in AppleTalk Networks P2C-29 Configure AppleTalk Tunneling P2C-29 Configure AppleTalk MacIP P2C-30 Cisco Implementation of AppleTalk MacIP P2C-30 When to Use AppleTalk MacIP P2C-30 Advantages of Using MacIP P2C-3 Implementation Considerations P2C-3 Configure AppleTalk MacIP Task List P2C-32 Establish MacIP Server for Zone P2C-32 Allocate IP Addresses for Macintosh Users P2C-32 Configure IPTalk P2C-33 Configure IP Encapsulation of
Recommended publications
  • Decbrouter 90 Products Command Summary

    Decbrouter 90 Products Command Summary

    DECbrouter 90 Products Command Summary Order Number: EK–DECBR-CS. A01 First Edition, May 1993 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 1993. 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, DECbrouter, DECnet, VAX, VMS, and the Digital logo. Apollo NCS is a trademark of Apollo Computer, Inc.
  • OES 2 SP3: Novell CIFS for Linux Administration Guide 9.2.1 Mapping Drives from a Windows 2000 Or XP Client

    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.
  • Shared Resource Matrix Methodology: an Approach to Identifying Storage and Timing Channels

    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.
  • Shared Resource

    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.
  • Resource Management in Multimedia Networked Systems

    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.
  • Novell Cluster Services,. for Linux. and Netware

    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
  • Novell® Platespin® Recon 3.7.4 User Guide 5.6.4 Printing and Exporting Reports

    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.
  • Characterizing Peer-Level Performance of Bittorrent

    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.
  • Server I/O Networks Past, Present, and Future Renato John Recio Chief Architect, IBM Eserver I/O IBM Systems Group, Austin, Texas Recio@Us.Ibm.Com

    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.
  • Cisco IOS Appletalk Configuration Guide Release 12.4

    Cisco IOS Appletalk Configuration Guide Release 12.4

    Cisco IOS AppleTalk Configuration Guide Release 12.4 Corporate 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 526-4100 Customer Order Number: DOC-7817505= Text Part Number: 78-17505-01 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.
  • Local Infrastructures for School Networking: Current Models and Prospects

    Local Infrastructures for School Networking: Current Models and Prospects

    DOCUMENT RESUME ED 349 957 IR 015 693 AUTHOR Newman, Denis; And Others _TITLE Local Infrastructures for School Networking: Current Models and Prospects. Technical Report No. 22. INSTITUTION Center for Technology in Education, New York, NY. SPONS AGENCY Department of Education, Washington, DC.; National Science Foundation, Washington, D.C. PUB DATE May 92 CONTRACT 1-135562167-Al; MDR-9154006 NOTE 30p. PUB TYPE Information Analyses (070) Viewpoints (Opinion/Position Papers, Essays, etc.) (120) EDRS PRICE MF01/PCO" Plus Postage. DESCRIPTORS Communications; Comparative Analysis; *Computer Networks; Educational Change; Educational Technology; Elementary Secondary Education; *Futures (of Society); Information Networks; *Local Area Networks; Microcomputers; *Models; *Telecommunications IDENTIFIERS *Wide Area Networks ABSTRACT This paper identifies a paradigm shift that must take place in school networking. The ultimate goal is to retool the schools with a local technical infrastructure that gives teachersand students immediate access to communication systems andinformation resources, thereby supporting the implementation of advancesin pedagogy and educational technology. The current notionof telecomputing cannot address the information requirements locally within the school and, ultimately, will fragment and inhibit any move toward universal access to information resources. A technologyis needed that combines local and wide area networking(LAN and WAN), making access to remote resources part of the everyday work with school computers. This report contains the following sections: (1) The Problem: Combining Local and Wide Area Communication--facts about the current state of school networks and the dissociation of school LANs and WANs;(2) A Brief History of Network Technology;(3) A Convergence of School LAN's and WAN's--integrating and simplifying a school internetwork;(4) Current Models of School LAN-WAN Connectivity--a comparison of six models; and (5) Prospects for the Future.
  • Setting up Your Gatorbox Lv July 1991 Tt

    Setting up Your Gatorbox Lv July 1991 Tt

    ® 11lis manual describes how to set up and connect the GatorBox network gateway and how to download its software. Tllis manual, taken together with the 2.0 version of the GatorBox User's Guide and the GatorBox Reference, completely replaces previous versions of the GatorBox documentation. Changes to this manual will be distributed as document updates or new revisions. Your comments about this manual are welcome. Use the forms at the back of the manual or address your comments to: Technical Services Cayman Systems 26 Landsdowne Street Cambridge, MA 02139 Telephone: (617) 494-1999 (9:00AM to 6:00PM EST) FAX: (617) 494-5167 Internet: [email protected] AppleLink: CAYMAN.TECH GatorBox, Cayman Systems, and the Cayman logo are registered trademarks of Cayman Systems, Inc. GatorKeeper, GatorMIM, GatorSystem, GatorPrint, and GatorShare are trademarks of Cayman Systems, Inc. Apple, the Apple logo, AppleLink, AppleTalk, A/lJX, LaserWriter, and Macintosh are registered trademarks of Apple Computer, Inc. EtherTalk, Finder, and Loca!Talk are trademarks of Apple Computer, Inc. UNIX is a registered trademark of American Telephone and Telegraph Company. Ethernet is a registered trademark of Xerox Corporation. NCSA Telnet is a trademark of the Board of Trustees of the University of Illinois at Champaign-Urbana. NFS and Sun are trademarks of Sun Microsystems, Inc. PhoneNET is a trademark of Farallon Computing. MMAC is a trademark of Cabletron Systems, Inc. Changes or modifications to the GatorBox not expressly approved by Cayman Systems can void your authorization to operate the equipment. FCC Class Notice TI1is 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.