Detailed Test and Validation — Global WAN Backbone: FCR + IP-WAN

1 Purpose and How to Use This Document

This document contains the detailed test evidence supporting the Global WAN Backbone EVD. It is a companion to — not a replacement for — the EVD itself. The EVD contains the design, the architecture, and the validation summary. This document contains the raw evidence behind that summary.

Readers who want to understand the design, implement it, or evaluate its relevance should read the EVD. Readers who want to see exactly how the validation was performed — what the routing tables looked like before and after filter policies were applied, what the NE router BGP outputs showed, and what the traceroutes confirmed — should use this document.

This document is organised as follows:

• Phase 1 — Pre-Filter Baseline Active Routes: all three FCR Active Routes tables before route filter policies were applied. Rows that are removed after policies are applied are highlighted in red.
• Phase 2 — Post-Filter Active Routes: all three FCR Active Routes tables after route filter policies were applied.
• Phase 3 — NE Router BGP Validation: BGP session health, advertised routes, and full BGP table outputs from all three NE routers.
• Phase 4 — Traceroute Evidence: traceroute outputs from all three NE routers confirming end-to-end traffic paths.
• Appendix — NE Router Configurations: full per-metro NE router configurations used in this lab.

Rows highlighted in red in the pre-filter tables indicate prefixes that are removed after route filter policies are applied. All red-highlighted rows are absent from the post-filter tables

2 Phase 1 — Pre-Filter Baseline Active Routes

Before route filter policies were applied, FCR Active Routes showed the same EMEA prefixes arriving via both Regional and Global IP-WAN simultaneously — confirming the ECMP behaviour that this design solves.

Rows highlighted in red will be absent from the post-filter tables in Phase 2. These rows represent prefixes that violate the prefix separation rule or represent infrastructure and loopback ranges that must never enter the IP-WAN routing domain.

2.1 FCR-A Pre-Filter Baseline

Exported from Equinix Fabric portal before route filter policies were applied.

ECMP CONFIRMED: 10.2.x.x prefixes appear via both VC-Global-A (Global IP-WAN) and VC-Regional-A (Regional IP-WAN) simultaneously. Infrastructure range 192.168.2.0/30 and loopback 2.2.2.2/32 are visible from remote metro. All red-highlighted rows are removed after policies are applied.

2.2 FCR-B Pre-Filter Baseline

Exported from Equinix Fabric portal before route filter policies were applied.

ECMP CONFIRMED: 10.1.x.x prefixes appear via both VC-Global-B (Global IP-WAN) and VC-Regional-B (Regional IP-WAN) simultaneously. Infrastructure ranges and loopback visible from remote metros. All red-highlighted rows removed after policies applied.

2.3 FCR-C Pre-Filter Baseline

Exported from Equinix Fabric portal before route filter policies were applied.

FCR-C receives site-specific prefixes from both EMEA metros and infrastructure ranges before filters are applied. All red-highlighted rows removed after policies applied.

3 Phase 2 — Post-Filter Active Routes

After applying all five route filter policies, FCR Active Routes were exported and verified. The tables below show the post-policy state at each FCR.

3.1 FCR-A Post-Filter Active Routes

✅ PASS — FCR-A: AM site-specific prefixes via Regional IP-WAN only. AM and NY aggregates via Global IP-WAN only. No NY site-specific prefixes visible. No infrastructure or loopback ranges in IP-WAN domain. Universal rule confirmed.

3.2 FCR-B Post-Filter Active Routes

✅ PASS — FCR-B: FR site-specific prefixes via Regional IP-WAN only. FR and NY aggregates via Global IP-WAN only. No NY site-specific prefixes visible. Symmetric with FCR-A. Universal rule confirmed.

3.3 FCR-C Post-Filter Active Routes

✅ PASS — FCR-C: Only EMEA aggregates visible via Global IP-WAN. No site-specific EMEA prefixes at Metro-C. Metro-C site-specific prefixes remain local (VC-C only). Universal rule confirmed.

4 Phase 3 — NE Router BGP Validation

