Data Center Bridging Consortium

Total Page:16

File Type:pdf, Size:1020Kb

Data Center Bridging Consortium Data Center Bridging Consortium 802.1Qaz DCB Exchange Protocol Test Suite Version 1.9 Technical Document Last Updated: April 10, 2012 Data Center Bridging Consortium HTTP://WWW.IOL.UNH.EDU/CONSORTIUMS/DCB InterOperability Laboratory 121 Technology Drive, Suite 2 University of New Hampshire Durham, NH 03824 Phone: +1-603-862-0701 © 2012 University of New Hampshire InterOperability Laboratory Table of Contents Table of Contents...........................................................................................................................2 Modification Record......................................................................................................................3 Acknowledgments..........................................................................................................................4 Introduction....................................................................................................................................5 References.......................................................................................................................................7 Test Setup.......................................................................................................................................8 Group 1: ETS Configuration and Recommendation Capability...............................................9 TEST #38.1.1: TRANSMISSION OF A WELL FORMED ETS CONFIGURATION TLV.............................10 TEST #38.1.2: TRANSMISSION OF A WELL FORMED ETS RECOMMENDATION TLV.........................11 TEST #38.1.3: VALIDATION OF THE ETS CONFIGURATION TLV WILLING BIT................................12 TEST #38.1.4: GRACEFULLY IGNORE MALFORMED ETS RECOMMENDATION TLV..........................14 Group 2: Priority-based Flow Control Capability...................................................................16 TEST #38.2.1: TRANSMISSION OF A WELL FORMED PRIORITY-BASED FLOW CONTROL TLV............17 TEST #38.2.2: VALIDATION OF THE PRIORITY-BASED FLOW CONTROL TLV WILLING BIT...............18 TEST #38.2.3: CORRECT SETTING OF REMOTE WILLING.................................................................20 TEST #38.2.4: GRACEFULLY IGNORE MALFORMED PRIORITY-BASED FLOW CONTROL TLV.............21 Group 3: Application Priority Capability.................................................................................22 TEST #38.3.1: TRANSMISSION OF A WELL FORMED APPLICATION PRIORITY TLV...........................23 TEST #38.3.2: GRACEFULLY IGNORE MALFORMED APPLICATION PRIORITY TLV............................24 TEST #38.3.3: TRANSMISSION OF FCOE SUPPORT TLV................................................................25 TEST #38.3.4: TRANSMISSION OF ISCSI SUPPORT TLV................................................................26 Group 4: Congestion Notification Capability...........................................................................27 TEST #38.4.1: TRANSMISSION OF A WELL FORMED CONGESTION NOTIFICATION TLV.....................28 TEST #38.4.2: GRACEFULLY IGNORE MALFORMED CONGESTION NOTIFICATION TLV......................29 Group 5: System Configuration.................................................................................................30 TEST #38.5.1: DCBX ENABLED BY DEFAULT...............................................................................31 TEST #38.5.2: MULTIPLE LLDP NEIGHBORS................................................................................32 © 2012 University of New Hampshire InterOperability Laboratory Modification Record 1. January 4, 2009 Initial Version (mhagen, rzarick) 2. March 5, 2010 Updated to latest standards, added Congestion NotificationTLV (mhagen) 3. October 8, 2010 Updated to draft 2.0 standard (mhagen) 4. December 15, 2010 Fixed ETS Configuration and PFC Configuration tests (mhagen) 5. January 6, 2011 Fixed a mistake in Test 38.3.2 (mhagen) 6. January 6, 2011 Rev 1.5 – cleaned up ETS Recommendation and Configurations (mhagen) 7. January 7, 2011 Fixed a mistake in Test 38.1.4 (dshea) 8. January 31, 2011 Fixed Malformed TLV tests (dshea) 9. March 18, 2011 Updated to draft 2.4 standard (mhagen) 10. April 10, 2012 Updated to the final version of the standard (mhagen) © 2012 University of New Hampshire InterOperability Laboratory Acknowledgments The University of New Hampshire would like to acknowledge the efforts of the following individuals in the development of this test suite. Mikkel Hagen University of New Hampshire Daniel Shea University of New Hampshire Ryan Zarick University of New Hampshire © 2012 University of New Hampshire InterOperability Laboratory Introduction Overview The University of New Hampshire’s InterOperability Laboratory (IOL) is an institution designed to improve the interoperability of standards based products by providing an environment where a product can be tested against other implementations of a standard. These tests are designed to determine if a DCB product conforms to specifications defined in IEEE Std 802.1Qaz-2011 Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks – Amendment 18: Enhanced Transmission Selection for Bandwidth Sharing Between Traffic Classes (hereafter referred to as “DCBX”). This suite of tests has been developed to help implementers evaluate the functioning of their Data Center Bridging based products. The tests do not determine if a product conforms to the IEEE standard, nor are they purely interoperability tests. Rather, they provide one method to isolate problems within a Data Center Bridging device. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other Data Center Bridging devices. However, combined with satisfactory operation in the IOL’s semi-production environment, these tests provide a reasonable level of confidence that the Device Under Test (DUT) will function well in most multi-vendor Data Center Bridging environments. Organization of Tests The tests contained in this document are organized to simplify the identification of information related to a test and to facilitate in the actual testing process. Each test contains an identification section that describes the test and provides cross-reference information. The detailed section discusses the background information and specifies how the test is to be performed. Tests are grouped in order to reduce setup time in the lab environment. Each test contains the following information: Test Number The Test Number associated with each test follows a simple grouping structure. Listed first is the Clause followed by the Test Group Number followed by the test's number within the group. This allows for the addition of future tests to the appropriate groups of the test suite without requiring the renumbering of the subsequent tests. Purpose The purpose is a short statement describing what the test attempts to achieve. The test is written at the functional level. References The references section lists cross-references to the IEEE standards and other documentation that might be helpful in understanding and evaluating the test and results. Resource Requirements The requirements section specifies the software, hardware, and test equipment that will be needed to perform the test. The items contained in this section are special test devices, software that must reside on the DUT, or other facilities, which may not be available on all devices. Last Modification This specifies the date of the last modification to this test. Discussion The discussion covers the assumptions made in the design or implementation of the test as well as known limitations. Other items specific to the test are covered here. © 2012 University of New Hampshire InterOperability Laboratory Test Setup The setup section describes in detail the configuration of the test environment and includes a block diagram for clarification as well as information such as the interconnection of devices, what monitoring equipment should capture, what the generation equipment should send, and any other configuration information vital to carrying out the test. Small changes in the configuration should be included in the test procedure. Procedure The procedure section of the test description contains the step-by-step instructions for carrying out the test. It provides a cookbook approach to testing, and will often be interspersed with observable results. Observable Results The observable results section lists observables that can be examined by the tester to verify that the DUT is operating properly. When multiple values are possible for an observable, this section provides a short discussion on how to interpret them. Note that complete delineation between the observables in the Procedure and Observable Results is virtually impossible. As such a careful note should be made of the requirements in both sections. In certain cases, it may be necessary to modify certain steps in the Procedure section while doing the actual tests so as to be able to perform the tests. In such cases, the modifications will be noted in the summary report. Possible Problems This section provides some clues to look for if the test does not yield the expected results. Legend For reasons of brevity, the following abbreviation has been used in the Test Suite: DCBX Data Center Bridging Capability Exchange DUT Device Under Test ETS Enhanced Transmission Selection PFC Priority-based Flow Control TS Testing Station © 2012 University of New Hampshire InterOperability Laboratory References The following documents are referenced
Recommended publications
  • On Ttethernet for Integrated Fault-Tolerant Spacecraft Networks
    On TTEthernet for Integrated Fault-Tolerant Spacecraft Networks Andrew Loveless∗ NASA Johnson Space Center, Houston, TX, 77058 There has recently been a push for adopting integrated modular avionics (IMA) princi- ples in designing spacecraft architectures. This consolidation of multiple vehicle functions to shared computing platforms can significantly reduce spacecraft cost, weight, and de- sign complexity. Ethernet technology is attractive for inclusion in more integrated avionic systems due to its high speed, flexibility, and the availability of inexpensive commercial off-the-shelf (COTS) components. Furthermore, Ethernet can be augmented with a variety of quality of service (QoS) enhancements that enable its use for transmitting critical data. TTEthernet introduces a decentralized clock synchronization paradigm enabling the use of time-triggered Ethernet messaging appropriate for hard real-time applications. TTEther- net can also provide two forms of event-driven communication, therefore accommodating the full spectrum of traffic criticality levels required in IMA architectures. This paper explores the application of TTEthernet technology to future IMA spacecraft architectures as part of the Avionics and Software (A&S) project chartered by NASA's Advanced Ex- ploration Systems (AES) program. Nomenclature A&S = Avionics and Software Project AA2 = Ascent Abort 2 AES = Advanced Exploration Systems Program ANTARES = Advanced NASA Technology Architecture for Exploration Studies API = Application Program Interface ARM = Asteroid Redirect Mission
    [Show full text]
  • Ethernet Alliance Hosts Third IEEE 802.1 Data Center Bridging
    MEDIA ALERT Ethernet Alliance® Hosts Third IEEE 802.1 Data Center Bridging Interoperability Test Event Participation is Open to Both Ethernet Alliance Members and Non‐Members WHAT: The Ethernet Alliance Ethernet in the Data Center Subcommittee has announced it will host an IEEE 802.1 Data Center Bridging (DCB) interoperability test event the week of May 23 in Durham, NH at the University of New Hampshire Interoperability Lab. The Ethernet Alliance invites both members and non‐members to participate in this third DCB test event that will include both protocol and applications testing. The event targets interoperability testing of Ethernet standards being developed by IEEE 802.1 DCB task force to address network convergence issues. Testing of protocols will include projects such as IEEE P802.1Qbb Priority Flow Control (PFC), IEEE P802.1Qaz Enhanced Transmission Selection (ETS) and DCB Capability Exchange Protocol (DCBX). The test event will include testing across a broad vendor community and will exercise DCB features across multiple platforms as well as exercise higher layer protocols such as Fibre Channel over Ethernet (FCoE), iSCSI over DCB, RDMA over Converged Ethernet (RoCE) and other latency sensitive applications. WHY: These test events help vendors create interoperable, market‐ready products that interoperate to the IEEE 802.1 DCB standards. WHEN: Conference Call for Interested Participants: Friday, March 4 at 10 AM PST Event Registration Open Until: March 4, 2011 Event Dates (tentative): May 23‐27, 2011 WHERE: University of New Hampshire Interoperability Lab (UNH‐IOL) Durham, NH WHO: The DCB Interoperability Event is hosted by the Ethernet Alliance. REGISTER: To get more information, learn about participation fees and/or register for the DCB plugfest, please visit Ethernet Alliance DCB Interoperability Test Event page or contact [email protected].
    [Show full text]
  • Data Center Ethernet 2
    DataData CenterCenter EthernetEthernet Raj Jain Washington University in Saint Louis Saint Louis, MO 63130 [email protected] These slides and audio/video recordings of this class lecture are at: http://www.cse.wustl.edu/~jain/cse570-15/ Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse570-15/ ©2015 Raj Jain 4-1 OverviewOverview 1. Residential vs. Data Center Ethernet 2. Review of Ethernet Addresses, devices, speeds, algorithms 3. Enhancements to Spanning Tree Protocol 4. Virtual LANs 5. Data Center Bridging Extensions Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse570-15/ ©2015 Raj Jain 4-2 Quiz:Quiz: TrueTrue oror False?False? Which of the following statements are generally true? T F p p Ethernet is a local area network (Local < 2km) p p Token ring, Token Bus, and CSMA/CD are the three most common LAN access methods. p p Ethernet uses CSMA/CD. p p Ethernet bridges use spanning tree for packet forwarding. p p Ethernet frames are 1518 bytes. p p Ethernet does not provide any delay guarantees. p p Ethernet has no congestion control. p p Ethernet has strict priorities. Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse570-15/ ©2015 Raj Jain 4-3 ResidentialResidential vs.vs. DataData CenterCenter EthernetEthernet Residential Data Center Distance: up to 200m r No limit Scale: Few MAC addresses r Millions of MAC Addresses 4096 VLANs r Millions of VLANs Q-in-Q Protection: Spanning tree r Rapid spanning tree, … (Gives 1s, need 50ms) Path determined by r Traffic engineered path spanning tree Simple service r Service Level Agreement.
    [Show full text]
  • PROFINET for Network Geeks
    PROFINET for Network Geeks (and those who want to be) Introduction PROFINET is an open Industrial Ethernet standard. It is a communication protocol that exchanges data between automation controllers and devices. With over 25 million installed nodes (as of 2018), PROFINET is one of the most widely used Industrial Ethernet standards worldwide. But even though millions of users are familiar with PROFINET, not all users understand how it works. This white paper starts with a brief overview of Ethernet and the 7-layer ISO-OSI model. Then, it describes how PROFINET’s 3 communication channels fit in the model: TCP/IP and UDP/IP, Real-Time (RT), and Isochronous Real-Time (IRT). 1 Ethernet The transition from using 4-20 mA analog signals for I/O communication to digital fieldbuses provided the benefits of reduced wiring, access to network data, and robust diagnostics. The later transition from digital fieldbuses to Ethernet was also similarly a shift to a more modern technology. Ethernet incorporated and improved upon the benefits of fieldbuses. Ethernet is ubiquitous and PROFINET uses standard Ethernet. Ethernet gives PROFINET the ability to provide faster updates, more bandwidth, larger messages, an unlimited address space, and even more diagnostic capabilities. Also, as commercial Ethernet evolves, PROFINET can take advantage of these physical layer improvements. Figure 1 ISO-OSI Model The ISO-OSI Model Ethernet-based communications can be represented by a seven-layer model: the ISO/OSI Reference Model. The model generically describes the means and methods used to transmit data. Each layer has a specific name and function, as shown in Figure 1.
    [Show full text]
  • Žilinská Univerzita V Žiline Elektrotechnická Fakulta Katedra Telekomunikácií
    Žilinská univerzita v Žiline Elektrotechnická fakulta Katedra telekomunikácií Teoretický návrh a realizácia sieťového uzla na báze protokolov 802.1Q, IP a BGP Pavol Križan 2006 Teoretický návrh a realizácia sieťového uzla na báze protokolov 802.1Q, IP a BGP DIPLOMOVÁ PRÁCA PAVOL KRIŽAN ŽILINSKÁ UNIVERZITA V ŽILINE Elektrotechnická fakulta Katedra telekomunikácií Študijný odbor: TELEKOMUNIKÁCIE Vedúci diplomovej práce: Ing. Peter Zuberec Stupeň kvalifikácie: inžinier (Ing.) Dátum odovzdania diplomovej práce: 19.05.2006 ŽILINA 2006 Abstrakt Diplomová práca popisuje základy fungovania počítačových sietí VLAN, protokoly, ktoré sa v nich využívajú a základy smerovacích protokolov, špeciálne Border Gateway Protokol (BGP). Práca sa tiež zaoberá vytvorením modelu sieťového uzla, ktorý bude poskytovať smerovanie s použitím BGP protokolu, podporu VLAN a vysokú redundanciu zariadení alebo liniek. This diploma work is dealing with basic functions of Virtual Local Area Networks, protocols used in those netwoks and basics of routing protocols, specially Border Gateway Protocol (BGP). It describes creation of network node, which will provide routing using BGP protocol, VLAN support and high redundancy of devices or links . Žilinská univerzita v Žiline, Elektrotechnická fakulta, Katedra telekomunikácií ________________________________________________________________________ ANOTAČNÝ ZÁZNAM - DIPLOMOVÁ PRÁCA Priezvisko, meno: Križan Pavol školský rok: 2005/2006 Názov práce: Teoretický návrh a realizácia sieťového uzla na báze protokolov 802.1Q, IP a BGP Počet strán: 50 Počet obrázkov: 23 Počet tabuliek: 0 Počet grafov: 0 Počet príloh: 0 Použitá lit.: 16 Anotácia: Diplomová práca popisuje základy fungovania počítačových sietí VLAN, protokoly, ktoré sa v nich využívajú a základy smerovacích protokolov, špeciálne Border Gateway Protokol (BGP). Práca sa tiež zaoberá vytvorením modelu sieťového uzla, ktorý bude poskytovať smerovanie s použitím BGP protokolu, podporu VLAN a vysokú redundanciu zariadení alebo liniek.
    [Show full text]
  • IEEE Std 802.3™-2012 New York, NY 10016-5997 (Revision of USA IEEE Std 802.3-2008)
    IEEE Standard for Ethernet IEEE Computer Society Sponsored by the LAN/MAN Standards Committee IEEE 3 Park Avenue IEEE Std 802.3™-2012 New York, NY 10016-5997 (Revision of USA IEEE Std 802.3-2008) 28 December 2012 IEEE Std 802.3™-2012 (Revision of IEEE Std 802.3-2008) IEEE Standard for Ethernet Sponsor LAN/MAN Standards Committee of the IEEE Computer Society Approved 30 August 2012 IEEE-SA Standard Board Abstract: Ethernet local area network operation is specified for selected speeds of operation from 1 Mb/s to 100 Gb/s using a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) allow use of selected Physical Layer devices (PHY) for operation over coaxial, twisted-pair or fiber optic cables. System considerations for multisegment shared access networks describe the use of Repeaters that are defined for operational speeds up to 1000 Mb/s. Local Area Network (LAN) operation is supported at all speeds. Other specified capabilities include various PHY types for access networks, PHYs suitable for metropolitan area network applications, and the provision of power over selected twisted-pair PHY types. Keywords: 10BASE; 100BASE; 1000BASE; 10GBASE; 40GBASE; 100GBASE; 10 Gigabit Ethernet; 40 Gigabit Ethernet; 100 Gigabit Ethernet; attachment unit interface; AUI; Auto Negotiation; Backplane Ethernet; data processing; DTE Power via the MDI; EPON; Ethernet; Ethernet in the First Mile; Ethernet passive optical network; Fast Ethernet; Gigabit Ethernet; GMII; information exchange; IEEE 802.3; local area network; management; medium dependent interface; media independent interface; MDI; MIB; MII; PHY; physical coding sublayer; Physical Layer; physical medium attachment; PMA; Power over Ethernet; repeater; type field; VLAN TAG; XGMII The Institute of Electrical and Electronics Engineers, Inc.
    [Show full text]
  • 10-Port 2.5GBASE-T Web Smart Switch with 2 X 10G SFP+ Slots
    TEG-30102WS 10-Port 2.5GBASE-T Web Smart Switch with 2 x 10G SFP+ Slots TEG-30102WS (v1.0R) • 8 x 2.5GBASE-T RJ-45 ports with 2 x 10G SFP+ slots • 2.5GBASE-T supports up to 2.5Gbps connection speeds • Compatible with existing Cat5e or better cabling • Easy to use web-based management interface • Supports up to 32 IPv4/IPv6 static routes • Supports LACP, VLAN, and IGMP Snooping • IEEE 802.1p QoS with queue scheduling support • Per port MAC restriction and dynamic ARP inspection • Bandwidth control per port • 80Gbps switching capacity • 1U rack mountable (brackets included) TRENDnet’s 10-Port 2.5GBASE-T Web Smart Switch with eight 2.5GBASE-T ports and two 10G SFP+ slots, model TEG-30102WS, delivers advanced management features with an 80Gbps switching capacity. The TEG-30102WS is equipped with 2.5GBASE-T RJ-45 ports that provide higher gigabit speeds capable of up to 2.5Gbps over existing Cat5e or better cabling. This rack mountable IPv6 ready switch comes with an intuitive web-based interface. Advanced traffic management controls include IP routing, VLAN, QoS, access controls, link aggregation, troubleshooting, and SNMP monitoring, making this a powerful solution for SMB networks. TEG-30102WS Web Smart Management 2.5GBASE-T Ports 10G SFP+ Slots Provides an easy to use web-based GUI Equipped with eight 2.5GBASE-T RJ-45 Offers two 10G SFP+ slots for high-speed management interface for advanced traffic ports that provide higher gigabit speeds network connections providing a cost- management controls, IP routing, VLAN, capable of up to 2.5Gbps over existing effective solution in adding 10G link QoS, access controls, link aggregation, Cat5e or better cabling.
    [Show full text]
  • Converged Networking in the Data Center
    Converged Networking in the Data Center Peter P. Waskiewicz Jr. LAN Access Division, Intel Corp. [email protected] Abstract data center as a whole. In addition to the general power and cooling costs, other areas of focus are the physical The networking world in Linux has undergone some sig- amount of servers and their associated cabling that re- nificant changes in the past two years. With the expan- side in a typical data center. Servers very often have sion of multiqueue networking, coupled with the grow- multiple network connections to various network seg- ing abundance of multi-core computers with 10 Gigabit ments, plus they’re usually connected to a SAN: ei- Ethernet, the concept of efficiently converging different ther a Fiber Channel fabric or an iSCSI infrastructure. network flows becomes a real possibility. These multiple network and SAN connections mean large amounts of cabling being laid down to attach a This paper presents the concepts behind network con- server. Converged Networking takes a 10GbE device vergence. Using the IEEE 802.1Qaz Priority Group- that is capable of Data Center Bridging in hardware, ing and Data Center Bridging concepts to group mul- and consolidates all of those network connections and tiple traffic flows, this paper will demonstrate how dif- SAN connections into a single, physical device and ca- ferent types of traffic, such as storage and LAN traf- ble. The rest of this paper will illustrate the different fic, can efficiently coexist on the same physical connec- aspects of Data Center Bridging, which is the network- tion.
    [Show full text]
  • Carrier Ethernet Tutorial
    Carrier . Ethernet Raj Jain Washington University in Saint Louis Saint Louis, MO 63130 [email protected] These slides and audio/video recordings of this class lecture are at: http://www.cse.wustl.edu/~jain/cse570-19/ Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse570-19/ ©2019 Raj Jain 6-1 Overview 1. Enterprise vs Carrier Ethernet 2. UNI vs Peer-to-Peer Signaling 3. Metro Ethernet 4. Ethernet Provider Bridge (PB) 5. Provider Backbone Network (PBB) 6. Connection Oriented Ethernet Note: Although these technologies were originally developed for carriers, they are now used inside multi-tenant data centers Washington(clouds) University in St. Louis http://www.cse.wustl.edu/~jain/cse570-19/ ©2019 Raj Jain 6-2 Enterprise vs. Carrier Ethernet Enterprise Carrier Distance: up to 2km Up to 100 km Scale: Few K MAC addresses Millions of MAC Addresses 4096 VLANs Millions of VLANs Q-in-Q Protection: Spanning tree Shortest Path Routing Path determined by spanning Traffic engineered path tree Simple service SLA Priority ⇒ Aggregate QoS Need per-flow QoS No performance/Error Need performance/BER monitoring (OAM) Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse570-19/ ©2019 Raj Jain 6-3 Carriers vs. Enterprise We need to exchange topology for Sorry, We can’t tell you optimal routing. anything about our internal network. Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse570-19/ ©2019 Raj Jain 6-4 Network Hierarchy Provider Provider Backbone Provider Customer Bridge Network Bridge Network Bridge Network Customer Network (PBN) (PBBN) (PBN) Network Backbone Provider Provider Core Core Core Bridge Bridge Bridge Customer Provider Provider Customer Edge Edge Backbone Edge Edge Bridge Bridge Provider Backbone Edge Provider Bridge Bridge Edge Edge Bridge Edge Bridge Bridge Bridge Washington University in St.
    [Show full text]
  • Network Virtualization Using Shortest Path Bridging (802.1Aq) and IP/SPB
    avaya.com Network Virtualization using Shortest Path Bridging and IP/SPB Abstract This White Paper discusses the benefits and applicability of the IEEE 802.1aq Shortest Path Bridging (SPB) protocol which is augmented with sophisticated Layer 3 routing capabilities. The use of SPB and the value to solve virtualization of today’s network connectivity in the enterprise campus as well as the data center are covered. This document is intended for any technically savvy network manager as well as network architect who are faced with: • Reducing time to service requirements • Less tolerance for network down time • Network Virtualization requirements for Layer 2 (VLAN-extensions) and Layer 3 (VRF-extensions) • Server Virtualization needs in data center deployments requiring a large set of Layer 2 connections (VLANs) • Traffic separation requirements in campus deployments for security purposes as well as robustness considerations (i.e. contractors for maintenance reasons needing access to their equipment or guest access needs) • Multi-tenant applications such as airports, governments or any other network with multiple discrete (legal) entities that require traffic separation WHITE PAPER 1 avaya.com Table of Contents 1. Introduction ........................................................................................................................ 3 2. Benefits of SPB ................................................................................................................... 4 2.1 Network Service Enablement ............................................................................................................
    [Show full text]
  • Optical Transport Networks & Technologies Standardization Work
    Optical Transport Networks & Technologies Standardization Work Plan Issue 24, February 2018 GENERAL ........................................................................................................................... 3 PART 1: STATUS REPORTS AS OF JANUARY 2018 ...................................................... 4 1 HIGHLIGHT OF ITU-T SG15 ........................................................................................ 4 2 REPORTS FROM OTHER ORGANIZATIONS ............................................................ 4 PART 2: STANDARD WORK PLAN ................................................................................... 8 1 INTRODUCTION TO PART 2 ...................................................................................... 8 2 SCOPE ......................................................................................................................... 8 3 ABBREVIATIONS ........................................................................................................ 8 4 DEFINITIONS AND DESCRIPTIONS .......................................................................... 9 4.1 Optical and other Transport Networks & Technologies (OTNT) ....................................................... 9 4.2 Optical Transport Network (OTN) (largely revised in 09/2016 reflecting B100G) ............................ 9 4.2.1 FlexE in OIF (updated in June-2017) .......................................................................................... 11 4.3 Support for mobile networks (reference to ITU-R M2375 added
    [Show full text]
  • Ethernet (IEEE 802.3)
    Computer Networking MAC Addresses, Ethernet & Wi-Fi Lecturers: Antonio Carzaniga Silvia Santini Assistants: Ali Fattaholmanan Theodore Jepsen USI Lugano, December 7, 2018 Changelog ▪ V1: December 7, 2018 ▪ V2: March 1, 2017 ▪ Changes to the «tentative schedule» of the lecture 2 Last time, on December 5, 2018… 3 What about today? ▪Link-layer addresses ▪Ethernet (IEEE 802.3) ▪Wi-Fi (IEEE 802.11) 4 Link-layer addresses 5 Image source: https://divansm.co/letter-to-santa-north-pole-address/letter-to-santa-north-pole-address-fresh-day-18-santa-s-letters/ Network adapters (aka: Network interfaces) ▪A network adapter is a piece of hardware that connects a computer to a network ▪Hosts often have multiple network adapters ▪ Type ipconfig /all on a command window to see your computer’s adapters 6 Image source: [Kurose 2013 Network adapters: Examples “A 1990s Ethernet network interface controller that connects to the motherboard via the now-obsolete ISA bus. This combination card features both a BNC connector (left) for use in (now obsolete) 10BASE2 networks and an 8P8C connector (right) for use in 10BASE-T networks.” https://en.wikipedia.org/wiki/Network_interface_controller TL-WN851ND - WLAN PCI card 802.11n/g/b 300Mbps - TP-Link https://tinyurl.com/yamo62z9 7 Network adapters: Addresses ▪Each adapter has an own link-layer address ▪ Usually burned into ROM ▪Hosts with multiple adapters have thus multiple link- layer addresses ▪A link-layer address is often referred to also as physical address, LAN address or, more commonly, MAC address 8 Format of a MAC address ▪There exist different MAC address formats, the one we consider here is the EUI-48, used in Ethernet and Wi-Fi ▪6 bytes, thus 248 possible addresses ▪ i.e., 281’474’976’710’656 ▪ i.e., 281* 1012 (trillions) Image source: By Inductiveload, modified/corrected by Kju - SVG drawing based on PNG uploaded by User:Vtraveller.
    [Show full text]