> 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/create-a-layer-2-connection/select-a-partner-connect-as-access-point.md).

# Select a Partner Connect as Access Point

Partner connect reaches the backbone through a third-party interconnection platform. Ordering issues a service token that you use on the partner portal to establish the connection.

## Background Information

Partner connect lets you reach the Zenlayer backbone through a third-party interconnection platform. If you already have a port on that platform, you do not need to order a data center port and establish a cross connect at the access location.

Supported partners:

* **Equinix Fabric** — available
* **Megaport Fabric** — coming soon

A partner connect has an A side and a Z side: the **A side** is the Zenlayer access point (a data center port, a public cloud, and so on), and the **Z side** is the partner node. Once you place the order, a service token is issued. You use that token on the partner portal to request the connection, and the access point becomes active after the far end accepts.

<figure><img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-0735fdeceeb92702c47616d1c9ab5eaef8f9d151%2Fpartner-connect-flow.svg?alt=media" alt=""><figcaption><p>Partner Connect (Equinix Fabric) Flow</p></figcaption></figure>

## Procedures

{% stepper %}
{% step %}
**Configure the A-side access point**

Select the Zenlayer access point as usual — a data center, a public cloud, and so on — and complete its basic configuration.
{% endstep %}

{% step %}
**Configure the Z side: select an Equinix Fabric node**

Under the access point types, select **Partner Connect** > **Equinix Fabric**, then select the node to connect from.

* The node list comes from the NNI nodes between Zenlayer and Equinix. Each node shows the partner logo, the city (DC), and the **port priority** (`PRIMARY` / `SECONDARY`).
* After selecting a node, select the **Zenlayer DC**. A city may offer both an `alpha` and a `beta` DC so you can build for high availability; when more than one is available, `alpha` is recommended by default.
* The Zenlayer NNI you select is mapped to its corresponding Equinix port automatically — you do not enter it yourself.

The nodes currently available are:

| City           | Zenlayer DC | Equinix data center |
| -------------- | ----------- | ------------------- |
| Dubai          | DXB1        | DX1                 |
| Frankfurt      | FRA5        | FR7                 |
| Hong Kong      | HKG2        | HK2                 |
| Hong Kong      | HKG3        | HK3                 |
| Ashburn        | IAD1        | DC6                 |
| London         | LON1        | LD8                 |
| Sao Paulo      | SAO1        | SP2                 |
| Sao Paulo      | SAO2        | SP3                 |
| Singapore      | SIN2        | SG2                 |
| Silicon Valley | SJC1        | SV5                 |
| Silicon Valley | SJC2        | SV2                 |
| Tokyo          | TYO2        | TY8                 |

<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;">The available nodes, their port priority, and the alpha / beta DCs change with partner capacity. The creation page shows what you can actually select.</mark>
{% endstep %}

{% step %}
**Set the parameters**

* **Bandwidth**: fixed tiers of 50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, and 10 Gbps. Custom values are not supported.
* **VLAN ID**: specify one yourself, or let the system assign it (depending on the Zenlayer network configuration).
  {% endstep %}

{% step %}
**Configure the network information (cloud router only)**

When the partner connect is an access point of a Layer 3 cloud router, you also configure:

* The routing type: **BGP routing** or **static routing**
* The interconnection IPs on your side and the Zenlayer side
* The Autonomous System Number (**ASN**)
* Whether to enable **BFD**
* Advanced BGP settings (AS Override, Local Preference, MED)
* The **backbone access bandwidth** and the **Equinix port bandwidth**

See [**Configure Routing**](https://docs.console.zenlayer.com/welcome/cloud-networking/get-started/create-a-layer-3-connection/configure-routing-information.md) for details.
{% endstep %}

{% step %}
**Confirm the order and pay**
{% endstep %}
{% endstepper %}

## Get the service token

Once the order is complete, the order confirmation page shows a **service token** — a UUID string such as:

```
2709ac64-b875-4953-853f-3f5de561a93a
```

Copy this token and go to the **Equinix Fabric Portal** to complete the connection. The page also shows when the token expires: tokens are valid for **7 to 15 days**, so they do not sit idle indefinitely.

## Token state

The connection details in the connection list show the token **state**:

| State      | Shown in the list   | Meaning                                     |
| ---------- | ------------------- | ------------------------------------------- |
| `INACTIVE` | **Unused** (orange) | The expiry time is shown alongside          |
| `ACTIVE`   | **Used** (green)    | The token has been used on the partner side |
| `EXPIRED`  | **Expired** (red)   | Hover to see the exact expiry date          |

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

<mark style="color:blue;">A token cannot be refreshed or reissued. If it has expired, create the connection again to get a new token.</mark>
{% endhint %}

## Billing

A partner connect is billed by bandwidth on a tiered rate — the larger the bandwidth, the lower the unit price. The price is shown on the creation page.

## What to Do Next

1. Use the service token on the **Equinix Fabric Portal** to request the connection.
2. Once the far end accepts, the access point becomes **Active** and the connection is ready to use.
