Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI Studio
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Router
    • All use cases
    • On-prem without redundancy and 1 VPC
    • On-prem without redundancy and multiple VPCs
    • On-prem with redundancy and 1 VPC
    • On-prem with redundancy and multiple VPCs
    • Two separate RIs without on-prem redundancy
    • Even redistribution of on-prem traffic (Active-Active)
    • Prioritizing on-prem traffic based on direction (Active-Standby)
    • On-prem (PRC) connection redundancy via a VPN gateway
    • Prioritizing a static VPC route over routes from PRC
    • Even traffic distribution for route 0.0.0.0/0
    • Prioritizing traffic by direction for route 0.0.0.0/0
    • VPC Stithcing. Connectivity for two cloud networks
    • VPC Stitching. Connectivity for two cloud networks and on-prem
  • Access management
  • Release notes
  1. Use cases
  2. On-prem with redundancy and 1 VPC

On-prem with redundancy and 1 VPC

Written by
Yandex Cloud
Updated at June 10, 2025

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

The network topology is presented on the diagram in the following configuration:

  • 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.
  • 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.

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.

Was the article helpful?

Previous
On-prem without redundancy and multiple VPCs
Next
On-prem with redundancy and multiple VPCs
© 2025 Direct Cursus Technology L.L.C.