Broadcom announced their new SDKLT, a logical table-based API for programming Tomahawk switches. But why is this new idea so important? Tom Hollingsworth looks at the impact of both the new data structures and open source release and why it matters to network programmers.
Intent-based networking is the new hotness, but what does it actually mean? In this episode, the panel discusses how it differs from older SDN ideas. IBN integrates an abstraction layer and orchestration into a system that identifies a single source of truth that isn’t the network itself.
On this episode, we’ll be talking about a hot topic in the networking space, automation. The panel discusses why organizations see automation as prohibitively complex, what exactly they mean by automation, and why it isn’t coming for their jobs.
With all the expectations and hype that surround software-defined networkings, it’s easy to get a little jaded. But that misses the massive impact it’s had for enterprise networks. In this piece, Tom Hollingsworth rightly points out that this programmability is no longer a new feature that network engineers are excited about. Instead, it’s become a staple of the modern data center, one that increasingly organizations depend on.
When I first saw the Aruba 8400 I was awestruck, surprised, actually legitimately excited! I know, I know it’s just a bunch of ports inside of a chassis, but that’s not all it was though. The 8400 brought something to the party which has been forlorn and forgotten in the systemic world of Network Engineering and Administration, and that is they realized the end-users of this product WERE Network Engineers and Administrators. But wait, what do I mean by that?
On this iteration of the Gestalt IT Networking News:
– Discussing Intel and NFV on our new podcast, the On-Premise IT Roundtable
– TELoIP tries to shake up the same old SD-WAN recipe
– An in-depth look at TCP terminator
Plus looks a VMware NSX, the future of SDN, and trying to find out who moved Jordan Martin’s Control Plane!
Jordan Martin has a problem. The idea of moving the control plane from a device to a central controller sounds like it makes a lot of sense in SDN. I mean, it’s called a control plane, why not move it to a controller? Despite the phonic similarity, this isn’t actually what happens.
The big problem with a DDoS, especially one like Mirai, is how to discern real users in all that volume. If you simply “cut the hardline” and shut the network off, the DDoS was effectively successful, bringing you offline and disrupting business. Mirai made this particularly difficult, with it’s glut of IoT devices directed at the target. An effective solution needs to be able to keep your network running, and identify legitimate traffic from the noise. Enter Big Switch Networks’ BigSecure Architecture.
Software Defined Networking (SDN) is a paradigm shift. But it has been looking for a real use-case for the technology that combines increased software function, analytics, and unprecedented control over hardware resources. Automation and orchestration certainly show off the potential of the technology, but something more concrete is necessary to make it hit home with engineers and architects. That’s where Software Defined WAN (SD-WAN) comes into play.
Whenever I visualized SD-WAN, it always seemed like it would have to be a relatively top-down solution. A lot of what I’ve seen in the category certainly seems to shift this way, with SD-WAN companies working with service provides to implement their solutions. There’s nothing wrong with this approach, as long as it delivers the intended functionality.