![]() The specific connectivity is in the overview drawing below. 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. This was tested under a 25 Gbps load on both routers with a cpu load of 12%. TLDR 2.1 million routes learned and forwarding in 46 seconds and withdrawn in 44 seconds. Hope this is helpful and look for more BGP perf tests in the coming months! 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. ![]() 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. One of the long-awaited features is improved BGP performance and the ability to leverage multiple CPU cores. MikroTik has come a long way since the first release of RouterOS v7 beta. The most common use case among MikroTik users is more efficient subnetting of IPv4 and directly replaces LDPv4 for this Continue readingĠ MikroTik – RouterOS v7 – BGP performance testing for full tables It generally operates in much the same way as LDPv4. LDPv6 is defined by RFC 7552 and is fairly recent as it finalized in 2015. While I generally am in favor of SR-MPLS/SRv6 long term due to the protocol simplification and traffic management capabilities, having an IPv6 MPLS stack is a great starting point for MikroTik. SR-MPLS (less common and usually with IS-IS) and SRv6 are the other options besides LDPv6. There are a few different ways to distribute labels in IPv6 MPLS. Single stack networks are easier and cheaper to operate in the long run and are a natural evolution of dual stack networks as we begin to turn IPv4 off for underlay infrastructure. However, single stack networks with IPv4 as a service overlay are definitely on the horizon for MikroTik users now that MPLS can operate purely on IPv6. Dual stack networks are still the most common and easiest to initially deploy for carriers. IPv6 adoption has really picked up in the last 12 months and MikroTik RouterOSv7 development is no exception. ![]() “I can’t afford Cisco or Juniper but I need a network that’s highly available and resilient”Ĭoming from a telco background where a large chassis was used pretty much everywhere for redundancy and relying on links split across multiple line cards with LACP, that was one of my first inclinations to solve the Continue readingĠ MikroTik – ROSv7 – VPLS over IPv6 MPLS with LDPv6 “I have high CPU on my router and I don’t know how to add capacity and split the traffic” “I started with a single router, how do I make it redundant and keep NAT/peering working properly”? “ I’m out of ports on my router…how do I add more?” While the idea of “router on a stick” isn’t new, when we first started working with WISPs/FISPs and MikroTik routers 10+ years ago, we immediately noticed a few common elements in the requests we’d get for consulting: In the last decade, the work that we have done at with WISPs/FISPs in network design using commodity equipment like MikroTik and FiberStore has yielded quite a few best practices and lessons learned. This is an article i’ve wanted to write for a long time. 0 WISP/FISP Design: Switch Centric (SWC) Topology IP ArchiTechs switch centric core being built in the Denver DC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |