When choosing enterprise NVMe storage for servers and data centers, two form factors are commonly discussed today: U.2 and E3.S. Although both are designed for high-performance and high-reliability workloads, they differ significantly in physical design, scalability, cooling, and long-term viability.
This article explains the key differences in a practical and easy-to-understand way.
When designing a modern data center network, a very common architecture today is L3 underlay + VXLAN overlay + EVPN.
Sooner or later, however, the following question comes up:
Do I really need EVPN L3 routing (L3 VNI) if I only need Layer 2 connectivity over a Layer 3 network?
The short answer is: no, you don’t.
The longer and more important answer is when it makes sense and when it doesn’t.
That’s exactly what this article explains.
If you have ever built or operated a real network, you already know the problem: networking is often the last part of the infrastructure that still relies on manual work, device-by-device configuration, and vendor-specific CLI syntax. While compute and storage moved towards automation and declarative management years ago, networking often lags behind.
Here are two introductions videos ...
In this post, I want to briefly introduce Netris and explain why it is interesting from the perspective of modern, automation-driven environments.
The term “FRR router” appears frequently in enterprise, datacenter, and ISP networking discussions. Despite how it sounds, it is not a product name and not a hardware device.
Free Range Routing (FRR) is an open-source routing software suite. The name Free Range reflects its original goal: routing software that is free, open, flexible, and not tied to proprietary hardware.
FRR provides implementations of major dynamic routing protocols and runs on general-purpose operating systems such as Linux and FreeBSD.
