Does a pre-sales engineer need to have strong implementation experience to be good at their job?
Whitebox switches make use of generic and generally inexpensive hardware along with a network operating system that can be purchased and installed separately. Often the hardware and software come from different vendors, and there are several reasons this practice is becoming more common especially in the data center. What I’m interested in lately is how this is relevant to the non-webscale enterprise.
If you haven’t heard, the networking community is awesome. I’ve made some great friends, developed strong new relationships, and I’ve had the incredible luxury to bounce ideas off some seriously talented people. However, whether it’s through various Slack groups, Google hangouts, or private email chains, it’s all been relatively private. Not much makes its way onto Twitter, and not as much as I’d like makes it into blog posts.
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.
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.
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.