(Assigning an interface to a VRF automatically wipes it of any configured IP addresses. Now we need to assign the appropriate interfaces to each VRF and reapply their IP addresses. The command route-target both is used as a shortcut for the two commands route-target import and route-target export, which appear separately in the running configuration. PE2(config-vrf)# route-target both 65000:2 PE2(config-vrf)# route-target both 65000:1 PE1(config-vrf)# route-target both 65000:2 PE1(config-vrf)# route-target both 65000:1 VRF configuration must be performed on both PE routers.
CBT NUGGETS MPLS FUNDAMENTALS IOU FREE
For simplicity, we'll reuse the same value as both an import and export route target within each VRF (though we are free to choose a different or additional route targets if we prefer). We'll use a route distinguisher for each VRF in the form of. We need to assign each VRF a route distinguisher (RD) to uniquely identify prefixes as belonging to that VRF and one or more route targets (RTs) to specify how routes should be imported to and exported from the VRF. Our next step is to create customer VRFs on our PE routers and assign the customer-facing interfaces to them. State: Oper Msgs sent/rcvd: 12/12 Downstream State: Oper Msgs sent/rcvd: 12/13 Downstream P1# show mpls ldp neighbor Peer LDP Ident: 10.0.0.2:0 Local LDP Ident 10.0.0.1:0 LDP adjacencies can be verified with the command show mpls ldp neighbor: We can verify the configuration of MPLS interfaces with show mpls interfaces. LDP typically runs between loopback addresses not directly reachable by LDP peers, which is why it's important to configure an IGP in the core before enabling MPLS. LDP is enabled automatically as the default label distribution protocol (versus Cisco's legacy TDP). MPLS is not enabled on any CE-facing interfaces CE routers do not run MPLS, just plain IP routing. Enable MPLSįirst we need to enable MPLS on all P-P and P-PE links with the mpls ip interface command.
There are five core tasks we need to accomplish to get an MPLS VPN up and running: OSPF processes have also been preconfigured on the CE routers however, these OSPF topologies will remain separate from the provider OSPF. In our lab, OSPF is already in operation as the provider network IGP.
an IGP running among all P and PE routers is used to support LDP and BGP adjacencies within the provider network.CE (customer edge) routers exist at the edge of a customer site they have no VPN awareness.PE (provider edge) routers connect to customer sites and form the edge of a VPN.
P (provider) routers are ISP core routers which don't connect to customer routers and typically run only MPLS.If you're unfamiliar with the concepts of MPLS switching and VRFs on Cisco IOS, you may want to check out a few of my past articles before continuing: Today we're going to look at the configuration required to create a basic MPLS VPN servicing two customers, each with a presence at two physical sites.
0 kommentar(er)
