In this post, we introduce BGP EVPN and a VXLAN fabric in Cumulus Linux, with L2VNIs.
Now that we've covered the basics of BGP unnumbered in the last post, we'll start building a VXLAN based fabric with BGP EVPN.
Our topology remains the same, with a minor change - PC2 has now been moved to the same subnet as PC1, 10.1.1.0/24:
In this post, we'll look at BGP unnumbered on Cumulus Linux.
The last post introduced basic BGP bringup on a Cumulus box with OSPF as the IGP. Let's now move towards a BGP unnumbered design and understand how that works.
We will use the same network topology as before:
The idea behind BGP unnumbered is to use the IPv6 link local addressing on hop by hop basis. When you're building a L3 fabric, what is the goal of the underlay? Outside of any multicast replication that may be required, the main goal (from a unicast perspective) is to provide connectivity from one tunnel end point to another. Typically, you would use something like OSPF or IS-IS to advertise the loopbacks of the tunnel endpoints and thus, provide connectivity from one loopback to another.
In this post, we introduce BGP on Cumulus Linux.
The goal of this post is to introduce BGP on Cumulus Linux and then move towards a BGP unnumbered design, in the following post.
We'll be using the following network topology for this post:
First, we will try to create a traditional BGP scenario with OSPF as an IGP. For now, OSPF is up and running and I have learnt the loopback of each LEAF switch.
In this post, we will look at an introduction to routing on Cumulus Linux, with static routing and OSPF.
Initially, Cumulus OS used the Quagga suite for routing capability. However, more recently, there has been a general adoption of a fork of Quagga called FRRouting (FRR) - Cumulus now includes FRR instead of Quagga. Like always, you can either edit the files directly or using Cumulus' NCLU to enable the respective routing features as well.
We'll be using the following network topology for this post:
This second blog on Cumulus looks at basic layer2 functionality in Cumulus Linux.
This post is going to introduce you to basic Layer2 functionality on the Cumulus platform. Like before, we are going to be working with Cumulus VX.
We will be using the following network topology for this post:
PC1 and PC2 are two end clients in the same Layer2 domain (VLAN 10) that want to communicate with each other.
This first blog on Cumulus introduces the reader to the basics of the operating system and Cumulus' NCLU.
This is going to be a new mini series that we will do in preparation for the first open networking certification that Cumulus Networks introduced,see here.
Cumulus Networks has a great page (both free and paid content) where you can spend some time and learn all things Cumulus and open networking related, see here.
So, where do we begin? Every time I learn a new product, I start at the start. Things we learned way back when. Because Cumulus Linux is a native Linux distribution (and it's interface may be unfamiliar to many), we'll start with some very simple aspects of working with the box - basic port bring up/down, port configurations, gathering information about a port and finally an introduction to Cumulus' NCLU!
As a reference, we'll be working on the following topology:
