Since R3 has the 3.3.3.0/24 network as its connected network, if in this case, R4 established LDP sessions with its 3.3.3.4 address, the penultimate hop popping would occur on R2. The requirement to deliver the tunnel-tagged packet to the tunnel endpoint explains the configuration recommendations for using “Loopback” IP addresses as tunnel endpoints. In fact, the same thing happens in VPLS tunnel traffic and the transport label (18) popped on R3 and the packet is switched only with the tunnel label. In the traceroute output, you can see that the tunnel endpoint is receiving an unlabeled probe. For example, the traceroute from R1 to R4 is as follows:
So, you can observe transport label behavior between tunnel endpoints with the traceroute tool. This causes the VPLS tunnel endpoint to only look for a label to find out what to do with the packet.
The penultimate hop popping of the transport label causes the packets to reach the endpoint of the VPLS tunnel with only one tunnel tag. Penultimate Effects of Hop Popping in VPLS Tunnels The imposed labels reflect this configuration: packets generated by the tunnel have 2 labels on them: 21 and 24. The tunnel label applied to packets is determined by the remote router (R4) for this tunnel. That is, when traffic is forwarded to the remote endpoint of the tunnel, this router imposes the transport label – the label distributed by the next hop to 9.9.9.4/32 for route 9.9. Igp-prefix indicates the route used to reach the remote endpoint of the tunnel. The remote endpoint (R4) is assigned label 24. The MPLS forwarding table indicates that this label is detected and received on this tunnel instead of forwarding to the next hop: To be able to view information about a VPLS interface, you should monitor its status:Īs you can see, R1 has assigned label 27 for the tunnel between R1 and R4. Routers maintain all of the exchanged labels so that they are immediately ready for use when needed. IP route labels are also exchanged between VPLS peers, but none can be used. After this setup, R1 LDP neighbors are as follows: A targeted LDP session is a session established between two routers that are not direct neighbors. VPLS tunnel configuration creates a dynamic LDP neighbor and establishes a “targeted” LDP session. The vpls-id parameter must be unique for each tunnel between this tunnel and the remote peer and identifies the VPLS tunnel. VPLS tunnel configurations are in the /interface VPLS menu. In fact, this label ensures traffic delivery to the other endpoint of the tunnel. To forward data in the tunnel, you need to impose 2 labels on packets which are the tunnel label and the transport label. The LDP protocol negotiates VPLS tunnels – both endpoints exchange tunnel labels to use for the tunnel. Establish the following tunnels to achieve transparent ethernet segment forwarding between customer sites:Įach tunnel setup involves creating VPLS interfaces on both tunnel endpoints. You can consider the VPLS interface as a tunnel interface like the EoIP interface.
#Mikrotik loopback interface how to#
In this section, you will learn how to configure VPLS on Mikrotik. We already taught how to Setup MPLS in Mikrotik in previous posts.
It provides the best solution to create a wide, interconnected, and secure network. In fact, For customers implementing VPLS, all sites will be on the same Ethernet LAN. This technology enables you to connect geographically dispersed Ethernet local area network (LAN) sites to each other across an MPLS backbone. VPLS stands for Virtual Private LAN Service and is a way to provide an Ethernet-based multipoint to multipoint communication over IP or MPLS networks. Recommended Article: How to Change Cisco Switch Port to Routed Port What is VPLS?
0 kommentar(er)
