My first reaction was to say that there is not enough information here for us to give you good advice. For example you mention the possibility of BGP advertising it. But you give us zero information about BGP.
Then I read a bit more closely and realize that we can give you some advice - the static route that you suggest is a big mistake. Taking R1 as an example - 10.70.100.0 may be the LAN on the other side, but it also contains the tunnel destination. And your static route to that subnet uses the tunnel peer address as the next hop. You absolutely do not want to have a route to the tunnel destination using the tunnel peer as the next hop. If you do configure this the tunnel will not come up and there will be error messages about recursive routing. The tunnel destination needs to be reachable via something other than the tunnel.
Same issue on the R2 side.
So change the static routes. And if you give us more information about the environment perhaps we can give you some helpful advice.
Ok so all these routers belong to a MPLS cloud. There are lets say 20 sites total that were company A, now 10 sites were purchased by company B. Company A and Company B have overlapping subnets which causes an issue when company B needs to access services for Company B. So what we decided to do was create static GRE tunnels between the 10 sites and the main Datacenter that has a Point to Point ASA VPN at it. So we are tunneling the required routes to the datacenter then over the point to point. All sites are parcipating in PE and CE BGP peering and advertising their local routes. At each of the 10 sites, not including the datacenter, I have put in static routes to all company B subnets in each router with a gateway of the datacenter router tunnel interface.
Then on datacenter router I have a static route to each of the 10 sites with the opposite tunnel IP. Does this make sense?
I have got to admit that right now it does not make much sense.
Will BGP be running over these tunnels?
Being confused about the topology and the requirements, I will offer this suggestion. The first thing that I would suggest would be that the tunnel destination probably should not be in the LAN of the remote site. Some times the tunnel destination might be a loopback at the remote site, or it might be the address of the WAN interface at the retmote site. In either case you can have a route to the remote LAN go over the tunnel without causing the recursive issue.
Sets say Company A Site 1 has a subnet of 10.32.0.0/16
Company B has the same subnet over the point to point VPN tunnel back at the datacenter.
NAT Is not an option because of DNS.
So Company B Site 1 on the same MPLS as Company A Site 1 needs to get to a webpage at 10.32.1.11, but Company B Site 1 will go to Company A Site 1 for this as its advertising it is 10.32.0.0/16
Now at the datacenter router I have a static that says to get to 10.32.1.0/24 next hop is the internal ASA of the Datacenter. Now how do I get all my 10 sites belonging to Company B to across the tunnel? Well I can redistribute my statics into BGP, but then any other Company A site needing to get to 10.32.0.0/16 will route to me...cant have that.
Being that ALL sites for both Company A and Company B in the same MPLS VPN/VRF, it becomes an issue.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...