Multilayer switch | EPFL Graph Search

Are you an EPFL student looking for a semester project?

Work with us on data science and visualisation projects, and deploy your project as an app on top of GraphSearch.

A multilayer switch (MLS) is a computer networking device that switches on OSI layer 2 like an ordinary network switch and provides extra functions on higher OSI layers. The MLS was invented by engineers at Digital Equipment Corporation. Switching technologies are crucial to network design, as they allow traffic to be sent only where it is needed in most cases, using fast, hardware-based methods. Switching uses different kinds of network switches. A standard switch is known as a layer 2 switch and is commonly found in nearly any LAN. Layer 3 or layer 4 switches require advanced technology (see managed switch) and are more expensive and thus are usually only found in larger LANs or in special network environments. Multi-layer switching combines layer 2, 3 and 4 switching technologies and provides high-speed scalability with low latency. Multi-layer switching can move traffic at wire speed and also provide layer 3 routing. There is no performance difference between forwarding at different layers because the routing and switching are all hardware-based - routing decisions are made by specialized application-specific integrated circuits (ASICs) with the help of content-addressable memory. Multi-layer switching can make routing and switching decisions based on the following MAC address in a data link frame Protocol field in the data link frame IP address in the network layer header Protocol field in the network layer header Port numbers in the transport layer header MLSs implement QoS in hardware. A multilayer switch can prioritize packets by the 6 bit differentiated services code point (DSCP). These 6 bits were originally used for type of service. The following 4 mappings are normally available in an MLS: From OSI layer 2, 3 or 4 to IP DSCP (for IP packets) or IEEE 802.1p From IEEE 802.1p to IP DSCP From IP DSCP to IEEE 802.1p From VLAN IEEE 802.1p to port egress queue. MLSs are also able to route IP traffic between VLANs like a common router. The routing is normally as quick as switching (at wire speed).

About this result

This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.

Related publications (3)

Related concepts (20)

Related courses (12)

Related lectures (91)

Software Dataplane Verification

Mihai Dobrescu

Software dataplanes are emerging as an alternative to traditional hardware switches and routers, promising programmability and short time to market. These advantages are set against the risk of disrupting the network with bugs, unpredictable performance, or security vulnerabilities. We explore the feasibility of verifying software dataplanes to ensure smooth network operation. For general programs, verifiability and performance are competing goals; we argue that software dataplanes are different -- we can write them in a way that enables verification and preserves performance. We present a verification tool that takes as input a software dataplane, written in a way that meets a given set of conditions, and (dis)proves that the dataplane satisfies crash-freedom, bounded-execution, and filtering properties. We evaluate our tool on stateless and simple stateful Click pipelines; we perform complete and sound verification of these pipelines within tens of minutes, whereas a state-of-the-art general-purpose tool fails to complete the same task within several hours.

2014

Software dataplanes are emerging as an alternative to traditional hardware switches and routers, promising programmability and short time to market. These advantages are set against the risk of disrupting the network with bugs, unpredictable performance, or security vulnerabilities. We explore the feasibility of verifying software dataplanes to ensure smooth network operation. For general programs, verifiability and performance are competing goals; we argue that software dataplanes are different---we can write them in a way that enables verification \emph{and} preserves performance. We present a verification tool that takes as input a software dataplane, written in a way that meets a given set of conditions, and (dis)proves that the dataplane satisfies crash-freedom, bounded-execution, and filtering properties. We evaluate our tool on stateless and simple stateful Click pipelines; we perform complete and sound verification of these pipelines within tens of minutes, whereas a state-of-the-art general-purpose tool fails to complete the same task within several hours.

2014

Software dataplanes are emerging as an alternative to traditional hardware switches and routers, promising programmability and short time to market. These advantages are set against the concern of introducing buggy or under-performing code into the network. We explore whether it is practical to formally prove that a software dataplane satisfies key properties that would ensure smooth network operation. In general, proving properties of real programs remains an elusive goal, but we argue that dataplanes are different: they typically follow a pipeline structure that enables our proposed approach, in which we verify pieces of the code in isolation, then compose the results to reason about the entire dataplane. We preliminarily demonstrate the potential of our approach by applying it on simple Click pipelines and proving that they are crash-free and execute a bounded number of instructions. This takes on the order of minutes, whereas a general-purpose state-of-the-art verifier fails to complete the same task within 12 hours.

2013

AR-219: Advanced CAO and Integrated Modeling DIM

1ère année: bases nécessaires à la représentation informatique 2D (3D). Passage d'un à plusieurs logiciels: compétence de choisir les outils adéquats en 2D et en 3D. Mise en relation des outils de CAO

COM-407: TCP/IP networking

In the lectures you will learn and understand the main ideas that underlie and the way communication networks are built and run. In the labs you will exercise practical configurations.

MATH-448: Statistical analysis of network data

A first course in statistical network analysis and applications.

Networking hardware, also known as network equipment or computer networking devices, are electronic devices which are required for communication and interaction between devices on a computer network. Specifically, they mediate data transmission in a computer network. Units which are the last receiver or generate data are called hosts, end systems or data terminal equipment.

A network socket is a software structure within a network node of a computer network that serves as an endpoint for sending and receiving data across the network. The structure and properties of a socket are defined by an application programming interface (API) for the networking architecture. Sockets are created only during the lifetime of a process of an application running in the node.

ServiceNow: Creating Dashboards and Reports

Explores creating dashboards in ServiceNow, focusing on advantages, transition from homepages, and important concepts like tasks and incidents.

AutoCAD Basics: Vault View AR-219: Advanced CAO and Integrated Modeling DIM

Introduces basic AutoCAD functions for creating vault elevations and working with parametric modifications and layers.

Dynamics of Linear Neural Networks

Explores the learning dynamics of deep neural networks using linear networks for analysis, covering two-layer and multi-layer networks, self-supervised learning, and benefits of decoupled initialization.