MPLS / MLS difference?

MPLS / MLS difference?

NewsGroups | Search | Tools
 alt.certification.cisco  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
MPLS / MLS difference? dilan.weerasinghe 09-14-2006
Posted by on September 14, 2006, 4:29 am
If you were  Registered and logged in, you could reply and use other advanced thread options


Hi

Can someone tell me if MPLS (multi protocol layer switching) and MLS
(multi layer switching) are essentially the same thing?

Cheers


Network Magic 20% Off NMEASY coupon code spring banner 468x60
Posted by Paul Matthews on September 14, 2006, 12:25 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


dilan.weerasinghe@gmail.com wrote:

>Hi
>
>Can someone tell me if MPLS (multi protocol layer switching) and MLS
>(multi layer switching) are essentially the same thing?

They are way different.

Basically MPLS is the addition of a label to a packet such that only the label
need be read for a device to decide what to do with it. Initially this was to
try to speed things up as just a tag needed to be checked when routers did
stuff in CPU. The main advantage now is not performance as most ruters work in
hardware but separation. Through the MPLS network it is the label that needs to
be checked rather than the IP info.

That means an MPLS carrier could provide services to, say Microsoft and Cisco.
they could both use the same area of RFC1918 network addressing and be able to
function totally independantly.

MLS is Multi layer switching. The first packet in a flow will be processes in
CPU, and then a cache entry written to the switch engine so that subsequent
packets can be switched in hardware without having to trouble the CPU.
This is where thing like code red cause problems to the network. At the router
near the infected device traffic was being sent to random[1] addresses. These
were not previously in the cache and needed full lookup. If you had a router
with a large routing table *and* a default route the routing table was checked
then the packet was forwarded according to the default so it could cause the
same problem at the nest router. The real crippler was where a random address
hit a valid subnet within the network, and the taget router had to ARP for lots
of nonexistant addresses...


[1] I know it was not totlly random, but near enough...

P.
--
Paul Matthews
paul@cattytown.me.uk
http://www.hepcats.co.uk

Similar ThreadsPosted
MPLS 642-611 really a 643-611? March 26, 2005, 1:43 pm
MPLS & QoS July 28, 2005, 12:18 pm
642-611 MPLS Lab June 8, 2008, 10:07 pm
642-611 mpls exam May 10, 2005, 10:50 am
Book for MPLS February 21, 2007, 1:00 pm
Lab Challenge 6 - Simple MPLS VPN August 3, 2005, 3:17 pm
CCIP - Implementing MPLS February 26, 2006, 5:31 am
tag switching / MPLS IOS on 3810 April 27, 2006, 8:24 am
implementing mpls 642-611 question November 10, 2006, 10:39 am
642-611 MPLS - simulator question exam September 22, 2005, 9:13 pm

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map