> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/other-pages/ip-network/configuring-a-vlan.md).

# Configuring a VLAN

> **Applies to:** SBC 3.1, 3.3

After you create a virtual port, you must create a new VLAN.

### To configure a VLAN

1. Select **IP Interfaces** from the navigation panel

![Create Vlan Interface Tsbc 0](https://docs.telcobridges.com/w/images/b/ba/Create_Vlan_Interface_Tsbc_0.png)

2. Click the **Virtual Ports** tab.

* Select a Virtual Port

![Create Vlan Interface Tsbc 1](https://docs.telcobridges.com/w/images/2/29/Create_Vlan_Interface_Tsbc_1.png)

3. Create a VLAN that uses this virtual port

* Click **Create new Host VLAN**

![Create Vlan Interface Tsbc 2](https://docs.telcobridges.com/w/images/c/c1/Create_Vlan_Interface_Tsbc_2.png)

4. Configure the new VLAN

**Important Note**

Vlans can be configured on the SBC in these cases:

* Baremetal installation
* VMware installation with Passthrough or SR-IOV network interfaces
* VMware installation with a network interface using vlan ID 4095

Vlans should **not** be configured on the SBC in this case:

* VMware installation with network interfaces using vlans from 1 to 4094 In this case, all interfaces on the SBC should be configured as untagged. Vlans are configured in the VMware port Groups.

Please check here: [How to add VMware Network Interfaces](https://prosbcdocs.telcobridges.com/)

If VLANs must be configured, follow these steps:

* Enter a name for the VLAN
* If the port is to be used untagged, make sure **Untagged** is checked.
* If the port is to be used with a 802.1Q tag, uncheck **Untagged** and enter a VLAN ID.
* Click **Create**

![Create Vlan Interface Tsbc 3](https://docs.telcobridges.com/w/images/9/91/Create_Vlan_Interface_Tsbc_3.png)

OR

![Create Vlan Interface Tsbc 4](https://docs.telcobridges.com/w/images/5/52/Create_Vlan_Interface_Tsbc_4.png)

### List of Parameters

* [Name](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [Untagged](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/untagged)
* [VLAN id](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/ip-network#v)
* [Allow ICMP](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/ip-network#a)
* [Allow IP fragmentation](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/ip-network#a)


---

# 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://tmediadocs.telcobridges.com/other-pages/ip-network/configuring-a-vlan.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.