Enterprise IP Routing Best Practices
What motivated me to write this post is a state of the IP routing of some of the enterprise networks I’ve seen.
A quick show ip route command reveals a non-disentanglable mixture of dynamic and static route with multiple points of redistribution and complex,
rigid filtering rules, something you’d only see in your bad dream or a CCIE-level lab. It certainly takes
a good engineer to understand how it works and even that can take up to several hours. I think the reason for that
is that people have generally been concentrated on learning about the routing protocol, how it works, all the knobs you can twist
to influence a routing decision logic. However, one thing often overlooked is the routing protocols best practice design,
i.e. when and how to use a particular protocol.
And since the latter is often an acquired skill, a lot of not-so-lucky engineers end up with wrong ideas and concepts
in the heads. Below I’ll try to list what I{:.underline} consider a best practice design of today’s enterprise networks.
Cisco-Piston, IBM-Blue Box, Oracle-Nebula. It's a busy day in OpenStack Land.
Learn how to have business continuity during significant business disruptions. Sign up now for the Sonus DemoFriday!