1/13/2024 0 Comments Configure jdiskreport![]() Packet sent with a source address of 11.11.11.11 Sending 5, 100-byte ICMP Echos to 22.22.22.22, timeout is 2 seconds: Perfect! Lets check the connectivity to see if the VPN labels are used correctly in the MPLS backbone. Lets check the routing tables of the site routers. Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path Route Distinguisher: 1:1 (default for vrf CUSTOMER) 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, SPEDGE1#sh ip bgp vpnv4 allīGP table version is 282, local router ID is 10.10.10.2 We should now have all networks in the BGP table and after that we can check the site routers if they are receiving OSPF routes from the MPLS backbone. SPEDGE2(config-router-af)#redistribute ospf 2 metric 100 match internal external SPEDGE2(config-router)#address-family ipv4 unicast vrf CUSTOMER SPEDGE2(config-router)#redistribute bgp 1 metric 100 subnets SPEDGE1(config-router-af)#redistribute ospf 2 metric 100 match internal external SPEDGE1(config-router)#address-family ipv4 unicast vrf CUSTOMER SPEDGE1(config-router)#redistribute bgp 1 metric 100 subnets So here is the config of BGP and OSPF on the SPEDGE routers: SPEDGE1(config-router)#router ospf 2 vrf CUSTOMER ![]() (By the way, on the SPEDGE routers you now should see the OSPF routes of the attached SITE router). ![]() Nothing! Well thats quite logical because we have not configured mutual redistribution between OSPF and BGP yet. For example at SITE1 we are missing the networks of SITE2 and vice versa. When checking the routing tables we can see that we dont have ALL routes in the routing table. We can then see our adjacencies coming up! SITE1#sh ip o n SPEDGE2(config)#router ospf 2 vrf CUSTOMER SPEDGE1(config)#router ospf 2 vrf CUSTOMER We need to generate a separate OSPF process and bind this process to the corresponding vrf. As you can see now, there is no such thing like address families. We will now enter the configuration for the SPEDGE routers. SITE2(config-router)#redistribute connected subnets SITE1(config-router)#redistribute connected subnets So lets start with configuring OSPF on the SITE routers. Neighbor 10.10.10.2 send-community extended Neighbor 10.10.10.2 update-source Loopback0 SPEDGE2 (MPLS, OSPF backbone and MP-BGP) SPEDGE2#sh run | sec router Neighbor 10.10.10.3 update-source Loopback0 SPEDGE1 (MPLS, OSPF backbone and MP-BGP) SPEDGE1(config)#do sh run | sec router SPCORE (MPLS and OSPF “1” only for backbone connectivity) SPCORE#sh run | sec router Here is the config part of the SP routers (the routing protocol part): – configure OSPF as the PE-CE routing protocol and make sure that the networks of SITE1 and SITE2 can reach each other via the MPLS VPN backbone. – some loopback interfaces which simulate networks connected to the SITE routers – on the SP routers there is an OSPF process “1” which is used for backbone connectivity for the MP-BGP routers and for LDP – fa0/1 of the SPEDGE routers are in vrf “CUSTOMER” – a small MPLS backbone with SPCORE as P-Router (MPLS only, no BGP), SPEDGE routers as PE-Routers with MP-BGP enabled ![]() Here is our topology (same topology like with the other protocols used): Right now I am going to show how to use OSPF as a PE-CE routing protocol when using MPLS VPNs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |