> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/servers-1/how-to/how-to-create-a-vpc-and-associate-a-tier.md).

# How to Create a VPC and Associate a TIER in Plenit

A VPC lets you organize your Server environment network into separate subnets, the TIERs.

In this tutorial, you create a VPC and associate its first TIER with it, the basis for segmenting by layers (application, database) or later setting up a VPN between networks.

> #### 👍 What you get
>
> A created VPC with an associated TIER, ready for you to attach your servers to it and define access from the outside.

### What a VPC is and what a TIER is

A VPC is defined with a **Super CIDR**, the main network that contains all subnets. Each subnet is a **TIER**, which corresponds to a VLAN. All the TIERs in a VPC communicate with each other and with the Internet through a virtual router.

<figure><img src="https://files.readme.io/d7c96edeef779f98e91d7916d27fbbd992d574387ffe09750e02e5e2e0dc316f-diagram-vpc-tiers-servidores.png" alt=""><figcaption></figcaption></figure>

| Concept        | What it is                                                                           |
| -------------- | ------------------------------------------------------------------------------------ |
| Super CIDR     | The global range of the VPC, within which the TIERs live (for example `10.1.0.0/16`) |
| TIER           | A subnet within the VPC (for example `10.1.0.0/24`)                                  |
| Virtual router | What connects the TIERs to each other and to the Internet                            |

> #### 📘 Why segment into TIERs
>
> Separating the application layer from the database layer into different TIERs lets you control what talks to what, instead of having everything on a flat network.
>
> A VPC supports up to three TIERs on the same virtual router.

### Before you begin

* Having an active Servers subscription.
* If you don't have one yet, deploy a server first: [Deploy your server.](https://docs.plenit.com/docs-en/productos/servers/quickstart.md)

### Step 1. Access the Servers subscription

Enter the Servers subscription from its card in the service.

{/\* 📸 SCREENSHOT 1 · Servers subscription card \*/}

![Access to the Servers subscription](https://reemplaza-url/servidores-howto-vpc-01.png)

### Step 2. Open Networks/IP and create the VPC network

In the left side menu, open **Networks/IP**, select **VPC networks** and click **Create VPC network**.

{/\* 📸 SCREENSHOT 2 · left menu Networks/IP > VPC networks with the Create VPC network button \*/}

![VPC networks section with the Create VPC network button](https://reemplaza-url/servidores-howto-vpc-02.png)

### Step 3. Name the VPC

Enter a name to identify it easily, for example `VPC1`. If you leave it blank, we generate it automatically. Press **Continue**.

{/\* 📸 SCREENSHOT 3 · VPC name field and the auto-generated Super CIDR highlighted \*/}

![VPC naming with the auto-generated Super CIDR](https://reemplaza-url/servidores-howto-vpc-03.png)

> #### 📘 The Super CIDR, auto-generated but yours
>
> We generate the Super CIDR automatically, but you can change it. If you do, make a note of the range: the TIERs you create later must fit within it.

### Step 4. Add and name a TIER

When the VPC has been created, you'll see a notice that it still doesn't contain any TIER. Press the **three dots** on the VPC and choose **Add Tier**. Enter a name, for example `TIER1`. If you leave it blank, we'll fill it in for you.

The platform assigns a range by default `10.1.0.0/24`, which is contained within the Super CIDR `10.1.0.0/16`. When you're done, the VPC and its TIER appear in **Networks/IP → VPC Networks**.

{/\* 📸 SCREENSHOT 4 · three-dots menu with "Add Tier" and the TIER name field \*/}

![Add a TIER to the VPC from the three-dots menu](https://reemplaza-url/servidores-howto-vpc-04.png)

> #### 👍 Use clear names from the start
>
> Naming VPCs and TIERs well (by function or by layer) saves you time when the network grows and you need to know at a glance what each thing is.

### Check the network from a server

When you connect a server to the TIER, confirm from inside that it has received the correct IP and gateway.

In Linux:

```shell
ip addr show      # the IP and mask assigned to the server
ip route          # the gateway (the virtual router)
```

In Windows, from PowerShell or CMD:

```powershell
ipconfig /all
```

To check connectivity with another server on the network, run `ping` to its IP. In Windows, the firewall blocks incoming ICMP by default, so allow it on the destination server with an inbound rule:

```powershell
New-NetFirewallRule -DisplayName "ICMPv4-In" -Protocol ICMPv4 -IcmpType 8 -Direction Inbound -Action Allow
```

### Plan the ranges before you grow

The biggest oversight when setting up several VPCs is overlapping ranges, which breaks routing as soon as you connect them. Reserve a different Super CIDR per VPC from the start.

| Item         | VPC1          | VPC2          |
| ------------ | ------------- | ------------- |
| Super CIDR   | `10.1.0.0/16` | `10.2.0.0/16` |
| Example TIER | `10.1.0.0/24` | `10.2.0.0/24` |

### Next steps

* To connect two VPCs, create a second one (for example `VPC2` with `10.2.0.0/16`, without overlapping) and bring up the tunnel: [How to create a site-to-site VPN tunnel.](https://docs.plenit.com/docs-en/productos/servers/how-to/how-to-create-a-site-to-site-vpn-tunnel.md)
* The VPC is the only type of network with site-to-site IPSec VPN, and you can connect it with VPCs from other cloud providers or with compatible equipment (Cisco ISR with IOS 12.4 or later, Juniper J-Series routers with JunOS 9.5 or later).
* To review the network types: [Server networks.](https://docs.plenit.com/docs-en/productos/servers/concepts/networks.md)

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/productos/servers-1/how-to/how-to-create-a-vpc-and-associate-a-tier.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
