1# CNI Configuration
2 
3See [README.md](README.md) for overview.
4 
5## Workflow (2-4 weeks)
6 
71. **Submit request** (Week 1): Contact account team, provide type/location/use case
82. **Review config** (Week 1-2, v1 only): Approve IP/VLAN/spec doc
93. **Order connection** (Week 2-3):
10   - **Direct**: Get LOA, order cross-connect from facility
11   - **Partner**: Order virtual circuit in partner portal
12   - **Cloud**: Order Direct Connect/Cloud Interconnect, send LOA+VLAN to CF
134. **Configure** (Week 3): Both sides configure per doc
145. **Test** (Week 3-4): Ping, verify BGP, check routes
156. **Health checks** (Week 4): Configure [Magic Transit](https://developers.cloudflare.com/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels) or [Magic WAN](https://developers.cloudflare.com/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/#add-tunnels) health checks
167. **Activate** (Week 4): Route traffic, verify flow
178. **Monitor**: Enable [maintenance notifications](https://developers.cloudflare.com/network-interconnect/monitoring-and-alerts/#enable-cloudflare-status-maintenance-notification)
18 
19## BGP Configuration
20 
21**v1 Requirements:**
22- BGP ASN (provide during setup)
23- /31 subnet for peering
24- Optional: BGP password
25 
26**v2:** Simplified, less BGP config needed.
27 
28**BGP over CNI (Dec 2024):** Magic WAN/Transit can now peer BGP directly over CNI v2 (no GRE tunnel required).
29 
30**Example v1 BGP:**
31```
32Router ID: 192.0.2.1
33Peer IP: 192.0.2.0
34Remote ASN: 13335
35Local ASN: 65000
36Password: [optional]
37VLAN: 100
38```
39 
40## Cloud Interconnect Setup
41 
42### AWS Direct Connect (Beta)
43 
44**Requirements:** Magic WAN, AWS Dedicated Direct Connect 1/10 Gbps.
45 
46**Process:**
471. Contact CF account team
482. Choose location
493. Order in AWS portal
504. AWS provides LOA + VLAN ID
515. Send to CF account team
526. Wait ~4 weeks
53 
54**Post-setup:** Add [static routes](https://developers.cloudflare.com/magic-wan/configuration/manually/how-to/configure-routes/#configure-static-routes) to Magic WAN. Enable [bidirectional health checks](https://developers.cloudflare.com/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/#legacy-bidirectional-health-checks).
55 
56### GCP Cloud Interconnect (Beta)
57 
58**Setup via Dashboard:**
591. Interconnects → Create → Cloud Interconnect → Google
602. Provide name, MTU (match GCP VLAN attachment), speed (50M-50G granular options available for partner interconnects)
613. Enter VLAN attachment pairing key
624. Confirm order
63 
64**Routing to GCP:** Add [static routes](https://developers.cloudflare.com/magic-wan/configuration/manually/how-to/configure-routes/#configure-static-routes). BGP routes from GCP Cloud Router **ignored**.
65 
66**Routing to CF:** Configure [custom learned routes](https://cloud.google.com/network-connectivity/docs/router/how-to/configure-custom-learned-routes) in Cloud Router. Request prefixes from CF account team.
67 
68## Monitoring
69 
70**Dashboard Status:**
71 
72| Status | Meaning |
73|--------|---------|
74| **Healthy** | Link operational, traffic flowing, health checks passing |
75| **Active** | Link up, sufficient light, Ethernet negotiated |
76| **Unhealthy** | Link down, no/low light (<-20 dBm), can't negotiate |
77| **Pending** | Cross-connect incomplete, device unresponsive, RX/TX swapped |
78| **Down** | Physical link down, no connectivity |
79 
80**Alerts:**
81 
82**CNI Connection Maintenance** (Magic Networking only):
83```
84Dashboard → Notifications → Add
85Product: Cloudflare Network Interconnect
86Type: Connection Maintenance Alert
87```
88Warnings up to 2 weeks advance. 6hr delay for new additions.
89 
90**Cloudflare Status Maintenance** (entire PoP):
91```
92Dashboard → Notifications → Add
93Product: Cloudflare Status
94Filter PoPs: gru,fra,lhr
95```
96 
97**Find PoP code:**
98```
99Dashboard → Magic Transit/WAN → Configuration → Interconnects
100Select CNI → Note Data Center (e.g., "gru-b")
101Use first 3 letters: "gru"
102```
103 
104## Best Practices
105 
106**Critical config-specific practices:**
107- /31 subnets required for BGP
108- BGP passwords recommended
109- BFD for fast failover (v1 only)
110- Test ping connectivity before BGP
111- Enable maintenance notifications immediately after activation
112- Monitor status programmatically via API
113 
114For design patterns, HA architecture, and security best practices, see [patterns.md](./patterns.md).
115