{"id":1992,"date":"2010-07-12T01:57:45","date_gmt":"2010-07-12T07:57:45","guid":{"rendered":"http:\/\/gregsowell.com\/?p=1992"},"modified":"2010-07-11T23:05:44","modified_gmt":"2010-07-12T05:05:44","slug":"mikrotik-vrrp-hardware-redundancy","status":"publish","type":"post","link":"https:\/\/gregsowell.com\/?p=1992","title":{"rendered":"Mikrotik VRRP – Hardware Redundancy"},"content":{"rendered":"

So working for a datacenter, I hear plenty of buzz words…what good sales guy doesn’t work one in every other sentence? One of those phrases you hear is “concurrently maintainable”. What does this mean? It means you can sustain loss in your infrastructure and still be up. We are talking about hardware redundancy.<\/p>\n

In our DC if you aren’t doing BGP with us, you would do well to use VRRP…what is VRRP? Here’s wikipedia’s definition<\/a>. In essence it works like such. You have two of your routers connected to the same layer 2 segment. You have a subnet configured that is \/29 or larger. You configure a physical IP on the interfaces, then you create a VRRP interface on each router associated with those connected interfaces. You then assign the same VRRP IP address on both routers to the VRRP interface.<\/p>\n

The VRRP router that has the higher priority(default is 100) is the master. The master responds to ARP requests for the VRRP IP. If the master router fails, then the backup router takes over and owns the VRRP IP. Soooo, your default gateway points towards the VRRP IP so that if the master fails and the backup takes over your default route is still valid! There is also a concept of premption. By default preemption will migrate the VRRP IP over to the router with the highest priority.<\/p>\n

Here are some examples:
\n\"\"<\/a>
\n\"\"<\/a>
\n\"\"<\/a>
\n\"\"<\/a><\/p>\n

So here’s our demo config:
\n\"\"<\/a><\/p>\n

So what happens when one of our providers fail?
\n

\"\"<\/a>
Provider fails on one link. The backup guy takes over the VRRP IP. Our default route points to 10.0.0.1 so we still route out!<\/figcaption><\/figure>
\n
\"\"<\/a>
We drop half of our network gear, but have no fear. The ISP was pointing towards 10.0.0.6 to route to me, so all is good in the hood.<\/figcaption><\/figure><\/p>\n

Router 10.0.0.4<\/strong>
\nCreate the VRRP interface *assign it higher priority – default is 100*:<\/p>\n

\/interface vrrp\r\nadd arp=enabled authentication=none comment="" disabled=no interface=ether1 \\\r\n    interval=1 mtu=1500 name=vrrp1 on-backup="" on-master="" password="" \\\r\n    preemption-mode=yes priority=150 vrid=1<\/code><\/pre>\n
Configure our IPs:<\/p>\n
\/ip address\r\nadd address=10.0.0.4\/29 broadcast=10.0.0.7 comment="" disabled=no interface=\\\r\n    ether1 network=10.0.0.0\r\nadd address=10.0.0.6\/32 broadcast=10.0.0.6 comment="" disabled=no interface=\\\r\n    vrrp1 network=10.0.0.6<\/code><\/pre>\n
Our default route:<\/p>\n
\/ip route\r\nadd comment="" disabled=no distance=1 dst-address=0.0.0.0\/0 gateway=10.0.0.1 \\\r\n    scope=30 target-scope=10<\/code><\/pre>\n
Router 10.0.0.5<\/strong>
\nCreate the VRRP interface:<\/p>\n
\/interface vrrp\r\nadd arp=enabled authentication=none comment="" disabled=no interface=ether1 \\\r\n    interval=1 mtu=1500 name=vrrp1 on-backup="" on-master="" password="" \\\r\n    preemption-mode=yes priority=100 vrid=1<\/code><\/pre>\n
Configure our IPs:<\/p>\n
\/ip address\r\nadd address=10.0.0.5\/29 broadcast=10.0.0.7 comment="" disabled=no interface=\\\r\n    ether1 network=10.0.0.0\r\nadd address=10.0.0.6\/32 broadcast=10.0.0.6 comment="" disabled=no interface=\\\r\n    vrrp1 network=10.0.0.6<\/code><\/pre>\n
Our default route:<\/p>\n
\/ip route\r\nadd comment="" disabled=no distance=1 dst-address=0.0.0.0\/0 gateway=10.0.0.1 \\\r\n    scope=30 target-scope=10<\/code><\/pre>\n
This is great for the WAN side, but is quite often used for the LAN also!
\nYou can also run two separate VRRP groups on a single interface which will allow you to load balance with redundancy.<\/p>\n
Go forth and route my peoples!<\/p>\n","protected":false},"excerpt":{"rendered":"
So working for a datacenter, I hear plenty of buzz words…what good sales guy doesn’t work one in every other sentence? One of those\u2026<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,6],"tags":[],"class_list":["post-1992","post","type-post","status-publish","format-standard","hentry","category-hardware","category-mikrotik"],"_links":{"self":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts\/1992","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1992"}],"version-history":[{"count":9,"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts\/1992\/revisions"}],"predecessor-version":[{"id":2006,"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts\/1992\/revisions\/2006"}],"wp:attachment":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1992"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1992"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1992"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}