Dynamic routing best practices

Started by Dieselboy, October 17, 2018, 10:39:47 PM

Previous topic - Next topic

Dieselboy

Are there any short-hand notes on how best to establish and run your dynamic routing protocols?

icecream-guy

Quote from: Dieselboy on October 17, 2018, 10:39:47 PM
Are there any short-hand notes on how best to establish and run your dynamic routing protocols?

use routing protocols not routed protocols  :XD:
use authentication when applicable
set peers manually if possible
don't use RIPv1
think about growth, future, and interoperability when choosing routing protocol.
( i.e. don't put everything in OSPF area 0)
summarize where possible.
if you do choose OSPF, think about where exactly the DR and BDR should exist. (unless setting peers manually)
borders? plan for redistribution
:professorcat:

My Moral Fibers have been cut.

Otanx

To add to Ristau's list

BCP38. Link - https://tools.ietf.org/html/bcp38
Review default timers. They may not need to be changed, but understand their impact on fail over
Use BFD if supported.
passive-interface default
don't use EIGRP. This falls under the future growth. Use OSPF so you don't need to deal with redistribution later.
Pay attention to licensing. I got bit in our new install that 3850s only support 200 OSPF entries with IPBase. This is fine at the Access layer where you summarize. Not so good at your WAN aggregation. The license to extend that limit costs as much as the switch.

-Otanx



Dieselboy

Thanks, very helpful. Looking at utilising bgp for site to site VPNs and havent set up dynamic routing in a little while and wanted to brush up.

That book looks good, but it's static  :XD: :mrgreen: