Design of a Diversified Router: Packet Formats

Slides:

Advertisements

Similar presentations

Understanding IPv6 Slide: 1 Appendix A Link-Layer Support for IPv6.

Advertisements

ISO/OSI Model Layers Application: applications that use the network. This is were mail, browsers, ftp, etc reside Presentation: data formats, character.

Senior Project with the SPP Michael Williamson. Communicating with a Slice Slice-RMP library using a Unix Domain Socket ◦ RPC-Like ◦ Slice application.

1 Application TCPUDP IPICMPARPRARP Physical network Application TCP/IP Protocol Suite.

Source Port # (16)Destination Port # (16) Sequence Number (32 bits) Acknowledgement Number (32 bits) Hdr Len (4) Flags (6)Window Size (16) Options (if.

ARP Request/Reply Can we modify our previous device-driver so it will allow us to send and receive ‘raw’ packets?

Network Redundancy Multiple paths may exist between systems. Redundancy is not a requirement of a packet switching network. Redundancy was part of the.

John DeHart ONL NP Router Block Design Review: Lookup (Part of the PLC Block)

Microsoft Windows Server 2003 TCP/IP Protocols and Services Technical Reference Slide: 1 Lesson 9 Internet Group Management Protocol (IGMP)

McGraw-Hill©The McGraw-Hill Companies, Inc., 2004 Chapter 15 Network Layer Protocols: ARP, IPv4, ICMPv4, IPv6, and ICMPv6.

資管 Lee Appendix A1 Link-Layer Support for IPv6. 資管 Lee Lesson Objectives Basic structure of IPv6 packets LAN media WAN media IPv6 over IPv4.

John DeHart and Mike Wilson SPP V2 Router Design.

Washington WASHINGTON UNIVERSITY IN ST LOUIS Packet Routing Within MSR Fred Kuhns

Lecture 3 Overview. Protocol An agreed upon convention for communication both endpoints need to understand the protocol. Protocols must be formally defined.

Chapter 9 Hardware Address & Frame Type Identification Hardware address of frame Addressing schemes Ethernet Frame header format.

Chapter 9 Hardware Addressing and Frame Type Identification 1.Delivering and sending packets 2.Hardware addressing: specifying a destination 3. Broadcasting.

Michael Wilson Block Design Review: Line Card Key Extract (Ingress and Egress)

Network Layer4-1 Datagram networks r no call setup at network layer r routers: no state about end-to-end connections m no network-level concept of “connection”

BAI513 - PROTOCOLS ARP BAIST – Network Management.

Where are we? Chapter 3 and 4 are focused on getting the data from one place to another. Switching and routing Review the next slides First our goal is.

John DeHart Block Design Review: Lookup for IPv4 MR, LC Ingress and LC Egress.

Brandon Heller Block Design Review: Substrate Decap and IPv4 Parse.

ARP ‘n RARP. The Address Resolution Protocol (ARP) is a request sent out by a computer to find another computer’s MAC address. It already knows the IP.

David M. Zar Block Design Review: PlanetLab Line Card Header Format.

IP Fragmentation. Network layer transport segment from sending to receiving host on sending side encapsulates segments into datagrams on rcving side,

Data Communication Networks Lec 18. Wired LAN:Ethernet Datalink layer – Logical link control(LLC) – MAC Physical layer.

Behrouz A. Forouzan TCP/IP Protocol Suite, 3rd Ed.

Chapter 21 Address Mapping

A quick intro to networking

: An Introduction to Computer Networks

Standards Basics.

Design of a High Performance PlanetLab Node

Design of a Diversified Router: Memory Usage

Design of a Diversified Router: TCAM Usage

Design of a Diversified Router: TCAM Usage

Design of a Diversified Router: Model and System Overview

John DeHart Design of a Diversified Router: Lookup Block with All Associated Data in SRAM John DeHart

John DeHart Design of a Diversified Router: Lookup Block with All Associated Data in SRAM John DeHart

An NP-Based Ethernet Switch for the Open Network Lab Design

Ethernet : Framing and Addressing

Design of a Diversified Router: Line Card

Design of a Diversified Router: Packet Formats

Design of a Diversified Router: Common Router Framework

Design of a Diversified Router: Project Management

Design of a Diversified Router: Line Card

Design of a Diversified Router: Model and System Overview

