> For the complete documentation index, see [llms.txt](https://docs.console.zenlayer.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.console.zenlayer.com/welcome/cloud-networking/get-started/connection-management.md).

# Connection Management

Check connection states, manage private connects and cloud routers, change bandwidth, and delete connections on zenConsole.

Once a connection is created, you can check its state, add access points, change its bandwidth, or delete it on zenConsole. This page covers the day-to-day management of private connects, cloud routers, and ports.

## States

| State         | Meaning                                                    |
| ------------- | ---------------------------------------------------------- |
| **Inactive**  | The port or connection is not connected yet                |
| **Deploying** | The port or private connect is being deployed              |
| **Up**        | The port or connection is connected and running            |
| **Warning**   | One or more ports or connections are down or abnormal      |
| **Down**      | The port or connection is disabled                         |
| **Power off** | You deleted the service, or your balance is 2 days overdue |

{% hint style="info" %} <mark style="color:blue;">**Note**</mark>

* <mark style="color:blue;">Private connects and ports: if your balance is overdue, go to</mark> <mark style="color:blue;">**Action**</mark> <mark style="color:blue;">></mark> <mark style="color:blue;">**Redeploy**</mark> <mark style="color:blue;">or refill within 2 days. Otherwise the service is fully terminated and cannot be restored.</mark>
* <mark style="color:blue;">Cloud routers: a deleted cloud router cannot be restored in zenConsole —</mark> [<mark style="color:purple;">**submit a support ticket**</mark>](https://console.zenlayer.com/ticket) <mark style="color:blue;">to restore one.</mark>
  {% endhint %}

## Manage your private connect

### Private connect view <a href="#private-connect-view" id="private-connect-view"></a>

1. Expand the private connect to view its port or cloud connect details.
2. Click the label of your private connect to:
   * View your bandwidth graph in **Overview**
   * Update your notes in **Information**
   * Change your bandwidth cap in **Configuration**
   * Delete the private connect in **Delete**

### Port view

1. Expand the port to view the private connects created on it.
2. Click **+ Connection** to create a new private connect on an existing port.
3. Click the label of your port to:
   * View your bandwidth graph in **Overview**
   * Change the LOA owner or update your notes in **Information**
   * View the port's **change history**
   * Delete the port in **Delete**

<img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-5961bea9ac389c1aa2f03164b5622f10a99895e1%2FIcon.svg?alt=media&amp;token=b85eac46-fd05-4800-aa2b-8db408b8af26" alt="" data-size="line"><mark style="color:blue;">**Note**</mark>\ <mark style="color:blue;">A port can be deleted only when it is not an access point of any private connect or cloud router, and it was purchased on zenConsole. Subscription ports cannot be deleted manually; they are released when the subscription ends.</mark>

### Cloud view

Shows the private connects whose access point type is a public cloud. They are managed the same way as in the [**private connect view**](#private-connect-view).

### Traffic queries and how the figures are measured

The **Overview** of a private connect or a port shows its bandwidth graph, counted separately for the inbound and outbound directions.

* **Sampling granularity**: 5 minutes. Each window reports a **minimum, an average, the 95th percentile, and the 99th percentile**, so you can read the baseline and the spikes apart.
* **Query range**: a single query spans at most 1 day, within the last 30 days.
* **Empty is not zero**: an empty graph means the window has no valid samples (collection was interrupted, for example) — which is not the same as `0` traffic.
* **What you can query**: traffic data is also available over the OpenAPI; latency and packet loss are currently visible only on zenConsole.

## Manage your cloud router

1. Expand the cloud router to view its port or cloud connect details.
2. Click **+ Add Point** to add a new access point.
3. Click the label of your cloud router to:
   * Select access points and view your bandwidth graph in **Overview**
   * Update your notes or delete the cloud router in **Information**
   * Click **+ Add Point** in the upper-right corner to add a new access point

### Checking access points and links

* **Per access point**: in **Overview**, select an access point to see its bandwidth graph; expanding the cloud router lists every access point and cloud connect with its details.
* **Whole topology**: the **network overview** page maps every connection in service. Each access point is labelled with its type (data center, public cloud, partner connect, Internet, bare metal VPC, IX, and so on), its city and facility, and its connectivity state (normal, abnormal, or down).
* **How a link's state is decided**: on a cloud router, a link's state is derived from its two ends — **down** if either end is down, **normal** only when both ends are, and **abnormal** when only part of it is connected. A private connect's link state comes straight from the connection itself.
* **Access utilization**: the network overview also lists interface speed, bandwidth utilization, and inbound/outbound traffic per data center port, cloud access, VPC access, and Internet, which makes a saturated access point easy to spot.

For the overall picture, see the [**network health score**](https://docs.console.zenlayer.com/welcome/cloud-networking/overview/network-health.md).

{% hint style="info" %} <mark style="color:blue;">**Note**</mark>

* <mark style="color:blue;">Changing the bandwidth cap adjusts your monthly fee accordingly. See</mark> [<mark style="color:purple;">**Cloud Networking Billing**</mark>](https://docs.console.zenlayer.com/welcome/pricing/cloud-networking-pricing.md)<mark style="color:blue;">.</mark>
* <mark style="color:blue;">If the billing cycle has already started (UTC+0), the day you delete the service is still charged. See</mark> [<mark style="color:purple;">**Cloud Networking Billing**</mark>](https://docs.console.zenlayer.com/welcome/pricing/cloud-networking-pricing.md)<mark style="color:blue;">.</mark>
* <mark style="color:blue;">Once a service is fully terminated, all data is cleared and cannot be recovered. Proceed with care.</mark>
  {% endhint %}

## Change bandwidth

After creating a Layer 2 or Layer 3 connection, you can change its bandwidth:

* **Private connect**: go to **Action** > **Change Bandwidth Cap**.
* **Cloud router**: expand the cloud router's name, click the access point you want, and select **Change Access Bandwidth** on the **Information** tab.

Which limits apply depends on what sits at each end of the connection:

<figure><img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-140ed9e778a740fd3cba843bc2a3c449a264435a%2Fbandwidth-change-scenarios.svg?alt=media" alt=""><figcaption><p>Changing bandwidth, by connection scenario</p></figcaption></figure>

### Port to port

With a data center port at each end, the bandwidth cap is bound only by the port speeds — the lower of the two. The change takes effect immediately, with nothing to do on any third-party platform.

### Port to a public cloud

When one end is a public cloud, the change is also bound by that cloud's access bandwidth tiers:

<figure><img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-b6080fe018732d2e2102561a26d45669aa7ec22c%2Fbandwidth-change-tiers.svg?alt=media" alt=""><figcaption><p>How bandwidth tiers work when you change bandwidth</p></figcaption></figure>

* For a connection to AWS, you can only move within the AWS cloud connect bandwidth tier.
* For a connection to Alibaba Cloud, leaving the original tier means accepting the connection again on Alibaba Cloud. See [**Alibaba Cloud Express Connect Configuration**](https://docs.console.zenlayer.com/welcome/cloud-networking/get-started/validate-connection-in-public-cloud/alibaba-cloud-configuration.md).
* Staying inside a tier needs no action on the cloud side; the change takes effect immediately.

### Example 1: a private connect between AWS and Alibaba Cloud

Suppose the private connect is set to `60 Mbps`. You are charged:

* `100 Mbps` AWS cloud connect fee
* `100 Mbps` Alibaba cloud connect fee
* `60 Mbps` private connect bandwidth fee

Because the AWS cloud connect sits at `100 Mbps` and cannot leave its tier, the private connect bandwidth can only move between `51 Mbps` and `100 Mbps`. Changing it to `80 Mbps` stays inside Alibaba Cloud's `50 Mbps`–`100 Mbps` tier, so there is nothing to re-accept.

### Cloud router access points

A cloud router's access bandwidth is changed one access point at a time, and the backbone bandwidth and the access bandwidth are billed separately. When the access point is a public cloud, the tier rules above still apply.

### Example 2: a cloud router with an Alibaba Cloud access point

Suppose a cloud router has an Alibaba Cloud access point set to `60 Mbps`, inside the `50 Mbps`–`100 Mbps` tier:

* Changing it within the tier (for example to `80 Mbps`) needs no action on Alibaba Cloud.
* Lowering it or leaving the tier (for example to `40 Mbps` or `180 Mbps`) means accepting the connection again on Alibaba Cloud.

## Delete a cloud connect

A cloud connect is deleted **on both sides, in order**: delete the connection on the public cloud console first, wait for the cloud side to sync, then delete it on zenConsole. Billing stops once the deletion on zenConsole succeeds.

<figure><img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-a37b2854c16664657bd068e242ae2f356ab7a0ae%2Fdelete-cloud-connect-flow.svg?alt=media" alt=""><figcaption><p>Deleting a cloud connect</p></figcaption></figure>

{% hint style="info" %} <mark style="color:blue;">**Note**</mark>

<mark style="color:blue;">After you delete it on the cloud side, the tunnel state takes</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**10 to 15 minutes**</mark> <mark style="color:blue;"></mark><mark style="color:blue;">to sync. The cloud console may still list the tunnel during that window — this is expected. Wait for the sync to finish before deleting on zenConsole, otherwise the deletion may fail validation.</mark>
{% endhint %}

The entry point on each cloud, for step 1, is as follows.

### AWS

1. Go to the AWS Direct Connect console and select **Connections**.
2. Select the connection to delete, then select **Delete**.

See the [**AWS documentation**](https://docs.aws.amazon.com/directconnect/latest/UserGuide/deleteconnection.html).

### Tencent Cloud

1. Go to the Tencent Cloud Direct Connect console and select **Dedicated Virtual Interfaces**.
2. Select the dedicated tunnel to delete, then select **Delete**.

See the [**Tencent Cloud documentation**](https://www.tencentcloud.com/document/product/216/19252).

### Google Cloud

1. Go to the Google Cloud console > Cloud Interconnect **Physical connections**.
2. Select the dedicated interconnect to delete, then select **Delete**.

See the [**Google Cloud documentation**](https://cloud.google.com/network-connectivity/docs/interconnect/how-to/dedicated/deleting-interconnects).

### Alibaba Cloud

1. Go to the Alibaba Cloud Express Connect console > Physical Connections.
2. On the **VBR** tab, find the VBR to delete. Click the **More** icon in the Actions column and select **Delete**.
3. On the **Shared Physical Connection** tab, find the shared port to delete and click **Delete** in the Actions column.

See the [**Alibaba Cloud documentation**](https://www.alibabacloud.com/help/en/express-connect/user-guide/manage-connections-for-tenants).

### Azure Cloud

On the Azure console, right-click the peering and select **Delete** to remove the private peering.

See the [**Azure documentation**](https://learn.microsoft.com/en-us/azure/expressroute/expressroute-howto-routing-portal-resource-manager#deleteprivate).

### Huawei Cloud

Delete in dependency order:

1. Delete the virtual interface.
2. Delete the virtual gateway, once no other virtual interface uses it.
3. Release the hosted connection assigned to you.

See the [**Huawei Cloud Direct Connect user guide**](https://support.huaweicloud.com/intl/en-us/usermanual-dc/).

### Volcengine

Delete in dependency order:

1. Delete the virtual interface.
2. Detach the DC gateway from the CEN, then delete the gateway.
3. Delete the **shared physical connection** you accepted earlier.

<img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-5961bea9ac389c1aa2f03164b5622f10a99895e1%2FIcon.svg?alt=media&amp;token=b85eac46-fd05-4800-aa2b-8db408b8af26" alt="" data-size="line"><mark style="color:blue;">**Note**</mark>\ <mark style="color:blue;">Do not skip step 3. While the shared physical connection exists, port charges keep accruing.</mark>

See the [**Volcengine Direct Connect documentation**](https://www.volcengine.com/docs/6408/68176).

### BytePlus

The steps match Volcengine: delete the virtual interface, detach and delete the DC gateway in the CEN, then delete the **shared physical connection** you accepted earlier.

See the [**BytePlus Direct Connect documentation**](https://docs.byteplus.com/docs/directconnect/).

### Oracle Cloud

1. In **FastConnect**, find the virtual circuit and select **Delete**.
2. If the attached dynamic routing gateway (DRG) is no longer used, delete it as well.

See the [**FastConnect overview**](https://docs.oracle.com/en-us/iaas/Content/Network/Concepts/fastconnectoverview.htm) and [**Managing DRGs**](https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/managingDRGs.htm).
