Skip to content

Commit 79b2efc

Browse files
added prereqs
1 parent 62f44a3 commit 79b2efc

File tree

1 file changed

+15
-0
lines changed
  • src/content/docs/network-interconnect/express-cni

1 file changed

+15
-0
lines changed

src/content/docs/network-interconnect/express-cni/index.mdx

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,3 +12,18 @@ Connecting to Cloudflare directly with a Direct CNI reduces latency, makes your
1212
The use case for Direct CNI is Magic Transit or Magic WAN. If you have publicly routable origins that are behind Magic Transit over a Direct CNI, then all Cloudflare services that work with public origins will run over the CNI (for example, Load Balancer, WAF, Cache, etc).
1313

1414
In the Cloudflare dashboard you can find Cloudflare's nearest Cloudflare data center, and order a Direct CNI connection with speeds up to 100 gigabits per second, as well as create a Letter of Authorization (LoA).
15+
16+
## Prerequisites
17+
18+
- Small Form-factor Pluggable (SFP) optics supported
19+
- 10GBASE-LR optics will support up to 10 Km
20+
- 100GBASE-LR4 optics will support up to 10 Km
21+
- Maximum MTU is 1500 bytes.
22+
23+
### Limitations
24+
25+
The following functionality is not yet supported on Direct CNI's dedicated ports.
26+
- Virtual LAN (VLAN) tagging (802.1Q)
27+
- Link Aggregation Control Protocol (LACP) and link aggregation. You can use ECMP instead.
28+
- Bidirectional Forwarding Detection (BFD)
29+
- IPv6 (you cannot create CNIs in an account with IPv6 beta enabled)

0 commit comments

Comments
 (0)