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/cloud-cni.mdx
+1-42Lines changed: 1 addition & 42 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,45 +20,4 @@ Azure ExpressRoute support is coming soon.
20
20
21
21
## Cloud Interconnect Setup
22
22
23
-
Enterprise customers using Magic WAN can get started with Cloud Interconnect by contacting their account team.
24
-
25
-
### AWS Direct Connect (beta)
26
-
27
-
If you are a Magic WAN customer, you can connect to [AWS Direct Connect](https://docs.aws.amazon.com/directconnect/) using Cloud Interconnect. Currently, Cloud Interconnect only supports Dedicated Direct Connect, not Hosted Direct Connect. A Dedicated AWS Direct Connect involves a full physical port allocation in AWS, whereas a Hosted AWS Direct Connect uses a VLAN on a shared port between AWS and Cloudflare.
28
-
29
-
For your AWS Direct Connect, you can choose between connection speeds of 10 Gbps or 1 Gbps.
30
-
31
-
To connect to AWS Direct Connect:
32
-
33
-
1. Contact your account team to start the Cloud Interconnect provisioning process. Your team will let you know of available interconnect locations so you can choose the best one for you, as well as all the details involved in this process.
34
-
2. Log in to your AWS portal and order a Direct Connect.
35
-
3. AWS will provide you a Letter of Agency (LOA) — sometimes referred to as a Letter of Authorization — and a VLAN ID that you need to send to your account team.
36
-
4. Your account team will continue the process of provisioning your Cloud Interconnect with the AWS documents you have provided. Overall, this process should take around four weeks to finish.
37
-
38
-
### Google Cloud interconnect (beta)
39
-
40
-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
41
-
2. Select **Interconnects** > **Create new**.
42
-
3. Under **Cloud CNI** select **Create new** .
43
-
4. Under **Google Integration**, select **Select integration**.
44
-
5. Give your interconnect a name and optionally a description. Make sure the **MTU** value matches the MTU configured on the [GCP VLAN attachment](https://cloud.google.com/network-connectivity/docs/interconnect/how-to/dedicated/creating-vlan-attachments).
45
-
6. Select **Continue**.
46
-
7. From the **Interface speed** dropdown menu, select an **Interface speed**. GCP will charge you based on the speed of the interconnect that you choose.
47
-
8. Enter your [VLAN attachment pairing key](https://cloud.google.com/network-connectivity/docs/interconnect/how-to/partner/creating-vlan-attachments).
48
-
9. Select **Continue**.
49
-
10. Review the details you provided and select **Confirm order**.
50
-
51
-
Your Google Cloud Platform (GCP) interconnect will take a few minutes to be available. A BGP session will be established but no routes will be exchanged.
52
-
53
-
#### GCP next steps
54
-
55
-
You can now select **View interconnects** for a list of all interconnects on your account. Select the interconnect name to show the interconnect details. The interconnect has a unique **Interconnect ID**.
56
-
57
-
After you have configured your Google Cloud Interconnect, you will need to add routes to use the interconnect:
58
-
59
-
- To create routes in the Magic routing table to direct traffic towards GCP:
60
-
- Add [static routes](/magic-wan/configuration/manually/how-to/configure-routes/#configure-static-routes) to your Magic WAN routing table with [legacy bidirectional tunnel health checks](/magic-wan/configuration/manually/how-to/configure-tunnels/#legacy-bidirectional-health-checks) to detect failures and steer traffic to alternative paths.
61
-
- Note that routes advertised by BGP from GCP Cloud Router will be ignored.
62
-
- To create routes in GCP routing table to direct traffic towards Cloudflare, you must use the GCP Cloud Router:
63
-
- Add [custom learned routes to Cloud Router](https://cloud.google.com/network-connectivity/docs/router/how-to/configure-custom-learned-routes).
64
-
- Use the BGP session. Reach out to your account team to request a list of one or more prefixes to advertise, and specify the interconnect ID you want to advertise over.
23
+
To create a new cloud interconnect, contact your customer success manager to get started with the set up.
Copy file name to clipboardExpand all lines: src/content/docs/network-interconnect/express-cni/create-interconnects.mdx
+1-26Lines changed: 1 addition & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,29 +5,4 @@ sidebar:
5
5
order: 2
6
6
---
7
7
8
-
To create a new interconnect, make sure you are logged in with Admin or higher-level account permissions. This is required for the wizard to successfully request and provision a new Direct CNI connection.
9
-
10
-
1. Log in to the [Cloudflare dashboard](https://developers.cloudflare.com/), and select your account.
11
-
2. Select **Interconnects**.
12
-
3. In **Direct CNI**, select **Create new**.
13
-
4. From the list, choose a location that suits you with **Select location**, or search for one in the search box. In addition to city, state and country, you can also search by the [IATA airport code](https://en.wikipedia.org/wiki/IATA_airport_code) for the metro area where your data center is located.
14
-
:::note
15
-
If your location is not listed it means that Direct CNI is not available in your location yet. Refer to [Classic CNI](/network-interconnect/classic-cni/) to learn how you can use the classic version of Cloudflare Network Interconnect to connect your location to Cloudflare.
16
-
:::
17
-
5. Your interface is automatically assigned a speed of 10G. Give it a name, and select **Continue**.
18
-
:::note
19
-
Contact your account team if you need 100 Gigabit connections.
20
-
:::
21
-
6. Review the options you have chosen, and select **Confirm order**.
22
-
7. Download the Letter of Authorization that Cloudflare created with your settings. You will need this document to contact your data center and provide them the IP addresses for the CNI connection.
23
-
8. Select **View Interconnects** to review the CNIs you have ordered.
24
-
25
-
## Review interconnects
26
-
27
-
The Cloudflare dashboard shows a list of all previously created interconnects, as well as useful information such as IP addresses, speed, type of interconnect, and status.
28
-
29
-
The [Status column](https://dash.cloudflare.com/?to=/:account/interconnects/all) in the dashboard shows three different status:
30
-
31
-
-**Active**: The link operational state at the interconnect port on the Customer Connectivity Router (CCR) is up. This means that the CCR port sees sufficient light levels and has negotiated an Ethernet link.
32
-
-**Unhealthy**: The link operational state at interconnect port is down. This might mean the CCR does not see light, cannot negotiate an Ethernet signal, or the light levels are below -20 dBm. You can take general troubleshooting steps to solve the issue (such as checking cables and status lights for connectivity issues). If you are unable to solve the issue in this way, contact your account team.
33
-
-**Pending**: The link is not yet active. This is expected and can occur for several reasons: the customer has not received a cross-connect, the device is unresponsive, or physical adjustments may be required, such as swapping RX/TX fibers. The `Pending` status will disappear after the customer completes the cross-connect and status moves to `Active`.
8
+
To create a new interconnect, contact your customer success manager to get started with the set up.
0 commit comments