Adding rest of the chapters

Oxyjun · Oxyjun · commit f4b311062405 · 2025-09-02T11:42:22.000+01:00
diff --git a/src/content/docs/fundamentals/reference/partners.mdx b/src/content/docs/fundamentals/reference/partners.mdx
@@ -21,7 +21,7 @@ Learn how to configure a variety of products with Cloudflare Analytics:
 
 Connect your network infrastructure with Cloudflare network fabric partners for increased reliability and security.
 
-<DirectoryListing folder="network-interconnect/classic-cni/set-up/partners" />
+<DirectoryListing folder="network-interconnect/get-started/#connectivity-partners" />
 
 ## Cloudflare Zero Trust Technology Partners
 
@@ -35,7 +35,7 @@ Enterprise customers have access to detailed logs of the metadata generated by o
 
 <DirectoryListing folder="/logs/logpush/logpush-job/enable-destinations/" />
 
-## ​​Cloudflare Technology Partners for Magic WAN
+## Cloudflare Technology Partners for Magic WAN
 
 Cloudflare Magic WAN integrates with a number of third-party partners, which enables our users to securely route their Internet traffic.
 
diff --git a/src/content/docs/network-interconnect/changelog.mdx b/src/content/docs/network-interconnect/changelog.mdx
@@ -2,7 +2,7 @@
 pcx_content_type: changelog
 title: Changelog
 sidebar:
-  order: 7
+  order: 99
 head: []
 description: Review recent changes to Cloudflare Network Interconnect.
 ---
