A Survey of Virtual LAN Usage in Campus Networks

Total Page:16

File Type:pdf, Size:1020Kb

A Survey of Virtual LAN Usage in Campus Networks YU LAYOUT 6/20/11 4:24 PM Page 98 TOPICS IN NETWORK AND SERVICE MANAGEMENT A Survey of Virtual LAN Usage in Campus Networks Minlan Yu and Jennifer Rexford, Princeton University Xin Sun and Sanjay Rao, Purdue University Nick Feamster, Georgia Institute of Technology ABSTRACT router configuration data, we have obtained deeper insights into how the administrators use VLANs are widely used in today’s enterprise VLANs to achieve a variety of design goals, and networks to improve Ethernet scalability and the difficulties they encounter in the process. We support network policies. However, manuals and show that VLANs are not well-suited for many textbooks offer very little information about how of the tasks that they support today, and argue VLANs are actually used in practice. Through that future enterprise network architectures discussions with network administrators and anal- should decouple policy specification from scala- ysis of configuration data, we describe how three bility concerns with layer-2 protocols, topology, university campuses and one academic depart- and addressing. ment use VLANs to achieve a variety of goals. After a brief survey of VLAN technology, we We argue that VLANs are ill-suited to some of describe how the four networks use VLANs to these goals (e.g., VLANs are often used to real- support resource isolation, access control, decen- ize access control policies, but constrain the types tralized management, and host mobility. Howev- of policies that can be expressed). Furthermore, er, VLANs were not designed with these goals in the use of VLANs leads to significant complexity mind — network administrators use VLANs for in the configuration of network devices. the lack of a better alternative. We argue that VLANs are too crude a mechanism for specify- INTRODUCTION ing policies, due to scalability constraints (on the number and size of VLANs) and the coarse- Enterprise networks, which connect the comput- grained ways of assigning traffic to different ers within a college campus or corporate loca- VLANs. Further, VLAN configuration is far too tion, differ markedly from backbone networks. complicated, due to the tight coupling with span- These networks have distinctive topologies, pro- ning-tree construction, failure recovery, host tocols, policies, and configuration practices. Yet, address assignment, and IP routing, as discussed. the unique challenges in enterprise networks are We conclude the article. not well understood outside of the operator community. One prominent example is virtual LANs (VLANs) — a widely- used technology VIRTUAL LOCAL AREA NETWORKS that is barely discussed in networking textbooks. VLANs were initially intended to allow net- An enterprise network consists of islands of Eth- work administrators to connect a group of hosts ernet switches connected both to each other and in the same broadcast domain, independent of to the rest of the Internet by IP routers, as shown their physical location. However, today’s enter- in Fig. 1. We describe how administrators group prise administrators use VLANs for a variety of related hosts into VLANs, and how the switches other purposes, most notably for better scalabili- and routers forward traffic between hosts. ty and flexible specification of policies. However, enterprise administrators have seen many prob- CONVENTIONAL LOCAL AREA NETWORKS lems of VLANs because VLANs are used for other functions they were not designed for. In a traditional local area network (LAN), hosts Understandably, VLANs are at best an incom- are connected by a network of hubs and switch- plete solution for some of these problems. As a es. The switches cooperate to construct a span- result, managing VLANs is one of the most chal- ning tree for delivering traffic. Each switch lenging tasks they face. forwards Ethernet frames based on its destina- In this article, we study four networks — tion MAC address. If the switch contains no for- three university campuses and one academic warding-table entry for the frame’s destination department — to better understand how VLANs MAC address, the switch floods each frame over are used in practice. Through discussions with the entire spanning tree. A switch learns how to network administrators, and targeted analysis of reach a MAC address by remembering the 98 0163-6804/11/$25.00 © 2011 IEEE IEEE Communications Magazine • July 2011 YU LAYOUT 6/20/11 4:24 PM Page 99 incoming link for frames sent by that MAC address and creating a mapping between the H3 MAC address and that port. H4 To connect to the rest of the enterprise net- Ethernet island work (and the rest of the Internet), the island of R2 VLAN2 S5 VLAN1 Ethernet switches connects to IP routers that forward traffic to and from remote hosts. Each S2 R1 host interface in the LAN has an IP address S4 S6 from a common IP prefix (or set of prefixes). S1 IP router R3 Traffic sent to an IP address in the same subnet backbone S3 stays within the LAN; the sending host uses the VLAN1 Address Resolution Protocol (ARP) to deter- R5 VLAN2 H1 R4 mine the MAC address associated with the desti- Ethernet nation IP address. For traffic destined to remote H2 island Ethernet IP addresses, the host forwards the packets to island the gateway router, which forwards packets fur- ther toward their destinations. Figure 1. Enterprise network with Ethernet islands interconnected by IP routers. COMMUNICATION WITHIN A VLAN Administrators use VLANs to construct network segments that behave logically like a convention- port, which is connected to a host; or a trunk al LAN but are independent of the physical port, which is connected to another switch. An locations of the hosts; for example, hosts H1 and access port typically transports traffic for a single H3 in Fig. 1 both belong to VLAN1. As in a VLAN; the VLAN associated with a port may conventional physical LAN, the switches in a be either statically configured or dynamically VLAN construct a spanning tree, and use flood- assigned when the host connects, based on the ing and learning to forward traffic between host’s MAC address (e.g., using VLAN Manage- hosts. For example, the switches S3, S4, and S5 ment Policy Server VMPS [1]). In either case, form a spanning tree for VLAN2. the access port can tag incoming frames with the Communication between hosts in the same 12-bit VLAN identifier and removes the tag VLAN stays within the VLAN, with the switches from outgoing frames, obviating the need for the forwarding Ethernet frames along the spanning hosts to support VLANs. tree to the destination MAC address. For exam- In contrast, a trunk port may carry traffic for ple, hosts H2 and H4 communicate over the 2 multiple VLANs; for example, switch S4’s port spanning tree in VLAN2 based on their MAC connecting to S5 must forward traffic for both addresses. Similarly, hosts H1 and H3 communi- VLAN1 and VLAN2 (and participate in each cate over the spanning tree in VLAN1, where VLAN’s spanning tree protocol), but the trunk some of the IP routers (e.g., R1, R2, and R2) port to S3 does not. The administrators either may also act as switches in the spanning tree; manually configure each trunk port with a list of alternatively, a tunnel between R1 and R2 could VLAN identifiers, or run a protocol like VLAN participate in VLAN1 so the links in the IP back- Trunking Protocol (VTP) [2] or Multiple VLAN bone do not need to participate in the VLANs. Registration Protocol (MVRP) [3] to automati- cally determine which VLANs a trunk link should COMMUNICATION BBETWEEN VLANS handle. Configuring a VLAN also requires con- Each host has an IP address from an IP prefix figuring the gateway router to announce the asso- (or prefixes) associated with its VLAN; IP ciated IP prefixes into the routing protocol; each routers forward packets based on these prefixes, host interface must be assigned an IP address over paths computed in the routing protocol from the prefix associated with its VLAN. (e.g., Open Shortest Path First [OSPF] or Rout- ing Information Protocol [RIP]). Hence, traffic between hosts in different VLANs must traverse VLAN USAGE IN an intermediate IP router. For example, traffic AMPUS ETWORKS between hosts H3 and H4 would traverse router C N R2, even though the two hosts connect to the same Our campus network administrators use VLANs switch. For example, when sending traffic to H4, to achieve four main policy objectives — limiting host H3 forwards the packets to its gateway the scope of broadcast traffic, simplifying access router R2, since the destination IP address control policies, supporting decentralized net- belongs to a different prefix. R2 would then look work management, and enabling seamless host up the destination IP address to forward the mobility for wireless users. The four networks packet to H4 in VLAN2. If H4 sends an IP pack- include two large universities (campuses 1 and 2) et to H1, then H4’s router R3 forwards the pack- and a department network (campus 3) within et based on the IP routing protocol toward the another university-wide network (campus 4). All router announcing H1’s IP prefix, and that router four networks primarily run IPv4, with relatively would then forward the packet over the span- limited experimental deployment of IPv6. ning tree for VLAN1. SCOPING BROADCAST TRAFFIC CONFIGURING VLAN PORTS VLANs enable administrators to limit the scope Supporting VLANs requires a way to associate of broadcast traffic and network-wide flooding, switch ports with one or more VLANs. Adminis- to reduce network overhead and enhance both trators configure each port as either an access privacy and security. IEEE Communications Magazine • July 2011 99 YU LAYOUT 6/20/11 4:24 PM Page 100 Limiting the Broadcast/Flooding Overhead — are allowed to communicate freely.
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]
  • AT-GS950/16 Gigabit Ethernet Switch
    AT-GS950/16 Gigabit Ethernet Switch AT-GS950/16 Web Interface User Guide AT-S114 Version 1.1.0 [1.00.021] 613-001857 Rev A Copyright © 2013 Allied Telesis, Inc. All rights reserved. No part of this publication may be reproduced without prior written permission from Allied Telesis, Inc. Allied Telesis and the Allied Telesis logo are trademarks of Allied Telesis, Incorporated. All other product names, company names, logos or other designations mentioned herein are trademarks or registered trademarks of their respective owners. Allied Telesis, Inc. reserves the right to make changes in specifications and other information contained in this document without prior written notice. The information provided herein is subject to change without notice. In no event shall Allied Telesis, Inc. be liable for any incidental, special, indirect, or consequential damages whatsoever, including but not limited to lost profits, arising out of or related to this manual or the information contained herein, even if Allied Telesis, Inc. has been advised of, known, or should have known, the possibility of such damages. Contents List of Figures ................................................................................................................................................ 11 List of Tables ................................................................................................................................................. 15 Preface ...........................................................................................................................................................
    [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]
  • Vlans Feature Overview and Configuration Guide
    TechnicalTTechnicalechnical GuideGuidGuidee Virtual LANs (VLANs) Feature Overview and Configuration Guide VLAN Introduction This guide describes Virtual LANs (VLANs), VLAN features and configuration on the switch. It begins with a description of what a VLAN is, its evolution and purpose, and also provides the meaning of some common VLAN terminology. This is followed with a detailed look at VLAN implementation. Port-based VLAN membership is the most common way to split a network into sets of virtual LANs. We look at how this is achieved using the VLAN tagging. The use of double-tagging (or VLAN stacking) to tunnel VLANs across Layer 2 networks is described, and an example is provided for the configuration of VLAN stacking. Next we discuss private VLANs and the communication rules that limit what is possible between devices operating within the VLAN. AlliedWare Plus™ has two private VLAN solutions: private VLANs for ports in Access Mode private VLANs for ports in Trunked Mode Configuration examples are provided for both of these solutions. Then, we look at combining private VLANs with other features, such as: EPSR, ARP, LLDP, GVRP, Link aggregation, and management servers. The guide ends with a section on configuring protocol based VLANs and then describes how data counters are used to count both the number of received frames or the number of received bytes (octets) belonging to a particular VLAN. C613-22001-00 x REV C alliedtelesis.com Products and software version that apply to this guide This guide applies to all AlliedWare Plus™ products, running version 5.4.4 or later. However, not all features in this guide are supported on all products.
    [Show full text]