Cumulus Linux architecture

Issue link: https://read.uberflip.com/i/1114282

Contents of this Issue


Page 0 of 3

Understanding the architecture of Cumulus Linux CUMULUS LINUX — ARCHITECTURE To best understand Cumulus Linux and how it fits into your network, it's important to understand the basic components and foundation of a network. At their heart, all networking stacks all have the same components. In the past (think 1990s), traditional networking software had all of these components wrapped up as a monolithic single-threaded binary. Since then, computer science, hardware components, Linux and the management CPUs have advanced to the point where the heart of each layer is pretty easy to see in a given system. There may be blurring where the lines are drawn, how each element is built, etc., but in the end, these components all exist. We'll focus on definitions that relate to a hardware-based switch/router, but the elements still exist in a software version. THE ARCHITECTURE OF A STACK Component definitions CONFIGURATION This is where you define how the system is intended to operate. What is its purpose in the network architecture? Is it a bridge or a router, does it have VLANs and/or bonds, and where are the name/ time servers? Examples of configuration mechanisms would be command line utilities (like Cumulus Networks' NCLU) configuration files or an API. NETWORK PROTOCOLS Here you can set the network to dynamically interact with peers to make sure things work smoothly. Examples of protocols include a routing protocol (or suite of them), Spanning Tree Protocol (STP), Link Aggregation Control Protocol (LACP) and Link Layer Discovery Protocol (LLDP). NETWORKING ASIC DE VICE DRIVER NE T WORK PROTOCOLS NE T WORK PROTOCOLS NE T WORK PROTOCOLS NET WORKING MODEL CONFIGUR ATION MANAGEMENT

Articles in this issue

view archives of Overview - Cumulus Linux architecture