As I mentioned, Blake was helping me work on this failover scenario.
Good news is we were able to get it working using RSTP and EoIP tunnels
as alternate paths. I've included the original email below for reference
of the environment.
If anyone is interested in more detail on the nuts and bolts, let me
know and I will share the config. Big thanks to Blake for his help!
Rory McCann
*Minn-Kota Ag Products
P*: 701-403-4877*| E*: [email protected]
On 8/29/2011 3:34 PM, Rory McCann wrote:
Hey everyone,
I have a failover question that I'm hoping you all might be able to
offer some input on. I'll do my best to explain the setup/scenario and
make it as clear as possible.
We have several physical locations for our company, all connected via
wireless links and all on the same layer 2 network. I have one
location in particular that is a longer shot (26 miles) that will
sometimes drop due to bad weather. I want to provide a failover
solution for this site using an EoIP tunnel and a second internet
connection (this is in place and has been working. We recently hooked
them back up to wireless but they were connected to the rest of the
company over the EoIP tunnel for several months). I do not need
instant failover, but I'd like something that automatically fails over
to the EoIP tunnel in the event the wireless drops and automatically
fails back when the link comes back up. Failover time should be under
5 minutes, but doesn't need to be any less than 2-3 mins. I just want
to make sure they aren't dead in the water if the wireless fails and
they can't work.
Secondly, I want to use that internet connection as a failover
internet connection in the event our primary internet dies. I'm not
concerned about WAN-side IP addressing - just want people to continue
to be able to browse the web in the event of a failure.
These two routers only have 1 direct point of connection (the internet
/ EoIP tunnel). The wireless link is at another location connected via
fiber so I have no way to directly connect the wireless to the other
router - I think that would rule out something like OSPF but I am not
sure.
I'm wondering if for my link failover, since the EoIP tunnel and the
interface with the wireless are on the same bridged interface at the
far end, can I simply use path cost to avoid a bridge loop? I'm
assuming I could also do a netwatch type of script to add/remove the
interfaces from the bridge as necessary, but my scripting experience
is very limited.
Second - my WAN failover - what would be the best method of doing
this? Should I have my DHCP server assign two default gateways and let
the computers sort it out, or is there something like VRRP that I
could implement at layer two with limited complexity (I want something
that simply hands off NAT to the other router in the event of a
failover - ideally switching it back when the primary connection comes
back online).
I hope I've explained things but I can provide a diagram or more info
as needed. Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.butchevans.com/pipermail/mikrotik/attachments/20110910/82217180/attachment.html>
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
