> 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/solution/instance-failing-to-initialize-networking.md).

# Instance Failing to Initialize Networking (Unable to Receive DHCP Response)

## Problem

* Instance is failing to boot or be reachable.
* No DHCP reply is received.
* DHCP request is observed on both the physical (e.g. bond0) interface of both the hypervisor, and designated DHCP agent host(s).

## Environment

* Platform9 Managed OpenStack - All Versions

## Cause

Either on which the hypervisor on which the instance resides, or one of the associated hosts of the designated DHCP agents for the given network, the Linux/OVS bridge which is defined as part of the bridge\_mappings variable in `/opt/pf9/etc/pf9-neutron-ovs-agent/ml2.conf` is either invalid, or the bridge has no associated physical interface (e.g. bond0).

## Resolution

1. Ensure that `bridge_mappings` in the `/opt/pf9/etc/pf9-neutron-ovs-agent/ml2_conf.ini` configuration file on the affected host (whether the hypervisor, or DHCP host) has the correct physical interface name specified.
2. If it has been modified, restart the `pf9-neutron-ovs-agent` service.
3. Otherwise, ensure the physical interface is added to the specified interface, e.g.

{% tabs %}
{% tab title="Bash" %}

```bash
ovs-vsctl add-port br-pf9 bond0
```

{% endtab %}
{% endtabs %}


---

# 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 dynamically by asking a question.

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

```
GET https://platform9.com/kb/pmo/solution/instance-failing-to-initialize-networking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.