DOCSLIB.ORG

Transparent LAN Service Over Cable

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
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. Table 1: Hardware Compatibility Matrix for the Cisco cBR Series Routers Cisco CMTS Platform Processor Engine Interface Cards Cisco cBR-8 Converged Cisco IOS-XE Release 3.15.0S Cisco IOS-XE Release 3.15.0S Broadband Router and Later Releases and Later Releases Cisco cBR-8 Supervisor: Cisco cBR-8 CCAP Line Cards: • PID—CBR-CCAP-SUP-160G • PID—CBR-LC-8D30-16U30 • PID—CBR-CCAP-SUP-60G1 • PID—CBR-LC-8D31-16U30 • PID—CBR-SUP-8X10G-PIC • PID—CBR-RF-PIC • PID—CBR-RF-PROT-PIC Cisco cBR-8 Downstream PHY Modules: • PID—CBR-D30-DS-MOD • PID—CBR-D31-DS-MOD Cisco cBR-8 Upstream PHY Modules: • PID—CBR-D30-US-MOD 1 Effective with Cisco IOS-XE Release 3.17.0S, CBR-CCAP-SUP-60G supports 8 cable line cards. The total traffic rate is limited to 60Gbps, the total number of downstream service flow is limited to 72268, and downstream unicast low-latency flow does not count against the limits. Prerequisites for Transparent LAN Service over Cable • You must know the hardware (MAC) addresses of the cable modems that are to be mapped to IEEE 802.1Q VLANs. • You must create a bridge group for each separate customer on the Layer 2 bridge aggregator, so that traffic from all of the Customer Premises Equipment (CPE) devices for the customer is grouped together into the same 802.1Q tunnel. Cisco Converged Broadband Routers Software Configuration Guide For DOCSIS 2 Transparent LAN Service over Cable Restrictions for Transparent LAN Service over Cable Restrictions for Transparent LAN Service over Cable • Configuring 802.1Q for a particular cable modem removes any previous cable modem configuration on the router. • We strongly recommend that TLS over Cable only be used when Baseline Privacy Interface (BPI) is enabled in the environment. If BPI is not enabled when using the TLS feature, traffic can flow between multiple virtual private networks (VPNs), and become vulnerable to denial-of-service attacks or snooping. We also recommend that remote networks be isolated with a gateway or firewall router when BPI is not enabled. When the TLS feature is used with Layer 2 VPNs, the participating cable modems must have the Baseline Privacy Interface security feature (BPI) enabled. Otherwise, the Cisco CMTS drops such Layer 2 traffic in the upstream or downstream. • Packets are mapped to their Layer 2 tunnel only on the basis of Layer 2 information (the cable modem’s MAC address and primary SID). Layer 3 services, such as access lists, IP address source-verify, and IP QoS, are not supported as packets are sent through the tunnel. • All traffic from a cable modem is mapped to the same Layer 2 tunnel. It is not possible to differentiate traffic from different customer premises equipment (CPE) devices behind the cable modem. • CPE learning is not available when using the Transparent LAN Service over Cable feature. When a cable modem is mapped to a Layer 2 tunnel, the show interface cable modem command shows that the IP addresses for its CPE devices are “unavailable.” • DOCSIS QoS is supported across the Layer 2 tunnel only on the primary SID. Traffic using secondary services uses the same Layer 2 tunnel as the primary SID. • The Spanning Tree Protocol (STP) cannot be used with devices (cable modems, their CPE devices, and the endpoint CPE devices) that are using this feature. In particular, Spanning Tree Protocol cannot be used between the VLAN bridge aggregator and the endpoint customer devices. • The following restrictions apply to Layer 2 tunnels over an Ethernet IEEE 802.1Q VLAN interface: ◦ IEEE 802.1Q tunnels are supported only on Ten Gigabit Ethernet interfaces. ◦ The Cisco CMTS router supports a maximum of 4095 VLAN IDs, but the switches acting as the bridge aggregator might support a lower number of VLAN IDs. If this is the case, the Cisco CMTS should be configured only for the maximum number of VLANs that are supported by the bridge aggregator switches. Information About Transparent LAN Service over Cable This section contains the following: Cisco Converged Broadband Routers Software Configuration Guide For DOCSIS 3 Transparent LAN Service over Cable Feature Overview Feature Overview The Transparent LAN Service over Cable feature enables service providers to provide Layer 2 tunnels for traffic to and from cable modems. This allows customers to create their own virtual local area network (VLAN) using any number of cable modems in multiple sites. On the Cisco CMTS, you map each cable modem (on the basis of its MAC address) to the appropriate VLAN. The CMTS then creates an internal database of this one-to-one mapping of cable modems to VLANs, and uses it to encapsulate packets for the appropriate VLAN. The CMTS encapsulates the CPE traffic from mapped cable modems using the following method: • IEEE 802.1Q Mapping—The cable modem’s MAC address is mapped to an IEEE 802.1Q VLAN on a specific Ten Gigabit Ethernet interface, so that all traffic from the cable modem is tagged with the specified VLAN ID. Traffic to and from this group of cable modems is bridged into a single logical network (the VLAN) by the bridge aggregator, creating a secure Virtual Private Network (VPN) for that particular group of cable modems. Traffic in one VLAN cannot be sent into another VLAN, unless specifically done so by an external router. The switch acting as the Layer 2 Bridge Aggregator uses the VLAN tagging to forward the traffic to the appropriate destination. This frees up service providers from needing to know the addressing, routing, and topological details of the customer’s network. Transparent LAN Service and Layer 2 Virtual Private Networks In addition, service providers can provide a Layer 2 VPN with only minimal configuration changes on the provider’s routers. The service subscriber does not need to make any changes to their private network or cable modems, nor does the service provider have to provide any special DOCSIS configuration files to enable this feature. For the TLS feature with Layer 2 VPNs: • When the TLS feature is used with Layer 2 VPNs, the participating cable modems must have the Baseline Privacy Interface security feature (BPI) enabled. Otherwise, the Cisco CMTS drops such Layer 2 traffic in the upstream or downstream. • Information about Customer Premises Equipment (CPE) does not display in the output of the show cable modem command. IEEE 802.1Q Mapping This section describes the mapping of cable modems to an IEEE 802.1Q VLAN, as it is available in the Transparent LAN Service over Cable feature: Overview The Transparent LAN Service over Cable feature enables service providers to provide Layer 2 tunnels over an Ethernet network, using IEEE 802.1Q standard tags. This allows customers to create their own virtual network using any number of cable modems in different sites. Cisco Converged Broadband Routers Software Configuration Guide For DOCSIS 4 Transparent LAN Service over Cable Benefits On the Cisco CMTS, you map each cable modem (on the basis of its MAC address) to the appropriate VLAN. The CMTS then creates an internal database of this one-to-one mapping of cable modems to VLANs, and uses it to encapsulate packets for the appropriate VLAN. The CMTS encapsulates the CPE traffic from mapped cable modems using VLAN tags, as defined in IEEE 802.1Q-1993, IEEE Standards for Local and Metropolitan Area Networks: Virtual Bridged Local Area Networks . The switch acting as the Layer 2 Bridge Aggregator uses the VLAN tagging to forward the packets to the appropriate destination. Traffic to and from this group of cable modems is bridged into a single logical network by the bridge aggregator, creating a secure Virtual Private Network (VPN) for that particular group of cable modems. Traffic in one VLAN cannot be sent into another VLAN, unless specifically done so by an external router.
Load more

