One of the design scenarios we covered in Leaf-and-Spine Fabric Architectures webinar is a pure layer-3 data center, and in the “how do I do this” part of that section Dinesh Dutt talked about the details you need to know to get this idea implemented on Cumulus Linux.
We covered a half-dozen design scenarios in that webinar; for an even wider picture check out the new Designing and Building Data Center Fabrics online course.
 |
| Fig 1.1- VSS using SUP Engines |
Projects are the latest attempts by vendors to ease container management.
SolidFire Element OS is an integral part of NetApp HCI.
Yesterday we published a new policy brief: Spectrum Approaches for Community Networks
Access to affordable and available spectrum is critical for Community Networks. Policy makers can play a key role in ensuring adequate access to spectrum. The policy brief examines the various ways that Community Networks can gain access to spectrum, including:
Network operators also play a key role in helping Community Networks. The policy brief outlines recommendations for operators which include:
Please read our press release for more information about this new paper. Also visit our World Telecommunications Development Conference (WTDC) 2017 page for more about what our team is doing there in Buenos Aires this week.
The post New Policy Brief published on Community Networks and Access to Spectrum appeared first on Internet Society.
Part three! Let’s get straight to business and carry on where we left off from part two.
Thinking about automation in an agnostic way is your first footstep. Automation is about data flowing through building blocks that do things and decision points, allow you when to do things.
Removing CLI and replacing it with an abstraction layer isn’t much of a win. For instance, I regularly talk about the process of creating a VLAN and applying it to an Ethernet switch-port on a tagged interface. This somewhat simple ‘workflow’ creates more conversational friction than imagine-able. Let’s work through it.
Task: Create a VLAN
This task requires domain-specific parameters to a VLAN. These are: ‘VLAN_Number’ and ‘VLAN_Description’.
Task: Apply VLAN to Switchport
This task requires domain-specific parameters to a switchport. These are: ‘Port_Name’ and ‘VLAN_Number’.
Note how the inputs flow through the actions within the workflow?
The green arrows descending illustrate the ‘success transition path’ for each action component.
So, what about these questions?
1. Is the VLAN in use?
We can be more specific here, but it adds complications to the answer. Version two is: “Is the VLAN in use in the network zone that the device Continue reading
He played a key role in moving HPE into the SDN and NFV space.
On this episode of the History of Networking over at the Network Collective, we interviewed Radia Perlman about the origin of Spanning Tree. She is really delightful, and we plan on bringing her back on in the future to talk about other topics in the history of networking technology.
The post History of Networking: Radia Perlman and Spanning Tree appeared first on rule 11 reader.
Company executives had touted its cloud business as part of its Q2 results.
IT is flooded with acronyms. It takes a third of our working life to figure out what they all mean. Protocols aren’t any easier to figure out if it’s just a string of three or four letters that look vaguely like a word. Which, by the way, you should never pronounce.
But what if the acronyms of our favorite protocols didn’t describe what the designers wanted but instead described what they actually do?
Obscurity Sends Packets Flying
Expensive Invention Gets Routers Puzzled
Vexing Router Firmware
Really Intensive Protocol
Someone Doesn’t Worry About Networking
Somewhat Quixotic Language
Blame It oN DNS
Cisco’s Universal Call Misdirector
Some Mail’s Thrown Places
Mangles Packets, Looks Silly
Amazingly Convoluted Lists
ImProperly SECured
May Push Lingering Sanity To Expire
Are there any other ones you can think of? Leave it in the comments.
The data center software also integrates with Kubernetes.
The new book should be out around the 29th of December, give or take a few days. For readers interested in what Ethan and I (and Ryan, and Pete Welcher, and Jordan Martin, and Nick Russo, and… the entire list is in the front matter), the general idea is essentially grounded in RFC1925, rule 11. There is really only a moderately sized set of problems computer system needs to solve in order to carry data from one application to another. For instance, in order to transport data across a network, you need to somehow format the data so everyone can agree on how to write and read it, ensure the data is carried without errors, ensure neither the sender nor the receiver overrun or underrun one another, and find some way to allow multiple applications (hosts, etc.), to talk over the same media. These four problems have somewhat proper names, of course: marshaling, which involves dictionaries and grammars; error control; flow control; and multiplexing. So the first step in understanding network engineering is to figure out what the problems are, and how to break them apart.
Once you understand the problems, then you can start thinking about solutions. As Continue reading
Analysis of large volumes of real-time network data can help optimize network forwarding mechanisms.
Analysis of large volumes of real-time network data can help optimize network forwarding mechanisms.