Other routers are configured in similar way - LDP is enabled on interfaces that connect routers and not enabled on interfaces that connect customer networks. This makes router originate LDP session connections with this address and also advertise this address as transport address to LDP neighbors. Note that transport-address gets set to 9.9.9.1. mpls ldp set enabled=yes transport-address=9.9.9.1 lsr-id=9.9.9.1 On R1 this is done by commands (interface ether3 is facing network 1.1.1.0/24): In order to distribute labels for routes, LDP should get enabled. This yields routing table on R5 like > ip route printįlags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,ī - blackhole, U - unreachable, P - prohibit On other routers OSPF is configured in similar way. routing ospf network add area=backbone network=5.5.5.0/24 routing ospf network add area=backbone network=4.4.4.0/24 routing ospf instance set redistribute-connected=as-type-1 For example, on R5 OSPF is configured with the following commands: In given example setup OSPF is used to distribute routes. LDP by default distributes labels for active IGP routes (that is - connected, static, and routing protocol learned routes, except BGP). The rest of routers are configured similar way.Īs LDP distributes labels for active routes, essential requirement is properly configured IP routing. ip address add address=9.9.9.1/32 interface=lobridge For example, on R1 it is done with the following commands: In RouterOS "loopback" IP address can be configured by creating dummy bridge interface without any ports and adding address to it. use of loopback address as LDP transport address ensures proper penultimate hop popping behaviour when multiple labels are attached to packet as in case of VPLS.as there is only one LDP session between any 2 routers, no matter how many links connect them, loopback IP address ensures that LDP session is not affected by interface state or address changes.Prerequisites for MPLS "Loopback" IP addressĪlthough not a strict requirement, it is advisable to configure routers participating in MPLS network with "loopback" IP addresses (not attached to any real network interface) to be used by LDP to establish sessions. This guide gives step by step instructions that will lead to implementation of VPLS to achieve necessary service. Using one of MPLS applications - VPLS can further increase efficency of ethernet frame forwarding by not having to encapsulate ethernet frames in IP frames, thus removing IP header overhead. Note that there are no IP addresses configured on R1, R4 and R5 interfaces that face customer networks.Įnabling MPLS forwarding can speed up packet forwarding process in such network. So far it has been implemented by means of bridging EoIP tunnels with physical ethernet interfaces. 8.2 Effects of label binding filtering on data forwarding in networkįor MPLS overview and MPLS features that RouterOS supports see MPLS Overview Example networkĬonsider network service provider that is connecting 3 remote sites of Customer A (A1,A2 and A3) and 2 remote sites of Customer B (B1 and B2) using its routed IP network core, consisting of routers (R1-R5):Ĭustomers require transparent ethernet segment connection between sites.7.3 Bridging ethernet segments with VPLS.7.2 Penultimate hop popping effects on VPLS tunnels.6.2 Penultimate hop popping and traceroute source address.
6 Drawbacks of using traceroute in MPLS network.
0 kommentar(er)
