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

This guide explains how to set up a direct trunk.

Getting startedGetting started

• See the documentation to learn how the service works.

• Contact your Yandex Cloud manager to agree upon the pricing plan (connection capacity).

• Select a point of presence for connecting a trunk.

  Warning

  To ensure fault tolerance, connect trunks in two points of presence.

• Select the type of an optical transceiver to enable a cross connect to the Yandex Cloud equipment in the point of presence. A port of the selected type will be reserved for you on the Yandex Cloud equipment side. For installation on your equipment, purchase the transceiver of the selected type on your own.

• If a Yandex Cloud solution architect is working with you, discuss and agree on a Yandex Cloud Interconnect service setup diagram.

Contacting tech support to set up a new trunkContacting tech support to set up a new trunk

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

Write a support request as follows:

Subject: [CIC] Creating a new trunk.

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

client: My Company Ltd
folder-id: b1g28j9359gic3p2gca2
point of presence: M9
transceiver type: 10GBASE-LR
connection capacity: 250mbps

The details for a private connection will be provided later in a separate ticket.

Where:

• client: Company name.
• folder-id: ID of the folder to send Cloud Interconnect monitoring metrics to.
• point of presence: Code of the point of presence.
• transceiver type: Type of transceiver to enable a cross connect.
• connection capacity: Bandwidth in Mbps.

Tech support team's response to the customer's requestTech support team's response to the customer's request

Once the requested trunk is set up, the support team will send you information about the created trunk.

Sample response from the support team:

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

Where:

• trunk_id: ID of the created Cloud Interconnect trunk.
• pop: Code of the point of presence where the Cloud Interconnect trunk is created.
• rack: Location of the Yandex Cloud equipment in the point of presence.
• unit: Number from 1 to 45 that indicates the equipment location in the Yandex Cloud rack.
• port: Number from 1 to 48 that specifies the port number on the equipment to enable the cross connect for.

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 point of presence you need in .docx format.
• In the form, specify your company data and equipment location in the point of presence (highlighted in yellow).
• Using the information received from the support team, set the unit and port parameter values in the form (highlighted in green).
• Attach the completed form to the open support request.
• Within two business days, you will receive the agreement letter in PDF format signed by Yandex Cloud as an attachment to the open support request.

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

Request and set up a cross connect between your equipment and Yandex Cloud in the point of presence you need using the agreement letter you received.

Monitoring the trunk statusMonitoring the trunk status

Use the monitoring service to track when the trunk's physical port on the Yandex Cloud equipment switches to the running status. If there are any issues, contact support so that they may run diagnostics and troubleshooting.

Setting up a public connectionSetting up a public connection

To set up a new public connection in an existing trunk, create a new support request.

Contacting tech support to set up a public connectionContacting tech support to set up a public connection

Write a support request as follows:

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

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

trunk_id: euus5dfgchu23b81d472
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 received from the support team at the previous step.
• vlan_id: VLAN-ID for the public connection in trunk 802.1Q. This value is selected by the customer. It must be different from the VLAN-ID values of the private connections previously set up in this trunk.
• peer_bgp_asn: BGP ASN on the customer's equipment in ASPlain format. This value is selected by the customer.
• allowed-public-services: List of API Endpoint FQDNs for the services from the table to provide access to via this public connection.
• is_nat_subnet_required: Determines whether the customer needs to be allocated an additional /32 service address (prefix) apart from the point-to-point /31 subnet, to implement NAT functions. By default, no additional service prefix is allocated (the value is false).
• folder_id (optional): By default, public connection monitoring metrics will be saved to the folder specified when creating a trunk. If required, you can explicitly specify the folder to save the public connection monitoring metrics to.

Support team's response to the customer's requestSupport team's response to the customer's request

Once all the actions required to set to set up a public connection are completed, the support team provides the customer with the ID of the connection created.

Here is how the support team may respond to the request for creating a public connection (this sample is provided for indicative purposes only):

id: cf3qdug4fsf737g2gpdu
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: ID of the created public connection.
• peering_subnet: Point-to-point subnet for BGP peering, which is allocated from the Yandex Cloud address pool.
• peer_ip: IP address of the point-to-point (peering) subnet on the customer's equipment. It is assigned by Yandex Cloud.
• cloud_ip: IP address of the point-to-point (peering) subnet on the Yandex Cloud equipment. It is assigned by Yandex Cloud.
• nat_subnet: Additional subnet allocated from the Yandex Cloud public address space to implement NAT functions.
• allowed-public-services: List of API Endpoint FQDNs from the customer request for the services to provide access to via the created public connection.

Monitoring the status of a public connectionMonitoring the status of a public connection

• Use the monitoring service to monitor, on your own, when the public connection BGP session on the Yandex Cloud equipment switches to the running status.
• The support team will notify you once they finish configuring access to the requested Yandex Cloud services. The configuration process usually takes up to one business day.
• Make sure to check the IP connectivity between your equipment and the Yandex Cloud services to be accessed over the configured public connection, and notify the support team of the check results.
• If there are any IP connectivity issues, contact support so that they may run diagnostics and troubleshooting.