BGP session health, advertised routes, and full BGP table outputs from all three NE routers confirm the access layer is operating correctly and that prefix origination and separation are enforced end-to-end.

4.1 Router-A (Metro-A / Frankfurt)

✅ PASS — Router-A: BGP session to FCR-A Established (up 3w2d). Advertising 5 correct prefixes — loopback, aggregate, and three site-specific prefixes. Full BGP table shows Metro-B site-specific prefixes and Metro-C aggregate only. No site-specific Metro-C prefixes visible.

4.2 Router-B (Metro-B / Amsterdam)

✅ PASS — Router-B: BGP session to FCR-B Established. Advertising 5 correct prefixes. Full BGP table shows Metro-A site-specific prefixes and Metro-C aggregate only. Symmetric with Router-A

4.3 Router-C (Metro-C / New York)

✅ PASS — Router-C: BGP session to FCR-C Established. Advertising 5 correct prefixes. Full BGP table shows only Metro-A and Metro-B aggregates — no site-specific EMEA prefixes visible at Metro-C. This is the key confirmation that prefix separation is enforced end-to-end at the access layer.

5 Phase 4 — Traceroute Evidence

Traceroutes confirm that actual traffic paths match the routing table design. Regional IP-WAN next-hop addresses fall within 206.126.236.0/22. Global IP-WAN next-hop addresses fall within 142.215.8.0/22.

5.1 Router-A Traceroutes (Metro-A / Frankfurt)

✅ PASS — All 6 Router-A traceroutes correct. Metro-B site-specific destinations use Regional IP-WAN (hop 2 = 206.126.237.1). Metro-B aggregate and Metro-C destinations use Global IP-WAN (hop 2 = 142.215.9.1 or 142.215.8.16).

5.2 Router-B Traceroutes (Metro-B / Amsterdam)

✅ PASS — All 6 Router-B traceroutes correct. Metro-A site-specific destinations use Regional IP-WAN (hop 2 = 206.126.237.7). Metro-A aggregate and Metro-C destinations use Global IP-WAN (hop 2 = 142.215.9.7 or 142.215.8.16). Symmetric with Router-A.

5.3 Router-C Traceroutes (Metro-C / New York)

✅ PASS — All 8 Router-C traceroutes correct. All EMEA destinations — including site-specific addresses that FCR-C has no explicit route for — are reachable via the EMEA aggregate. Hop 2 is always in the 142.215.8.0/22 Global IP-WAN range. No Regional IP-WAN addresses appear. Aggregate-based inter-regional routing confirmed end-to-end.

6 Appendices

A: NE Router Configurations

Router-A Configuration — Frankfurt (Metro-A)

! ── Loopbacks ────────────────────────────────────────────────
interface Loopback0
 description Management
 ip address 1.1.1.1 255.255.255.255

interface Loopback1
 description FR-Site-1-Service
 ip address 10.1.1.1 255.255.255.0

interface Loopback2
 description FR-Site-2-Service
 ip address 10.1.2.1 255.255.255.0

interface Loopback3
 description FR-Site-3-Service
 ip address 10.1.3.1 255.255.255.0

! ── Gi3 toward FCR-A ─────────────────────────────────────────
interface GigabitEthernet3
 description VC-A toward FCR-A
 ip address 192.168.1.2 255.255.255.252
 no shutdown

! ── Static routes for aggregate origination ──────────────────
! /16 aggregate — advertised over Global IP-WAN only
ip route 10.1.0.0 255.255.0.0 Null0

! ── BGP configuration ─────────────────────────────────────────
router bgp 65100
 bgp log-neighbor-changes
 bgp router-id 1.1.1.1

 ! Loopback0 — management
 network 1.1.1.1 mask 255.255.255.255

 ! Service prefixes — /24 specifics for Regional IP-WAN
 network 10.1.1.0 mask 255.255.255.0
 network 10.1.2.0 mask 255.255.255.0
 network 10.1.3.0 mask 255.255.255.0

 ! /16 aggregate — for Global IP-WAN (FCR-A applies filter)
 network 10.1.0.0 mask 255.255.0.0

 ! BGP session toward FCR-A
 neighbor 192.168.1.1 remote-as 59991
 neighbor 192.168.1.1 description FCR-A-VC-A
 neighbor 192.168.1.1 password 0 Equinix123

