Two separate virtual routers without on-prem redundancy
Written by
Updated at August 21, 2026
Two separate independent network topologies. In each topology, there is a private connection on one side of the virtual router and a virtual cloud network on the other.
The network topology is presented on the diagram in the following configuration:
On-Premclient with two local subnets:subnet-c1andsubnet-c2.- The on-prem network hardware connects to the Yandex Cloud network hardware via Cloud Interconnect.
- Private connection
prc-m9-1established via theM9point of presence connects to virtual router 1 in Yandex Cloud. - On the Yandex Cloud side, the
Net-1virtual network comprised of three subnets,subnet-a1,subnet-b1, andsubnet-d1, connects to virtual router 1. - Private connection
prc-m9-2established via theM9point of presence connects to virtual router 2 in Yandex Cloud. - On the Yandex Cloud side, the
Net-2virtual network comprised of three subnets,subnet-a2,subnet-b2, andsubnet-d2, connects to virtual router 2.
This creates two network topologies (based on the number of virtual routers used):
- Topology 1 enables connectivity between on-prem subnets and
Net-1VPC subnets via virtual router 1. - Topology 2 enables connectivity between on-prem subnets and
Net-2VPC subnets via virtual router 2.
These topologies do not enable network connectivity between the subnets of virtual networks Net-1 and Net-2.
Note
If needed, the customer can establish network connectivity between Net-1 and Net-2 VPC subnets by setting up routing between private connections on their network hardware.