Building a L3-Only Data Center with Cumulus Linux
Dinesh Dutt was the guest speaker in the second Leaf-and-Spine Fabric Design session. After I explained how you can use ARP/ND information to build a layer-3-only data center fabric that still supports IP address mobility Dinesh described the details of Cumulus Linux redistribute ARP functionality and demoed how it works in a live data center.
Recent posts in the same categories
design
- EVPN Designs: EVPN EBGP over IPv4 EBGP
- EVPN Designs: EBGP Everywhere
- One-Arm Hub-and-Spoke VPN with MPLS/VPN
- EVPN Hub-and-Spoke Layer-3 VPN
- Hub-and-Spoke VPN on a Single PE-Router
- Hub-and-Spoke VPN Topology
data center
- Response: The Usability of VXLAN
- Migrating a Data Center Fabric to VXLAN
- The Mythical Use Cases: Traffic Engineering for Data Center Backups
- Video: What Is Software-Defined Data Center
- Repost: L2 Is Bad
- Path Failure Detection on Multi-Homed Servers
1. how Linux accepts two interfaces with the same IP /32 addresses? Here it's mentioned like the matter of known fact, but I still wonder, never seen it before https://support.cumulusnetworks.com/hc/en-us/articles/204339077-Redistribute-Neighbor
2. By what standard Linux will send ARP request on interface with /32 IP address? I'm talking here about Dual-connected Host configuration via the web-link I provided before. From my perspective static mac record for default gateway should be manually provisioned
Andrey