Asynchronous Transfer Mode Configuration Guide, Cisco IOS Release 15S

Total Page:16

File Type:pdf, Size:1020Kb

Asynchronous Transfer Mode Configuration Guide, Cisco IOS Release 15S Asynchronous Transfer Mode Configuration Guide, Cisco IOS Release 15S 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. Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http:// www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) © 2014 Cisco Systems, Inc. All rights reserved. CONTENTS CHAPTER 1 Configuring ATM 1 Finding Feature Information 1 How to Configure ATM 1 Enabling Configuring the ATM Interface 1 Configuring PVCs 2 Creating a PVC 3 Mapping a Protocol Address to a PVC 3 Configuring the AAL and Encapsulation Type 4 Configuring PVC Traffic Parameters 4 Configuring ABR VCs 5 Configuring PVC Discovery 5 Enabling Inverse ARP 8 Configuring Loopback Cells to Verify Connectivity 9 Configuring Broadcast on a PVC 10 Assigning a VC Class to a PVC 10 Configuring PVC Trap Support 11 PVC Failure Notification 11 PVC Status Tables 11 Prerequisites 11 Enabling PVC Trap Support 12 Configuring SVCs 13 Configuring Communication with the ILMI 14 Configuring the PVC That Performs SVC Call Setup 15 Configuring the NSAP Address 16 Configuring the ESI and Selector Fields 16 Configuring the Complete NSAP Address 17 Creating an SVC 17 Configuring ATM UNI Version Override 18 Asynchronous Transfer Mode Configuration Guide, Cisco IOS Release 15S iii Contents Configuring the Idle Timeout Interval 19 Configuring Point-to-Multipoint Signaling 19 Configuring IP Multicast over ATM Point-to-Multipoint Virtual Circuits 22 Configuring SVC Traffic Parameters 22 Configuring Strict Traffic Shaping 24 Configuring Loopback Cells to Verify SVC Connectivity 25 Configuring Broadcast on an SVC 26 Assigning a VC Class to an SVC 26 Configuring SSCOP 26 Setting the Poll Timer 27 Setting the Keepalive Timer 27 Setting the Connection Control Timer 27 Setting the Transmitter and Receiver Windows 28 Closing an SVC 28 Configuring VC Classes 28 Creating a VC Class 28 Configuring VC Parameters 29 Applying a VC Class on an ATM PVC or SVC 29 Applying a VC Class on an ATM Interface 30 Configuring VC Management 31 Configuring ILMI Management 32 Configuring OAM Management for PVCs and SVCs 34 Configuring OAM Management for PVCs 34 Configuring OAM Management for SVCs 36 Configuring Classical IP and ARP over ATM 37 Configuring Classical IP and ARP in an SVC Environment 37 Configuring the Router as an ATM ARP Client 38 Configuring the Router as an ATM ARP Server 39 Configuring Classical IP and Inverse ARP in a PVC Environment 41 Customizing the ATM Interface 42 Configuring the Rate Queue 42 Using Dynamic Rate Queues 43 Configuring Rate Queue Tolerance 43 Configuring a Permanent Rate Queue 44 Configuring MTU Size 45 Asynchronous Transfer Mode Configuration Guide, Cisco IOS Release 15S iv Contents Setting the SONET PLIM 45 Setting Loopback Mode 46 Setting the Exception Queue Length 46 Configuring the Maximum Number of Channels 46 Limiting the Number of Virtual Circuits 47 Setting the Raw-Queue Size 47 Configuring Buffer Size 48 Setting the VCI-to-VPI Ratio 48 Setting the Source of the Transmit Clock 49 Configuring ATM Subinterfaces for SMDS Networks 49 Limiting the Message Identifiers Allowed on Virtual Circuits 50 Setting the Virtual Path Filter Register 51 Configuring Fast-Switched Transparent Bridging 51 Configuring Inverse Multiplexing over ATM 53 IMA Protocol Overview 54 General Description of ATM T1 E1 IMA 55 Restrictions 55 IMA Configuration Task List 56 Configuring an ATM Interface for IMA Operation 56 Configuring the Multiport T1 E1 ATM Network Module for IMA Operation 56 Configuring the Multiport T1 E1 ATM Port Adapter for IMA Operation 58 Verifying an ATM Interface Configured for IMA Operation 61 Verifying the Multiport T1 E1 ATM Network Module for IMA Operation 61 Verifying the Multiport T1 E1 ATM Port Adapter for IMA Operation 63 Configuring IMA Groups 65 Configuring IMA Groups on the Multiport T1 E1 ATM Network Module 65 Configuring IMA Groups on the Multiport T1 E1 ATM Port Adapter 67 Verifying IMA Group Configuration 69 Verifying IMA Group Configuration on the Multiport T1 E1 ATM Network Module 69 Verifying IMA Group Configuration on the Multiport T1 E1 ATM Port Adapter 73 Troubleshooting Tips 74 Bandwidth Considerations 75 Related Documents 76 Configuring ATM E.164 Auto Conversion 76 Asynchronous Transfer Mode Configuration Guide, Cisco IOS Release 15S v Contents Configuring Circuit Emulation Services 79 CES Overview 79 Configuring CES on the CES Network Module 80 Restrictions for th ATM CES Network Module 80 Configuring the ATM Interface 81 Configuring PVCs for CES Operation 81 Configuring SVCs for CES Operation 82 Configuring the T1 E1 Controller 83 Configuring Unstructured Circuit Emulation Service 83 Configuring Structured Circuit Emulation Service 84 Configuring Channel-Associated Signaling for Structured CES 86 Activating the Connection 87 Verifying CES Configuration on the CES Network Module 88 Configuring CES on the ATM-CES Port Adapter 88 Configuring Unstructured Clear Channel CES Services 89 Configuring Structured N x 64 CES Services 90 Configuring Channel-Associated Signaling for Structured CES Services 93 Configuring Network Clock Source and Priorities 95 Configuring Virtual Path Shaping 96 Configuring ATM Access over a Serial Interface 97 Enabling the Serial Interface 98 Enabling ATM-DXI Encapsulation 99 Setting Up the ATM-DXI PVC 99 Mapping Protocol Addresses to the ATM-DXI PVC 99 Monitoring and Maintaining the ATM-DXI Serial Interface 100 Troubleshooting the ATM Interface 100 Monitoring and Maintaining the ATM Interface 102 ATM Configuration Examples 103 Example Creating a PVC 103 Examples PVC with AAL5 and LLC SNAP Encapsulation 103 Example VCs in a Fully Meshed Network 104 Example Configuring an ABR PVC 105 Example Configuring PVC Discovery 105 Example Enabling Inverse ARP 106 Example Configuring Loopback Cells 106 Asynchronous Transfer Mode Configuration Guide, Cisco IOS Release 15S vi Contents Example Configuring PVC Trap Support 106 Example Configuring Communication with the ILMI 107 Example SVCs in a Fully Meshed Network 107 Example ATM ESI Address 108 Example ATM NSAP Address 108 Example SVCs with Multipoint Signaling 108 Example Configuring SVC Traffic Parameters 109 Example Creating a VC Class 109 Examples Applying a VC Class 110 Example LMI Management on an ATM PVC 110 Example OAM Management on an ATM PVC 110 Example OAM Management on an ATM SVC 111 Examples Classical IP and ARP 111 Example Configuring ATM ARP Client in an SVC Environment 111 Example Configuring ATM ARP Server in an SVC Environment 111 Example Configuring ATM Inverse ARP in a PVC Environment 111 Examples Dynamic Rate Queue 112 Example ATM Interfaces for SMDS Encapsulation 113 Example Transparent Bridging on an AAL5-SNAP PVC 113 Examples Inverse Multiplexing over ATM 113 Example E1 IMA on Multiport T1 E1 ATM Network Module 114 Example T1 IMA on Multiport T1 E1 ATM Network Module 116 Example T1 IMA on Multiport T1 E1 ATM Port Adapter 118 Example Configuring ATM E.164 Auto Conversion 119 Examples Circuit Emulation Service 120 Example Configuring CES on a CES Network Module 120 Example Configuring CES on an ATM-CES Port Adapter 121 Example Configuring Network
Recommended publications
  • LLDP-MED and Cisco Discovery Protocol
    White Paper LLDP-MED and Cisco Discovery Protocol DEVICE DISCOVERY PROTOCOLS Device discovery protocols enable directly connected devices to discover information about each other. They advertise information about the device over every interface, allowing any device in the network to “know” everything it is connected to. Examples of applications that use the information conveyed by discovery protocols include: ● Network topology—A network management system (NMS) can accurately represent a map of the network topology. ● Inventory—A management system can query a switch to learn about all the devices connected to that switch. ● Emergency services—Location of a phone can be determined by the switch port to which it is connected. ● VLAN configuration—The switch can tell the phone which VLAN to use for voice. ● Power negotiation—The phone and the switch can negotiate the power that the phone can consume. Cisco Systems ® introduced the Cisco ® Discovery Protocol in 1994 to provide a mechanism for the management system to automatically learn about devices connected to the network. Cisco Discovery Protocol runs on Cisco devices (routers, switches, phones, etc.) and is also licensed to run on some network devices from other vendors. Using Cisco Discovery Protocol, network devices periodically advertise their own information to a multicast address on the network, making it available to any device or application that wishes to listen and collect it. Because Cisco Discovery Protocol runs over Ethernet, ATM, and Frame Relay links, it is independent of network protocol (for example, TCP/IP, Internetwork Packet Exchange [IPX], AppleTalk, etc.). With this capability in the network, Cisco customers can introduce a new network management application that can discover and display an accurate topology of all the Cisco devices active on the network.
    [Show full text]
  • Provisioning Link Layer Discovery Protocol
    Provisioning Link Layer Discovery Protocol The Cisco Discovery Protocol (CDP) is a device discovery protocol that runs over Layer 2 (the data link layer) on all Cisco-manufactured devices (routers, bridges, access servers, and switches). CDP allows network management applications to automatically discover and learn about other Cisco devices connected to the network. To support non-Cisco devices and to allow for interoperability between other devices, the switch supports the IEEE 802.1AB Link Layer Discovery Protocol (LLDP). LLDP is a neighbor discovery protocol that is used for network devices to advertise information about themselves to other devices on the network. This protocol runs over the data link layer, which allows two systems running different network layer protocols to learn about each other. LLDP supports a set of attributes that it uses to discover neighbor devices. These attributes contain type, length, and value descriptions and are referred to as TLVs. LLDP supported devices can use TLVs to receive and send information to their neighbors. Details such as configuration information, device capabilities, and device identity can be advertised using this protocol. By default, LLDP is disabled globally and on interfaces. The switch supports these basic management TLVs. These are mandatory LLDP TLVs. • Port description TLV • System name TLV • System description • System capabilities TLV • Management address TLV These organizationally-specific LLDP TLVs are also advertised to support LLDP-MED. • Port VLAN ID TLV (IEEE 802.1 organizationally specific TLVs) • MAC/PHY configuration/status TLV (IEEE 802.3 organizationally specific TLVs) • How To Configure LLDP, page 2 • Other Commands For LLDP Configuration, page 8 Cisco ME 1200 Series Carrier Ethernet Access Devices Controller Configuration Guide, Cisco IOS 15.6(1)SN and Later Releases 1 Provisioning Link Layer Discovery Protocol How To Configure LLDP How To Configure LLDP Setting LLDP Global Configuration DETAILED STEPS Command or Action Purpose Step 1 configure terminal Enters global configuration mode.
    [Show full text]
  • Understanding and Configuring CDP
    CHAPTER20 Understanding and Configuring CDP This chapter describes how to configure Cisco Discovery Protocol (CDP) on the Catalyst 4500 series switch. It also provides guidelines, procedures, and configuration examples. This chapter includes the following major sections: • Overview of CDP, page 20-1 • Configuring CDP, page 20-2 Note For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2; Cisco IOS System Management; Configuring Cisco Discovery Protocol (CDP) at this URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ffun_c/fcfprt3/fcf015.htm and to the Cisco IOS Configuration Fundamentals Command Reference, Release 12.1; Cisco IOS System Management Commands; and CDP Commands publication at this URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ffun_r/ffrprt3/frf015.htm Note For complete syntax and usage information for the switch commands used in this chapter, refer to the Catalyst 4500 Series Switch Cisco IOS Command Reference and related publications at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/index.htm. Overview of CDP CDP is a protocol that runs over Layer 2 (the data link layer) on all Cisco routers, bridges, access servers, and switches. CDP allows network management applications to discover Cisco devices that are neighbors of already known devices, in particular, neighbors running lower-layer, transparent protocols.With CDP, network management applications can learn the device type and the SNMP agent address of neighboring devices. CDP enables applications to send SNMP queries to neighboring devices.
    [Show full text]
  • Af-Saa-Api-Dlpi-0091.000
    Technical Committee Native ATM Services Data Link Provider Interface (DLPI) Addendum Version 1.0 AF-SAA-API-DLPI-0091.000 February, 1998 af-saa-api-dlpi-0091.000 Native ATM Services DLPI Addendum Version 1.0 © 1998 by The ATM Forum. The ATM Forum hereby grants its members the limited right to reproduce in whole, but not in part, this specification for its members internal use only and not for further distribution. This right shall not be, and is not, transferable. All other rights reserved. Except as expressly stated in this notice, no part of this document may be reproduced or transmitted in any form or by any means, or stored in any information storage and retrieval system, without the prior written permission of The ATM Forum. The information in this publication is believed to be accurate as of its publication date. Such information is subject to change without notice and The ATM Forum is not responsible for any errors. The ATM Forum does not assume any responsibility to update or correct any information in this publication. Notwithstanding anything to the contrary, neither The ATM Forum nor the publisher make any representation or warranty, expressed or implied, concerning the completeness, accuracy, or applicability of any information contained in this publication. No liability of any kind shall be assumed by The ATM Forum or the publisher as a result of reliance upon any information contained in this publication. The receipt or any use of this document or its contents does not in any way create by implication or otherwise: • Any
    [Show full text]
  • Stealth Analysis of Network Topology Using Spanning Tree Protocol
    Stealth Analysis of Network Topology using Spanning Tree Protocol Stephen Glackin M.Sc. in Software and Network Security 2015 Computing Department, Letterkenny Institute of Technology, Port Road, Letterkenny, Co. Donegal, Ireland. Stealth Analysis of Network Topology using Spanning Tree Protocol Author: Stephen Glackin Supervised by: John O’ Raw A thesis presented for the award of Master of Science in Software and Network Security. Submitted to the Higher Quality and Qualifications Ireland (QQI) Dearbhú Cáilíochta agus Cáilíochtaí Éireann May 2015 Declaration I hereby certify that the material, which l now submit for assessment on the programmes of study leading to the award of Master of Science in Computing in Software and Network Security, is entirely my own work and has not been taken from the work of others except to the extent that such work has been cited and acknowledged within the text of my own work. No portion of the work contained in this thesis has been submitted in support of an application for another degree or qualification to this or any other institution. Signature of Candidate Date Acknowledgements I would like to thank my wife, kids, family members and extended family members for their support and encouragement, without them this project never would have been completed. Also I would like to offer my greatest appreciation to my supervisor Mr. John O'Raw for all his help and support. His knowledge with regards to everything relating to computing is truly amazing and I am very grateful for the time he has given in assisting me to carry out this project.
    [Show full text]
  • Crash Course: Ipv6 & Network Protocols
    SharkFest ’18 Europe Crash Course: IPv6 & Network Protocols by looking at packets! Johannes Weber Network Security Consultant #sf18eu#sf18eu • Imperial • Johannes Riding Weber School • https://weberblog.net Renaissance Vienna •• @webernetz Oct 29 - Nov 2 #whoami: Johannes Weber • Network Security Consultant @ TÜV Rheinland i-sec GmbH • (Next-Gen) Firewalls • VPN/Crypto • Routing/Switching • IPv6, DNS, NTP • https://weberblog.net • @webernetz #sf18eu • Johannes Weber • https://weberblog.net • @webernetz Agenda/Motivation • Many „unknown“ packets • IPv6 • Network Protocols • Crash course -> fast, no deep dive & skipping ;) • Normally: 2 day workshop for IPv6 only • Never ending acronyms • Who is familiar with IPv6? #sf18eu • Johannes Weber • https://weberblog.net • @webernetz Tracefiles • https://tinyurl.com/ipv6-crash-course • -> download of „weber01.zip“ • -> 3x pcaps • Plz do me a favour: listen first ;) • flavoured with 12x challenges #sf18eu • Johannes Weber • https://weberblog.net • @webernetz “Today’s latte, World IPv6 Launch.” by Yuko Honda is licensed under CC BY-SA 2.0. • Johannes Weber • https://weberblog.net • @webernetz• https://weberblog.net • Weber Johannes • #sf18eu IPv6 • IPv4 space is exhausted • IPv6 brings enough addresses ;) • every client is global addressable • end-to-end communication (no NAT!) • subnets for everyone • Only layer 3 changes (almost) • No broadcast anymore, but multicast #sf18eu • Johannes Weber • https://weberblog.net • @webernetz IPv6 Addresses • 128 bits long, hexadecimal, 8 groups called „hextets“
    [Show full text]
  • CISCO IOS Asynchronous Transfer Mode Configuration Guide Full
    Cisco IOS Asynchronous Transfer Mode Configuration Guide, Release 15.0 Release 15.0 October 2, 2009 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 Text Part Number: 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.
    [Show full text]
  • Cisco IOS Asynchronous Transfer Mode Command Reference Americas Headquarters Cisco Systems, Inc
    Cisco IOS Asynchronous Transfer Mode Command Reference 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.
    [Show full text]
  • Passive Asset Discovery User Guide
    ICS SHIELD R 510.2 Asset Passive Discovery (Asset PD) User Guide CS-ICSE777en-510B September 2019 DISCLAIMER This document contains Honeywell proprietary information. Information contained herein is to be used solely for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or disclosed to a third party without the express permission of Honeywell International Sàrl. While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The information and specifications in this document are subject to change without notice. Copyright 2019 – Honeywell International Sàrl DocID CS-ICSE777en-510B 2 Notices Trademarks Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks of Honeywell International, Inc. ControlEdge™ is a trademark of Honeywell International, Inc. OneWireless™ is a trademark of Honeywell International, Inc. Matrikon® and MatrikonOPC™ are trademarks of Matrikon International. Matrikon International is a business unit of Honeywell International, Inc. Movilizer® is a registered trademark of Movilizer GmbH. Movilizer GmbH is a business unit of Honeywell International, Inc. Other trademarks Trademarks that appear in this document are used only to the benefit of the trademark owner, with no intention of trademark infringement. Third-party licenses This product may contain or be derived from materials, including software, of third parties. The third party materials may be subject to licenses, notices, restrictions and obligations imposed by the licensor.
    [Show full text]
  • Monitoring and Visualization of LLDP Information in Zabbix Agenda Introduction
    Monitoring and visualization of LLDP information in Zabbix Agenda Introduction Technical choice & Problems Solution Use case Unresolved issue & Plan for the future How to use Introduction About me Takeshi Tanaka [email protected] System Architect & Management > Monitoring system design > Product planning NTT Com Solutions since 2008 About Corporation NTT Com Solutions Corporation (https://www.nttcsol.com/) ・Technical subsidiary of NTT Communications Group ・Founded in 1988 ・Provide Zabbix support service for Japanese market from 2008 ・First Zabbix premium partner in the world 2017 2008 About Corporation ・We provide Zabbix to many companies. (communication, manufacturing, finance, etc.) ・At the beginning, we provided a Japanese version of Zabbix 1.4. ・Currently we are provide Zabbix for large-scale enterprise systems. 30,000 hosts 1,200,000 items 60,000 triggers 4,000 NVPS Motivation of the project The current system is a combination of logical and physical structure. ・Logical structure provides visualization. ・Physical structure has limited visualization. It is a big problem with large-scale cloud services and communication line services. Logical structure Physical structure Cloud services Virtual infrastructure Physical infrastructure Problems cause It does not Cloud services work! Customers Which customers are Virtual affected? infrastructure Sales staff Do not ask Physical me! infrastructure System administrator Technical choice & Problems Technical choice ・The information neighbor devices managed in data link layer ・Manufacturers
    [Show full text]
  • Asynchronous Transfer Mode (ATM)
    ATM v1.03 – Aaron Balchunas 1 - Asynchronous Transfer Mode - Asynchronous Transfer Mode (ATM) Asynchronous Transfer Mode (ATM) is a high-speed, non-broadcast Layer 2 technology, similar in many respects to Frame Relay. In addition to supporting higher bandwidths, ATM integrates QoS mechanisms directly into the technology. ATM is thus a very flexible technology, supporting data, voice and video traffic. Other Layer 2 technologies, such as Ethernet or Token Ring, support variable-sized packets. For example, Ethernet packets are 1514 bytes by default, but the MTU can be changed. ATM utilizes fixed-sized packets called cells. Each cell is exactly 53 bytes. Because the cell size is always consistent, traffic can be routed or switched far more efficiently. Two ATM interface types exist: • User-Network Interface (UNI) – connects an ATM end-user device to an ATM switch or router • Network-Network Interface (NNI) – connects an ATM switch to another ATM switch ATM, like Frame Relay, builds Virtual Channels ( or Circuits ) between ATM devices. These virtual channels can be permanent (PVC) or switched (SVC) , and are one-way . Each virtual channel is identified by a Virtual Channel Identifier (VCI), the equivalent of a Frame-Relay DLCI. The VCI is only locally significant to the router/switch. Multiple virtual channels can then be bundled together into a Virtual Path, which is identified by a Virtual Path Identifier (VPI) . Like VCI’s, a VPI is only locally significant. A VPI essentially identifies a “route” between two ATM devices. * * * All original material copyright © 2007 by Aaron Balchunas ( [email protected] ), unless otherwise noted. All other material copyright © of their respective owners.
    [Show full text]
  • 13 Network Layer
    13 THE NETWORK LAYER Like all the other OSI layers, the network layer provides both connection- less and connection-oriented services. The upper layers and transport provide these two types of service to satisfy a broad range of application and end-user needs. This is universally recognized as a “good thing.” In the network layer, the presence of two types of service is generally con- sidered to be a “bad thing.” The reason for this is simple: everything above the network layer is host-specific and can be tailored to suit a par- ticular application running among some set of mutually consenting hosts without affecting the communications of other hosts using the same internetwork; the network layer, however, provides the fundamental connectivity without which no communication of any kind can take place among hosts. Most people agree that having one type of service at the network layer would be preferable to having two; as always, though, the problem stems from having to decide which one.1 The TCP/IP architecture, which from the beginning was based on an “internetworking” model of the network layer,2 avoided this contro- versy entirely; the TCP/IP network layer is exclusively connectionless.3 1. There are people who attempt to justify a “diversity of needs” at the network layer, but their sense of what constitutes interoperability is quite different from ours. 2. The best (and certainly the most succinct) description of the fundamental architec- tural premise of the TCP/IP network layer is the one that Vint Cerf uses to describe the TCP/IP internetworking model: “I P on everything.” 3.
    [Show full text]