We have a VPN with a hub router and 30+ remote sites. These are partner sites so standard IPSec (not GRE) with no routing protocol. Routing is done by static routes.
Recently one partner wants ISDN backup. We decided to use Object Tracking and we configured this on the remote partner router to ?track? the public IP address of our Hub VPN router. This works fine and fails over to ISDN when the DSL circuit fails or the route is lost to the tracked address. The ISDN comes up ok but the Hub router cannot route back to the remote subnet (192.168.42.0 /24) as it uses a Default route (0.0.0.0) which points via it?s ISP router ? so all traffic still routes this way.
We?ve tried adding various static?s by specifying the interface etc. and changing distance but with no success.
Can anyone offer any advice as to how we configure a route to 192.168.42.0 (remote LAN subnet)on our Hub router so that it routes over the Dialer99 interface ONLY when the ISDN is active. When the ISDN is down all traffic should just go via the default route via the ISP.?
Relevant config bits as follows:
HUB ROUTER ISDN config for Partner site
description PARTNER-1 ISDN Backup
ip address 10.10.10.1 255.255.255.252 (example)
ip route 0.0.0.0 0.0.0.0 126.96.36.199 (default route on Hub via ISP router)
PARTNER-1 REMOTE ROUTER
description ISDN Backup Link to HUB
ip address 10.10.10.2 255.255.255.252 (example)
ip local policy route-map ROUTING-POLICY
ip route 0.0.0.0 0.0.0.0 Dialer0 track 123 (DSL interface)
ip route 0.0.0.0 0.0.0.0 Dialer2 254 (ISDN interface)
As can be seen above, the Hub router has only a Default route so sends traffic this way all the time. We need to know how we can specify a route to 192.168.42.0 to be used ONLY when the ISDN is active on the Hub router.?
1. Configure a static route to 192.168.42.0 to point to 188.8.131.52 and track the DSL IP address of the remote site in the same statement. If the DSL IP becomes unreachable the router should remove the route to 192.168.42.0 via 184.108.40.206.
2. Configure a floating static route (with a admin distance of 200) for network 192.168.42.0 to point to the next hop via ISDN or Dialer2 interface.
You would only specify the tracking object # in the static route. The tracked object configuration is done separately in the global configuration mode and that's where you would specify the remote DSL IP address to be polled.
Check the following link that lists the configuration procedure and contains a good number of examples.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...