Skip to content

Commit e8eeceb

Browse files
added dash status
1 parent d1182f5 commit e8eeceb

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

src/content/docs/network-interconnect/express-cni/create-interconnects.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,3 +17,13 @@ pcx_content_type: how-to
1717
6. Review the options you have chosen, and select **Confirm order**.
1818
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.
1919
8. Select **View Interconnects** to review the CNIs you have ordered.
20+
21+
## Review interconnects
22+
23+
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.
24+
25+
Direct CNI connections are LACP (Link Aggregation Control Protocol) enabled and use LACP packets to negotiate with other ports. The [Status column](https://dash.cloudflare.com/?to=/:account/interconnects/all) in the dashboard shows three different status:
26+
27+
- **Pending**: Pending shows up in new interconnects that are not yet active. This is expected and can occur for several reasons: the customer has not received their interconnect, the device is unresponsive, or physical adjustments may be required, such as swapping RX/TX fibers. The `Pending` status will go away after the customer completes the cross-connect.
28+
- **Active**: The interconnect port on the Customer Connectivity Router (CCR) has established a LACP session with the connected port on the customer device.
29+
- **Unhealthy**: The interconnect port on the CCR has lost a previously established LACP session with the connected port on the customer device. 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.

0 commit comments

Comments
 (0)