Creating a direct trunk and a public connection in it

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

1. Setting up a trunk.
2. Setting up a public connection in the trunk.

Setting up a direct trunkSetting up a direct trunk

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

Getting startedGetting started

• See our guides to learn how this service works.

• Contact your Yandex Cloud manager to choose your pricing plan and connection capacity.

• Select a point of presence for the trunk.

  Warning

  To ensure fault tolerance, we recommend setting up trunk links at two points of presence.

• Select the type of an optical transceiver for Yandex Cloud equipment cross-connection in the point of presence. 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.

• 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 trunkContacting support for a new partner trunk

Create a new support ticket to reserve a port on the Yandex Cloud equipment and set up a trunk.

Follow this request format:

Subject: [CIC] Creating a new trunk.

Request text:
Please set up a new Cloud Interconnect trunk
with the following parameters:

client: My Business LLC 
folder-id: b1g28j9359gi********
point of presence: M9
transceiver type: 10GBASE-LR
connection capacity: 250mbps

I will send the private connection details later in a separate ticket.

Where:

• client: Company name.
• folder-id: ID of the folder that will receive Cloud Interconnect monitoring metrics.
• point of presence: Point of presence code.
• transceiver type: Type of a cross connect transceiver.
• connection capacity: Bandwidth in Mbps.

Support team's response to the your ticketSupport team's response to the your ticket

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

Support response example:

trunk_id: euus5dfgchu2********
pop: M9
rack: 10th floor, room 30-1, row 11, space 10
unit: 36
port: 18

Where:

• trunk_id: New Cloud Interconnect trunk ID.
• pop: Point of presence 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.

How to write an agreement letter for a point of presenceHow to write an agreement letter for a point of presence

• Download the agreement letter form for the relevant point of presence in .docx format.
• In the form, fill in the highlighted yellow fields, providing information about your company and your equipment location in the point of presence.
• Using the information provided by the support team, fill in the unit and port highlighted green fields.
• Attach the completed form to your open support ticket.
• Within two business days, you will receive the letter of authorization in PDF format signed by Yandex Cloud as an attachment to your open support ticket.

Setting up a cross connect in a point of presenceSetting up a cross connect in a point of presence

Using the signed agreement letter you received, request setting up an interconnect between your equipment and Yandex Cloud infrastructure at the point of presence.

Monitoring the trunk statusMonitoring the trunk status

Use the monitoring 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.

Setting up a public connectionSetting up a public connection

To add a public connection to an existing trunk, create a new support ticket.

Contacting support for a public connectionContacting support for a public connection

Follow this request format:

Subject: [CIC] Add a public connection to an existing trunk.

Request text:
Please add a public connection to an existing trunk.
Connection settings:

trunk_id: euus5dfgchu2********
vlan_id: 101
ipv4_peering:
  peer_bgp_asn: 65001
  #cloud_bgp_asn: 200350
allowed-public-services:
  - storage.yandexcloud.net
  - transcribe.api.cloud.yandex.net
is_nat_extra_ip_required: false

Where:

• trunk_id: Trunk ID you got from support in the previous step.
• vlan_id: Public trunk connection 802.1Q VLAN-ID. This value is selected by the customer. It must be different from the VLAN-ID values of other private connections in this trunk.
• peer_bgp_asn: Customer endpoint BGP ASN in ASPlain format. This value is selected by the customer.
• allowed-public-services: FQDN API Endpoints of services you want to access through this public connection.
• is_nat_extra_ip_required: Indicates whether the customer needs a /32 subnet prefix (in addition to the point-to-point /31 subnet prefix) to implement NAT. By default, this value is false, which means no additional subnet prefix is allocated.
• folder_id (optional): Folder to store public connection monitoring metrics. If left empty, monitoring metrics will be stored in the folder you specified when creating the trunk.

Support team's response to your ticketSupport team's response to your ticket

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

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

id: cf3qdug4fsf7********
ipv4_peering:
  peering_subnet: 178.210.118.46/31
  peer_ip: 178.210.118.46
  cloud_ip: 178.210.118.47
  peer_bgp_asn: 65001
  #cloud_bgp_asn: 200350
allowed-public-services:
  - storage.yandexcloud.net
  - transcribe.api.cloud.yandex.net

Where:

• id: Public connection ID.
• peering_subnet: Point-to-point BGP peering subnet prefix from the Yandex Cloud address pool.
• peer_ip: Customer endpoint IP address on the point to point BGP peering subnet assigned by Yandex Cloud.
• cloud_ip: Yandex Cloud endpoint on the point to point BGP peering subnet assigned by Yandex Cloud.
• nat_subnet: Additional Yandex Cloud pool subnet prefix to implement NAT.
• allowed-public-services: FQDN API Endpoints of services accessible through the new public connection.

Public connection status monitoringPublic connection status monitoring

• Use the monitoring service to see when your public connection BGP session starts on the Yandex Cloud endpoint.
• The support team will notify you once they provide access to the requested Yandex Cloud services. The configuration process usually takes up to one business day.
• Check whether the Yandex Cloud services are accessible from your endpoint through the new public connection and inform the support team about the results.
• If there are any IP connectivity issues, contact support for diagnostics and troubleshooting.