Design of a Diversified Router: Dedicated CRF for IPv4 Metarouter

Design of a Diversified Router: IPv4 MR (Dedicated NP)

SPP V2 Router Plans and Design

Documentation for Each Block

Design of a Diversified Router: Line Card

Design of a Diversified Router: Monitoring

An NP-Based Router for the Open Network Lab Overview by JST

John DeHart Design of a Diversified Router: Lookup Block with All Associated Data in SRAM John DeHart

IXP Based Router for ONL: Architecture

Design of a Diversified Router: November 2006 Demonstration Plans

SPP Version 1 Router Traffic Examples

John DeHart Design of a Diversified Router: Lookup Block with All Associated Data in SRAM John DeHart

Design of a Diversified Router: Dedicated CRF plus IPv4 Metarouter

Design of a Diversified Router: November 2006 Demonstration Plans

Code Review for IPv4 Metarouter Header Format

Code Review for IPv4 Metarouter Header Format

Design of a Diversified Router: Memory Usage

SPP Router Plans and Design

IXP Based Router for ONL: Architecture

Design of a High Performance PlanetLab Node: Line Card

Design of a Diversified Router: Project Management

Network Architecture Models: Layered Communications

Figure 6.11 Configuration for Example 4

Data-Link Layer The Internet is a combination of networks glued together by connecting devices (routers or switches) If a packet is to travel from a host.

Presentation transcript:

Design of a Diversified Router: Packet Formats John DeHart jdd@arl.wustl.edu http://www.arl.wustl.edu/arl

Revision History 6/2/06 (JDD): created

Internal Packet Format DAddr (6B) SAddr (6B) Type=802.1Q (2B) VLAN (2B) Type=Substrate (2B) Ethernet Header Destination MPE/MI (2B) Substrate Header Source MPE/MI (2B) Shim Metanet Frame Len (2B) Metanet Frame (Metanet Frame Len Bytes) Flags (10b) Shim Data Length (6b) Ethernet Trailer (Pad+CRC) Shim Data (0-63B) MPE: Meta Processing Element MI: Meta Interface MetaNet Frame Length: Length of Metanet Frame in Bytes Does not include Shim

LC  MPE Internal Format Metanet Frame (Metanet Frame Len Bytes) Ethernet Trailer (Pad+CRC) DAddr (6B) SAddr (6B) Type=802.1Q (2B) VLAN (2B) Type=Substrate (2B) Destination MPE (2B) RxMI (2B) Metanet Frame Len (2B) Flags (10b) = 0 Shim Data Length (6b) = 0 Shim Data (0-63B) MPE Destination MPE: ID of receiving MPE RxMI: Receive Meta Interface Shim: So far, no uses of shim have been defined for LC  MPE Flags = 0, Shim Data Length = 0  null/empty shim.

MPE  LC Internal Format Metanet Frame (Metanet Frame Len Bytes) Ethernet Trailer (Pad+CRC) DAddr (6B) SAddr (6B) Type=802.1Q (2B) VLAN (2B) Type=Substrate (2B) TxMI (2B) Source MPE (2B) Metanet Frame Len (2B) Flags (10b) Shim Data Length (6b) Shim Data (0-63B) MPE LC Source MPE: ID of sending MPE TxMI: Transmit Meta Interface Shim: May contain MN Address for ARP or Ethernet broadcast of multicast address

MPE  MPE Internal Format Metanet Frame (Metanet Frame Len Bytes) Ethernet Trailer (Pad+CRC) DAddr (6B) SAddr (6B) Type=802.1Q (2B) VLAN (2B) Type=Substrate (2B) Destination MPE (2B) Source MPE (2B) Metanet Frame Len (2B) Flags (10b) Shim Data Length (6b) Shim Data (0-63B) MPE MPE Destination MPE: ID of receiving MPE Source MPE: ID of sending MPE Shim: MR specific information, things like exception packet indicators, etc.

Pkt Format Delivered by Substrate to MPE Metanet Frame (Metanet Frame Len Bytes) Destination MPE (2B) RxMI (2B) Metanet Frame Len (2B) Flags (10b) Shim Data Length (6b) Shim Data (0-63B) In a shared NPU case: MR will not receive the Ethernet header Destination MPE should be id of MR MPE receiving packet

Extra The next set of slides are for templates or extra information if needed

Text Slide Template

Image Slide Template