I’m doing a series of three master classes through Juniper on various DC fabric topics—
Join Juniper’s Russ White, a widely published 30-year network engineering veteran, in a three-part masterclass exploring the data center. Choose from classes on data center fabric, physical topologies, or data center security.
From the schedule—
- Class 1: Data Center Fabric, December 2, 12 PM EST
- Class 2: Physical Topologies, January 13, 12 PM EST
- Class 3: Security in the Data Center, February 10, 12 PM EST
The commodification of networks is in full swing and everyone seems to think it is a good thing. You might hear this phrased as treating network devices like cattle, rather than pets. Or maybe you’ve heard that the network should move packets and do nothing more. Even, perhaps, that network bandwidth should be treated just like memory—you just add more when you need it.
If you don’t normally read IPJ, you should. Melchoir and I have an article up in the latest edition on link state in DC fabrics.
To make a case for linkstate protocols in DC fabric underlays, an extensive examination of the positive and negative aspects of BGP—and the other available protocols—is essential. Ultimately, it is up to individual operators to decide which protocol is “the best” for their application, a decision based on business and operational—as well as technical—reasons.
Did you know that today Video, gaming and social media account for almost 80% of the world’s internet traffic? The change in the composition of traffic has been accompanied by a dramatic change in the way content is delivered to the internet user: ISPs and transit providers have diminished in number and importance as the power and profile of a few Content Distribution Networks has increased as content is being pushed closer to the edge. But isn’t that just competition at work? What are the long-term consequences of such a change? In the second episode of our three-part series on “Internet Consolidation”, we talk to Russ White, co-host of The History of Networking and The Hedge podcast and a distinguished infrastructure architect and internet transit and routing expert.
Every old idea will be proposed again with a different name and a different presentation, regardless of whether it works. In other words, the present and future might not repeat the past, but it will certainly rhyme. The number of times this has happened in the world of networking technology is almost beyond counting—mostly because there are only a few real problems to solve in every area of networks, and there are only a few real solutions to those problems.
You might have seen, in the recent pandemic, advertisements for masks where “one size fits all.” You might see the same sort of thing for gloves, or maybe even flip-flops—but what you will rarely find, in the networking world, is anything that fits all. It is, in fact, challenging to explain the plethora of protocols designed and deployed by the networking community to solve any possible problem.
Everyone is aware that it always takes longer to find a problem in a network than it should. Moving through the troubleshooting process often feels like swimming in molasses—you’re pulling hard, and progress is being made, but never fast enough or far enough to get the application back up and running before that crucial deadline. The “swimming in molasses effect” doesn’t end when the problem is found either—repairing the problem requires juggling a thousand variables, most of which are unknown, combined with the wit and sagacity of a soothsayer to work with vendors, code releases, and unintended consequences.