! ── Verification commands ─────────────────────────────────────
! show ip bgp summary
! show ip bgp neighbors 192.168.1.1 advertised-routes
! show ip bgp

Router-B Configuration — Amsterdam (Metro-B)

! ── Loopbacks ────────────────────────────────────────────────
interface Loopback0
 description Management
 ip address 2.2.2.2 255.255.255.255

interface Loopback1
 description AM-Site-1-Service
 ip address 10.2.1.1 255.255.255.0

interface Loopback2
 description AM-Site-2-Service
 ip address 10.2.2.1 255.255.255.0

interface Loopback3
 description AM-Site-3-Service
 ip address 10.2.3.1 255.255.255.0

! ── Gi3 toward FCR-B ─────────────────────────────────────────
interface GigabitEthernet3
 description VC-B toward FCR-B
 ip address 192.168.2.2 255.255.255.252
 no shutdown

! ── Static routes for aggregate origination ──────────────────
! /16 aggregate — advertised over Global IP-WAN only
ip route 10.2.0.0 255.255.0.0 Null0

! ── BGP configuration ─────────────────────────────────────────
router bgp 65200
 bgp log-neighbor-changes
 bgp router-id 2.2.2.2

 ! Loopback0 — management
 network 2.2.2.2 mask 255.255.255.255

 ! Service prefixes — /24 specifics for Regional IP-WAN
 network 10.2.1.0 mask 255.255.255.0
 network 10.2.2.0 mask 255.255.255.0
 network 10.2.3.0 mask 255.255.255.0

 ! /16 aggregate — for Global IP-WAN (FCR-B applies filter)
 network 10.2.0.0 mask 255.255.0.0

 ! BGP session toward FCR-B
 neighbor 192.168.2.1 remote-as 60000
 neighbor 192.168.2.1 description FCR-B-VC-B
 neighbor 192.168.2.1 password 0 Equinix123

! ── Verification commands ─────────────────────────────────────
! show ip bgp summary
! show ip bgp neighbors 192.168.2.1 advertised-routes
! show ip bgp

Router-C Configuration — New York (Metro-C)

! ── Loopbacks ────────────────────────────────────────────────
interface Loopback0
 description Management
 ip address 3.3.3.3 255.255.255.255

interface Loopback1
 description NY-Site-1-Service
 ip address 172.16.1.1 255.255.255.0

interface Loopback2
 description NY-Site-2-Service
 ip address 172.16.2.1 255.255.255.0

interface Loopback3
 description NY-Site-3-Service
 ip address 172.16.3.1 255.255.255.0

! ── Gi3 toward FCR-C ─────────────────────────────────────────
interface GigabitEthernet3
 description VC-C toward FCR-C
 ip address 192.168.3.2 255.255.255.252
 no shutdown

! ── Static routes for aggregate origination ──────────────────
! /16 aggregate — advertised over Global IP-WAN only
ip route 172.16.0.0 255.255.0.0 Null0

! ── BGP configuration ─────────────────────────────────────────
router bgp 65300
 bgp log-neighbor-changes
 bgp router-id 3.3.3.3

 ! Loopback0 — management
 network 3.3.3.3 mask 255.255.255.255

 ! Service prefixes — /24 specifics
 ! NY has no Regional IP-WAN — all prefixes go over Global IP-WAN
 network 172.16.1.0 mask 255.255.255.0
 network 172.16.2.0 mask 255.255.255.0
 network 172.16.3.0 mask 255.255.255.0

 ! /16 aggregate
 network 172.16.0.0 mask 255.255.0.0

 ! BGP session toward FCR-C
 neighbor 192.168.3.1 remote-as 40052
 neighbor 192.168.3.1 description FCR-C-VC-C
 neighbor 192.168.3.1 password 0 Equinix123

! ── Verification commands ─────────────────────────────────────
! show ip bgp summary
! show ip bgp neighbors 192.168.3.1 advertised-routes
! show ip bgp

B: IP-WAN Address Reference