{"id":11781,"date":"2020-02-18T13:39:04","date_gmt":"2020-02-18T16:39:04","guid":{"rendered":"https:\/\/made4it.com.br\/interfaces-l3-in-tunnels-l2-mpls-in-router-huawei-ne-how-to-configure-mpls-with-ip-in-huawei\/"},"modified":"2023-03-08T16:44:37","modified_gmt":"2023-03-08T19:44:37","slug":"interfaces-l3-in-tunnels-l2-mpls-in-router-huawei-ne-how-to-configure-mpls-with-ip-in-huawei","status":"publish","type":"post","link":"https:\/\/made4it.com.br\/en\/interfaces-l3-in-tunnels-l2-mpls-in-router-huawei-ne-how-to-configure-mpls-with-ip-in-huawei\/","title":{"rendered":"L3 Interfaces in L2 MPLS Tunnels on Huawei NE Router (How to Configure MPLS with IP on Huawei)"},"content":{"rendered":"\n<p>\u201cMulti Protocol Label Switching\u201d is a mechanism in high-performance telecommunications networks that directs data from a network node to the next node based on shortest path labels ( Labels ) instead of network addresses ( Routes ), avoiding queries complexes in a routing table.<\/p>\n<p>One of the benefits of MPLS, in addition to its interoperability with different types of technologies such as E1\/xDSL\/ATM\/Ethernet, is the possibility of \u201cVPNs\u201d both at Layer 2 and Layer 3.<\/p>\n<p>Huawei, in its \u201cNE\u201d line, allows us to use MPLS + VPNs resources where the MPLS activation process itself takes place as in any other router for this purpose, being a <strong>prerequisite<\/strong>:<\/p>\n<ul>\n<li>Properly configured IGP<\/li>\n<li>Loopback interface properly configured with IP \/32<\/li>\n<li>Redistribution of routes in IGP<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>For MPLS activation, on the NE40, assuming the loopback IP is 10.1.1.1:<\/p>\n\n<pre class=\"wp-block-preformatted\">[huawei] mpls lsr-id 10.1.1.1 <br\/>[huawei] mpls <br\/>[huawei] mpls l2vpn <\/pre>\n\n<p>After that, we need to activate the protocols on the interfaces that will be part of MPLS<\/p>\n\n<pre class=\"wp-block-preformatted\">interface giga0\/3\/22.182<br\/> mpls<br\/> mpls te<br\/> mpls rsvp-te<br\/> mpls ldp <\/pre>\n\n<h2 class=\"wp-block-heading\">Virtual-Ethernet<\/h2>\n\n<p>Virtual Ethernet is used when we have the need to do services of&nbsp;<em>\u201cLayer 2\u201d<\/em>&nbsp;e&nbsp;<em>\u201cLayer 3\u201d<\/em>&nbsp;on the same device.<\/p>\n<p>We know that in a VLL in Martini mode for example&nbsp;<em>(MPLS + L2VC)<\/em>, applying Layer 2 settings is not allowed&nbsp;<em>(\u201cl2 binding vsi\u201d ou \u201cmpls l2vc\u201d)<\/em>&nbsp;and Layer 3&nbsp;<em>(\u201cip address x.x.x.x\u201d)<\/em>&nbsp;in the same interface, being necessary the proper \u201cseparation\u201d of them.<\/p>\n<p>Until then, in applications of this level, it was common to \u201cside\u201d \u201cLayer2\/Mpls\/VLLs\u201d in Switches or dedicated equipment for this purpose, however, using the&nbsp;<em>virtual-ethernet<\/em>&nbsp;in Huawei it becomes perfectly possible to have an MPLS approach, use L2VC tunnels or VPLS&#8217;es and still do \u201clayer3\u201d using only the box (router) without the need for other assets for this purpose.<\/p>\n<p>Using the concept of \u201cVirtual-Ethernet\u201d in Huawei, we created two virtual interfaces that are properly \u201clinked\u201d <span lang=\"PT-BR\">where&nbsp;<\/span>each of them belongs to a \u201cside\u201d being \u201clayer 2\u201d and \u201clayer3\u201d.<\/p>\n<p>&nbsp;<\/p>\n<h2>Possible applications<\/h2>\n<ul>\n<li>Redundancy based on MPLS and iBGP\/BGP sessions where OSPF\/MPLS and BGP work on the same box.<\/li>\n<li>MPLS based redundancy for BNG scenarios ( IPoE \/ PPPoE ) where OSPF\/MPLS and PPPoE-Service work on the same box.<\/li>\n<li>Scenarios for Layer2 VPNs accessing a public network.<\/li>\n<li>Scenarios for Layer 2 VANs accessing a Layer 3 VPN.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Limitations<\/h2>\n<ul>\n<li>\u201cVE Groups\u201d are only supported in \u201cVirtual System\u201d admin.<\/li>\n<li>There is a limitation of 3 \u201cVE Groups\u201d per box (in case of NE40E-M2K)<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n\n<figure class=\"wp-block-image\"><img fetchpriority=\"high\" decoding=\"async\" width=\"441\" height=\"118\" src=\"https:\/\/www.made4it.com.br\/wp-content\/uploads\/2020\/02\/ve-group.png\" alt=\"\" class=\"wp-image-1087\" srcset=\"https:\/\/made4it.com.br\/wp-content\/uploads\/2020\/02\/ve-group.png 441w, https:\/\/made4it.com.br\/wp-content\/uploads\/2020\/02\/ve-group-300x80.png 300w\" sizes=\"(max-width: 441px) 100vw, 441px\" \/><\/figure>\n\n<h2 class=\"wp-block-heading\">Configuration example 1<\/h2>\n\n<p>Consider a scenario where we want to \u201cterminate\u201d an L2VC tunnel and, in the same box, close an eBGP session with a remote host (inside said VLL) using virtual-ethernet. We will receive it in an L2VC with ID \u201c301\u201d and also use a vlan with ID \u201c301\u201d to close the eBGP with our remote operator.<\/p>\n<p>&nbsp;<\/p>\n<h3>Pre-requisites:<\/h3>\n<ul>\n<li>Communication interfaces with \u201cUP\u201d and \u201cRunning\u201d network equipment<\/li>\n<li>Communication interfaces with properly addressed network equipment<\/li>\n<li>IGP duly aligned on all network equipment.<\/li>\n<li>Loopbacks properly defined on all network equipment.<\/li>\n<li>Duly closed LDP sessions on all network devices.<\/li>\n<li>L2VPN properly aligned on the remote host.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h6>Settings:<\/h6>\n<p>Let&#8217;s create the virtual interface, and define it with the L2 function. The VE-GROUP is the 1.<\/p>\n\n<pre class=\"wp-block-preformatted\">interface virtual-ethernet 0\/1\/1<br\/> ve-group 1 l2-terminate<\/pre>\n\n<p>After that, let&#8217;s create the L3 pair of the virtual interface.<\/p>\n\n<pre class=\"wp-block-preformatted\">interface virtual-ethernet 0\/2\/1 <br\/> ve-group 1 l3-access<\/pre>\n\n<p>With these configurations, we have the \u201cVE0\/1\/1\u201d and \u201cVE0\/2\/1\u201d interfaces properly associated, where the \u201c0\/2\/1\u201d interface is responsible for the \u201clayer3\u201d side while the \u201c0\/1\/1\u201d \u201d is responsible for the \u201clayer2\u201d side. What properly associates the interfaces is the \u201cve-group\u201d, where interfaces of the same group are associated with each other.<\/p>\n<p>Now, we have to close the \u201cL2VC\u201d with our remote operator. For this, we are going to create a subinterface with ID \u201c301\u201d on the \u201clayer2\u201d side of our \u201cvirtual-ethernets\u201d. And after that create the L2VC VPN with the remote PE.<\/p>\n\n<pre class=\"wp-block-preformatted\">interface virtual-ethernet 0\/1\/1.301<br\/> vlan-type dot1q 301<br\/> description L2-Terminate 301 - L2VC Binding<br\/> mpls l2vc 10.1.1.4 301 raw<\/pre>\n\n<p>With that, we have the \u201clayer2\u201d side ready. We now have to configure the \u201clayer3\u201d side with settings related to IP connectivity.<\/p>\n<p>Let&#8217;s assume that our operator has delivered the IP 192.168.10.2\/30 to close an \u201ceBGP\u201d, therefore, we have to create the interface \u201cVE0\/2\/1.301\u201d and configure it with this data.<\/p>\n\n<pre class=\"wp-block-preformatted\">interface virtual-ethernet 0\/2\/1.301<br\/> vlan-type dot1q 301<br\/> ip address 192.168.10.2 30<br\/> description Terminacao L3 de VPN VPWS NE <\/pre>\n\n<p>As we can see, the \u201cVE0\/1\/1\u201d and \u201cVE0\/2\/1\u201d interfaces are properly associated, where the \u201csubinterfaces\u201d &#8211; &nbsp;both are part of the same \u201cve-group\u201d &#8211; &nbsp;are properly associated for whatever purpose, each one performing its function according to the declared, be it \u201cl2-terminate\u201d or \u201cl3-access\u201d.<\/p>\n<p>If you have questions, please contact us! We are available to help them.<\/p>\n<p>&nbsp;<\/p>\n<p>Cordial hugs,<\/p>\n<p>Gabriel Henrique<\/p>\n<p>IT Consulting &nbsp;Team &#8211; Made4it<\/p>\n\n<h2 class=\"wp-block-heading\"><br\/><\/h2>\n","protected":false},"excerpt":{"rendered":"<p>Learn how to configure L3 interfaces in L2 MPLS tunnels on Huawei Router.<\/p>\n","protected":false},"author":13,"featured_media":8502,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"postBodyCss":"","postBodyMargin":[],"postBodyPadding":[],"postBodyBackground":{"backgroundType":"classic","gradient":""},"footnotes":""},"categories":[530,296,531],"tags":[568,454,533,570,569,571,566,567,564,565,573,572],"class_list":["post-11781","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-huawei-en","category-network","category-routers","tag-huawei-configuration","tag-huawei-ne20-en","tag-huawei-ne40-en","tag-l3-interface-into-l2-tunnel-mpls-en","tag-l3-interface-on-l2-mpls-tunnels","tag-mpls-en","tag-mpls-configuration-huawei","tag-mpls-configuration-huawei-ne40","tag-mpls-configuration-with-ip","tag-mpls-configuration-with-ipv4","tag-mpls-huawei-en","tag-mpls-with-huawei-ip"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/posts\/11781","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/comments?post=11781"}],"version-history":[{"count":0,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/posts\/11781\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/media\/8502"}],"wp:attachment":[{"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/media?parent=11781"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/categories?post=11781"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/tags?post=11781"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}