DOCSLIB.ORG

Chapter 2 Link Layer Verilog Hardware Implementation, and One Wireless Broadcast Link, I.E

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Chapter 2 Link Layer Verilog Hardware Implementation, and One Wireless Broadcast Link, I.E Modern Computer Networks: An open source approach Chapter 2 Modern Computer Networks: An open source approach Chapter 2 package, one wired broadcast link, i.e. Ethernet in Section 2.4 along with its Chapter 2 Link Layer Verilog hardware implementation, and one wireless broadcast link, i.e. wireless LAN (WLAN) in Section 2.5 plus a brief on Bluetooth and WiMAX. PPP is Problem Statement popularly used in the last-mile dial-up services or routers carrying various network protocols over point-to-point links. Ethernet has occupied more than 95 percent of To effectively and efficiently transmit data over physical links from one node wired LANs. It is also poised to be ubiquitous in MANs and WANs. In contrast to to one or more nodes, there is much more to do than simply modulating or desktop PCs, which usually use wired links, many devices such as laptop PCs encoding bit stream into signal. Transmission impairments, such as crosstalk and cellular phones are mobile and prefer wireless links such as WLAN, Bluetooth, between two adjacent pairs, can unexpectedly change transmission signal and and WiMAX. thus result in errors. The transmitter might transmit faster than the receiver can Table 2.1 Link protocols. handle. The transmitter has to somehow indicate the destination(s), if on a PAN/LAN MAN/WAN broadcast link, i.e. LAN, and usually needs to name itself to let the receiver know Token Bus (802.4) DQDB (802.6) Token Ring (802.5) HDLC where the source is. If multiple stations share a LAN, an arbitration mechanism is HIPPI X.25 required to determine who can transmit next. Beyond all of the above, we need to Obsolete or Fiber Channel Frame Relay Isochronous (802.9) SMDS interconnect LANs, i.e. bridging to forward packets between LANs, to extend the Fading Demand Priority (802.12) ISDN coverage beyond a single LAN. These problems need to be addressed by a set of FDDI B-ISDN ATM functions above the physical link. The link layer in the 4-layer Internet architecture, HIPERLAN or the physical layer and the data link layer together in the 7-layer OSI Ethernet (802.3) Ethernet (802.3) WLAN (802.11) Resilient Packet Ring (802.17) architecture, manages the physical link to solve these problems. Upper layers are Mainstream or Bluetooth (802.15) Point-to-Point Protocol (PPP) therefore exempt from the duty of controlling parameters in a physical network. Fiber Channel DOCSIS Still active HomeRF WiMAX (802.16) These services greatly alleviate upper-layer protocol design and make it virtually HomePlug ATM independent of physical transmission characteristics. In this chapter, we present (1) functions or services provided in the link layer, As an independent issue, bridging for LAN interconnection is covered in (2) real-world popular link protocols, and (3) some of their open source software Section 2.6, along with its open source implementations of two key components, or hardware implementations. self learning and spanning tree. At the end, Section 2.7 illustrates the general Section 2.1 addresses the general issues in designing link layer functions concepts of Linux device drivers. We go deep into the Ethernet driver ranging from framing, addressing, error control, flow control, access control, to implementation. interfaces with other layers. Their possible solution alternatives are reviewed. Function calls in Linux are used to illustrate the interfaces and sk_buff packet 2.1 General Issues flows with the network adaptor and the upper IP layer, as a zoom-in of a packet life in Section 1.5. To prepare readers with physical background, Section 2.2 first Sandwiched between the physical link and the network layer, the link layer briefs the wired and wireless medium, and then their encoding and modulation provides control on physical communications and services to upper network layer. schemes. This layer includes the following major functions. Given the vast number of real-world links, it is nearly impossible to describe all of them. We summarize well-known data-link protocols in Table 2.1. Some are Framing Control information, in the header, comes along with the data, in the obsolete or fading nowadays, some are in the mainstream, and still some others payload, in the bit stream to specify the destination station, indicate the are under development. Among the mainstream, we detail one point-to-point link, upper-layer protocol, check possible errors and so on. Data are sent and i.e. Point-to-Point Protocol (PPP) in Section 2.3 along with an open source processed in units of frames which are “packets or packet data units (PDUs) at the 1 2 Modern Computer Networks: An open source approach Chapter 2 Modern Computer Networks: An open source approach Chapter 2 link layer” and usually contains two main parts: control information and the data. Ethernet (i.e., 100 Mb/s) because it can detect the physical link status. The latter The link protocols refer to control information during frame processing. The data is unable to to do so because it cannot tell whether the physical link is broken or part is from the upper layer and encapsulated with the control information into the no frames are being transmitted (no signal is on the link in both cases). It was frame. The link layer service should delimit the bit stream into frames and turn used in 10 Mb/s Ethernet, and no longer used in later Ethernet technology. frames into bit stream. The two terms, packets and frames, are usually used A bit-oriented frame can specify a special bit pattern, say 01111110 in HDLC, interchangeably. We refer to the packet data unit in the link layer as frames to be while a byte-oriented frame can specify special characters, say SOH (start of specific. Similarly for payload/data, header/control information, and node/station, header) and STX (start of text) to mark the beginning of frame header and data. data, control information, and station are called more often in the link layer. An ambiguity may exist when normal data characters or bits are the same as the Addressing We need an address when writing a letter to our friends, and also special characters or pattern. A technique called byte- or bit-stuffing is used to need a phone number when dialing up to them. Addressing is needed for the solve the ambiguity, as illustrated in Figure 2.1. A special escape character, same reason in the link layer. The identity of a station is indicated by an address, namely DLE (data link escape), precedes a special character to indicate the next often presented in a numeric form of a certain length. character is normal data in a byte-oriented frame. Because DLE itself is also a Error control Frames transmitted over physical media are subject to errors, special character, two consecutive DLEs represent a normal DLE character. For which must be detected by the receiver. The receiver may simply drop the frame, 01111110 used in HDLC, when five consecutive 1’s are in the normal data bits, a 0 or inform the transmitter that errors occur for the transmitter to retransmit the data. is stuffed, so that the pattern 01111110 never appears in normal data. Both the Flow control The transmitter may send at a rate faster than the receiver can transmitter and the receiver follow the same rule to solve the ambiguity. afford. In this case, the receiver has to discard the frames, making the transmitter A different approach is in the Ethernet. For example, 100BASE-X uses retransmits the dropped frames, but this is inefficient. Flow control provides a special encoding to mark the boundary because after 4B/5B encoding, 32 (= 25) method to let the receiver slow down the transmitter. possible codes can be transmitted over physical media while only 16 out of them Medium Access control There must be an arbitration mechanism when multiple come from actual data. Other codes can serve as control codes. These control nodes want to transmit data over shared media. A good arbitration mechanism codes are uniquely recognizable by the receiver and thus used to delimit a frame must offer fair access to a shared medium and keep the utilization of the shared out of a sequence of bit stream. Another Ethernet system, 10BASE-T, recognizes medium high when many nodes have backlog, i.e. queued data to transmit. the frame boundary simply according to the presence or absence of a signal. 2.1.1 Framing Frame Format A frame is divided into header fields that include various kinds of control Frame Delimiting information and the data from the network layer, which again contains control Because data are transmitted in raw bit stream in the physical layer, the link information of higher layers and the actual data. The control information of higher layer must tell the beginning and the end of a frame. It must also turn frames into layers is treated as normal data in the link layer. Typical header fields of control raw bit stream for physical transmission. This function is called framing. Many information other than the data field are listed below. methods can delimit the frames. Depending on the basic unit of a frame, which Address: It usually indicates the source or the destination address. The receiver can be byte (or octet) or bit, called a byte-oriented or bit-oriented frame, special knows the frame is for it if the destination address matches its own. It also can sentinel characters or bit patterns can mark the frame boundary. We introduce the respond to the source by filling in the destination address of the outgoing frame framing examples of bit-oriented HDLC frames.
Load more

