Multilayer switch

From Wikipedia, the free encyclopedia

It has been suggested that layer 4 router be merged into this article or section. (Discuss)

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.

1 Layer 3 Switching
2 MultiLayer Switch (MLS) - OSI layer 3 and/or 4
3 Layer 4-7 switch, web-switch, content-switch
4 External links

[edit] Layer 3 Switching

The major difference between the packet switching operation of a router and that of a Layer 3 switch is the physical implementation. In general-purpose routers, packet switching takes place using a microprocessor, whereas a Layer 3 switch performs this using application-specific integrated circuit (ASIC) hardware.

[edit] MultiLayer Switch (MLS) - OSI layer 3 and/or 4

A Multilayer Switch (MLS) can prioritize packets by the 6 bits in IP DSCP (differentiated services CodePoint). These 6 bits were used in the "old days" for Type of Service (ToS).

The following 4 mappings are normally available in an MLS:

From OSI layer 2, 3 or 4 to IP DSCP (if IP packet) and/or VLAN IEEE 802.1p.
From VLAN IEEE 802.1p to IP DSCP.
From IP DSCP to VLAN IEEE 802.1p.
From VLAN IEEE 802.1p to port queue.

Many MLSs implement QoS differentiated services and/or integrated services in hardware.

Some MLS's are also able to route between VLAN and/or ports like a common router. The routing is normally as quick as switching (at wirespeed). According to Cisco, Level 3 switches are basically routers that switch based on Layer 3 information, the basic difference being processing speed and/or the way they do the switching; Level 3 switches use ASICs/hardware instead of the CPU/software that a router would.

[edit] Layer 4-7 switch, web-switch, content-switch

Some switches can use up to OSI layer 7 packet information; they are called layer 4-7 switches, content-switches, content services switches, web-switches or application-switches.

Content switches are typically used for load balancing among groups of servers. Load balancing can be for HTTP, HTTPS and/or VPN, or for any application TCP/IP traffic using a specific port. Load balancing often involves NAT so that the client of the load-balanced service is not fully aware of precisely which server is handling its requests. Some of the layer 4-7 switches can NAT at wirespeed. Content switches can often also be used to perform standard operations such as SSL encryption/decryption to reduce the load on the servers receiving the traffic, and to centralise the management of digital certificates.

Some types of application require that repeated requests from a client are directed at the same application server. Since the client isn't generally aware of which server it spoke to earlier, content switches define a notion of stickiness. For example, requests from the same source IP address are directed to the same application server each time. Stickiness can also be based on SSL Ids, and some content switches can even use cookies to provide this functionality.