![]() ![]() ![]() When connecting the first time to the router with the default username admin and no password ( for some models, check user password on the sticker), you will be asked to reset or keep the default configuration (even if the default config has only an IP address). This document describes how to set up the device from the ground up, so we will ask you to clear away all defaults. The quick guide document will include information about which ports should be used to connect for the first time and how to plug in your devices. More information about the current default configuration can be found in the Quick Guide document that came with your device. When no specific configuration is found, IP address 192.168.88.1/24 is set on ether1 or combo1, or sfp1. If you noticed there are already labels for EVPN in the ilm-table output. This can jumpstart your transition to segment routing.īe sure to check back soon for more on segment routing and EVPN in the future. If it were not for the SR-LDP mapping server this functionality would not be possible. router bgp 65000Īdd address-families=vpnv4 name=OCNOS1 nexthop-choice=force-self \ A common service to put in a 元VPN is voice which is the name of the vrf above. Now that there is an end to end label switched path a 元VPN is built between IPI-1 and MikroTik-1. Here is what the label space looks like from the perspective of the MikroTik-1 as well. Tracing the label-switched path to 100.127.2.0/32 would take us via IPI-2 which does the stitching as seen above. I> 100.127.0.2/32 1 16102 Nolabel N/A N/AĪnd on IPI-1 we can see that this doesn’t appear “stitched” as it only runs IS-IS SR and not LDP as well as IS-IS SR. O - OSPF/OSPF6 SR, i - ISIS SR, k - SR CLIĬode FEC/VRF/L2CKT ILM-ID In-Label Out-Label In-Intf Out-Intf K - CLI ILM, T - MPLS-TP, s - Stitched ILMī - BGP, K - CLI, V - LDP_VC, I - IGP_SHORTCUT ipa.net#show mpls ilm-tableĬodes: > - installed ILM, * - selected ILM, p - stale ILM This will start with prefix 100.127.2.0/ to the segment routing global block starting point (16000 as defined) and be able to label the next 256 routes in order. This will assign labels to the routes in the LDP label space and distribute them to through the SR domain so we can have an end to end label switched path enabling the use of MPLS services. This is done with a segment routing – LDP mapping server. Since MikroTik only runs LDP we will have to “stitch” the LDP and segment routing domains together. Now that we have reachability between the loopbacks we can work on signaling for exchanging labels. Isis segment-routing global block 16000 23999 Redistribute ospf level-1-2 route-map REDIS-OSPF-TO-ISIS Redistribute isis IPv4-UNDERLAY route-map REDIS-ISIS-TO-OSPF Match ip address prefix-list SR-PE-LOOPBACKS Match ip address prefix-list LDP-PE-LOOPBACKS MPLS only requires the /32s of the loopbacks for functionality so redistribution is limited to the /32 loopbacks of the PE routers. MikroTik doesn’t support IS-IS so we will have to perform redistribution between the IS-IS segment and the OSPF segment as seen above. The first thing to accomplish is end to end reachability between the provider edge (PE) routers. The team here at IP architechs works on a lot of MikroTik and whitebox gear so we’ll focus on a deployment using MikroTik and IP infusion. ![]() ![]() One of the biggest questions was “how do we get there?” and while we won’t examine EVPN in this post (it’s coming in a future post don’t worry) we will look at how you can take advantage of SR while still having large portions of LDP in your network. During networking field day service provider 1 there was a ton of talk about segment routing (SR) and ethernet virtual private networks (EVPN). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |