MikroTik has come a long way since the first release of RouterOS v7 beta.
One of the long-awaited features is improved BGP performance and the ability to leverage multiple CPU cores.
Testing BGP performance is a long process of lab and prod evaluation, so we decided to run some quick and basic tests to get a baseline.
When the CCR2216-1G-12XS-2XQ was released and MikroTik entered the world of 100G, we ordered some right away to test and just got them in the lab a few days ago – the results are below.
Hope this is helpful and look for more BGP perf tests in the coming months!
TLDR; 2.1 million routes learned and forwarding in 46 seconds and withdrawn in 44 seconds. This was tested under a 25 Gbps load on both routers with a cpu load of 12%.
Lab overview: The lab consists of (2) CCR2216 routers running ROSv7.2 stable connected to a ProxMox hypervisor that runs (4) Linux route generators and MikroTik CHRs (also on 7.2) acting as border routers. The specific connectivity is in the overview drawing below.
IPv6: We are currently developing a route generator that will inject IPv4 Continue reading
Networking engineers proposing strict hierarchical addressing scheme as a solution to global BGP table explosion often cite the international telephone system numbering plan (E.164) as a perfect example of an addressing plan that uses hierarchy to minimize routing table sizes. Even more, widespread mobile roaming and local number portability indicate that we could solve IP mobility and multihoming if only insert-your-favorite-opinion-here.
Networking engineers proposing strict hierarchical addressing scheme as a solution to global BGP table explosion often cite the international telephone system numbering plan (E.164) as a perfect example of an addressing plan that uses hierarchy to minimize routing table sizes. Even more, widespread mobile roaming and local number portability indicate that we could solve IP mobility and multihoming if only insert-your-favorite-opinion-here.
ISDN, while an old technology, is still around in many parts of the world. When will it go away? George Michaelson joins Tom Ammon and Russ White to discuss the end of ISDN. The conversation then veers into old networking technologies, and the importance of ISDN in setting the terms and ideas we use today—ISDN is one of the key technologies around which network engineers built their mental maps of how to build and maintain networks.
This episode on Python for networking covers the lab topology we’ll be working with in VIRL, choosing a text editor, and basic lab configurations. Course files are in a GitHub repository: https://github.com/ericchou1/pp_practical_lessons_1_route_alerts Eric Chou is a network engineer with 20 years of experience, including managing networks at Amazon AWS and Microsoft Azure. He’s the founder […]
The post Practical Python For Networking: 2.1 – Lab Topology – Video appeared first on Packet Pushers.
Anyone who’s ever gone to a networking event knows that they can be exhausting. You’re constantly meeting new people, exchanging business cards, and trying to make a good impression. It’s no wonder that so many people end up burning out quickly.
The key to networking effectively is actually quite simple: getting a good night’s sleep beforehand.
Most people need around eight hours of sleep per night to function at their best. However, if you know you have an upcoming networking event, it’s important to get even more sleep than usual. Try to get at least nine or ten hours of sleep the night before. This will help ensure that you’re well-rested and won’t be as likely to feel exhausted during the event.
There are a few different things you can do to make sure you get enough sleep. First, avoid caffeine in the evening. Caffeine can stay in your system for up to eight hours, so it’s best to avoid it after lunchtime.
Second, establish a bedtime routine and stick to it as much as possible. Continue reading
Red Hat Insights is a suite of cloud services available on the Red Hat Hybrid Cloud Console, powered by an expert system that is built upon years of data collected from across Red Hat’s worldwide customer base. For Red Hat Ansible Automation Platform customers, it provides predictive analytical reporting of your Ansible automation.
This blog breaks down the new reports that analyze module usage within the Ansible Automation Platform.
In summary, module usage is really important because modules can contain security vulnerabilities and require updates to support new integrations of hardware or software. It is paramount to know which modules you are using in your automation.
Let's look at each report and what each of them can deliver for you.
Description: The number of job template and task runs, grouped by Ansible module usage.
Use Case: You can use this report to discover which modules are being used the most across your automation, helping you to check things like organization-wide adoption of purpose-built modules over potentially less performant, catch-all solutions.
Example:
This chart shows how the file and gather_facts modules are the most used, but also shows that over the past 6 Continue reading