Great presentation!! After getting a bit lost trying to Read various RFC's on MPLS-TP this made things much clearer. Sometimes a good well produced overview really helps before digging into the details. Much thanks!!
Hi, very nice presentation, it’s simple to understand and the flow which you have used to demonstrate are excellent. If you don’t mind, please share the PPT.
Briefly - yes it is becoming increasingly popular in transport networks. Many Mission Critical market segments are now employing the technology: rail, air traffic management, power distribution to name a few. For your information, KEYMILE / DZS sold their MPLS-TP technology to 'Hitachi ABB Power Grids' 4 years ago.
A TDM service (e.g. X.21 or PCM) is traditionally carried by an SDH (SONET) network. However if the network is Ethernet (Layer 2) then the TDM service can be packetised into a pseudowire using SAToP or CESoPSN and placed in an MPLS-TP tunnel. So in this case Layer 2 is Ethernet - Layer 2.5 is MPLS-TP - Layer 3 is IP - Layer 4 is UDP and RTP (for the circuit emulation). Both SDH protection rings and MPLS-TP protection rings can switch in less than 50ms which is the requirement for many mission critical applications - thus MPLS-TP can replace SDH. MPLS-TP can be a little tricky to understand initially because it is carried by Ethernet and carries Ethernet.
Pseudo-wire is an emulation of the various types of services over a packet network. The most common service carried by the PW is L2 Ethernet connection. Pseudo-wires can be implemented using LDP or RSVP-TE tunnels. It can emulate P2P connection for VLL (Virtual Leased Line) service or p2mp using VPLS (Virtual Private LAN Service). For VPLS, multiple PWs might be needed to connect PEs in a full mesh topology. Different types of tunnels can be used to build PW.
Firstly PHP is designed so that you can't pop a label with the Bottom-of-Stack bit set if the payload is indicated other than IP. Secondly, MPLS-TP is designed to be deterministic - we know the route that the LSP will follow - and at all times we know where packets have come from. The common understanding is that by popping the LSP label at the penultimte LSR we lose this origin information. And this is not acceptable. There is an interesting argument around this topic that you may wish to read - see www.ietf.org/mail-archive/web/mpls-interop/current/msg00438.html
Thanks for the explanation. Much appreciated. So my next question is why use MPLS-TP instead of MPLS ? It is true MPLS-TP helps us keeping the track about origin of packet. But in cisco documentation it is clearly stated that MPLS-TP don't support L2VPN. It also has hardware restriction.
The video explains the advantages of using MPLS-TP over MPLS for the operator - not least the ability to provide sub-50ms protection switch-over times. MPSL can't do that. Cisco may state that MPLS-TP does not support L2VPN - but I beg to differ. Services such as VPWS (Virtual Private Wire Service) and VPLS (Virtual Private LAN Service) both provide L2VPN. These are available on the XMC20 product from KEYMILE. Also see this white paper : www.keymile.com/documents/10181/56622/White+Paper+MPLS-TP+in+Mission+Critical+Systems/17e517d6-2ab7-46bf-bb5c-4b19044befe5
The similarity of MPLS-TP and SDH is that both can carry TDM services (the services must first be packetised into a pseudowire before being placed in the MPLS-TP tunnel). SDH rings are able on failure to switch direction to the protecting path within 50ms. MPLS-TP rings can also switch direction within 50ms.
Great presentation!! After getting a bit lost trying to Read various RFC's on MPLS-TP this made things much clearer. Sometimes a good well produced overview really helps before digging into the details. Much thanks!!
Great tutorial; you deserve more views.
Excellent. Very well done and clear explanation!
Hi, very nice presentation, it’s simple to understand and the flow which you have used to demonstrate are excellent. If you don’t mind, please share the PPT.
Very well done John. Informative and concise. Please make more of these. Thanks.
Hey Fanton Dang - thanks for the positive message! It's appreciated. John
Excellent tutorial - highly recommended and well done!
Great video John! Many thanks.
Great Video, very informative
excellent very clear and concise
Thank you very much!
thank you great explanation. What has the uptake been like? has MPLS-TP been adopted in transport networks?
Briefly - yes it is becoming increasingly popular in transport networks. Many Mission Critical market segments are now employing the technology: rail, air traffic management, power distribution to name a few. For your information, KEYMILE / DZS sold their MPLS-TP technology to 'Hitachi ABB Power Grids' 4 years ago.
VERY NICE EXPLANATION. GREAT EFFORTS FOR THE EDUCATION.
Crisp and clear explanation. Thanks.
very informative! thank you !
You're welcome!
this explanation emits your personality...very neat!!
Thanks for the tutorial
Many thanks for your upload. It really provide me useful information about MPLS.
Very well illustrated. Appreciate the info.
Thank you! Very good presentation.
VERY NICE SIR, PLZ make a tutorial on SD wAN as well
best tutorial, very neat. thanks
Very neat
this is really good material
Well explained
Thanks
very informative !!
At the end it says mpls tp can replace sdh. Then what is the layer 2 infrastructure that it uses
A TDM service (e.g. X.21 or PCM) is traditionally carried by an SDH (SONET) network. However if the network is Ethernet (Layer 2) then the TDM service can be packetised into a pseudowire using SAToP or CESoPSN and placed in an MPLS-TP tunnel. So in this case Layer 2 is Ethernet - Layer 2.5 is MPLS-TP - Layer 3 is IP - Layer 4 is UDP and RTP (for the circuit emulation). Both SDH protection rings and MPLS-TP protection rings can switch in less than 50ms which is the requirement for many mission critical applications - thus MPLS-TP can replace SDH. MPLS-TP can be a little tricky to understand initially because it is carried by Ethernet and carries Ethernet.
is there anyone else experiencing an issue with their vide quality? mine is only audio no video is displayed
Informative..
What is Psedowire pls elabarate
Pseudo-wire is an emulation of the various types of services over a packet network. The most common service carried by the PW is L2 Ethernet connection. Pseudo-wires can be implemented using LDP or RSVP-TE tunnels. It can emulate P2P connection for VLL (Virtual Leased Line) service or p2mp using VPLS (Virtual Private LAN Service). For VPLS,
multiple PWs might be needed to connect PEs in a full mesh topology. Different types of tunnels can be used to build PW.
I don't get the point of "php assumes layer 3 payload is ip". What's wrong with it ? Can explain please ?
Firstly PHP is designed so that you can't pop a label with the Bottom-of-Stack bit set if the payload is indicated other than IP. Secondly, MPLS-TP is designed to be deterministic - we know the route that the LSP will follow - and at all times we know where packets have come from. The common understanding is that by popping the LSP label at the penultimte LSR we lose this origin information. And this is not acceptable. There is an interesting argument around this topic that you may wish to read - see www.ietf.org/mail-archive/web/mpls-interop/current/msg00438.html
Thanks for the explanation. Much appreciated. So my next question is why use MPLS-TP instead of MPLS ? It is true MPLS-TP helps us keeping the track about origin of packet. But in cisco documentation it is clearly stated that MPLS-TP don't support L2VPN. It also has hardware restriction.
The video explains the advantages of using MPLS-TP over MPLS for the operator - not least the ability to provide sub-50ms protection switch-over times. MPSL can't do that. Cisco may state that MPLS-TP does not support L2VPN - but I beg to differ. Services such as VPWS (Virtual Private Wire Service) and VPLS (Virtual Private LAN Service) both provide L2VPN. These are available on the XMC20 product from KEYMILE. Also see this white paper :
www.keymile.com/documents/10181/56622/White+Paper+MPLS-TP+in+Mission+Critical+Systems/17e517d6-2ab7-46bf-bb5c-4b19044befe5
Sir MPLS-TP has any format like SDH frame format.
Please share
The similarity of MPLS-TP and SDH is that both can carry TDM services (the services must first be packetised into a pseudowire before being placed in the MPLS-TP tunnel). SDH rings are able on failure to switch direction to the protecting path within 50ms. MPLS-TP rings can also switch direction within 50ms.
video on GMPLS plz
★★★★★
S'il vous plait je veux une explication de MPLS-TP en francais
par tous le esprits,je veux une explication très simple en francais