# Troubleshooting IP Address Discovery for DHCP Networks PMO provides support for either a static IP address pool or external DHCP servers on a given network. This article describes the mechanism and troubleshooting for cases when an IP address for a given VM is not visible. ## Troubleshooting IP Address Discovery for DHCP Networks PMO uses host’s arp-cache to determine a VM’s IP address. Arp-cache is typically populated when an instance has network activity. If there is no network activity, the arp-cache is not populated and hence the instance won’t show the IP address. Practically, this is not an issue as every VM has one or another entity talking over the network. Some of the latest kernels and bridges that have bonds as their slaves do not populate the arp cache because of which IPs are not discovered. If this is something that you see please contact Platform9 support () and we can enable a more advanced IP discovery process for your hosts. In the case of PMO on VMware, the IP address for an instance is retrieved via VMwareTools installed on the instance. If this is not present, you may not see the IP address populated. --- # Agent Instructions: 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: ``` GET https://docs.platform9.com/managed-openstack/5.8/troubleshooting/linux-kvm/troubleshooting-kvm-dhcp-ip-discovery.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.