The Default Topology that routes traffic out to the Internet
Hello Everyone, I'm helping someone in the community and I'm going to share my Router 1 config so that users that want to routeEnterprise 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.
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.
GNS3 Weekly Development Report: June 1th
We publish weekly development reports in an effort to provide the community with increased transparency on what the development team isMy CLUS 2015 Schedule
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:
Monday
- Coding 101: How to Call REST APIs from a REST Client and Python
- IoT Solutions – Connecting Oil and Gas Pipelines
- An IoT Security Model & Architecture for Securing Cyber-Physical and IT-OT Converged Assets
- Keynote
Tuesday
- APIC-EM: Controller Workload and Use Cases
- Designing for the Secure Convergence of Enterprise and Process Control Networks
- Emerging Threats – The State of Cyber Security
Wednesday
- IWAN Customer Case Study
- Industrial Keynote – IoE and the IT Mindset Shift – The Evolution of the IT Career
- Ethernet Evolving – Ethernet at New Speeds, Deterministic Networking, and Power over Everything!
- Advanced Malware Protection
Thursday
- Snort Implementation in Cisco Products
- Cloud Consumption in North America
- No Lights, No Power, No Service? – Defending IoT
- Closing Keynote
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
The White Box SDN Twitter 45
With SDN and White Box news flying fast and furious through the Internet, it can be hard to keep up with really great articles. Twitter isCisco, IBM & Oracle Go on an OpenStack Shopping Spree
Cisco-Piston, IBM-Blue Box, Oracle-Nebula. It's a busy day in OpenStack Land.
Registration is Open for the Sonus DemoFriday: The Impact of SDN on Business Continuity
Learn how to have business continuity during significant business disruptions. Sign up now for the Sonus DemoFriday!
Network Documentation Series: Physical Diagram
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 […]
Author information
The post Network Documentation Series: Physical Diagram appeared first on Packet Pushers Podcast and was written by John W Kerns.