DOCSLIB.ORG

Aarnet's Experiences Using MPLS for Protection

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Aarnet's Experiences Using MPLS for Protection AARNet's experiences using MPLS for protection Internet2/NLANR Joint Techs Meeting Boulder, CO, USA 2002-07-28 Glen Turner, Network Engineer Australian Academic & Research Network [email protected] http://www.aarnet.edu.au/ Topics MPLS overview Protection technology AARNet's experiences with MPLS Other interesting stuff if we have time Coverage MPLS is a big topic with multiple implementation choices at almost every turn Only discuss some of the technolgy choices ● MPLS generic tagging, not ATM tagging ● RSVP and not LDP ● OSPF and not IS-IS Coverage Discuss the use of MPLS for protection, not discussing some important uses of MPLS ● VPNs (and thus BGP) ● GMPLS, the integrated control layer for switching technologies “How to speak Australian” ● words with “or” à “our”, “z” à “s” SONET à SDH (slight framing difference) T1 à E1 (E1 is 2Mbps) Topic MPLS overview Label switching Control plane protocols, RSVP Routing protocols, OSPF MPLS aims Scalable IP traffic engineering ● Avoid need for full IP network knowledge at core Virtual private network service ● By providing label switch paths exclusive to a customer This presentation focuses on traffic engineering ● Only beginning to experiment with VPNs MPLS is a layer 2½ protocol 7 Application 7 Application 6 Presentation 6 Presentation 5 Session 5 Session 4 Transport 4 Transport 3 Network 3 Network 2 Link 2½ MPLS 1 Physical 2 Link 1 Physical Advantages of layer 2½ No complex next hop algorithm ● IP address lookup is expensive – Closest matching prefix versus table lookup ● IP next hop algorithm gets more complex with each new service – Policy routing – Multicast Want GbE switch prices not GbE router prices New behaviours only effect edge routers Advantages of layer 2½, cond No need to follow IP routing ● The shortest path may not be the best path ● Want policy – For traffic engineering ● Bandwidth ● Diverse routers and paths – For arbitrary customer requirements ● eg: Australian Army doesn't want to be routed over links not owned by Australian-controlled telcos Advantages of layer 2½, cond Why MPLS for policy and not BGP? ● BGP is globally visible – Scalability: Does outer Mongolia need to know of an interface failure in outback Australia? – Can lose connectivity due to dampening, which is essential due to global visibility ● Not all reasonable policies can be expressed in BGP Disadvantages of layer 2½ Another set of control protocols ● ATM: OAM, ILMI, PNNI ● 802.1Q VLANs: Virtual LAN reservation protocol ● SDH/SONET MPLS uses IP as its control and routing protocol Layer 2.5 and protection Network layer protection requires a network-layer repsonse ● Limited by convergence time of routing protocol ● Fast convergence and global visibility do not mix – BGP rate limiting is an expression of this Layer 2.5 and protection Link layer protection requires a link layer response ● These often have constrained topologies – SDH/SONET rings – 802.1D and parallel links ● They often inefficiently use protection bandwidth ● They often treat all network traffic as equally valuable ● Lack of network topology: poor decisions Layer 2.5 and protection Allow network layer to establish pre- routed fallback path ● Full topology awareness Allow link layer to switch to fallback path ● Not globally visible ● Fast convergence This could get messy upon multiple failures ● Run interior routing protocol afterwards Forwarding equivalence class Another view of IP routing ● Step 1: Determine forwarding equivalence class from IP header (or more) – Standard: Destination IP address – Advanced: source IP address, multicast group, DSCP, TCP port, increasing bizaare ● Step 2: Lookup FEC forwarding table to determine output interface (ie: switch the packet) Forwarding equivalence class, cond IP router calculates forwarding equivalence class at every hop ● Expensive – either in CPU time or hardware ● Extensive – IP forwarding table is big with frequent updates ● Difficult to alter for new behaviours – ASIC designers may have not anticipated the change (reverse path lookup, source-specific multicast) Forwarding equivalence class, cond MPLS switching ● Determine forwarding equivalence class at ingress ● Tag packet with a fixed-length label for this forwarding equivalence class ● Switch using the label at every other hop to egress – Tags are designed for hardware manipulation Labels are not globally unique Even one router can run multiple “label spaces” – eth0, eth1 in LS1 – eth2, eth3 in LS2 Edge routers need distinct IP routing tables for each label space ● The key to MPLS VPNs ● We often want multiple routing tables and settle for policy routing instead MPLS tag A 32-bit header in front of the packet Tag contains just enough information for forwarding and queuing ● Unlike IPv4/IPv6 header, which carries a lot more Tag has hardware-friendly structure MPLS tag, fields Label ● Determines next-hop interface Experimental (QoS) ● Determines output interface queuing S for “last of stack” ● S=1 on last header Time to live ● Discard upon zero, otherwise decrement MPLS tag, stacking Tag Tag Tag Network-layer packet S=0 S=0 S=1 An MPLS tagged packet can be tagged again (“stacked”) ● Allows Provider-Provider connections to maintain customer tags ● Simplifies design considerably ● Avoids need for global label space MPLS tag, stacking and MTU The tag may reduce the size of the path maximum transmission unit (PMTU) ● TCP/IP stacks don't cope well with change of PMTU – PMTU at establishment of TCP determines TCP MSS ● Best to ensure that main and protect paths have identical tag depths Or may not, if the link layer will let us flex the rules MPLS operation mpls-path.dia MPLS operation, cond Label switch router Incoming packet, look up incoming label map, which contains ● Incoming label ● MPLS opcode: PUSH, POP, etc ● Forwarding equivalence class ● Link to outgoing next hop label entry MPLS operation, cond Label switch router Incoming packet operations ● Extract label from top tag ● Lookup incoming label map ● Execute MPLS opcodes to manipulate tags ● Forward packet to outgoing processing MPLS operation, cond Label switch router Outgoing packet, look up next hop label entry, which contains ● Outgoing label ● Outgoing interface ● Perhaps, outgoing per-hop queuing behaviour MPLS operation, cond Label switch router Outgoing packet operations ● Look up next hop label entry ● Create new tag containing outgoing label ● PUSH tag onto label stack ● Add to transmit queue on outgoing interface – queuing discipline may depend upon ● Value in next hop forwarding entry ● Value determined from Exp bits, a lá IP DSCP and weighted fair queuing + RED MPLS operation, cond Ingress label edge router Incoming packet, look up forwarding equivance class to next hop label entry (FTN), which contains ● forwarding equivalence class ● next hop label entry MPLS operation, cond Ingress label edge router Incoming packet operations ● Determine forwarding equivalence class using “standard” IP forwarding – Basic: lookup destination IP address in IP forwarding table – Advanced: policy routing, multicast routing, QoS routing, ... ● Use FEC to lookup forwarding equivalence class to next hop label entry table ● Process next hop label entry MPLS operation, cond Egress label edge router Next hop label entry shows this router as the penultimate hop Protocol-dependent actions to simulate label switch routers being real routers ● Decrement IP TTL ● Generate any ICMP which would have occurred Forward the packet using the standard IP algorithm Faking ICMP gives interesting results Traceroute from Glen's home to www.internet2.edu 1 sadial.sa.csiro.au 119.657 ms 129.673 ms 100.004 ms 2 sa.gw.csiro.au 119.944 ms 129.829 ms 110.382 ms 3 lis255.atm1-0.central.saard.net 131.917 ms 119.858 ms 109.980 ms 4 sa-nsw.atm.net.aarnet.edu.au 139.715 ms 149.829 ms 140.002 ms 5 vlan916.gbe3-0.sccn1.broadway.aarnet.net.au 149.941 ms 149.773 ms 149.968 ms 6 pos1-0.sccn1.manoa.aarnet.net.au 349.907 ms 279.791 ms 289.963 ms 7 pos2-0.sccn1.seattle.aarnet.net.au 279.866 ms 329.880 ms 279.904 ms 8 Abilene-PWAVE.pnw-gigapop.net 279.870 ms 351.155 ms 328.555 ms 9 dnvr-sttl.abilene.ucaid.edu 339.933 ms 339.861 ms 329.944 ms 10 kscy-dnvr.abilene.ucaid.edu 349.847 ms 339.622 ms 350.053 ms 11 ipls-kscy.abilene.ucaid.edu 339.756 ms 339.932 ms 339.903 ms 12 clev-ipls.abilene.ucaid.edu 339.884 ms 349.808 ms 339.963 ms 13 nycm-clev.abilene.ucaid.edu 349.752 ms 349.857 ms 339.969 ms 14 border-abilene-oc3.advanced.org 360.135 ms 359.857 ms 379.851 ms 15 www.internet2.edu 379.865 ms 359.838 ms 359.950 ms Architectural issues There is a lot of complexity at the edge ● Especially in the egress router But we want the edge to be cheap, as there is a lot of it There are no MPLS applications ATM has applications ● (Today's bizaare but true fact) Links between 3G base stations and switching points is the most recent application to treat ATM as a transport layer Even ethernet has applications ● DEC Local Area Transport There are no MPLS applications MPLS exists only to carry other protocols ● The label edge routers must support the protocol ● This isn't new – All routers have to support the network layer protocol they are routing Model is strained somewhat by abuse of MPLS to carry ethernet frames Configuring a label switch router Linux Both eth0 and eth1 in label space 1 ● mplsadm -L eth0:1 mplsadm -L eth1:1 Configuring a label switch router Linux Configure label switching ● mplsadm -A -I gen:10:1 -O gen:20:ipv4:10.3.0.2 -B mplsadm -A -I gen:21:1 -O gen:11:ipv4:10.2.0.1 -B – -A -B: add and bind – -I: incoming
Load more

