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:
Creating a new partner trunk
Getting 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.
Warning
To ensure fault tolerance, we recommend setting up trunk links, i.e. direct or partner trunks, at two points of presence.
- 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 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 ticket
Once the trunk setup has been completed, the support team will provide you the following information:
trunk_id
: Trunk IDservice_key
: Trunk service keycapacity
: 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 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.
Note
Currently, we do not provide monitoring metrics for partner trunks.
For private and public connections, we provide the monitoring metrics service in full.
Setting up a public connection
To add a public connection to an existing trunk, create a new support ticket
Contacting 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.1QVLAN-ID
. This value is selected by the customer. It must be different from theVLAN-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 isfalse
, 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 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 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.