---
title: "Connect a server in a DC to a dedicated server in the same pool"
sidebar_label: "Connect a server in a DC to a dedicated server in the same pool"
sidebar_position: 1
description: "How to connect a server in a DC to a dedicated server in the same pool via a private network"
---
import MoreVerticalIcon from '@selectel/docux/icons/more-vertical'
import Formbricks from '@theme/MDXComponents/Formbricks'
import EditIcon from '@selectel/docux/icons/edit'
import Tabs from '@theme/Tabs'
import TabItem from '@theme/TabItem'
import {TabItemLabel} from '@selectel/docux/components'
# Connect a server in a DC to a dedicated server in the same pool
Within a single [pool](/infrastructure/locations.mdx#pool), a server located in a DC and a [dedicated server](/dedicated/about/about-dedicated.mdx) outside the DC can be connected to a private (local) L3 network.
Network connectivity is provided via a [firewall](/firewalls/), which is located in the DC, and Selectel network equipment.
## How it works \{#principle-of-operation}
A dedicated server in a DC connects directly to the firewall in the DC. A dedicated server outside the DC and the firewall in the DC are connected via Selectel local network switches.
Configure IP addresses from the same private subnet on the network interfaces of the firewall in the DC and the server outside the DC.
Dedicated servers, except for some Chipcore Line servers, are connected to Selectel local network switches by default and included in a dedicated VLAN. The firewall in the DC is connected to the local network via technical support; the port for the firewall is provided free of charge.
## Connect a server in a DC to a dedicated server in the same pool via a private network \{#create-private-network-cdc-to-dedicated-one-pool}
1. [Connect the firewall to the VLAN of the server outside the DC](#configure-private-network-between-devices).
2. [Configure the firewall](#configure-firewall).
3. [Configure the dedicated server](#configure-dedicated-server).
### 1. Connect the firewall to the private VLAN of the server outside the DC \{#configure-private-network-between-devices}
1. [Create a ticket](https://my.selectel.ru/tickets/create/) to connect the firewall to the private VLAN of the server outside the DC. In the ticket, specify:
* Dedicated server ID, you can copy it in the [control panel](https://my.selectel.ru/servers/): in the top menu, click **Products** → **Dedicated Servers** → server page → copy the ID under the server name;
* firewall number in the DC, you can view it in the [control panel](https://my.selectel.ru/network/firewalls/): in the top menu, click **Products** → **Firewalls** → firewall page;
* the local port number on the firewall for connecting to the local network switch.
2. A Selectel employee will connect the firewall to the private network and configure one private VLAN on the private network switches for the server outside the DC and the firewall.
3. Wait for a response from the Selectel employee confirming that the private network between the devices has been set up.
### 2. Configure the firewall \{#configure-firewall}
FortiGate
1. [Connect to FortiGate via the graphical interface](/firewalls/fortigate/connect-to-firewall.mdx).
2. On the private network interface, configure an IP address from the subnet you want to use to establish connectivity:
2.1. Go to **Network** → **Interfaces**.
2.2.For the port interface you specified in the ticket for connecting the firewall, click .
2.3. In the **IP/Netmask** field, enter an available IP address from any private subnet you want to use for connectivity, for example `192.168.100.1/24`.
2.4.Click **OK**.
3. Configure a security policy that allows traffic from the dedicated server outside the DC to the dedicated server in the DC:
3.1.Go to **Policy & Objects** → **Firewall Policy**.
3.2.Click **Create New**.
3.3. Enter a policy name.
3.4.In the **Incoming Interface** field, select the interface for which you configured the IP address in step 2.
3.5.In the **Outgoing Interface** field, select the interface to which the dedicated server in the A-DC is connected.
3.6.In the **Source** field, enter another IP address from the same private subnet you configured on the firewall in step 2. This address will be used on the dedicated server outside the A-DC.
3.7.In the **Destination** field, enter the IP address of the dedicated server in the A-DC.
3.8.Click **Save**.
4. Configure a security policy that allows traffic from the dedicated server outside the DC to the dedicated server in the DC:
4.1.Go to **Policy & Objects** → **Firewall Policy**.
4.2.Click **Create New**.
4.3. Enter a policy name.
4.4.In the **Incoming Interface** field, select the interface to which the dedicated server in the A-DC is connected.
4.5.In the **Outgoing Interface** field, select the interface for which you configured the IP address in step 2.
4.6.In the **Source** field, enter the IP address of the dedicated server in the A-DC.
4.7.In the **Destination** field, enter the IP address that will be used on the dedicated server outside the A-DC.
4.8.Click **Save**.
### 3. Configure the dedicated server outside the DC \{#configure-dedicated-server}
1. On the network interface of the private network of the server outside the A-DC, configure an available IP address from the subnet you [configured on the firewall](#configure-firewall). Use the [Configure private network interface](/dedicated/networks/configure-network-interface-on-server.mdx#configure-network-interface-of-private-network) section of the [Configure network interface on server](/dedicated/networks/configure-network-interface-on-server.mdx) guide. The private network for a dedicated server is provided on the network interface with the highest MAC address value.
2. [Add a static route](/dedicated/networks/static-routes.mdx#write-routes-on-server) on the network interface you configured in step 1. In the route, specify:
* destination subnet — the subnet of the server in the DC;
* gateway — the firewall address from the subnet you configured on both the firewall and the server outside the DC.