# Create a CIDR Block

## **CIDR (Super Block) Deployment Model**

If your workload requires a super high volume of public IPv4 blocks, this model allows you to enable nearly unlimited super blocks within a region. All ECS and Bare Metal Servers (BMS) can attach to the same CIDR. It also provides two flexible internet data packages, which we will describe more in the **Networking** section.

***

<figure><img src="/files/TAixHBwSu3ksrD9gbjpc" alt=""><figcaption></figcaption></figure>

## The deployment workflow

{% stepper %}
{% step %}

### [Select Internet Package](#create-a-shared-data-package-shared-95th-bandwidth)

{% endstep %}

{% step %}

### [Create a CIDR Block](#create-a-cidr)

{% endstep %}

{% step %}

### [Associate the Internet Package with the CIDR](#bind-your-cidr-to-the-internet-package)

{% endstep %}

{% step %}

### [Create ECS/BMS](#bind-your-cidr-to-the-internet-package)

{% endstep %}

{% step %}

### [Select the corresponding Internet Package](#now-you-will-see-this-internet-package-when-you-create-ecs-bms)

{% endstep %}
{% endstepper %}

<figure><img src="/files/1RK7MQ67SkyAQe2OvosF" alt=""><figcaption></figcaption></figure>

***

### Create a Shared Data Package / Shared 95th Bandwidth

#### There are two internet package options available; both options provide sharing capabilities to reduce the cost of traffic usage. It is also suitable for workloads that require scalable options. Imagine your application or workload may require additional compute resources, and your ECS can leverage the same internet package to reduce the individual internet cost.

<table><thead><tr><th width="256">Package Name</th><th width="481">Option Details</th></tr></thead><tbody><tr><td>Shared Data Package</td><td>This option charged by traffic transaction</td></tr><tr><td>Shared 95th Bandwidth</td><td>Allows cloud servers (ECS) and bare metal products to share traffic simultaneously.</td></tr></tbody></table>

### Select the Region and Traffic

<figure><img src="/files/p5nyGMyDwdmXwadCj7U4" alt=""><figcaption></figcaption></figure>

### Create a CIDR

Go to the left menu again, and select Network -> CIDR Block&#x20;

Click on the Create CIDR Block Button

<figure><img src="/files/5i83XrBP3lm0KnnZzWFI" alt=""><figcaption></figcaption></figure>

### Select CIDR Region

<figure><img src="/files/tnsPoTaWuAAoJbmbTh7Y" alt=""><figcaption></figcaption></figure>

> <mark style="background-color:green;">**If you require a super large block of IPv4 addresses, please be sure to reach out to us, as our team can offer you a more cost-effective bundle package!**</mark>

{% hint style="info" %}
Similar to our internet packages, we offer several different IP types, but by default, the **"Global"** type is selected, which is the most general option. If your use case requires a specific IP type, please reach out to **<consolesupport@a-fieldtech.com>**.
{% endhint %}

***

### Check your CIDR Block

#### After the CIDR creation is successful, you can check your CIDR resources under the **"CIDR Block"** tab on the left-side menu bar.

<figure><img src="/files/WpKOmp1U1j5YmysnTyow" alt=""><figcaption></figcaption></figure>

### Bind Your CIDR to the Internet Package

Click on the **"Set Relationship"** from the left menu bar.

<figure><img src="/files/zYtv25X74UTdfF635Voc" alt=""><figcaption></figcaption></figure>

You will see this screen, and find your CIDR from the "drop menu" and Click the "Bind" button.

<figure><img src="/files/SOu8D8MgiktEZKEXIBd7" alt=""><figcaption></figcaption></figure>

***

### Now, you will see this internet package when you create ECS/BMS

<figure><img src="/files/4yBOlLLgrzPucMdehAPI" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.a-fieldtech.com/a-fieldtech-docs/network/create-a-cidr-block.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.