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 the documentation to learn how the service works.
• Contact your Yandex Cloud manager to agree upon the pricing plan (connection capacity).
• Select a partner from the list, and make sure they can set up a trunk at the proper point of presence and with the required capacity.

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

Contacting support for a new partner trunkContacting support for a new partner trunk

Create a new support request for a new partner trunk.

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 parameters:

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

Where:

• client: Company name.
• folder-id: ID of the folder to send Cloud Interconnect monitoring metrics to.
• partner: Name of the partner from the partner list.
• Point of presence: Code of the point of presence from the partner list, where the partner provides connections to Yandex Cloud.
• 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 all requested actions are completed for a partner trunk, support will communicate to the customer:

• Trunk ID: trunk_id
• Trunk service key: service_key
• Trunk capacity: capacity

Here is an example of support's response when requested to create a partner trunk (for information):

trunk_id: euus5dfgchu23b******
service_key: euuq3f6g1zk8dbr******
capacity: 500mbps

Once the partner trunk is created, support will communicate its parameters to the partner. Here is the list of parameters:
partner_joint_id, partner_vlan_id, capacity, and service_key.

Customer's request to the partner to perform the partner trunk setupCustomer's request to the partner to perform the partner trunk setup

After Yandex Cloud support has responded, the customer requests the partner to activate (configure) the partner trunk on the partner's side. The request must feature the service_key obtained in the previous step.

The customer waits for the partner to acknowledge the request and follows up with the partner to establish the connection from the partner's to the customer's hardware.

The communication channel between the customer and partner will be such as agreed between them, e.g., by email.

Establishing a private connectionEstablishing a private connection

To establish a new private connection in an existing trunk, create a new support request.

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 parameters:

trunk_id: euus5dfgchu23b******
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: enpdffqsg8r221******
    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 the support team in the previous step.
• vlan_id: VLAN-ID for this private 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.
• peering_subnet: Point-to-point subnet for BGP peering. This value is selected by the customer.
• peer_ip: IP address of the point-to-point (peered) subnet on the customer's equipment. This value is selected by the customer.
• cloud_ip: IP address of the point-to-point (peered) subnet on the Yandex Cloud equipment. This value is selected by the customer.
• peer_bgp_asn: BGP ASN on the customer's equipment 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 via this private connection. These prefixes will be announced over BGP by the Yandex Cloud equipment in the direction towards the customer's equipment.
• folder_id (optional): 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 the customer's requestSupport team's response to the customer's request

Once you complete all required actions for setting up a private connection, the support team will provide the customer with the ID of the created private connection.

Here is an example of support's response when requested to create a private connection (for information):

Adding a private connection to the trunk completed successfully.
Connection ID: cf3qdug4fsf737******

Monitoring the status of a private connectionMonitoring the status of a private connection

• Use the monitoring service to monitor, on your own, when the private connection BGP session on the Yandex Cloud equipment switches to the running status.
• 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.
• You should check the IP connectivity between your equipment and the cloud resources to be accessible through the configured private connection yourself and notify the support team of the check results.
• If there are any IP connectivity issues, contact support for diagnostics and troubleshooting.