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.
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.
I’m lucky enough to be heading to Cisco Live in San Diego this year to host customers from my area. When I’m not with a customer during the day I plan on attending these sessions:
My main themes for picking sessions were industrial connectivity (due to the customer base I cover) and cyber security with a sprinkling of strategically chosen sessions to fill the gaps.
I plan on blogging my notes from each session soon after the session ends. Continue reading
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!
Introduction to the Physical Diagram This article is a quick tutorial for creating and maintaining a physical network diagram. I prefer to use the term “physical” instead of “L1″ because it is more easily understood by somebody unfamiliar with the OSI model. It also removes the assumption (made by many non-technical people) that “L1″ and […]
The post Network Documentation Series: Physical Diagram appeared first on Packet Pushers Podcast and was written by John W Kerns.
This post is the first in a series of articles tackling the topic of creating and maintaining proper network documentation. Each article will include a file which can be downloaded and used as a template for creating the document covered. Below you will find a few generic documentation best practices which apply to all documents […]
The post Network Documentation Series: Preamble appeared first on Packet Pushers Podcast and was written by John W Kerns.