diff --git a/src/content/docs/network-interconnect/get-started.mdx b/src/content/docs/network-interconnect/get-started.mdx
@@ -14,7 +14,7 @@ import { Render } from "~/components"
 Eligibility for CNI and port availability is determined in coordination with your Cloudflare account team. Notably:
 
 - CNI ports are currently offered at no charge to Enterprise customers. Non-Enterprise customers (and any third party) may peer with Cloudflare via Internet Exchange/PNI according to our [open peering policy](https://www.cloudflare.com/peering-policy/).
-- CNI provides benefits for certain Cloudflare products. Refer to [Product use cases section](#link) section to confirm that CNI is the right solution for your technical and business requirements.
+- CNI provides benefits for certain Cloudflare products. Refer to [Product use cases section](/network-interconnect/get-started/#product-use-cases) section to confirm that CNI is the right solution for your technical and business requirements.
 - CNI is available in a subset of Cloudflare data centers:
   - The type of dataplane offered in that location (v1.0 or v1.1) will determine specifications of the supported connection, such as the MTU.
   - The diversity offered in the location will vary.
@@ -32,4 +32,101 @@ Eligibility for CNI and port availability is determined in coordination with you
 - **MTU considerations:**
   - **Dataplane 1.0:** Requires GRE tunneling for Magic Transit / WAN traffic, limiting the MTU to 1476 bytes.
   - **Dataplane 1.1:** Supports a native 1500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1476-byte MTU for traffic from you to Cloudflare (egress).
-- **Bidirectional Forwarding Detection (BFD):** 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.
+- **Bidirectional Forwarding Detection (BFD):** 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.
+
+#### Performance Characteristics
+
+The following are the maximum throughput rates supported by the CNI connection. Actual performance will depend on your specific use case and configuration.
+
+| Direction (use case) | 10G Circuit | 100G Circuit |
+|----------------------|-------------|--------------|
+| From Cloudflare to Customer (all use case) | Up to 10 Gbps | Up to 100 Gbps |
+| From Customer to Cloudflare (peering use case) | Up to 10 Gbps | Up to 100 Gbps |
+| From Customer to Cloudflare (Magic Transit/WAN) | Up to 1 Gbps per GRE tunnel over the CNI | Up to 1 Gbps per GRE tunnel over the CNI |
+
+### Service Expectations
+
+Please consider the following service levels when planning your deployment:
+- **No Formal SLA**:
+  - CNI is currently offered at no charge and without a formal Service Level Agreement (SLA).
+  - Cloudflare will work to restore CNI service in the event of a Cloudflare issue. In some Cloudflare Data Centers the recovery time could be several days. Therefore we always recommend backup connectivity to a different device or via an Internet tunnel.
+- **Observability**: There is no visibility of the interconnect config/status within the Cloudflare dashboard.
+- **Availability**: While network-resilient locations are designed to maintain connectivity during maintenance, single-homed locations can experience full service disruption.
+- **Backup Connectivity**: You are required to maintain alternative Internet connectivity as a backup for all CNI implementations.
+
+## Location Alignment
+
+### Available Locations
+
+Direct connections are available at any Cloudflare data center where you are also located. Make sure to check whether the location of interest has the right dataplane version and diversity requirements for your use case. Refer to [available locations](/network-interconnect/static/cni-locations-04-08-2025.pdf) for details.
+
+### Connectivity Partners
+
+Cloudflare partners with leading global providers, including: Console Connect, CoreSite, Digital Realty, Equinix Fabric, Megaport, PacketFabric, and Zayo.
+
+## End-to-End Implementation Workflow
+
+The process of provisioning a CNI can take several weeks, depending on the complexity and third-party provider timelines. The most common delays occur during the physical connection phase, which is outside of Cloudflare's direct control.
+
+1. **Submit Request**: Work with your account team to create a CNI request ticket, providing your desired CNI type, location, use case, and technical details. An Implementation Manager will be assigned to guide the process.
+2. **Review Configuration**: The Implementation Manager will provide a detailed configuration document covering IP addressing, VLANs, and other technical specifications. You must review and approve this document.
+3. **Order Connection**:
+   - For a Direct Interconnect, you will receive a Letter of Authorization (LOA) from Cloudflare to order the physical cross-connect from the data center facility operator.
+   - For a Partner Interconnect, you will use the provided details to order a virtual circuit from the partner's portal.
+4. **Configure Network**: Both Cloudflare and your network team will configure the respective network devices according to the approved document.
+5. **Test and Verify**: Once the connection is physically established, teams will perform basic connectivity tests (for example, ping) and verify that the BGP session can be established.
+6. **Activate Services**: Configure your Cloudflare products (for example, Magic Transit) to route traffic over the new CNI. The Implementation Manager will verify end-to-end traffic flow before marking the deployment as complete.
+7. [Add maintenance notifications](/network-interconnect/monitoring-and-alerts/#enable-cloudflare-status-maintenance-notification).
+8. Enable tunnel health checks for Magic [Transit](/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels) / [WAN](/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/#add-tunnels).
+## How-To Guides
+
+### How-To: Provision a Direct Interconnect
+
+1. **Project Kickoff**: In an initial kickoff call, you will confirm the scope and timeline with Cloudflare. Be prepared to provide the following information:
+   - desired colocation facility
+   - required port speeds (10G or 100G)
+   - BGP ASN for Peering/Magic Transit
+   - BGP password (optional)
+2. **Order Cross-Connect**: Cloudflare will issue a Letter of Authorization (LOA). This document grants you permission to order a physical cross-connect between your equipment and a specific port on Cloudflare's hardware within the data center. This process can take one to two weeks or more, depending on the facility provider. Cloudflare's demarcation is the port that is specified in the LOA: you are responsible for the deployment, provisioning and ongoing support and operation of this connection and the commercial relationships with the facility provider and any 3rd party connectivity providers.
+
+### How-To: Provision a Partner Interconnect
+
+Cloudflare partners with leading connectivity providers globally. To provision a Partner Interconnect, you will initiate a connection request from your chosen provider's administrative portal. Cloudflare will then review and accept the request to activate the virtual circuit.
+
+### How-To: Configure BGP and Routing
+
+Once your physical cross-connect or virtual circuit is provisioned, the next phase is to configure IP routing using Border Gateway Protocol (BGP). This process typically takes about one week to complete.
+
+#### Step 1: IP Address Provisioning
+
+1. Cloudflare will send you a set of IPv4 and IPv6 addresses for your connection.
+2. Assign the provided IPs to your router's interface that connects to Cloudflare.
+3. Perform ping tests between your router and Cloudflare's router to confirm that the physical or virtual link is active and passing packets correctly.
+   - **For Partner Interconnects**: If you are using a partner like Megaport, ensure you have configured the correct VLAN provided by your Customer Success Manager, as an incorrect VLAN can cause IP provisioning to fail.
+
+#### Step 2: BGP Session Establishment
+
+After you confirm connectivity with successful ping tests, the next step is to establish the BGP session.
+
+1. Cloudflare will configure its side of the BGP session, and notify you once ready
+2. You will configure your side of the BGP session and accept the routes.
+3. Once the session is established, traffic will begin to flow over the CNI. Contact your solutions engineer to verify that traffic is routing as expected.
+
+#### BGP Configuration Options and Use Cases
+
+Depending on the Cloudflare services you use, your BGP configuration may vary:
+
+- **Standard Peering**: This is the most common scenario, where BGP is used to exchange routes between your network and Cloudflare. Cloudflare learns your network routes, which is useful for services like CDN-only deployments or on-demand Magic Transit. It is important to note that prefixes Cloudflare learns via CNI remain local to that specific data center and are not propagated to other Cloudflare locations.
+- **Magic Transit with Controlled Advertisement**: Magic Transit customers can use a second BGP session to control which prefixes are advertised to the internet. In this setup, Cloudflare advertises no prefixes to you, and you advertise only the specific prefixes you want Cloudflare to announce on your behalf.
+
+#### Important Note on Accepting Routes from Cloudflare
+
+If you wish to use the CNI for egress traffic from your network to Cloudflare-advertised prefixes (such as anycast or BYOIP addresses), you can accept the BGP prefixes you receive from Cloudflare (typically there will be around 4,000 routes advertised by Cloudflare). However, be aware that there is a 1 Gbps capacity limitation for traffic you send to Cloudflare over the CNI link.
+
+#### Optional: Bidirectional Forwarding Detection (BFD)
+
+For configurations that are highly sensitive to packet loss, Bidirectional Forwarding Detection (BFD) can be enabled to monitor link status on a sub-second basis.
+
+- BFD works by sending a rapid stream of small packets over the BGP session. If a few packets are lost, the link is immediately considered down, enabling faster failover.
+- BFD is only supported for Direct Interconnect connections. Contact your account team to enable it.
+- Note that enabling BFD on a CNI BGP session does not change the failover time for Magic Transit/WAN, which is controlled by its own tunnel health checks.
diff --git a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
@@ -0,0 +1,50 @@
+---
+pcx_content_type: concept
+title: Monitoring and alerts
+sidebar:
+  order: 5
+---
+
+import { Render } from "~/components"
+
+You can configure notifications for upcoming CNI maintenance events using the Notifications feature in the Cloudflare dashboard. It is recommended to subscribe to two types of notifications to stay fully informed.
+
+**CNI Connection Maintenance Alert (beta):** This alert informs you about maintenance events (scheduled, updated, or canceled) that directly impact your CNI circuits used with the Magic Networking overlay only.
+- You will receive warnings up to two weeks in advance for maintenance impacting your Magic Transit/WAN CNI connections.
+- You will be notified if the details of a scheduled maintenance change or if it is canceled.
+- For recently added maintenance, notifications are sent after a six-hour delay to prevent alerting fatigue from minor adjustments.
+
+**Cloudflare Status Maintenance Notification:** This alert informs you about maintenance for an entire Cloudflare Point of Presence (PoP). While not specific to your CNI, this maintenance will impact all CNI services in that location, including connections that are being used only for peering use cases without Magic Networking
+- You will be warned about potentially disruptive maintenance at the PoP level.
+- By default, you are notified for all event types (Scheduled, Changed, Canceled), but you can filter these.
+- By default, you are notified for all Cloudflare PoPs, but you can filter for only the specific locations where you have CNI circuits.
+
+## How to Configure Alerts
+
+### Enable CNI Connection Maintenance Alert (beta)
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. Go to **Notifications**.
+3. Select **Add**.
+4. From the product drop-down menu, select **Cloudflare Network Interconnect**.
+5. Select **Connection Maintenance Alert**.
+6. Give your notification a name and an optional description.
+7. Choose your preferred notification method (for example, email address).
+8. Select **Save**.
+
+### Enable Cloudflare Status Maintenance Notification
+
+1. First, identify the PoP code for your CNI circuit:
+   - Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+   - Navigate to **Magic Transit / WAN > Configuration > Interconnects**.
+   - Select the CNI you want to enable notifications for.
+   - In the menu that appears, note the Data Center code (for example, `gru-b`).
+2. Now, configure the alert:
+   - Go to **Notifications** and select **Add**.
+   - From the product drop-down menu, select **Cloudflare Status**.
+   - Select **Maintenance Notification**.
+   - Give your notification a name and choose your notification method.
+   - Select **Next**.
+   - Optionally, use the **Filter on Event Type** to select only the event types you want to be alerted for (Scheduled, Changed, Canceled).
+   - In **Filter on Points of Presence**, enter the three-letter code for your PoP (for example, for `gru-b`, enter `gru`). You can add multiple PoPs, separated by commas.
+   - Select **Create**.
diff --git a/src/content/docs/network-interconnect/operational-guidance.mdx b/src/content/docs/network-interconnect/operational-guidance.mdx
@@ -0,0 +1,29 @@
+---
+pcx_content_type: concept
+title: Operational guidance
+sidebar:
+  order: 7
+---
+
+import { Render } from "~/components"
+
+## Understanding Maintenance and Availability
+
+Also refer to [Monitoring and alerts](/network-interconnect/monitoring-and-alerts).
+
+Cloudflare performs regular network maintenance that may impact CNI connectivity.
+
+- **Maintenance Impact**: Maintenance windows average six hours.Customers who are not redundantly connected to diverse devices, for instance in single-homed PoPs will experience a complete service disruption on CNI in that location.
+- **Designing for Availability**: For critical applications, deploy CNI in locations that support diversity on the device level (multi-homed PoPs) to ensure protection against a single point of hardware failure and routine maintenance. Cloudflare does not guarantee coordinated maintenance between PoP locations. This means connecting to two different PoPs does not ensure protection against coincident service disruption.
+
+## Troubleshooting
+
+When facing connectivity problems, your first action should be to check for broader service disruptions. Visit `https://www.cloudflarestatus.com/` to see if any scheduled maintenance or active incidents are impacting services. This helps determine if the issue originates outside your network. Refer to [Monitoring and alerts](/network-interconnect/monitoring-and-alerts).
+
+If no system-wide problems are reported, gather the following information before submitting a support case. Providing comprehensive details facilitates a faster resolution:
+
+- **Timeline**: When the issue began and ended (if applicable), including the timezone.
+- **Identification**: The CNI IP address or point-to-point prefix for the impacted CNI. If your CNI is part of a Magic setup, please also provide the name of the Magic Transit/WAN interconnect as listed in your dashboard.
+- **Physical Layer**: Light levels of the CNI link (if applicable).
+- **Service Impact**: Confirmation whether Magic Transit / WAN traffic was affected.
+- **Problem Description**: A clear summary of the issue (for example, CNI down, BGP session down, prefixes withdrawn).
