Link the public cloud to other products via a docking subnet with an add on client Edge router and configuring static routes
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 docking private subnet of the public cloud, which will not be visible in the list of networks in the virtual data center.With the docking subnet, we will connect your (client) Edge router to the 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, please refer to the Edge routers manual for more details.You will define the network addressing and addresses for the Edge routers yourself and provide them in the ticket to create the docking private subnet.
On the service Edge router we will write static routes to the public cloud subnets of your choice 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 are written, the global router will be able to 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 link to the public cloud via a global router for configuration.The infrastructure elements and its network settings are shown for example.
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
- Create a global router.
- Connect the subnets of the dedicated server and cloud platform to a global router.
- Create a docking subnet to communicate with the global router.
- Write static routes on the client Edge router.
- Check the Firewall settings on the client Edge router.
- 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 docking subnet to communicate with the global router
-
Create a ticket requesting the creation of a public cloud docking private subnet that will connect the service Edge router to your (customer) Edge router. In the ticket, specify:
- The way to connect the public cloud to the global router is the second 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 subnet — in the example
10.0.0.0.0/29; - desired subnet gateway, this address will be assigned to the Service Edge router — in the example
10.0.0.1; - name of the client Edge router, can be viewed in the Control Panel under VMware-based Cloud → Virtual Data Centers → Virtual Data Center page → Edge routers tab;
- the desired IP address for the Edge client router from the docking subnet — in the example
10.0.0.2; - list of public cloud subnets that you want to associate with the global router — in the example
192.168.2.0/24.
-
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.
- From the Control Panel, open the Cloud Director panel: from the top menu, click Products → VMware-based Cloud → Cloud Director.
- Go to Networking → Edge Gateways.
- Open your Edge router's page.
- Press SERVICES.
- Open the Routing → Static routes tab.
- Press +.
- In the Network field, enter the subnet of the dedicated server — in the example
192.168.0.0/24. - In the Next Hop field, specify the address of the Service Edge — in the example
10.0.0.1. - Press KEEP.
- Repeat steps 6-9 for the cloud server subnet — in the example
192.168.1.0.0/24.
5. Check the Firewall settings
Ensure that the Firewall settings on your (client) Edge router allow the required 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 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.
- for a dedicated server —