11-04-2009 11:13 AM - edited 03-06-2019 08:26 AM
Looking for hardware solution and software solution.
Internal IP 10.10.10.x
Customer has 1 pt-2-pt and 1 DSL connection.
Pt-2-Pt connection is the path to all of the Email Servers and File Servers on the other end
The New DSL connection they want to use for internet but want the Pt-to-Pt if the DSL drops... this part no problem - DSL would be Default route and Pt-to-Pt secondary route.
If I make the DSL the primary what do I have to do to make sure that users can still access the Servers on the other end of the Pt-2-Pt? Other end of Pt-2-Pt sitll in the 10.10.10.x network.
I say
0.0.0.0 0.0.0.0 DSL Connection
** what about 2nd route
** what about routes to servers on the other side of Pt-2-Pt.
11-04-2009 11:38 AM
2nd route:
You can use a floating static route:
ip route 0.0.0.0 0.0.0.0 [IP of OTHER end of PTP] 250
The floating static ONLY works if the actual interface goes down, it does not account for upstream failures.
If you want to account for upstream failures, you can use an IP SLA and use a tracked object. You can set the IP SLA to ping an IP on the internet, if the IP is unreachable, remove that route and use the other one.
Example:
ip sla 190
icmp-echo 4.2.2.2 source-interface [DSL interface]
frequency 30 {pings every 30 seconds}
ip sla schedule 190 life forever start-time now
track 190 ip sla 190 reachability
ip route 0.0.0.0 0.0.0.0 [DSL IP] track 190
ip route 0.0.0.0 0.0.0.0 [IP of OTHER end of PTP] 250
The example creates an SLA that pings 4.2.2.2 every 30 seconds from the DSL internface. You then create a tracking object to keep track of the state of the SLA and link it to the static route. If the tracked object is in the "DOWN" state, the route that's linked to the tracked object is removed from the routing table and the floating static is put in.
Once the IP is reachable again, the route would go back to the DSL connection automatically. You still need the floating static route as well.
Other routes:
just use static routes. If for example the servers on the other side of the PTP are on the 10.1.1.x/24 network:
ip route 10.1.1.x 255.255.255.0 [IP of OTHER end of PTP]
11-04-2009 11:46 AM
Great thanks- I don't know why I put that 2nd question - I really need the the "weight" of the 2nd connection. thank you.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide