Setting the file. One moment.
Chapter 04 · Cloudflare Deploy
Subchapter 4.124
references/network-interconnect/configuration.mdMarkdown4 KBView on GitHub
v1 Requirements:
v2: Simplified, less BGP config needed.
BGP over CNI (Dec 2024): Magic WAN/Transit can now peer BGP directly over CNI v2 (no GRE tunnel required).
Example v1 BGP:
Router ID: 192.0.2.1
Peer IP: 192.0.2.0
Remote ASN: 13335
Local ASN: 65000
Password: [optional]
VLAN: 100Requirements: Magic WAN, AWS Dedicated Direct Connect 1/10 Gbps.
Process:
Post-setup: Add static routes (opens in a new tab) to Magic WAN. Enable bidirectional health checks (opens in a new tab).
Setup via Dashboard:
Routing to GCP: Add static routes (opens in a new tab). BGP routes from GCP Cloud Router ignored.
Routing to CF: Configure custom learned routes (opens in a new tab) in Cloud Router. Request prefixes from CF account team.
Dashboard Status:
| Status | Meaning |
|---|---|
| Healthy | Link operational, traffic flowing, health checks passing |
| Active | Link up, sufficient light, Ethernet negotiated |
| Unhealthy | Link down, no/low light (<-20 dBm), can’t negotiate |
| Pending | Cross-connect incomplete, device unresponsive, RX/TX swapped |
| Down | Physical link down, no connectivity |
Alerts:
CNI Connection Maintenance (Magic Networking only):
Dashboard → Notifications → Add
Product: Cloudflare Network Interconnect
Type: Connection Maintenance AlertWarnings up to 2 weeks advance. 6hr delay for new additions.
Cloudflare Status Maintenance (entire PoP):
Dashboard → Notifications → Add
Product: Cloudflare Status
Filter PoPs: gru,fra,lhrFind PoP code:
Dashboard → Magic Transit/WAN → Configuration → Interconnects
Select CNI → Note Data Center (e.g., "gru-b")
Use first 3 letters: "gru"Critical config-specific practices:
For design patterns, HA architecture, and security best practices, see patterns.md.