We have several routers around the world connected to a VLPS cloud. We want to backhaul the traffic, Inet and private, for some of the smaller sites through other larger sites. These smaller sites usually have an internal routing switch connected to the VPLS router and to a router we're running GRE tunnels back to the corporate HQ. The primary routers are the VPLS and the GRE routers are for redundancy. We're using EIGRP for routing. Some of the routers are IOS 15.0 and some are on 12.4.
We want the routing to automatically switch to the GRE routers when there is a VPLS circuit outage.
We have a site that has that working, the VPLS router at the site, Stanford Connecitcut, gets a default route pointing to the HQ VPLS router, Mason Ohio, and if that site's circuit goes down the EIGRP reroutes through the GRE router.
The problem is, we have a site, Sydney AU, that needs to backhaul through a large site, Melbourne AU. The Sydney router currently gets a default route back to the Mason VPLS router, so we have a static default route pointing to the Melborne VPLS router. We need to be able to get a default route pointing to the Melbourne VPLS router instead of the static route.
Is there a way to do that, like filtering the incoming router protocol? and am I right in thinking the default route being advertised is the HQ VPLS router because it has the smallest EIGRP router ID? Can you force a default route advertisement from a particular router to a particular router?
ausyd-coresw can run EIGRP ?
if possible I would run EIGRP over it
it it cannot be done for license problems or because ausyd-coresw is non cisco you can:
run an OSPF process on ausyd-coresw and R2, R3 with R2 advertising a default route only if it is receiving it from R1 on the VPLS cloud, R3 will generate a worse default route that is not used until R2 generates its own
OR you can use IP SLA to track reachability or R1's ip address on the VPLS cloud: until this IP address is reachable primary default route towards R2 is considered valid if it fails the primary static default route is removed from IP routing table on ausyd-coresw and the secondary floating static route is used, the one pointing to R3.
This is more near to your current setup but you need to check if ausyd-coresw operating system allows to do this
for reliable static routes with object tracking see the following document:
OR you can add a link between R2 and R3 so that R2 can use R3 to reach everything when VPLS is down, you can use a vlan for which the switch ausyd-coresw acts only as a L2 switch ( non SVI on it)
Hope to help