- \n
- Properly configured IGP<\/li>\n
- Loopback interface properly configured with IP \/32<\/li>\n
- Redistribution of routes in IGP<\/li>\n<\/ul>\n
<\/p>\n
For MPLS activation, on the NE40, assuming the loopback IP is 10.1.1.1:<\/p>\n\n
[huawei] mpls lsr-id 10.1.1.1
After that, we need to activate the protocols on the interfaces that will be part of MPLS<\/p>\n\n
interface giga0\/3\/22.182
Virtual-Ethernet<\/h2>\n\n
Virtual Ethernet is used when we have the need to do services of \u201cLayer 2\u201d<\/em> e \u201cLayer 3\u201d<\/em> on the same device.<\/p>\n
We know that, in a VLL in Martini mode, for example (MPLS + L2VC)<\/em>, it is not permitted to apply Layer 2 configurations (\u201cl2 binding vsi\u201d or \u201cmpls l2vc\u201d)<\/em> and Layer 3 (\u201cip address x.x.x.x\u201d)<\/em> on the same interface; they must be properly \u201cseparated.\u201d<\/p>\n
Until now, in applications of this level, it has been common to implement the \u201cLayer 2\/MPLS\/VLLs\u201d side on switches or dedicated equipment designed for this purpose, however, using virtual Ethernet<\/em> on Huawei makes it perfectly possible to implement an MPLS approach, use L2VC or VPLS tunnels, and still handle \u201cLayer 3\u201d using only the device (router) without the need for other equipment for this purpose.<\/p>\n
Using the concept of \u201cVirtual-Ethernet\u201d in Huawei, we created two virtual interfaces that are properly \u201clinked\u201d where <\/span>each of them belongs to a \u201cside\u201d being \u201clayer 2\u201d and \u201clayer3\u201d.<\/p>\n
<\/p>\n
Possible applications<\/h2>\n
- \n
- Redundancy based on MPLS and iBGP\/BGP sessions where OSPF\/MPLS and BGP work on the same box.<\/li>\n
- MPLS based redundancy for BNG scenarios ( IPoE \/ PPPoE ) where OSPF\/MPLS and PPPoE-Service work on the same box.<\/li>\n
- Scenarios for Layer2 VPNs accessing a public network.<\/li>\n
- Scenarios for Layer 2 VANs accessing a Layer 3 VPN.<\/li>\n<\/ul>\n
<\/p>\n
Limitations<\/h2>\n
- \n
- \u201cVE Groups\u201d are only supported in \u201cVirtual System\u201d admin.<\/li>\n
- There is a limitation of 3 \u201cVE Groups\u201d per box (in case of NE40E-M2K)<\/li>\n<\/ul>\n
<\/p>\n\n
![\"\"](\"https:\/\/www.made4it.com.br\/wp-content\/uploads\/2020\/02\/ve-group.png\")
<\/figure>\n\nConfiguration example 1<\/h2>\n\n
Consider a scenario where we want to \u201cterminate\u201d an L2VC tunnel and, on the same device, close an eBGP session with a remote host (within that VLL) using virtual Ethernet. We\u2019ll receive it on an L2VC with ID \u201c301\u201d and also use a VLAN with ID \u201c301\u201d to establish the eBGP session with our remote provider. <\/p>\n
<\/p>\n
Prerequisites:<\/h3>\n
- \n
- Communication interfaces with \u201cUP\u201d and \u201cRunning\u201d network equipment<\/li>\n
- Communication interfaces with properly addressed network equipment<\/li>\n
- IGP duly aligned on all network equipment.<\/li>\n
- Loopbacks properly defined on all network equipment.<\/li>\n
- Duly closed LDP sessions on all network devices.<\/li>\n
- L2VPN properly aligned on the remote host.<\/li>\n<\/ul>\n
<\/p>\n
Settings:<\/h6>\n
Let’s create the virtual interface, and define it with the L2 function. The VE-GROUP is the 1. <\/p>\n\n
virtual-ethernet interface 0\/1\/1
After that, let’s create the L3 pair of the virtual interface.<\/p>\n\n
virtual-ethernet interface 0\/2\/1
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
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
virtual-ethernet interface 0\/1\/1.301
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
Let’s assume that our ISP has assigned us the IP address 192.168.10.2\/30 to establish an \u201ceBGP\u201d connection. Therefore, we need to create the interface \u201cVE0\/2\/1.301\u201d and configure it with this information.<\/p>\n\n
virtual-ethernet interface 0\/2\/1.301
As we can see, the \u201cVE0\/1\/1\u201d and \u201cVE0\/2\/1\u201d interfaces are properly associated, where the \u201csubinterfaces\u201d\u2014both of which are part of the same \u201cve-group\u201d\u2014are properly associated for whatever purpose, each performing its function as specified, whether \u201cl2-terminate\u201d or \u201cl3-access.\u201d<\/p>\n