Recommended publications
  • Ciena 5305 Service Aggregation Switch Datasheet
    5305 SERVICE AGGREGATION SWITCH Features and Benefits The 5305 Ethernet/MPLS service aggregation > Features advanced Ethernet and MPLS to support demanding business, mobile switch is purpose-built for Carrier Ethernet backhaul, transport, and residential applications including L2VPN service to deliver cost-effective capacity, scalability, delivery and aggregation, 3G/4G wireless backhaul, FTTx and IP DSLAM and resiliency. With this switch, service Aggregation and L2 backhaul of L3VPNs > Delivers optimal density and service providers can keep pace with the constantly flexibility with a compact modular chassis, supporting incremental increasing demand for bandwidth and next- expansion of service and bandwidth capacity with linear CAPEX outlay generation services that support business, > Supports tens of thousands of services mobile backhaul, transport, and residential on a single system with robust scalability of up to 30,000+ VLANs and applications in metro networks. two million MAC addresses per chassis > Delivers high reliability, five-9s The 5305 is a modular, chassis-based system optimized for metro-edge deployments availability, and 50 ms protection in a wide variety of network topologies, including fiber and microwave rings, point-to- switching resiliency using state-of- the-art hardware and software design point fiber, microwave mesh, and fiber or copper to the subscriber. The switch coupled with advanced control plane supports high-density Gigabit Ethernet (GbE) connectivity to the subscriber edge and and Ethernet OAM capabilities
    [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]
  • Automotive Ethernet Kirsten Matheus , Thomas Königseder Frontmatter More Information
    Cambridge University Press 978-1-108-84195-5 — Automotive Ethernet Kirsten Matheus , Thomas Königseder Frontmatter More Information Automotive Ethernet Third Edition Learn about the latest developments in Automotive Ethernet technology and imple- mentation with this fully revised third edition. Including 20% new material and greater technical depth, coverage is expanded to include Detailed explanations of the new PHY technologies 10BASE-T1S (including multi- drop) and 2.5, 5, and 10GBASE-T1 Discussion of EMC interference models Descriptions of the new TSN standards for automotive use More on security concepts An overview of power saving possibilities with Automotive Ethernet Explanation of functional safety in the context of Automotive Ethernet An overview of test strategies The main lessons learned Industry pioneers share the technical and non-technical decisions that have led to the success of Automotive Ethernet, covering everything from electromagnetic require- ments and physical layer technologies, QoS, and the use of VLANs, IP, and service discovery, to network architecture and testing. The guide for engineers, technical managers, and researchers designing components for in-car electronics, and those interested in the strategy of introducing a new technology. Kirsten Matheus is a communications engineer who is responsible for the in-vehicle networking strategy at BMW and who has established Ethernet-based communication as a standard technology within the automotive industry. She has previously worked for Volkswagen, NXP, and Ericsson. In 2019 she was awarded the IEEE-SA Standards Medallion “For vision, leadership, and contributions to developing auto- motive Ethernet networking.” Thomas Königseder is CTO at Technica Engineering, supporting the smooth introduc- tion of Ethernet-based systems for automotive customers.
    [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]
  • 802.3 Opening Plenary March 2003
    Unconfirmed Minutes IEEE 802.3 CSMA/CD PLENARY DFW Airport, TX March 10 –14, 2003 MONDAY, MARCH 10, 2003 ADMINISTRATIVE MATTERS (802.3 Secretary’s Note: The minutes for the March 2003 802.3 Plenary are almost 300 pages long and include copies of all presentations and liaison materials. This document, therefore, will be terse and will not repeat material covered in the presentations. Please use the bookmarks to navigate to a particular attachment. Mr. Robert Grow, Chair of 802.3 CSMA/CD Working Group called the meeting to order at 1:08PM. Mr. Grow introduced Mr. David Law, Vice Chair of 802.3, and Mr. Steve Carlson, Secretary of 802.3, and Task Force Chair of 802.3af. Mr. Howard Frazier, Chair of the 802.3ah Task Force was also introduced, along with Brad Booth, Chair of the 10GBASE-T Study Group, and Dan Dove, Chair of the 10GBASE-CX4 Study Group. Mr. Grow then had the attendees stand and introduce themselves to the group. Mr. Grow asked if there were any additions or corrections to the agenda. None were indicated. MOTION Approve the agenda <802.3 Opening Agenda>. Moved: Brad Booth Seconded: Tom Dineen Agenda was passed by acclimation (voice vote). Mr. Grow presented his Opening Report <802.3 Opening Report>. MOTION Approve the 802.3 minutes from Kauai. M: Tom Dineen S: Lampson PASSED by acclamation Attendance Books Mr. Carlson explained the operation of the Attendance books for new voters and established voters. Voters we cautioned that they would be subjected to public humiliation if they failed to follow the instructions.
    [Show full text]
  • Optimizing 10-Gigabit Ethernet for Networks of Workstations, Clusters, and Grids: a Case Study ∗
    SLAC-PUB-10198 Optimizing 10-Gigabit Ethernet for Networks of Workstations, Clusters, and Grids: A Case Study ∗ Wu-chun Feng,† Justin (Gus) Hurwitz,† Harvey Newman,†† Sylvain Ravot,†† R. Les Cottrell,‡‡ Olivier Martin,‡ Fabrizio Coccetti,‡‡ Cheng Jin,†† Xiaoliang (David) Wei,†† and Steven Low†† †Los Alamos National Laboratory (LANL) ††California Institute of Technology (CalTech) Computer & Computational Sciences Division Pasadena, CA 91125 Research and Development in Advanced Network Technology Charles C. Lauritsen Laboratory of High Energy Physics Los Alamos, NM 87545 {newman,ravot}@caltech.edu {feng,ghurwitz}@lanl.gov Computer Science & Electrical Engineering Dept. {chengjin,weixl,slow}@caltech.edu ‡European Organization for Nuclear Research (CERN) ‡‡Stanford Linear Accelerator Center (SLAC) Information Technology Division SLAC Computing Services Geneva, Switzerland Menlo Park, CA 94025 {Olivier.Martin}@cern.ch {cottrell,cfabrizo}@SLAC.stanford.edu Abstract 1. Introduction This paper presents a case study of the 10-Gigabit Ether- Thirty years ago in a May 1973 memo, Robert Metcalfe net (10GbE) adapter from IntelR . Specifically, with appropri- described the technology that would evolve into today’s ubiq- ate optimizations to the configurations of the 10GbE adapter uitous Ethernet protocol. By 1974, Metcalfe and his col- and TCP,we demonstrate that the 10GbE adapter can perform league, David Boggs, built their first Ethernet; and by 1975, well in local-area, storage-area, system-area, and wide-area they demonstrated what was at the time
    [Show full text]
  • Interactions Between TCP and Ethernet Flow Control Over Netgear
    Interactions between TCP and Ethernet flow control over Netgear XAVB2001 HomePlug AV links Radika Veera Valli, Grenville Armitage, Jason But, Thuy Nguyen Centre for Advanced Internet Architectures, Technical Report 130121A Swinburne University of Technology Melbourne, Australia [email protected], [email protected], [email protected], [email protected] Abstract—HomePlug AV links are usually slower than buffers along network paths. A side-effect of such loss- the surrounding wired LAN links, creating a bottleneck based CC behaviour is that all traffic sharing the bottle- where traffic may be buffered and delayed. To investigate neck will experience additional latency due to increased the interactions between TCP congestion control and average queueing delays [5]. This is particularly prob- Ethernet flow control we trialled four TCP variants over a lematic for real-time application flows (such as VoIP and HomePlug AV link using two Netgear XAVB2001 devices. We observed that the XAVB2001’s use of Ethernet flow online games) given the growth of arguably-gratuitous control effectively concatenates the buffers in both the buffering (“buffer bloat”) in network devices, interface XAVB2001 and the directly attached sending host. This led cards and network software stacks [6]. to multi-second RTTs when using NewReno and CUBIC In this report we borrow from, and extend, previous (loss-based) TCPs, which is significantly troublesome for work by one of the current authors [7]. Our new work multimedia traffic on home LANs. In contrast, Vegas explores in greater detail the latency and flow control and CDG (delay-based) TCPs kept buffer utilisation low, issues that emerge when end-to-end TCP is allowed to and induced five to ten milliseconds RTT.
    [Show full text]
  • Ethernet: an Engineering Paradigm
    Ethernet: An Engineering Paradigm Mark Huang Eden Miller Peter Sun Charles Oji 6.933J/STS.420J Structure, Practice, and Innovation in EE/CS Fall 1998 1.0 Acknowledgements 1 2.0 A Model for Engineering 1 2.1 The Engineering Paradigm 3 2.1.1 Concept 5 2.1.2 Standard 6 2.1.3 Implementation 6 3.0 Phase I: Conceptualization and Early Implementation 7 3.1 Historical Framework: Definition of the Old Paradigm 7 3.1.1 Time-sharing 8 3.1.2 WANs: ARPAnet and ALOHAnet 8 3.2 Anomalies: Definition of the Crisis 10 3.2.1 From Mainframes to Minicomputers: A Parallel Paradigm Shift 10 3.2.2 From WAN to LAN 11 3.2.3 Xerox: From Xerography to Office Automation 11 3.2.4 Metcalfe and Boggs: Professional Crisis 12 3.3 Ethernet: The New Paradigm 13 3.3.1 Invention Background 14 3.3.2 Basic Technical Description 15 3.3.3 How Ethernet Addresses the Crisis 15 4.0 Phase II: Standardization 17 4.1 Crisis II: Building Vendor Support (1978-1983) 17 4.1.1 Forming the DIX Consortium 18 4.1.2 Within DEC 19 4.1.3 Within Intel 22 4.1.4 The Marketplace 23 4.2 Crisis III: Establishing Widespread Compatibility (1979-1984) 25 4.3 The Committee 26 5.0 Implementation and the Crisis of Domination 28 5.1 The Game of Growth 28 5.2 The Grindley Effect in Action 28 5.3 The Rise of 3Com, a Networking Giant 29 6.0 Conclusion 30 A.0 References A-1 i of ii ii of ii December 11, 1998 Ethernet: An Engineering Paradigm Mark Huang Eden Miller Charles Oji Peter Sun 6.933J/STS.420J Structure, Practice, and Innovation in EE/CS Fall 1998 1.0 Acknowledgements The authors would like to thank the following individuals for contributing to this project.
    [Show full text]
  • Ethernet Basics Ethernet Basics
    2016-09-24 Ethernet Basics based on Chapter 4 of CompTIA Network+ Exam Guide, 4th ed., Mike Meyers Ethernet Basics • History • Ethernet Frames • CSMA/CD • Obsolete versions • 10Mbps versions • Segments • Spanning Tree Protocol 1 2016-09-24 Ethernet – Early History • 1970: ALOHAnet, first wireless packet-switched network - Norman Abramson, Univ. of Hawaii - Basis for Ethernet’s CSMA/CD protocol - 1972: first external network connected to ARPANET • 1973: Ethernet prototype developed at Xerox PARC - (Palo Alto Research Center) - 2.94 Mbps initially • 1976: "Ethernet: Distributed Packet Switching for Local Computer Networks" published in Communications of the ACM. - Bob Metcalfe and David Boggs - sometimes considered “the beginning of Ethernet” Ethernet goes Mainstream • 1979: DEC, Intel, Xerox collaborate on a commercial Ethernet specification - Ethernet II, a.k.a. “DIX” Ethernet - (Digital Equipment Corporation) • 1983: IEEE 802.3 specification formally approved - Differs from Ethernet II in the interpretation of the third header field • 1987: alternatives to coaxial cables - IEEE 802.3d: FOIRL, Fiber Optic Inter-Repeater Link - IEEE 802.3e: 1 Mbps over Twisted Pair wires (whoopee!) • 1990: Twisted-Pair wiring takes over - IEEE 802.3i: 10 Mbps over Twisted-Pair – 10Base-TX, 10Base-T4 2 2016-09-24 the Future is Now (next chapter) (and Now is so Yesteryear…) 1995 – Now: speed and cabling improvements • 1995: 100Mbps varieties • 1999: 1Gbps on twisted-pair • 2003-2006: 10Gbps on optical fiber and UTP • 2010: 40Gbps, 100Gbps (802.3ba) - optical fiber or twinaxial cable - point-to-point physical topology; for backbones • 2016, September: 2.5GBase-T, 5GBase-T ? - who knows? What Is Ethernet? • Protocols, standards for Local Area Networks » Ethernet II, IEEE 802.3 • Specifies Physical-layer components - Cabling, signaling properties, etc.
    [Show full text]
  • History Panel 8.5X11 Lo-Res
    400GbE 400 300 (Gb/s) 200 100GbE 40GbE 100 10GbE Ethernet Speeds 0 The Early Years of Ethernet Standards Early Years of Ethernet Optics 1973 - Bob Metcalfe writes 1985 – First Ethernet 4 port FDDI Switch Blade 2 port GbE Switch Blade first memo about Ethernet standard released as at XEROX PARC IEEE 802.3 CSMA/ CD 1975 – Patent filed for Ethernet (10Mb/s) Hand drawn diagram of 1995 – Fast Ethernet by Bob Ethernet by Bob Metcalfe, Ethernet Pre-1990 – Metcalfe – circa 1976 David Boggs, Chuck (100Mbps) FDDI Module Fast Ethernet (100Mb/s) Thacker and Butler standard released Lampson as IEEE 802.3u Gigabit Ethernet (1Gb/s) Early NIC with COAX 1980 – “DIX” and RJ-45 support 1998 – Gigabit “Digital /Intel/Xerox” Ethernet (GbE) standard submitted standard released 1x9 non-pluggable 1998 – Gigabit Interface with 48-bit Ethernet as IEEE 802.3z Module Converter (GBIC) address standard released Sugar Cube Optics 1970 1980 1990 2000 1990 1995 2000 10GbE Returns to SFP+ 40GbE in QSFP+ and Eventually SFP+ SFP+ released in 2009 with serial 10Gbps Breakout cable to electrical interface and SFF – The QSFP+ is the dominant support 4X10GbE dominates 10GbE non-pluggable 40GbE module type cousin of SFP+ XFP released in 2006 with serial CEI-56G-VSR being 10GbE and 2001 – The SFP standard 10Gbps electrical standardized in OIF and finalizes and quickly interface could lead to 40GbE Serial dominates GbE optic interface to SFP+ 40GbE XENPAK, X2 and All 10GbE modules XPAK are 2nd gen interoperate at the 10GbE modules optical interface Will IEEE CFP used for 40GBASE-FR
    [Show full text]
  • Understanding Ethernet
    Chapter 1 Understanding Ethernet In This Chapter ▶ Exploring carrier sensing and collision detection methods ▶ Understanding directional traffic and simultaneous transmissions ▶ Examining Ethernet speed limits and wire-rated standards ▶ Exploring Gigabit Ethernet ▶ Distinguishing between local and backbone Ethernet ▶ Recognizing Ethernet interfaces ▶ Understanding Ethernet’s simplicity n today’s connected business world, ubiquitous access to Idigitized information and data is critical. Networking has not only reshaped the information landscape, but it has also vastly increased speeds at which information moves and is consumed. In fact, networking is the key to accessing the com- plex services and applications within which information plays a starring role. Although access to the Internet is essential, all networking begins at the local level. For modern networks, Ethernet is the standard infrastructure upon which local net- works rest. Ethernet comprises a family of frame-based protocols and tech- nologies designed to connect local area networks (LANs) — computersCOPYRIGHTED and devices situated in MATERIAL close proximity and able to communicate with one another. Ethernet draws its name from the fanciful Latin terminology luminiferous aether, which trans- lates to a light-bearing medium once thought to fill space and propagate magnetic waves. As such, Ethernet is a metaphorical reference for the physical transmission medium in the work- place (and at home) that propagates digitized information in electronic form. The term “Ethernet” was originally coined by 4 Carrier Ethernet For Dummies Bob Metcalfe while jointly developing basic Ethernet network computing with David Boggs at Xerox Palo Alto Research Center (PARC). Sensing a Carrier and Handling Collisions Two people on opposite ends of a phone conversation can sense carrier presence (either a dial-tone or a connected call) and handle collisions (overlapping conversations).
    [Show full text]
  • Storage and Network Convergence Using Fcoe and Iscsi
    Front cover Storage and Network Convergence Using FCoE and iSCSI Learn how to improve IT service performance and availability Simplify your storage and network infrastructure See how to reduce data center network costs Sangam Racherla Silvio Erdenberger Harish Rajagopal Kai Ruth ibm.com/redbooks International Technical Support Organization Storage and Network Convergence Using FCoE and iSCSI January 2014 SG24-7986-01 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. Second Edition (January 2014) This edition applies to the latest supported Converged Network Adapters and Switches in the IBM System Networking Portfolio of products. © Copyright International Business Machines Corporation 2012, 2014. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xi Trademarks . xii Preface . xiii Authors. xiii Now you can become a published author, too! . .xv Comments welcome. .xv Stay connected to IBM Redbooks . xvi Part 1. Overview of storage and network convergence . 1 Chapter 1. Introduction to convergence . 3 1.1 What convergence is. 4 1.1.1 Calling it what it is . 4 1.2 Vision of convergence in data centers . 4 1.3 The interest in convergence now . 5 1.4 Fibre Channel SANs today . 5 1.5 Ethernet-based storage today. 6 1.6 Benefits of convergence in storage and network . 7 1.7 Challenge of convergence . 8 1.8 Conclusion . 10 Chapter 2. Fibre Channel over Ethernet . 11 2.1 Background: Data Center Bridging . 12 2.1.1 Priority-based Flow Control: IEEE 802.1Qbb .
    [Show full text]