I have a private MPLS network with Verizon that connects my 6 offices. My routers communicate using BGP and everything has worked fine for years. I'm not a router expert so please bear with me.
Recently Verizon added some fiber connections to 3 of my branch offices. These will replace the current copper lines. So I plugged these new circuits into a different interface and added in the new BGP neighbor.
I can do an extended traceroute from new interface here to the new interface at a branch office and that works fine. When I shutdown my current WAN interface nothing works. I cant connect to my branch offices. Any ideas? Here is the BGP part of my config.
When you shutdown your current WAN interface through which interface do packets travel?
My suggestion is to compare the BGP table and the Routing table, because you might have addresses to reach outside on the BGP table perspective but not on your Routing table.
A known issue is that the addresses found on the Enterprise-Internet connected routers when announcing the BGP routes have the next hop address as the ID of the ISP router and your internal routers do not have a way of reaching them, therefore you would need to use the command neighbor xx next-hop-self to advertise those routes with the ID of your local router.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.