This content is for Patreon subscribers of the j2 blog. Please consider becoming a Patreon subscriber for as little as $1 a month. This helps to provide higher quality content, more podcasts, and other goodies on this blog.
Category Archives: BGP
Unlock with PatreonBGP Local Pref and how it can influence traffic
This content is for Patreon subscribers of the j2 blog. Please consider becoming a Patreon subscriber for as little as $1 a month. This helps to provide higher quality content, more podcasts, and other goodies on this blog.
Hurricane Electric route table over 800,000 routes
Had a Hurricane peer without any filtering or the like reach over 800,000 routes today. As some of you may know providers do their own aggregation and such so your mileage may vary.
Need an ASN, IP space? I have a package for you.
Are you intimidated by getting an ASN to participate in BGP? Do you not have the time to learn all the ins and out of dealing with ARIN to get IP space or routing registries? Let me help you.
The ARIN starter package
-Organization ID and POC IDs setup
-Paperwork to get your own ASN
-Paperwork for your own IPV6 allocation
-Paperwork for an IPV4 /24
-ASN validation
-Documentation and maintenance documents
Cost $899 plus ARIN fees
Add Ons
-RPKI Setup $199
-Routing Registry setup $199
Add-ons are priced to add-on to the starter package. Please let me know if you need just the add-ons for a proper quote.
Cisco ORF (Outbound route filtering)
Outbound Route Filtering (ORF) is a Cisco proprietary feature that prevents the unnecessary exchanging of routes that are subject to inbound filtering. This, in turn, minimizes bandwidth across the links and reduces CPU cycles upon the router during the processing of the neighbor UPDATE.
ORF works by the router transmitting its inbound filters to its neighbor, which the neighboring router then applies outbound.
great article on how to do this if you are running Cisco routers and your provider is too.
BGP Messages
This content is for Patreon subscribers of the j2 blog. Please consider becoming a Patreon subscriber for as little as $1 a month. This helps to provide higher quality content, more podcasts, and other goodies on this blog.
EVPNs: The answer to your MPLS issues
I had a good discussion with my Buddy JJ tonight on kind of the next step of network evolution for provider networks. Many providers have evolved to MPLS networks with VPLS. There are some inherent issues with this when it comes to things like bonding, MLAG, among other issues. Nothing is perfect, right?
So as we dive into What is EVPN I want you to know I am approaching this from a service provider standpoint. I also am no EVPN expert, but I am seeing it more and more as a solution to solve specific issues. As a result, EVPN is sliding into a natural progression of the service provider network.
So what is EVPN?
There are folks much more versed on EVPN than I am. As a result, I will lean on some already written articles.
https://blog.ipspace.net/2018/05/what-is-evpn.html
https://www.cisco.com/c/en/us/products/ios-nx-os-software/ethernet-vpn.html#~stickynav=1
Components of EVPN
Now that you have a high-level overview of EVPN, what are some of the major components and features you should know? Let’s dive into that
Unified control plane. EVPN can be used throughout your network. You don’t have to use one stack for data center, one for metro to the data center, and yet another for connectivity between data centers. You can bring it all under one control roof so to speak.
EVPN, through BGP, marries the Layer 2 and Layer 3 layers together. With MPLS everything is controlled at the layer3 level. Now with EVPN Mac addresses become much more important. For example, Each EVPN MAC route announces the customer MAC address and the Ethernet segment associated with the port where the MAC was learned from and is associated MPLS label. This EVPN MPLS label is used later by remote PEs when sending traffic destined to the advertised MAC address. Pretty cool huh?
As networks grow network engineers learn about things such as north-south traffic and east-west traffic. Microsoft has a great article which explains this concept. https://blogs.technet.microsoft.com/tip_of_the_day/2016/06/29/tip-of-the-day-demystifying-software-defined-networking-terms-the-cloud-compass-sdn-data-flows/
East-West – East-West refers to traffic flows that occur between devices within a datacenter. During convergence for example, routers exchange table information to ensure they have the same information about the internetwork in which they operate. Another example are switches, which can exchange spanning-tree information to prevent network loops.
North | South – North- South refers to traffic flows into and out of the datacenter. Traffic entering the datacenter through perimeter network devices is said to be southbound. Traffic exiting via the perimeter network devices is said to be northbound.
So, if you are a growing Service provider look at EVPN. In some upcoming articles, I will talk more about various components of EVPN and such.
Route Server Diagram for an IX
Normally on a peering exchange, all connected parties will establish bilateral peering relationships with each other customer connected to the exchange. As the number of connected parties increases, it becomes increasingly more difficult to manage peering relationships with customers of the exchange.
However, by using route servers for peering relationships, the number of BGP sessions per router stays at two, if the IX has deployed redundant servers.
A secure BGP routing infrastructure using RPKI
This content is for Patreon subscribers of the j2 blog. Please consider becoming a Patreon subscriber for as little as $1 a month. This helps to provide higher quality content, more podcasts, and other goodies on this blog.
How does BGP select routes?
This content is for Patreon subscribers of the j2 blog. Please consider becoming a Patreon subscriber for as little as $1 a month. This helps to provide higher quality content, more podcasts, and other goodies on this blog.