* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Chapter5b
Deep packet inspection wikipedia , lookup
Airborne Networking wikipedia , lookup
Asynchronous Transfer Mode wikipedia , lookup
Computer network wikipedia , lookup
Point-to-Point Protocol over Ethernet wikipedia , lookup
Wake-on-LAN wikipedia , lookup
Network tap wikipedia , lookup
IEEE 802.1aq wikipedia , lookup
Serial digital interface wikipedia , lookup
Nonblocking minimal spanning switch wikipedia , lookup
Cracking of wireless networks wikipedia , lookup
Dynamic Host Configuration Protocol wikipedia , lookup
Recursive InterNetwork Architecture (RINA) wikipedia , lookup
Internet protocol suite wikipedia , lookup
Multiprotocol Label Switching wikipedia , lookup
Zero-configuration networking wikipedia , lookup
Link layer, LANs: outline 5.1 introduction, services 5.5 link virtualization: MPLS 5.2 error detection, correction 5.6 data center networking 5.3 multiple access protocols 5.7 a day in the life of a web request 5.4 LANs addressing, ARP Ethernet switches VLANS Link Layer 5-1 Ethernet “dominant” wired LAN technology: cheap for add-in NIC (<$20), but commonly integrated on motherboard (chipset typically <$5) first widely used LAN technology simpler, cheaper than token LANs and ATM kept up with speed race: 10 Mbps –> 10 Gbps Robert Metcalfe’s Ethernet sketch Link Layer 5-2 Ethernet: physical topology bus: popular through mid 90s all nodes in same collision domain (can collide with each other) star: prevails today until late 90s, with a hub (layer-1repeater) at center each “spoke” runs a (separate) Ethernet protocol (nodes do not collide with each other) star Hub bus: coaxial cable Link Layer 5-3 Ethernet’s CSMA/CD Efficiency 1.0 1024 byte frames 0.9 Channel Efficiency 0.8 512 byte frames 0,7 256 byte frames 0.6 0.5 128 byte frames 0.4 0.3 64 byte frames 0.2 0.1 0 1 2 4 8 16 32 64 128 256 512 Number of Stations Trying to Send 5: DataLink Layer 5b-4 Switched Ethernet: physical topology prevalent since early-2000 star topology with active switch in center layer-2 device each “spoke” runs a (separate) Ethernet protocol (nodes do not collide with each other) acts as a store-and-forward packet switch, but at the link layer, not network layer star switch Link Layer 5-6 Ethernet frame structure sending adapter encapsulates IP datagram (or other network layer protocol packet) in Ethernet frame type dest. source preamble address address data (payload) CRC preamble: 7 bytes with pattern 10101010 followed by one byte with pattern 10101011 used to synchronize receiver, sender clock rates necessary due to slight variations in internal adapter clocks (“drift”) Link Layer 5-7 Ethernet frame structure (more) addresses: 6 byte source, destination MAC addresses if adapter receives frame with matching destination address, or with broadcast address (e.g. ARP packet), it passes data in frame to network layer protocol otherwise, adapter discards frame type: indicates higher layer protocol (mostly IP but others possible, e.g., Novell IPX, AppleTalk) data: 46-1500 bytes form layer above (typ. IP datagram) CRC: cyclic redundancy check at receiver (IEEE CRC-32 error detected: frame is dropped type dest. source preamble address address data (payload) CRC Link Layer 5-8 Ethernet: unreliable, connectionless connectionless: no handshaking between sending and receiving NICs unreliable service: i.e., no reliable data transfer: receiving NIC doesn’t send acks or nacks to sending NIC data in dropped frames recovered only if initial sender uses higher layer reliable data transfer (e.g., TCP), otherwise dropped data lost Ethernet’s MAC protocol: unslotted CSMA/CD with binary backoff Link Layer 5-9 802.3 Ethernet standards: link & physical layers many different Ethernet standards common MAC protocol and frame format different speeds: 2 Mbps (obsolete), 10 Mbps, 100 Mbps (common), 1Gbps, 10Gbps different physical layer media: fiber, cable application transport network link physical MAC protocol and frame format 100BASE-TX 100BASE-T2 100BASE-FX 100BASE-T4 100BASE-SX 100BASE-BX copper (twister pair) physical layer fiber physical layer Link Layer 5-10 Link layer, LANs: outline 5.1 introduction, services 5.5 link virtualization: MPLS 5.2 error detection, correction 5.6 data center networking 5.3 multiple access protocols 5.7 a day in the life of a web request 5.4 LANs addressing, ARP Ethernet switches VLANS Link Layer 5-11 Ethernet switch link-layer device: takes an active role store and forward Ethernet frames examine incoming frame’s MAC address, selectively forward frame to one-or-more outgoing links when frame is to be forwarded on segment, uses CSMA/CD to access segment transparent hosts are unaware of presence of switches (looks like a single physical link) plug-and-play, self-learning switches do not need to be configured Link Layer 5-12 Switch: multiple simultaneous transmissions hosts have dedicated, direct connection to switch switches buffer packets Ethernet protocol used on each incoming link, but no collisions; full duplex each link is its own collision domain switching: A-to-A’ and B-to-B’ can occur simultaneously, without collisions A B C’ 6 1 2 4 5 3 C B’ A’ switch with six interfaces (1,2,3,4,5,6) Link Layer 5-13 Switch forwarding table Q: how does switch know A’ reachable via interface 4, B’ reachable via interface 5? A: each switch has a switch table, each entry: (MAC address of host, interface to reach host, time stamp) looks like a routing or ARP table! A B C’ 6 1 2 4 5 3 C B’ A’ Q: how are entries created, maintained in switch table? switch with six interfaces (1,2,3,4,5,6) something like a routing protocol? Link Layer 5-14 Switch: self-learning switch learns which hosts can be reached through which interfaces when frame received, switch “learns” location of sender: incoming LAN segment records sender/location pair in switch table Source: A Dest: A’ A A A’ B C’ 6 1 2 4 5 3 C B’ A’ MAC addr. A interface 1 time 6:03 Switch table (initially empty) Link Layer 5-15 Switch: frame filtering/forwarding when frame received at switch: 1. record incoming link, MAC address of sending host 2. index switch table using MAC destination address 3. if entry found for destination then { if destination on segment from which frame arrived then drop frame else forward frame on interface indicated by entry } else flood /* forward on all interfaces except arriving interface */ Link Layer 5-16 Self-learning, forwarding: example frame destination, A’, location unknown: flood destination A location known: selectively send on just one link use incoming frames to make new entries in table A A A’ B C’ 1 6 2 A A’ 4 5 3 C B’ A’ A A’ MAC addr interface A A’ Source: A Dest: A’ 1 4 time 6:03 6:04 switch table (initially empty) Link Layer 5-17 Interconnecting switches switches can be connected together S4 S1 S3 S2 A B C F D E I G H Q: sending from A to G - how does S1 know to forward frame destined to F via S4 and S3? A: self learning! (works exactly the same as in single-switch case!) Link Layer 5-18 Institutional network mail server to external network router web server IP subnet Link Layer 5-20 Switches vs. routers both are store-and-forward: routers: network-layer devices (examine networklayer headers) switches: link-layer devices (examine link-layer headers) both have forwarding tables: routers: compute tables using routing algorithms, IP addresses switches: learn forwarding table using flooding, learning, MAC addresses datagram frame application transport network link physical frame link physical switch network datagram link frame physical application transport network link physical Link Layer 5-21 VLANs: motivation consider: Computer Science Electrical Engineering Computer Engineering CS user moves office to EE, but wants connect to CS switch? single broadcast domain: all layer-2 broadcast traffic (ARP, DHCP, MAC address not in switch table) must cross entire LAN security/privacy, efficiency issues Link Layer 5-22 VLANs port-based VLAN: switch ports grouped (by switch management software) so that single physical switch …… Virtual Local Area Network switch(es) supporting VLAN capabilities can be configured to define multiple virtual LANS over single physical LAN infrastructure. 1 7 9 15 2 8 10 16 … … Electrical Engineering (VLAN ports 1-8) Computer Science (VLAN ports 9-15) … operates as multiple virtual switches 1 7 9 15 2 8 10 16 … Electrical Engineering (VLAN ports 1-8) … Computer Science (VLAN ports 9-16) Link Layer 5-23 Port-based VLAN router traffic isolation: frames to/from ports 1-8 can only reach ports 1-8 can also define VLAN based on MAC addresses of endpoints, rather than switch port dynamic membership: ports can be dynamically assigned among VLANs 1 7 9 15 2 8 10 16 … Electrical Engineering (VLAN ports 1-8) … Computer Science (VLAN ports 9-15) forwarding between VLANS: done via routing (just as with separate switches) in practice vendors sell combined switches plus routers Link Layer 5-24 VLANS spanning multiple switches 1 7 9 15 1 3 5 7 2 8 10 16 2 4 6 8 … Electrical Engineering (VLAN ports 1-8) … Computer Science (VLAN ports 9-15) Ports 2,3,5 belong to EE VLAN Ports 4,6,7,8 belong to CS VLAN trunk port: carries frames between VLANS defined over multiple physical switches frames forwarded within VLAN between switches can’t be vanilla 802.1 frames (must carry VLAN ID info) 802.1q protocol adds/removed additional header fields for frames forwarded between trunk ports Link Layer 5-25 802.1Q VLAN frame format type preamble dest. address source address data (payload) CRC 802.1 frame type preamble dest. address source address data (payload) 2-byte Tag Protocol Identifier (value: 81-00) CRC 802.1Q frame Recomputed CRC Tag Control Information (12 bit VLAN ID field, 3 bit priority field like IP TOS) Link Layer 5-26 Link layer, LANs: outline 5.1 introduction, services 5.5 link virtualization: MPLS 5.2 error detection, correction 5.6 data center networking 5.3 multiple access protocols 5.7 a day in the life of a web request 5.4 LANs addressing, ARP Ethernet switches VLANS Link Layer 5-27 Multiprotocol label switching (MPLS) “MPLS: The intelligence of routing with the performance of switching.” MPLS Goal: provide ATMlike traffic management and QoS within IP-based networks Reality: provides an approach that reduces perpacket processing required at routers, thereby enhancing IP routing performance Plus: significant new capabilities are introduced in MPLS: 1. support for connectionoriented QoS 2. Traffic engineering 3. VPN support RFC 3031 and RFC 3032 issued in January 2001 (updated) Link Layer 5-28 Multiprotocol label switching (MPLS) high-speed IP forwarding using fixed length label (instead of IP address) fast lookup using fixed length identifier (rather than shortest prefix matching) borrowing ideas from Virtual Circuit (VC) approach but IP datagram still keeps IP address! PPP or Ethernet header MPLS header label 20 IP header remainder of link-layer frame Exp S TTL 3 1 5 Link Layer 5-29 MPLS capable routers a.k.a. label-switched router (LSR) forward packets to outgoing interface queue based only on label value (don’t inspect IP address) MPLS forwarding table distinct from IP forwarding tables flexibility: MPLS forwarding decisions can differ from those of IP use destination and source addresses to route flows to same destination differently (traffic engineering) re-route flows quickly if link fails: pre-computed backup paths (useful for VoIP) engineered QoS routes Link Layer 5-30 MPLS forwarding tables in label out label dest 10 12 8 out interface A D A 0 0 1 in label out label dest out interface 10 6 A 1 12 9 D 0 R6 0 0 D 1 1 R3 R4 R5 0 0 R2 in label 8 out label dest 6 A out interface in label 6 outR1 label dest - A A out interface 0 0 Link Layer 5-31 MPLS versus IP paths R6 D R4 R3 R5 A R2 IP routing: path to destination determined by destination address alone IP router Link Layer 5-32 MPLS versus IP paths entry router (R4) can use different MPLS routes to A based, e.g., on source address R6 D R4 R3 R5 A R2 IP routing: path to destination determined by destination address alone IP-only router MPLS routing: path to destination can be based on source and dest. address MPLS and IP router fast reroute: precompute backup routes in case of link failure Link Layer 5-33 MPLS signaling Modified OSPF, IS-IS link-state flooding protocols carry info used by MPLS routing, e.g., link bandwidth, amount of “reserved” link bandwidth Entry MPLS router uses RSVP-TE (RFC 3346, et al) signaling protocol to set up MPLS forwarding at downstream routers RSVP-TE R6 D R4 R5 modified link state flooding A Link Layer 5-34 MPLS in practice High-speed IP backbones IP over MPLS-capable ATM networks IP over optical (point-to-point) networks IP over frame relay networks Most prevalent usage is for transporting IP data over these networks with low overhead/latency, and often to implement a VPN for IP traffic Link Layer 5-35 Link layer, LANs: outline 5.1 introduction, services 5.5 link virtualization: MPLS 5.2 error detection, correction 5.6 data center networking 5.3 multiple access protocols 5.7 a day in the life of a web request 5.4 LANs addressing, ARP Ethernet switches VLANS Link Layer 5-36 Data center networks 10’s to 100’s of thousands of hosts, often closely coupled, in close proximity: e-business (e.g. Amazon) content-servers (e.g., YouTube, Akamai, Apple, Microsoft) search engines, data mining (e.g., Google) social networks (e.g. Facebook) challenges: multiple applications, each serving massive numbers of clients managing/balancing load, avoiding processing, networking, data bottlenecks Inside a 40-ft Microsoft container, Chicago data center Link Layer 5-37 Data center networks load balancer: application-layer routing receives external client requests directs workload within data center returns results to external client (hiding data center internals from client, like NAT) Internet Border router Load balancer Access router Tier-1 switches B A Load balancer Tier-2 switches C TOR switches Server racks 1 2 3 4 5 6 7 8 Link Layer 5-38 Data center networks rich interconnection among switches, racks: increased throughput between racks (multiple routing paths possible) increased reliability via redundancy Tier-1 switches Tier-2 switches TOR switches Server racks 1 2 3 4 5 6 7 8 Link layer, LANs: outline 5.1 introduction, services 5.5 link virtualization: MPLS 5.2 error detection, correction 5.6 data center networking 5.3 multiple access protocols 5.7 a day in the life of a web request 5.4 LANs addressing, ARP Ethernet switches VLANS Link Layer 5-40 Synthesis: a day in the life of a web request journey down protocol stack complete! application, transport, network, link putting-it-all-together: synthesis! goal: identify, review, understand protocols (at all layers) involved in seemingly simple scenario: requesting www page scenario: student attaches laptop to campus network, requests/receives www.google.com Link Layer 5-41 A day in the life: scenario DNS server browser Comcast network 68.80.0.0/13 school network 68.80.2.0/24 web page web server 64.233.169.105 Google’s network 64.233.160.0/19 Link Layer 5-42 A day in the life… connecting to the Internet DHCP UDP IP Eth Phy DHCP DHCP DHCP DHCP connecting laptop needs to get its own IP address, addr of first-hop router, addr of DNS server: use DHCP DHCP DHCP DHCP DHCP DHCP DHCP UDP IP Eth Phy router (runs DHCP) DHCP request encapsulated in UDP, encapsulated in IP, encapsulated in 802.3 Ethernet Ethernet frame broadcast (dest: FFFFFFFFFFFF) on LAN, received at router running DHCP server Ethernet demuxed to IP demuxed, UDP demuxed to DHCP Link Layer 5-43 A day in the life… connecting to the Internet DHCP UDP IP Eth Phy DHCP DHCP DHCP DHCP DHCP DHCP DHCP DHCP DHCP DHCP UDP IP Eth Phy router (runs DHCP) DHCP server formulates DHCP ACK containing client’s IP address, IP address of first-hop router for client, name & IP address of DNS server encapsulation at DHCP server, frame forwarded (switch learning) through LAN, demultiplexing at client DHCP client receives DHCP ACK reply Client now has IP address, knows name & addr of DNS server, IP address of its first-hop router Link Layer 5-44 A day in the life… ARP (before DNS, before HTTP) DNS DNS DNS ARP query DNS UDP IP ARP Eth Phy ARP ARP reply Eth Phy router (runs DHCP) before sending HTTP request, need IP address of www.google.com: DNS DNS query created, encapsulated in UDP, encapsulated in IP, encapsulated in Eth. To send frame to router, need MAC address of router interface: ARP ARP query broadcast, received by router, which replies with ARP reply giving MAC address of router interface client now knows MAC address of first hop router, so can now send frame containing DNS query Link Layer 5-45 A day in the life… using DNS DNS DNS DNS DNS DNS DNS DNS UDP IP Eth Phy DNS DNS DNS UDP IP Eth Phy DNS server DNS Comcast network 68.80.0.0/13 router (runs DHCP) IP datagram containing DNS query forwarded via LAN switch from client to 1st hop router IP datagram forwarded from campus network into Comcast network, routed (tables created by RIP, OSPF, IS-IS and/or BGP routing protocols) to DNS server demux’ed to DNS server DNS server replies to client with IP address of www.google.com Link Layer 5-46 A day in the life…TCP connection carrying HTTP HTTP HTTP TCP IP Eth Phy SYNACK SYN SYNACK SYN SYNACK SYN router (runs DHCP) SYNACK SYN SYNACK SYN SYNACK SYN TCP IP Eth Phy web server 64.233.169.105 to send HTTP request, client first opens TCP socket to web server TCP SYN segment (step 1 in 3way handshake) inter-domain routed to web server web server responds with TCP SYNACK (step 2 in 3-way handshake) TCP connection established! Link Layer 5-47 A day in the life… HTTP request/reply HTTP HTTP HTTP TCP IP Eth Phy HTTP HTTP HTTP HTTP HTTP HTTP web page finally (!!!) displayed HTTP HTTP HTTP HTTP HTTP TCP IP Eth Phy web server 64.233.169.105 router (runs DHCP) HTTP request sent into TCP socket IP datagram containing HTTP request routed to www.google.com web server responds with HTTP reply (containing web page) IP datagram containing HTTP reply routed back to client Link Layer 5-48 Chapter 5: Summary principles behind data link layer services: error detection, correction sharing a broadcast channel: multiple access link layer addressing instantiation and implementation of various link layer technologies Ethernet switched LANS, VLANs virtualized networks as a link layer: MPLS synthesis: a day in the life of a web request Link Layer 5-49 Chapter 5: let’s take a breath journey down protocol stack complete (except PHY) solid understanding of networking principles, practice ….. could stop here …. but lots of interesting topics! wireless multimedia security network management Link Layer 5-50