Adding a public connection to a direct or partner trunk

Setting up a public connectionSetting up a public connection

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

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 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.1Q VLAN-ID. This value is selected by the customer. It must be different from the VLAN-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 is false, 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 ticketSupport 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 monitoringPublic 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.