Creating a partner 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 partner trunk.
2. Setting up a public connection in the created trunk connection.

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.

Setting up a public connectionSetting up a public connection

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

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

trunk_id: euus5dfgchu23b******
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: VLAN-ID for this 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 FQDN API Endpoint for the services from the table to provide access to via this public connection.
• is_nat_extra_ip_required: Indicates whether the customer needs 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 an example of support's response when requested to create a public connection (for information):

id: cf3qdug4fsf737******
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 new 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 (peer) subnet on the customer's equipment. It is assigned by Yandex Cloud.
• cloud_ip: IP address of the point-to-point (peer) subnet on the Yandex Cloud equipment. It is assigned by Yandex Cloud.
• nat_subnet: Additional subnet allocated from the Yandex Cloud address pool to implement NAT functions.
• allowed-public-services: List of FQDN API Endpoints from the customer request for the services access was provided 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 for diagnostics and troubleshooting.