The output of /ip route print now is interesting enough to deserve detailed observationįlags: X - disabled, A - active, D - dynamic,Ĭ - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,ī - blackhole, U - unreachable, P - prohibit # add route to the remote BGP peer's loopback address routing bgp peer add remote-address=10.5.5.2 remote-as=65000 address-families=vpnv4 \ routing bgp instance vrf add instance=default routing-mark=cust-two redistribute-connected=yes routing bgp instance vrf add instance=default routing-mark=cust-one redistribute-connected=yes routing bgp instance set default as=65000 mpls ldp set enabled=yes transport-address=10.5.5.3 Ia - IS-IS inter area, * - candidate default, U - per-user static route I - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2Į1 - OSPF external type 1, E2 - OSPF external type 2 Route Distinguisher: 1.1.1.1:111 (default for vrf cust-one)Ĭodes: C - connected, S - static, R - RIP, M - mobile, B - BGPĭ - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area Network Next Hop Metric LocPrf Weight Path Origin codes: i - IGP, e - EGP, ? - incomplete Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, (Default configuration has valid label range.)īGP table version is 5, local router ID is 10.5.5.3
#Mpls fundamentals luc de ghein example 10 4 explanation install
You need to install mpls-test package and configure valid label range for this to work. Please note that a VPNv4 route will be distributed only if it has a valid MPLS label. This way you can have overlapping IPv4 prefixes distributed in BGP. These so called VPNv4 routes have prefix that consists of a route distinguisher and an IPv4 network prefix. They are installed in a separate route table and, if present, visible under /routing bgp vpnv4-route. Once list of VRFs for BGP instance, route distinguisher and export route targets has been configured, some active VPNv4 address family routes may be created, depending on BGP redistribution settings. Then configure a list of VRFs for each BGP instance that will participate in VRF routing. Export route target list for a VRF should contained at least the route distinguisher for that VRF. Configure import and export lists under /ip route vrf, import-route-targets and export-route-targets. Route installation in VRF tables is controlled by BGP extended communities attribute. Usually there will be one-to-one correspondence between route distinguishers and VRFs, but that's not a mandatory requirement. First configure the route distinguisher for a VRF. You can use multi-protocol BGP with VPNv4 address family to distribute routes from VRF route tables - not only to other routers, but also to different routing tables in the router itself. (You can still override this behavior with custom route lookup rules, as they have precedence.) For VRFs: if lookup is done, and no route is found in VRF route table, the lookup fails with "network unreachable" error. For policy routing: after route lookup has been done in policy-route table, and no route was found, route lookup proceeds to the main route table. Read-only route attribute gateway-table displays information about which table is used for a particular route (default is main).