Skip to main content
Link the public cloud to other products via a docking subnet with an add on client Edge router and configuring static routes
Last update:

Link the public cloud to other products via a docking subnet with an add on client Edge router and configuring static routes

With the help of global router Selectel can link the public cloud with other Selectel products that can be connected to a global router, more details in the instructions General information about Selectel Global Router service.

You can customize cohesion in several scenarios, see the instructions for other scenarios Ways to connect a public cloud to a global router.

Customization Description⁠

At your request, we will create a docking private subnet in the public cloud, which will not be visible in the list of networks in the virtual data center. Using the docking subnet, we will connect your (client) Edge router to a Service Edge router managed by Selectel. The gateway will be the service Edge router. On the client Edge router you will be able to configure NAT, Firewall and other features, see the instructions for more details Edge routers. You will define the network address and addresses for the Edge routers yourself and report them in the ticket to create a docked private subnet.

On the service Edge router we will write static routes to your selected public cloud subnets through the client Edge router as Next Hop, these routes are announced to the global router. When servers and other resources connected to the global router send packets to the public cloud subnets for which static routes have been written, the global router can address them correctly. After configuring connectivity, you can announce new subnets on the Service Edge router via a ticket.

On your Edge router, you autonomously prescribe static routes to servers and other resources outside the VMware-based public cloud that are connected to the global router, via the Service Edge router as the Next Hop.

What you need to customize⁠

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

Infrastructure elementInfrastructure network parameters in the example
Dedicated server on a private subnet
  • the server has been added to the subnet 192.168.0.0/24
  • gateway: 192.168.0.1
Cloud server on a private subnet
  • the server has been added to the subnet 192.168.1.0/24
  • gateway: 192.168.1.1
Virtual machine in the public cloud on a private subnet
  • the virtual machine is added to the subnet 192.168.2.0/24
  • gateway: 192.168.2.1
  • subnet added to the client Edge router.

Customization result⁠

In the example, the dedicated server, cloud server, and public cloud subnets will be connected through a global router using a public cloud docking network.

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 docking subnet to communicate with the global router.
  4. Write static routes on the Edge client router.
  5. Check the Firewall settings on the Edge client router.
  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 subnet of a dedicated server (in the example 192.168.0.0/24) and the subnet of the cloud platform (in the example 192.168.1.0/24) to the global router, use section Connect networks and subnets to a global router instructions Link products and services through a global router.

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

  1. Create a ticket with a request to create a public cloud docking private subnet that will connect the service Edge router to your (client) Edge router. In the ticket, specify:

    • The way to connect the public cloud to the global router is the second way;
    • The ID of the global router, can be found in the control panels under Network services → Selectel Global Router → router page → the field under the router name;
    • the name of the virtual data center, you can see in the control panels under VMware-based cloud → Virtual data centers → virtual data center card;
    • desired CIDR of the subnet — in the example 10.0.0.0/29;
    • the desired subnet gateway, this address will be assigned to the service Edge router — in the example 10.0.0.1;
    • the name of the Edge client router, you can see in the control panels under VMware-based cloud → Virtual data centers → virtual data center page → tab Edge routers;
    • the desired IP address for the Edge client router from the docking subnet — in the example 10.0.0.2;
    • a list of public cloud subnets that you want to associate with the global router — in the example 192.168.2.0/24.

  2. We will create a subnet and report it in the ticket.

4. Write static routes on the client Edge router⁠

Static routes are prescribed to all subnets that you want to associate the public cloud with through the global router.

  1. From control panels open the Cloud Director panel: in the top menu, click Products → VMware-based cloud → section Cloud Director.
  2. Go to the section Networking → Edge Gateways.
  3. Open your Edge router's page.
  4. Click SERVICES.
  5. Open the tab Routing →Static routes.
  6. Click +.
  7. In the field Network enter the subnet of the dedicated server — in the example 192.168.0.0/24.
  8. In the field Next Hop Specify the address of the Service Edge — in the example 10.0.0.1.
  9. Click KEEP.
  10. Repeat steps 6-9 for the cloud server subnet — in the example 192.168.1.0/24.

5. Check the Firewall settings⁠

Make sure the settings Firewall on your (client) Edge router allow the necessary traffic between the public cloud subnets and the subnets connected to the global router.

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 cloud and dedicated servers that are linked to a global router, static routes:

  • specify the CIDR of the new public cloud subnet as the destination subnet — in the example 192.168.2.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.