> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pcd/networking/mtu-for-virtual-networks-cannot-be-modified.md).

# MTU for Virtual Networks Cannot be Modified

## Problem

* MTU for Virtual Networks cannot be modified.
* PCD UI does not provide any option to increase the MTU for Virtual Networks.

## Environment

* Private Cloud Director Virtualization - v2026.1 and Higher
* Self Hosted Private Cloud Director Virtualization - v2026.1 and Higher

## Cause

* This is a known issue and is already reported with ID: **PCD-6454**.

{% hint style="info" %}
Refer the [**Workaround**](#workaround) section on how to set the MTU for Virtual Networks.
{% endhint %}

## Workaround

* MTU for Virtual Networks can be modified through CLI.
* In the RC file that is needed for the communication between `pcdctl` CLI and PCD, change the variable `OS_INTERFACE` value from `public` to `admin`.
* Set the relevant tenant name in the `OS_PROJECT_NAME` variable if applicable.
* Re-source the RC file.
* Change the MTU using the below command:

{% code title="" %}

```bash
pcdctl network set --mtu <MTU_VALUE> <NETWORK_UUID/NAME>
```

{% endcode %}

## Additional Information

* Reach out to Platform9 Support with the issue ID mentioned in the [**Cause**](#cause) section if there are any questions/concerns.


---

# 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://platform9.com/kb/pcd/networking/mtu-for-virtual-networks-cannot-be-modified.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.
