Routing instance

The routing instance (RI) object is a core resource in the Cloud Router resource model. It is designed to create network topologies enabling network connectivity between cloud resources in different networks.

General rules and recommendationsGeneral rules and recommendations

The following rules and recommendations apply to Cloud Router and Cloud Interconnect:

1. Consistent IP addressing. Subnet IP prefixes you add to an RI must be coordinated between themselves. You cannot add two identical IP prefixes to a single RI. IP addressing on On-Prem side must be coordinated with IP addressing in the virtual cloud networks. IP address overlapping will cause IP connectivity problems. Plan IP addressing carefully.

2. Network communication across virtual networks is strictly confined to a single cloud organization. All Cloud Router and Cloud Interconnect resources, as well as the virtual cloud networks that are going to be integrated into a network topology using an RI, must reside in cloud folders within the same cloud organization. For network connectivity between virtual cloud networks belonging to different cloud organizations, consider migrating clouds from several organizations into a single one.

   If such migration is not feasible, you have to obtain formal written consents (on paper) from owners of all such cloud organizations for cross-organization networking. For detailed information about the verification procedure, contact Yandex Cloud support.

3. No direct exchange of routing info between any private connections (PRCs) within an RI is allowed.

4. The IP prefixes announced by the client’s network hardware also get into the RI and from there to the virtual networks connected to that RI. Currently, you cannot view these IP prefixes at the RI level. We recommend getting this information from the client's network hardware. In some cases, if routing issues arise, you may contact support for this information.

5. You can communicate with an RI via the CLI and API calls. For a list of available operations, see step-by-step guides.

RI network topologiesRI network topologies

Here is a list of network topologies you can create using an RI:

No.	Topology type	Short description
1	OnPrem-1xRI-1xVPC-1xPRC	Non-reserved on-prem connection (private Cloud Interconnect connection) to one RI with one cloud network.
2	OnPrem-1xRI-2xVPC-1xPRC	Non-reserved on-prem connection (private Cloud Interconnect connection) to one RI with two or more cloud networks without network connectivity to each other.
3	OnPrem-1xRI-1xVPC-2xPRC	Reserved on-prem connection (two private Cloud Interconnect connections) to one RI with one cloud network.
4	On-Prem-1xRI-2xVPC-2xPRC	Reserved on-prem connection (two private Cloud Interconnect connections) to one RI with two or more cloud networks without network connectivity to each other.
5	OnPrem-2x(1xRI-1xVPC-1xPRC)	Two separate non-reserved on-prem connections (each private Cloud Interconnect connection to a separate RI) without network connectivity between cloud networks.

OnPrem-1xRI-1xVPC-1xPRC [1]OnPrem-1xRI-1xVPC-1xPRC [1]

Non-reserved on-prem connection via a single Cloud Interconnect private connection to a single RI with a single VPC cloud network.

• On-Prem client with two local subnets: subnet-c1 and subnet-c2.
• The On-Prem network hardware is connected to the Yandex Cloud network hardware via Cloud Interconnect.
• The prc-m9 private connection established via the M9 point of presence connects to RI in Yandex Cloud.
• The Net-1 virtual network comprised of three subnets, subnet-a1, subnet-b1, and subnet-d1, connects to RI on the Yandex Cloud side.

This topology enables network connectivity between On-Prem subnets and Net-1 VPC subnets.

OnPrem-1xRI-2xVPC-1xPRC [2]OnPrem-1xRI-2xVPC-1xPRC [2]

Non-reserved on-prem connection via a single Cloud Interconnect private connection to a single RI with two or more cloud networks without network connectivity between them.

• On-Prem client with two local subnets: subnet-c1 and subnet-c2.
• The On-Prem network hardware is connected to the Yandex Cloud network hardware via Cloud Interconnect.
• The prc-m9 private connection established via the M9 point of presence connects to RI in Yandex Cloud.
• Two virtual networks connect to RI on the Yandex Cloud side:
  • Net-1 comprised of three subnets: subnet-a1, subnet-b1, and subnet-d1.
  • Net-2 comprised of three subnets: subnet-a2, subnet-b2, and subnet-d2.

