Because they help decipher the operation of ifupdown2, frr, and other routing tools.
- Interface Configuration and Management
- Ethernet Virtual Private Network - EVPN
- Management VRF
- Virtual Router Redundancy - VRR
- Data Center Host to ToR Architecture
- Power over Ethernet - PoE
- Network Virtualization
- Redistribute Neighbor - uses ifplugd
- Equal Cost Multipath Load Sharing - Hardware ECMP
- Segment Routing
- VLAN-aware Bridge Mode for Large-scale Layer 2 Environments
- Data Center Layer 2 High Availability - validated design
- VXLAN Routing - probably associated with FRR symmetric,asymmetric routing
Third party blogs:
- BGP in EVPN-Based Data Center Fabrics - implies that EVPN with eBGP may not 'work out of the box', but seems to be functioning just fine with my implementation of Linux kernel 4.8/4.14, Free Range Routing 4.0.
- Layer 3 Leaf/Spine Fabric with EVPN / VXLAN control - with a note about using the "Common Spine ASN – Discrete Leaf ASN", with eBGP, which results in inherent ECMP (Equal Cost Multi Path) routing. (made possible with FRRouting as the underlying routing engine).
- VRF for Linux where David Ahearn discusses the rationale for adding VRF to the Linux kernel. There is also an entry about listening on ports in a VRF: "gives users and architects a choice: bind a socket per VRF or use a ‘VRF any’ socket. "
- Ifupdown2: Network Interface Manager slideshare from DebConf16, with a discussion of ifquery, policy manager, vrf, ...
- Using the Linux VRF Solution - comprehensive slide deck by David Ahearn on using VRF in Linux: systemd, iproute2, ifupdown2, ...
- Microservice Networking - Leveraging VRF on the host - another David Ahearn slide deck - discusses the use of /32 addresses in a container