Can't browse to internal website nor internet after ISP failover

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2016 09:57 AM - edited 03-05-2019 03:03 AM
Good morning all,
I connected two remote sites via Metro Ethernet and run IBGP through it. These remote routers are 2921 routers.
Each site has its own L3 MPLS connection back to data center, which in turn directs internet traffic out its ASA.
After I shut down L3 link at one of the site, the EBGP and IBGP convert with no problem, no RIP failure. From the remote router with failed L3 link, I can ping back to data center and internet. I can even traceroute to my PC at the data center and 8.8.8.8, no problem whatsoever.
However, when I use a PC at the remote location with failed L3 link, I can't browse internet nor internal website. It's so strange. DNS server is still the same as before the link failover. there is not ACL blocking http or https along the path. I can ping DNS server also.
This confuses me greatly.
Thank you so much for your help in advance!!!
Ben Washington
- Labels:
-
Other Routing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2016 11:48 PM
I'm guessing the ping you are doing is from the routers nearest interface not from the lan interface, and if it was it would fail. I am also guessing the lan subnet is not being redistributed when the failure happens.
When you do a traceroute from a PC during the failure where does it stop? The problem is at the hop after where it is stopping.
