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

# Creating a direct trunk and a private connection in it

The process of activating the Yandex Cloud Interconnect service can be logically divided into the following stages:

1. [Creating a direct trunk](#trunk-create).
1. [Creating a private connection in the trunk](#priv-create).

## Setting up a direct trunk {#trunk-create}

In this tutorial, we will set up a direct trunk.

### Getting started {#trunk-prep}

* See our [guides](../../interconnect/concepts/index.md) to learn how this service works.
* Select a [point of presence](../../interconnect/concepts/pops.md) for the [trunk](../../interconnect/concepts/trunk.md).
* Select the type of an [optical transceiver](../../interconnect/concepts/transceivers.md) for Yandex Cloud equipment cross-connection in the [point of presence](../../interconnect/concepts/pops.md). We will reserve a compatible transceiver port for you on the Yandex Cloud endpoint. You will need to buy a compatible transceiver to install on your endpoint.
* Select the [connection capacity](../../interconnect/concepts/capacity.md).
* 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 {#trunk-ticket}

Create a [new support ticket](https://center.yandex.cloud/support) to reserve a port on the Yandex Cloud equipment and set up a trunk.

Follow this request format:




Where:

* `client`: Company name.
* `folder-id`: [ID of the folder](../../resource-manager/operations/folder/get-id.md) that will receive Cloud Interconnect monitoring metrics.
* `point of presence`: [Point of presence code](../../interconnect/concepts/pops.md).
* `transceiver type`: [Type of a cross connect transceiver](../../interconnect/concepts/transceivers.md).
* `connection capacity`: [Bandwidth](../../interconnect/pricing.md) in Mbps.


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

Once the trunk setup has been completed, the support team will send you the following information.

Support response example:



Where: 

* `trunk_id`: New Cloud Interconnect trunk ID.
* `pop`: [Point of presence](../../interconnect/concepts/pops.md) code.
* `rack`: Yandex Cloud equipment location at the point of presence.
* `unit`: Number between 1 and 45 that shows where your equipment is located in the Yandex Cloud rack.
* `port`: Number between 1 and 48 specifying the port number for cross connection.


### Monitoring the trunk status {#trunk-check}

Use the [monitoring](../../interconnect/concepts/monitoring.md#trunk-mon) service to track when the physical port of the trunk on the Yandex Cloud endpoint transitions to the operational state. If there are any issues, contact support for diagnostics and troubleshooting.

A private or public connection can only be established after the physical port of the trunk becomes operational.

## 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.