Intent-based networking is a hot new topic in the networking industry right now, but what really is intent-based networking? Watch my video to find out more.
There are a small variety of methods to implement failover of your WAN perimeter between two ISPs. In this post we’ll look at one way to accomplish this goal with a few technical requirements.
Keep in mind that there are several ways to accomplish this same goal depending on the hardware available, the flexibility of the ISPs, and the skill level or preference of the engineer.
This topology utilizes two edge routers and two ISPs instead of the single edge router design I wrote about recently (you can read that here). For this post we’re using Cisco routers, but the concepts apply universally. Our requirements are that we maintain connectivity from our inside host to the internet in the event one of the company routers fails or one of the ISPs fails. Failover and fail-back must be automatic with no manual intervention.
Check out the first Network Collective video podcast, Top 10 Ways to Break Your Network, in which experienced network engineers share their most memorable blunders and the lessons learned from them.
Here’s the website: http://thenetworkcollective.com/
The header image was used with permission from Michael Nelson who was one of the Twitter participants during the first show. Check out his site here.
No Networking Field Day would be complete without a presentation from an SD-WAN vendor. The technology is now established and maturing into a ubiquitous WAN solution across small and large enterprises alike, so at the upcoming Networking Field Day 15, I’ll be focused on how TELoIP, one of the presenters at the event, differentiates itself from its competitors.
Sometimes political, financial, or logistical hurdles determine how we solve networking problems. In these tricky situations we may not be able to solve the problem the way we’d prefer, but we still need to solve the problem.
In this post I’m going to look at how we can solve a WAN failover scenario when we have a default route learned from both of our service providers and a reachability problem via our primary ISP.
I’ve been thinking a little bit about the Amazon S3 incident. Not really the incident, actually, but the responses to it. More than once I read something along the lines of “I’m sure that guy got fired” with regard to the engineer who entered the fatal command.
Sure, that’s kind of funny for a quick tweet or in the greater context of a blog post on change control, but for me, I’m not sitting at my desk shaking my head right now. Instead, I’m reminded about the times I did the exact same thing (on a much smaller scale) and will probably do it again.
Cisco’s DMVPN Phase 3 protocol offers many benefits, but make sure you evaluate options before using OSPF. Read the rest of the article at Tech Target’s SearchNetworking site.
Here’s a list of carefully thought-out pairings of songs for specific types of network activities like cutovers, refresh projects, and typical pain-in-the-butt network tasks.
Click on the network-y activity to listen, and make sure to have your sound at a decent volume. Most of these tasks take longer than the length of one typical song, so usually I’m listening to the entire album.
Tap everywhere. Tap everything. Trustworthy visibility is the key to network monitoring and security.
Apstra, Incorporated isn’t focused on new features, more advanced silicon, or some new widget. Instead, they’re offering a different way to look at networking. Apstra offers an early form of intent-driven networking that abstracts network programmability and allows network engineers to configure intent rather than device features. We expect the network to behave in a specific way, so we configure our intent accordingly. I was very excited to meet the Apstra team at Networking Field Day 13, and they didn’t disappoint.
It looks like we’re going to have some SD-WAN goodness next week at Networking Field Day 13. I love the technology itself because of the real-world use case and practical benefits a good SD-WAN solution can offer. Many of the SDN-labeled offerings out there are still a little immature, but adding intelligence to the WAN edge is something that is already being adopted wholeheartedly in even small enterprises.
In a couple weeks I’ll be headed to sunny San Jose for Networking Field Day 13. If you’re not familiar with Networking Field Day and other Field Day events, check out their website, YouTube channel, Twitter feed, and LinkedIn page. Tech Field Day does a great job bringing technology influencers, bloggers, and craft beer enthusiasts together with some of the biggest and newest names in the tech industry.
I’m particularly interested in Apstra’s presentation on Thursday afternoon. I recently wrote an article about intent-driven networking, something of particular interest to me, so I’m really interested to hear what they have to say about their platform, the Apstra Operating System, or AOS.
There’s a new story being told in the networking industry. The CCIE isn’t what it used to be, and pursuing it doesn’t make as much sense as in years past. My initial response to this is simple: BALONEY.
Over the last few weeks I’ve noticed a few tweets and blog posts regarding the immaturity of network automation methods and the danger in utilizing those methods in production networks. Though I agree that processes always have room to mature and that wiggling wires in a production environment always poses some risk, I believe this new emerging narrative in social media makes several assumptions that aren’t necessarily true.
Getting the job done, whether blog-worthy or not, always gave me a deep sense of accomplishment in my work. Besides, it’s always the junior engineers cutting over IDFs in the middle of the night that get to expense all the pizza they want.
Why aren’t our wired LANs more like WLANs? Wireless vendors have already been doing for years what switch manufacturers are only starting to get into in the last couple years. A rough comparison of a few attributes of typical wired and wireless networks shows striking differences in how we manage our LANs and WLANs.
We don’t think in five paragraph essays. At least I don’t. We think in small explosions of ideas in a nebulous, non-linear cloud of word pictures. It makes sense in our own minds, but try to communicate those ideas to someone else, and we find that sometimes we don’t have as clear a picture of our own ideas as we thought we did.
Network engineers like redundancy. It’s not that we just want double of everything – we want the networks we design and manage to be super fast, super smart, and super resilient. In the LAN and in the data center we’ve been logically joining network switches using technologies such as Cisco StackWise, the Virtual Switching System and Virtual Port Channels with fabric extenders in order to consolidate control and data plane activities and provide greater fault tolerance, easier management and multichassis etherchannel for path redundancy. These are great benefits, but they can be reaped only by proper design. Otherwise, an engineer may introduce more risk into the network rather than make it more resilient.