3 Commits

Author	SHA1	Message	Date
Damien	ef4211afe5	Rename devices to <area>-<role> scheme ... DC fabric: spine/leaf/border-leaf/access/host -> dc-spine, dc-leaf, dc-border-leaf, dc-access, dc-server. Campus border leafs flipped from border-leaf-campus to campus-border-leaf for consistency. Core, campus spines/leafs/access/hosts unchanged. Updates topology, annotations, all configs (hostnames + peer descriptions), host interface files, README, TROUBLESHOOTING, END_TO_END_TESTING, and the SVG diagram.	2026-04-24 07:43:02 +00:00
Damien	cb74dd118f	Fix VRF gold BGP IPv4 activation on cores and border leafs ... With 'no bgp default ipv4-unicast' set at the router level, VRF gold eBGP/iBGP neighbors were establishing but not exchanging any IPv4 prefixes, breaking inter-fabric transit between DC and Campus. Add an explicit 'address-family ipv4' block with 'neighbor X activate' under 'vrf gold' on both cores and all four border leafs. Also drop 'redistribute learned' from the border leaf VRF gold stanza: it is not a valid command in that context and was silently stripped by EOS.	2026-04-23 10:26:41 +00:00
Damien	4b4c1852c4	Add Core router configs (AS 65500, iBGP + VRF gold transit) ... core1/core2 provide L3 transit between DC and Campus fabrics. Each physical link toward a Border Leaf is subinterfaced (.100 default, .200 VRF gold). OSPF area 0 in default VRF, eBGP to DC BLs (65005) and Campus BLs (66005), iBGP between core1 and core2 via Loopback0. VRF gold uses redistribute connected and VRF-aware eBGP sessions on .200 subinterfaces to stitch VRF gold end-to-end across fabrics.	2026-04-18 08:38:21 +00:00