Adding a public connection to a direct or partner trunk

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.