Skip to main content

Connect Public Cloud to other products via a Public Cloud interconnection subnet by adding the subnet to the client Edge Router and setting up a BGP session

Using the global router, you can connect the public cloud to other Selectel products that support connection to the global router; for details, see the Selectel Global Router service overview instructions.

You can configure connectivity using several scenarios; to view other scenarios, see the Methods for connecting Public Cloud to the global router instructions.

Configuration description

Upon your request, we will create an interconnect private subnet of the public cloud, which will not be visible in the list of virtual data center networks. Using the interconnect subnet, we will connect your (client) Edge router to the service Edge router managed by Selectel. The service Edge router will serve as the gateway. On the client Edge router, you can configure NAT, Firewall, and other features; for details, see the Edge routers instructions. You will define the network addressing and addresses for the Edge routers yourself and provide them in the ticket to create the interconnect private subnet.

A BGP session is established between the service and client Edge Routers: you configure BGP parameters on the client Edge Router side, and we perform the configuration on the service Edge Router side.

For each subnet interacting with Global Router, you configure route redistribution on the client Edge Router. Route exchange between the client Edge Router and Global Router will be performed automatically via the service Edge Router.

You can connect virtual machines to the subnets added to the Edge Router; they will use the client Edge Router address as their gateway.

Prerequisites

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

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

Configuration result

In the example, the dedicated server, cloud server, and Public Cloud subnets will be connected via Global Router using a Public Cloud interconnect network.

Configuration steps

  1. Create a global router.
  2. Connect the dedicated server and Cloud Platform subnets to the global router.
  3. Create an interconnect subnet to connect to the global router.
  4. Configure BGP.
  5. Configure Route Redistribution on the Edge router.
  6. Check Firewall settings on the client Edge router.
  7. Specify static routes on dedicated and cloud servers.

1. Create a Global Router

  1. In the control panel, in the top menu, click Products and select Global Router.
  2. Click Create router. Each account has a limit of five global routers.
  3. Enter the router name.
  4. Click Create.
  5. If the router was created with the status ERROR or is stuck in one of the statuses, create a ticket.

2. Connect the dedicated server and cloud platform subnets 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 the global router, use the Connect networks and subnets to the global router ⁠ section of the Connect products and services via global router instructions.

3. Create an interconnect subnet to connect to the Global Router

  1. Create a ticket requesting the creation of an interconnect private subnet of the public cloud that will connect the service Edge router to the client Edge router. In the ticket, specify:

    • the Public Cloud to Global Router connection method — the third method;

    • virtual data center name, which can be viewed in the control panel under Cloud Powered by VMware → Virtual Data Centers → virtual data center card;

    • desired subnet CIDR — 10.0.0.0/29 in the example;

    • desired subnet gateway; this address will be assigned to the service Edge router — 10.0.0.1 in the example;

    • global router ID, which can be viewed in the control panel under Network Services → Selectel Global Router → router page → field below the router name;

    • client Edge router name, which can be viewed in the control panel under Cloud Powered by VMware → Virtual Data Centers → virtual data center page → Edge Routers tab;

    • desired IP address for the client Edge router from the interconnect subnet — 10.0.0.2 in the example;

    • the desired Autonomous System Number (ASN) for the client Edge Router;

    • optional: additional session parameters. If these are not specified, the default values are used:

      • Weight — 60;
      • Keep Alive Time (Seconds) — 5;
      • Hold Down Time (Seconds) — 15.

  2. We will create the subnet and inform you in the ticket.

4. Configure BGP

  1. From the control panel, open the Cloud Director panel: in the top menu, click Products → Cloud Powered by VMware → the Cloud Director section.
  2. Go to Networking → Edge Gateways.
  3. Open the page for your Edge Router.
  4. Click SERVICES.
  5. Open the Routing → Routing Configuration tab.
  6. In the DYNAMIC ROUTING CONFIGURATION block, in the Router ID field, select one of the Edge router interfaces.
  7. Click Save changes.
  8. Open the Routing → BGP tab.
  9. Turn on the Enable BGP toggle switch.
  10. In the Local AS field, enter your AS number.
  11. In the Neighbors block, click +.
  12. In the IP Address field, enter the service Edge router address — in the example, 10.0.0.1
  13. In the Remote AS field, enter the ASN value we sent in the ticket.
  14. In the Weight field, enter 60 or the value you specified in the ticket.
  15. In the Keep Alive Time field, enter 5 or the value you specified in the ticket.
  16. In the Hold Down Time field, enter 15 or the value you specified in the ticket.
  17. Turn on the Remove Private AS toggle switch.
  18. Optional: to restrict sending and receiving routes, configure BGP filters in the BGP Filters block.
  19. Click KEEP.

5. Configure route redistribution

  1. From the control panel, open the Cloud Director panel: in the top menu, click Products → Cloud Powered by VMware → the Cloud Director section.
  2. Go to Networking → Edge Gateways.
  3. Open the page for the client Edge Router.
  4. Click SERVICES.
  5. Open the Routing → Route Redistribution tab.
  6. Turn on the BGP Status toggle switch.
  7. In the Ip Prefixes block, click + and add the public cloud subnet that you are connecting to the global router — in the example, 192.168.2.0/24
  8. Click KEEP.
  9. Repeat steps 7-8 for all Public Cloud networks you want to connect to the Global Router.
  10. In the Route Redistribution Table block, click +.
  11. In the Prefix Name field, select Ip Prefix — the public cloud subnet for which the allow rule will be configured.
  12. In the Learner Protocol field, select BGP.
  13. In the Allow learning from field, select the Connected checkbox.
  14. In the Action field, select Permit.
  15. Click KEEP.
  16. Repeat steps 10-15 for all Ip Prefixes.
  17. In the Route Redistribution Table block, click +.
  18. In the Prefix Name field, select Any.
  19. In the Learner Protocol field, select BGP.
  20. In the Allow learning from field, select the OSPF, Static Routes, Connected checkboxes.
  21. In the Action field, select Deny.
  22. Click KEEP.
  23. Click Save changes.
  24. Make sure that the Deny rule is added last in the list.

6. Check Firewall settings

Make sure that the Firewall settings on your Edge router allow the required traffic between the public cloud subnets and the subnets connected to the global router.

7. Add static routes on the dedicated and cloud servers

If Global Router is used as the default gateway on the cloud and dedicated servers, you do not need to add static routes.

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

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

  • as the gateway, specify the address from the subnet to which the corresponding server is added and which is used as the Global Router gateway; in the example:

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