![]() 1 folder of images & 1 GPX file (w/o time adjustments). I've previously used my GPS device & GeoSetter only for single local outings. I just returned from a 25-day African wildlife photo safari. To all those who have helped me previously, please bear with me again. Packet sent with a source address of 172.16.20.Help! I've gone brain-dead again. Sending 5, 100-byte ICMP Echos to 172.16.10.1, timeout is 2 seconds: Packet sent with a source address of 172.16.10.1 Sending 5, 100-byte ICMP Echos to 172.16.20.1, timeout is 2 seconds: Example 4-30 shows that the ping has been successful.Įxample 4-30. Verify end-to-end connectivity using ping – Verify end-to-end connectivity between the CE1-A and CE2-A by issuing a ping from CE1-A to network 172.16.20.0/24 on CE2-A and vice versa. Verify Routes on CE1-A and CE2-AĬ 172.16.20.0 is directly connected, Loopback0 Verify RIP routes on CE routers CE1-A and CE2-A – Check the BGP VPNv4 routing table to see if routes are received properly. Verify VRF routing table on PE1-AS1 and PE2-AS1 – Check the VRF routing table to see if routes to the CE networks are configured properly and remote routes from PE routers are received in the VRF.Įxample 4-28 shows that PE1-AS1 has received routes from the PE2-AS1 router for the 172.16.20.0/24 network and has also received 172.16.10.0 network from CE1-A.Įxample 4-28. The steps to verify RIPv1 PE-CE routing are as follows: Neighbor 10.10.10.102 send-community extended Neighbor 10.10.10.102 update-source Loopback0 Version 2 redistribute bgp 1 metric transparent CE1-A and PE1-AS1 Configuration – RIPv1 PE-CE Example 4-27 shows the PE1-AS1 and CE1-A final configuration.Įxample 4-27. RIPv1 PE-CE Routing – PE1-AS1 and CE1-A Final ConfigurationĬonfiguration for PE2-AS1, P1-AS1, P2-AS2, and CE2-A remains the same as what was shown in the "RIPv2 PE-CE Routing – Provider Edge PE1-AS1 and PE2-AS1 Configuration" section. Interface Send Recv Triggered RIP Key-chain Incoming update filter list for all interfaces is not setĭefault version control: send version 2, receive version 2 Outgoing update filter list for all interfaces is not set Invalid after 180 seconds, hold down 180, flushed after 240 Sending updates every 30 seconds, next due in 5 seconds ![]() PE1-AS1(config-if)#ip rip receive version 1 PE1-AS1(config-if)# ip vrf forwarding VRF-RIP PE1-AS1(config)#interface FastEthernet0/0 ![]() Example 4-26 shows the necessary steps to configure PE1-AS1 interface connected to CE1-A to send and receive RIPv1 routes.Įxample 4-26. RIPv2 PE-CE routing configuration is still used on PE2-AS1 because the MP-iBGP session between PE routers transports only RIPv2 routes. IP addressing for the CE networks adheres to classful addressing. Because CE1-A is sending RIPv1 routes, the interface on PE1-AS1 connected to CE1-A is configured to receive and send RIPv1 routes. Provider Implementing RIPv1 PE-CE RoutingĬE1-A is running RIPv1 routing protocol. The topology to demonstrate RIPv1 PE-CE routing is shown in Figure 4-7.įigure 4-7. RIPv1 is not recommended for MPLS VPN networks and is demonstrated here only for learning purposes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |