Our head office has two GRE+IPSEC Tunnels to our data center. This is a Primary and Backup setup using EIGRP internal. The Head office connects to the spokes over MPLS using BGP. So we have 2way redistribution with filters in place. The spokes use the MPLS link to Head office as the primary connection to the Data center, however if the Primary at the HEad office fails, the spokes don't use their own local GREVPN backups we have configured due to admin distance issues obviously. The spokes also run EIGRP to the Data center and BGP into the MPLS core.
I can successfully tag routes on the backup VPN tunnel at the head office fine, however I am having a hard time carrying this tag over to the remote spokes and matching them to deny those routes from being injected into the route table. Any ideas?
Me too :D I figured it out last night. I matched the EIGRP tags I was using on the backup at the HQ site, and then tagging again with BGP community and was able to deny those routes at the spokes selectively. Thanks.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...