Creating a partner trunk and a private connection in it

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

1. Setting up a partner trunk.
2. Setting up a private connection in the created trunk.

Creating a new partner trunkCreating a new partner 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.
• Using this list, find a partner that can set up a trunk at your selected point of presence with the required capacity.

• 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 partner trunk support ticket.

Follow this request format:

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 that will receive Cloud Interconnect monitoring metrics.
• partner: Name of your Cloud Interconnect partner.
• Point of presence: Code of the point of presence where your partner can provide connections to Yandex Cloud.
• Connection capacity: Bandwidth in Mbps.

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

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

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

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 trunkRequesting the partner to configure the new partner trunk

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.

Setting up a private connectionSetting up a private connection

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

Contacting support for a new private connectionContacting support for a new private connection

Follow this request format:

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

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

trunk_id: euus5dfgchu2********
vlan_id: 101
ipv4_peering:
  peering_subnet: 192.168.10.0/30
  peer_ip: 192.168.10.1
  cloud_ip: 192.168.10.2
  peer_bgp_asn: 65001
  #cloud_bgp_asn: 200350
vpc:
  vpc_net_id: enpdffqsg8r2********
    vpc_subnets:
      ru-central1-a: [10.60.192.0/21]
      ru-central1-b: [10.60.200.0/21, 10.60.220.0/24]
      ru-central1-d: [10.60.208.0/20]

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 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 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. 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.
• folder_id (optional): Folder to store private 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 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):

A new private connection has been successfully added to the trunk.
Connection ID: cf3qdug4fsf7********

Private connection status monitoringPrivate connection status monitoring

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