08-25-2014 08:02 AM - edited 03-04-2019 11:36 PM
Guys,
I have a reasonably simple setup in which our two Offices are connected via an MPLS network. Then from Office 2 we have lots of VPN (Easy VPN) connections to remote sites. Now Office 1 can not connect (ping or otherwise) to any of the Remote Site(s). When I do a tracert from any Office 1 PC it gets to 192.168.2.2 on our Core switch at Office 2, from there onwards the tracert times out. Basically all that should happen is that the traffic should be routed from FA3/48 to VLAN111 , but the traffic does not make that jump.
When you do "show ip route remote_site_ip" from our Core for instance it does know the EIGRP route to the remote site. The Core switch can ping the remote sites, it can traceroute to the remote sites, but the traffic just does not want to jump from FA3/48 to VLAN 111.
Any ideas ?
Solved! Go to Solution.
08-25-2014 08:37 AM
Based on your description of the symptom I would guess that the remote sites do not have a route for the network at Office 1. Can you check the routing table at the remote sites for any entry that would get them to the network of Office 1?
HTH
Rick
08-25-2014 02:01 PM
Hello
I aggree with richard, may be its a missing route
"When you do "show ip route remote_site_ip" from our Core for instance it does know the EIGRP route to the remote site. The Core switch can ping the remote sites, it can traceroute to the remote sites, but the traffic just does not want to jump from FA3/48 to VLAN 111"
your icmp connectivity test which is successful from the core is sourced from what interface?
Do you have auto summerisation enabled on the eigrp process? Is the interface/subnet 192.168.2.0 being advertised towards office2
res
Paul
08-25-2014 08:37 AM
Based on your description of the symptom I would guess that the remote sites do not have a route for the network at Office 1. Can you check the routing table at the remote sites for any entry that would get them to the network of Office 1?
HTH
Rick
08-25-2014 02:01 PM
Hello
I aggree with richard, may be its a missing route
"When you do "show ip route remote_site_ip" from our Core for instance it does know the EIGRP route to the remote site. The Core switch can ping the remote sites, it can traceroute to the remote sites, but the traffic just does not want to jump from FA3/48 to VLAN 111"
your icmp connectivity test which is successful from the core is sourced from what interface?
Do you have auto summerisation enabled on the eigrp process? Is the interface/subnet 192.168.2.0 being advertised towards office2
res
Paul
08-26-2014 06:26 AM
Thanks Richard & Paul. Your questions guided me to solve the problem. Our Office 1 sites were advertised as the default route only. I changed the EIGRP to advertise the individual routes which then properly propagated through all the way to our VPN routers.
08-26-2014 07:38 AM
I am glad that you were able to solve your problem and that our suggestions did help to guide you to find the solution. Thank you for using the rating system to mark this question as answered. That will help to identify for other readers of the forum that helpful information is found in this thread.
HTH
Rick
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide