Configure connection to infrastructure outside Servercore

1. Ensure that you have connected the Direct Connect service – physical port.
2. Ensure that a global router network is created in your account and that all devices you need to connect to your external infrastructure via the provider channel are included in it.
3. Connect the Direct Connect network to the global router.
4. Assign an IP address from the Direct Connect subnet to the router in the external infrastructure.
5. Configure routing to the Direct Connect subnet in the global router network.
6. If several subnets are located behind the external router, configure routing on the global router.

1. Check service connection

Check that in the ticket for the service order you received a VLAN ID and this VLAN appeared in the Control panel: in the top menu, click Products → Dedicated Servers → Network → VLAN tab.

2. Check or create a global router network

Ensure that your account has a global router network and that all devices you need to connect to the external infrastructure are included in it. You can view created global routers in the Control panel: in the top menu, click Products → Global Router.

If you do not have a global router yet or need to create a new one, use the instructions in Create private connectivity via a global router.

3. Connect the Direct Connect network to the global router

1. In the Control panel, in the top menu click Products and select Global Router.
2. Open the router page → Networks tab.
3. Click Create network.
4. Enter a network name. It will only be used in the control panel.
5. Select the Servers and Hardware service.
6. Select the network location —the region and pool you specified when ordering the Direct Connect – physical port service.
7. Select or enter the VLAN to which the provider port is added. The VLAN ID can be found in the ticket you received when ordering the Direct Connect – physical port service.
8. If a trunk port is configured on the provider side, specify a Q-in-Q tag—a number from 2 to 4094.
9. Enter the subnet name. It will only be used in the control panel.
10. Enter the CIDR—the IP address and mask of the private subnet. You can choose any addressing that does not overlap with other subnets on the global router and with subnets used in your external infrastructure.
11. Enter the gateway IP address or leave the first address of the subnet, which is assigned by default. Do not assign this address to your devices so as not to disrupt network operation.
12. Enter service IPs or leave the last addresses of the subnet, which are assigned by default. Do not assign these addresses to your devices so as not to disrupt network operation.
13. Click Create network.
14. Optional: check the network topology on the global router. In the Control panel, in the top menu click Products → Global Router → router page → Network map.
15. If you specified a Q-in-Q tag, ensure that you enabled Q-in-Q on the switch port for the VLAN you specified in step 7.

4. Assign an IP address to the router in the external infrastructure

Assign an IP address from the Direct Connect subnet that you connected to the global router to the router in your external infrastructure.

The address must not match the gateway address or the service addresses you selected during connection. The gateway address and service addresses can be viewed in the Control panel: in the top menu, click Products → Global Router → global router page → open the card of the network to which the subnet belongs → Gateway field.

5. Configure routing to the Direct Connect subnet in the global router network

On all devices in the global router network, configure static routes to the Direct Connect subnet that you connected to the global router.

Set the next-hop to the IP address from the device subnet that is assigned to the global router as a gateway. You can view the gateway address in the Control Panel: in the top menu, click Products → Global Router → global router page → open the card of the network to which the subnet belongs → field Gateway.

Dedicated server

Ubuntu

1. Connect to the server.

2. Open the network configuration file with the vi text editor:

   vi /etc/netplan/01-netcfg.yaml

3. At the end of the data block for the required network interface, add a route:

   routes:
     - to: <ip_address>/<mask>
       via: <gateway>

   Specify:

   • <ip_address>/<mask> — the IP address of the Direct Connect subnet that you connected to the global router, including the mask;
   • <gateway> — the gateway for the current server subnet, which is specified on the global router.

4. Press the ESC key.

5. Exit the vi text editor and save your changes:

   :wq

6. Check the settings:

   sudo netplan try

7. Apply the changes:

   netplan apply

Debian

1. Connect to the server.

2. Open the network configuration file with the vi text editor:

   vi  /etc/network/interfaces

3. At the end of the data block for the required network interface, add the required route:

   up route add -net <ip_address> netmask <mask> gw <gateway>
   down route del -net <ip_address> netmask <mask> gw <gateway>

   Specify:

   • <ip_address> — the IP address of the Direct Connect subnet that you connected to the global router;
   • <mask> — the Direct Connect subnet mask, for example 255.255.255.0;
   • <gateway> — the gateway for the current server subnet, which is specified on the global router.

4. Press the ESC key.

5. Exit the vi text editor and save your changes:

   :wq

6. Restart the network:

   sudo /etc/init.d/networking restart

CentOS

1. Connect to the server.

2. Create and fill in a file to configure static routes:

   echo "<ip_address>/<mask> via <gateway>" >> /etc/sysconfig/network-scripts/route-<eth_name>

   Specify:

   • <ip_address>/<mask> — the IP address of the Direct Connect subnet that you connected to the global router, including the mask;
   • <gateway> — the gateway for the current server subnet, which is specified on the global router;
   • <eth_name> — the name of the local network interface.

3. Restart the network:

   systemctl restart network

Windows

1. Connect to the server via RDP or via KVM console.

2. Add the route:

   route -p ADD <ip_address> MASK <mask> <gateway> METRIC <x>

   Specify:

   • <ip_address> — the IP address of the Direct Connect subnet that you connected to the global router;
   • <mask> — the Direct Connect subnet mask, for example 255.255.255.0;
   • <gateway> — the gateway for the current server subnet, which is specified on the global router;
   • <x> — a parameter from 1 to 9999 that defines the priority of the specified gateway, 1 being the highest priority.

Cloud platform

To configure static routes for a cloud server, Managed Database cluster, or Managed Kubernetes cluster, you must configure a static route on the private subnet where the server or cluster resides.

When configuring the route, specify the destination subnet — the Direct Connect subnet that you connected to the global router.

6. Configure routing on the global router

If several subnets are located behind the router in your external infrastructure, add static routes to each of them or configure dynamic routing via BGP.

Add static routes

1. In the Control panel, in the top menu click Products and select Global Router.
2. Open the router page → Static Routes tab.
3. Click Create route.
4. Enter a route name—any name, it will only be displayed in the control panel.
5. Enter the CIDR of the destination subnet—this is the subnet located behind the router in your external infrastructure.
6. Enter the Next hop IP address—the IP address from the Direct Connect subnet that you assigned to the router in the external infrastructure.
7. Click Create.

Configure dynamic routing via BGP

1. In the Control panel, in the top menu click Products and select Global Router.
2. Open the router page → BGP tab.
3. Click Configure BGP.
4. Enter the BGP neighbor IP address (BGP neighbor) — an IP address from the Direct Connect subnet that you assigned to the router in the external infrastructure.
5. Enter an autonomous system (AS) number. You can specify a private AS from the 64512–65534 range, except for AS 64530, which is used for the global router.
6. Specify the tasks for which dynamic routing via BGP is required.
7. Click Create ticket. In the ticket, we will clarify the data and provide further instructions on organizing the connection.