Recommended publications
  • 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]
  • Introduction to Spanning Tree Protocol by George Thomas, Contemporary Controls
    Volume6•Issue5 SEPTEMBER–OCTOBER 2005 © 2005 Contemporary Control Systems, Inc. Introduction to Spanning Tree Protocol By George Thomas, Contemporary Controls Introduction powered and its memory cleared (Bridge 2 will be added later). In an industrial automation application that relies heavily Station 1 sends a message to on the health of the Ethernet network that attaches all the station 11 followed by Station 2 controllers and computers together, a concern exists about sending a message to Station 11. what would happen if the network fails? Since cable failure is These messages will traverse the the most likely mishap, cable redundancy is suggested by bridge from one LAN to the configuring the network in either a ring or by carrying parallel other. This process is called branches. If one of the segments is lost, then communication “relaying” or “forwarding.” The will continue down a parallel path or around the unbroken database in the bridge will note portion of the ring. The problem with these approaches is the source addresses of Stations that Ethernet supports neither of these topologies without 1 and 2 as arriving on Port A. This special equipment. However, this issue is addressed in an process is called “learning.” When IEEE standard numbered 802.1D that covers bridges, and in Station 11 responds to either this standard the concept of the Spanning Tree Protocol Station 1 or 2, the database will (STP) is introduced. note that Station 11 is on Port B. IEEE 802.1D If Station 1 sends a message to Figure 1. The addition of Station 2, the bridge will do ANSI/IEEE Std 802.1D, 1998 edition addresses the Bridge 2 creates a loop.
    [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]
  • Analysis of Qos in Software Defined Wireless Network with Spanning Tree Protocol
    I. J. Computer Network and Information Security, 2017, 6, 61-68 Published Online June 2017 in MECS (http://www.mecs-press.org/) DOI: 10.5815/ijcnis.2017.06.07 Analysis of QoS in Software Defined Wireless Network with Spanning Tree Protocol Rafid Mustafiz, Abu Sayem Mohammad Delowar Hossain, Nazrul Islam+, Mohammad Motiur Rahman Department of Computer Science and Engineering +Department of Information and Communication Technology Mawlana Bhashani Science and Technology University, Santosh, Tangail-1902, Bangladesh E-mail: [email protected], [email protected], [email protected], [email protected] Abstract—Software Defined Network (SDN) is more technique. The data controlling actions are controlled by dynamic, manageable, adaptive and programmable a software or hardware based centralized controller and network architecture. This architecture separates the data forwarding task has performed by a hardware core control plane from the forwarding plane that enables the device [3]. This enables the control plane to be directly network to become directly programmable. The programmable which makes it suitable in the field of programmable features of SDN technology has research. Data plane functionality contains features such dramatically improved network efficiency and simplify as quality of service (QoS) [4]. The overall performance the network configuration and resource management. of a network topology depends mostly on the parameters SDN supports Open-Flow technology as forwarding of QoS. The present goal of SDN is to design a network function and centralized control successfully. Wireless that is capable the maximum improvement of QoS environment has recently added to the SDN infrastructure parameters. SDN supports many new types of that has rapidly emerged with Open-Flow protocol.
    [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]