You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/network-interconnect/get-started.mdx
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,9 @@ Eligibility for CNI and port availability is determined in coordination with you
16
16
- CNI ports are currently offered at no charge to Enterprise customers.
17
17
- Non-Enterprise customers (and any third party) may peer with Cloudflare via Internet Exchange according to our [open peering policy](https://www.cloudflare.com/peering-policy/).
18
18
- CNI is available at select Cloudflare data centers:
19
-
- The type of dataplane offered in that location (v1 or v1.1) will determine specifications of the supported connection, such as the MTU.
19
+
- The type of dataplane offered in that location (v1) will determine specifications of the supported connection, such as the MTU.
20
20
- The diversity offered in the location will vary.
21
-
- Customers must have a BGP session established for CNI v1/1.1 to be operational.
21
+
- Customers must have a BGP session established for CNI v1 to be operational.
22
22
23
23
### Product use cases
24
24
@@ -27,22 +27,21 @@ Eligibility for CNI and port availability is determined in coordination with you
-**Dataplane v1**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR (single-mode fiber).
31
31
-**Dataplane v2 (beta)**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR4 (single-mode fiber) optics are supported.
32
32
-**Distance limitations:** Cloudflare does not support optical links longer than 10 km. For longer distances, you must use intermediate hardware or a third-party provider to extend the connection.
33
33
-**IP addressing:** All Direct and Partner CNI connections use a `/31` subnet for point-to-point IP connectivity between your router and Cloudflare.
34
34
-**VLAN support:**
35
-
-**Dataplane v1 & v1.1**: CNI ports may be assigned a single 802.1Q VLAN tag.
35
+
-**Dataplane v1**: CNI ports may be assigned a single 802.1Q VLAN tag.
36
36
-**Dataplane v2 (beta)**: VLAN tagging (802.1Q) and QinQ are not yet supported.
37
37
-**MTU considerations:**
38
-
-**Dataplane v1**: Requires GRE tunneling for Magic Transit / WAN traffic, limiting the MTU to 1,476 bytes.
39
-
-**Dataplane v1.1**: Supports a native 1,500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1,476-byte MTU for traffic from you to Cloudflare (egress).
38
+
-**Dataplane v1**: Supports a native 1,500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1,476-byte MTU for traffic from you to Cloudflare (egress).
40
39
-**Dataplane v2 (beta)**: Supports a maximum MTU of 1,500 bytes bidirectionally with no GRE requirement.
41
40
-**Bidirectional Forwarding Detection (BFD):**
42
-
-**Dataplane v1 & v1.1**: BFD provides fast failure detection for BGP sessions and is supported on direct connections. To enable BFD, contact your account team. Note that BFD on a CNI does not impact the failover time for Magic Transit / WAN tunnels, which rely on separate health checks.
41
+
-**Dataplane v1**: BFD provides fast failure detection for BGP sessions and is supported on direct connections. To enable BFD, contact your account team. Note that BFD on a CNI does not impact the failover time for Magic Transit / WAN tunnels, which rely on separate health checks.
43
42
-**Dataplane v2 (beta)**: Not yet supported.
44
43
-**Link Aggregation Control Protocol (LACP)**:
45
-
-**Dataplane v1 & v1.1**: To increase bandwidth and provide link resiliency, Cloudflare supports combining multiple physical CNI ports into a single logical channel using Link Aggregation Control Protocol (LACP). You can bundle multiple connections to increase total throughput and add redundancy to your private connection with Cloudflare.
44
+
-**Dataplane v1**: To increase bandwidth and provide link resiliency, Cloudflare supports combining multiple physical CNI ports into a single logical channel using Link Aggregation Control Protocol (LACP). You can bundle multiple connections to increase total throughput and add redundancy to your private connection with Cloudflare.
46
45
-**Dataplane v2 (beta)**: Not yet supported. Use ECMP instead.
47
46
48
47
### Performance characteristics
@@ -53,7 +52,7 @@ The following are the maximum throughput rates supported by the CNI connection.
| From Cloudflare to Customer (all use cases) | Up to 10 Gbps | Up to 100 Gbps |
55
54
| From Customer to Cloudflare (peering use case) | Up to 10 Gbps | Up to 100 Gbps |
56
-
| From Customer to Cloudflare (Magic Transit/WAN) |•**v1 & v1.1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> •**v2 (beta)**: Up to 1 Gbps per CNI connection |•**v1 & v1.1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> •**v2 (beta)**: Up to 1 Gbps per CNI connection |
55
+
| From Customer to Cloudflare (Magic Transit/WAN) |•**v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> •**v2 (beta)**: Up to 1 Gbps per CNI connection |•**v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> •**v2 (beta)**: Up to 1 Gbps per CNI connection |
0 commit comments