> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/verkada-cameras/configuration/camera-network-settings/use-lldp-with-cameras.md). # Use LLDP with Cameras Use LLDP to discover information about your Verkada cameras Verkada cameras support the Link Layer Discovery Protocol (LLDP). LLDP is a standard link layer protocol used across various network devices to advertise their identity, capabilities, and neighbors in a local area network (LAN). The primary value of using LLDP is to manage network integrations and troubleshooting. For example, a network admin can quickly identify which Verkada device is connected to a particular switch port or configure a policy to automatically reconfigure the port based on specific LLDP information. Verkada cameras advertise the following information every 30 seconds: * Device ID * Firmware revision * Serial number * Manufacturer name (Verkada) * Model name * Extreme Fabric Connect TLV * Auto-negotiation capabilities --- # 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://help.verkada.com/verkada-cameras/configuration/camera-network-settings/use-lldp-with-cameras.md?ask=&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.