> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/private-cloud-director/virtualized-networking/troubleshooting-and-log-files.md).

# Troubleshooting And Log Files

## Troubleshooting Network Service Problems

If the Networking Service appears <mark style="color:red;">`Unhealthy`</mark> in the <code class="expression">space.vars.product\_name</code> Service Health page, this likely means that the networking service components running on one or more hosts are experiencing an issue. Reference the Networking Service [#log-files](#log-files "mention") to identify the specific error.

## Log Files

The Networking Service component log files are located at:

`/var/log/pf9/pf9-neutron-ovn-metadata-agent.log`

`/var/log/pf9/ovn/ovn-controller.log`

{% hint style="info" %}
**Agent naming**

`pcdctl network agent list` reports these components as the **OVN Neutron agent** and the **OVN Controller Gateway agent**. The on-host package, service, and log file names have not changed and still use the earlier `pf9-neutron-ovn-metadata-agent` naming shown above. This naming difference is expected and does not indicate a failed or incomplete deployment.
{% endhint %}

\## VM Cloud-Init Fails to Retrieve Metadata on a Physical Network

### Symptom

A virtual machine on a physical network boots without its SSH keys injected or its user data applied. The VM's console log shows repeated `Missing mandatory path` warnings for `meta_data.json`, ending in a `DataSourceNone` fallback message from cloud-init.

### Cause

A known cause is a flat physical network whose host interface also carries the hypervisor's own management traffic. When the host's management address falls inside the subnet's allocation pool, return traffic for the metadata connection can be misdirected back onto the physical uplink instead of the local metadata proxy, so the connection never completes before cloud-init exhausts its retries. This has been observed on flat networks; tagged (VLAN) physical networks and virtual networks are not known to be affected, since they do not share a physical bridge with host management traffic in the same way.

### Resolution

1. Check whether the host's management address is already allocated to a port:

   ```
   pcdctl port list --fixed-ip ip-address=<host-management-ip>
   ```

   If a port already owns that address, resolve the conflict before changing the allocation pool.
2. Narrow the subnet's allocation pool to exclude the host's management address and any other infrastructure addresses on the same interface:

   ```
   pcdctl subnet set <subnet-id> --no-allocation-pool
   pcdctl subnet set <subnet-id> \
     --allocation-pool start=<pool-start-ip>,end=<pool-end-ip>
   ```
3. For a more thorough fix, keep hypervisor management interfaces on a dedicated management network, separate from any physical network used for tenant workloads. This removes the shared-bridge condition rather than just working around it.

See [Physical Network](/private-cloud-director/virtualized-networking/physical-network.md#allocation-pools) for background on allocation pools.

## Related Pages

* [Physical Network](/private-cloud-director/virtualized-networking/physical-network.md#allocation-pools): allocation pool configuration for physical networks
* [Troubleshoot VM Metadata Service Connectivity Failures](https://platform9.com/kb/pcd-ts/networking/troubleshoot-vm-metadata-service-connectivity-failures): diagnose and recover VMs that can't reach the metadata service at boot


---

# 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://docs.platform9.com/private-cloud-director/virtualized-networking/troubleshooting-and-log-files.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.