Link the public cloud to other products via a new subnet to connect virtual machines without a client Edge router

Last update: May 27 2025

Link the public cloud to other products via a new subnet to connect virtual machines without a client Edge router

With the Selectel Global Router, you can link the public cloud with other Selectel products that can be connected to the Global Router, see the Selectel Global Router Service General Information instructions for more information.

There are several scenarios to configure connectivity, see the instructions Ways to connect a public cloud to a global router for other scenarios.

Customization Description⁠

At your request, we will create a private subnet of the public cloud, which will be visible in the list of networks in your virtual data center.The subnet will connect virtual machines directly to the Service Edge router, which is managed by Selectel.The Service Edge router will be the gateway.The network address and address for the Service Edge router will be determined by you and will be reported in the ticket for creating the new subnet.

You will not be able to control the routing of the subnet you create — only add virtual machines to it.Virtual machines that you add to this subnet can simultaneously be added to other subnets in the public cloud.

What you need to customize⁠

You can use any infrastructure that you want to link to the public cloud via a global router for configuration.The infrastructure elements and its network settings are shown for example.

Infrastructure element	Infrastructure network parameters in the example
Dedicated server on a private subnet	the server is added to the 192.168.0.0/24 subnet. gateway: 192.168.0.1
Cloud server on a private subnet	the server is added to the 192.168.1.0/24 subnet. gateway: 192.168.1.1
A virtual machine in the public cloud	the virtual machine is not added to the subnet
A virtual machine in the public cloud on a private subnet	virtual machine is added to subnet 192.168.20.0/24 gateway: 192.168.20.100

Customization result⁠

In the example, the dedicated server, cloud server, and public cloud virtual machine will be connected through a global router using a new public cloud subnet.

Customization steps⁠

1. Create a global router.
2. Connect the subnets of the dedicated server and cloud platform to a global router.
3. Create a new subnet to communicate with the global router.
4. Connect the virtual machines to the new subnet.
5. If the virtual machine is added to other subnets, write routes on the virtual machine.
6. Write static routes on dedicated and cloud servers.

1. Create a global router⁠

Use the instructions Create a global router.

2. Connect the subnets of the dedicated server and cloud platform to the global router⁠

To connect the dedicated server subnet ( 192.168.0.0/24 in the example) and the cloud platform subnet ( 192.168.1.0/24 in the example ) to a global router, use the Connect Networks and Subnets to a Global Router section of the Connecting Products and Services through a Global Router instructions.

3. Create a new subnet to communicate with the global router⁠

1. Create a ticket requesting the creation of a new private subnet in the public cloud that will connect the Service Edge router to the virtual machines. In the ticket, specify:

   • The way to connect the public cloud to the global router is the first way;
   • Global router ID, can be viewed in the control panel under Network Services → Selectel Global Router → router page → router page → field under router name;
   • virtual data center name, can be viewed in the Control Panel under VMware-based Cloud → Virtual Data Centers → Virtual Data Center Card;
   • the desired CIDR of the new subnet — in the example 192.168.2.0.0/24;
   • the desired subnet gateway, this address will be assigned to the Service Edge router — in the example 192.168.2.1;
   • optional: name for the subnet.

2. We will create the subnet and report it in the ticket. The subnet will appear in Cloud Director in the list of virtual data center subnets.

4. Connect the virtual machine to the new subnet⁠

1. From the Control Panel, open the Cloud Director panel: from the top menu, click Products → VMware-based Cloud → Cloud Director.
2. Open the virtual data center page.
3. Go to Compute → Virtual Machines.
4. Open the page of the virtual machine you want to associate with the global router.
5. Go to VM Hardware → NICs.
6. Press EDIT.
7. Optional: to create a new port, press NEW.
8. In the port row, in the Adapter Type column, select VMXNET3.
9. In the port row in the Network column, select the subnet that was created through the ticket.
10. In the port line in the IP column, enter the address for the virtual machine from the created subnet 192.168.2.0.0/24 — in the example 192.168.2.2.2.
11. Click Save.
12. If you added networking to a powered on virtual machine, turn it off and on with recastomization. The network interface and its settings will be added to the virtual machine.

5. Write routes on the virtual machine⁠

If the public cloud virtual machine is only added to the new subnet we created at your request via ticket, skip this step.

If a public cloud virtual machine is added not only to the new public cloud virtual machine but also to other public cloud subnets that are connected to your Edge router, you will need to prescribe static routes.

The route configuration options depend on which gateway you choose as the Default Gateway:

• the address of your (client) Edge router — in the example 192.168.20.1
• or the address of the service Edge router — in the example 192.168.2.1

Client Edge router address

1. From the Control Panel, open the Cloud Director panel: from the top menu, click Products → VMware-based Cloud → Cloud Director.
2. Open the virtual data center page.
3. Go to Compute → Virtual Machines.
4. Open the page of the virtual machine you want to associate with the global router.
5. Go to VM Hardware → NICs.
6. Press EDIT.
7. In the row with the subnet that is connected to the client Edge router and is not connected to the global router, check the Primary NIC checkbox.
8. In the virtual machine, write static routes to the subnets of servers and other services that are associated with the global router through the address of the Service Edge router — in the example 192.168.2.1.

Service Edge router address

1. From the Control Panel, open the Cloud Director panel: from the top menu, click Products → VMware-based Cloud → Cloud Director.
2. Open the virtual data center page.
3. Go to Compute → Virtual Machines.
4. Open the page of the virtual machine you want to associate with the global router.
5. Go to VM Hardware → NICs.
6. Press EDIT.
7. In the row with the new subnet that is connected to the Service Edge router, check the Primary NIC checkbox.
8. On the virtual machine, write static routes to the other subnets that are not connected to the global router and with which the virtual machine should communicate, through the address of your (client) Edge router — in the example 192.168.20.1. To the service subnets that are connected to the global router, routes do not need to be configured — the virtual machine will be accessible from them by default.

6. Prescribe static routes on dedicated and cloud servers⁠

If the global router is used as the default gateway on the cloud and dedicated servers, you do not need to specify routes.

If not, on the cloud and dedicated servers that are connected to the global router, write static routes:

• specify the CIDR of the new public cloud subnet as the destination subnet — in the example 192.168.2.0.0/24;

• as gateway, specify the address from the subnet to which the corresponding server is added and which is used as the gateway of the global router, in the example:

  • for a dedicated server — 192.168.0.1;
  • for the cloud server — 192.168.1.1.