This topology enables network connectivity between:

• On-Prem subnets and Net-1 VPC subnets subnet-a1, subnet-b1, and subnet-d1.
• On-Prem subnets and Net-2 VPC subnets subnet-a2, subnet-b2, and subnet-d2.

This topology enables network connectivity between Net-1 and Net-2 virtual networks subnets.

OnPrem-1xRI-1xVPC-2xPRC [3]OnPrem-1xRI-1xVPC-2xPRC [3]

Reserved on-prem connection via two Cloud Interconnect private connections to a single RI with a single cloud network.

• On-Prem client with two local subnets: subnet-c1 and subnet-c2.
• The On-Prem network hardware connects to the Yandex Cloud network hardware via Cloud Interconnect.
• Two private connections called prc-m9 and prc-nord via the M9 and NORD points of presence connect to RI in Yandex Cloud.
• On the Yandex Cloud side, the Net-1 virtual network comprised of three subnets, subnet-a1, subnet-b1, and subnet-d1, connects to RI.

This topology enables network connectivity between On-Prem subnets and Net-1 VPC subnets.

Use appropriate Cloud Interconnect routing tools to prioritize traffic between private connections.

In case of failure of any of the private connections above, all network traffic will be automatically switched over to the remaining private connection.

On-Prem-1xRI-2xVPC-2xPRC [4]On-Prem-1xRI-2xVPC-2xPRC [4]

Reserved on-prem connection via two Cloud Interconnect private connections to a single RI with two or more cloud networks without network connectivity between them.

• On-Prem client with two local subnets: subnet-c1 and subnet-c2.
• The On-Prem network hardware connects to the Yandex Cloud network hardware via Cloud Interconnect.
• Two private connections, prc-m9 and prc-nord, established via two points of presence, M9 and NORD, connect to RI in Yandex Cloud.
• Two virtual networks connect to RI on the Yandex Cloud side:
  • Net-1 comprised of three subnets: subnet-a1, subnet-b1, and subnet-d1.
  • Net-2 comprised of three subnets: subnet-a2, subnet-b2, and subnet-d2.

This topology enables network connectivity between:

• On-Prem subnets and Net-1 VPC subnets subnet-a1, subnet-b1, and subnet-d1.
• On-Prem subnets and Net-2 VPC subnets subnet-a2, subnet-b2, and subnet-d2.

In case of failure of any of the private connections above, all network traffic will be automatically switched over to the remaining private connection.

This topology enables network connectivity between Net-1 and Net-2 virtual networks subnets.

OnPrem-2x(1xRI-1xVPC-1xPRC) [5]OnPrem-2x(1xRI-1xVPC-1xPRC) [5]

Two separate independent network topologies. In each topology, there is a private connection connected to RI on one side and a virtual cloud network on the other.

• On-Prem client with two local subnets: subnet-c1 and subnet-c2.
• The On-Prem network hardware connects to the Yandex Cloud network hardware via Cloud Interconnect.
• The prc-m9-1 private connection via the M9 point of presence connects to Routing Instance 1 in Yandex Cloud.
• The Net-1 virtual network comprised of three subnets, subnet-a1, subnet-b1, and subnet-d1, connects to RI 1 on the Yandex Cloud side.
• The prc-m9-2 private connection via the M9 point of presence connects to Routing Instance 2 in Yandex Cloud.
• The Net-2 virtual network comprised of three subnets, subnet-a2, subnet-b2, and subnet-d2, connects to RI 2 on the Yandex Cloud side.

This creates two network topologies (based on the number of RIs used):

• Topology 1 enables network connectivity between On-Prem subnets and Net-1 VPC subnets via RI 1.
• Topology 2 enables network connectivity between On-Prem subnets and Net-2 VPC subnets via RI 2.

These topologies do not enable network connectivity between Net-1 and Net-2 virtual networks subnets.