Recommended publications
  • Transparent LAN Service Over Cable
    Transparent LAN Service over Cable This document describes the Transparent LAN Service (TLS) over Cable feature, which enhances existing Wide Area Network (WAN) support to provide more flexible Managed Access for multiple Internet service provider (ISP) support over a hybrid fiber-coaxial (HFC) cable network. This feature allows service providers to create a Layer 2 tunnel by mapping an upstream service identifier (SID) to an IEEE 802.1Q Virtual Local Area Network (VLAN). Finding Feature Information Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An account on http:// www.cisco.com/ is not required. Contents • Hardware Compatibility Matrix for Cisco cBR Series Routers, page 2 • Prerequisites for Transparent LAN Service over Cable, page 2 • Restrictions for Transparent LAN Service over Cable, page 3 • Information About Transparent LAN Service over Cable, page 3 • How to Configure the Transparent LAN Service over Cable, page 6 • Configuration Examples for Transparent LAN Service over Cable, page 8 • Verifying the Transparent LAN Service over Cable Configuration, page 10 • Additional References, page 11 • Feature Information for Transparent LAN Service over Cable, page 12 Cisco Converged Broadband Routers Software Configuration Guide For DOCSIS 1 Transparent LAN Service over Cable Hardware Compatibility Matrix for Cisco cBR Series Routers Hardware Compatibility Matrix for Cisco cBR Series Routers Note The hardware components introduced in a given Cisco IOS-XE Release are supported in all subsequent releases unless otherwise specified.
    [Show full text]
  • Ieee 802.1 for Homenet
    IEEE802.org/1 IEEE 802.1 FOR HOMENET March 14, 2013 IEEE 802.1 for Homenet 2 Authors IEEE 802.1 for Homenet 3 IEEE 802.1 Task Groups • Interworking (IWK, Stephen Haddock) • Internetworking among 802 LANs, MANs and other wide area networks • Time Sensitive Networks (TSN, Michael David Johas Teener) • Formerly called Audio Video Bridging (AVB) Task Group • Time-synchronized low latency streaming services through IEEE 802 networks • Data Center Bridging (DCB, Pat Thaler) • Enhancements to existing 802.1 bridge specifications to satisfy the requirements of protocols and applications in the data center, e.g. • Security (Mick Seaman) • Maintenance (Glenn Parsons) IEEE 802.1 for Homenet 4 Basic Principles • MAC addresses are “identifier” addresses, not “location” addresses • This is a major Layer 2 value, not a defect! • Bridge forwarding is based on • Destination MAC • VLAN ID (VID) • Frame filtering for only forwarding to proper outbound ports(s) • Frame is forwarded to every port (except for reception port) within the frame's VLAN if it is not known where to send it • Filter (unnecessary) ports if it is known where to send the frame (e.g. frame is only forwarded towards the destination) • Quality of Service (QoS) is implemented after the forwarding decision based on • Priority • Drop Eligibility • Time IEEE 802.1 for Homenet 5 Data Plane Today • 802.1Q today is 802.Q-2011 (Revision 2013 is ongoing) • Note that if the year is not given in the name of the standard, then it refers to the latest revision, e.g. today 802.1Q = 802.1Q-2011 and 802.1D
    [Show full text]
  • Understand Vlans, Wired Lans, and Wireless Lans
    LESSON 1,2_B 98-366 Networking Fundamentals UnderstandUnderstand VLANs,VLANs, WiredWired LANs,LANs, andand WirelessWireless LANsLANs LESSON 1.2_B 98-366 Networking Fundamentals Lesson Overview In this lesson, you will review: Wired local area networks Wireless local area networks Virtual local area networks (VLANs) LESSON 1.2_B 98-366 Networking Fundamentals Anticipatory Set Explain why wireless networks are so popular, especially in homes Describe the elements that make up a wireless network What is the opposite of a wireless network? LESSON 1.2_B 98-366 Networking Fundamentals LAN A local area network (LAN) is a single broadcast domain. This means the broadcast will be received by every other user on the LAN if a user broadcasts information on his/her LAN. Broadcasts are prevented from leaving a LAN by using a router. Wired LAN An electronic circuit or hardware grouping in which the configuration is determined by the physical interconnection of the components LESSON 1.2_B 98-366 Networking Fundamentals Wireless LAN Communications that take place without the use of interconnecting wires or cables, such as by radio, microwave, or infrared light Wireless networks can be installed: o Peer-to-peer “Ad hoc” mode—wireless devices can communicate with each other o "Infrastructure" mode—allows wireless devices to communicate with a central node that can communicate with wired nodes on that LAN LESSON 1.2_B 98-366 Networking Fundamentals Sample example of a wireless LAN design: LESSON 1.2_B 98-366 Networking Fundamentals Wired LANs: Advantages Most wired LANs are built with inexpensive hardware: 1. Network adapter 2. Ethernet cables 3.
    [Show full text]
  • (Rapid) Spanning Tree Protocol
    STP – Spanning Tree Protocol indigoo.com STP & RSTP (RAPID) SPANNING TREE PROTOCOL DESCRIPTION OF STP AND RSTP, PROTOCOLS FOR LOOP FREE LAN TOPOLOGIES Peter R. Egli INDIGOO.COM1/57 © Peter R. Egli 2015 Rev. 1.60 STP – Spanning Tree Protocol indigoo.com Contents 1. Goal of STP: Loop-free topology for Ethernet networks 2. STP standards overview 3. IEEE 802.1D STP protocol 4. IEEE 802.1w RSTP Rapid STP 5. IEEE 802.1Q CST Common Spanning Tree 6. Cisco PVST+ and PVRST+ 7. IEEE 802.1s MST Multiple Spanning Tree Protocol 8. STP Pros and Cons 2/57 © Peter R. Egli 2015 Rev. 1.60 STP – Spanning Tree Protocol indigoo.com 1. Goal of STP: Loop-free topology for Ethernet networks Ethernet bridges (or switches) must forward unknown unicast and broadcast Ethernet frames to all physical ports. Therefore Ethernet networks require a loop-free topology, otherwise more and more broadcast and unknown unicast frames would swamp the network (creation of frame duplicates resulting in a broadcast storm). Unknown unicast frame: Frame with a target Ethernet address that is not yet known by the receiving bridge. Broadcast frame: Ethernet frame with a broadcast target Ethernet address, e.g. for protocols such as ARP or BOOTP / DHCP. Broadcast Ethernet frames and unknown unicast frames circle forever in an Ethernet network with loops. 3/57 © Peter R. Egli 2015 Rev. 1.60 STP – Spanning Tree Protocol indigoo.com 2. STP standards overview: A number of different STP ‘standards’ and protocols evolved over time. Standard Description Abbreviation Spanning Tree Protocol • Loop prevention. IEEE 802.1D • Automatic reconfiguration of tree in case of topology changes (e.g.
    [Show full text]
  • Refs. 769001, 769002 Art
    Refs. 769001, 769002 Art. Nr. WAVEDATAP, WAVEDATAS WaveData AP MyNETWiFi User Guide www.televes.com Table of Contents Important Safety Instructions ..................................................................................... 4 EN Introduction ................................................................................................................. 4 WaveData highlights .............................................................................................. 4 WaveData Package content .................................................................................. 5 Security Considerations ............................................................................................. 5 Operating Considerations .......................................................................................... 5 ENGLISH WaveData Device ........................................................................................................ 5 Port Connections .................................................................................................. 5 Device Buttons ...................................................................................................... 6 Device Leds ........................................................................................................... 6 Installing WaveData ..................................................................................................... 7 Installation example Ref.769001 .......................................................................... 7 Installation
    [Show full text]
  • Sample Architecture for Avaya IP Telephony Solutions with Extreme Networks and Juniper Networks - Issue 1.0
    Avaya Solution & Interoperability Test Lab Sample Architecture for Avaya IP Telephony Solutions with Extreme Networks and Juniper Networks - Issue 1.0 Abstract These Application Notes describe the configuration used for interoperability testing conducted between Avaya, Extreme Networks, Juniper Networks and Infoblox. The configuration consists of two locations, Site A and Site B, which were interconnected via serial links over a Wide Area Network (WAN). Testing included aspects of High Availability (HA) architecture, redundant design, Quality of Service (QoS) for voice communications, 802.11x port authentication and firewall Application Layer Gateway (ALG) security. The test cases were designed to confirm basic functionality amongst the vendors in the configuration at Layers 2 through 7. All test cases completed successfully. Information in these Application Notes has been obtained through compliance testing and additional technical discussions. Testing was conducted via the DeveloperConnection Program at the Avaya Solution & Interoperability Test Lab. GAK/SZ; Reviewed: Solution & Interoperability Test Lab Application Notes 1 of 47 SPOC 9/28/2005 ©2005 Avaya Inc. All Rights Reserved. aejarch.doc 1. Introduction The Application Notes provide a sample architecture demonstrating interoperability of products and solutions from Avaya, Extreme Networks, Juniper Networks and Infoblox. Figure 1 depicts the sample configuration. Figure 1: Sample Reference Architecture Configuration GAK/SZ; Reviewed: Solution & Interoperability Test Lab Application Notes 2 of 47 SPOC 9/28/2005 ©2005 Avaya Inc. All Rights Reserved. aejarch.doc An Avaya S8700 IP-Connect based system was used at Site A, depicted in Figure 2. Duplicated IP Server Interface (IPSI) circuit packs were used to provide “High” reliability to the two IPSI- connected G650 Media Gateways.
    [Show full text]
  • Layer 2 Virtual Private Networks CM-SP-L2VPN-I11-130808
    Data-Over-Cable Service Interface Specifications Business Services over DOCSIS® Layer 2 Virtual Private Networks CM-SP-L2VPN-I11-130808 ISSUED Notice This DOCSIS specification is the result of a cooperative effort undertaken at the direction of Cable Television Laboratories, Inc. for the benefit of the cable industry and its customers. This document may contain references to other documents not owned or controlled by CableLabs®. Use and understanding of this document may require access to such other documents. Designing, manufacturing, distributing, using, selling, or servicing products, or providing services, based on this document may require intellectual property licenses from third parties for technology referenced in this document. Neither CableLabs nor any member company is responsible to any party for any liability of any nature whatsoever resulting from or arising out of use or reliance upon this document, or any document referenced herein. This document is furnished on an "AS IS" basis and neither CableLabs nor its members provides any representation or warranty, express or implied, regarding the accuracy, completeness, noninfringement, or fitness for a particular purpose of this document, or any document referenced herein. Cable Television Laboratories, Inc., 2006-2013 CM-SP-L2VPN-I11-130808 Data-Over-Cable Service Interface Specifications DISCLAIMER This document is published by Cable Television Laboratories, Inc. ("CableLabs®"). CableLabs reserves the right to revise this document for any reason including, but not limited to, changes in laws, regulations, or standards promulgated by various agencies; technological advances; or changes in equipment design, manufacturing techniques, or operating procedures described, or referred to, herein. CableLabs makes no representation or warranty, express or implied, with respect to the completeness, accuracy, or utility of the document or any information or opinion contained in the report.
    [Show full text]
  • 7-Port Gigabit Ethernet Switch with Audio Video Bridging and Two RGMII/MII/RMII Interfaces
    KSZ9567R 7-Port Gigabit Ethernet Switch with Audio Video Bridging and Two RGMII/MII/RMII Interfaces Highlights • Five Integrated PHY Ports - 1000BASE-T/100BASE-TX/10BASE-Te IEEE 802.3 • Non-blocking wire-speed Ethernet switching fabric - Fast Link-up option significantly reduces link-up time • Full-featured forwarding and filtering control, includ- - Auto-negotiation and Auto-MDI/MDI-X support ing Access Control List (ACL) filtering - On-chip termination resistors and internal biasing for • Full VLAN and QoS support differential pairs to reduce power • Five ports with integrated 10/100/1000BASE-T PHY - LinkMD® cable diagnostic capabilities for determining transceivers cable opens, shorts, and length • Two ports with 10/100/1000 Ethernet MACs and con- • Advanced Switch Capabilities figurable RGMII/MII/RMII interfaces - IEEE 802.1Q VLAN support for 128 active VLAN • IEEE 1588v2 Precision Time Protocol (PTP) support groups and the full range of 4096 VLAN IDs - IEEE 802.1p/Q tag insertion/removal on per port basis • IEEE 802.1AS/Qav Audio Video Bridging (AVB) - VLAN ID on per port or VLAN basis • IEEE 802.1X access control support - IEEE 802.3x full-duplex flow control and half-duplex • EtherGreen™ power management features, back pressure collision control including low power standby - IEEE 802.1X access control 2 • Flexible management interface options: SPI, I C, (Port-based and MAC address based) MIIM, and in-band management via any port - IGMP v1/v2/v3 snooping for multicast packet filtering • Industrial temperature range support - IPv6
    [Show full text]
  • Red Hat Virtualization 4.3 Planning and Prerequisites Guide
    Red Hat Virtualization 4.3 Planning and Prerequisites Guide Planning for the Installation and Configuration of Red Hat Virtualization 4.3 Last Updated: 2019-05-09 Red Hat Virtualization 4.3 Planning and Prerequisites Guide Planning for the Installation and Configuration of Red Hat Virtualization 4.3 Red Hat Virtualization Documentation Team Red Hat Customer Content Services [email protected] Legal Notice Copyright © 2019 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • Traveo™ II Ethernet Mac
    Customer Training Workshop Traveo™ II Ethernet Mac Q1 2021 Target Products › Target product list for this training material Family Category Series Code Flash Memory Size Traveo™ II Automotive Body Controller High CYT3BB/4BB Up to 4160 KB Traveo II Automotive Body Controller High CYT4BF Up to 8384 KB Traveo II Automotive Cluster CYT3DL Up to 4160 KB Traveo II Automotive Cluster CYT4DN Up to 6336 KB 002-25166 *D 2021-02-12 Copyright © Infineon Technologies AG 2021. All rights reserved. 2 Introduction to Traveo II Body Controller High › Ethernet MAC is located in the peripheral blocks Hint Bar ITCM DTCM CPU Subsystem ITCM16 KB DTCM16 KB SWJ/ETM/ITM/CTI Review TRM section 31 for CYT4BF 16 KB 16 KB MXS40-HT SWJ/ETM/ITM/CTI SWJ/MTB/CTI additional details Cortex M7 143Channel M P P 65 Channel 65 ASIL-B eCT FLASH Channel 8 CRYPTO - - 350 MHz - DMA1 Arm Cortex-M7 SRAM0 SRAM1 SRAM2 DMA0 ROM 8384 KB Code Flash DMA0 AES, SHA, CRC, Arm 350 MHz 512 KB 256 KB 256 KB TRNG, RSA, 64 KB FPU D$ I$ + 256 KB Work Flash Cortex-M0+ (SP/DP) 16KB 16KB ECC System Resources FPU D$ I$ AHBP NVIC, MPU, AXI AHBS 100 MHz (SP/DP) 16 KB 16 KB 8 KB $ SRAM SRAM SRAM Power Initiator/MMIO ROM Controller AHBP NVIC, MPU, AXI AHBS FLASH Controller Controller Controller Controller MUL, NVIC, MPU Sleep Control POR BOD OVP LVD System Interconnect (Multi Layer AXI/AHB, IPC, MPU/SMPU) REF PWRSYS-HT LDO PCLK Peripheral Interconnect (MMIO, PPU) (Hyperbus,Memory Single SPI, Serial Interface Clock Clock Control SPI,DualQuadOctal SPI) SPI, 10/100/1000 Ethernet 10/100/1000 + AVB 2xILO WDT Prog.
    [Show full text]
  • LAN Planning Guide
    LAN Planning Guide LAST UPDATED: 1 May 2013 LAN Planning Guide XO Hosted PBX Document version: 1.05 Issue date: 1 May 2013 © Copyright 5/1/2013. XO Communications, LLC. All rights reserved. XO, the XO design logo, and all related marks are trademarks of XO Communications, LLC. All other trademarks are property of their respective owners. LAN Planning Guide LAST UPDATED: 1 May 2013 Table of Contents Table of Contents ..................................................................................................................................................................... i About this Document............................................................................................................................................................... 1 Introduction: Components of XO Hosted PBX ......................................................................................................................... 1 LAN Fundamentals .................................................................................................................................................................. 2 Cabling and Power ............................................................................................................................................................... 2 Ethernet switching .................................................................................................................................................................. 2 Quality of Service Settings .....................................................................................................................................................
    [Show full text]
  • V1.1.1 (2014-09)
    Final draft ETSI ES 203 385 V1.1.1 (2014-09) ETSI STANDARD CABLE; DOCSIS® Layer 2 Virtual Private Networking 2 Final draft ETSI ES 203 385 V1.1.1 (2014-09) Reference DES/CABLE-00008 Keywords access, broadband, cable, data, IP, IPcable, L2VPN, modem ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice The present document can be downloaded from: http://www.etsi.org The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI.
    [Show full text]