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

Last update:

With a Global Router, you can connect Public Cloud to other Selectel products that support Global Router. For more information, see General information about the Selectel Global Router service.

There are several scenarios for configuring connectivity; you can view other scenarios in the guide Ways to connect Public Cloud to Global Router.

Configuration description

Upon your request, we will create a private interconnect subnet for Public Cloud that will not be visible in the virtual data center network list. Using this interconnect subnet, we will connect your (client) Edge Router to a service Edge Router managed by Selectel. The service Edge Router will act as the gateway. You can configure NAT, Firewall, and other functions on the client Edge Router; for more details, see the Edge Routers guide. You will define the network addressing and Edge Router addresses yourself and provide them in a ticket to create the private interconnect 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 the subnet 192.168.0.0/24
  • gateway: 192.168.0.1
Cloud server in a private subnet
  • server added to the subnet 192.168.1.0/24
  • gateway: 192.168.1.1
Virtual machine in Public Cloud in a private subnet
  • virtual machine added to the 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 the Firewall settings on the client Edge Router.
  7. Add static routes on the 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. A limit of five global routers is set for each account.
  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 (in the example 192.168.0.0/24) and the cloud platform subnet (in the example 192.168.1.0/24) to the Global Router, use the Connect networks and subnets to Global Router guide section.

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

  1. Create a ticket requesting the creation of a private Public Cloud interconnect subnet that will connect the service Edge Router with the client Edge Router. In the ticket, specify:

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

    • the name of the virtual data center; you can find it in the Control Panel under VMware-based cloud → Virtual Data Centers → virtual data center card;

    • the desired subnet CIDR — 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;

    • Global Router ID; can be found in the Control Panel under Network Services → Selectel Global Router → router page → field under the router name;

    • client Edge Router name; can be found in the Control Panel under VMware-based cloud → Virtual Data Centers → virtual data center page → Edge Routers tab;

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

    • 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 → VMware-based cloud → Cloud Director.
  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. Enable the Enable BGP 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 provided in the ticket.
  14. In the Weight field, specify 60 or the value you specified in the ticket.
  15. In the Keep Alive Time field, specify 5 or the value you specified in the ticket.
  16. In the Hold Down Time field, specify 15 or the value you specified in the ticket.
  17. Enable the Remove Private AS switch.
  18. Optional: to limit route reception and transmission, in the BGP Filters block, configure BGP filters.
  19. Click KEEP.

5. Configure route redistribution

  1. From the Control Panel, open the Cloud Director panel: in the top menu, click Products → VMware-based cloud → Cloud Director.
  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. Enable the BGP Status switch.
  7. In the Ip Prefixes block, click + and add the Public Cloud subnet 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 an Ip Prefix — the Public Cloud subnet for which a permit 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, and Connected checkboxes.
  21. In the Action field, select Deny.
  22. Click KEEP.
  23. Click Save changes.
  24. Ensure that the Deny rule is added to the end of the list.

6. Check Firewall settings

Ensure that the Firewall settings on your Edge Router allow the necessary 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 that are connected to the Global Router, add static routes:

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

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