> 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/pmo/frequently-asked-questions/external-networks-are-not-visible-while-deploying-instances-in-c.md).

# External Networks Unavailable while Deploying Instances in Clarity UI

## Problem

* Unable to use external networks to create instance via Clarity UI
* Networks configured with `router:external` pointing to `External` are not able to be utilized while creating VMs on PMO.

## Environment

* Platform9 Managed OpenStack: All Versions
* Clarity UI

## Cause

* The provider network was created as an [external type](https://docs.openstack.org/install-guide/launch-instance-networks-provider.html) via enabling `router:external` that caused filtering out of the network to be inspected for available subnet IP allocations.
* Clarity UI restricts directly provisioning VMs from networks from an `External` as they are intended to be used to provide floating IPs.

## Resolution

* Disabling `router:external` or pointing it to `False` comes in as a workaround for the network to be used while deploying an instance.
* This can be done by editing into the desired network and uncheck the `External Network` field.

<figure><img src="https://3413721029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8o9pwjt91cVZOj58RUXj%2Fuploads%2Fgit-blob-532a0d6d8a4f20a6399ffe17773d9a3f7dc614c1%2Fs4vnbw1yv1eogif2orxwfgcnemhm85k55b5pes7nov7gon1t1rgp3xutrte3szdh.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/pmo/frequently-asked-questions/external-networks-are-not-visible-while-deploying-instances-in-c.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.