[Yandex Cloud documentation](../../index.md) > [Yandex Virtual Private Cloud](../index.md) > [Tutorials](index.md) > Cloud Interconnect > Creating a new partner trunk and a private connection in it

# Creating a partner trunk and a private connection in it

Yandex Cloud Interconnect activation follows these logical steps:

1. [Setting up a partner trunk](#trunk-create).
1. [Creating a private connection in the new trunk](#priv-create).

## Creating a new partner trunk

### Getting started {#trunk-prep}

* See our [guides](../../interconnect/concepts/index.md) to learn how this service works.
* Contact your Yandex Cloud manager to choose your pricing plan and [connection capacity](../../interconnect/pricing.md).
* Using [this list](../../interconnect/concepts/partners.md#list), find a partner that can set up a trunk at your selected [point of presence](../../interconnect/concepts/pops.md) with the required [capacity](../../interconnect/concepts/partners.md#list). To **ensure fault tolerance**, we recommend setting up trunk links at two points of presence.
* If you work with a Yandex Cloud solution architect, discuss with them and agree on a Yandex Cloud Interconnect service setup plan.

### Contacting support for a new partner trunk {#partner-trunk-ticket}

Create a new partner trunk [support ticket](https://center.yandex.cloud/support).


Follow this request format:

```text
Subject: [CIC] Creating a new partner trunk.

Request text:

Please set up a new Cloud Interconnect partner trunk 
with the following settings:

client: My Business LLC 
folder-id: b1g28j9359gi********
partner: RETN
point of presence: M9
connection capacity: 250mbps
```

Where:

* `client`: Company name.
* `folder-id`: [ID of the folder](../../resource-manager/operations/folder/get-id.md) that will receive Cloud Interconnect monitoring metrics.
* `partner`: Name of your Cloud Interconnect [partner](../../interconnect/concepts/partners.md#list).
* `Point of presence`: Code of the point of presence where your [partner](../../interconnect/concepts/partners.md#list) can provide connections to Yandex Cloud.
* `Connection capacity`: [Bandwidth](../../interconnect/pricing.md) in Mbps.


### Support team’s response to your ticket {#partner-trunk-ticket-resp}

Once the trunk setup has been completed, the support team will provide you the following information:
* `trunk_id`: Trunk ID
* `service_key`: Trunk service key
* `capacity`: [Trunk capacity](../../interconnect/concepts/capacity.md)

Here is an example of the support response to the request for a new partner trunk (for reference only):

```s
trunk_id: euus5dfgchu2********
service_key: euuq3f6g1zk8********
capacity: 500mbps
```

Once the partner trunk has been created, the support team will provide your partner the following information:
`partner_joint_id`, `partner_vlan_id`, `capacity`, and `service_key`.

### Requesting the partner to configure the new partner trunk {#client-req-partner}

Once you have received the Yandex Cloud support response, you should request your partner to activate and configure their side of the partner trunk. In your request, provide the `service_key` you got in the previous step.

Once your partner has processed your request, they will notify you, following which you should coordinate with your partner and establish a connection between your respective endpoints.

To communicate with your partner, you can arrange a mutually convenient means, such as email.


{% note info %}

Currently, [we do not provide](../../interconnect/concepts/monitoring.md#notes) monitoring metrics for partner trunks.
For private and public connections, we provide the monitoring metrics service [in full](../../interconnect/concepts/monitoring.md#private-metrics).

{% endnote %}

## Setting up a private connection {#priv-create}

To add a private connection to an existing trunk, create a [new support ticket](https://center.yandex.cloud/support).

### Contacting support for a new private connection {#priv-ticket}

Follow this request format:




Where:

* `trunk_id`: Trunk ID you got from support in the previous step.
* `vlan_id`: Private trunk connection 802.1Q `VLAN-ID`. This value is selected by the customer. It must be different from `VLAN-ID` values of other private connections in this trunk.
* `peering_subnet`: [Point-to-point subnet](../../interconnect/concepts/priv-con.md#priv-address) for BGP peering. This value is selected by the customer.
* `peer_ip`: Customer endpoint IP address on the point to point BGP peering subnet. This value is selected by the customer.
* `cloud_ip`: Yandex Cloud endpoint IP address on the point-to-point BGP peering subnet. This value is selected by the customer.
* `peer_bgp_asn`: Customer endpoint [BGP ASN](../../interconnect/concepts/priv-con.md#bgp-asn) in ASPlain format. This value is selected by the customer.
* `vpc_net_id`: ID of the Yandex Virtual Private Cloud network for a private connection.
* `vpc_subnets`: List of IPv4 subnet prefixes grouped by Yandex Cloud [availability zones](../../overview/concepts/geo-scope.md). The resources in these subnets will only be accessible through your private connection. These prefixes will be announced over BGP from Yandex Cloud to the customer endpoint.
* Optionally, `folder_id`: By default, private connection monitoring metrics will be saved to the folder specified when creating the trunk. If required, you can explicitly specify the folder to save private connection monitoring metrics to.

### Support team's response to your ticket {#priv-ticket-resp}

Once the new private connection has been added, the support team will message you its ID

Here is an example of the support response to the request for a new private connection (for reference only):
```s
A new private connection has been successfully added to the trunk.
Connection ID: cf3qdug4fsf7********
```

### Private connection status monitoring {#priv-check}

* Use the [monitoring service](../../interconnect/concepts/monitoring.md#private-mon) to see when your private connection BGP session starts on the Yandex Cloud endpoint.
* The support team will notify you once they finish configuring BGP announcements for the subnet prefixes you requested. It may take up to two business days to configure BGP announcements.
* Check whether the cloud resources are accessible from your endpoint through the new private connection and inform the support team about the results.
* If there are any IP connectivity issues, contact support for diagnostics and troubleshooting.